New
#1
Soft BSOD only at restart
I use Windows 10 Pro, version 1909 Build 18363.657.
Attached V2 log collector zip file.
Let me start out by saying that my main question is not how to fix my BSOD issue.
My main question is, is it possible that there is a certain part of the RAM or CPU (cache, ALU, CU, etc) that would only be utilized at runtime, at a computer boot, and not utilized again after boot? (For this reason, I am not including my entire system specs unless someone wants them)
I'll now explain my issue and you'll understand why I ask.
My computer is on 24\7. I usually reboot once a week just to clear up stuff.
During the week, I have no issues. The computer works like a horse. It handles multitasking like a pro. I am a professional graphic designer, video editor and software engineer programmer. The computer works with photoshop flawlessly while rendering 4K video. No freezes, no stuttering, no problems at all.
It's only when I restart the computer, will I get the BSOD at boot. The culprit will always be some generic file such as ntoskrnl.exe with a generic reason such as "PAGE_FAULT_IN_NONPAGES_AREA" or some other file\code that is non-specific and does not give much info to work with to figure out what caused the crash.
Usually, after the BSOD, the computer will restart a second time by itself just fine.
Sometimes, the second reboot will also cause a BSOD and it will try to do the auto repair thing.
The auto repair will not succeed and it will give me the "advanced mode" button.
All I have to do is click on the advanced options but not choose any of them. I just choose "Continue to Windows" and it will then boot into Windows just fine and work great for another week... until I restart again.
My main dilemma was if it's a hardware issue, how does the computer work fine all week and the BSOD only happens at reboot. That's why it would make much sense if there was some part of the ram\cpu that is only utilized at boot. And even if there was, I can't understand why the computer boots fine on its own after going through 1-2 cycles of the BSOD. Also, if the solution is to simply skip something at boot (which is why "continue to windows" boots fine) then why can't Windows figure this out during the auto-repair attempt?
SOME FACTS:
- Being a programmer, I am very computer savvy, so before you attempt to offer a solution to the BSOD, just know that if your solution is mentioned anywhere on the first 30 pages of a Google search, It's most likely that I've tried that already.
- I have tested and benchmarked my ram, cpu, gpu and other hardware components. drivers are fine, no malware, no bloatware. No electric current issues. No software issues or clashing dll's (I write registry entries and dll files for a living.)
- I started my first computer course when I was 12 (in 1985) and have had computers for the past 35 years and not once have I come across an issue that I couldn't solve... this is the first time that I am stumped.
IN CONCLUSION:
I would like to know if it's possible that a BSOD that occurs only at boot, can indicate that the culprit is something that is only triggered at boot, and if so, what can that be?
Thank you!
Last edited by zvit; 03 Mar 2020 at 03:46.