J
jake2021
Hi there,
Have been struggling with this problem for months now. At random intervals (sometimes days, sometimes minutes) I get a selection of BSoDs. Uusally IRQL Not less or equal but there are a few it could be, not just a single error. Sometimes it's talking about trying to access memory that isn't available or something - sorry I don't have all of the codes listed..
Minidumps here: minidumps
Interestingly the most recent BSoD doesn't seem to have created a minidump - not sure if that's important
WhoCrashed tells me:
On Sat 23/01/2021 15:01:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012321-11031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF804160973E9)
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 Sat 23/01/2021 15:01:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8299)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF804160973E9)
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 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 Sat 23/01/2021 14:49:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012321-10734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x139 (0x4, 0xFFFF9A001F3FE010, 0xFFFF9A001F3FDF68, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 14/01/2021 19:36:19 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011421-14296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x139 (0x3, 0xFFFFF68E9B317380, 0xFFFFF68E9B3172D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 09/11/2020 14:03:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110920-14281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0xA (0xFFFFC08000011958, 0x2, 0x1, 0xFFFFF8016C1EEBC3)
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 09/11/2020 13:45:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110920-10421-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80049B244E4, 0xFFFFF201E4EBA748, 0xFFFFF201E4EB9F80)
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
I have formatted and reinstalled numerous times. I have run memtest (and the other recommended memory testing tools) and not had any issues. I have tried 3 power supplies and currently running a fairly high quality Corsair PSU so I really do not believe it is PSU related. Potentially it could be related to my GPU but I did purchase a cheap alternative to test and if memory serves I still had issues (otherwise I would have purchased a new card at the time).
Would love to get some help on this as I've reached my limit of troubleshooting.
Thanks a lot.
Continue reading...
Have been struggling with this problem for months now. At random intervals (sometimes days, sometimes minutes) I get a selection of BSoDs. Uusally IRQL Not less or equal but there are a few it could be, not just a single error. Sometimes it's talking about trying to access memory that isn't available or something - sorry I don't have all of the codes listed..
Minidumps here: minidumps
Interestingly the most recent BSoD doesn't seem to have created a minidump - not sure if that's important
WhoCrashed tells me:
On Sat 23/01/2021 15:01:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012321-11031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF804160973E9)
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 Sat 23/01/2021 15:01:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8299)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF804160973E9)
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 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 Sat 23/01/2021 14:49:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012321-10734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x139 (0x4, 0xFFFF9A001F3FE010, 0xFFFF9A001F3FDF68, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 14/01/2021 19:36:19 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011421-14296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x139 (0x3, 0xFFFFF68E9B317380, 0xFFFFF68E9B3172D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 09/11/2020 14:03:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110920-14281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0xA (0xFFFFC08000011958, 0x2, 0x1, 0xFFFFF8016C1EEBC3)
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 09/11/2020 13:45:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110920-10421-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80049B244E4, 0xFFFFF201E4EBA748, 0xFFFFF201E4EB9F80)
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
I have formatted and reinstalled numerous times. I have run memtest (and the other recommended memory testing tools) and not had any issues. I have tried 3 power supplies and currently running a fairly high quality Corsair PSU so I really do not believe it is PSU related. Potentially it could be related to my GPU but I did purchase a cheap alternative to test and if memory serves I still had issues (otherwise I would have purchased a new card at the time).
Would love to get some help on this as I've reached my limit of troubleshooting.
Thanks a lot.
Continue reading...