Repeated BlueScreen Code 124 on OC'd 5820k

deekay510 · Apr 28, 2016

Hi everyone,

Novice overclocker here. I have had my 5820k OC'd to 4.2Ghz for a couple of months now, but a couple of days a week, up to sometimes once a day every day or 2, my PC crashes with BSOD 124.

Note: If it BSOD's, it ONLY happens within the first 30mins of the PC being turned on for the first time on that particular day and when it's at Idle or light web-browsing (no streaming or youtube, etc).

It NEVER happens once the PC has been on over that time period stated and no other issues or error codes, it runs like a dream ongoing , if it doesn't crash in those first 30 minutes (e.g. long gaming sessions, video editing and rendering, etc - no issues at all and never crashes).

After the BSOD, i go into the BIOS and reload my OC profile (BSOD seems to reset everything to default) and reboot, again after doing this it's boots up fine and never crashes again that day.

PC Spec Info:

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 Info:

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 on 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\042216-5179-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
==================================================

==================================================
Dump File : 041916-7815-01.dmp
Crash Time : 19/04/2016 12:02:48 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`0ef538d8
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,416
Dump File Time : 19/04/2016 12:05:07 PM
==================================================

I have ran countless stress tests with RealBench, XTU and AiDa64 - all passed without issue.
I have ran countless (and multiple simultaneous) runs of MemTest - no errors.
I have opened cmd prompt and ran the system file checker - verification complete with no issues/errors.

From what i have read in other posts on here, it's more likely to be a hardware or driver issue, rather than a voltage issue (as some posts stated)...any help would be greatly appreciated!

Its' not a massive issue in terms of being able to use the PC, but would like to resolve it anyway ofcourse.

Cheers,
Deekay

1LiquidPC · Apr 29, 2016

Have you tried a lower OC or higher voltage to be sure. You mentioned this has been going on since you've been OC'd. Even with all the stresstests, it might be worth a shot.

deekay510 · Apr 29, 2016

Yep over the last couple months i've tried a range of OC's...i got it up to 4.4 on 1.25 and again stable through all stresstests, however I only wanted to settle around 4.2.
I've tried going down to 4.1 and 4.0, results replicate the same. I've tried uping the voltage incrementally up to 1.25 with same results. Given it's only happening in the first 30 minutes and whilst at idle or very low CPU load, my best guess is that it isn't that it's not getting enough juice at load; when i play demanding games or better yet rendering 1080p youtube videos from Sony Vegas which puts the system under heavy load, it's never failed once.

1LiquidPC · Apr 29, 2016

Is your voltage always at a static setting? Like you mentioned, I'm wondering if the voltage is to low when idle. If your are running a constant voltage, maybe try disabling speedstep and C-states. Try a static CPU ratio w/ speedstep disabled instead of dynamic perhaps. Also, I see your cache speed is at stock 3000 Mhz. Have you tried increasing this a bit to be closer to your core speed? I can't say for sure if this should have any affect, but given the "gap" between your OC and this stock cache frequency, perhaps it's causing an issue. At stock CPU speed, there's only at most a 600 Mhz difference between the two. I did however run my cache at stock when testing my CPU core speed OC, but it wasn't for a long length of time, maybe a week or two before adjusting it higher.

deekay510 · Apr 30, 2016

Yep i've tried a number of different combinations; step step & C-state off (current), still the same results. I haven't touched the ring/cache speed and i was actually thinking of trying that next was just unsure how to about it as i know if i adjust that ratio above 3000Mhz i'm pretty sure i'd need to change the cache voltage setting and have no idea what to use (or what is safe to test).

I've removed a few drivers that weren't in use and a webcam that i never used that did cause software issues when I installed it...it hasn't crashed on first boot for the last 2 mornings now, i'm praying it might just of been that webcam/drivers.

I'll report back soon, see if it happens tomorrow.

Thanks for your input so far though

deekay510 · Apr 30, 2016

Yep i've tried a number of different combinations; step step & C-state off (current), still the same results. I haven't touched the ring/cache speed and i was actually thinking of trying that next, was just unsure how to about it as i know if i adjust that ratio above 3000Mhz i'm pretty sure i'd need to change the corresponding cache voltage setting and I have no idea what to set there (or what is safe to test).

I've removed a few drivers that weren't in use and a webcam that i never used that did cause software issues when I installed it...it hasn't crashed on first boot for the last 2 mornings now, i'm praying it might just of been that webcam/drivers.

I'll report back soon, fingers crossed i more days without crashing.

Thanks for your input so far though

1LiquidPC · Apr 30, 2016

OK. Hopefully its the software issues you mentioned. With that said, I've been using 1.25v for my cache at 4Ghz.

deekay510 · May 2, 2016

well after 3 days without issue it crashed again today after being up for about 15-20mins (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 try uping the ring/cache ratio and voltage and see if that helps...damn i thought i had it sorted!

William Henrickson · May 2, 2016

Auto and fixed are kind of sht.

Run the Ring at 4.0, use offset for voltage, its obvious "to me" your voltage is drooping too low at idle.

deekay510 · May 2, 2016

Nothing is obvious to me, being a novice overclocker as noted in the OP - I was under the impression that setting a 'fixed' voltage meant the voltage would be a constant 1.17, regardless of at idle or load.

In the MSI BIOS under the "Core/Ring Voltage mode" there are multiple options:
- Auto
- Adaptive
- Override (Fixed)
- Offset
- Adaptive + Offset
- Override + Offset

If i select offset mode, it then requires me to complete the following items:
- Core Voltage mode ( + or - )
- Core Voltage ( the core voltage value )
- Ring Voltage mode ( + or - )
- Ring Voltage (the ring voltage value )

I have not been able to find a useful simple guide to setting offset core/ring values - compounded by the fact that MSI seem to use different terminology to other Mobo manufacturers...hence I have been reluctant to try anything using offset, until I can find some better reference material to follow.

Thanks for your help though.

William Henrickson · May 2, 2016

From stock, set Vcore offset to 1.25v, Turbo on at 43x all cores, 40x ring bus. Raise Vring/Uncore & Vin .5v from stock. Disable C3/C6, leave EIST on. Perhaps your RING has a seperate voltage and clock, set it the same as vcore.

This should be a good base to start from. Try 44x or a lower voltage as the next step. Use "Overclocking Haswell" guides.

Search

Repeated BlueScreen Code 124 on OC'd 5820k

deekay510

Commendable

William Henrickson

1LiquidPC

Splendid

deekay510

Commendable

1LiquidPC

Splendid

deekay510

Commendable

deekay510

Commendable

1LiquidPC

Splendid

deekay510

Commendable

William Henrickson

Reputable

deekay510

Commendable

William Henrickson

Reputable

TRENDING THREADS

Latest posts

Moderators online

Share this page