J
JusTDutcH101-91E4DBBF-E59F-4CD1-99EF-A694DD4ACA78
So my laptop died around a year ago and I had it repaired 3 to 4 times (due to BSOD on start-up). After the 4th time repaired (it was the only shop I was allowed to repair for free since they covered almost all costs, otherwise it would cost me a fortune) I just settled with the game being able to run less games. However, recently he started to give me the BSOD 'Driver power state failure' on startup from certain games. I let it analyse by WhoCrashed and it said this: ''crash dump file: C:\Windows\Minidump\010218-28953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DBA0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001B1D14060, 0xFFFFD000B183F960, 0xFFFFE001B61FD9C0)
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. 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. ''
Anyone with knowledge if there is anything I can do by myself or do I need to get it checked again? It's a laptop and the rapir was about the motherboard.
Continue reading...
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DBA0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001B1D14060, 0xFFFFD000B183F960, 0xFFFFE001B61FD9C0)
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. 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. ''
Anyone with knowledge if there is anything I can do by myself or do I need to get it checked again? It's a laptop and the rapir was about the motherboard.
Continue reading...