VM Failing to Reboot

dinhngtu

kagbasi-ngc

@dinhngtu So I removed both drivers, oem3.inf and oem5.inf successfully. Unfortunately, the VM is still crashing with a BSOD of INACCESSIBLE_BOOT_DEVICE with Secure Boot on or off.

dinhngtu

@kagbasi-ngc That's expected since the boot storage driver is gone. You'll need to get into Safe Mode with the Recovery or F8 menu.

kagbasi-ngc

@dinhngtu I got into Safe Mode, then did nothing and just rebooted, result was still the same BSOD.

dinhngtu

@kagbasi-ngc It worked on my VM when I tried that procedure on my local lab system. Unfortunately without a closer inspection I can't tell what's going on. If you still want to recover the VM, I'd start at removing all the non-inbox drivers.

kagbasi-ngc

@dinhngtu I’m not sure I understand what you mean by non-inbox drivers.

I will talk with our ISSO to see if sending an export of the VM is allowable. If not, would you be interested in a video call where we can troubleshoot in realtime?

dinhngtu

@kagbasi-ngc I think for that it'd be more appropriate to contact our support team, which will be able to help you directly on your infrastructure. I'd also like to keep any troubleshooting information on the forum in case someone runs into a similar problem.

Non-inbox drivers mean drivers with "Inbox : No" as seen in your screenshot.

kagbasi-ngc

@dinhngtu Roger that, agreed.

I just got back to the lab, so I'm gonna try and remove those non-inbox drivers and see what happens.

kagbasi-ngc

@dinhngtu Unfortunately, I don't have good news. I removed all the non-inbox drivers, one by one (rebooting after removing each one), yet still the VM is crashing with the same BSOD message.

dinhngtu

@kagbasi-ngc Could the VM get into Safe Mode?

kagbasi-ngc

@dinhngtu Yes, it does. There is no Last Known Good State option however.

dinhngtu

@kagbasi-ngc The fact that your VM still boots in Safe Mode means that there's still some drivers blocking Windows from booting in normal mode. Please enable boot logging by running bcdedit /store bcd /set {default} bootlog yes then post the boot logs of normal mode versus safe mode. This log is found at C:\Windows\ntbtlog.txt.

Could you send another copy of your SYSTEM hive?

kagbasi-ngc

@dinhngtu Just to clarify, the VM isn't booting into Safe Mode; I have to trigger it by smashing the F8 key at boot. It boots normally then goes to the BSOD.

I will get the logs for you shortly. Do you want me to drop them in the same location you sent earlier?

dinhngtu

@kagbasi-ngc Just to confirm, if you use the F8 menu it boots into Safe Mode without getting a BSOD, right? Please upload the SYSTEM hive to the same location.

kagbasi-ngc

@dinhngtu Yes, it does. The only time I get the BSOD is if I allow the VM to boot normally without interfering.

kagbasi-ngc

@dinhngtu So I managed to enable the boot logging, allowed the VM to do a normally boot to BSOD, then I booted with Hiren's, however, I'm not seeing the log file at C:\Windows.

dinhngtu

@kagbasi-ngc You might need the debugger in normal mode. Attach the debugger right at boot time and run the following command (beware the exact spelling):

sxe -c "lm1mna (poi(rdx));g" ld

Click Go until Windows loads completely or until you get a VM crash in Windbg, then paste the entire Windbg output.

kagbasi-ngc

@dinhngtu sorry for the delayed response, having trouble getting the debugger to reattach. I've re-input all the boot parameters, yet still, no data is being piped to the debug port on the host.

Do you think perhaps the removal of the drivers we did yesterday has removed the VM's ability to talk to the host?

dinhngtu

@kagbasi-ngc It shouldn't, the debugger drivers are built into Windows. If you're having issues with attaching the debugger, you can get into the F8 menu, start attaching WinDbg then choose Debugging mode in the F8 menu to start the guest. This should give WinDbg the correct timing to attach to the guest.