BSOD Stop Error 0x124

[MindoverMaster]

BSOD stop error: 0x...124

Running Windows 7 Ultimate.

Yes, I looked online about this, and I found a lot of different things. Pointed towards some sort of hardware that had a fault. I had never seen a BSOD in 7 yet. This is a first for me.

(saw that it could be towards OCZ RAM, ATI GPUs, etc.)

Nothing happened 24 hours after this incident. It was right as rain.

My specs are in my sig.

Edit: And here is my dump file - http://nerd-ctrl.com/z-files/

 

[Slaymate]

That is a memory controller error.

Try raising the FSB Termination Voltage and the North Bridge Voltage a little, one at a time. If a little extra volts doesn't help by raising them one at a time, try raising both of them at the same time.

 

[MindoverMaster]

Why would it happen suddenly? I never had a problem before. I'd have to wait until next week though. I will be gone on vacation for a week.

In the mean time, Slay, can you brush me up on how much to raise them by? It's been awhile. Also, I haven't got another BSOD yet. How will I know when it is enough?

 

[KSoD]

Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR

 

[MindoverMaster]

It just happened again, playing StarCraft 2

I'm unsure what you meant, Sly. How would I know if raising the FSB cures it? It happens randomly.

 

[Slaymate]

It's been a long time since I had a LGA775 mobo and I'm not sure just what bios options you have. But a 0x00000124 is usually caused by the memory controller. On your mobo the controller is built into the chipset so it could need a fresh coat of thermal paste. If it's already good and cool then a little extra voltage might help stabilize the system. I don't know how memory intensive those games are but they maybe pushing your memory harder than it's ever been pushed.

Try running LinX for 20 passes with the "ALL" Memory button selected and see what happens. Run HWMonitor and keep your eyes on your temps. Stop the test if anything starts getting really hot.

And you don't raise the FSB, you raise the FSB Voltage, it maybe called FSB Voltage or FSB Termination Voltage or even something else. I'm just not sure what your options are.

 

[MindoverMaster]

Might try regreasing it. I never replaced it, manufacturer made. Would a fan on that help at all?

 

[KSoD]

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [G:\072210-11388-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0844a000 PsLoadedModuleList = 0xfffff800`08687e50
Debug session time: Thu Jul 22 22:51:49.309 2010 (GMT-4)
System Uptime: 0 days 3:03:14.150
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
......
*** WARNING: Unable to verify timestamp for hal.dll
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004c65028, b2000040, 800}

Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
Probably caused by : hardware

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

Looks like a hardware error like Slay is saying.

 

[MindoverMaster]

I played StarCraft after this, and I got no BSOD.

Included the current dump file below

Edit: I ran Linx twice now. First time I ran it, it got to 1:30 (m:s) and BSOD'd me again. Temps were ~70C. I'm running it now. temps are normal so far. 14:40 in.

 

[MindoverMaster]

'Tis a mystery. Sometimes I get that BSOD, sometimes I don't when running the exact apps. I'll up the voltage stuff later today when I have more time. Would lowering the OC of my CPU help?