- Jun 12, 2017
- 2
- 0
- 510
For the past few days my computer keeps crashing and giving me errors, "IRQL NOT LESS OR EQUAL," and "UNEXPECTED KERNEL MODE TRAP." I went into my system and updated my drivers through windows and my PC still crashes. I did some research and downloaded WhoCrashed. I ran an analysis and got these results:
System Information (local)
________________________________________
Computer name: DESKTOP-O158C78
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH Z170 S
CPU: GenuineIntel Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17091231744 bytes total
________________________________________
Crash Dump Analysis
________________________________________
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 6/12/2017 2:30:46 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\061217-4531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xA (0x89F5575603, 0x2, 0x1, 0xFFFFF80267AF6A7A)
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 Mon 6/12/2017 2:30:46 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: 0xA (0x89F5575603, 0x2, 0x1, 0xFFFFF80267AF6A7A)
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 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 Sun 6/11/2017 10:02:43 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\061117-14171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xA (0xFFFFC9058A61D410, 0x2, 0x1, 0xFFFFF803B7ABA6BC)
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 6/10/2017 5:07:41 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\061017-5531-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x7F (0x8, 0xFFFFF802601BCE70, 0x0, 0xFFFFF8025DDCC3F8)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 6/10/2017 4:34:32 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\061017-5531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xA (0x10796E88, 0x2, 0x1, 0xFFFFF80021914E54)
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.
________________________________________
Conclusion
________________________________________
8 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
I am not a tech pro so I don't know what to do to solve these crashes....PLEASE HELP!!
ChrisH6693
*update* I ran a memory check and it says my memory is working fine.
System Information (local)
________________________________________
Computer name: DESKTOP-O158C78
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH Z170 S
CPU: GenuineIntel Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17091231744 bytes total
________________________________________
Crash Dump Analysis
________________________________________
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 6/12/2017 2:30:46 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\061217-4531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xA (0x89F5575603, 0x2, 0x1, 0xFFFFF80267AF6A7A)
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 Mon 6/12/2017 2:30:46 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: 0xA (0x89F5575603, 0x2, 0x1, 0xFFFFF80267AF6A7A)
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 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 Sun 6/11/2017 10:02:43 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\061117-14171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xA (0xFFFFC9058A61D410, 0x2, 0x1, 0xFFFFF803B7ABA6BC)
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 6/10/2017 5:07:41 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\061017-5531-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x7F (0x8, 0xFFFFF802601BCE70, 0x0, 0xFFFFF8025DDCC3F8)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 6/10/2017 4:34:32 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\061017-5531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xA (0x10796E88, 0x2, 0x1, 0xFFFFF80021914E54)
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.
________________________________________
Conclusion
________________________________________
8 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
I am not a tech pro so I don't know what to do to solve these crashes....PLEASE HELP!!
ChrisH6693
*update* I ran a memory check and it says my memory is working fine.
Facebook
Twitter
Instagram