F
FemiFel
Guest
I've been having the issue the past few days of windows 10 blue screening with different errors multiple times a day. I have tried many different approaches to debugging it and have not found a solution. I have updated and reinstalled various drivers. The computer is relatively new (<6 months old).
Minidump zip
From WhoCrashed's analysis:
System Information (local)
[COLOR=rgba(17, 17, 17, 1)]Computer name: DESKTOP-J05QUH6
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\Windows
Hardware: ASUS, ASUSTeK COMPUTER INC., PRIME Z490-V
CPU: GenuineIntel Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz 8664, level: 6
16 logical processors, active mask: 65535
RAM: 34242936832 bytes (31.9GB)
[/COLOR]
Crash Dump Analysis
[COLOR=rgba(17, 17, 17, 1)]Crash dumps are enabled on your computer. [/COLOR]
[COLOR=rgba(17, 17, 17, 1)]Crash dump directories: [/COLOR]
[COLOR=rgba(17, 17, 17, 1)]C:\Windows[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]C:\Windows\Minidump[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]On Tue 3/16/2021 11:07:45 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]ntkrnlmp.exe[/COLOR] (nt!setjmpex+0x81C9)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF8046E3FD10C, 0xFFFFC7010B546920, 0x0)
Error: [COLOR=rgba(17, 17, 17, 1)]SYSTEM_SERVICE_EXCEPTION[/COLOR]
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.
[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]On Tue 3/16/2021 2:16:04 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031621-4640-01.dmp
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]ntoskrnl.exe[/COLOR] (nt+0x3F5C50)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803059FD022, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [COLOR=rgba(17, 17, 17, 1)]KMODE_EXCEPTION_NOT_HANDLED[/COLOR]
file path: C:\Windows\system32\ntoskrnl.exe
product: [COLOR=rgba(17, 17, 17, 1)]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba(17, 17, 17, 1)]Microsoft Corporation[/COLOR]
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.
[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]On Tue 3/16/2021 1:37:47 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031621-4687-01.dmp
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]ndis.sys[/COLOR] (0xFFFFF8046A0DDE27)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8046A0DDE27, 0xFFFFAC083BF9F2E8, 0xFFFFDB80F5346920)
Error: [COLOR=rgba(17, 17, 17, 1)]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/COLOR]
file path: C:\Windows\system32\drivers\ndis.sys
product: [COLOR=rgba(17, 17, 17, 1)]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba(17, 17, 17, 1)]Microsoft Corporation[/COLOR]
description: Network Driver Interface Specification (NDIS)
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 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.
[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]On Tue 3/16/2021 11:07:02 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031621-4609-01.dmp
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]intelppm.sys[/COLOR] (0xFFFFF801395944E0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801395944E0, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [COLOR=rgba(17, 17, 17, 1)]KMODE_EXCEPTION_NOT_HANDLED[/COLOR]
file path: C:\Windows\system32\drivers\intelppm.sys
product: [COLOR=rgba(17, 17, 17, 1)]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba(17, 17, 17, 1)]Microsoft Corporation[/COLOR]
description: Processor Device Driver
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 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.
[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]On Tue 3/16/2021 11:07:45 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031621-4609-02.dmp
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]ntoskrnl.exe[/COLOR] (nt+0x3F5C50)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF8046E3FD10C, 0xFFFFC7010B546920, 0x0)
Error: [COLOR=rgba(17, 17, 17, 1)]SYSTEM_SERVICE_EXCEPTION[/COLOR]
file path: C:\Windows\system32\ntoskrnl.exe
product: [COLOR=rgba(17, 17, 17, 1)]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba(17, 17, 17, 1)]Microsoft Corporation[/COLOR]
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.
[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]On Mon 3/15/2021 10:46:13 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031521-5093-01.dmp
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]netio.sys[/COLOR] (0xFFFFF8033C0110A6)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8033C0110A6, 0xFFFFB5089438DDD8, 0xFFFFF8033C883920)
Error: [COLOR=rgba(17, 17, 17, 1)]KMODE_EXCEPTION_NOT_HANDLED[/COLOR]
file path: C:\Windows\system32\drivers\netio.sys
product: [COLOR=rgba(17, 17, 17, 1)]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba(17, 17, 17, 1)]Microsoft Corporation[/COLOR]
description: Network I/O Subsystem
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 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.
[/COLOR]
Conclusion
[COLOR=rgba(17, 17, 17, 1)]6 crash dumps have been found and analyzed. No offending third party drivers have been found.[/COLOR]
Continue reading...
Minidump zip
From WhoCrashed's analysis:
System Information (local)
[COLOR=rgba(17, 17, 17, 1)]Computer name: DESKTOP-J05QUH6
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\Windows
Hardware: ASUS, ASUSTeK COMPUTER INC., PRIME Z490-V
CPU: GenuineIntel Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz 8664, level: 6
16 logical processors, active mask: 65535
RAM: 34242936832 bytes (31.9GB)
[/COLOR]
Crash Dump Analysis
[COLOR=rgba(17, 17, 17, 1)]Crash dumps are enabled on your computer. [/COLOR]
[COLOR=rgba(17, 17, 17, 1)]Crash dump directories: [/COLOR]
[COLOR=rgba(17, 17, 17, 1)]C:\Windows[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]C:\Windows\Minidump[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]On Tue 3/16/2021 11:07:45 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]ntkrnlmp.exe[/COLOR] (nt!setjmpex+0x81C9)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF8046E3FD10C, 0xFFFFC7010B546920, 0x0)
Error: [COLOR=rgba(17, 17, 17, 1)]SYSTEM_SERVICE_EXCEPTION[/COLOR]
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.
[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]On Tue 3/16/2021 2:16:04 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031621-4640-01.dmp
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]ntoskrnl.exe[/COLOR] (nt+0x3F5C50)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803059FD022, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [COLOR=rgba(17, 17, 17, 1)]KMODE_EXCEPTION_NOT_HANDLED[/COLOR]
file path: C:\Windows\system32\ntoskrnl.exe
product: [COLOR=rgba(17, 17, 17, 1)]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba(17, 17, 17, 1)]Microsoft Corporation[/COLOR]
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.
[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]On Tue 3/16/2021 1:37:47 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031621-4687-01.dmp
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]ndis.sys[/COLOR] (0xFFFFF8046A0DDE27)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8046A0DDE27, 0xFFFFAC083BF9F2E8, 0xFFFFDB80F5346920)
Error: [COLOR=rgba(17, 17, 17, 1)]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/COLOR]
file path: C:\Windows\system32\drivers\ndis.sys
product: [COLOR=rgba(17, 17, 17, 1)]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba(17, 17, 17, 1)]Microsoft Corporation[/COLOR]
description: Network Driver Interface Specification (NDIS)
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 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.
[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]On Tue 3/16/2021 11:07:02 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031621-4609-01.dmp
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]intelppm.sys[/COLOR] (0xFFFFF801395944E0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801395944E0, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [COLOR=rgba(17, 17, 17, 1)]KMODE_EXCEPTION_NOT_HANDLED[/COLOR]
file path: C:\Windows\system32\drivers\intelppm.sys
product: [COLOR=rgba(17, 17, 17, 1)]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba(17, 17, 17, 1)]Microsoft Corporation[/COLOR]
description: Processor Device Driver
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 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.
[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]On Tue 3/16/2021 11:07:45 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031621-4609-02.dmp
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]ntoskrnl.exe[/COLOR] (nt+0x3F5C50)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF8046E3FD10C, 0xFFFFC7010B546920, 0x0)
Error: [COLOR=rgba(17, 17, 17, 1)]SYSTEM_SERVICE_EXCEPTION[/COLOR]
file path: C:\Windows\system32\ntoskrnl.exe
product: [COLOR=rgba(17, 17, 17, 1)]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba(17, 17, 17, 1)]Microsoft Corporation[/COLOR]
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.
[/COLOR]
[COLOR=rgba(17, 17, 17, 1)]On Mon 3/15/2021 10:46:13 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031521-5093-01.dmp
This was probably caused by the following module: [COLOR=rgba(17, 17, 17, 1)]netio.sys[/COLOR] (0xFFFFF8033C0110A6)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8033C0110A6, 0xFFFFB5089438DDD8, 0xFFFFF8033C883920)
Error: [COLOR=rgba(17, 17, 17, 1)]KMODE_EXCEPTION_NOT_HANDLED[/COLOR]
file path: C:\Windows\system32\drivers\netio.sys
product: [COLOR=rgba(17, 17, 17, 1)]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba(17, 17, 17, 1)]Microsoft Corporation[/COLOR]
description: Network I/O Subsystem
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 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.
[/COLOR]
Conclusion
[COLOR=rgba(17, 17, 17, 1)]6 crash dumps have been found and analyzed. No offending third party drivers have been found.[/COLOR]
Continue reading...