Hi!
Every time I try to boot the system I'll get this BSOD at the end of the 3rd stage of loading the NT kernel (according to this illustration from the Microsoft Docs), so when I see the Windows logo and see the progress ring. At this time observing the HDD LED it seems like if the OS would periodically retry to access a file for a few times before giving up.
I've read the posting instructions, but currently I can only boot into WinRE and WinPE, and these say that I can't run the collector on them, so not sure how to provide the needed information. Until that problem gets solved, I did my research which I'll show for you, but I got into a dead end, and I need the help of professionals to continue.
Here are some important information about my config:
OS: Windows 10 Pro 1903 64 bit (18362.719, more on that later)
No memory dumps found, but maybe I just haven't searched in the right place.
Not sure what else to include, hardware does not seam to be important. If you need anything else please ask for it. Don't be afraid to use technical terms, I'm not the user who scares about them :)
The stop code is PROCESS1 INITIALIZATION FAILED, for which Microsoft has a basic documentation here.
The first param is 0xFFFFFFFFC0000279
The second param is 0x2 (trimmed the leading zeros)
The third and fourth params are full zeros.
The documentation says that the first param is an NT status code, and that the other 3 are preserved.
Starting from that, if I don't consider the first 8 F's, then it's the code for STATUS_IO_REPARSE_TAG_NOT_HANDLED. hresult.info translates that to ERROR_CANT_ACCESS_FILE
And if I look at the comments at the documentation of said BSOD, it turns out that we may know the meaning of the second parameter. Geoff Chappell wrote a study about the parameters of this BSOD for 32 bit systems. It says that if the second parameter is 2, then the problem is with loading system DLL's.
He concluded that at the writing of the study the second parameter being 2 could only mean a problem with ntdll.dll, but it may not be accurate because it's about 32 bit systems, and it's fairly old
Looking at ntdll.dll it looks to be correct. It has a correct size, it's signature is valid (so if I understand correctly, it can't be corrupted), and it's version number matches the version of the system. It does not seem to be a link, but maybe it was only an extension of my main OS to show if the file is a symbolic/other link, which has difficulties now.
If you need more information on the context I will provide it, but for now I don't want to overcomplicate it if the problem can be solved without that. In short I have a Windows Update problem at the same time (pending update from 18362.719 to 720), but it might be solved if the OS gets to the point to integrate the .720 package(s).
Could you help in solving this problem? I have never seen this BSOD before, and it's a miracle that I found that link of that study, I usually don't even remember MS Docs have a comment section. I don't think I'll find any more information on that by myself, but I don't want to give up this system, it would take a lot of time to set everything up from scratch as it was in this system, more so because there are a lot of settings which I found and set in a time when I didn't do bookmarking properly, or at all
Every time I try to boot the system I'll get this BSOD at the end of the 3rd stage of loading the NT kernel (according to this illustration from the Microsoft Docs), so when I see the Windows logo and see the progress ring. At this time observing the HDD LED it seems like if the OS would periodically retry to access a file for a few times before giving up.
I've read the posting instructions, but currently I can only boot into WinRE and WinPE, and these say that I can't run the collector on them, so not sure how to provide the needed information. Until that problem gets solved, I did my research which I'll show for you, but I got into a dead end, and I need the help of professionals to continue.
Here are some important information about my config:
OS: Windows 10 Pro 1903 64 bit (18362.719, more on that later)
No memory dumps found, but maybe I just haven't searched in the right place.
windir\minidumps\ is empty for sure.Not sure what else to include, hardware does not seam to be important. If you need anything else please ask for it. Don't be afraid to use technical terms, I'm not the user who scares about them :)
The stop code is PROCESS1 INITIALIZATION FAILED, for which Microsoft has a basic documentation here.
The first param is 0xFFFFFFFFC0000279
The second param is 0x2 (trimmed the leading zeros)
The third and fourth params are full zeros.
The documentation says that the first param is an NT status code, and that the other 3 are preserved.
Starting from that, if I don't consider the first 8 F's, then it's the code for STATUS_IO_REPARSE_TAG_NOT_HANDLED. hresult.info translates that to ERROR_CANT_ACCESS_FILE
And if I look at the comments at the documentation of said BSOD, it turns out that we may know the meaning of the second parameter. Geoff Chappell wrote a study about the parameters of this BSOD for 32 bit systems. It says that if the second parameter is 2, then the problem is with loading system DLL's.
He concluded that at the writing of the study the second parameter being 2 could only mean a problem with ntdll.dll, but it may not be accurate because it's about 32 bit systems, and it's fairly old
Looking at ntdll.dll it looks to be correct. It has a correct size, it's signature is valid (so if I understand correctly, it can't be corrupted), and it's version number matches the version of the system. It does not seem to be a link, but maybe it was only an extension of my main OS to show if the file is a symbolic/other link, which has difficulties now.
If you need more information on the context I will provide it, but for now I don't want to overcomplicate it if the problem can be solved without that. In short I have a Windows Update problem at the same time (pending update from 18362.719 to 720), but it might be solved if the OS gets to the point to integrate the .720 package(s).
Could you help in solving this problem? I have never seen this BSOD before, and it's a miracle that I found that link of that study, I usually don't even remember MS Docs have a comment section. I don't think I'll find any more information on that by myself, but I don't want to give up this system, it would take a lot of time to set everything up from scratch as it was in this system, more so because there are a lot of settings which I found and set in a time when I didn't do bookmarking properly, or at all
