Windows Suddenly Won't Boot, CRITICAL_SERVICE_FAILED

After a few error messages (btTool.exe) my pc got a BSOD and rebooted. The pc was unable to boot and kept throwing a BSOD: CRITICAL SERVICE FAILURE. The only way I could boot Windows was by booting with the option "Disable driver signature enforcement".

I tried a lot of things: memory tests, sfc, bcdedit options, ... . Unfortunately without luck. 

I fixed this issue by doing a repair using a Windows 10 .iso and just doing an installation of Windows overriding the current version with keeping files and apps. This repair took two hours and the system is working and booting fine now.

Today I had some trouble printing, so I rebooted my PC. However, I was very surprised to find that Windows 10 wouldn't start. After clicking "Restart" it would take me to a blue screen, "CRITICAL SERVICE FAILED".

I've tried the automatic repair option, but it failed. Looking at the log file at C:WindowsSystem32LogfilesSrtSrtTrail.txt, it says that:

A recent driver installation or upgrade may be preventing the system from starting.

Repair action: System files integrity check and repair

Result: Failed. Error code 0x490

I've also tried booting into Safe Mode, but it would still yield a blue screen.

I've also tried some command line tools.

bootrec /fixmbr

bootrec /rebuildbcd

bootrec /fixboot

did not work.

sfc /scannow /offbootdirc: /offwindirc:windows

also didn't yield anything useful:

Windows Resource Protection did not find any integrity violations.

Chkdsk completed successfully, but did not change anything:

X:windowssystem32>chkdsk /f C:

The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another

process. Chkdsk may run if this volume is dismounted first.

ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.

Would you like to force a dismount on this volume? (Y/N)

y

Volume dismounted. All opened handles to this volume are now invalid.

Volume label is Windows.

Stage 1: Examining basic file system structure ...

1212672 file records processed.

File verification completed.

9383 large file records processed.

0 bad file records processed.

Stage 2: Examining file name linkage ...

1514736 index entries processed.

Index verification completed.

0 unindexed files scanned.

0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...

CHKDSK is compacting the security descriptor stream

Security descriptor verification completed.

151033 data files processed.

CHKDSK is verifying Usn Journal...

35484208 USN bytes processed.

Usn Journal verification completed.

Correcting errors in the master file table's (MFT) BITMAP attribute.

Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

No further action is required.

233434111 KB total disk space.

219701928 KB in 1055398 files.

552960 KB in 151036 indexes. 0 KB in bad sectors.

1324039 KB in use by the system.

65536 KB occupied by the log file.

11855184 KB available on disk. 4096 bytes in each allocation unit.

58358527 total allocation units on disk.

2963796 allocation units available on disk.

Failed to transfer logged messages to the event log with status 50.

I'm actually running out of ideas right now. I'm on the Anniversary Update.

·OTHER ANSWER:

Today I had some trouble printing, so I rebooted my PC. However, I was very surprised to find that Windows 10 wouldn't start. After clicking "Restart" it would take me to a blue screen, "CRITICAL SERVICE FAILED".

I've tried the automatic repair option, but it failed. Looking at the log file at C:WindowsSystem32LogfilesSrtSrtTrail.txt, it says that:

A recent driver installation or upgrade may be preventing the system from starting.

Repair action: System files integrity check and repair

Result: Failed. Error code 0x490

I've also tried booting into Safe Mode, but it would still yield a blue screen.

I've also tried some command line tools.

bootrec /fixmbr

bootrec /rebuildbcd

bootrec /fixboot

did not work.

sfc /scannow /offbootdirc: /offwindirc:windows

also didn't yield anything useful:

Windows Resource Protection did not find any integrity violations.

Chkdsk completed successfully, but did not change anything:

X:windowssystem32>chkdsk /f C:

The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another

process. Chkdsk may run if this volume is dismounted first.

ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.

Would you like to force a dismount on this volume? (Y/N)

y

Volume dismounted. All opened handles to this volume are now invalid.

Volume label is Windows.

Stage 1: Examining basic file system structure ...

1212672 file records processed.

File verification completed.

9383 large file records processed.

0 bad file records processed.

Stage 2: Examining file name linkage ...

1514736 index entries processed.

Index verification completed.

0 unindexed files scanned.

0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...

CHKDSK is compacting the security descriptor stream

Security descriptor verification completed.

151033 data files processed.

CHKDSK is verifying Usn Journal...

35484208 USN bytes processed.

Usn Journal verification completed.

Correcting errors in the master file table's (MFT) BITMAP attribute.

Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

No further action is required.

233434111 KB total disk space.

219701928 KB in 1055398 files.

552960 KB in 151036 indexes. 0 KB in bad sectors.

1324039 KB in use by the system.

65536 KB occupied by the log file.

11855184 KB available on disk. 4096 bytes in each allocation unit.

58358527 total allocation units on disk.

2963796 allocation units available on disk.

Failed to transfer logged messages to the event log with status 50.

I'm actually running out of ideas right now. I'm on the Anniversary Update.

Security Safe related articles
Is It True That Android Apps Are Less Secure These Days?
What Are Some Ways to Keep My Hair Really Healthy?
How Was the First Sale of Vivo X60 Series?
Huami Technology Held a Press Conference on August 27, and Amazfit Smart Sports Watch 3 Officially A
Connect to Nonencrypted Wireless Network Using Ubuntu Commands

Copyright © 2020 Coffee bag - Guangzhou tianci packaging industry Co,. Ltd. | Sitemap