Geting BSOD and usb ports doesnt work after hibernating

coolraghav

Disciple
Solve my problems please, I'm not that kind of geeky person..So really need help.

First is..I'm getting BSOD while when it comes it says in CAPS " DRIVER POWER STATE FAILURE" (minidump file enclosed)

081711-35786-01.dmp

Whats the solution for it? It comes anytime..my hdd gonna die ?

Secondly whenever i turn on my laptop from hibernating ..my usb ports doesnt work. I've already changed the power management thing from device manager but it is of no help. So probably there needs to be another solution.

Waiting for your help.
 
You system specs ?

Is it a new machine which has this problem from the beginning or an old machine ? If it is an old machine then what were you doing last before these problems started ?

If you feel this is a disk problem, did you run chkdsk ?
 
apple os? the problem with usb ports not working from standby seem to be mostly related to apple os x.
on the other hand it could be vista too.

do post your laptop specs and os used.
 
my laptop is lenovo u330 running on windows 7 professional.

My laptop is old, around 2 years and I haven't done anything which could affect the normalcy.

I thought minidump could help :( .
 
--------------------------------------------------------------------------------

Welcome to WhoCrashed HOME EDITION v 3.02

--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit Resplendence Software - Contact and Support Form

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...

--------------------------------------------------------------------------------

Home Edition Notice

--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.

Click here to buy the the professional edition of WhoCrashed.

--------------------------------------------------------------------------------

System Information (local)

--------------------------------------------------------------------------------

computer name: RAGHAV-LAPPY

windows version: Windows 7 , 6.1, build: 7600

windows dir: C:\Windows

CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz Intel586, level: 6

2 logical processors, active mask: 3

RAM: 4222513152 total

VM: 2147352576, free: 1894928384

--------------------------------------------------------------------------------

Crash Dump Analysis

--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 17-08-2011 10:04:52 GMT your computer crashed

crash dump file: C:\Windows\Minidump\081711-32526-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)

Bugcheck code: 0x9F (0x3, 0xFFFFFA8006030060, 0xFFFFF80000BA2748, 0xFFFFFA8007B867F0)

Error: DRIVER_POWER_STATE_FAILURE

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 17-08-2011 05:37:43 GMT your computer crashed

crash dump file: C:\Windows\Minidump\081711-35786-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)

Bugcheck code: 0x9F (0x3, 0xFFFFFA800606D060, 0xFFFFF80000B9C518, 0xFFFFFA80051555D0)

Error: DRIVER_POWER_STATE_FAILURE

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Tue 16-08-2011 07:02:03 GMT your computer crashed

crash dump file: C:\Windows\Minidump\081611-17160-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)

Bugcheck code: 0x9F (0x3, 0xFFFFFA8004E57060, 0xFFFFF80000B9C518, 0xFFFFFA80048A6BD0)

Error: DRIVER_POWER_STATE_FAILURE

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Tue 16-08-2011 06:16:56 GMT your computer crashed

crash dump file: C:\Windows\Minidump\081611-34382-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)

Bugcheck code: 0x9F (0x3, 0xFFFFFA8005F6F060, 0xFFFFF80000BA2748, 0xFFFFFA800811CA10)

Error: DRIVER_POWER_STATE_FAILURE

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sun 14-08-2011 05:38:10 GMT your computer crashed

crash dump file: C:\Windows\Minidump\081411-37331-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)

Bugcheck code: 0x9F (0x3, 0xFFFFFA8006050060, 0xFFFFF80004C2C518, 0xFFFFFA800487F010)

Error: DRIVER_POWER_STATE_FAILURE

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

--------------------------------------------------------------------------------

Conclusion

--------------------------------------------------------------------------------

5 crash dumps have been found and analyzed.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 
Back
Top