ntoskrnl.exe/BAD_Pool_Header/BSOD

[douglas9x]

Wasn't doing anything unusal nor have i added any hardware or updated windows recently. Had two browsers open(Opera 12.4/Vivaldi) and Winamp when i got the dreaded BSOD(below) Suspect a driver....any input appreciated. Thanks in advance.

------------------------------------------------------------------------------
A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

BAD_POOL_HEADER

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000019 (0x0000000000000003, 0xfffff8000361a940, 0x0000000000000000,
0xfffff8000361a940)

*** ntoskrnl.exe - Address 0xfffff80003487180 base at 0xfffff80003417000 DateStamp
0x57c9932e

 

[douglas9x]

ntoskrnl.exe/BAD_Pool_Header/BSOD/Additional Details

Failed to mention in first post that this was the second BDOD after another on 1.29.17. Have posted both BSOD details here to provide additional infor to help diagnose the problem.....It would appear the same culprit is involved in both incidents. Just can't figure out which driver is causing the problem if that is the case. TIA



-----------------------------------------------------------------------------------------------------------------------------
4.21.17 BSOD:

Dump File : 042117-12604-01.dmp
Crash Time : 4/21/2017 7:40:22 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffff800`0361a940
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`0361a940
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70180
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.23539 (win7sp1_ldr.160902-0600)
Processor : x64
Crash Address : ntoskrnl.exe+70180
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042117-12604-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 280,408
Dump File Time : 4/21/2017 7:41:25 AM

----------------------------------------------------------------------------------------------------------
1.29.17 BSOD
==================================================

Dump File : 012917-12963-01.dmp
Crash Time : 1/29/2017 7:18:19 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffff800`0365b940
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`0365b940
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70180
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.23539 (win7sp1_ldr.160902-0600)
Processor : x64
Crash Address : ntoskrnl.exe+70180
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012917-12963-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 280,408
Dump File Time : 1/29/2017 7:19:12 AM
==================================================

 

[axe0]

Upload a new zip.

 

[douglas9x]

Updated zip file

As per request updated zip file 4.23.17

 

[axe0]

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[douglas9x]

Just before i was going to reply to your response got another crash....with the crash details below:
Dump File : 042417-13322-01.dmp
Crash Time : 4/24/2017 7:13:33 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffff800`03655940
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`03655940
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70180
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.23539 (win7sp1_ldr.160902-0600)
Processor : x64
Crash Address : ntoskrnl.exe+70180
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042417-13322-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 280,408
Dump File Time : 4/24/2017 7:14:21 AM
==================================================

Could you please do me a favor and recheck the new crash results...the reason being a bit hesitant to go the driver verifier route.....just not that comfortable trying that...Perhaps if you recheck the 4.24.17 crash you will be able to identify the problem...It would appear all three crashes are caused by the same problem...Thanks for your time.....

 

[axe0]

The last dump shows that Adguard would be causing issues, the other dump doesn't show possible causes directly.

 

[douglas9x]

Thanks...i was kind of thinking that myself...crashes didn't start until about a month after installing AdGuard.