Login | Register

Core Temp 1.1 - 1.8.1 - Driver failed to load

Post about bugs you find in Core Temp so they can be addressed and fixed efficiently
  • Author
    Message

Core Temp 1.1 - 1.8.1 - Driver failed to load

Postby The Coolest » Sun Jul 03, 2016 8:10 pm

Update 4:
Core Temp version 1.9 has Microsoft's signature on the drivers now, so it should work fine on any Windows 10 machine.

Update 3:
After what seemed like an eternity and a lot of headaches and runabouts, I can finally say that my certificate is on its way.
So I hope that within 2-4 weeks I should have it and be able to sign drivers in a way that Win10 will find acceptable.

Update 2:
I placed an order for an EV code signing certificate. It will probably take a while for me to get it and to receive the hardware token by mail, though.
As soon as I get it, Core Temp will be updated with properly signed drivers and this issue will be resolved. Until then you can keep using version 1.0 RC9, as it's the latest one that will still work.
http://www.alcpu.com/CoreTemp/oldversions/CT10-rc9.zip

Update:
The problem with Windows Vista and Window 7 has been resolved, the problem users of the new Windows 10 still experience has to do with how Core Temp's drivers are digitally signed. Please refer to the following posts for more information.
viewtopic.php?f=62&t=5720&start=25#p14188
viewtopic.php?f=62&t=5720&start=25#p14198
viewtopic.php?f=62&t=5720&p=14282#p14214
This will be fixed in the future, but unfortunately I can't give an accurate time frame right now.

---------------------------------------------------------------------------------------------

In case you encounter this problem with the latest 1.1 version (or future versions) please read this post for some information on the problem.

The source of the problem is the new digital signature of the Core Temp driver. This version comes with an updated driver, which is signed with the new digital signature certificate.
This certificate can only sign using the SHA-2 algorithm, and can't co-sign using the deprecated SHA-1 algorithm that older operating systems support. Because of this, Windows can't interpret this signature and considers it invalid. Thus a 64bit OS will not allow the driver to load and start.
Windows 7 requires a patch to add support for SHA-2 based digital signatures. You must have SP1 installed for the patch to work on your OS. (Sadly at this time this version will not run on Windows Vista 64bit, and I'm looking for a solution)
This update is required for Core Temp 1.1 and all future versions to work (in case you encounter this problem), otherwise you can keep using 1.0 RC9.
http://www.alcpu.com/CoreTemp/oldversions/CT10-rc9.zip

Windows 7 SP1, KB3033929
Download link: https://www.microsoft.com/en-us/downloa ... x?id=46148
Information: https://support.microsoft.com/en-us/kb/3033929
Member of our O/C Folding @ Home team
"<The_Coolest> you can't unwaste wasted CPU cycles" - Start FOLDing now!
Main rig:
Core i7 2600K 3.4GHz @ 4.5GHz (Scythe Mugen2) / Mobo: Biostar TP67XE / SSD: Crucial M4 128GB (+ HDDs) / GPU: HD5450 / Mem: 4x4GB DDR3-1600 G.Skill 4GBXL RipJaws X - 16GB total / PSU: Seasonic S12II 620W.
Secondary rig:
Core i3 540 3.06GHz @ Stock / Mobo: MSI H55M-ED55 / GPU: Integrated / Mem: 2x2GB DDR3-1600 G.Skill 4GBRL RipJaws - 4GB total / PSU: FSP ATX350-PNR 350W.

Core Temp - Accurate temperature monitor for Intel's Core/Core 2 and AMD64 processors
User avatar
The Coolest
Site Admin
Site Admin
 
Posts: 2951
Joined: Tue Feb 18, 2003 7:48 pm
Location: Tel Aviv, Israel

Re: Core Temp 1.1 - Driver failed to load

Postby Jacob Klein » Mon Jul 04, 2016 10:35 pm

I'm getting this "Driver has failed to load." error, even on Windows 10 x64, latest Insider Build 14379.
Are you saying that Windows 10 is unsupported?

---------------------------
Core Temp: Error
---------------------------
Driver has failed to load.

This program will not continue.
---------------------------
OK
---------------------------
Jacob Klein
Registered User
Registered User
 
Posts: 27
Joined: Mon Jul 04, 2016 10:33 pm

Re: Core Temp 1.1 - Driver failed to load

Postby The Coolest » Tue Jul 05, 2016 1:47 am

It seems to be an odd problem with your machine. Core Temp works fine on Win10, but on your specific machine Windows can't validate the digital signature of the driver.
I'm not sure what the reason for this problem is yet, but with more information I can try to find out.
Please go to Event Viewer, Windows Logs, System. There should be a series of "Errors" with ALSysIO info in it.
Take a screenshot of this and post it here please.
Member of our O/C Folding @ Home team
"<The_Coolest> you can't unwaste wasted CPU cycles" - Start FOLDing now!
Main rig:
Core i7 2600K 3.4GHz @ 4.5GHz (Scythe Mugen2) / Mobo: Biostar TP67XE / SSD: Crucial M4 128GB (+ HDDs) / GPU: HD5450 / Mem: 4x4GB DDR3-1600 G.Skill 4GBXL RipJaws X - 16GB total / PSU: Seasonic S12II 620W.
Secondary rig:
Core i3 540 3.06GHz @ Stock / Mobo: MSI H55M-ED55 / GPU: Integrated / Mem: 2x2GB DDR3-1600 G.Skill 4GBRL RipJaws - 4GB total / PSU: FSP ATX350-PNR 350W.

Core Temp - Accurate temperature monitor for Intel's Core/Core 2 and AMD64 processors
User avatar
The Coolest
Site Admin
Site Admin
 
Posts: 2951
Joined: Tue Feb 18, 2003 7:48 pm
Location: Tel Aviv, Israel

Re: Core Temp 1.1 - Driver failed to load

Postby erice » Tue Jul 05, 2016 3:48 am

I'm also getting this "Driver has failed to load." error, Windows 10 x64, latest Insider Build 14379. it`s no upgrade of an former windows-installation (7, 8 or others).



Protokollname: System
Quelle: Service Control Manager
Datum: 04.07.2016 13:05:19
Ereignis-ID: 7045
Aufgabenkategorie:Keine
Ebene: Informationen
Schlüsselwörter:Klassisch
Benutzer: SZE-PC\erich
Computer: SZE-PC
Beschreibung:
Im System wurde ein Dienst installiert.

Dienstname: ALSysIO
Dienstdateiname: C:\Users\erich\AppData\Local\Temp\ALSysIO64.sys
Diensttyp: Kernelmodustreiber
Dienststarttyp: Manuell starten
Dienstkonto:
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="16384">7045</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2016-07-04T11:05:19.913977900Z" />
<EventRecordID>10510</EventRecordID>
<Correlation />
<Execution ProcessID="840" ThreadID="1032" />
<Channel>System</Channel>
<Computer>SZE-PC</Computer>
<Security UserID="S-1-5-21-639688551-3358222093-2610598826-1001" />
</System>
<EventData>
<Data Name="ServiceName">ALSysIO</Data>
<Data Name="ImagePath">C:\Users\erich\AppData\Local\Temp\ALSysIO64.sys</Data>
<Data Name="ServiceType">Kernelmodustreiber</Data>
<Data Name="StartType">Manuell starten</Data>
<Data Name="AccountName">
</Data>
</EventData>
</Event>




Protokollname: System
Quelle: Application Popup
Datum: 04.07.2016 13:05:19
Ereignis-ID: 26
Aufgabenkategorie:Keine
Ebene: Informationen
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: SZE-PC
Beschreibung:
Die Beschreibung für die Ereignis-ID "26" aus der Quelle "Application Popup" wurde nicht gefunden. Entweder ist die Komponente, die dieses Ereignis auslöst, nicht auf dem lokalen Computer installiert, oder die Installation ist beschädigt. Sie können die Komponente auf dem lokalen Computer installieren oder reparieren.

Falls das Ereignis auf einem anderen Computer aufgetreten ist, mussten die Anzeigeinformationen mit dem Ereignis gespeichert werden.

Die folgenden Informationen wurden mit dem Ereignis gespeichert:

\??\C:\Users\erich\AppData\Local\Temp\ALSysIO64.sys failed to load

Die Meldungressource ist vorhanden, aber die Meldung wurde nicht in der Zeichenfolge-/Meldungstabelle gefunden

Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Popup" Guid="{47bfa2b7-bd54-4fac-b70b-29021084ca8f}" EventSourceName="Application Popup" />
<EventID Qualifiers="16384">26</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-07-04T11:05:19.915980300Z" />
<EventRecordID>10511</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8972" />
<Channel>System</Channel>
<Computer>SZE-PC</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>\??\C:\Users\erich\AppData\Local\Temp\ALSysIO64.sys failed to load</Data>
<Binary>0000000002003000000000001A000040280400C06C0200C000000000000000000000000000000000</Binary>
</EventData>
</Event>




Protokollname: System
Quelle: Service Control Manager
Datum: 04.07.2016 13:05:19
Ereignis-ID: 7000
Aufgabenkategorie:Keine
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: SZE-PC
Beschreibung:
Der Dienst "ALSysIO" wurde aufgrund folgenden Fehlers nicht gestartet:
Die digitale Signatur dieser Datei kann nicht überprüft werden. Möglicherweise wurde durch eine kürzlich durchgeführte Hardware- oder Softwareänderung eine falsch signierte oder beschädigte Datei oder eine Datei, bei der es sich um böswillige Software aus einer unbekannten Quelle handelt, installiert.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2016-07-04T11:05:19.915980300Z" />
<EventRecordID>10512</EventRecordID>
<Correlation />
<Execution ProcessID="840" ThreadID="1032" />
<Channel>System</Channel>
<Computer>SZE-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">ALSysIO</Data>
<Data Name="param2">%%577</Data>
<Binary>41004C0053007900730049004F000000</Binary>
</EventData>
</Event>
erice
Registered User
Registered User
 
Posts: 5
Joined: Tue Jul 05, 2016 3:32 am

Re: Core Temp 1.1 - Driver failed to load

Postby Jacob Klein » Tue Jul 05, 2016 4:07 am

I agree. Something is odd about this particular "Windows 10 Insider Build 14379" PC, because I did more testing, and Core Temp v1.1 installs and runs just fine on my other 3 "Windows 10 Insider Build 14379" PCs.

For the PC with the problem, when I launch Core Temp v1.1, it immediately generates 48 events in Event Viewer. 16 sets of the following 3 messages, below.

I'll try to troubleshoot further, by uninstalling apps that may be interfering (like Visual Studio Community 2015? Intel Extreme Tuning Utility? CPUID?)
... but if you have any insight into the cause of this problem, I'd love to have it fixed.

Thanks,
Jacob

#1
Code: Select all
Log Name:      System
Source:        Service Control Manager
Date:          7/4/2016 11:28:10 PM
Event ID:      7045
Task Category: None
Level:         Information
Keywords:      Classic
User:          SPEED\Jacob
Computer:      Speed
Description:
A service was installed in the system.

Service Name:  ALSysIO
Service File Name:  C:\Users\Jacob\AppData\Local\Temp\ALSysIO64.sys
Service Type:  kernel mode driver
Service Start Type:  demand start
Service Account: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="16384">7045</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-05T03:28:10.354865000Z" />
    <EventRecordID>1554</EventRecordID>
    <Correlation />
    <Execution ProcessID="980" ThreadID="140" />
    <Channel>System</Channel>
    <Computer>Speed</Computer>
    <Security UserID="S-1-5-21-2690933982-4067065176-439439206-1001" />
  </System>
  <EventData>
    <Data Name="ServiceName">ALSysIO</Data>
    <Data Name="ImagePath">C:\Users\Jacob\AppData\Local\Temp\ALSysIO64.sys</Data>
    <Data Name="ServiceType">kernel mode driver</Data>
    <Data Name="StartType">demand start</Data>
    <Data Name="AccountName">
    </Data>
  </EventData>
</Event>


#2:
Code: Select all
Log Name:      System
Source:        Application Popup
Date:          7/4/2016 11:28:10 PM
Event ID:      26
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Speed
Description:
The description for Event ID 26 from source Application Popup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\??\C:\Users\Jacob\AppData\Local\Temp\ALSysIO64.sys failed to load

the message resource is present but the message is not found in the string/message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Popup" Guid="{47bfa2b7-bd54-4fac-b70b-29021084ca8f}" EventSourceName="Application Popup" />
    <EventID Qualifiers="16384">26</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-05T03:28:10.370490800Z" />
    <EventRecordID>1555</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="6896" />
    <Channel>System</Channel>
    <Computer>Speed</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Data>\??\C:\Users\Jacob\AppData\Local\Temp\ALSysIO64.sys failed to load</Data>
    <Binary>0000000002003000000000001A000040280400C06C0200C000000000000000000000000000000000</Binary>
  </EventData>
</Event>


#3
Code: Select all
Log Name:      System
Source:        Service Control Manager
Date:          7/4/2016 11:28:10 PM
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Speed
Description:
The ALSysIO service failed to start due to the following error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-05T03:28:10.370490800Z" />
    <EventRecordID>1556</EventRecordID>
    <Correlation />
    <Execution ProcessID="980" ThreadID="140" />
    <Channel>System</Channel>
    <Computer>Speed</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">ALSysIO</Data>
    <Data Name="param2">%%577</Data>
    <Binary>41004C0053007900730049004F000000</Binary>
  </EventData>
</Event>
Jacob Klein
Registered User
Registered User
 
Posts: 27
Joined: Mon Jul 04, 2016 10:33 pm

Re: Core Temp 1.1 - Driver failed to load

Postby The Coolest » Tue Jul 05, 2016 10:43 am

Sadly this is really out of my control. I have submitted a ticket with Comodo (the provider of my digital signature) to try and figure out what is wrong.
Member of our O/C Folding @ Home team
"<The_Coolest> you can't unwaste wasted CPU cycles" - Start FOLDing now!
Main rig:
Core i7 2600K 3.4GHz @ 4.5GHz (Scythe Mugen2) / Mobo: Biostar TP67XE / SSD: Crucial M4 128GB (+ HDDs) / GPU: HD5450 / Mem: 4x4GB DDR3-1600 G.Skill 4GBXL RipJaws X - 16GB total / PSU: Seasonic S12II 620W.
Secondary rig:
Core i3 540 3.06GHz @ Stock / Mobo: MSI H55M-ED55 / GPU: Integrated / Mem: 2x2GB DDR3-1600 G.Skill 4GBRL RipJaws - 4GB total / PSU: FSP ATX350-PNR 350W.

Core Temp - Accurate temperature monitor for Intel's Core/Core 2 and AMD64 processors
User avatar
The Coolest
Site Admin
Site Admin
 
Posts: 2951
Joined: Tue Feb 18, 2003 7:48 pm
Location: Tel Aviv, Israel

Re: Core Temp 1.1 - Driver failed to load

Postby Jacob Klein » Tue Jul 05, 2016 12:46 pm

I will try to troubleshoot this more in the upcoming few days/weeks, and if need be, may resort to a full reinstall of my partition. I vow to help you track this down.
Jacob Klein
Registered User
Registered User
 
Posts: 27
Joined: Mon Jul 04, 2016 10:33 pm

Re: Core Temp 1.1 - Driver failed to load

Postby The Coolest » Tue Jul 05, 2016 1:03 pm

Thank you.
I'm working with Comodo on fixing this. It's possible we've found a problem.
I'll keep updating this thread when there's any news.
Member of our O/C Folding @ Home team
"<The_Coolest> you can't unwaste wasted CPU cycles" - Start FOLDing now!
Main rig:
Core i7 2600K 3.4GHz @ 4.5GHz (Scythe Mugen2) / Mobo: Biostar TP67XE / SSD: Crucial M4 128GB (+ HDDs) / GPU: HD5450 / Mem: 4x4GB DDR3-1600 G.Skill 4GBXL RipJaws X - 16GB total / PSU: Seasonic S12II 620W.
Secondary rig:
Core i3 540 3.06GHz @ Stock / Mobo: MSI H55M-ED55 / GPU: Integrated / Mem: 2x2GB DDR3-1600 G.Skill 4GBRL RipJaws - 4GB total / PSU: FSP ATX350-PNR 350W.

Core Temp - Accurate temperature monitor for Intel's Core/Core 2 and AMD64 processors
User avatar
The Coolest
Site Admin
Site Admin
 
Posts: 2951
Joined: Tue Feb 18, 2003 7:48 pm
Location: Tel Aviv, Israel

Re: Core Temp 1.1 - Driver failed to load

Postby The Coolest » Tue Jul 05, 2016 3:02 pm

I sent both of you a PM, please take a look.
Member of our O/C Folding @ Home team
"<The_Coolest> you can't unwaste wasted CPU cycles" - Start FOLDing now!
Main rig:
Core i7 2600K 3.4GHz @ 4.5GHz (Scythe Mugen2) / Mobo: Biostar TP67XE / SSD: Crucial M4 128GB (+ HDDs) / GPU: HD5450 / Mem: 4x4GB DDR3-1600 G.Skill 4GBXL RipJaws X - 16GB total / PSU: Seasonic S12II 620W.
Secondary rig:
Core i3 540 3.06GHz @ Stock / Mobo: MSI H55M-ED55 / GPU: Integrated / Mem: 2x2GB DDR3-1600 G.Skill 4GBRL RipJaws - 4GB total / PSU: FSP ATX350-PNR 350W.

Core Temp - Accurate temperature monitor for Intel's Core/Core 2 and AMD64 processors
User avatar
The Coolest
Site Admin
Site Admin
 
Posts: 2951
Joined: Tue Feb 18, 2003 7:48 pm
Location: Tel Aviv, Israel

Re: Core Temp 1.1 - Driver failed to load

Postby erice » Tue Jul 05, 2016 5:56 pm

sorry, it`s all the same
greetings
Last edited by erice on Tue Jul 05, 2016 10:56 pm, edited 1 time in total.
erice
Registered User
Registered User
 
Posts: 5
Joined: Tue Jul 05, 2016 3:32 am

Re: Core Temp 1.1 - Driver failed to load

Postby The Coolest » Tue Jul 05, 2016 10:09 pm

Yep. Something between this new build and the signature I use are not playing ball.
I have Comodo looking into it. Everything *seems* to be good with my setup now.

Sadly it seems that the update I mentioned for Vista isn't working at all. Basically this version won't run on Vista 64 bit. I'm trying to get this problem sorted out as well.
Member of our O/C Folding @ Home team
"<The_Coolest> you can't unwaste wasted CPU cycles" - Start FOLDing now!
Main rig:
Core i7 2600K 3.4GHz @ 4.5GHz (Scythe Mugen2) / Mobo: Biostar TP67XE / SSD: Crucial M4 128GB (+ HDDs) / GPU: HD5450 / Mem: 4x4GB DDR3-1600 G.Skill 4GBXL RipJaws X - 16GB total / PSU: Seasonic S12II 620W.
Secondary rig:
Core i3 540 3.06GHz @ Stock / Mobo: MSI H55M-ED55 / GPU: Integrated / Mem: 2x2GB DDR3-1600 G.Skill 4GBRL RipJaws - 4GB total / PSU: FSP ATX350-PNR 350W.

Core Temp - Accurate temperature monitor for Intel's Core/Core 2 and AMD64 processors
User avatar
The Coolest
Site Admin
Site Admin
 
Posts: 2951
Joined: Tue Feb 18, 2003 7:48 pm
Location: Tel Aviv, Israel

Re: Core Temp 1.1 - Driver failed to load

Postby The Coolest » Thu Jul 07, 2016 2:02 am

So I just installed Insider build 14366 which is the latest one available for download as an ISO from Microsoft. On that OS Core Temp is actually working just fine.
Both the test versions I sent to you and the released 1.1.
Did you update to this build through MS or did you use some sort of method to construct the ISO to install it? I think it's possible that non-official builds could be broken in certain aspects.
Of course it's possible that MS changed something in 14379 which broke the way Windows interprets the digital signature I have.

Please do the following:
Start --> MMC --> File --> Add\Remove snap in.
Add Certificates for Local Computer. Click OK.
In the list go to Trusted Root Certificates Authorities --> Certificates, right click Certificates and Export list. This will create a text file.
Do the same for Third Party Root Certificates Authorities.
Please upload these files. I'd like to take a look, see if I can find anything that's wrong there.
Member of our O/C Folding @ Home team
"<The_Coolest> you can't unwaste wasted CPU cycles" - Start FOLDing now!
Main rig:
Core i7 2600K 3.4GHz @ 4.5GHz (Scythe Mugen2) / Mobo: Biostar TP67XE / SSD: Crucial M4 128GB (+ HDDs) / GPU: HD5450 / Mem: 4x4GB DDR3-1600 G.Skill 4GBXL RipJaws X - 16GB total / PSU: Seasonic S12II 620W.
Secondary rig:
Core i3 540 3.06GHz @ Stock / Mobo: MSI H55M-ED55 / GPU: Integrated / Mem: 2x2GB DDR3-1600 G.Skill 4GBRL RipJaws - 4GB total / PSU: FSP ATX350-PNR 350W.

Core Temp - Accurate temperature monitor for Intel's Core/Core 2 and AMD64 processors
User avatar
The Coolest
Site Admin
Site Admin
 
Posts: 2951
Joined: Tue Feb 18, 2003 7:48 pm
Location: Tel Aviv, Israel

Re: Core Temp 1.1 - Driver failed to load

Postby Jacob Klein » Thu Jul 07, 2016 4:37 am

First off ... I'm using Fast-Ring build 14379. Please be sure to update to that (Select Fast Ring, then takes 24-48 hours of runtime before Windows Update offers it), to test on our same version.

Secondly, in addition to the newest Core Temp not working (Event Viewer says:)
Code: Select all
The ALSysIO service failed to start due to the following error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

... I've also noticed that I can't get the new "Intel® Extreme Tuning Utility (Intel® XTU) v6.1.2.8", to operate correctly either. (Event Viewer says:)
Code: Select all
The iocbios2 service failed to start due to the following error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

... it will run, but doesn't allow me to see/edit any my CPU features/overclocks.
The old version, "Intel® Extreme Tuning Utility (Intel® XTU) v6.0.2.8.exe", installs and runs just fine with no problems.

I spent the better part of this evening, testing.
- Upgrading from Visual Studio 2015 Update 2, to Visual Studio 2015 Update 3... did not fix the problem.
- Uninstalling Visual Studio 2015... did not fix the problem.
- Uninstall other related components (SQL Server, components, Speech components)... did not fix the problem.
- Uninstall all Redistributables... did not fix the problem.
- Uninstall Oculus Rift software... did not fix the problem.

I've noticed that there are items in the Windows Feedback app, indicating that this might be a semi-widespread issue on the 14xxx Windows 10 Insider builds. People are complaining about updated CPU drivers that don't work/install/start, and updated audio drivers that don't work/install/start, all with the error "Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source."

My current hunch is that, perhaps on a UEFI BIOS (which my main rig has), recent Insider builds have problems with newer signed executables. As a reminder, Core Temp 1.1 installed just fine and works, on all of my 3 other non-UEFI PCs.

If I'm feeling up for it, I might consider a fresh reinstall of this Insider (my main) partition, this-coming weekend. But I'd LOVE for you to convince me not to :) Please? :)

I'll see about exporting my certificates, and sharing privately.
Jacob Klein
Registered User
Registered User
 
Posts: 27
Joined: Mon Jul 04, 2016 10:33 pm

Re: Core Temp 1.1 - Driver failed to load

Postby erice » Thu Jul 07, 2016 11:26 am

the same behavior with 1.5
certs in the attachement
thanks
Attachments
3rd.txt
(8.6 KiB) Downloaded 142 times
root.txt
(10.69 KiB) Downloaded 140 times
erice
Registered User
Registered User
 
Posts: 5
Joined: Tue Jul 05, 2016 3:32 am

Re: Core Temp 1.1 - Driver failed to load

Postby The Coolest » Thu Jul 07, 2016 7:33 pm

Thanks guys.
I've switched my install to the Fast ring, and I'll let it run for a bit. Hopefully it won't take long to update to the same build as you are on.
Member of our O/C Folding @ Home team
"<The_Coolest> you can't unwaste wasted CPU cycles" - Start FOLDing now!
Main rig:
Core i7 2600K 3.4GHz @ 4.5GHz (Scythe Mugen2) / Mobo: Biostar TP67XE / SSD: Crucial M4 128GB (+ HDDs) / GPU: HD5450 / Mem: 4x4GB DDR3-1600 G.Skill 4GBXL RipJaws X - 16GB total / PSU: Seasonic S12II 620W.
Secondary rig:
Core i3 540 3.06GHz @ Stock / Mobo: MSI H55M-ED55 / GPU: Integrated / Mem: 2x2GB DDR3-1600 G.Skill 4GBRL RipJaws - 4GB total / PSU: FSP ATX350-PNR 350W.

Core Temp - Accurate temperature monitor for Intel's Core/Core 2 and AMD64 processors
User avatar
The Coolest
Site Admin
Site Admin
 
Posts: 2951
Joined: Tue Feb 18, 2003 7:48 pm
Location: Tel Aviv, Israel

Re: Core Temp 1.1 - Driver failed to load

Postby erice » Thu Jul 07, 2016 8:07 pm

coretemp 1.1 is ok with the build of today 14383
greetings
eric
erice
Registered User
Registered User
 
Posts: 5
Joined: Tue Jul 05, 2016 3:32 am

Re: Core Temp 1.1 - Driver failed to load

Postby The Coolest » Thu Jul 07, 2016 8:26 pm

Great to hear. So perhaps this was just a fluke with that specific build from Microsoft.
Member of our O/C Folding @ Home team
"<The_Coolest> you can't unwaste wasted CPU cycles" - Start FOLDing now!
Main rig:
Core i7 2600K 3.4GHz @ 4.5GHz (Scythe Mugen2) / Mobo: Biostar TP67XE / SSD: Crucial M4 128GB (+ HDDs) / GPU: HD5450 / Mem: 4x4GB DDR3-1600 G.Skill 4GBXL RipJaws X - 16GB total / PSU: Seasonic S12II 620W.
Secondary rig:
Core i3 540 3.06GHz @ Stock / Mobo: MSI H55M-ED55 / GPU: Integrated / Mem: 2x2GB DDR3-1600 G.Skill 4GBRL RipJaws - 4GB total / PSU: FSP ATX350-PNR 350W.

Core Temp - Accurate temperature monitor for Intel's Core/Core 2 and AMD64 processors
User avatar
The Coolest
Site Admin
Site Admin
 
Posts: 2951
Joined: Tue Feb 18, 2003 7:48 pm
Location: Tel Aviv, Israel

Re: Core Temp 1.1 - Driver failed to load

Postby Jacob Klein » Thu Jul 07, 2016 9:10 pm

I confirm that, after installing Windows 10 Build 14383, both:
- Core Temp 1.1
- Intel® Extreme Tuning Utility (Intel® XTU) v6.1.2.8
... are working correctly.

Keep in mind, Core Temp 1.1 was working just fine on my 3 other PCs that were using the same build. So, I now suspect that the certificate store was updated/reset/fixed when the new build was installed, and that this still could be a problem if something messed it up in the first place, like Visual Studio.

I'll do a little more testing in the upcoming days, but I'm very relieved that I don't have to reinstall my partition :)
Jacob Klein
Registered User
Registered User
 
Posts: 27
Joined: Mon Jul 04, 2016 10:33 pm

Re: Core Temp 1.1 - Driver failed to load

Postby Jacob Klein » Thu Jul 07, 2016 9:29 pm

What the crap.... I had a notification that said "Finish installing device software", I clicked it, I restarted, and now the 2 programs don't work again.
:) Making progress to ironing this out! But I don't know what that notification did.
Jacob Klein
Registered User
Registered User
 
Posts: 27
Joined: Mon Jul 04, 2016 10:33 pm

Re: Core Temp 1.1 - Driver failed to load

Postby Jacob Klein » Sat Jul 09, 2016 4:30 pm

My plan is, whenever the next Insider build is released:
- Install the build
- Don't hit "Finish installing device software" right away
- Test whether I can get Core Temp 1.1, and Intel XTU 6.1.2.8, to install and function correctly
- Uninstall them
- Open Task Manager (to monitor what will happen when I click "Finish installing device software")
- Open Process Monitor (to monitor what will happen when I click "Finish installing device software")
- Start Process Monitor logging
- Click "Finish installing device software"
- Wait a couple seconds, while watching Task Manager for activity
- Stop Process Monitor logging
- Re-test whether I can get Core Temp 1.1, and Intel XTU 6.1.2.8, to install and function correctly

The goal is to determine what "Finish installing device software" actually does to my machine, and also determine if it's causing my problem.
Are we having fun yet? I'll report back when I know more.

PS: For some reason, I'm NOW getting an actual error during the installation of XTU 6.1.2.8. It still installs, and then fails to register the service, and then launches with most overclocking options missing. If I uninstall the new version, and install the old version, the old version works just fine.

The error is:
Program Compatibility Assistant
A digitally signed driver is required
Windows blocked the installation of a digitally unsigned driver. Uninstall the program or device that uses the driver and check the publisher's website for a digitally signed version of the driver.

1.png
1.png (8.67 KiB) Viewed 33001 times
Jacob Klein
Registered User
Registered User
 
Posts: 27
Joined: Mon Jul 04, 2016 10:33 pm

Re: Core Temp 1.1 - Driver failed to load

Postby Jacob Klein » Sun Jul 10, 2016 3:28 am

Hmm.. Well, my test results are basically: The same problem is happening on Build 14385 on this PC, and .. I was able to use the newer versions right after installing the Build, and after clicking "Finish installing device software"... but after the first restart, they didn't work. The certificate stores remained the same. I honestly don't know what's going on yet.

My next test will involve restarting, WITHOUT clicking the "Finish installing device software".

Sorry it feels like I'm grasping at straws. Doing the very best that I can. Once I run out of valid tests for the "build upgrade" scenario, then I will proceed to "fresh-install partition from ISO". Not looking forward to it lol!
Jacob Klein
Registered User
Registered User
 
Posts: 27
Joined: Mon Jul 04, 2016 10:33 pm

Re: Core Temp 1.1 - Driver failed to load

Postby The Coolest » Sun Jul 10, 2016 9:45 pm

I finally managed to get my test machine updated to the latest build - 14385. I have not seen any dialogs to "finish installing device software". And Core Temp works just fine.
I suspect that there could be some driver package which messes some things up with the driver signature enforcement (or the certificate store) on your machines.
Member of our O/C Folding @ Home team
"<The_Coolest> you can't unwaste wasted CPU cycles" - Start FOLDing now!
Main rig:
Core i7 2600K 3.4GHz @ 4.5GHz (Scythe Mugen2) / Mobo: Biostar TP67XE / SSD: Crucial M4 128GB (+ HDDs) / GPU: HD5450 / Mem: 4x4GB DDR3-1600 G.Skill 4GBXL RipJaws X - 16GB total / PSU: Seasonic S12II 620W.
Secondary rig:
Core i3 540 3.06GHz @ Stock / Mobo: MSI H55M-ED55 / GPU: Integrated / Mem: 2x2GB DDR3-1600 G.Skill 4GBRL RipJaws - 4GB total / PSU: FSP ATX350-PNR 350W.

Core Temp - Accurate temperature monitor for Intel's Core/Core 2 and AMD64 processors
User avatar
The Coolest
Site Admin
Site Admin
 
Posts: 2951
Joined: Tue Feb 18, 2003 7:48 pm
Location: Tel Aviv, Israel

Re: Core Temp 1.1 - Driver failed to load

Postby Jacob Klein » Mon Jul 11, 2016 4:46 am

Still trying to troubleshoot this problem (before throwing in the towel and rebuilding the partition... a task for next weekend perhaps).
Anyway, sfc did not return any problems. If you can think of anything else you want me to try, let me know.

Code: Select all
C:\WINDOWS\system32>sfc /VERIFYONLY

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.


Code: Select all
C:\WINDOWS\system32>sfc /SCANNOW

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
Jacob Klein
Registered User
Registered User
 
Posts: 27
Joined: Mon Jul 04, 2016 10:33 pm

Re: Core Temp 1.1 - Driver failed to load

Postby Jacob Klein » Wed Jul 13, 2016 12:46 am

I did another test with the new Windows 10 Build 14388, released today. I installed the build, was able to use Core Temp 1.1, restarted the PC, and then was unable to use it. So, I've concluded that the problem has nothing to do with the "Finish installing device software" notification. But I'm no closer to solving the problem.

I will consider reinstalling the partition this weekend.
Jacob Klein
Registered User
Registered User
 
Posts: 27
Joined: Mon Jul 04, 2016 10:33 pm

Driver failed to load

Postby Synergiance » Wed Jul 13, 2016 6:54 pm

As the title says, I'm getting a message saying the driver failed to load and core temp can't run, after updating to 1.1, my previous version works fine, so I have that running, not sure what changed with the driver in 1.1 that caused it to refuse to load but I'd like to help diagnose if I can
Synergiance
New User
 
Posts: 1
Joined: Wed Jul 13, 2016 6:48 pm

Next

Return to Bug reports

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 1 guest

cron