The How-To Geek Forums Have Migrated to Discourse


How-To Geek Forums / Windows 7

How to fix Blue Screen on windows 7 after shut down/sleep/hibernate and restart

(9 posts)
  • Started 6 years ago by DIGGY416
  • Latest reply from keshu
  • Topic Viewed 6242 times

DIGGY416
Posts: 9

I have Windows 7 home premium and lately ive been having this problem and i thought i had it fixed but it started happening again... so everytime i shut down/sleep/hibernate or restart my laptop witch is a ACER Aspire 5251-1007 it give a blue screen before it shuts down and when i restart it it tells me it has recoverd from a unexpected shut down like every single time i turn it on any ideas on how i can fix this if needed i can give you like the log files or whatever if you tell me how to or i can allow remote control/assistance and you can help me fix this problem as soon as possible because i dont want to have to send it back to acer and end up erasing all my stuff....

Thanks in advance.

Posted 6 years ago
Top
 
mfletch
Posts: 1434

Hi

Can you please download and run this WhoCrashed

http://www.resplendence.com/whocrashed

Its most probably a driver that's causing the blue screen and hopefully whocrashed will tell us which one

Can you post the log back on here.

Posted 6 years ago
Top
 
DIGGY416
Posts: 9

Hi thanks for replying here is the report from that program.

System Information (local)
--------------------------------------------------------------------------------

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD V120 Processor AMD586, level: 16
1 logical processors, active mask: 1
RAM: 2947440640 total
VM: 2147352576, free: 1962217472

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 07/10/2011 5:29:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100711-27690-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003087A10, 0xFFFFF8000519D748, 0xFFFFFA800543A270)
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 Fri 07/10/2011 5:29:03 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003087A10, 0xFFFFF8000519D748, 0xFFFFFA800543A270)
Error: DRIVER_POWER_STATE_FAILURE
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 Thu 06/10/2011 10:19:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100611-26379-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003085A10, 0xFFFFF80000BA2748, 0xFFFFFA80028388F0)
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 Thu 06/10/2011 5:30:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100611-21091-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003076060, 0xFFFFF80000BA2748, 0xFFFFFA8002869C60)
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 Thu 06/10/2011 1:02:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100611-26442-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003057A10, 0xFFFFF80000BA2748, 0xFFFFFA8004C4B740)
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 05/10/2011 10:18:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100511-23072-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003072A10, 0xFFFFF80000BA2748, 0xFFFFFA8003682480)
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 05/10/2011 2:39:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100511-38953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800306A360, 0xFFFFF80000BA2748, 0xFFFFFA8004F14CF0)
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 05/10/2011 5:45:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100511-60606-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003052360, 0xFFFFF80005197518, 0xFFFFFA8004145010)
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 04/10/2011 9:45:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100411-28594-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003057060, 0xFFFFF80005197518, 0xFFFFFA8003701390)
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 Mon 03/10/2011 3:06:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100311-34335-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8002223980, 0xFFFFF80000B9C518, 0xFFFFFA80037FBE10)
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
--------------------------------------------------------------------------------

10 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.

Posted 6 years ago
Top
 
mfletch
Posts: 1434

First have you installed any new software if yes remove it and see if alls ok then if not.

Backup all your documents pictures etc then.

NTOSKRNL.EXE is a operating system file.

I would recommend using the W7 CD to repair the system

1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings, and then click “Next”.
3. Click “Repair your computer.”

Posted 6 years ago
Top
 
DIGGY416
Posts: 9

Unfortunately i don't have a Windows installation disk, i never got one with my laptop... because its windows 7 i just usually reinstall windows to factory settings but at this time i dont have a back up CD either or a data CD i just back up my stuff to my C:/ drive any other ideas of what i can do about this other than reinstalling windows? i just don't wanna loose all my stuff i just work so hard last week to put back on...

Posted 6 years ago
Top
 
Lighthouse
Posts: 13598

May still work,
http://www.askvg.com/direct-do.....nd-64-bit/

Posted 6 years ago
Top
 
DIGGY416
Posts: 9

okay i saw the link but i dont know what to download if those are service pack 1 for windows 7 i think my computer already installed those updates... what do i do to fix this? :(

Posted 6 years ago
Top
 
babinlonston
Posts: 177

Backup ur all needed files in ur pen drive r usb hard drive first then right click my computer select managae in that choose Disk management it will load ur drives see there wether any drive named as Recovery Partion ? May be around 8 GgB if its there u can resoter ur Pc to ur factory settings which brand ur using ? May be F10 r F12 want to be pressed for recovery while system gets on Post ur Laptop model and its Brand

Posted 6 years ago
Top
 
keshu
Posts: 21

Hi DIGGY416,

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

first backup your files on to a pen drive and do a "system restore." This will uninstall all the programs and softwares and after that scan your computer with your anti virus which will eliminate any viruses or bugs!

keshu

Posted 6 years ago
Top
 



Topic Closed

This topic has been closed to new replies.