TechSpot

Daily BSOD on WinXP: Bad_Pool_Header caused by ntoskrnl.exe

By dpiperjr
Jan 24, 2011
Post New Reply
  1. Everyday but once a day, I get a blue screen of death. "Bad Pool Header" caused by "ntoskrnl.exe" I am a computer techie but when it comes to BSOD's, I am fairly new to these.

    This is the exact results from the Minidump though I will include it.

    "
    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 (0x00000020, 0xe28e3848, 0xe28e3868, 0x0c040206)

    *** ntoskrnl.exe - Address 0x80533846 base at 0x804d7000 DateStamp 0x4bd6eca8
    "

    Please help me solve this problem. It occured when I was playing "CrimeCity" on facebook and the other night it happened when I was on youtube. The first time it happened I had to copy the whole hard drive onto another or it would take it 30 minutes to load and I had no access to "My Computer". it would keep loading and loading non-stop. While I am waiting for a response, I will be googling for a solution.

    Thanks.

    Computer Specs:
    Microsoft Windows XP Home Edition V2
    SP3
    Pentium 4 CPU 2.80 GHz
    1.24 GB RAM

    If you need anything else, please ask.

    Update:
    I updated both my graphics driver and network driver.
     

    Attached Files:

  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    0x00000019: BAD_POOL_HEADER
    A pool header issue is a problem with Windows memory allocation. Device driver issues are probably the most common, but this can have diverse causes including bad sectors or other disk write issues, and problems with some routers.

    Nothing definitive was cited as to the cause except the core Windows OS driver ntoskrnl.exe. The thing is OS drivers are usually too general to be of much diagnostic help. They function more as flagging that there is a problem rather than pointing to the cause of the problem.

    For clarification, you installed a new harddrive, correct?
     
  3. dpiperjr

    dpiperjr TS Rookie Topic Starter

    I thought it was my hard drive so I cloned the hard drive to another and I am using that which is the first hard drive I began using.
     
  4. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Did you run harddrive diagnostics at any time or security scans?
     
  5. dpiperjr

    dpiperjr TS Rookie Topic Starter

    Yes, Acronis Drive Monitor. I rely on that most of the time and there is no problems with the hard drive.
     
  6. dpiperjr

    dpiperjr TS Rookie Topic Starter

    I just got the "KERNEL_STACK_INPAGE_ERROR". I am thinking it is a MBR bootsector virus possibly.
    Does anyone know how to fix this?
    Tomorrow I am going to do a reinstallation if the CHKDSK /F /R does not work.
     

Similar Topics

Add New Comment

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