Blue Screen on Startup: BAD_POOL_HEADER

[hblomqvist]

I know there are threads already but most of them is not my exact problem and I've tried most solutions in the answers

So I recently made a clean install of Windows 10 and all I've installed so far is Skype, Steam and Drivers.
What I noticed is that on like 50% of the time I start the computer I get a blue screen saying there was a problem and the computer will automatically restart. The name of the error is: BAD_POOL_HEADER.
After 1 or 2 restarts it doesn't appear and I get to my Windows. Sometimes after the first restart I get to Windows Auto-recovery aswell but restart works just fine in that scenario too,

I've done memtest86 and the RAM had no problems. I have no antivirus except for default Defender. Windows works fine when it loads.

I've heard it could be a driver error and it's pretty likely that's the case since I've installed alot of drivers lately!

PC Specs: http://pcpartpicker.com/p/zHNYcc
Things I installed (mostly drivers): http://pastebin.com/3DAFhMyC
Should I post minidump file?

also, at the same time as this happened my lockscreen picture has changed to my solid theme color, strange.

Thanks for any help!!!!!

 

[Colif]

try running sfc /scannow in a command prompt with admin rights

4 most common causes of error are drivers, registry corruption, bad ram or bad hdd. SFC scans pc, wouldn't think there be much after a fresh install.
you got latest drivers from usual places, try running driver booster and see if it finds anything old.
can test ram with http://www.memtest86.com/
can use this to test SSD: http://support.kingston.com/en/support/technical/kingston-ssd-toolbox
there is seagate software too but wouldn't think it be involved in boot.

download and run http://www.resplendence.com/whocrashed
it looks at error logs and may show what caused errors

copy/paste results here.

Yes, you can share logs, I can't read them but others can.

 

[hblomqvist]

try running sfc /scannow in a command prompt with admin rights

4 most common causes of error are drivers, registry corruption, bad ram or bad hdd. SFC scans pc, wouldn't think there be much after a fresh install.
you got latest drivers from usual places, try running driver booster and see if it finds anything old.
can test ram with http://www.memtest86.com/
can use this to test SSD: http://support.kingston.com/en/support/technical/kingston-ssd-toolbox
there is seagate software too but wouldn't think it be involved in boot.

download and run http://www.resplendence.com/whocrashed
it looks at error logs and may show what caused errors

copy/paste results here.

Yes, you can share logs, I can't read them but others can.

Thanks for your answer, very helpful!

Cmd, memtest and Kingston scan got 0 errors but...

WhoCrashed told me that the problem "amifldrv64.sys". Did some search and I didn't find much but it seems to be some MSI Click Bios or something. I installed it recently so I don't think there's an update. I also use MSI Live Update.
Should I reinstall? And I found this thread: http://www.tomshardware.co.uk/answers/id-2615648/bsods-minutes-logging.html maybe it's worth having a look at.
Thanks again.

EDIT: the .sys is not listed in Local Drivers in WhoCrashed but I have the same OC tools as in the thread, is that a problem? ^^^^

 

[Colif]

educated guess its to do with the built in bios updating function. Not sure why its causing errors at start up. New boards let you update bios while in windows. http://systemexplorer.net/file-database/file-variants/amifldrv64-sys

i know you updated drivers recently but try running driver booster and see if it finds any you overlooked. it might be an Intel driver.

if you post your log files, the guy who answered that might just look at them.

try removing the oc tools and see if it still happens.. removing oc is a good start to fix errors.

 

[hblomqvist]

Ok, thanks.
Now I also got PNR_LIST_CORRUPT once.
I'm gonna try driver booster, bios update and remove oc.
Haven't overclocked anything yet though. Just have the programs.

 

[Colif]

PFN_LIST_CORRUPT Causes


The most common cause for these types of errors are driver problems or corruption problems. Corruption problems can be due to a virus that has worked its way into the vital system files of your computer or it could be due to the fact that your computer’s registry is being affected with corrupt files. If it is a definite driver problem then it is likely due to a specific driver passing a bad memory descriptor list.

http://wiki-errors.com/battling-a-pfn_list_corrupt-error/

 

[hblomqvist]

educated guess its to do with the built in bios updating function. Not sure why its causing errors at start up. New boards let you update bios while in windows. http://systemexplorer.net/file-database/file-variants/amifldrv64-sys

i know you updated drivers recently but try running driver booster and see if it finds any you overlooked. it might be an Intel driver.

if you post your log files, the guy who answered that might just look at them.

try removing the oc tools and see if it still happens.. removing oc is a good start to fix errors.

Thank you sooo much!!!
Driver Booster 3 did the job, it updated 9 outdated drivers, errors gone.
Thanks!!! DDD

 

[hblomqvist]

The error did come back later. I removed MSI Command Center & MSI Super RAID and it seems to be working now. So if you get this error and the RAM seems to be fine, try removing overclocking tools.