[SOLVED] Blue Screen of Death at bootup

Toggle sidebar Toggle sidebar
Solution
Colif
the difference between 1903 & 1909 is literally just a version number, when i updated from 3 to 9, all my pc did was restart. Perhaps you got that update between crashes.

Problem with 2004 "coming" is that its actually already here. It could complicate a fix if you continue to get that error as either a repair install or an extended DISM both need a copy of the ISO that is installed. The current ISO on Microsoft website is for 2004. Easy enough to fix that, just update to 2004. (if you want to update now, click the Update now button on here - https://www.microsoft.com/en-us/software-download/windows10 - and it will download the upgrade assistant. Run it on your PC and unless there are drivers that still need updating, it...
Sort by date Sort by votes
can you get past startup or stuck there?

I get a friend to convert files but it sounds like a windows problem

On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB (handy boot drive if nothing else)

anything on PC you want to save?
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose command prompt
type notepad and press enter
in notepad, select file>open
Use file explorer to copy any files you need to save to USB or hdd
 
Upvote 0 Downvote
Colif said:
can you get past startup or stuck there?

I get a friend to convert files but it sounds like a windows problem

On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB (handy boot drive if nothing else)

anything on PC you want to save?
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose command prompt
type notepad and press enter
in notepad, select file>open
Use file explorer to copy any files you need to save to USB or hdd
Click to expand...


It was stuck on the bios screen for a while after it restarted itself when it got to 100% , I'm currently at the desktop
Any ideas what caused this?

Thanks for the reply
 
Upvote 0 Downvote
i suspect that code has many different files that could be cause. As there are a few WIndows files, that if they crash, WIndows has no choice but to follow. I have sent dump toa friend who can convert it for me. See if it tells me anything useful.

lets check windows out -
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC
 
Upvote 0 Downvote
Hi, I ran the dump file through the debugger and got the following information: https://pastebin.com/tjVUR5eG

File information:070220-15390-01.dmp (Jul 2 2020 - 07:14:47)
Bugcheck:CRITICAL_SERVICE_FAILED (5A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 06 Sec(s)

BIOS info was not included in the dump files which can mean an outdated BIOS is being used.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Upvote 0 Downvote
It appears your Windows installation may be corrupt.

There's no documentation on the bugcheck, but from the parameters and the stack it's clear the filecrypt.sys driver is corrupt.
During system initialization the system drivers/services are loaded, but a dependency, filecrypt.sys, of one of these services can't be loaded.
Code: 
CRITICAL_SERVICE_FAILED (5a)
Arguments:
Arg1: 0000000000000001
Arg2: ffffba8f4e9f8c50
Arg3: ffffce06bf0caa90
Arg4: ffffffffc0000428

0: kd> !error ffffffffc0000428
Error code: (NTSTATUS) 0xc0000428 (3221226536) - 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.
0: kd> !dpx
Start memory scan  : 0xffffef0de8207828 ($csp)
End memory scan    : 0xffffef0de8208000 (Kernel Stack Base)

               rbx : 0xffffba8f4e9f8c50 :  !du "\FileSystem\FileCrypt"
                r8 : 0xffffba8f4e9f8c50 :  !du "\FileSystem\FileCrypt"
                r9 : 0xffffce06bf0caa90 :  !du "\SystemRoot\system32\drivers\filecrypt.sys"
               r14 : 0xffffce06bc0d7d00 :  !du "FileCrypt"
0xffffef0de8207840 : 0xffffba8f4e9f8c50 :  !du "\FileSystem\FileCrypt"
0xffffef0de8207848 : 0xffffce06bf0caa90 :  !du "\SystemRoot\system32\drivers\filecrypt.sys"
0xffffef0de8207890 : 0xffffce06bf0caa90 :  !du "\SystemRoot\system32\drivers\filecrypt.sys"
0xffffef0de82078a8 : 0xffffce06bc0d7d00 :  !du "FileCrypt"
0xffffef0de82078c0 : 0xffffba8f4e9f8c50 :  !du "\FileSystem\FileCrypt"
0xffffef0de82079a0 : 0xfffff800378267d0 :  !du "DependOnGroup"
0xffffef0de82079b8 : 0xfffff80037812ab4 : nt!PipCheckDependencies+0x30
0xffffef0de8207a08 : 0xfffff80037811f91 : nt!IopInitializeSystemDrivers+0x151
0xffffef0de8207a88 : 0xfffff80037397010 : nt!KiSystemStartup
0xffffef0de8207a98 : 0xfffff80037558a80 : nt!Phase1Initialization
0xffffef0de8207aa8 : 0xfffff80037811182 : nt!IoInitSystem+0x12
0xffffef0de8207ad8 : 0xfffff80037558ac2 : nt!Phase1Initialization+0x42
0xffffef0de8207af0 : 0xfffff80037558a80 : nt!Phase1Initialization
0xffffef0de8207b08 : 0xfffff80036f1e135 : nt!PspSystemThreadStartup+0x55
0xffffef0de8207b18 : 0xfffff80037558a80 : nt!Phase1Initialization
0xffffef0de8207b50 : 0xfffff80037391400 : nt!KiInitialThread
0xffffef0de8207b58 : 0xfffff80036fc99a8 : nt!KiStartSystemThread+0x28
0xffffef0de8207b70 : 0xfffff80036f1e0e0 : nt!PspSystemThreadStartup

Follow @Colif's advice on the SFC and Repair-WindowImage commands. Hopefully, those commands are sufficient.
 
Upvote 0 Downvote
I've did the SFC and it says no problems found and also for Repair windows image says healthy, so far no crashes and no blue screens.
Thanks for help , i'll report back if any issues
 
Upvote 0 Downvote
Filecrypt.sys is listed in the article below:

https://msdn.microsoft.com/en-us/library/windows/hardware/dn265170(v=vs.85).aspx

It belongs to FSFilter Encryption group, which the group includes filter drivers that encrypt and decrypt data during file I/O.

Reference here: https://msdn.microsoft.com/en-us/library/windows/hardware/ff549689(v=vs.85).aspx

filecrypt.sys is one of minifilter drivers, which used together with fliter manager:

https://msdn.microsoft.com/en-us/library/windows/hardware/ff541610(v=vs.85).aspx

There is no more detailed information that I could find out about the filecrypt.sys specially.
Click to expand...
https://social.technet.microsoft.co...filterquot-as-per-its?forum=win10itprogeneral

updating windows might help as you are on version 1903 and there are 2 new versions since then.
 
Upvote 0 Downvote
The dump file that was created on the 2nd says the following about your Windows version:
Code: 
Built by: 18362.1.amd64fre.19h1_release.190318-1202
BUILD_VERSION: 10.0.18362.900 (WinBuild.160101.0800)
BUILD: 18362
SERVICEPACK: 900
PLATFORM_TYPE: x64
NAME: Windows 10
EDITION: Windows 10 WinNt TerminalServer SingleUserTS
BUILD_TIMESTAMP: 2012-07-06 17:22:33
BUILDDATESTAMP: 160101.0800

1909 starts at: 10.0.18363
Source: https://docs.microsoft.com/en-us/windows/release-information/

Press Win+R and type in winver and press OK. What does it say?
 
Upvote 0 Downvote
gardenman said:
The dump file that was created on the 2nd says the following about your Windows version:
Code: 
Built by: 18362.1.amd64fre.19h1_release.190318-1202
BUILD_VERSION: 10.0.18362.900 (WinBuild.160101.0800)
BUILD: 18362
SERVICEPACK: 900
PLATFORM_TYPE: x64
NAME: Windows 10
EDITION: Windows 10 WinNt TerminalServer SingleUserTS
BUILD_TIMESTAMP: 2012-07-06 17:22:33
BUILDDATESTAMP: 160101.0800

1909 starts at: 10.0.18363
Source: https://docs.microsoft.com/en-us/windows/release-information/

Press Win+R and type in winver and press OK. What does it say?
Click to expand...


Microsoft Windows
Version 1909 (OS Build 18363.900)
 
Upvote 0 Downvote
the difference between 1903 & 1909 is literally just a version number, when i updated from 3 to 9, all my pc did was restart. Perhaps you got that update between crashes.

Problem with 2004 "coming" is that its actually already here. It could complicate a fix if you continue to get that error as either a repair install or an extended DISM both need a copy of the ISO that is installed. The current ISO on Microsoft website is for 2004. Easy enough to fix that, just update to 2004. (if you want to update now, click the Update now button on here - https://www.microsoft.com/en-us/software-download/windows10 - and it will download the upgrade assistant. Run it on your PC and unless there are drivers that still need updating, it should update you to 2004)
 
Upvote 0 Downvote
Solution
Colif said:
the difference between 1903 & 1909 is literally just a version number, when i updated from 3 to 9, all my pc did was restart. Perhaps you got that update between crashes.

Problem with 2004 "coming" is that its actually already here. It could complicate a fix if you continue to get that error as either a repair install or an extended DISM both need a copy of the ISO that is installed. The current ISO on Microsoft website is for 2004. Easy enough to fix that, just update to 2004. (if you want to update now, click the Update now button on here - https://www.microsoft.com/en-us/software-download/windows10 - and it will download the upgrade assistant. Run it on your PC and unless there are drivers that still need updating, it should update you to 2004)
Click to expand...

Hmm I think I got 1909 as soon as it came out as far as I remember I've had that for ages ~ haha
As for win ver 2004 I've heard it still has issues and a bit buggy, so I'll think I'll stick to 1909. Plus, on windows update it says my device is not ready and i'll be notified when I can update rather than manually downloading it for now. Nevertheless, thanks a lot Colif for the guidance and advice so far 😉 and other members.

Hopefully I won't see another bsod in a while after typing those commands you suggested
 
Upvote 0 Downvote
Lulu101 said:
As for win ver 2004 I've heard it still has issues and a bit buggy, so I'll think I'll stick to 1909.
Click to expand...
This is true for literally every version of Windows, there will always be bugs but most of them you won't even notice as you will never look into those areas of Windows. That means that your experience with a specific version of Windows may be entirely different from another user's experience, don't solely rely on what you heard when taking the next move.

About those commands bear in mind that they only worked for this very specific situation. In another situation, if any, they may not work because the commands rarely are a good solution for BSOD crashes.
 
Upvote 0 Downvote
The fear of a new update seems to get more articles every time. 2004 is no less of a problem than the last few versions, and so far I have only read about the problems caused by updates, I don't seem to get them myself. And I get them almost right away... impatient. Only time an update caused any problems was version 1507 (the original version of win 10) and that was cause I updated from 7 to 10.

Most BSOD aren't windows errors, the one you got is one of the few that are. There are a lot of codes I have never seen, and most of the ones I do seem to be caused by drivers/hardware.. not windows itself.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom