ALCPU Forums

There was a Windows update today. Afterwards, now starting CoreTemp causes Windows to crash.

Starting Core Temp today has caused Windows 10 to just go to black screen - this is a crash I have not seen before on this system. No bluescreen. No memory dump. Nothing - just a back screen (no video) and nothing apparently happening inside the computer- can not Remote Desktop into the system, for all intents and purposes the system seems to instantly just DIE when I started Core Temp v1.7 today. Never happened before, been running CoreTemp for YEARS.

I uninstalled / reinstalled CoreTemp. No change - starting CoreTemp causes a "black screen" crash.

Nothing at all in any of the Windows logs.

SYSTEM Windows 10 X64 ENTERPRISE w/ latest updates,
Intel i7 6800K, Gigabyte X99-Phoenix SLI. Bios F4, 16 GB DDR4 RAM, Nvidia GTX 970 graphics w/ 4 GB GDDR5, 512 GB Samsung 950 NVMe SSD


Any ideas?

Do you use UEFI on this PC?
If so, it is a known issue for Core Temp to fail/cause whole PC to fail.
You may need to go back to Core Temp 1.0 RC9 for now, it should work.

I sent the user an internal build to test and it fixed their issue.
So the next release should be ok.

The Coolest wrote:I sent the user an internal build to test and it fixed their issue.
So the next release should be ok.

Great, thanks for the quick update!
Please could you tell us what the issue was? Is it really with some kind of recent Windows Update Microsoft released - if so, which one?

I am not getting any issues on my Windows 10 PCs, despite using UEFI, but I want to know, as I could encounter same issue too!
(I am using much older PCs - 2 of them use Intel 1155 socket, and newest one uses 1150 socket, also quite old now.)

In 1.7 I added support for the HPET timer, and apparently on some systems the timer is not implemented as described in the specs. This made Core Temp access memory space allocated to something else, which would cause a BSOD or a system crash.
The fix simply makes it work correctly on those systems.

The Coolest wrote:In 1.7 I added support for the HPET timer, and apparently on some systems the timer is not implemented as described in the specs. This made Core Temp access memory space allocated to something else, which would cause a BSOD or a system crash.
The fix simply makes it work correctly on those systems.

Please can you PM me the same, then?
I am getting a system crash sometimes, might be Core Temp or GPU-Z, should be one of them.
I need to figure out which one and rule one out, please.

Hello

I have the same crasch still under W8.1

On Asus X99-Deluxe I have W7, W8.1 and W10

It is now Ok under W7 and W10

There is still the bug under W8.1. I have given 1.6 Core temp

Best regards

FJ

The Coolest wrote:In 1.7 I added support for the HPET timer, and apparently on some systems the timer is not implemented as described in the specs. This made Core Temp access memory space allocated to something else, which would cause a BSOD or a system crash.
The fix simply makes it work correctly on those systems.

Hello The Coolest,

Thank you very much. Everything is working

Post en PM

FJ

milosz wrote:There was a Windows update today. Afterwards, now starting CoreTemp causes Windows to crash.

Starting Core Temp today has caused Windows 10 to just go to black screen - this is a crash I have not seen before on this system. No bluescreen. No memory dump. Nothing - just a back screen (no video) and nothing apparently happening inside the computer- can not Remote Desktop into the system, for all intents and purposes the system seems to instantly just DIE when I started Core Temp v1.7 today. Never happened before, been running CoreTemp for YEARS.

I uninstalled / reinstalled CoreTemp. No change - starting CoreTemp causes a "black screen" crash.

Nothing at all in any of the Windows logs.

SYSTEM Windows 10 X64 ENTERPRISE w/ latest updates,
Intel i7 6800K, Gigabyte X99-Phoenix SLI. Bios F4, 16 GB DDR4 RAM, Nvidia GTX 970 graphics w/ 4 GB GDDR5, 512 GB Samsung 950 NVMe SSD


Any ideas?

Same problem here.

Hello,

You can specify the version of W10 ? 1511 ... 1607 ... 1703 ?

At the risk of deceiving me. I would say that the latest updates in W10 version 1607 have bugged your bike. That's what happened to me. (Asus X99-Deluxe / i7-5820K)
Only this machine was impacted. Under W8.1 and W10 ... W7 OK

No worries with a dozen other PCs (not even with CoreTemp)

Personally W10 Pro or Family in 1703

1 PC W10 Company LTSB 1607

Hello The Coolest,

Thank you very much. Everything is working

Post en PM

FJ

Thank you guys for trying it out