1.15.1 Driver has failed to load

[SalCal]

I built my PC in Feburary, and Core Temp was working fine up until this morning where Core Temp gives me "Driver has failed to load. This program will not continue" on PC startup.
I didn't install any new drivers or make any major changes to anything the night prior.
I've tried restarting the program, reinstalling it, and deleting the config file.

Some specs:
- Windows 10 64-bit Home
- Intel i7-9700k
- NVidia RTX 2060 SUPER
- 16 GB RAM

These two logs show up four times each in the event viewer when Core Temp tries to open:

Code: Select all

- System 

  - Provider 

   [ Name]  Service Control Manager 
   [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4} 
   [ EventSourceName]  Service Control Manager 
 
  - EventID 7045 

   [ Qualifiers]  16384 
 
   Version 0 
 
   Level 4 
 
   Task 0 
 
   Opcode 0 
 
   Keywords 0x8080000000000000 
 
  - TimeCreated 

   [ SystemTime]  2020-04-28T12:54:01.231504000Z 
 
   EventRecordID 10816 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  784 
   [ ThreadID]  16940 
 
   Channel System 
 
   Computer DESKTOP-CBRUGLN 
 
  - Security 

   [ UserID]  S-1-5-21-2264290667-3730228874-220544048-1002 
 

- EventData 

  ServiceName ALSysIO 
  ImagePath C:\Users\Bug\AppData\Local\Temp\ALSysIO64.sys 
  ServiceType kernel mode driver 
  StartType demand start 
  AccountName

Code: Select all

- System 

  - Provider 

   [ Name]  Service Control Manager 
   [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4} 
   [ EventSourceName]  Service Control Manager 
 
  - EventID 7000 

   [ Qualifiers]  49152 
 
   Version 0 
 
   Level 2 
 
   Task 0 
 
   Opcode 0 
 
   Keywords 0x8080000000000000 
 
  - TimeCreated 

   [ SystemTime]  2020-04-28T12:54:01.241477600Z 
 
   EventRecordID 10817 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  784 
   [ ThreadID]  16940 
 
   Channel System 
 
   Computer DESKTOP-CBRUGLN 
 
   Security 
 

- EventData 

  param1 ALSysIO 
  param2 %%647 
   41004C0053007900730049004F000000 


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

Binary data:


In Words

0000: 004C0041 00790053 00490073 0000004F 


In Bytes

0000: 41 00 4C 00 53 00 79 00   A.L.S.y.
0008: 73 00 49 00 4F 00 00 00   s.I.O...

[The Coolest]

Does the Windows user you are using have administrator privileges?
If it does, then it could be some sort of anti-virus and the sort preventing the driver from starting correctly.

[SalCal]

I have only one user on this PC, and it has admin rights.
I also only use Windows Defender, which has always been on since I've started using this PC.

[Noctix]

I'm also having the same issue. Everything worked fine yesterday however this morning upon starting up my PC I got the "Driver failed to load" error.
I'm also using Windows 10 64-bit Home.

[The Coolest]

Can you try to see if there are any errors relating to the alsysio driver in event viewer? It's possible a Windows update broke something.

[SalCal]

Not finding any entries unique to the two that I mentioned.
I'm at least relieved to know that I'm not the only one experiencing this.

[Noctix]

I've found a few errors on my end. Here's all the information it is giving me. Not sure if this was the information you were looking for.
Source: Service Control Manager
Event ID: 7000
"The ALSysIO service failed to start due to the following error:
The driver was not loaded because it failed its initialization call."

[xbitionart]

Hello all !
I am Julie, and i am french and i have a same bug....

Since I reformatted ...
Core Temp no longer opens, I have a message:
The pilot failed to load. Core Temp will stop.
If someone has an idea I take, three short hours that I look for why because I need it with my skin "Rainmeter".
Thank you & good evening everyone
Ps: I am at version 1.15.1 & I have the same bug with old versions and news version 1.6// Installation & uninstallation already tested
----
I looked in the event viewer on windows & we will say that I have a problem with an ALSysIO64.sys file

---

Code: Select all

<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="2020-04-29T01:06:34.526862000Z" /> 
  <EventRecordID>2456</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="888" ThreadID="4580" /> 
  <Channel>System</Channel> 
  <Computer>DESKTOP-UF9NQHM</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data Name="param1">ALSysIO</Data> 
  <Data Name="param2">%%647</Data> 
  <Binary>41004C0053007900730049004F000000</Binary> 
  </EventData>
  </Event>

If you have a solution, I take it and thank you.
I've been looking for more than 3 hours!

Bye.

Julie (xbitionart)

[The Coolest]

Can it be related to this?
viewtopic.php?f=62&t=6479&p=16264#p16264

[SalCal]

I do believe that is the case! I started playing Valorant very recently. I haven't seen that error message myself, so there was probably no way I would have known.

[Naki]

I do believe that is the case! I started playing Valorant very recently. I haven't seen that error message myself, so there was probably no way I would have known.

Can you disable the damn thing, and see if that helps?
Here is how:
Riot now let you disable Valorant’s controversial kernel-level anti-cheat tool (when you’re not playing)
https://www.thesixthaxis.com/2020/04/28 ... at-driver/

Please tell us how it goes.

[SalCal]

Core Temp was able to run when I uninstalled Riot Vanguard, and then stopped working as soon as I reinstalled Riot Vanguard. So I think it's safe to say that is the cause.

[brodyc1]

Can it be related to this?
viewtopic.php?f=62&t=6479&p=16264#p16264

I had the same issue for a little while, however I've never gotten that message with the Valorant Anti-cheat. I'd say a week ago, I started to get the driver cant load message though. Checking my Event Viewer, It all pointed to the fact that the driver was just not loading for any reason. I've been poking around trying to see if anyone else was having the same issue and I ran into some old threads here saying there were issues with the driver signature not getting along well with Windows 10 updates. That might seem to be the case again. As a test, I disabled Driver Signature Enforcement on bootup, and it works now! CoreTemp started up and is currently working fine. Now obviously this isn't something anyone would want to keep running due to security reasons, but it's help shine some light to what is possibly happening. This could still be an issue with the Valorant Anti-Cheat system somehow since I also have this installed, but just wanted to give you an update.

My current Windows build is Build 18362.19h1_release.190318-1202. If you'd like me to attach any event viewer logs or anything like that, just let me know.

[brodyc1]

Okay, scratch my last post. Did some more poking around and it turns out disabling Driver Signature Enforcement actually stops Valorant's Anti-Cheat from running. Turned it back on but disabled the anti-cheat manually, and it was still working.