- Apr 30, 2016
- 18
- 0
- 1,520
Hey there, I am currently expriencing a delema with my PC. I recently upraded my CPU and Motherboard from a 1700X to a 8700k and with the 1700x I got some periodic BSODs but nothing often. However, with my new setup:
I7 8700k
GTX 1080ti
32 GBs Trident RGB Ram
Z370e Asus Strix motherboard
250 Gb Samsung 960 pro SSD
1Tb WD HDD
2Tb Seagate HDD
2x 120Gb Sandisk SSD's
At first, what I thought was causing the crashes was my 5 Ghz overclock even though it seemed stable so I reset it to factory. I have all the drivers updated for everything.
I honestly dont know whats causing the crashes. My games most of the time just freeze and crash or sometimes just close without any warning or errors. My BSODS have a lot of different reasons here they are:
On Thu 4/12/2018 5:24:54 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\041218-7453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175930)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803B0750E27, 0x0, 0xFFFFFFFFFFFFFFFF)
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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 4/12/2018 5:24:54 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KeRegisterNmiCallback+0x21A)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803B0750E27, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 4/11/2018 6:06:31 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\041118-7468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80267058207, 0xFFFFF284F37619B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
Thank you for your Help
I7 8700k
GTX 1080ti
32 GBs Trident RGB Ram
Z370e Asus Strix motherboard
250 Gb Samsung 960 pro SSD
1Tb WD HDD
2Tb Seagate HDD
2x 120Gb Sandisk SSD's
At first, what I thought was causing the crashes was my 5 Ghz overclock even though it seemed stable so I reset it to factory. I have all the drivers updated for everything.
I honestly dont know whats causing the crashes. My games most of the time just freeze and crash or sometimes just close without any warning or errors. My BSODS have a lot of different reasons here they are:
On Thu 4/12/2018 5:24:54 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\041218-7453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175930)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803B0750E27, 0x0, 0xFFFFFFFFFFFFFFFF)
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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 4/12/2018 5:24:54 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KeRegisterNmiCallback+0x21A)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803B0750E27, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 4/11/2018 6:06:31 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\041118-7468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80267058207, 0xFFFFF284F37619B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
Thank you for your Help
Facebook
Twitter
Instagram