Turbo Boost Causing BSOD

[Mr7axi]

Hi, so whenever i try to enable turbo boost, my pc will get a BSOD even before successfully boosting into Windows,

On Fri 6/16/2017 2:53:50 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\061617-6062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0xE3 (0xFFFF8F895BC7F900, 0xFFFF8F895E896080, 0xFFFF8F895C265120, 0x2)
Error: RESOURCE_NOT_OWNED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread tried to release a resource it did not own.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 3/17/2017 2:28:00 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)
Bugcheck code: 0x124 (0x0, 0xFFFFA0010E954028, 0xBE200000, 0xB110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: 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).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

These are the latest dumps, honestly the problem has started quite a long time ago, more than 6months ago. All this time, i managed to get my com stable just by disabling intel turbo boost in the bios, the com is on 24/7 and heavily used without a single crash when turbo boost is disabled.

So my main concern is, is it possible for a faulty CPU to only with turbo boost enabled, while working perfectly when it is disabled?

OS:Windows 10 64bit (Latest Creators Update)
MB: Asus Rampage 4 Extreme
CPU:i7-4930K
RAM:4x8GB G.Skrill Ripjaws
PSU:Cooler Master V750 Gold

BIOS Setting is Default with X.M.P with rams @ 2133mhz
and disabled fan control for cpu cause water cooling.

 

[Vitric9]

I could read those Windows reports for hours and still know nothing more. Try troubleshoot your System Memory. If your using XMP, set that to Auto for the default frequency and timings on the memory. Should be 1333 MHz. 2 sticks, instead of 4. maybe even alternating 1 stick. I imagine you have the latest BIOS by now, if not you may need update to the current BIOS version.

THe more likely reason is something windows is misidentifying when loading drivers and whatnot. Specifically the BCLK can be very slightly different clocks when choosing XMP or Auto or Manual.
Let me finish this up with a link to a thread which may or may not be helpful
Here is the post with the answer about ¾ down the page. https://answers.microsoft.com/en-us/windows/forum/all/my-computer-keeps-crashing-with-bugcheck-code/509b456a-c598-4a29-90fd-13ac817b810f

 

[Mr7axi]

Thanks for the reply, after further research and digging through the web, I found this post on rogforums and the guy was pretty confident that most 0x124 BSOD is caused by lack of voltage to the CPU. I bumped up my VCORE voltage and its stable now. I am unsure if its due to old age of the chip or any reason, but apparently it now requires a slightly higher voltage than stock to be stable.

 

[Vitric9]

Thanks for the reply, after further research and digging through the web, I found this post on rogforums and the guy was pretty confident that most 0x124 BSOD is caused by lack of voltage to the CPU. I bumped up my VCORE voltage and its stable now. I am unsure if its due to old age of the chip or any reason, but apparently it now requires a slightly higher voltage than stock to be stable.

Good to know. I thought maybe that, but turned to the more obvious.... I thought perhaps if anything like the i7 and Asus board i use, then the slight change in BCLK would have set off some alarms over at Microsoft Headquarters. Windows reports 3922 MHz and not the 3900 MHz that it originally detected. a Chain reaction sets in and it is Y2K Bug in action. Before we know it our toasters are trying to kill us.