R
Rayblanc
This has been a problem since I first bought the computer, new. I've tried updating the drivers, doing a factory reset, installing a new hard drive, and
installing new ram. The problem doesn't go away. Here's the most recent crash dumps. The problem seems to occur at random.
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-N8QN1UF
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\Windows
Hardware: Aspire E5-576, Acer, KBL, Ironman_SK
CPU: GenuineIntel Intel(R) Core(TM) i3-8130U CPU @ 2.20GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 17051127808 bytes (15.9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sat 6/13/2020 7:29:37 PM 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+0x81C9)
Bugcheck code: 0xA (0xFFFFDE6F46DCE398, 0x2, 0x0, 0xFFFFF8067225F2C4)
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 6/13/2020 6:44:53 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061320-5953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0)
Bugcheck code: 0xA (0xFFFF810BE0E37B70, 0x2, 0x0, 0xFFFFF8054D059F00)
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 6/13/2020 7:29:37 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061320-5578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0)
Bugcheck code: 0xA (0xFFFFDE6F46DCE398, 0x2, 0x0, 0xFFFFF8067225F2C4)
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 Wed 6/10/2020 9:42:13 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061020-8546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0xFFFFBC076997EA78, 0x2, 0x0, 0xFFFFF807644C9012)
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 Tue 6/9/2020 8:37:18 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060920-6968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x154 (0xFFFFA80A10770000, 0xFFFFFB8E9F306520, 0x1, 0x0)
Error: UNEXPECTED_STORE_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 the store component caught an unexpected exception.
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.
Continue reading...
installing new ram. The problem doesn't go away. Here's the most recent crash dumps. The problem seems to occur at random.
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-N8QN1UF
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\Windows
Hardware: Aspire E5-576, Acer, KBL, Ironman_SK
CPU: GenuineIntel Intel(R) Core(TM) i3-8130U CPU @ 2.20GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 17051127808 bytes (15.9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sat 6/13/2020 7:29:37 PM 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+0x81C9)
Bugcheck code: 0xA (0xFFFFDE6F46DCE398, 0x2, 0x0, 0xFFFFF8067225F2C4)
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 6/13/2020 6:44:53 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061320-5953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0)
Bugcheck code: 0xA (0xFFFF810BE0E37B70, 0x2, 0x0, 0xFFFFF8054D059F00)
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 6/13/2020 7:29:37 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061320-5578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0)
Bugcheck code: 0xA (0xFFFFDE6F46DCE398, 0x2, 0x0, 0xFFFFF8067225F2C4)
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 Wed 6/10/2020 9:42:13 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061020-8546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0xFFFFBC076997EA78, 0x2, 0x0, 0xFFFFF807644C9012)
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 Tue 6/9/2020 8:37:18 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060920-6968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x154 (0xFFFFA80A10770000, 0xFFFFFB8E9F306520, 0x1, 0x0)
Error: UNEXPECTED_STORE_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 the store component caught an unexpected exception.
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.
Continue reading...