C
Chemfu
Hello,
I have multiple BSOD that are completely random in time (I can get one in a month, several in a week, etc.). Here is the .log in my WhoCrashed so you can see my problem:
On Thu 29/10/2020 12:39:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102920-5515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
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 Sun 25/10/2020 16:56:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102520-5296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0xA (0x1, 0x2, 0x0, 0xFFFFF801736E231E)
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 is a software bug.
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 Mon 19/10/2020 19:40:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101920-5953-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8017F66BB49, 0xFFFFF30D49AE74A8, 0xFFFFF30D49AE6CE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Mon 14/09/2020 23:22:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\091420-6296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80340AE0170, 0x0, 0x1)
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 Sat 22/08/2020 17:42:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082220-6312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801718FAFBE, 0x0, 0xFFFFFFFFFFFFFFFF)
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 Sat 18/07/2020 21:22:40 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: win32kbase.sys (0xFFFFD8D69F2BCAE5)
Bugcheck code: 0x7F (0x8, 0xFFFFC681B753D030, 0x0, 0xFFFFD8D69F2BCAE5)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\win32kbase.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador de kernel Win32 básico
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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.
Also, I'll include a .zip with the Mini-dump files if needed.
Files
I am at a complete loss as to what could be causing this, it's a different reason every single time, I have also used driver verifier on multiple occasions as well, I have tested my ram, have tested my hard drive, have tested my temps, everything seems to be working perfectly fine from a hardware perspective.
Thanks in advance. Regards.
Continue reading...
I have multiple BSOD that are completely random in time (I can get one in a month, several in a week, etc.). Here is the .log in my WhoCrashed so you can see my problem:
On Thu 29/10/2020 12:39:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102920-5515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
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 Sun 25/10/2020 16:56:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102520-5296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0xA (0x1, 0x2, 0x0, 0xFFFFF801736E231E)
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 is a software bug.
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 Mon 19/10/2020 19:40:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101920-5953-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8017F66BB49, 0xFFFFF30D49AE74A8, 0xFFFFF30D49AE6CE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Mon 14/09/2020 23:22:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\091420-6296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80340AE0170, 0x0, 0x1)
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 Sat 22/08/2020 17:42:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082220-6312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDF40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801718FAFBE, 0x0, 0xFFFFFFFFFFFFFFFF)
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 Sat 18/07/2020 21:22:40 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: win32kbase.sys (0xFFFFD8D69F2BCAE5)
Bugcheck code: 0x7F (0x8, 0xFFFFC681B753D030, 0x0, 0xFFFFD8D69F2BCAE5)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\win32kbase.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador de kernel Win32 básico
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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.
Also, I'll include a .zip with the Mini-dump files if needed.
Files
I am at a complete loss as to what could be causing this, it's a different reason every single time, I have also used driver verifier on multiple occasions as well, I have tested my ram, have tested my hard drive, have tested my temps, everything seems to be working perfectly fine from a hardware perspective.
Thanks in advance. Regards.
Continue reading...