Bsod every hour, windows 10 ( DRIVER_IRQL_NOT_LESS_OR_EQUAL, KMODE_EXCEPTION_NOT_HANDLED )

[Raphaeloper]

https://drive.google.com/file/d/0B3fb6j6UhGJkdlhHdDJCdHJjdlU/view?usp=sharing
This is the link to the dump files. (The reason why there are only 3 of them is that I updated Windows, and it erased the older dumps...)
So my problem is that my pc keeps crashing every hour or so, even when I'm doing some casual tasks. I used sfc, memtest. I updated everything I could, and i'm pretty sure it's not a hardware problem... So now I feel pretty lost... I would happily provide any information I can...
Thanks in advance

 

[Colif]

I can't read dumps but this can, Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

we can have a look while you wait for someone to read dumps.

 

[Raphaeloper]

I can't read dumps but this can, Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

we can have a look while you wait for someone to read dumps.

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 13-May-17 03:39:37 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\051317-10687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xD1 (0xD66, 0xFF, 0xA1, 0xD66)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 13-May-17 03:39:37 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: 0xD1 (0xD66, 0xFF, 0xA1, 0xD66)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 13-May-17 03:12:09 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\051317-5078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF803E46078C8, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sat 13-May-17 02:23:11 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\051317-6031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xD1 (0x4D66, 0xFF, 0x49, 0x4D66)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

Its just blaming the windows kernel as usual

In case no one looks at this for a while, you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, run Who crashed and see what driver it reveals

note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again
download the Windows 10 media creation tool and use it to make a win 10 installer on USB

The instructions to stop it are in the link above but I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose command Prompt
type verifer /reset and press enter
restart PC

 

[Raphaeloper]

Its just blaming the windows kernel as usual

In case no one looks at this for a while, you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, run Who crashed and see what driver it reveals

note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again
download the Windows 10 media creation tool and use it to make a win 10 installer on USB

The instructions to stop it are in the link above but I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose command Prompt
type verifer /reset and press enter
restart PC

Thanks dude, will try this

 

[HARRY_6]

Its just blaming the windows kernel as usual

In case no one looks at this for a while, you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, run Who crashed and see what driver it reveals

note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again
download the Windows 10 media creation tool and use it to make a win 10 installer on USB

The instructions to stop it are in the link above but I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose command Prompt
type verifer /reset and press enter
restart PC

 

[Colif]

2 things,
1. this is an old thread and now I wouldn't recommend driver verifer as much as it tends to cause boot loops too often, and
2. you are better off starting your own thread as not all BSOD are caused by same things, and more people will look at it.

Can you follow option one here
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 in the new thread, and someone with right software to read them will help you fix it