Solved BSOD - Shutting Down/Starting Up/Sleeping/Waking

[Nadger]

I shut down my computer last night, or i slept it, i don't remember which because i walked away. I came home from work, turned on my computer and stepped away, upon coming back i noticed it said windows recovered from a BSOD.

This is the first time I've encountered this error.

The only thing ive changed recently is I installed the Intel HD 4000 driver and the Lucid Virtu MVP Drivers.

Please help me track this down. I just built the computer a few weeks ago, so its a fresh OEM Install of Windows 7 Pro 64bit

Specs are as follows:

i7 3770k Ivy Bridge Cpu
ASUS Z77 Sabertooth Motherboard
Geforce GTX 680 (Zotac)
16gb Corsair Vengeance LP 1600 RAM
Corsair Force3 GT 60gb SSD (SSD Cache)
Western Digital 1TB Caviar Black HDD (Raided With SSD to Cache)
Corsair H100 Closed Loop Watercooler
Noctua NF F12 FocusFlow Fans on H100
ASUS Xonar DX 7.1 Soundcard
Corsair AX 750 Gold PSU w/ White cables
Corsair 600T SE White Case
LG Lightscribe Bluray Multi Drive
26" Doublesight 263n S-IPS Monitor
Noppoo Choc Mini Mech Keyboard
Razer Naga & Deathadder Mice

Yes there is irrelevant info in there but its easier to C&P it from another forum were I posted pictures of the computer i built ;p

 

[JMH]

The analysis indicates a Stop 0x124 which is a hardware error

If you are overclocking try resetting your processor to standard settings and see if that helps.

If you continue to get BSODS, here are some things you may want to consider.

This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

Stop 0x124 - what it means and what to try
Synopsis:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


Generic "Stop 0x124" Troubleshooting Strategy:

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.


2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.


3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.


4) Update the motherboard BIOS according to the manufacturer's instructions.
Their website should provide detailed instructions as to the brand and model-specific procedure.


5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing.
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent harware troubleshooting steps may, in some cases, void your warranty:

8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[Nadger]

Yes there are 2 dumps in there that were from OC testing but the latest was caused by igpu drivers. Ive updated the drivers, hopefully that will make it go away.

 

[JMH]

Let us know how you go please.

 

[Nadger]

Reformatted again, updated drivers, still having exact same issue.

igdkmd64.sys igdkmd64.sys+1b8902 fffff880`11098000 fffff880`11ea7080 0x00e0f080 0x4f4c9675 2/28/2012 2:55:17 AM


I may end up just disabling the onboard graphics and using only dedicated gpu. Seems to happen in the sleep/wake power cycle.

 

[JMH]

124 Error for desktops not under warranty.
If you are at all uncomfortable don't do it.


This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).


Remove ALL power and re-seat all cards, memory and cables (on both ends) - actually remove and replace - do not just snug.

Make sure the system has adequate ventilation - add a small fan blowing into intakes.

Carefully inspect the motherboard and other cards for damage. Pay attention to the fatal hardware error implication.You may need a real computer shop (not leeks and peeks at a BestBuy or other BigBox stores) or the System maker's Support.

Check the processor seating, heat sink, and the compound between the processor and
the heat sink which are common causes.

There have been a few instances where Norton/Symantec and other antivirus/security
programs have caused this error.

BCCode: 124 0x00000124

The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug
check indicates that a fatal hardware error has occurred. This bug check uses the error
data that is provided by the Windows Hardware Error Architecture (WHEA).

0x00000124 <-- read this link
The system encountered an uncorrectable hardware error.

 

[Nadger]

Yeah as i said the first 2 BSODs are just from testing OC levels. I had it overclocked to 4.6ghz on those dumps, so i was expecting BSODs....It was the 3rd dump thats been on repeat. I forgot to remove those other 2 dumps.

Anyway, I went into UEFI bios and disabled Render Standby option of the IGPU and so far the BSODs on sleep/wake/power cycles seem to be gone. If I don't update again assume that fixed it.

 

[JMH]

If indeed "fixed" please mark your thread as solved.
Good luck!