Tech Support Forum - View Single Post - Shutdown/hibernate results in memory dump and restart

dave.ruybal · 06-19-2009, 08:40 PM

Howdy y'all,

I am dealing with quite the annoying problem that has been plaguing me for a couple weeks now. When i either hit the power key, or select hibernate/shutdown/restart from the start menu, my laptop will give me the blue screen explaining that a memory dump has been initiated. On this screen it references usbhub.sys as the culprit.

I did a little googling to find out how to debug memory dumps, and I downloaded and installed the WinDbg utility. The problem is that the memory.dmp file in the Windows folder lists June 9th as the date, which is not current as I have recreated this memory dumping situation a few times today. And in the minidumps folder, I see one from 6/9/09, and a couple from 6/6/09, which seem out dated as well.

In looking into these dumps with WinDbg, i see a bunch of references to libusb.sys, which is something I know that I have installed in the recent past in conjunction with another utility to use my Playstation 3 controller over USB. I also installed a cheesy program called WinDS3, which installs custom drivers into my laptops built in bluetooth adapter, allowing use of the Playstation controller over Bluetooth. I have since uninstalled this software, which also uninstalls the custom drivers from my bluetooth adapter.

I have run a full virus scan with AVG, and ran a scan with SpyBot. SpyBot found a couple things and repaired them, but they did not affect this problem in anyway that I'm aware of.

I am dual-booting Vista SP2 and Windows 7 Ultimate. Windows 7 runs just fine and does not display any of these symptoms.

So, I'm obviously not too sure what I'm looking for in the debug data, just trying to find a little guidance in the direction of the problem. If there is a way to force it to find an up to date dump to debug, I'm sure that would be very effective.

I don't know all there is to know, but I'm good at following directions. Thanks for any help in advance.

My system specs are:
Dell XPS M1530 Laptop
Windows Vista Home Premium SP2 32-bit
3GB RAM
1.66Ghz Core 2 Duo

Website for WinDS3: http://www.winds3.com/en/index.htm

06-19-2009, 08:40 PM	#1 (permalink)
dave.ruybal Registered User Join Date: Jun 2009 Posts: 2 OS: Vista SP2, Win 7 Ult	Shutdown/hibernate results in memory dump and restart Howdy y'all, I am dealing with quite the annoying problem that has been plaguing me for a couple weeks now. When i either hit the power key, or select hibernate/shutdown/restart from the start menu, my laptop will give me the blue screen explaining that a memory dump has been initiated. On this screen it references usbhub.sys as the culprit. I did a little googling to find out how to debug memory dumps, and I downloaded and installed the WinDbg utility. The problem is that the memory.dmp file in the Windows folder lists June 9th as the date, which is not current as I have recreated this memory dumping situation a few times today. And in the minidumps folder, I see one from 6/9/09, and a couple from 6/6/09, which seem out dated as well. In looking into these dumps with WinDbg, i see a bunch of references to libusb.sys, which is something I know that I have installed in the recent past in conjunction with another utility to use my Playstation 3 controller over USB. I also installed a cheesy program called WinDS3, which installs custom drivers into my laptops built in bluetooth adapter, allowing use of the Playstation controller over Bluetooth. I have since uninstalled this software, which also uninstalls the custom drivers from my bluetooth adapter. I have run a full virus scan with AVG, and ran a scan with SpyBot. SpyBot found a couple things and repaired them, but they did not affect this problem in anyway that I'm aware of. I am dual-booting Vista SP2 and Windows 7 Ultimate. Windows 7 runs just fine and does not display any of these symptoms. So, I'm obviously not too sure what I'm looking for in the debug data, just trying to find a little guidance in the direction of the problem. If there is a way to force it to find an up to date dump to debug, I'm sure that would be very effective. I don't know all there is to know, but I'm good at following directions. Thanks for any help in advance. My system specs are: Dell XPS M1530 Laptop Windows Vista Home Premium SP2 32-bit 3GB RAM 1.66Ghz Core 2 Duo Website for WinDS3: http://www.winds3.com/en/index.htm