Bad_Pool_Header BSOD

Getting these too often so need to address it now.

This is my first time posting so please go easy. I know you need stuff to help advise and I'll do my best to upload everything...

I think I've uploaded the SF Analyzer file...it said it uploaded but I can't see it anywhere!

Aha...THERE it is...any advice greatly appreciated...!

Hello Grey Area, Welcome to SF

Thats quite a collection of dump files you got there with lots of different error codes in, gonna take a while to go through this, in the mean time have a read of the stuff below start with sys specs and virus checks and i will see what i can find i already noticed you got some crazy old drivers on your system so theres gonna be quite a few recommendations coming your way may not post back for hour or two but i will

First off if your OCing in anyway stop, return everything to stock settings for the purposes of testing

If you havent already, fill in your system specs so we know what we are dealing with
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

Make sure you have read the guide on asking for help with BSOD so you know what we need
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

And if necessary set your machine to create minidumps (Method 2 Step 2 is easiest IMO)
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html


Run some scans to check against virus or infection
http://support.kaspersky.com/5350
http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

Run some basic hardware tests
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
http://www.sevenforums.com/tutorials/433-disk-check.html (windows based check)
Hard Drive Diagnostic Procedure (bootable disk check)

OK had a look through and the errors codes are
1 0xA BSOD Index Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
1 0x18 BSOD Index Usual causes: Device driver, kernel, hardware
4 0x19 BSOD Index Usual causes: Device driver
1 0x4E BSOD Index Usual causes: Device driver, ?memory
1 0x50 BSOD Index Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
1 0xbe BSOD Index Usual causes: Device driver, Memory
3 0x1....7E BSOD Index Usual causes: ?

These crashes are blamed on a few different drivers but the repeat offenders are
dxgmms1.sys DirectX driver
nvlddmkm.sys nVidia GFX driver

Now directx is part of the windows package so should be ok its more probable the issue is with your nVidia drivers so i recommend you uninstall them then run http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html before visiting nVidia download page and selecting option 2 to allow automatic detection of your required driver

You have four drivers on your system that predate windows 7 some would be good to try to update these if possible i have listed them with a reference to what they may be associated with follow the link or go to manufacturers website to see if you can obtain updated versions
preferably WHQL certified
SaiHF51A.sys 31/05/2007 08:46:53 Saitek Device, probably some sort of input device ?
SaiUF51A.sys 31/05/2007 08:47:01 Saitek Device as above http://www.saitek.com/uk/down/drivers.php
JmtFltr.sys 28/09/2007 17:04:57 JMicron JMB38X Memory Card Reader Driver http://www.jmicron.com/Driver.htm
hardlock.sys 02/02/2009 15:34:08 Hardlock Device Driver by Aladdin KnowledgeSystems http://www.aladdin.co.il/support/default.aspx

That gives you some starting points try to do what you can any probs post back if any more crashes follow please post the new dumps

Wow Pauly, a lot to go at, many thanks. At work right now but will get onto that lot when I get a chance.

The Sai drivers are from Saitek...unfortunately they're for old devices and I don't think there are updated Win7 drivers, but I still use the devices, so I might be kinda stuck with them.

The nvidia thing is irritating...I always do a clean install of drivers and I only updated recently...but I'll do it again and see what happens.

Thanks again!

If no updated drivers are available you have the option of uninstalling temporarily for testing purposes until you achieve a stable system then reinstalling its all about narrowing down the variables

System info updated - check
Virus check done - check (AVG, hope that's good enough!)
Spyware check done - check (Spybot S&D)
RAM Test done - check (no errors)
Diskcheck done - check (no errors)
HDD Boot Check done - check (no errors)

Used Driversweeper on the Nvidia drivers, both for the GFX card and for PhysX.
No luck on updated drivers for those four devices though. The first one is my gamepad, and since i play games mostly when getting crashes, no hope of disconnecting that for testing purposes. The disk reader is also ancient but not used regularly so I've just uninstalled it. The HardLock is a USB dongle I think, but a lot of the downloads for it look disreputable.

Thanks for the help so far, but short of spending a fortune that I don't have on new hardware, I think I've gone as far as I can.

Boo. Got another one. Details attached. Just let me know if it's one of those drivers again and I'll have to make a decision on whether or not I can afford some new Win7 compliant gear.

Not suggesting you buy new hardware mate theres more stuff we can try yet, it was me blaming them for the crashes not the dump files they are just top of my suspect list as the dumps are quite general
What i may suggest is you uninstall all the devices mentioned before then reboot your computer and try to allow windows to find the best drivers for you. To uninstall go to device manager find the entry for that device and select to uninstall (note the device will need to be plugged in and active to show), after rebooting you may need to select to allow computer to search windows update for best driver
I might add though that we have been seeing a few BSODs generated by Xbox & PS3 controllers as the drivers are a bit how do you say it shit
Seems to be that they are not officially supported so drivers are a bit backroom developed
Other thing worth mentioning is how crap AVG is causes loads of problems, if you want my advice IMHO ditch all your AV and run with Microsoft Security Essentials - Microsoft Windows which will automatically turn on your windows defender firewall & use Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer as your on demand scanner just untick trial version box when installing

Everyone always disses my poor ol' AVG, but in five years of of using it I've never had a virus slip through. Still, I am here for advice, so it would be churlish not to take it - have already done so in fact so I've done the MSE part, just about to do Malwarebytes.

Edit...wow, a Malwarebytes full scan takes quite some time...not found anything so far, nearly 2 hours running time.

OK keep us posted

OK full scan found nothing...just a question - why Malwarebytes over Spybot S&D? the latter allows me to immunize without paying, the former requires me to register if I want the "protection" option...?

We look at MBAM as a periodic on demand scanner, MSE is a good AV its just there as a suplementary, also over the years we have been here those two have very good compatibility with win 7 & we have seen issues/BSODs caused by other AV`s inc AVG/kaspersky/avira etc
Its not a must we just know those two are good and work well, its all about reducing possible causes and variables to narrow down causes of crashes/BSODs as its generally not clear cut what causes them

OK. Well both installed now and AVG and Spybot S&D both mothballed...at least until my next BSOD.

I haven't done the auto-driver install though - but only because I've done it before and Windows can't find one - I always end up back with the old Saitek driver. So I'm stuck with it or have to buy a new one (though from what you said that may not solve the problem either).

I like the Cyborg one too...it has a nice feel and in conjunction with x360ce works with all my games bar one (and that one well known for the issue).

Have you had any more BSODs since redoing GFX drivers, the Saitek driver may be ok i was just suggesting as it was so old, if you had any more dumps since the initial ones you posted upload them or if you get any more

Yeah the SF-05 folder I already posted was post GFX update.

My bad didnt look at that one, i have now and its quite interesting the dump points to a faulting driver named pciidex.sys now from what i can make out it relates to the way the system transfers info on and off of your disks (HDDs) but i think it only applies to ide/pata drives but your system specs only indicate one hitachi sataII drive, can you please confirm what drives you have connected to your system, how they are connected and what settings you are running them in under your bios, eg ide/ahci/raid etc and i will do some more digging tomorrow

Interesting. The only directly connected drive is the SATA, not sure if it's in a RAID config - any idea how I find out?

There is a network drive but the only connection to that is over my wireless network. There are a few USB drives (memory sticks, the microSD card on my phone) that I connect from time to time.

RAID is only for when you have more than one drive attached

That answers that then...just the one SATA drive