Multiple BSOD's A day with different stopcodes

Agent Dash

Reputable
Apr 3, 2015
42
0
4,530
0
I have been getting multiple BSOD's a day with different stopcodes but usually the same few ones each time. I am lead to believe it is a driver issue but I can't seem to figure out what it would be. I have updated all my drivers (I'm pretty sure) and gotten rid of all viruses. what could be the issue??

My specs are as follows

ASUS ROG Rampage V 10 edition
Intel i7 6850k
128 GB RAM
2x 1080 TI SLI
500 GB Samsung 850 EVO SSD
2x 2 TB WD Black HDD's

the crash dumps are as follows...

On Mon 8/20/2018 12:04:19 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082018-14734-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF8000D66C50D)
Bugcheck code: 0xA (0xFFFF8600952DA0C0, 0x2, 0x1, 0xFFFFF8000D66C50D)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error.
Google query: IRQL_NOT_LESS_OR_EQUAL



On Mon 8/20/2018 12:04:19 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: Unknown (0xFFFFF8000D66C50D)
Bugcheck code: 0xA (0xFFFF8600952DA0C0, 0x2, 0x1, 0xFFFFF8000D66C50D)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error.
Google query: IRQL_NOT_LESS_OR_EQUAL



On Mon 8/20/2018 11:11:07 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082018-15406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF802E2069378, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 8/19/2018 6:42:05 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081918-14859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0xA (0xFFFF99811ACF1740, 0x2, 0x1, 0xFFFFF8015BBC650D)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 8/19/2018 3:26:02 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081918-15890-01.dmp
This was probably caused by the following module: Unknown (0x0000000000000000)
Bugcheck code: 0x139 (0x3, 0xFFFFF802C1E5BF00, 0xFFFFF802C1E5BE58, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
A third party driver was identified as the probable root cause of this system error.
Google query: KERNEL_SECURITY_CHECK_FAILURE


 

Agent Dash

Reputable
Apr 3, 2015
42
0
4,530
0


My GPU driver is up to date and CPU temp is 48 degrees C
 

Similar threads


ASK THE COMMUNITY