Same BlueScreen Code 124 issue after flashing 5820k
Same BlueScreen Code 124 issue after flashing 5820k
Hi all,
I'm a beginner overclocker. My 5820k has been boosted to 4.2Ghz for a few months now. However, occasionally, every day or sometimes even once a day, my PC crashes with a BSOD 124.
Note: The BSOD only occurs within the first 30 minutes after turning on the PC for the first time that day, and only when it's idle or doing light web browsing (no streaming or YouTube, etc.). It never happens once the PC has been running for that period and there are no other errors or codes. It runs smoothly during those initial 30 minutes—whether I'm gaming, editing videos, or doing rendering, there are no interruptions.
After the crash, I restart the BIOS and reload my OC profile (the BSOD seems to reset everything back to defaults), then reboot. Once I do this, it boots normally and doesn't crash again that day.
PC Specifications:
- i7 5820K (OC'd to 4.2Ghz)
- MSI X99A Gaming 7
- MSI GeForce GTX 980 Gaming 4G
- Corsair Dominator Platinum 16GB DDR4
- Corsair H100i GTX Liquid CPU Cooler
- Windows 7 Professional
OC Information:
- 42 x multi
- CPU Ratio = Dynamic
- EIST + Intel Turbo Boost + Enhanced Turbo = ALL enabled
- Ring Ratio/Frequency = Auto/3000Mhz
- CPU BLK = 100
- DRAM Frequency = Auto (2133Mhz)
- CPU Core Voltage Mode = Override (Fixed)
- CPU Core Voltage: 1.170
Everything else is set to Auto.
Intel C-State = Disabled
Last 4 DMP files:
==================================================
Dump File : 042816-8455-01.dmp
Crash Time : 28/04/2016 5:13:26 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`0ef858d8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042816-8455-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 409,504
Dump File Time : 28/04/2016 5:14:35 PM
==================================================
==================================================
Dump File : 042416-7846-01.dmp
Crash Time : 24/04/2016 11:33:08 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`0ef868d8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042416-7846-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 409,448
Dump File Time : 24/04/2016 11:34:32 AM
==================================================
==================================================
Dump File : 042216-5179-01.dmp
Crash Time : 22/04/2016 12:54:56 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`0ef57038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041916-7815-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 409,360
Dump File Time : 22/04/2016 12:55:35 PM
==================================================
I've performed numerous stress tests using RealBench, XTU, and AiDa64—all passed without problems.
I've also run many MemTest instances, none reported errors.
Opening the command prompt and executing the system file checker confirmed everything is clean and error-free.
From what I've seen elsewhere, it seems more likely a hardware or driver issue rather than a voltage problem (some posts suggested otherwise).
It's not a major obstacle for using the PC, but I'd appreciate any help to fix it.
Cheers,
Deekay
From stock, adjust Vcore offset to 1.25v, enable Turbo at 43x all cores, and 40x ring bus. Increase Vring/Uncore & Vin to 0.5v from stock. Turn off C3/C6, keep EIST active. If your RING has separate voltage and clock, match them to Vcore. This setup offers a solid starting point. Consider trying 44x or a lower voltage next. Refer to "Overclocking Haswell" guides.
Over the past few months I've experimented with various OC settings... I reached a stable 4.4 on 1.25 and it remained consistent during all stress tests. However, I aimed for around 4.2. I've also tested lowering the voltage to 4.1 and 4.0, with identical outcomes. Since these changes only occurred in the first 30 minutes and under idle or low CPU conditions, my conclusion is that it's likely the system isn't receiving enough power when under heavy load—such as during demanding games or high-resolution YouTube videos from Sony Vegas.
Are you always maintaining a fixed voltage level? As you pointed out, I'm concerned the voltage might be too low during idle. If you're using a constant voltage, consider disabling speedstep and C-states. Instead, try a static CPU ratio with speedstep turned off. Regarding your cache, it's currently running at the stock 3000 Mhz. Have you thought about increasing it slightly to match your core speed? It's uncertain if this change would help, but the difference between your output voltage and the stock cache frequency could be contributing to the problem. At standard CPU speed, the maximum difference between your voltage and the stock cache is around 600 Mhz. I tested my cache at stock speed during a CPU core speed test, but it didn't last long—possibly a week or two before I raised it.
I've experimented with various combinations; step by step and C-state off (current), the outcomes remain unchanged. I haven't adjusted the ring or cache speed, and I was initially uncertain about trying it next since I'm not sure how to proceed. I think if I go above 3000Mhz, I might need to change the cache voltage setting, but I have no idea what to use or what is safe to test.
I removed some unused drivers and a webcam that I never used, which caused software problems during installation. It hasn't crashed on the first boot in the last two mornings, though I'm hoping it was just those drivers.
I'll let you know soon to see if the issue recurs tomorrow. Thanks for your feedback so far!
I've experimented with various combinations; step by step and C-state off (current), the outcomes remain unchanged. I haven't adjusted the ring or cache speed and was considering that next, but I'm not sure how to approach it since changing the cache voltage setting is uncertain and I have no guidance on what to set.
I removed some unused drivers and a webcam that I never used, which caused software problems during installation. It hasn't crashed on the first boot in the last two mornings, though I'm hoping it was just those drivers.
I'll keep you updated soon, hoping for more stable days. Thanks for your feedback so far.
Hopefully the software problems are the cause. To be precise, I've been operating at 1.25v for my cache at 4Ghz.
Well after three days without any problems, it crashed again today after running for about 15 to 20 minutes (at idle).
🙁
DMP file:
==================================================
Dump File : 050216-7410-01.dmp
Crash Time : 2/05/2016 5:24:03 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`0ef4f8d8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70380
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\050216-7410-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 294,648
Dump File Time : 2/05/2016 5:25:10 PM
==================================================
I’ll attempt adjusting the ring/cache ratio and voltage to see if it resolves the issue... damn, I thought I had it figured out!
Auto and fixed are kind of sht.
Run the Ring at 4.0, use offset for voltage, it's clear your voltage is dropping too much at idle.