- Feb 18, 2015
- 8
- 0
- 4,510
Here's my WhoCrashed log. Any help?
System Information (local)
Computer name: DESKTOP-UL07TQ2
Windows version: Windows 10 , 10.0, version 1511, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., PRIME A320M-K
CPU: AuthenticAMD AMD Ryzen 5 3600 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17113505792 bytes (15.9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Wed 7/31/2019 3:31:45 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-5828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142900)
Bugcheck code: 0xD1 (0x1, 0x2, 0x8, 0x1)
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 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 Wed 7/31/2019 3:31:45 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32kfull.sys (win32kfull!NtUserSetTimer+0x4D2)
Bugcheck code: 0xD1 (0x1, 0x2, 0x8, 0x1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 7/31/2019 3:29:18 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-5546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142900)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8020EDC4157, 0xFFFFD001FB6E9F80, 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.
On Wed 7/31/2019 2:50:36 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-5562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142900)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8018EDE689F, 0xFFFFD00021D3BC10, 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.
On Wed 7/31/2019 2:42:00 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-5906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1 (0x7FF85CA346C4, 0x0, 0xFFFF0000, 0xFFFFD00155A13B80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 Wed 7/31/2019 2:33:33 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-6093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803D9B4D7EA, 0xFFFFD0008F118CB0, 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.
On Wed 7/31/2019 2:30:47 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-6156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1 (0x7FFF0A874D04, 0x0, 0x1, 0xFFFFD0002395EB80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 Wed 7/31/2019 2:16:16 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-3671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xF7 (0x16903ED261AA, 0x16903ED2602A, 0xFFFFE96FC12D9FD5, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
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. 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.
System Information (local)
Computer name: DESKTOP-UL07TQ2
Windows version: Windows 10 , 10.0, version 1511, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., PRIME A320M-K
CPU: AuthenticAMD AMD Ryzen 5 3600 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17113505792 bytes (15.9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Wed 7/31/2019 3:31:45 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-5828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142900)
Bugcheck code: 0xD1 (0x1, 0x2, 0x8, 0x1)
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 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 Wed 7/31/2019 3:31:45 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32kfull.sys (win32kfull!NtUserSetTimer+0x4D2)
Bugcheck code: 0xD1 (0x1, 0x2, 0x8, 0x1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 7/31/2019 3:29:18 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-5546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142900)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8020EDC4157, 0xFFFFD001FB6E9F80, 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.
On Wed 7/31/2019 2:50:36 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-5562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142900)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8018EDE689F, 0xFFFFD00021D3BC10, 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.
On Wed 7/31/2019 2:42:00 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-5906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1 (0x7FF85CA346C4, 0x0, 0xFFFF0000, 0xFFFFD00155A13B80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 Wed 7/31/2019 2:33:33 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-6093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803D9B4D7EA, 0xFFFFD0008F118CB0, 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.
On Wed 7/31/2019 2:30:47 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-6156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1 (0x7FFF0A874D04, 0x0, 0x1, 0xFFFFD0002395EB80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 Wed 7/31/2019 2:16:16 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073119-3671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xF7 (0x16903ED261AA, 0x16903ED2602A, 0xFFFFE96FC12D9FD5, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
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. 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.
Last edited by a moderator:
Facebook
Twitter
Instagram