D
daytona675(2)
Hi There, completely stumped with troubleshooting. Hope someone here can provide some insight. Please see below for all troubleshooting I have tried. Log outputs along with system specs at the end.
Symptoms - after Win10 update last week, computer will boot in to Windows and crash sometimes immediately and sometimes after 10-20 minutes, each time throwing same BSOD code KMODE_EXCEPTION_NOT_HANDLED.
Attempted troubleshooting:
-Attempted system restore to prior to update, attempted to uninstall last known updates
-Attempted brand new Windows 10 install on TWO different and formatted known working SSD's
-Total of two x 4GB RAM sticks- attempted to reseat and remove one to isolate if there was a bad player
-All drivers updated
-Ran Memory Diagnostic Tool; test came back successful with no found issues
-Ran Driver Verifier to stress test all non-microsoft related drivers; didn't point to any new issues in crash log besides the same ones shared below (primarily ntoskrnl.exe)
-Ran sfc /scannow; system file checker came back successful with no found issues
-Ran chkdsk
WhoCrashed Logs:
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sat 2/13/2021 11:07:14 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021421-7593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF800192E8616, 0xFFFF8108263FF8C0, 0x5A)
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 Fri 2/12/2021 11:40:22 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!HvlPerformEndOfInterrupt+0x4DEE)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8003C269336, 0xFFFF928E16C7E140, 0x5A)
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 Sat 2/13/2021 10:57:13 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-18828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8064E4F9616, 0xFFFFD98F0C2FE780, 0x5A)
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 Fri 2/12/2021 11:40:22 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021221-7218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8003C269336, 0xFFFF928E16C7E140, 0x5A)
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 Fri 2/12/2021 11:36:35 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021221-8328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF80258E69336, 0xFFFF8C8CFCEFF470, 0x5A)
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 Fri 2/12/2021 11:30:10 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021221-5359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8055BC69336, 0xFFFFAE82C12F7D40, 0x5A)
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.
System Specs:
It's an old rig:
Continue reading...
Symptoms - after Win10 update last week, computer will boot in to Windows and crash sometimes immediately and sometimes after 10-20 minutes, each time throwing same BSOD code KMODE_EXCEPTION_NOT_HANDLED.
Attempted troubleshooting:
-Attempted system restore to prior to update, attempted to uninstall last known updates
-Attempted brand new Windows 10 install on TWO different and formatted known working SSD's
-Total of two x 4GB RAM sticks- attempted to reseat and remove one to isolate if there was a bad player
-All drivers updated
-Ran Memory Diagnostic Tool; test came back successful with no found issues
-Ran Driver Verifier to stress test all non-microsoft related drivers; didn't point to any new issues in crash log besides the same ones shared below (primarily ntoskrnl.exe)
-Ran sfc /scannow; system file checker came back successful with no found issues
-Ran chkdsk
WhoCrashed Logs:
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sat 2/13/2021 11:07:14 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021421-7593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF800192E8616, 0xFFFF8108263FF8C0, 0x5A)
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 Fri 2/12/2021 11:40:22 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!HvlPerformEndOfInterrupt+0x4DEE)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8003C269336, 0xFFFF928E16C7E140, 0x5A)
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 Sat 2/13/2021 10:57:13 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-18828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8064E4F9616, 0xFFFFD98F0C2FE780, 0x5A)
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 Fri 2/12/2021 11:40:22 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021221-7218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8003C269336, 0xFFFF928E16C7E140, 0x5A)
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 Fri 2/12/2021 11:36:35 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021221-8328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF80258E69336, 0xFFFF8C8CFCEFF470, 0x5A)
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 Fri 2/12/2021 11:30:10 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021221-5359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8055BC69336, 0xFFFFAE82C12F7D40, 0x5A)
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.
System Specs:
It's an old rig:
Asrock P67 Extreme 4
Intel i5-2500k
MSI Nvidia GeForce GT1030
2x4GB G.SKILL DDR3 1600
250GB WD Blue SSD Drive (fresh install)
64GB Crucial M4 SSD (second test fresh install)
Continue reading...