I have a windows 10 installs that was upgraded from a windows 7 install. I think i have uninstalled all of the windows 7 drivers at this point. Basically i am getting a couple errors. I will attach my mini dump files to see if that might help. I thought i had fixed this about a month ago by updating the bios on my motherboard.
I have a AMD FX 8350 processor (8 core)
Sabertooth 990FX gen 2.0
MSI Geforce GTX1070
Mini Dump analysis with WhoCrashed:
On Thu 10/20/2016 5:37:38 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\102016-11984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFCB81B7C80180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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 Thu 10/20/2016 1:20:52 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\102016-12625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF802F78AF59A)
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 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 10/15/2016 6:56:44 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\101516-17890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xD1 (0xFFFFDA8C07120080, 0xFF, 0xE8, 0xFFFFDA8C07120080)
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.
I have a AMD FX 8350 processor (8 core)
Sabertooth 990FX gen 2.0
MSI Geforce GTX1070
Mini Dump analysis with WhoCrashed:
On Thu 10/20/2016 5:37:38 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\102016-11984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFCB81B7C80180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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 Thu 10/20/2016 1:20:52 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\102016-12625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF802F78AF59A)
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 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 10/15/2016 6:56:44 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\101516-17890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xD1 (0xFFFFDA8C07120080, 0xFF, 0xE8, 0xFFFFDA8C07120080)
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.
Facebook
Twitter
Instagram