开发者

how to get memory dump after blue screen

开发者 https://www.devze.com 2023-01-28 01:30 出处:网络
I\'m getting a lovely BSOD on bootup (STOP: 0x0000007E) from a driver I\'m writing, and would like to load up the memory dump for analysis.However, it\'s not getting dumped anywhere.Everything is setu

I'm getting a lovely BSOD on bootup (STOP: 0x0000007E) from a driver I'm writing, and would like to load up the memory dump for analysis. However, it's not getting dumped anywhere. Everything is setup correctly in the Startup and Recovery settings, but I get no dump file, and nothing in the event log stating a dump has taken place. It looks like a dump is not even occurring...

I know the exact line of code causing it (a 开发者_如何学编程call to IoAttachDevice()), but am not sure why, and would like to view the DbgPrint output to see where exactly it's failing. Could Windows possibly be crashing before the dumping functionality is set up? If so, how do I get access to the state of the machine when the failure occurs?

UPDATE: Other possibly useful information: I'm running Windows XP through VirtualBox on a Linux host.


I don't know why you're not getting a dump file, but if you have ready access to the machine, attach a kernel debugger to it an repro the error - you'll be left with the machine sitting in the debugger, ready to go (you can have the debugger produce the dumpfile for you if you want to debug offline as well).


Right-click on "my computer" select "Advanced", under "startup and recovery" click "settings". select "kernel memory dump" or "complete memory dump".


What's the start setting of your driver? If it starts too early in the boot order, the filesystem might not be remounted read-write yet, and therefore there's no place for a dump to go.

Drivers under development shouldn't generally be set to auto-start until you've gotten the driver stable when loaded later. Of course you eventually need to set it to auto-start so you can verify it works correctly, but that comes later.

0

精彩评论

暂无评论...
验证码 换一张
取 消