Early Boot Windows Debugging – Part 2 – Kernel Debugging over Serial

Early Boot Windows Debugging – Part 2 – Kernel Debugging over Serial

This post is a continuation of Part 1; I think I shall call it “Help, my ntbtlog.txt isn’t being written to disk and I’m flying blind”

Ok, now I need more data because I’m not getting anywhere. Fortunately Windows still has the option to log kernel debugging over serial. A feature I wasn’t aware existed util today. That brings up the big question: how do I make that work on a VM and a physical device without a serial port?

First you need to enable virtual printers in VMware Workstation under Edit > Preferences. Without this enabled Workstation can’t attach to named pipes.

Next we need to add a virtual serial port to our VM and tell it to output to named pipe
Next accept or change the named pipe (only replace the part “com_1” if you change it) and set it so that “This end is the server” and “The other end is an application”.  This means that your VM is the server and you are going to attach an application to the named pipe.
With that out of the way you need to install the Windows Debugging Tools which are included in the Windows SDK. Link for Windows 10 is here. After installing the debugging toolset we need to launch a new kernel debug session.
Go File > Kernel Debug in WinDbg
Next select the COM tab and fill it out with the below settings but replacing the name of the port with your named pipe.
Hit Ok and you should see your debugger start and say it’s “Waiting to reconnect…”
Even if you boot the VM at this point you won’t get any information first we need to boot to the Windows Repair wizard, go to Troubleshoot > Command Prompt and enable debugging using bcdedit.
bcdedit /bootdebug {bootmgr} on (Windows Boot Manager)
bcdedit /bootdebug on (boot loader)
bcdedit /debug on (OS Kernel debugger)
At this point you can now reboot. In theory this should be all that you need for debugging but I’ve noticed that the information is still lacking.
Instead have it boot explicitly to debug mode
Now your debug should have much more valuable information, this time pointing to “IOINIT: Built-in driver Driversacdrv failed to initialize with status – 0xc0000037
Congratulations, you can now see what is actually going on in your OS and where the root of the issue is at more more clarity.

Leave a Reply

Your email address will not be published. Required fields are marked *