Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD and usb failing


30 Mar 2011   #1

Windows 7 Home Premium 32bit
 
 
BSOD and usb failing

This morning while updating before shutdown my laptop bluescreened, I thought meh perhaps a coincidence, I'll deal with it after work and closed the lid, came back this arvo, laptop was still on, hadn't shutdown and won't shutdown.(unless I hold the power button in.) it just does BSOD, mentions Driver_Power_State_Failure, counts to 10 and then restarts.

Before this update there was a critical update on Saturday morning(28th), and before that nothing since the 14th. And I havent noticed anything wrong except that my laptop would not recognize any USB devices at all on sunday.(and still won't)

Never had any problems with windows 7 until now, though I doubt its windows 7 thats the problem.

any ideas?
anyways thanks in advance

minidump.zip attatched

My System SpecsSystem Spec
.

30 Mar 2011   #2

Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
 
 

Hi there,

The dump reports are pointing to thpdrv.sys which is a toshiba laptop i believe that file relates to HDD protection program. Uninstall the current HDD protection system, then download and install the one from the Toshiba website.

Bugcheck:

Code:
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 00000258, Timeout in seconds.
Arg3: 861a9d48, The thread currently holding on to the Pnp lock.
Arg4: 83536b24

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  861a9d48

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  83575f60 -- (!locks 83575f60)

Resource @ nt!PiEngineLock (0x83575f60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0x83575f60
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 8347ec25 to 83477aa6

STACK_TEXT:  
8dd23788 8347ec25 861a9d48 00000000 807c2120 nt!KiSwapContext+0x26
8dd237c0 8347d523 861a9e08 861a9d48 8dd2388c nt!KiSwapThread+0x266
8dd237e8 8347740f 861a9d48 861a9e08 00000000 nt!KiCommitThreadWait+0x1df
8dd23864 8c0014f3 8dd2388c 00000000 00000000 nt!KeWaitForSingleObject+0x393
WARNING: Stack unwind information not available. Following frames may be wrong.
8dd238a4 8c003861 8b7db8e8 8b7db9a0 01579300 thpdrv+0x14f3
8dd238b8 8c004cc1 8b7db8e8 8b7db9a0 87878f38 thpdrv+0x3861
8dd23970 83424787 87878f38 8b85fba0 8ba35b38 thpdrv+0x4cc1
8dd2398c 835bf7c9 8b85fba0 8c004b9e 00000003 nt!PpvUtilCallAddDevice+0x19
8dd239d4 835b8300 87878f38 8c004b9e 00000001 nt!PnpCallAddDevice+0xb9
8dd23aa8 835b788c 8ba35b38 8dd23cd0 8b7ff4d0 nt!PipCallDriverAddDevice+0x565
8dd23ca4 835b1630 8b8d3e78 8b7ff4d0 8dd23cd0 nt!PipProcessDevNodeTree+0x15d
8dd23cd8 83423f9f 83573e80 861a9d48 8354a5bc nt!PiProcessReenumeration+0x74
8dd23d00 8347e03b 00000000 00000000 861a9d48 nt!PnpDeviceActionWorker+0x224
8dd23d50 8361e9df 00000001 abb8c0c1 00000000 nt!ExpWorkerThread+0x10d
8dd23d90 834d01d9 8347df2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .thread 0xffffffff861a9d48 ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    83477c9f - nt!SwapContext_PatchFxb+2
    [ 01:21 ]
    83477eed - nt!EnlightenedSwapContext_PatchFxb+2 (+0x24e)
    [ 01:21 ]
2 errors : !nt (83477c9f-83477eed)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT_LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT_LARGE

Followup: memory_corruption
---------
My System SpecsSystem Spec
Reply

 BSOD and usb failing




Thread Tools



Similar help and support threads for2: BSOD and usb failing
Thread Forum
Programs failing to launch after boot, followed by BSOD BSOD Help and Support
When installing Graphic driver, system is failing(BSOD). BSOD Help and Support
Occasional failing to start up and BSOD BSOD Help and Support
Is this HD failing ? Hardware & Devices
Failing SSD ? Hardware & Devices
BSOD after failing to shutdown or sleep BSOD Help and Support
something must be failing? Hardware & Devices

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 02:24 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33