Hi there. I am having three problems with my brand new HP8540w computer running Windows 7 x64. New USB devices are not recognized. Windows Backup fails - timeout when creating shadow copy. Shutdown fails - blue screen after looooong time 1 - New UBS devices are not recognized When running in normal mode, new USB devices are not recognized. Rebooting with the device plugged in works perfectly. Plugging devices in and out when in safe mode works perfectly. 2 - Windows Backup fails - timeout when creating shadow copy. I have tried the recommendation posted in http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/6232100d-1b9b-46ed-960d-f5a866e357c5 to no avail. I have a very large backup set (~150GB due to several virtual machines++), but backup should still work... 3 - Shutdown fails - blue screen after looooong time When shutting down, the PC is hanging for several minutes. I finally get a bluescreen - with the following minidump: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000009F, {4, 258, fffffa8006c90680, fffff80000b9c510} Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem. Arg2: 0000000000000258, Timeout in seconds. Arg3: fffffa8006c90680, The thread currently holding on to the Pnp lock. Arg4: fffff80000b9c510 Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 4 FAULTING_THREAD: fffffa8006c90680 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800032c3992 to fffff800032c25da STACK_TEXT: fffff880`03ba8760 fffff800`032c3992 : fffffa80`06c90680 fffffa80`06c90680 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a fffff880`03ba88a0 fffff800`032c5cff : fffff800`03448b40 fffff880`03ba8a70 00000000`000000ca fffff880`03ba8a00 : nt!KiCommitThreadWait+0x1d2 fffff880`03ba8930 fffff800`03285242 : 00000000`00000000 fffff800`0000001b 00000000`00000000 fffff880`03964100 : nt!KeWaitForSingleObject+0x19f fffff880`03ba89d0 fffff800`032c45ac : ffffffff`fd9da600 fffffa80`09e18b00 fffff800`034c0400 00000000`00000000 : nt!ExpWaitForResource+0xae fffff880`03ba8a40 fffff800`035177ef : fffff880`03ba8cb8 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ExAcquireResourceExclusiveLite+0x14f fffff880`03ba8ab0 fffff800`03735dc7 : 00000000`00000000 fffffa80`0b35d190 fffff8a0`158bfd90 fffff880`03ba8cb8 : nt! ?? ::NNGAKEGL::`string'+0x1354c fffff880`03ba8ae0 fffff800`03736fdc : fffff880`03ba8cb8 fffffa80`0f9bd900 fffffa80`06c90680 fffffa80`0f9bd980 : nt!PnpProcessQueryRemoveAndEject+0x77 fffff880`03ba8c20 fffff800`036220dc : 00000000`00000000 fffffa80`0f9bd980 fffff8a0`158bfd90 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c fffff880`03ba8c50 fffff800`032c9961 : fffff800`03528008 fffff8a0`158bfd90 fffff800`034615f8 fffffa80`06c90680 : nt! ?? ::NNGAKEGL::`string'+0x58ffb fffff880`03ba8cb0 fffff800`03560c06 : 00000000`00000000 fffffa80`06c90680 00000000`00000080 fffffa80`06c78040 : nt!ExpWorkerThread+0x111 fffff880`03ba8d40 fffff800`0329ac26 : fffff880`039d5180 fffffa80`06c90680 fffff880`039dffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03ba8d80 00000000`00000000 : fffff880`03ba9000 fffff880`03ba3000 fffff880`03ba7440 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .thread 0xfffffa8006c90680 ; kb FOLLOWUP_IP: nt!KiSwapContext+7a fffff800`032c25da 488d8c2400010000 lea rcx,[rsp+100h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiSwapContext+7a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x9F_4_nt!KiSwapContext+7a BUCKET_ID: X64_0x9F_4_nt!KiSwapContext+7a Followup: MachineOwner --------- Before I disabled the system restore, I got another error message: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000009F, {4, 258, fffffa8006c90b60, 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 *** WARNING: Unable to verify timestamp for umbus.sys *** ERROR: Module load completed but symbols could not be loaded for umbus.sys Probably caused by : umbus.sys Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem. Arg2: 0000000000000258, Timeout in seconds. Arg3: fffffa8006c90b60, The thread currently holding on to the Pnp lock. Arg4: fffff80000b9c510 Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 4 DRIVER_OBJECT: fffffa8009dfb060 IMAGE_NAME: umbus.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc20 MODULE_NAME: umbus FAULTING_MODULE: fffff88006eb7000 umbus CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 STACK_TEXT: fffff880`03ba11c0 fffff800`0327c992 : fffffa80`06c90b60 fffffa80`06c90b60 00000000`00000000 00000000`00000007 : nt!KiSwapContext+0x7a fffff880`03ba1300 fffff800`0327ecff : fffffa80`0ceffc60 fffffa80`0c642810 00000000`00000000 00000000`0000000c : nt!KiCommitThreadWait+0x1d2 fffff880`03ba1390 fffff880`01c75bcf : 00000000`03ba1500 fffffa80`00000000 fffff880`03ba1400 00000000`00000700 : nt!KeWaitForSingleObject+0x19f fffff880`03ba1430 00000000`03ba1500 : fffffa80`00000000 fffff880`03ba1400 00000000`00000700 fffff880`009ea180 : hpdskflt+0x2bcf fffff880`03ba1438 fffffa80`00000000 : fffff880`03ba1400 00000000`00000700 fffff880`009ea180 fffff800`00000008 : 0x3ba1500 fffff880`03ba1440 fffff880`03ba1400 : 00000000`00000700 fffff880`009ea180 fffff800`00000008 fffffa80`0719c100 : 0xfffffa80`00000000 fffff880`03ba1448 00000000`00000700 : fffff880`009ea180 fffff800`00000008 fffffa80`0719c100 fffffa80`0719c160 : 0xfffff880`03ba1400 fffff880`03ba1450 fffff880`009ea180 : fffff800`00000008 fffffa80`0719c100 fffffa80`0719c160 fffff880`03ba1490 : 0x700 fffff880`03ba1458 fffff800`00000008 : fffffa80`0719c100 fffffa80`0719c160 fffff880`03ba1490 00000000`00000000 : 0xfffff880`009ea180 fffff880`03ba1460 fffffa80`0719c100 : fffffa80`0719c160 fffff880`03ba1490 00000000`00000000 fffff880`03ba1548 : 0xfffff800`00000008 fffff880`03ba1468 fffffa80`0719c160 : fffff880`03ba1490 00000000`00000000 fffff880`03ba1548 00000000`c0000000 : 0xfffffa80`0719c100 fffff880`03ba1470 fffff880`03ba1490 : 00000000`00000000 fffff880`03ba1548 00000000`c0000000 fffffa80`06c8bc90 : 0xfffffa80`0719c160 fffff880`03ba1478 00000000`00000000 : fffff880`03ba1548 00000000`c0000000 fffffa80`06c8bc90 fffff800`03270f30 : 0xfffff880`03ba1490 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_4_IMAGE_umbus.sys BUCKET_ID: X64_0x9F_4_IMAGE_umbus.sys Followup: MachineOwner --------- Does anyone have any tips or hints as to how to proceed? I am considering a clean Win7 install, but of course I would rather not do that...Espen Halsaa Albrektsen www.albrektesen.net

Forgot to mention: The USB and shutdown issues are "new" - my machine was working OK up untill last week - at least with respect to USB and shutdown. Windows backup I have not tried before my machine started to malfunction, since I use the excellent online backup service from www.mozy.com which protects most of my files.Espen Halsaa Albrektsen www.albrektesen.net

Have you tried a system restore to back before you had the problem? Have you tried restoring the computer back to factory settings?

System Restore has not been tried - since I wiped the restore when trying to follow the recommendations in the other post, so I could not. I did uninstall the drivers that had been installed (A USB-serial port driver from Prolific) manually - and that did not help. I am moving all my files off to an external HDD and will do a factory reset once they have been copied - will update this issue once that has been tried...Espen Halsaa Albrektsen www.albrektesen.net

Please temporary remove the antivirus and check the result.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

This has been tried - no effectEspen Halsaa Albrektsen www.albrektesen.net

Hi. I'm having the same issues you had... Could you solve the problem? Thanks. Marcus Gaspar

Yes - I solved the problem by uninstalling a driver for my Western Digital ShareSpace NAS. Several posts on the Western Digital forums talk of similar issues: http://community.wdc.com/t5/WD-ShareSpace/WD-Sharespace-4TB-suddenly-giving-my-computer-a-BSOD-Blue-Screen/td-p/32738 In my case the driver prevented the machine from shutting down - looks like the driver can cause other problems as well...Espen Halsaa Albrektsen www.albrektesen.net

Thanks Espen. How can I find out which driver is giving me problems? How did you get the minidump log? Many thanks in advance.

Hi guys! I solved the problem! The problem was also related to a Western Digital driver which was installed in my computer (I believe through Windows Update). In my case, the driver was "My Book World Edition Network Storage", for the external network hard drive: My World book - http://www.wdc.com/en/products/products.aspx?id=300). I just disabled this driver in the Windows Device Manager and everything returned to work properly! This driver, in my case, is not necessary... because the hard drive works like a NAS, so I just need to map (on Windows) my hard drive's shared folders. I had the exactly same problem in two different notebooks (Dell 830 and HP 8540w). Best, Marcus Gaspar