S
ScotGiambalvo
My primary PC just suffered from the dreaded Windows 10 Spring 1803 Update, BSOD Driver PNP WATCHDOG crash, and now refused to boot.
Following are the steps I have attempted to resolve this issue using command prompt only (I have been unsuccessful so far)
I have booted from W10 Repair Disc, and OEM 1709 and 1803 Install Discs with the following results:
System Restore - No points unavailable
Startup Repair - Unable to resolve problem
Go back to a previous version - Failed
System Image Recovery - (Don't have one, won't make that mistake again.)
I have successfully enabled "Legacy Boot" and can see the F8 options, but none seem to have any effect.
Disable Early Launch Anti-Malware Driver > result > Endless spinning dots
Disable Driver Signature Enforcement >result > Endless spinning dots
Debugging Mode >result > Endless spinning dots
Safe Mode / Safe Mode with Command Prompt >result > Endless spinning dots
When I boot with the Repair Disc, the only option that works properly, is "Command Prompt".
Using the Command Prompt, I have successfully executed the following commands, though I'm not sure they "stuck" as implied.
bcdedit /set {default} bootmenupolicy legacy (How I got the F8 to work again)
bcdedit /set {default} safeboot minimal (which doesn't seem to stick)
bcdedit /set {default} nointegritychecks on (which should bypass driver signature enforcement. Again, not really indicating as such.)
At the still no luck point, I've followed the "strip all your cards and connected devices from your motherboard" diagnostic steps.
I tried a set of boot attempts with just the on-board intel video (set in bios) and then a Nivdia PCI card video. No go.
I have used the tools on my "Falcon 4" bootable diagnostic CD to check my memory sticks and other essential hardware, with no resulting errors.
I followed a thread about using DISM to check drivers and disable them, but I'm not sure this is the right path, since offline images .wim are not actually the installed and activated drivers for the OS. [dism-driver-servicing-command-line-options]
My only remaining option is the Command Prompt, which I can access, but I don't know what do to, in a command-line capacity, to force Windows 10 to either boot into safe mode, or disable all but a minimal set of drivers, so I can at least get into the operating system.
Can someone help me create a batch file? A script? A nanobot?
Or at least tell me how to enable boot logging to collect a log file and assist me in deciphering it?
I know how to disable drivers and services in safe mode, but I can't even get that far. I guess I should have stayed awake in my DOS class in 1983.
Any help is appreciated.
NOTE: For those following the "Hibernation File Loop" diagnosis, my system's hibernation was disabled before the 1803 Update and there is no "hiberfil.sys" file to delete.
Continue reading...
Following are the steps I have attempted to resolve this issue using command prompt only (I have been unsuccessful so far)
I have booted from W10 Repair Disc, and OEM 1709 and 1803 Install Discs with the following results:
System Restore - No points unavailable
Startup Repair - Unable to resolve problem
Go back to a previous version - Failed
System Image Recovery - (Don't have one, won't make that mistake again.)
I have successfully enabled "Legacy Boot" and can see the F8 options, but none seem to have any effect.
Disable Early Launch Anti-Malware Driver > result > Endless spinning dots
Disable Driver Signature Enforcement >result > Endless spinning dots
Debugging Mode >result > Endless spinning dots
Safe Mode / Safe Mode with Command Prompt >result > Endless spinning dots
When I boot with the Repair Disc, the only option that works properly, is "Command Prompt".
Using the Command Prompt, I have successfully executed the following commands, though I'm not sure they "stuck" as implied.
bcdedit /set {default} bootmenupolicy legacy (How I got the F8 to work again)
bcdedit /set {default} safeboot minimal (which doesn't seem to stick)
bcdedit /set {default} nointegritychecks on (which should bypass driver signature enforcement. Again, not really indicating as such.)
At the still no luck point, I've followed the "strip all your cards and connected devices from your motherboard" diagnostic steps.
I tried a set of boot attempts with just the on-board intel video (set in bios) and then a Nivdia PCI card video. No go.
I have used the tools on my "Falcon 4" bootable diagnostic CD to check my memory sticks and other essential hardware, with no resulting errors.
I followed a thread about using DISM to check drivers and disable them, but I'm not sure this is the right path, since offline images .wim are not actually the installed and activated drivers for the OS. [dism-driver-servicing-command-line-options]
My only remaining option is the Command Prompt, which I can access, but I don't know what do to, in a command-line capacity, to force Windows 10 to either boot into safe mode, or disable all but a minimal set of drivers, so I can at least get into the operating system.
Can someone help me create a batch file? A script? A nanobot?
Or at least tell me how to enable boot logging to collect a log file and assist me in deciphering it?
I know how to disable drivers and services in safe mode, but I can't even get that far. I guess I should have stayed awake in my DOS class in 1983.
Any help is appreciated.
NOTE: For those following the "Hibernation File Loop" diagnosis, my system's hibernation was disabled before the 1803 Update and there is no "hiberfil.sys" file to delete.
Continue reading...