- Nov 7, 2013
- 12
- 0
- 10,510
Hey Everyone,
For the longest time I have had my computer hard reboot at certain times, typically during gaming sessions. I have already ruled out that its an overheating situation and was hoping someone with experience reading minidump files can give me some insight into what exactly is causing the problem for me. Thanks in advance!
https://drive.google.com/open?id=0B3RWhe9je1RsbHBVLV9vNWpVRGc
https://drive.google.com/open?id=0B3RWhe9je1RsU19NNm1ZanVVS1k
https://drive.google.com/open?id=0B3RWhe9je1RsT2U1M21tXzRzV2M
https://drive.google.com/open?id=0B3RWhe9je1Rsel9SWHo3V0pzaE0
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 10/22/2016 8:50:43 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102216-5781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0xFFFFA58C68234DD0, 0xFF, 0x0, 0xFFFFF8024FC54C38)
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 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 Fri 10/21/2016 4:12:31 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102116-5968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0xFFFFD8898CE33190, 0xFF, 0x0, 0xFFFFF8025904FC38)
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 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 Fri 10/21/2016 7:19:44 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102116-6031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0xFFFFDD0122813580, 0xFF, 0x0, 0xFFFFF800CE452C38)
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 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 10/19/2016 7:56:13 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101916-8390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0xFFFFDA0C87084A60, 0xFF, 0x0, 0xFFFFF800533E7C38)
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 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.
For the longest time I have had my computer hard reboot at certain times, typically during gaming sessions. I have already ruled out that its an overheating situation and was hoping someone with experience reading minidump files can give me some insight into what exactly is causing the problem for me. Thanks in advance!
https://drive.google.com/open?id=0B3RWhe9je1RsbHBVLV9vNWpVRGc
https://drive.google.com/open?id=0B3RWhe9je1RsU19NNm1ZanVVS1k
https://drive.google.com/open?id=0B3RWhe9je1RsT2U1M21tXzRzV2M
https://drive.google.com/open?id=0B3RWhe9je1Rsel9SWHo3V0pzaE0
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 10/22/2016 8:50:43 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102216-5781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0xFFFFA58C68234DD0, 0xFF, 0x0, 0xFFFFF8024FC54C38)
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 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 Fri 10/21/2016 4:12:31 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102116-5968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0xFFFFD8898CE33190, 0xFF, 0x0, 0xFFFFF8025904FC38)
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 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 Fri 10/21/2016 7:19:44 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102116-6031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0xFFFFDD0122813580, 0xFF, 0x0, 0xFFFFF800CE452C38)
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 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 10/19/2016 7:56:13 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101916-8390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0xFFFFDA0C87084A60, 0xFF, 0x0, 0xFFFFF800533E7C38)
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 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.
Facebook
Twitter
Instagram