Core Temp 1.7 BSOD - DRIVER_POWER_STATE_FAILURE

[mariojuniorjp]

Hi. I've been noticing several problems between the core temp and the AMD Radeon Settings (Crimson Relive 17.2.1 WHQL). In version 1.6 every time I start the program, the video signal disappears and then comes back. Already in version 1.7 the system goes into general panic and enters an eternal loop where the video signal comes and goes and in some cases the system restarts itself.

I noticed that this problem occurs only in the version with installer. I have not faced this problem in the zipped version. As I write this here, I just did the test in version 1.6. I will still test the 1.7 zipped version to see if it has the same problem as the installable version.

My setup:

[The Coolest]

That's interesting, but both the zipped and installer versions are identical.
The only thing it could be is with the extra things you get in the installer, such as the Core Temp Remote Server plugin and the extra languages.
I don't really see how any of that can cause the problem you're describing, but more testing is definitely needed.

[mariojuniorjp]

That's interesting, but both the zipped and installer versions are identical.
The only thing it could be is with the extra things you get in the installer, such as the Core Temp Remote Server plugin and the extra languages.
I don't really see how any of that can cause the problem you're describing, but more testing is definitely needed.

I uncheck all the options and install only the core temp. As I run out of video signal, I have no way to harvest the log.

I'll see what I can do to harvest the log.

[The Coolest]

In that case it shouldn't matter whether you're installing it or extracting from a zip file, the Core Temp.exe is the same exact file, simply packaged differently.

[Cauli]

In the last week I added an external drive enclose connected via USB 3 to my main pc. Today I accepted some windows update (for Win 10 64bit), rebooted, updated coretemp to 1.7.0.0 at its request & my machine promptly blue screened with a DRIVER_POWER_STATE_FAILURE (9f).

I rebooted & repeated the process noting the crash occurred during log on just after coretemp started up, so I restarted & logged into a different user account, uninstalled coretemp & restarted once again, this time logging back in as myself. No crash. I tried reinstalling & running coretemp after start up. No immediate crash but it did die in the same way within about ten minutes. So I removed it again & this time ran for a prolonged period without coretemp; no crash. I installed coretemp 1.6 & have been running all day with no further crashes.

Any idea what's going on?

My current system details: http://speccy.piriform.com/results/jBrV ... Abae4vxR4h

[The Coolest]

Sadly I don't 100% know what could have caused this to happen, but if it was due to Core Temp itself, I made a few adjustments to some of the new code to hopefully prevent this from happening again. Or at the very least reduce the chance of it. It will be available in the next release.

[Cauli]

Thanks. I've left CT set to report updates on start up so I will notice when the next one is out.

I use CCleaner, had it set to remove memory dumps & idiotically ran it without thinking after the problems yesterday. However as I wanted to eliminate my external drive enclosure as part of the cause (I wondered if it introduced excessive periods of non-responsiveness & as Win 10's usb 3 support is flaky) I ran some more tests with the drives disconnected. They weren't involved & CT 1.7.0.0 still killed my machine.

Incidentally I forgot to mention an intermittent symptom before the machine dies - the screen might go blank for a number of seconds, perhaps several times. Anyhow, I now have a memory.dmp. I installed WinDbg & here's its output: http://pastebin.com/u74Lr1Ad Is that of any use to you? Anything else I can do to help?

[The Coolest]

I didn't understand. Does your system still BSOD or is it the dump from before?

[Cauli]

I didn't understand. Does your system still BSOD or is it the dump from before?

Sorry if I wasn't clear. The dumps from the initial BSODs were accidentally deleted. I ran another test of CT 1.7 with my external drives disconnected & my system still BSOD. The dump, analysed in the pastebin I linked, is from this last BSOD.

[The Coolest]

I see, OK.
So you only get BSODs when the HDDs are disconnected.

[The Coolest]

Ok, took another look at the dump you posted. It's possible that a change I implemented in 1.7 somehow causes a conflict with Intel's driver (as that's the faulting module, iaStore), the next update should not have this problem, as it will not use this code anymore.

[Cauli]

I see, OK.
So you only get BSODs when the HDDs are disconnected.

Oh dear, sorry, no. I really must be making a bad job of this..

The BSODs occur regardless of whether the drives are connected or not. I only mentioned the drives in my first post as they were the only other recent change to my system.

Ok, took another look at the dump you posted. It's possible that a change I implemented in 1.7 somehow causes a conflict with Intel's driver (as that's the faulting module, iaStore), the next update should not have this problem, as it will not use this code anymore.

Thanks for the info. I look forward to checking out the update. I've had Coretemp on all my machines for years now. It would be a real shame if I was cut off from future versions due to an issue such as this. BTW Thanks for Coretemp

[wkramer]

I got the message that a new version of core temp (1.7) was available. As usual I installed the program. Almost immediately I got the DRIVER_POWER_STATE_FAILURE (BSOD). Windows restarted my PC and I got past login and startup programs started loading. Screen starts going off and on with a few seconds between going off and on. Perhaps a minute later the BSOD returns. After a number of try's rebooting I booted from a disk and removed Core Temp 1.7 and the PC booted properly. What's up?

[The Coolest]

It must be related somehow to a fix of another issue, you're not the first to report this issue.
It will be fixed in the next release. You can continue using 1.6 for now.

[The Coolest]

I sent you guys a PM, please take a look.

[wkramer]

I loaded the file you sent and it works without any BSOD problems. Thanks for a quick fix.

[The Coolest]

Great! Thank you very much for testing it out.

[Rodney]

I can confirm this issue on Intel Z97 plus a few other Intel chip sets. Pretty much sent me into a non recovery BSOD loop. Also confirm driver error with previous versions in UEFI secure boot mode. Maybe I'll try the 1.1...

[The Coolest]

Check your PM please.
Also 1.6 should still work fine.
Regarding the driver issue, only 1.0 RC9 will work right now. But I'm in the process of fixing that by obtaining a new digital signature certificate.

[Rodney]

RC9 works great for me on Intel Z97 UEFI secure boot thanks.

[Bal3Wolf]

Same problem on my x99 with a 6800k and a gtx 1080 anytime i load coretemp 1.7 video goes off i dont get a bsod usualy i can close coretemp befor that happens, I formated windows and it fixed till i had all the chipset drivers installed and it started doing it again.



testing the internal build seems to work fine no problems with it 1.6 also works but reads wattage wrong.

[Bal3Wolf]

I did notice something else when you open it the video driver goes off and comes back but then its fine no bsods or anything.

[mcrob83]

I am having the same problem - an internal build to test would be fine

[fjsorg]

In the last week I added an external drive enclose connected via USB 3 to my main pc. Today I accepted some windows update (for Win 10 64bit), rebooted, updated coretemp to 1.7.0.0 at its request & my machine promptly blue screened with a DRIVER_POWER_STATE_FAILURE (9f).

I rebooted & repeated the process noting the crash occurred during log on just after coretemp started up, so I restarted & logged into a different user account, uninstalled coretemp & restarted once again, this time logging back in as myself. No crash. I tried reinstalling & running coretemp after start up. No immediate crash but it did die in the same way within about ten minutes. So I removed it again & this time ran for a prolonged period without coretemp; no crash. I installed coretemp 1.6 & have been running all day with no further crashes.

Any idea what's going on?

My current system details: http://speccy.piriform.com/results/jBrV ... Abae4vxR4h

Hello,

Hotfixes
Installed
20/03/2017 Update for Windows 10 Version 1607 for x64-based Systems (KB3150513)

You have made the latest updates for W10 version 1607

The bug is there!

Core Temp 1.7 participates for very little

Install W10 1703

cordially

FJ