New Windows 10 Insider Preview Fast+Skip Build 18917 (20H1) - June 12 Insider

f14tomcat said:

There is an anomaly here, I think. This is from a VM of the latest Fast Ring last Wed., 6/12. Clearly shows 1903, and 18917. What all that means, I have no idea. I think JGToy was saying he gets a BSOD right up front very early on in the bootup process, not Green. I agree that Green is the color of choice now for Insider, has been for a long time. But....I'm wondering if the crash is so early on, the full OS never has a chance to get going to set the Green vs. Blue. He stated it was a Power Driver failure. That would indicate somewhere very close to the POST routines and the hand-off to the OS. Just thinking out loud....

Attachment 237569

Hi TC,
Your analogy is pretty good.
The BSOD isn't at boot time, it happens on waking up the computer and freezes everything even the blue screen itself.
I left it alone for half hour and collection of data never change from 0%, the only way I could get in was turn the computer off / back on again.

this is not from a VM but standard desktop install of the current build ---with 1903 in front of the build identifier. Go figure that.

magilla said:

this is not from a VM but standard desktop install of the current build ---with 1903 in front of the build identifier. Go figure that.

Yes, it's consistent, whatever the reason. I only did a VM cause it was easy to do without booting out of where I was. But, seems to be all over.

JGToy said:

Hi TC,
Your analogy is pretty good.
The BSOD isn't at boot time, it happens on waking up the computer and freezes everything even the blue screen itself.
I left it alone for half hour and collection of data never change from 0%, the only way I could get in was turn the computer off / back on again.

JG, just thinking out loud again. The sleep states supported by the machine are set in the BIOS, S1-S2-S3, etc. Could still be due to the full OS not quite awake yet, and still running in the PE environment, which may only know Blue and nothing about Green. I'm not getting all the terms correct, I know, but that's a possibility.

If you have the time, and inclination, it would be interesting to see if you would get a Green GSOD under normal circumstances in this build. There is a way to make a couple of temp reg changes to test and force a Screen of Death (color omitted intentionally )

It can be easily undone. Just a test.

How to force a Windows 'Blue Screen of Death' — and why you might want to | Windows Central

f14tomcat said:

JG, just thinking out loud again. The sleep states supported by the machine are set in the BIOS, S1-S2-S3, etc. Could still be due to the full OS not quite awake yet, and still running in the PE environment, which may only know Blue and nothing about Green. I'm not getting all the terms correct, I know, but that's a possibility.

If you have the time, and inclination, it would be interesting to see if you would get a Green GSOD under normal circumstances in this build. There is a way to make a couple of temp reg changes to test and force a Screen of Death (color omitted intentionally )

It can be easily undone. Just a test.

How to force a Windows 'Blue Screen of Death' — and why you might want to | Windows Central

Tomorrow I will have more spare time and I will go throughout yours indications and I'll let you know.
I really appreciate your time and observations!

Windows 10 SDK Preview Build 18917 available now - June 18

Blue screen, green screen, we all scream when we see these screens.*

* Perhaps some of you never heard the saying from my childhood "You scream, I scream, we all scream for ice cream"