Cannot Shutdown without BSOD

pauljeter · Aug 4, 2010

I cannot Shutdown without the Shutdown Screen stalling for 10 minutes and then getting a BSOD. Also, when I close the lid, the screen goes black, but it does not go to sleep. (Fan continues to run, Quickplay buttons are still lit up, and the computer gets hot) When I reopen the lid, the computer will not wake up and the screen remains black. I have to physically power down and restart with the power button.

I have downloaded the Debugging Tools to read the dump files, but cannot figure out what needs to be fixed. The Dump Files show umbus.sys and ntkrnlmp.exe

I Reintalled Windows 7 and updated the drivers one at a time to diagnose, but it did not happen again until after I had completed this. I also tried flashing the BIOS to earlier versions, but this does not help either.

Any help would be apreciated.

-Windows 7 x64
-Full retail version
-Originally Vista x64
-System is 1.5 years old
-OS was re-installed last week

System Info:

HP Pavilion dv5-1125nr
CPU:AMD Turion X2 Dual-Core Mobile RM-72 2.10 GHz
Memory: 4.00 GB (3.75 GB Usable)
Graphics Card: ATI Radeon HD 3200
Hard Drives: WDC WD2500BEVS-60UST0 ATA Device

ttran · Aug 4, 2010

Can you please follow this instruction:
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

pauljeter · Aug 4, 2010

My apologies

My apologies. I was following the instructions in creating my post. I do not know why the zip file did not attach the first time. Here it is.

ttran · Aug 4, 2010

umbus.sys was blamed in the DMP, it is User-Mode Bus Enumerator, make sure you are having WINDOW UPDATE on.
Another thing which was not directly blamed but seem to be problem. It is hpdskflt.sys, which is HP Mobile Data Protection System Disk Filter. I would download and install fresh copy of it.

BUGCHECK SUMMARY:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.470\080410-29374-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c4be50
Debug session time: Wed Aug  4 20:51:06.188 2010 (UTC + 7:00)
System Uptime: 0 days 9:46:25.136
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8003cf1680, fffff80000b9c510}

Unable to load image \SystemRoot\system32\DRIVERS\hpdskflt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for hpdskflt.sys
*** ERROR: Module load completed but symbols could not be loaded for hpdskflt.sys
Probably caused by : umbus.sys

Followup: MachineOwner
---------

Update this driver please:

Code:

agrsm64  agrsm64.sys  Mon Nov 10 22:01:35 2008 (49184CCF)

It is Agere Systems Soft Modem, see if you can update it to newer version
Support and Downloads

Regard,

Tuan

pauljeter · Aug 6, 2010

Solved - WD My Book World Edition at fault

Thanks for your response. I performed a "Clean" install of Windows 7 and installed the updates and drivers one at a time to find the culprit. I had no issues after I did this until I connected to my WD My Book World Edition network drive. It did not install the driver correctly, so I did a search for the Windows 7 Driver, but could not find one. What I did find was this post:

http://www.sevenforums.com/network-sharing/5708-my-book-world-edition.html

It outlined the problems that I was having and a work around to use until Western Digital fixes the drivers for Windows 7. Here is how it was fixed:

pejx72 said:
For me, at least: From reading the various forum discussions on this I surmise that the Win 7 64 shutdown problems are caused by Windows waiting for the hard drive to respond that it is powering-down. Under the Network Tab of Windows Explorer, my Windows 64 setup seems to recognise the MyBook as a "Storage Device" and as a "Computer". The "Storage Device" element doesn't work properly, but the Computer one does (I can access all my MyBook directories from there - I also mapped them to Drive letters just in case...). This means the "Storage Device" is unnecessary, right? So I went to Device Manager and "Disabled" the MyBook as a Hard Drive. Since then everything has worked perfectly: No shutdown problems; constant visibility of the MyBook as a "Computer" on my home network. I guess all the issues were caused by a bad/wrong driver for the MyBook as a *Hard Drive*, and by preventing Windows 64 seeing it as a Hard Drive I have fixed my problems.

Let's see how long before it goes wrong again...

Let me know if this worked for anyone else?

Thanks again,

Paul Jeter

cluberti · Aug 6, 2010

In the future, if windows just hangs and isn't responding, you can configure the machine so that you can cause it to crash via the keyboard and generate a dump (in this instance, you probably want to have the machine configured for at least a kernel memory dump, and if possible, a complete dump). Once you make the reg change and reboot, the machine now has an event handler for the keyboard drivers where if you hold down the CTRL key, and press SCROLL LOCK twice while holding down that key, the machine will crash with a STOP 0xE2 (manually initiated dump).

Glad to see you figured it out, but I figured I'd drop this just for future reference - a kernel or complete dump gathered this way would have shown the stuck disk queue and IRP to the WD drive, if that is indeed what is causing it, for what it's worth.

Cannot Shutdown without BSOD

pauljeter

New member

My Computer

ttran

Computational Biologist

My Computer

pauljeter

New member

My Computer

ttran

Computational Biologist

My Computer

pauljeter

New member

My Computer

cluberti

Cat herder

My Computer