Share via

BSOD BAD_POOL_HEADER caused by ntoskrnl.exe (Windows 7)

Anonymous
2015-07-17T18:07:56+00:00

Hello there everyone.  Over the past week or so I have noticed my laptop become quite slow, it would freeze up when I click into any application, and then would say not responding. As of two days ago I got my first BSOD, I had fallen asleep with my laptop next to me and went to use it and then a BSOD appeared with the error BAD_POOL_HEADER with the bug check code bug check code of 0x00000019. The other two BSODs said the exact same. I downloaded Bluescreenviewer and all 3 BSOD are caused by ntoskrnl.exe. My laptop works perfectly in safe mode so I am very confused to what could be causing this BSOD. I have exams very soon and I am stressing trying to figure out whats wrong. I recently uninstalled adobe reader XI as it was constantly freezing.

I have a Sony Vaio laptop which is around 3-4 years old.

Processor: Intel(R) Core(TM) i5-2430M CPU @ 2.4Ghz

OS: Windows 7 Home Premium, 64-bit.

I have checked for driver updates but all seem fine.

Here is a link to the memory dump files: https://onedrive.live.com/redir?resid=BF4EB0E0945D544%21119 Thank you in advance.

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

7 answers

Sort by: Most helpful
  1. Anonymous
    2015-07-18T08:59:47+00:00

    Hi again, so I ran memtest overnight for 9 passes, which took around 9 hours and no errors appeared. I will also put the link to the BSOD from yesterday that appeared 5 minutes after running driver verifier.

    https://onedrive.live.com/?id=BF4EB0E0945D544%21118&cid=0BF4EB0E0945D544&group=0

    It's in the folder named minidumpnewfile.

    (I hope I'm posting the link correctly)!

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2015-07-17T18:36:52+00:00

    **These crashes were related to memory corruption (probably caused by a driver).**Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.

    If you are over-clocking anything reset to default before running these tests.

    In other words STOP!!!  If you do not know what this means you probably are not



    1-Driver verifier (for complete directions see our wiki here)

    **2-Memtest. (**You can read more about running memtest here)


    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2015-07-18T10:42:56+00:00

    When I type verifier /query the box pops up and immediately closes

    0 comments No comments
  4. Anonymous
    2015-07-18T10:00:08+00:00

    Laura

    This DMP did not appear to have verifier enabled.  What were the results when you typed verifier /query?

    0 comments No comments
  5. Anonymous
    2015-07-17T19:31:55+00:00

    Thank you for the reply! I am not overclocking anything.. i even had to google what that meant. I ran driver verifier in safe mode (dont know if that was a bad idea). I then restarted my laptop and went to normal windows mode' the screen then froze after 5 minutes and a blue sceeen appeared saying 'KERNAL_DATA_INPAGE_ERROR 0X0000007A. It is still on the blue screen and still says collecting data for crash dump... inititalising disk for crash dump...

    Im not sure what to do next!

    I shut down and logged in through safe mode and it said the KERNAL_DATA_INPAGE_ERROR blue screen was also caused by the ntoskrnl.exe driver.

    0 comments No comments