none
Debug Windows 7 64-bit "hang-while-driver-installs" issue RRS feed

  • Question

  • Hi All,

    I am working on a display driver for Windows 7 64-bit . I have set up this 64-bit windows as a VirtualBox Guest OS. While installing the display driver on this guest OS, it hangs (The guest OS hangs, not the host). The driver debug prints are also not giving any proper idea as the last function returns successfully and then the control is going to the kernel.

    I also tried DebugView "Log to File" option, but after HANG, I do a restart only to see the log file is empty.

    Can anyone suggest some ways so that at least I can know which component is going bad in my driver? Or else some pointers so that I can proceed.

    Thanks in advance


    • Edited by deepak_ Thursday, April 25, 2013 2:21 PM
    Thursday, April 25, 2013 2:20 PM

Answers

  • It sounds like your driver is trashing much of the system.  You will need to see what portions of the driver are being called before the hang by putting in a ton of breakpoints and debug print statements.  Your driver is either putting the system into high IRQL and leaving it there or is trashing parts of memory includings the kernel debugging driver.


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Thursday, April 25, 2013 3:09 PM

All replies

  • The first step after the hang is to break into Windbg, the use !process 0 7 to dump all the threads in the system.  Search the dump for threads that were in your driver and see what they are waiting on.  Hopefully this will identify the problem.  If not things become harder.


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Thursday, April 25, 2013 2:40 PM
  • Thanks for responding Donald!!

    FYI, the WinDbg is running on the Host Machine and connected to the Target Machine (x64 Windows 7) through a pipe.

    Now, there are two things:

    First, after the Windows HANGS, even if I click on "Break" in WinDbg, nothing happens.

    Second, if the system is not breaking into WinDbg then how can I use  !process 0 7?? If you could elaborate a little plz....

    Thanks!!

    Thursday, April 25, 2013 2:58 PM
  • It sounds like your driver is trashing much of the system.  You will need to see what portions of the driver are being called before the hang by putting in a ton of breakpoints and debug print statements.  Your driver is either putting the system into high IRQL and leaving it there or is trashing parts of memory includings the kernel debugging driver.


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

    Thursday, April 25, 2013 3:09 PM