locked
BSOD on Aspire 1810tz with Win 7 / 64 RRS feed

  • Question

  • Hello folks,

    I just had another unexpected BSOD restart of my Aspire 1810tz with Win 7 / 64 on it. It happens rarely and I suspect driver update I made few months ago, but I’m not a pro so it can be anything.

    Kaspersky 2010 also stopped working, giving the message that databases are corrupted. I got it sorted.

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000019 (0x0000000000000003, 0xfffffa8006d6d4e0, 0xfffffa8006d6d4df, 0xfffffa8006d6d4e0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 112510-23852-01.

    Dump file: http://rapidshare.com/files/433174156/112510-23852-01.dmp

    Can anyone please diagnose it and help?

    Friday, November 26, 2010 7:11 PM

All replies

  • Bug Check 0x19: BAD_POOL_HEADER

    The BAD_POOL_HEADER bug check has a value of 0x00000019. This indicates that a pool header is corrupt.

    http://msdn.microsoft.com/en-us/library/ff557389%28VS.85%29.aspx


    STACK_TEXT: 
    nt!KeBugCheckEx
    nt!ExDeferredFreePool+0xc7b
    nt!ExFreePoolWithTag+0x411
    volsnap!ExFreeToNPagedLookasideList+0x28
    volsnap!VspFreeWriteContext+0x77
    volsnap!VspWriteContextCompletionRoutine+0xae
    nt!IopfCompleteRequest+0x3a6
    CLASSPNP!TransferPktComplete+0x1ce
    nt!IopfCompleteRequest+0x3a6
    iaStor +0x52790

    the Intel storage driver maybe the cause:

        Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
        Image name: iaStor.sys
        Timestamp:        Fri Jun 05 03:53:40 2009

    so update the driver, please.

    if this doesn't fix it, please enable Driver verifier to get the causing driver:

    http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

    http://support.microsoft.com/?kbid=244617

    when you get a new BSOD, boot to safe mode, disable driver verifier, reboot to normal mode and upload the newest dmp file from the folder C:\Windows\Minidump to your public SkyDrive [1] folder and post the link here.

    You can also check your RAM with memtest86+ for errors.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Saturday, November 27, 2010 3:40 AM
  • Hi Andre,

    Thank you, I will try that.

    Saturday, November 27, 2010 10:34 PM
  • Hello people / Andre.

    That’s m e again.

    I tried to update every possible driver, and all seems to be fine except one thing. Yesterday I've put my PC into sleep mode and went to work. When I came back and switched it on, there was a message that Windows just recovered from another BSOD, this time it was different: The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff80003041387, 0x0000000000000000, 0x00000000ffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120210-22776-01.

    http://rapidshare.com/files/434550510/120210-22776-01.dmp

     

    Can I ask someone again to read it for me and point me to the right direction.

    P.S. I will also perform a memcheck.

     

    Thanks,

    Aleksandr

    Thursday, December 2, 2010 10:28 PM
  • KMODE_EXCEPTION_NOT_HANDLED (1e)

    STACK_TEXT: 
    nt!KeBugCheckEx
    nt!KiDispatchException+0x1b9
    nt!KiExceptionDispatch+0xc2
    nt!KiPageFault+0x23a
    nt!IopFreeBandwidthContract+0x17
    nt! ?? ::NNGAKEGL::`string'+0x1ea9b
    nt!ObpDecrementHandleCount+0xb4
    nt!ObpCloseHandleTableEntry+0xb1
    nt!ObpCloseHandle+0x94
    nt!KiSystemServiceCopyEnd+0x13
    nt!KiServiceLinkage
    fileinfo !FIPfInterfaceClose+0x48
    nt!PfpOpenHandleClose +0x55

    because the crash happens when closing files you should run chkdsk C: /r /f to detect NTFS filesystem issues.

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, December 3, 2010 1:00 PM
  • Thanks very much Andre! Really appreciated!
    Friday, December 3, 2010 11:29 PM