Windows 10 crashing and can't sleep or turn off without hard turn off

P

PokreFace

I have laptop lenovo ideapad 320 ikb and i can't turn off it or let it sleep because everytime i try to put it sleep or turn off it show black screen but the power button light is still on and if i want to turn it off i need to use the power button and when i put it sleep i can't wake it up. I looked reliability history and it says windows stopped working so i downloaded "whocrashed" and i found 2 crash dump files :


[COLOR=rgba(17, 17, 17, 1)]On Sat 17/04/2021 21:45:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041821-95500-01.dmp
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]ntoskrnl.exe[/COLOR] (nt+0x3F5E40)
Bugcheck code: 0x9F (0x3, 0xFFFFE40C7855F360, 0xFFFFF8011E181750, 0xFFFFE40C855226F0)
Error: [COLOR=rgba(17, 17, 17, 1)]DRIVER_POWER_STATE_FAILURE[/COLOR]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [COLOR=rgba(17, 17, 17, 1)]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba(17, 17, 17, 1)]Microsoft Corporation[/COLOR]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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.

[COLOR=rgba(17, 17, 17, 1)]On Sat 17/04/2021 21:45:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]ntkrnlmp.exe[/COLOR] (nt!MmTrimAllSystemPagableMemory+0x28907)
Bugcheck code: 0x9F (0x3, 0xFFFFE40C7855F360, 0xFFFFF8011E181750, 0xFFFFE40C855226F0)
Error: [COLOR=rgba(17, 17, 17, 1)]DRIVER_POWER_STATE_FAILURE[/COLOR]
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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. [/COLOR][/COLOR]

Continue reading...
 
Back
Top Bottom