Blue Screen of Death every few days, caused by ntoskrnl.exe

[Xenonrai]

Hey guys, for the past few weeks I've been getting BSOD every few days due to ntoskrnl.exe. I've tried solving this issue myself with Google but most solution haven't worked for me. Here's the dump files:

On Mon 16/01/2017 8:46:02 AM your computer crashed
crash dump file: C:\Windows\Minidump\011617-8593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x9F (0x3, 0xFFFFE28C76AEA060, 0xFFFFB001A5A5C8E0, 0xFFFFE28C77873010)
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.



On Mon 16/01/2017 8:46:02 AM 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, 0xFFFFE28C76AEA060, 0xFFFFB001A5A5C8E0, 0xFFFFE28C77873010)
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 that cannot be identified at this time.



On Fri 13/01/2017 1:03:31 AM your computer crashed
crash dump file: C:\Windows\Minidump\011317-8609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x9F (0x3, 0xFFFF9A0622A5A060, 0xFFFFAD0019CF58E0, 0xFFFF9A0624C66B80)
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.



On Wed 11/01/2017 8:18:26 PM your computer crashed
crash dump file: C:\Windows\Minidump\011117-8093-01.dmp
This was probably caused by the following module: syntp.sys (0xFFFFF80A319F0BF4)
Bugcheck code: 0xD1 (0xFFFFC6861D7CA000, 0x2, 0x0, 0xFFFFF80A319F0BF4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\syntp.sys
product: Synaptics Pointing Device Driver
company: Synaptics Incorporated
description: Synaptics Touchpad Win64 Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: syntp.sys (Synaptics Touchpad Win64 Driver, Synaptics Incorporated).
Google query: Synaptics Incorporated DRIVER_IRQL_NOT_LESS_OR_EQUAL

For the last dump file I updated the syn touchpad driver so hopefully that is resolved. I've tried memory tests so I doubt it's my ram and I have gone into Device Manager and changed up the settings. I'm pretty sure my drivers are up to date, but if not please point that out to me.

Thanks

 

[Colif]

its quite possible than unless you have had an error since you updated the Synaptics driver, the rest are fixed. The driver power state error generally means a driver isn't waking properly from sleep

ntoskrnl & ntkrnlmp.exe are both the Windows Kernel, often blamed for driver errors as they deal with driver requests.

If it keeps happening, can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[Xenonrai]

Yeah it hasn't happened since after I've updated the Synaptics driver, but it's only been a couple of days or so. I'll let you know if it happens again thanks!

 

[Xenonrai]

I got another BSOD today, here's the dump:

On Tue 17/01/2017 9:47:23 PM your computer crashed
crash dump file: C:\Windows\Minidump\011717-8375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x9F (0x3, 0xFFFFC18112CBB060, 0xFFFFF803EEF598E0, 0xFFFFC18112D05900)
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.



On Tue 17/01/2017 9:47:23 PM 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, 0xFFFFC18112CBB060, 0xFFFFF803EEF598E0, 0xFFFFC18112D05900)
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 that cannot be identified at this time.

 

[Colif]

can you upload the actual dump file as it should help us identify actual driver causing error, it isn't either of the files mentioned.

 

[Xenonrai]

Will dropbox work? I hope I did everything right

https://www.dropbox.com/sh/4x558pgly12xo31/AAB9YFW6HPIGP6Y4eXtvgloYa?dl=0

 

[Colif]

it should, just need to wait for someone to look at it now.