Windows 10 - Critical System Failure

[jukash]

Hi,

I installed the current CoreTemp Version on my Windows 10 Pro 64 Bit machine and checked "start coretemp with windows".
everything worked untill I turned of my PC.
Wanted to boot today and I get a bluescreen "ciritcal servce failure" everytime.

Only way to be able to boot is choosing 7 (in the advanced startup options) deactivate driver signature.
I then deinstalled core temp and tried to restart. But bluescreen consists. I'm not able to boot windows 10 normally anymore.
what can I do?

There is the error code 0x0000005A in the logs

[The Coolest]

That is odd. This is the first time I see such an issue.
Try to boot up the system with deactivated driver signature enforcement, and see if you have ALSysIo loaded as a non-plug & play driver in Device Manager. If it is uninstall it.
Also check your services.

[jukash]

the problem is I can't open the device manager when I boot with disabled driver signature enforcement.

well if that error isn't the known failure I "hope" this is the fault of core temp. because thats the only thing I changed lately.
If it's not I have no idea where to look for a solution.

[The Coolest]

In that case I'd suggest you try from Safe mode.
I haven't checked in Win10, but earlier Windows versions have a feature where it will let you rollback your OS to an earlier date, maybe that can fix it.

[jukash]

safe mode also gives me the bluescreen.
unfortunately there are no "rescue points" that I can go back to.

[The Coolest]

Open the command prompt and type in

Code: Select all

driverquery /si

You should see the output of all signed drivers.

Code: Select all

DeviceName                     InfName       IsSigned Manufacturer
============================== ============= ======== =========================
ALSysIO                        N/A           FALSE    N/A
Generic volume                 volume.inf    TRUE     Microsoft
Generic volume                 volume.inf    TRUE     Microsoft
Generic volume shadow copy     volsnap.inf   TRUE     Microsoft

If you have ALSysIO in there that means that it was installed somehow, normally Core Temp loads the driver when you start it and unloads it when you exit the program.
If it's there, perform a search for ALSysIO64.sys or ALSysIO.sys if it's a 32bit OS. Delete all instances you find of the file, and try to reboot.
You should probably also try the following command as well just to be safe before deleting the *.sys files if they're found.

Code: Select all

wmic sysdriver where "name=ALSysIO" call delete

[jukash]

that file was only in the temp directory. deleted it there but with no success.

a bit clueless now.. unplugged all devices.. nothing
the only way to start is the option 7 in the advanced start menu.
safe mode etc all doesn't work.

is there a way to see which driver causes problems?

[jukash]

This are the error messages in the event display:

Code: Select all

Der Computer wurde nach einem schwerwiegenden Fehler neu gestartet. Der Fehlercode war: 0x0000005a (0x0000000000000001, 0xffffb38dc589f820, 0xffffa4091b7a68c0, 0xffffffffc0000428). Ein volles Abbild wurde gespeichert in: C:\WINDOWS\MEMORY.DMP. Berichts-ID: 17ed4980-b279-4398-b0f6-ac8df2da5249.

memory dump analyzed with "whocrashed"

Code: Select all

On Sat 11.03.2017 15:47:10 your computer crashed
crash dump file: C:\WINDOWS\Minidump\031117-9703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0) 
Bugcheck code: 0x5A (0x1, 0xFFFFB38DC589F820, 0xFFFFA4091B7A68C0, 0xFFFFFFFFC0000428)
Error: CRITICAL_SERVICE_FAILED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

[The Coolest]

Did you run the commands I suggested? Did it find the ALSysIO loaded?
One more thing you can try as a temporary fix so that you can boot up normally is to disable Secure Boot in the BIOS.
This may allow your system to boot normally and for you to have access to Device Manager and all the other services required to remove the driver.

[jukash]

yes I tried the steps with no success. secure boot cannot be disabled with my bios (msi x99a bios 4).
I think I'll have to reinstall windows - which I tried to avoid

[The Coolest]

I see. What did the commands show, though? Was ALSysIO loaded or not?

[jukash]

I was not loaded. So maybe it wasn't core temps fault at all.
after fresh install I'll make save points and backups and try it again and let you know if it happens again.

[The Coolest]

Alright, thanks.