I have some problems with my new build and Windows right now.. For some reason Mutex gets sometimes (About 1 of 10 reboots) locked and I can't use CPU-Z, Core Temp, HWMonitor or anything that monitors CPU speed and temperature. On Cinebench I get much less points than normally. (409 vs 725)
[bInitDriver] path = C:\Users\User\AppData\Local\Temp\
[bInitDriver] GetCurrentDirectory = C:\Program Files\CPUID\CPU-Z
[bInitDriver] GetModuleFileName = C:\Program Files\CPUID\CPU-Z\cpuz.exe
[vGetOSVersion] m_iOSVersion = 2 (10.0)
[vGetOSVersion] m_bIsAMD64 = 0
[bInitDriver] m_hDriverMutex = 1EC
[bDeleteFile 13:49:32] DeleteFile returned = 0 (error = 5)
[bDeleteFile 13:49:32] RemoveDirectory C:\Users\User\AppData\Local\Temp\\cpuz139\ returned = 0 (error = 145)
[bInitDriver] m_szFilename = cpuz139_x64.sys
[bInitDriver] bInitDriver returned 258
[vCloseDriver 13:49:34] WaitForSingleObject error = 258
[vCloseDriver] CloseHandle(mutex) = 1
And when I reboot, it takes about 15 minutes and then I get a BSOD that says DRIVER_POWER_STATE_FAILURE.
My CPU is i5 6600K and system is overclocked to 4.5GHz @ 1.300V. Usually this system runs fine for a week straight, but sometimes this stuff happens.
However, on my Arch Linux installation I haven't had any problems even with a 4.7GHz at 1.325V overclock and I can compile Android from source code no problem. (Compiling 20-30 gigabytes of source code for about 60-70 minutes.)
So what could the problem be? This SEEMS to be a problem in Windows only. Bad drivers? Bad BIOS settings? Bad overclock?