BSOD - BAD POOL HEADER

G

georgent

Member
Joined
Oct 28, 2017
Posts
19
Hello to everyone :)


A few days ago I performed a clean install of windows 10 v 1709 build 16299.19. My machine is a Lenovo Thinkcentre tiny M93p i5-4790t 8gigs of ram. Nothing fancy.
Today while I was downloading an iso from Microsoft I got a BSOD (BAD POOL HEADER) :/

I am uploading the files I got from sysnative's tool here. If someone would like to help me I will be eternally grateful to this person :)

Thank you in advance!
 

Attachments

Hi. . .

The lone dump was of little help to us. It listed "memory corruption" as the probable cause.

To be on the safe side and rule software (drivers) out, please run Driver Verifier.

Driver Verifier - Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista

Let it run for 24 hours minimum.

If Driver Verifier flags a 3rd party driver, it will BSOD your system immediately, so be sure to save any work very frequently. A VERIFIER_ENABLED memory dump will [hopefully] contain the name of the offending 3rd party driver, if the BSODs are being caused by a software problem.

If no 3rd party driver is named, we then know the cause of the VERIFIER_ENABLED BSOD is "unknown hardware failure".

Regards. . .

jcgriff2
 
Hi jcgriff2 ! Thank you for your answer!

Quick question before i proceed with driver verifier. Like i said to my previous post its a clean install, sorry that i didnt mention earlier that all the drivers that my system is using came from windows update. After the os installation i left the computer for a few minutes and windows installed all the necessary drivers in order to work. Device manager looks great, all devices identified, everything is working. So even if am using windows update drivers i still have to use the verifier?

Thank you
 
georgent said:
... So even if am using windows update drivers i still have to use the verifier?
Click to expand...

Yes. Driver Verifier checks 3rd party (non-Microsoft) drivers out and it is these 3rd party drivers that are the usual cause of software related BSODs.

There really is nothing for you to do. Just bring up D/V, select the options as indicated; let it run for at least 24 hours.

If a BSOD occurs, get the dump (\windows\minidump), copy it to Desktop or Documents; zip it up and attach to your post. You will not be able to zip it up in the \windows directory.

I'm requesting this (running Driver Verifier) so that we can either rule-in or out software as the cause of your BSODs.

Right now, it does appear that unknown hardware failure is the culprit.

Regards. . .

jcgriff2
 
Last edited:

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top