BSOD error 124 on OC build (i5 2500k 4.4Ghz)

Syther101 · 13 Mar 2012

A few days ago after discussing settings and other things with somebody with pretty much the same setup as mine I got my overclock settings to what I thought was stable.

The computer runs fine under load both playing games and when running a intel burn test for 20 loops.

I have recently found that the computer bluescreens when idle, I will just simply be watching a youtube video not even touching the mouse or keyboard and BAMM, audio freezes and I get bluescreen error 124. The past 2 bluescreens have been while on YouTube.

My settings can be seen here. I'm unsure what I need to do as it's fine after tests yet continues to bluescreen :/

Thanks so much if you can help me out as I'm trying to get coursework done and this is taking up more of that time than actual work XD

Build:

i5 2500k OC @ 4.4Ghz
Gigabyte z68xp-UD3p
Asus GTX 560Ti
8GB Corsair Venegence LP RAM @ 1600Mhz

Dump files and Health report are attached

My BIOS settings:

Frequency Settings
CPU CLOCK - 33X
BCLK - ( DISABLED ) left at default 100mhz
EXTREME MEMORY PROFILE XMP - ( PROFILE 1 )
SYSTEM MEMORY MULTI - ( AUTO )

Advanced CPU Settings
PWM Frequency Control: Auto
CPU Over Current Protection: Auto
Internal CPU PLL Overvoltage: Enabled
Real-Time Ratio Chnaged In OS: Disabled
Turbo Ration: 44 (All)
Turbo Power Limit: 300
Core Current Limit: 300
CPU Cores Enabled: All
CPU Enhanced Halt (C1E): Auto
C3/C6 State Support: Auto
CPU Thermal Monitor: Disabled
CPU EIST Function: Auto
Bi-Directional PROCHOT

Advanced Memory Settings
Extreme Memory Profile: Profile1
System Memory Multiplier: Auto
DRAM Timing Selectable: Auto
Channel Interleaving: Auto
Rank Interleaving: Auto
Performance Enhance: Standard

Advanced Voltage Settings
Multi-Steps Load-Line: 6
VCore: 1.305
Dynamic Vcore: Auto
QPI/Vtt Voltage: 1.175
System Agent Voltage: Auto
Graphics Core Voltage: Auto
Graphics Core: Auto
Graphics DVID: Auto
CPU PLL: 1.800
DRAM Voltage: 1.600

Misc Settings

ISOCHRONOUS SUPPORT [ ENABLED ]
VIRTUALIZATION TECH [ ENABLED ]

Power Management

HPET SUPPORT [ ENABLED ]
HPET MODE [ 64BIT ] - 64bit windows versions

Tews · 13 Mar 2012

Stop 0x124 is a hardware error.... you say that you have over clocked your I5 processor 4.4Ghz, which could very well be the reason for your problem. Try resetting your processor to standard settings and see if that helps ... if you continue to get BSOD here are some more things you may want to consider ..

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. Otherwise, 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.

Stop 0x124 - what it means and what to try

Syther101 · 01 Apr 2012

My problems are still persisting. Update on what I have tried so far. Also is anybody able to look at the dump files to see if there is any information you can gather from them?

-Updated audio/network drivers
-Updated and used older BIOS
-Completely removed and re-installed flash
-Wiped and re-installed Nividia drivers (Both old and new versions)
-Updated Intel HD graphics
-Tried a lower and higher VTT
-Disabled hardware acceleration
-Have tried stock settings for a day but the BSOD's can be random so might need to test this longer
-used all auto settings in BIOS
-2 Runs of memtest
-20 Runs of IBT passes fine with good temps and good VCore
-Never happened in game nor battlefield which I run in high for several hours

It would be much appreciated if somebody could help with this problem!

Thanks

Syther101

writhziden · 02 Apr 2012

Please upload the latest crash reports. It is difficult to look at the .dmp files without having them.

I trust that your old ones were already analyzed completely by Tews, but I will take a look for anything I notice anyway.

Security Software (just to check you have it and it is working; nothing needs to be done at this time):

Code:

ccsvchst.exe	c:\program files (x86)\norton internet security\engine\18.7.0.13\ccsvchst.exe	2044	8	1024	10240	13/03/2012 13:15	10.1.1.16	126.96 KB (130,008 bytes)	31/01/2012 11:36
ccsvchst.exe	c:\program files (x86)\norton internet security\engine\18.7.0.13\ccsvchst.exe	3040	8	1024	10240	13/03/2012 13:15	10.1.1.16	126.96 KB (130,008 bytes)	31/01/2012 11:36

Possible out of date drivers:

Code:

GVTDrv64	fffff880`0bc87000	fffff880`0bc91000	Tue Sep 05 01:10:02 2006 (44fd22ca)	00014d8a		GVTDrv64.sys
gdrv	fffff880`0bd2b000	fffff880`0bd34000	Thu Mar 12 21:22:29 2009 (49b9d175)	000105ce		gdrv.sys
SaiUA50A	fffff880`0bc20000	fffff880`0bc28700	Mon Jun 29 08:00:08 2009 (4a48c8e8)	0000aabc		SaiUA50A.sys
SaiKA50A	fffff880`0bc29000	fffff880`0bc51000	Mon Jun 29 08:00:15 2009 (4a48c8ef)	0002e81f		SaiKA50A.sys

Remove Gigabyte EasyTune6; it is known to have problems with Windows 7 and could be the cause of your 0x124 stop error.
Remove Gigabyte Easy Saver - mobo power utility; it is also known to cause problems with Windows 7.
Update your USB drivers for your Saitek Usb Drivers: Download Saitek Drivers and Software | Saitek.com If the drivers came with your motherboard, let us know, and we will try to help you find the appropriate driver updates. If they came with a PCI card, the link given should help with updating them.

Other than that, 0x124 is one of the more difficult crashes to debug because it is typically hardware related. Some supplementary hardware checking to do:

If you are overclocking any hardware, please stop.
Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
- Follow the steps for doing a CPU stress test using IntelBurnTest
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.