BSOD on Toshiba Laptop

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by hsrstud, Jul 13, 2010.

  1. hsrstud

    hsrstud New Member

    Joined:
    Nov 10, 2009
    Messages:
    22
    Likes Received:
    0
    Thank you for your help.

    My Toshiba Laptop has been randomly crashing. I've searched for a solution, and while many others have posted with similar issues, I haven't been able to find a solution for my situation yet. Here are the results of an analysis of my dump files. The results don't seem that useful to me, aside from the fact that they appear to suggest that a Vista driver may be the culprit (I'm using Windows 7).

    Please let me know what other information would be helpful to identify the source of the problem.


    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 00000020, a pool block header size is corrupt.
    Arg2: 8520d000, The pool entry we were looking for within the page.
    Arg3: 8520d300, The next pool entry.
    Arg4: 08600000, (reserved)

    Debugging Details:
    ------------------

    GetPointerFromAddress: unable to read from 82ba3718
    Unable to read MiSystemVaType memory at 82b83160

    BUGCHECK_STR: 0x19_20

    POOL_ADDRESS: GetPointerFromAddress: unable to read from 82ba3718
    Unable to read MiSystemVaType memory at 82b83160
    8520d000

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 8aa3fa7b to 82b5a1b6

    STACK_TEXT:
    8cb0fadc 8aa3fa7b 8520d008 00000000 82a7551c nt!ExFreePoolWithTag+0x1b1
    8cb0faf4 8aa31c0c 8520d008 8cb0fb18 8aad6c4b Ntfs!NtfsFreeNonpagedDataFcb+0x28
    8cb0fb00 8aad6c4b 8aa65300 8520d008 851a2500 Ntfs!ExFreeToNPagedLookasideList+0x1e
    8cb0fb18 8aad3bc8 8520d008 00000000 861f1240 Ntfs!NtfsDeleteNonpagedFcb+0x3c
    8cb0fb40 8aa3f174 851a2500 8cb0fb70 8cb0fb7a Ntfs!NtfsDeleteFcb+0xd5
    8cb0fb94 8aabb15d 851a2500 861f10d8 aaee5888 Ntfs!NtfsTeardownFromLcb+0x24f
    8cb0fbe4 8aa37bec 851a2500 aaee5978 01ee5b20 Ntfs!NtfsTeardownStructures+0xf3
    8cb0fc0c 8aab755b 851a2500 aaee5978 aaee5b20 Ntfs!NtfsDecrementCloseCounts+0xaf
    8cb0fc6c 8aad64c3 851a2500 aaee5978 aaee5888 Ntfs!NtfsCommonClose+0x4f2
    8cb0fd00 82aa8f3b 00000000 00000000 84ee74c0 Ntfs!NtfsFspClose+0x118
    8cb0fd50 82c496bb 00000000 a888edf4 00000000 nt!ExpWorkerThread+0x10d
    8cb0fd90 82afb0f9 82aa8e2e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!ExFreePoolWithTag+1b1
    82b5a1b6 cc int 3

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!ExFreePoolWithTag+1b1

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cacf

    FAILURE_BUCKET_ID: 0x19_20_nt!ExFreePoolWithTag+1b1

    BUCKET_ID: 0x19_20_nt!ExFreePoolWithTag+1b1

    Followup: MachineOwner
    ---------

    0: kd> !analyze
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 19, {20, 8520d000, 8520d300, 8600000}

    GetPointerFromAddress: unable to read from 82ba3718
    Unable to read MiSystemVaType memory at 82b83160
    Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+1b1 )

    Followup: MachineOwner
    ---------
     
  2. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Hi.

    Please navigate to C:\Windows\Minidump

    Copy the files in there to any other folder. Then zip them. Attach the zip to a post using the paperclip above where you type, in advanced mode reply. We will look at the error(s) for you.
     
  3. hsrstud

    hsrstud New Member

    Joined:
    Nov 10, 2009
    Messages:
    22
    Likes Received:
    0
    Thanks for offering to help me with this!

    Unfortunately, file attachment limit appears to be 10MB, but the smallest size I was able to compress the file to was 44MB.
     
  4. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Wow, you must have a million crash dumps for it to be that large.

    You could try only zipping the latest 10, date wise. Or upload the current zip you have to www.rapidshare.com and then post a link to it here.
     
  5. hsrstud

    hsrstud New Member

    Joined:
    Nov 10, 2009
    Messages:
    22
    Likes Received:
    0
  6. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    One of the two crash dumps was a full one, not a minidump. Minidumps are the usual and not sure why one of them was output as full. That's why it was so large to upload.

    Anyhow...

    For now, I'd definitely remove the AVG which is most likely causing the problems. Here is a special tool to do so which is best used in safe mode:

    AV Uninstallers - Windows 7 Forums

    I recommend installing MSE as a replacement because it never causes bsod and is very resource friendly.

    -----

    This driver needs to be updated:

    Code:
    FwLnk    FwLnk.sys    Sun Nov 19 09:11:12 2006
    You can install the latest Toshiba Value Added Package for your specific laptop to update it from this link:

    Toshiba Support - Homepage
     
  7. hsrstud

    hsrstud New Member

    Joined:
    Nov 10, 2009
    Messages:
    22
    Likes Received:
    0
    Wow, thanks so much! This is very helpful.
     
  8. hsrstud

    hsrstud New Member

    Joined:
    Nov 10, 2009
    Messages:
    22
    Likes Received:
    0
    Unfortunately, I'm back again. I removed AVG and installed MSE. I also installed the Toshiba Value Added Package, but it said that everything was up-to-date and didn't allow me to install anything. This is my wife's computer and she says that she feels the bad_pool_header BSOD always seems to appear when she is downloading or working with photos on Facebook. I'm not sure if this is informative.

    Thanks again.
     
  9. hsrstud

    hsrstud New Member

    Joined:
    Nov 10, 2009
    Messages:
    22
    Likes Received:
    0
    I should also mention that I looked at the FwLnk.sys file downloaded with the most recent value added package and it is the same version (2006).
     
  10. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Here's what you can do then.

    Navigate to C:\Windows\System32\drivers

    Rename FwLnk.sys to FwLnk.BAK

    Reboot and hope for no further bsod troubles. If there are any, please post the new crash dump after doing this and good luck!
     
  11. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    It would probably be good to also update this Synaptics Touchpad driver if one is available for your model, on Toshiba's site:

    Code:
    SynTP    SynTP.sys    Thu Aug 14 22:02:22 2008
    If there is a new modem driver, update that one as well:

    Code:
    AGRSM    AGRSM.sys    Mon Nov 10 09:56:37 2008
    What I think is actually really causing the bsod issue is Soluto. Please uninstall that while in safe mode.
     
    #11 TorrentG, Jul 20, 2010
    Last edited: Jul 20, 2010
  12. hsrstud

    hsrstud New Member

    Joined:
    Nov 10, 2009
    Messages:
    22
    Likes Received:
    0
    Ok, will do. I also read elsewhere that my bios needed to be updated, because the old bios would give this BSOD with Windows 7. I updated the version from 1.7 to 1.9. I'll report back if the BSOD comes back.
     

Share This Page

Loading...