Vista - 0x124 BSoD (with minidump)

**jrobinson3k1** · 05-04-2009

Hi all,

I'm getting a very irritating BSoD. I recently reformatted and reinstalled Vista x86 and have been getting random BSoDs that I didn't get before. It only happens when I'm playing games. Sometimes it's 5 minutes into the game, other times it takes an hour or more. Also, this could be a likely problem, but I recently bought a 2nd harddrive and set up both harddrives in a RAID 0 array. They are different sizes, however (160GB and 320GB), but I was farely certain that the size difference wouldn't be a big deal (knowing it should just treat the 320GB as 160GB). Can different brand/speed harddrives be a reason for hardware failure when setting them up in RAID? Here's my minidump.

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 85def3f0, Address of the WHEA_ERROR_RECORD structure.
Arg3: b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

STACK_TEXT:  
81930f38 818118b5 00000124 00000000 85def3f0 nt!KeBugCheckEx+0x1e
81930f8c 818fe928 85def3f0 8515b580 8515b580 hal!HalBugCheckSystem+0xe1
81930fb8 818117c9 8515b580 00000000 81930ff4 nt!WheaReportHwError+0x1d0
81930fc8 81811ea7 00000003 8515b580 00000000 hal!HalpReportMachineCheck+0x31
81930ff4 8180d99f 80154000 00000000 00000000 hal!HalpMcaExceptionHandler+0xf7
81930ff4 00000000 80154000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel__UNKNOWN

BUCKET_ID:  0x124_GenuineIntel__UNKNOWN

Followup: MachineOwner

BTW, I've had numerous crashes, yet this is the first time it actually wrote a minidump file (yes, I've had it enabled the whole time). 1/2 the time the computer automatically restarts (no BSoD), and usually the rest of the time it says it writes the memory dump but it never does. So I'm lucky to of finally got something to hopefully pin-point my problem.

ambientmf · 05-04-2009

I don't think your RAID array is the problem, you'd probably be having trouble booting into Windows if there was a hardware failure with your drives.

I'm guessing an issue with your graphics drivers?
Have you updated to the latest versions?
Are you using a nvidia based card or ATI based card?

**H2SO4** · 05-04-2009

Well written problem description. Have some rep.

A stop 0x124 means the hardware has complained about something and Windows is passing along the message. The memory dump is devoid of pertinent info except for these two numbers, from your post:

Arg3: b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.

They're bitmasks and between them they make a 64-bit binary number:

10110010 00000000 00000000 01000000 00000000 00000000 00001000 00000000
^ bit "63", the "most significant" bit. The zero on the right end is bit "0".

To understand what each of the 1s signifies in your instance, you might want to review chapter 14 of this Intel doc:

http://www.intel.com/Assets/PDF/manual/253668.pdf

**jrobinson3k1** · 05-04-2009

Thanks for the replies.

If you click the link at the bottom left of my post you can see my system specs. The only difference now is I am running Vista Business x86 (because I thought x64 could be the culprit). Though I still get the same problem with x86, they're not nearly as frequent as they were before (guaranteed to crash within 5 minutes with x64). I have 2x GeForce 8800 GT in SLI (with SLI enabled) and running the latest drivers.

I also recently bought a 2nd monitor, but am highly doubtful that would cause an internal hardware failure.

I had stumbled across that PDF before, it's a very good find. I was in the process of separating the bits last night to determine my problem, but it was late and I didn't get to finish. Was difficult having to go back and forth between different pages of the PDF to get the information I needed. :P

Also, everything is running stock (no overclocking).

**jrobinson3k1** · 05-04-2009

OK, here's my analysis of the 64-bit MCi status

Code:

10110010 00000000 00000000 01000000 00000000 00000000 00001000 00000000

VAL - 1
OVER - 0
UC - 1
EN - 1
MISCV - 0
ADDRV - 0
PCC - 1
Reserved - 00
Threshold-based error status - 00
Other Information - 00000 00000000 01000000
Model-specific Error Code - 00000000 00000000
MCA Error Code - 00001000 00000000

I'm just going to type this up as I decipher it.

Looking at the MCA Error Code, I determine it's a compound error code. Looking at the types, it looks like 000F 1PPT RRRR IILL fits the bill of my error code. This is a Bus and Interconnect Error type.

Code:

0000 1000 0000 0000
000F 1PPT RRRR IILL

F is 0, so I have "normal" filtering.
LL is 00, which is a level 0 hierarchy level and mnemonic L0.
RRRR is 0000, which indicates a generic error with mnemoic ERR
PP is 00, local processor originated request, mnemoic SRC
T is 0, no time-out, mnemoic NOTIMEOUT
II is 00, memory access, mnemoic M

BUSL0_SRC_ERR_M_NOTIMEOUT_ERR

All right, so I have no idea what that means, but there it is. The PDF says to reference Appendix E, but it only appears to go to Chapter 17. Where's the rest of the PDF!?! Well if anyone knows these codes by hearts, please let me know if you can pick out any possible culprits! Thanks.

**stormy13** · 05-04-2009

More info here,

Solution to STOP 0x00000124

and Microsoft knows about it and have a hotfix for it,

The system may stop responding during restart when a computer that is running Windows Server 2008 or Windows Vista Service Pack 1 has a PCI Express interface

**jrobinson3k1** · 05-04-2009

Thanks, I'll try that out once I get off work and let you know if that works.

**jrobinson3k1** · 05-05-2009

I flashed an update for the BIOS and no problems since then. Thanks for the help!

**jrobinson3k1** · 05-16-2009

Nevermind, it's still doing it, though its rarer now for whatever reason. Only happens during WoW (hasn't crashed any other games in a while). Nothing in particular seems to trigger it. Any other suggestions are welcome.

**H2SO4** · 05-16-2009

Quote: Originally Posted by jrobinson3k1

Nevermind, it's still doing it, though its rarer now for whatever reason. Only happens during WoW (hasn't crashed any other games in a while). Nothing in particular seems to trigger it. Any other suggestions are welcome.

Perhaps some of this info may be useful to you:

Please help with BSOD STOP 0x00000124

MCEs are frequently encountered during periods of above-average load.

05-04-2009	#2 (permalink)
ambientmf Windows 7 RC x64 (previously Vista Business x64) 4 posts	Re: 0x124 BSoD (with minidump) I don't think your RAID array is the problem, you'd probably be having trouble booting into Windows if there was a hardware failure with your drives. I'm guessing an issue with your graphics drivers? Have you updated to the latest versions? Are you using a nvidia based card or ATI based card?
My System Specs

05-04-2009	#3 (permalink)
H2SO4 Win7x64 1,241 posts	Re: 0x124 BSoD (with minidump) Well written problem description. Have some rep. A stop 0x124 means the hardware has complained about something and Windows is passing along the message. The memory dump is devoid of pertinent info except for these two numbers, from your post: Arg3: b2000040, High order 32-bits of the MCi_STATUS value. Arg4: 00000800, Low order 32-bits of the MCi_STATUS value. They're bitmasks and between them they make a 64-bit binary number: 10110010 00000000 00000000 01000000 00000000 00000000 00001000 00000000 ^ bit "63", the "most significant" bit. The zero on the right end is bit "0". To understand what each of the 1s signifies in your instance, you might want to review chapter 14 of this Intel doc: http://www.intel.com/Assets/PDF/manual/253668.pdf
My System Specs

05-04-2009	#4 (permalink)
jrobinson3k1 Vista Business x64 11 posts	Re: 0x124 BSoD (with minidump) Thanks for the replies. If you click the link at the bottom left of my post you can see my system specs. The only difference now is I am running Vista Business x86 (because I thought x64 could be the culprit). Though I still get the same problem with x86, they're not nearly as frequent as they were before (guaranteed to crash within 5 minutes with x64). I have 2x GeForce 8800 GT in SLI (with SLI enabled) and running the latest drivers. I also recently bought a 2nd monitor, but am highly doubtful that would cause an internal hardware failure. I had stumbled across that PDF before, it's a very good find. I was in the process of separating the bits last night to determine my problem, but it was late and I didn't get to finish. Was difficult having to go back and forth between different pages of the PDF to get the information I needed. :P Also, everything is running stock (no overclocking).
My System Specs

05-04-2009	#5 (permalink)
jrobinson3k1 Vista Business x64 11 posts	Re: 0x124 BSoD (with minidump) OK, here's my analysis of the 64-bit MCi status Code: 10110010 00000000 00000000 01000000 00000000 00000000 00001000 00000000 VAL - 1 OVER - 0 UC - 1 EN - 1 MISCV - 0 ADDRV - 0 PCC - 1 Reserved - 00 Threshold-based error status - 00 Other Information - 00000 00000000 01000000 Model-specific Error Code - 00000000 00000000 MCA Error Code - 00001000 00000000 I'm just going to type this up as I decipher it. Looking at the MCA Error Code, I determine it's a compound error code. Looking at the types, it looks like 000F 1PPT RRRR IILL fits the bill of my error code. This is a Bus and Interconnect Error type. Code: 0000 1000 0000 0000 000F 1PPT RRRR IILL F is 0, so I have "normal" filtering. LL is 00, which is a level 0 hierarchy level and mnemonic L0. RRRR is 0000, which indicates a generic error with mnemoic ERR PP is 00, local processor originated request, mnemoic SRC T is 0, no time-out, mnemoic NOTIMEOUT II is 00, memory access, mnemoic M BUSL0_SRC_ERR_M_NOTIMEOUT_ERR All right, so I have no idea what that means, but there it is. The PDF says to reference Appendix E, but it only appears to go to Chapter 17. Where's the rest of the PDF!?! Well if anyone knows these codes by hearts, please let me know if you can pick out any possible culprits! Thanks.
My System Specs

05-04-2009	#6 (permalink)
stormy13 Vista Ultimate x64 607 posts	Re: 0x124 BSoD (with minidump) More info here, Solution to STOP 0x00000124 and Microsoft knows about it and have a hotfix for it, The system may stop responding during restart when a computer that is running Windows Server 2008 or Windows Vista Service Pack 1 has a PCI Express interface
My System Specs

05-04-2009	#7 (permalink)
jrobinson3k1 Vista Business x64 11 posts	Re: 0x124 BSoD (with minidump) Thanks, I'll try that out once I get off work and let you know if that works.
My System Specs

05-05-2009	#8 (permalink)
jrobinson3k1 Vista Business x64 11 posts	Re: 0x124 BSoD (with minidump) I flashed an update for the BIOS and no problems since then. Thanks for the help!
My System Specs

05-16-2009	#9 (permalink)
jrobinson3k1 Vista Business x64 11 posts	Re: 0x124 BSoD (with minidump) Nevermind, it's still doing it, though its rarer now for whatever reason. Only happens during WoW (hasn't crashed any other games in a while). Nothing in particular seems to trigger it. Any other suggestions are welcome.
My System Specs

05-16-2009	#10 (permalink)
H2SO4 Win7x64 1,241 posts	Re: 0x124 BSoD (with minidump) Quote: Originally Posted by jrobinson3k1 Nevermind, it's still doing it, though its rarer now for whatever reason. Only happens during WoW (hasn't crashed any other games in a while). Nothing in particular seems to trigger it. Any other suggestions are welcome. Perhaps some of this info may be useful to you: Please help with BSOD STOP 0x00000124 MCEs are frequently encountered during periods of above-average load.
My System Specs

Similar Threads
Thread	Forum
BSOD (with minidump)	Drivers
BSOD issue on new computer, minidump included	General Discussion
BSOD minidump analysis	Vista performance & maintenance
BSOD -- need help understanding minidump	Vista General
BSOD and minidump points to ntfs.sys	Vista performance & maintenance