BSOD after Log-in, "BAD_POOL_HEADER", STOP: 0x00000019


  1. Posts : 15
    Windows 7 Home Premium 64-bit
       #1

    BSOD after Log-in, "BAD_POOL_HEADER", STOP: 0x00000019


    I had my laptop disconnected from AC power, totally off, and it had worked perfectly so far. I haven't had any problems, except for a few Trojans/rootkits long ago, and I have only gotten one BSOD plus this one.

    I turn my laptop on, connect it to AC power, and after having logged in, I initiated an Avast! scan out of curiosity and around 5 seconds after that a BSOD popped up. I restarted laptop, and now I logged in normally, am running antivirus scan, and checking for maintenance/performance options.

    What have I installed/updated recently?

    QuickTime, yesterday. Nothing else.

    I use Windows 7 64-bit in an OEM version, ASUS laptop. The first BSOD got fixed by updating a driver, but this one doesn't appear in "Windows Solutions to Problems" nor my laptop has experienced a problem after it. What can I do?

    Is there something wrong in the laptop?
      My Computer


  2. Posts : 15
    Windows 7 Home Premium 64-bit
    Thread Starter
       #2

    Casually, I have a laptop model similar to the one found here. I do have System Restore's, I think automatically made SR Points.

    Please help.
      My Computer


  3. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #3


    We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.


    Please attach the DMP files to your next post not to post one.


    If you are overclocking STOP

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:
    Quote:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    *If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

    To ensure minidumps are enabled:
    Quote:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.

      My Computer


  4. Posts : 15
    Windows 7 Home Premium 64-bit
    Thread Starter
       #4

    Ok… lol. Last time I had the first BSOD I got the same answer

    Also, why is the Minidumps folder locked? And if I allow access, how do I restringe it again? It asks for admin access I think.
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #5

    The Minidumps folder is a subfolder in the Windows directory, so it inherits the same permissions/ownership as the Windows directory. That directory is protected from tampering for your security, so any subdirectories are also protected.

    The https://www.sevenforums.com/crashes-d...tructions.html should allow you to gather the information required and will also provide us with more details about your crashes than the simple .dmp files would.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:57.
Find Us