BSOD - bad pool header

By waterproof · 16 replies
Dec 3, 2011
Post New Reply
  1. I got a BSOD while playing games on my PC, here is the sys data it dumped.

    The BSOD error was 'bad pool header' tried googling, said it could be drivers, but i am not sure what drivers caused it... maybe nvidia? any1 can decode this mess? :)

    see attachments

    Attached Files:

  2. Mark56

    Mark56 TechSpot Paladin Posts: 1,886

    Not too sure what that text file is, never seen anything like that before. Please follow this guide to attach your minidumps to your next post.

  3. waterproof

    waterproof TS Booster Topic Starter Posts: 208

    its gone now :(

    but you have any idea what caused it? right after the BSOD i couldnt boot my pc, so i turned it off for 20 mins and then it booted up again...
  4. Mark56

    Mark56 TechSpot Paladin Posts: 1,886

    It could have been caused by several factors, drivers, memmory, overheating, virus, etc. In most cases, once you have had a BSOD you will get another one.

    Post the minidump files and I'll have a look.
  5. waterproof

    waterproof TS Booster Topic Starter Posts: 208

    Here's one that happened today, still can't find the fault of this!

    Attached Files:

  6. Mark56

    Mark56 TechSpot Paladin Posts: 1,886

    Is that the first BSOD you have had since last April?

    All I can tell you from the minidump is that it was probably caused by a bad driver. Obviously the problem is only a minor issue as the crashes are very rare. That being the case it will be very difficult to track down the cause.

    If you had had any other BSOD's then please post all the minidumps as just analysing one dump is not conclusive.
  7. waterproof

    waterproof TS Booster Topic Starter Posts: 208

    I think you read the date format on my thread wrong ;) it's from last november, yeah I assume you're not American as well? :)

    I got two of these this month alone, could be 3 but I was asleep, same issue. I only updated my nVidia drivers (using the beta) so thats the only driver update I have done. However, Im not sure if it's the cause though.
  8. Mark56

    Mark56 TechSpot Paladin Posts: 1,886

    Sorry about the date mix up, haven't been on this site for a while and forgot it was in American format.

    As you are using a Beta driver that could be the cause as it will still be in development. Did you have any BSOD's before you installed this driver? If not then that would seems like the most likely culprit so try going back to the most up to date non Beta and see if the BSOD's still happen.

    If that does not do the trick then please post all the dump files in the minidump folder.
  9. waterproof

    waterproof TS Booster Topic Starter Posts: 208

    I had rarely though before I installed BETA drivers but at the same time, I was running lots of stuff on my desktop.

    Here's another BSOD with different reason, which Im still dumbstruck why I'm getting it again. It happens nearly everyday (pool header) but this is new. (its fault in nonpaged area) i assume its software again.

    Attached Files:

  10. Mark56

    Mark56 TechSpot Paladin Posts: 1,886

    This particular crash can be caused by a bad driver but all too often it is due to faulty memory.

    The system had been running for over 2 days before this occured.

    A quick way to see if it is faulty RAM is to remove all but one of the RAM sticks and then keep using the PC to see if the crashes continue, if you get another crash, post the minidump and then swap the sticks around and continue normal use. You may find it only crashes with one of your RAM sticks.

    If you have overclocked the RAM then switch it back to default settings.
  11. waterproof

    waterproof TS Booster Topic Starter Posts: 208

    I never overclocked my RAM, but I believe your statement sounds like a RAM issue, as I got another BSOD today, different summary. Its "Memory Management" attached the files.

    Attached Files:

  12. waterproof

    waterproof TS Booster Topic Starter Posts: 208

    Actually I think I should take back what I said it could be RAM, tested my ram sticks using memtest, also tried each slot 1 by 1 to see if it's a single ram stick, 0 errors found. Now this leaves to some silly driver thats causing BSOD which i can't find. Btw I remove the BETA drivers for nvidia and revert back to the stable version, then next day I got that BSOD as i posted previously
  13. Mark56

    Mark56 TechSpot Paladin Posts: 1,886

    If you were using Memtest86+ it needs to be run for at least 8 passes to get a conclusive result which would have taken a long time. Even after that I have seen several examples of Memtest passing a RAM stick as being fault free, only to find later that the RAM was infact faulty, Memtest can miss some minor errors.

    That minidump does indeed state Memory Management but that could still be caused by a driver.

    We need to prove if it is the RAM or not so what I would suggest you now try is (as suggested in post 10) to run the PC with just one Ram stick fitted, keep it going until you have a BSOD or at least 48 hours of up time, then swap the sticks and see if you still get another BSOD.

    If BSOD's occur with both Ram sticks then we can move on to running the Driver Verifier.
  14. waterproof

    waterproof TS Booster Topic Starter Posts: 208

    8 tests is too long lol, i might as well get new RAM slots and since i have 16gb it will take very long. anyway I will do what you have suggested, however before i do, i want to test the drivers (if its from that) because as from what the thread I have made, I didn't get any until the point I mess with my graphic drivers.

    new bsod after 2 days, this time its 'system service exception BSOD 0x0000003B'
    didn't provide a minidump (odd) but did sys data.

    Attached Files:

  15. Mark56

    Mark56 TechSpot Paladin Posts: 1,886

    There is no dump file in that zip folder only sysdata.

    There is no consistency in the error codes which is often an indication of faulty memory.

    If it is the new beta graphics driver that is causing the problem then roll back to the previous driver and see if the problem stops.

    I would suggest running Memtest overnight.
  16. waterproof

    waterproof TS Booster Topic Starter Posts: 208

    I think i figured out my BSOD issue, however I don't know what to do.

    I realize, the period of when I made the thread and when I didn't had BSOD was because I wasn't playing my audio music winamp which i use, i decided to go a week without listening to music on my PC, no bsod, but once i have music/video running the same time, within minutes, playing music i get bsod, and each time i got bsod its either i had music / video playing the same time - coincidence but when i didnt have bsod is when i'm not playing music.

    i manage to use bluescreenview and the cause of bsod was HDAUDBUS.sys and NTOSKRNL.exe, which I googled doesnt say much.. so what should i do regarding this error? i def. think its a driver issue not a ram issue.

    Attached Files:

  17. Mark56

    Mark56 TechSpot Paladin Posts: 1,886

    The minidump states Memory Management again and the windows audio driver.

    I would still recommend you run the Memtest for the time required to complete at least 8 passes.

    You could also try updating the driver for your audio device.

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...