New
#1
Bsod Driver_Power_State
hi i get Bsod i need help to resolve
hi i get Bsod i need help to resolve
Hello mate now if you are running 10 like it says in your specs then best post in our sister forum Ten Forums at the top of the page - sign up just like you did for here - same crew different oS.
Plus please do the specs up System Specs - Fill in at Ten Forums - Windows 10 Tutorials - if you are heading off over there:)
no i use windows 7 no windows 10
Sorry mate I am sure it said 10 in the specs but anyway we still need specs for the 7 setup please
System Info - See Your System Specs it is very hard when one doesn't know what one is working with
This seems to be a very common dump and we have to track it down as I do see some graphical problems too. So it is important to know what you have in that machine hard and soft ware wise.Code:Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols
Edit: I meant to add these a couple of simplistic scans to start with
SFC /SCANNOW Command - System File Checker
Disk Check < if necessary include the /f and /r in the command line as per Option2
Run these in safe mode and the sfc often best run for two to three runs – you can leave out the /r switch in ckdsk if you feel it not necessary
i do sfc /scannow % chkdsk /f /r
and today i get again bsod
On Tue 13/12/2016 10:42:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121316-18158-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800CCD8870, 0xFFFFF800057483D8, 0xFFFFFA800A654E10)
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 that cannot be identified at this time.
i attach msinfo to this replay
Last edited by Almogc; 13 Dec 2016 at 07:42.
To help our BSOD Team please complete this tutorial completely.
Blue Screen of Death (BSOD) Posting Instructions
next to the original post i get again bsod