- Feb 25, 2017
- 16
- 0
- 510
I recently upgraded from Win7 to Win10, I completely formatted my one section of HDD but I left the other out because it was full of games and files I didn't have the luxury to backup at the time.
These BSODs occur every time I boot up my computer and run any game, after 10-15 minutes of gaming it gives me a BSOD, and after the restart it never has any problems again for as long as the computer is still on. If I shut down and power on again, it still gives a BSOD after 10-15 minutes of gaming.
My specs are as follows;
i3-6100
8 GB DDR4 RAM
GIGABYTE H110M-S2
ASUS GTX1060 6GB
650W PSU (built-in one with my Zalman Z3 Plus)
My last 5 crash reports from WhoCrashed;
Using Bluescreenviewer I noticed that the faulty filename is always ntoskrnl.exe, and its variants are including but not limited to +55a0a, +179bba, +179d85, +159929, +5cd94, +8b182, +35070, +351de and so on.
My bug checks are mostly MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA, but I also get SYSTEM_SERVICE_EXCEPTION and DRIVER_IRQL_NOT_LESS_OR_EQUAL.
I can provide more information if necessary.
These BSODs occur every time I boot up my computer and run any game, after 10-15 minutes of gaming it gives me a BSOD, and after the restart it never has any problems again for as long as the computer is still on. If I shut down and power on again, it still gives a BSOD after 10-15 minutes of gaming.
My specs are as follows;
i3-6100
8 GB DDR4 RAM
GIGABYTE H110M-S2
ASUS GTX1060 6GB
650W PSU (built-in one with my Zalman Z3 Plus)
My last 5 crash reports from WhoCrashed;
On Fri 31.03.2017 01:46:35 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFE20010804310)
Bugcheck code: 0x1A (0x41284, 0xAF8000, 0x2C92, 0xFFFFE20010804310)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query: MEMORY_MANAGEMENT
On Tue 28.03.2017 01:41:58 your computer crashed
crash dump file: C:\WINDOWS\Minidump\032817-19156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x61941, 0x233105020C8, 0xD, 0xFFFFE48062A7BA80)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
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 27.03.2017 16:47:03 your computer crashed
crash dump file: C:\WINDOWS\Minidump\032717-18671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x50 (0xFFFFA981E0E13348, 0x0, 0xFFFFF803D86D7714, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sun 26.03.2017 16:38:21 your computer crashed
crash dump file: C:\WINDOWS\Minidump\032617-21921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x50 (0xFFFFA96000B87C48, 0x0, 0xFFFFF8038C8D653C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sat 25.03.2017 13:49:29 your computer crashed
crash dump file: C:\WINDOWS\Minidump\032517-22781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x139 (0x3, 0xFFFFA3802851D3E0, 0xFFFFA3802851D338, 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.
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFE20010804310)
Bugcheck code: 0x1A (0x41284, 0xAF8000, 0x2C92, 0xFFFFE20010804310)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query: MEMORY_MANAGEMENT
On Tue 28.03.2017 01:41:58 your computer crashed
crash dump file: C:\WINDOWS\Minidump\032817-19156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x61941, 0x233105020C8, 0xD, 0xFFFFE48062A7BA80)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
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 27.03.2017 16:47:03 your computer crashed
crash dump file: C:\WINDOWS\Minidump\032717-18671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x50 (0xFFFFA981E0E13348, 0x0, 0xFFFFF803D86D7714, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sun 26.03.2017 16:38:21 your computer crashed
crash dump file: C:\WINDOWS\Minidump\032617-21921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x50 (0xFFFFA96000B87C48, 0x0, 0xFFFFF8038C8D653C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sat 25.03.2017 13:49:29 your computer crashed
crash dump file: C:\WINDOWS\Minidump\032517-22781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x139 (0x3, 0xFFFFA3802851D3E0, 0xFFFFA3802851D338, 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.
Using Bluescreenviewer I noticed that the faulty filename is always ntoskrnl.exe, and its variants are including but not limited to +55a0a, +179bba, +179d85, +159929, +5cd94, +8b182, +35070, +351de and so on.
My bug checks are mostly MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA, but I also get SYSTEM_SERVICE_EXCEPTION and DRIVER_IRQL_NOT_LESS_OR_EQUAL.
I can provide more information if necessary.
Facebook
Twitter
Instagram