Numerous and inconsistent BSOD errors

[Josh_134]

Hello,

over the last month or so I've had a number of random BSOD errors. The most common errors I get are bad_pool_header, kernel_security_check_error and the most common being memory management.

To fix this issue I had re-installed windows, updated all of my drivers, run memory diagnostics on windows 10 and have removed and re-plugged in my graphics card and ram.

I'm semi-computer literate but I just don't know what to do now. The error primarily happens when in a game like Overwatch or Dota however it occasionally happens when not in-game.

My specs are:
i5-6400
nvidia gtx 970
8 gig ddr4 ram


Any help would be hugely appreciated. Thank you all very much.

 

[Colif]

download and run who crashed: http://www.resplendence.com/whocrashed
it looks at errors and might show us the cause

Copy/paste results in here.

 

[Josh_134]

I downloaded and ran whocrashed. The problem it said at the end is my graphics card driver, of which I only updated today AFTER the crashes. It did not fix the issue

Information as follows:

Computer name: DESKTOP-OKRP7Q0
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: MS-7982, MSI, B150M BAZOOKA (MS-7982)
CPU: GenuineIntel Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8551030784 bytes total


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 6/08/2016 9:54:14 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080616-4890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x19 (0x3, 0xFFFFE000F6ECE010, 0xFFFFE000F6E8E010, 0xFFFFE000F6ECE010)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Sat 6/08/2016 9:54:14 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ahcache.sys (ahcache+0x13FE3)
Bugcheck code: 0x19 (0x3, 0xFFFFE000F6ECE010, 0xFFFFE000F6E8E010, 0xFFFFE000F6ECE010)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\ahcache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Application Compatibility Cache
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 a standard 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.



On Sat 6/08/2016 9:53:20 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080616-4765-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x139 (0x3, 0xFFFFD000214BD210, 0xFFFFD000214BD168, 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 Sat 6/08/2016 9:08:41 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080616-4765-02.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xBA86F3)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000BD086F3, 0xFFFFD00020C1C5D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 368.81
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 368.81
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 368.81 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION



On Sat 6/08/2016 8:01:34 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080616-5296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1A (0x41792, 0xFFFFF680002F3280, 0x40000, 0x0)
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.
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/08/2016 6:51:48 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080616-4750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x50 (0xFFFFF68000000200, 0x0, 0x0, 0x6)
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 6/08/2016 4:30:05 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080616-4765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x19 (0x20, 0xFFFFE0011C1892A0, 0xFFFFE0011C1893F0, 0x4150008)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Fri 5/08/2016 4:55:31 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080516-5062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x4E (0x2, 0x19BA59, 0x26EFFF, 0x1)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
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 4/08/2016 5:58:48 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080416-4859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Wed 3/08/2016 9:34:29 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080316-5703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1A (0x5003, 0xFFFFF58010804000, 0x50366, 0x4FF6600E06CC)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

20 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 368.81 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

 

[Colif]

If you have all the drivers from MSI then the next step is a more comprehensive dump

follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidumps
copy that file to documents
upload the copy from documents to a cloud server and share link here

someone who can read them will help you more