BsOD: 0x00000124

[pr0grammer1]

This happened when quitting the Crysis demo. I've been having similar crashes for a while. I've overclocked my CPU, GPU and graphics memory before, but none of it is currently overclocked.


OS: Vista Home Premium x64
CPU: C2Q Q6600
Motherboard: XFX 680i LT SLI
Memory: 4GB OCZ DDR2-800MHz
Graphics Card: Palit 8800GT Super+1GB
Hard Drives: 2x Maxtor 500GB SATA-II


A picture of the error (Sorry it's a little blurry) :

Here's what WinDbg gave me from Memory.dmp:

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: 0000000000000000, MCA_ASSERT
Arg2: fffffa8008045c6e, Address of WHEA_ERROR_RECORD structure
Arg3: 00000000b2000040, High 32 bits of MCi_STATUS MSR for the MCA bank that had
    the error
Arg4: 0000000000000800, Low  32 bits of MCi_STATUS MSR for the MCA bank that had
    the error

Debugging Details:
------------------


WHEA_ERROR_RECORD: !errrec fffffa8008045c6e

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffffa60`0176a958 fffff800`01e0f72a : 00000000`00000124 00000000`00000000 fffffa80`08045c6e 00000000`b2000040 : nt!KeBugCheckEx
fffffa60`0176a960 fffff800`01f713b3 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000001 : hal!HalBugCheckSystem+0x12e
fffffa60`0176a9d0 fffff800`01e0f097 : fffffa60`00000c3e fffffa60`0176abb0 fffffa60`0176ac30 00000000`00000000 : nt!WheaReportHwError+0x243
fffffa60`0176aa30 fffff800`01ea25f1 : 00000000`00000000 fffffa60`0176ac30 fffffa80`04f17f00 00000000`00000000 : hal!HalpMcaExceptionHandler+0xf3
fffffa60`0176aa70 fffff800`01ea2435 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x71
fffffa60`0176abb0 fffffa60`00905d3c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
fffffa60`0178aae8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : acpi!DefPortReadAcpiRegister+0x104


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel

BUCKET_ID:  X64_0x124_GenuineIntel

Followup: MachineOwner
---------

The "X64_0x124_GenuineIntel" makes it seem like there's an issue with my CPU. Also, Windows told me that the problem was caused by my CPU when I told it to check for a solution. Does anyone have any ideas?

 

[caretaker]

Sorry to say but the easiest way to fix it is to rebuild. I had the same problem and tried for weeks to fix. Reinstall and all is well.

 

[Dzomlija]

If possible, check your BIOS settings for your hard disk controllers. and make sure that 32-Bit disk access is turned on for ALL devices, whether they are in use or not.

I had a similar problem several months ago (last year, infact) with my old motherboard. I resolved the problem by turning on 32-Bit disk access for all hard disk ports. : http://www.vistax64.com/vista-general/87842-stop-0x00000124.html#post433493

 

[pr0grammer1]

Sorry to say but the easiest way to fix it is to rebuild. I had the same problem and tried for weeks to fix. Reinstall and all is well.

I just did a complete format and reinstall a couple weeks ago. Does this mean I have to do that again?

If possible, check your BIOS settings for your hard disk controllers. and make sure that 32-Bit disk access is turned on for ALL devices, whether they are in use or not.

I had a similar problem several months ago (last year, infact) with my old motherboard. I resolved the problem by turning on 32-Bit disk access for all hard disk ports. : http://www.vistax64.com/vista-general/87842-stop-0x00000124.html#post433493

I checked and don't have that option. My motherboard was made by XFX and yours was made by Asus, so we probably have different options.

 

[Dzomlija]

Sorry to say but the easiest way to fix it is to rebuild. I had the same problem and tried for weeks to fix. Reinstall and all is well.

I just did a complete format and reinstall a couple weeks ago. Does this mean I have to do that again?

If possible, check your BIOS settings for your hard disk controllers. and make sure that 32-Bit disk access is turned on for ALL devices, whether they are in use or not.

I had a similar problem several months ago (last year, infact) with my old motherboard. I resolved the problem by turning on 32-Bit disk access for all hard disk ports. : http://www.vistax64.com/vista-general/87842-stop-0x00000124.html#post433493

I checked and don't have that option. My motherboard was made by XFX and yours was made by Asus, so we probably have different options.

True, your BIOS will different options than mine did, but that doesn't negate the fact that the may be one obscure setting that is causing this STOP 0x124 error on your machine. It took me several weeks, but after removing RAID setups, changing drivers and even going so far as considering replacing hard disks, I stumbled on the BIOS setting that fixed everything.

If you are using SATA hard disks, what mode are the controllers set to? IDE or RAID? (There's sometimes a third option, but I dont recall what that is right now). And more specifically, what mode was set on the SATA controllers when Vista was installed - sometimes Vista doesn't like the SATA controller mode to be changed after installation.

Perhaps if you check the XFX website for a non-BETA BIOS update?

Also, have you overclocked anything?

 

[pr0grammer1]

Sorry to say but the easiest way to fix it is to rebuild. I had the same problem and tried for weeks to fix. Reinstall and all is well.

I just did a complete format and reinstall a couple weeks ago. Does this mean I have to do that again?

If possible, check your BIOS settings for your hard disk controllers. and make sure that 32-Bit disk access is turned on for ALL devices, whether they are in use or not.

I had a similar problem several months ago (last year, infact) with my old motherboard. I resolved the problem by turning on 32-Bit disk access for all hard disk ports. : http://www.vistax64.com/vista-general/87842-stop-0x00000124.html#post433493

I checked and don't have that option. My motherboard was made by XFX and yours was made by Asus, so we probably have different options.

True, your BIOS will different options than mine did, but that doesn't negate the fact that the may be one obscure setting that is causing this STOP 0x124 error on your machine. It took me several weeks, but after removing RAID setups, changing drivers and even going so far as considering replacing hard disks, I stumbled on the BIOS setting that fixed everything.

If you are using SATA hard disks, what mode are the controllers set to? IDE or RAID? (There's sometimes a third option, but I dont recall what that is right now). And more specifically, what mode was set on the SATA controllers when Vista was installed - sometimes Vista doesn't like the SATA controller mode to be changed after installation.

Perhaps if you check the XFX website for a non-BETA BIOS update?

Also, have you overclocked anything?

I have two 500GB SATA drives, one for Vista and one for Ubuntu and backups. The controllers are set to IDE and haven't been changed since installation.

As far as I know, I have the latest BIOS (1/22/08).

I have previously overclocked my graphics card and CPU, but they are currently at the stock speeds.

Also, I've been getting a lot of errors with BCCode: 117 whenever I try to load the Crysis demo, which seem to indicate a graphics card problem (How much can go wrong? >.<)

 

[SCSIraidGURU]

What power supply do you have? What are the specs? Does anything share with your computer on the circuit? It could be a power issue.

I installed a 20A double pole breaker, split it to 2 x 20A@120V to a 20A double pole switch, each side has a 20A Tripp Lite 2400W line conditioner. One for my beast and one for monitor and other stuff. Even in low power conditions, the computer runs good.

PC Power and Cooling power supplies are designed to run in very low voltage conditions. It might be worth getting one.

 

[pr0grammer1]

What power supply do you have? What are the specs? Does anything share with your computer on the circuit? It could be a power issue.

I installed a 20A double pole breaker, split it to 2 x 20A@120V to a 20A double pole switch, each side has a 20A Tripp Lite 2400W line conditioner. One for my beast and one for monitor and other stuff. Even in low power conditions, the computer runs good.

PC Power and Cooling power supplies are designed to run in very low voltage
conditions. It might be worth getting one.

I've been running this computer on the same circuit for a long time, and it hasn't had any problems. My power supply is an OCZ 700W (Link), so it should be fine. In addition to my desktop, I have a monitor, laptop and router connected to this circuit, so it shouldn't be a power overload issue.

Also, this only happens when I get to the main menu of the Crysis demo. Everything else (including other games) works fine.

 

[SCSIraidGURU]

I would uninstall and reinstall the game with admin rights.

I would get a driver cleaner and remove and reinstall the video drivers.

 

[pr0grammer1]

I would uninstall and reinstall the game with admin rights.

I would get a driver cleaner and remove and reinstall the video drivers.

The game plays fine, it's just that whenever I pause on the menu for too long it crashes. If I quickly load a game it works fine.

My account is the only one on the computer, and it's an admin.

I'll try reinstalling the drivers though.

 

[PainlessTorture]

Look here at your error codes, http://www.vistax64.com/general-discussion/168364-awesome-download.html

Too many files opened for sharing is the problem...according to the error code

 

[pr0grammer1]

Look here at your error codes, http://www.vistax64.com/general-discussion/168364-awesome-download.html

Too many files opened for sharing is the problem...according to the error code

0x00000124 doesn't show up, and neither does 0x00000117 (The other one I'm getting).

Reinstalling the nVidia drivers didn't work. I'll check again for any BIOS updates.


Edit: I installed the latest BIOS and nothing changed.

 

[Element]

So I know this an older topic, however My pc after a normal sleep mode last night all the sudden developed this issue. BSOD 0124, I have tried everything the processor fix does not apply to my computer as it states when I try to install it. I have NO sound card installed, not even the onboard. I have 32bit enabled on my HD in bios, as well all other bios settings are default. NO OVERCLOCKING. I think this is purely a video card issue, cannot be 100% though. I have read lots and lots of articles online but nothing gives a clear answer. Does anyone know or remember a clear answer here?

 

[acdcfan]

So I know this an older topic, however My pc after a normal sleep mode last night all the sudden developed this issue. BSOD 0124, I have tried everything the processor fix does not apply to my computer as it states when I try to install it. I have NO sound card installed, not even the onboard. I have 32bit enabled on my HD in bios, as well all other bios settings are default. NO OVERCLOCKING. I think this is purely a video card issue, cannot be 100% though. I have read lots and lots of articles online but nothing gives a clear answer. Does anyone know or remember a clear answer here?

Attach .dupm file(s) here and I will analyse it for you.

 

[Element]

Can you tell me where to locate the file you need? Also I am on msn msgr @ [email protected]

*Also is there anyway to make sure I have uninstalled all the Nvida drivers off the machine, control panel shows none but we all know there could be residual files.*


Thanks

 

[Element]

Ok I think I got the files you are looking for I put them in a compressed folder on my webserver.

http://www.bortzmedia.com/dump.zip

 

[Element]

Interestingly enough I was able to get the system stable for a bit with only 1 stick of my RAM installed. So I decided to install the rest of my RAM and rebooted to only get this error just before the BSOD.

NMI: Parity Check / Memory Parity Error

The wierder thing is that I also got this error once today:

NMI: Channel Check / IOCHK

So I found this article and still am a little stumped, I think maybe now its the ram I dunno??

Hardware malfunction results in system error message

 

[Element]

Anyone?