BSOD Crash Dump - Help!

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Versus13, Nov 18, 2012.

  1. Versus13

    Versus13 New Member

    Joined:
    Nov 18, 2012
    Messages:
    10
    Likes Received:
    0
  2. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
  3. Versus13

    Versus13 New Member

    Joined:
    Nov 18, 2012
    Messages:
    10
    Likes Received:
    0
  4. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    Only 106 updates after SP1, most systems have 130 to 140 updates at this point. Please visit Windows Updates and get ALL available updates.

    MSINFO32 file is truncated, please run the data collection tool again for the MSINFO32 report.

    We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
    If it's not the SSD/storage controller drivers, then we have to start suspecting other hardware. Please run these free hardware diagnostics: Hardware Diagnostics

    Analysis:
    The following is for informational purposes only.
    Code:
    [font=lucida console]**************************Mon Nov 19 08:24:32.512 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111912-6006-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:53:59.683[/B]
    BugCheck Code: [B]BugCheck 4E, {99, 19e09b, 2, 19d79a}[/B]
    Probably caused by :[B]memory_corruption ( nt!MiBadShareCount+4c )[/B]
    BugCheck Info: [B]PFN_LIST_CORRUPT (4e)[/B]
    Arguments: 
    Arg1: 0000000000000099, A PTE or PFN is corrupt
    Arg2: 000000000019e09b, page frame number
    Arg3: 0000000000000002, current page state
    Arg4: 000000000019d79a, 0
    BUGCHECK_STR:  0x4E_99
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]chrome.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x4E_99_nt!MiBadShareCount+4c[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Sun Nov 18 21:37:26.047 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111912-5725-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:54:21.233[/B]
    BugCheck Code: [B]BugCheck 1A, {41790, fffffa8003993ea0, ffff, 0}[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )[/B]
    BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
    Arguments: 
    Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
        contains the address of the PFN for the corrupted page table page.
        On a 32 bit OS, parameter 2 contains a pointer to the number of used
        PTEs, and parameter 3 contains the number of used PTEs.
    Arg2: fffffa8003993ea0
    Arg3: 000000000000ffff
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_41790
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]wermgr.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Sat Nov 17 20:04:06.590 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111812-5600-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 2:48:18.211[/B]
    BugCheck Code: [B]BugCheck 1A, {41790, fffffa8003993e40, ffff, 0}[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )[/B]
    BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
    Arguments: 
    Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
        contains the address of the PFN for the corrupted page table page.
        On a 32 bit OS, parameter 2 contains a pointer to the number of used
        PTEs, and parameter 3 contains the number of used PTEs.
    Arg2: fffffa8003993e40
    Arg3: 000000000000ffff
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_41790
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]conhost.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Sat Nov 17 17:16:07.365 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111712-5522-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 3:54:16.552[/B]
    BugCheck Code: [B]BugCheck 3B, {c0000005, fffff80002cae383, fffff880098c58e0, 0}[/B]
    Probably caused by :[B]memory_corruption ( nt!MmCopyToCachedPage+223 )[/B]
    BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
    Arguments: 
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80002cae383, Address of the instruction which caused the bugcheck
    Arg3: fffff880098c58e0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME: [B]UnRAR.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x3B_nt!MmCopyToCachedPage+223[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Sat Nov 17 08:22:37.542 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111712-6661-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:32:02.728[/B]
    BugCheck Code: [B]BugCheck 4E, {2, 43adf, 21f5ff, 1}[/B]
    Probably caused by :[B]memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )[/B]
    BugCheck Info: [B]PFN_LIST_CORRUPT (4e)[/B]
    Arguments: 
    Arg1: 0000000000000002, A list entry was corrupt
    Arg2: 0000000000043adf, entry in list being removed
    Arg3: 000000000021f5ff, highest physical page number
    Arg4: 0000000000000001, reference count of entry being removed
    BUGCHECK_STR:  0x4E_2
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]MsMpEng.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8d[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Fri Nov 16 17:46:14.633 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111612-5522-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:15:46.819[/B]
    BugCheck Code: [B]BugCheck 50, {fffff880e88a9f88, 0, fffff80002e01a9b, 5}[/B]
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :[B]Pool_Corruption ( nt!ExDeferredFreePool+1df )[/B]
    BugCheck Info: [B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B]
    Arguments: 
    Arg1: fffff880e88a9f88, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002e01a9b, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME: [B]TubeDigger.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x50_nt!ExDeferredFreePool+1df[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Fri Nov 16 14:17:56.916 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111612-6770-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 1:20:44.102[/B]
    BugCheck Code: [B]BugCheck 1A, {41790, fffffa8003993e70, ffff, 0}[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )[/B]
    BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
    Arguments: 
    Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
        contains the address of the PFN for the corrupted page table page.
        On a 32 bit OS, parameter 2 contains a pointer to the number of used
        PTEs, and parameter 3 contains the number of used PTEs.
    Arg2: fffffa8003993e70
    Arg3: 000000000000ffff
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_41790
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]wermgr.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Fri Nov 16 08:05:07.358 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111612-5943-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:30:56.544[/B]
    BugCheck Code: [B]BugCheck 1A, {41790, fffffa8003993ea0, ffff, 0}[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35054 )[/B]
    BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
    Arguments: 
    Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
        contains the address of the PFN for the corrupted page table page.
        On a 32 bit OS, parameter 2 contains a pointer to the number of used
        PTEs, and parameter 3 contains the number of used PTEs.
    Arg2: fffffa8003993ea0
    Arg3: 000000000000ffff
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_41790
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]rundll32.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Fri Nov 16 07:25:46.752 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111612-6208-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:05:15.938[/B]
    BugCheck Code: [B]BugCheck 1E, {ffffffffc0000005, fffff80002c91284, 0, ffffffffffffffff}[/B]
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :[B]ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+0 )[/B]
    BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002c91284, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]msdt.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x1E_c0000005_R_nt!SwapContext_PatchXRstor+0[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Thu Nov 15 07:45:12.524 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111512-6224-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:08:00.710[/B]
    BugCheck Code: [B]BugCheck 50, {fffff8a0e0379cc4, 0, fffff80002fa993e, 5}[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )[/B]
    BugCheck Info: [B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B]
    Arguments: 
    Arg1: fffff8a0e0379cc4, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002fa993e, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME: [B]checksur.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x50_nt!CmpKcbCacheLookup+1de[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Tue Nov 13 18:12:10.328 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111312-6240-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:00:49.514[/B]
    BugCheck Code: [B]BugCheck 50, {fffff8a08f580ab4, 1, fffff8800125cd5f, 5}[/B]
    Probably caused by :[B]Ntfs.sys ( Ntfs!NtfsRemoveClose+a3 )[/B]
    BugCheck Info: [B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B]
    Arguments: 
    Arg1: fffff8a08f580ab4, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff8800125cd5f, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME: [B]System[/B]
    FAILURE_BUCKET_ID: [B]X64_0x50_Ntfs!NtfsRemoveClose+a3[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Tue Nov 13 16:46:43.039 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111312-6146-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:04:09.836[/B]
    BugCheck Code: [B]BugCheck 19, {3, fffffa8006674c80, fffffa80a8674c80, fffffa80a0674c80}[/B]
    *** WARNING: Unable to verify timestamp for MpFilter.sys
    *** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
    Probably caused by :[B]Pool_Corruption ( nt!ExDeferredFreePool+a53 )[/B]
    BugCheck Info: [B]BAD_POOL_HEADER (19)[/B]
    Arguments: 
    Arg1: 0000000000000003, the pool freelist is corrupt.
    Arg2: fffffa8006674c80, the pool entry being checked.
    Arg3: fffffa80a8674c80, the read back flink freelist value (should be the same as 2).
    Arg4: fffffa80a0674c80, the read back blink freelist value (should be the same as 2).
    BUGCHECK_STR:  0x19_3
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]SearchProtocol[/B]
    FAILURE_BUCKET_ID: [B]X64_0x19_3_nt!ExDeferredFreePool+a53[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Tue Nov 13 14:02:25.307 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111312-6364-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:24:37.494[/B]
    BugCheck Code: [B]BugCheck 19, {3, fffffa8006676180, fffffa8027676180, fffffa8006676180}[/B]
    Probably caused by :[B]Pool_Corruption ( nt!ExDeferredFreePool+a53 )[/B]
    BugCheck Info: [B]BAD_POOL_HEADER (19)[/B]
    Arguments: 
    Arg1: 0000000000000003, the pool freelist is corrupt.
    Arg2: fffffa8006676180, the pool entry being checked.
    Arg3: fffffa8027676180, the read back flink freelist value (should be the same as 2).
    Arg4: fffffa8006676180, the read back blink freelist value (should be the same as 2).
    BUGCHECK_STR:  0x19_3
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]lsass.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x19_3_nt!ExDeferredFreePool+a53[/B]
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    [/font]
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    [font=lucida console]**************************Mon Nov 19 08:24:32.512 2012 (UTC - 5:00)**************************
    intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
    MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
    amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
    rtl8192se.sys               Fri Apr 30 04:04:26 2010 (4BDA8F0A)
    asmtxhci.sys                Fri Mar  4 02:54:59 2011 (4D709AD3)
    asmthub3.sys                Fri Mar  4 02:55:10 2011 (4D709ADE)
    k57nd60a.sys                Tue May 10 00:42:30 2011 (4DC8C236)
    ISCTD64.sys                 Tue Aug 23 13:32:39 2011 (4E53E437)
    WPRO_41_2001.sys            Mon Nov  7 16:04:48 2011 (4EB847F0)
    IntcDAud.sys                Tue Dec  6 06:23:07 2011 (4EDDFB1B)
    ikbevent.sys                Tue Jan  3 19:35:09 2012 (4F039EBD)
    imsevent.sys                Tue Jan  3 19:35:31 2012 (4F039ED3)
    RTKVHD64.sys                Tue Jan 31 05:55:06 2012 (4F27C88A)
    iusb3hub.sys                Mon Feb 27 05:56:50 2012 (4F4B6172)
    iusb3xhc.sys                Mon Feb 27 05:56:53 2012 (4F4B6175)
    iusb3hcs.sys                Mon Feb 27 05:58:49 2012 (4F4B61E9)
    HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
    MpFilter.sys                Thu Aug 23 19:03:14 2012 (5036B6B2)
    SbieDrv.sys                 Sat Aug 25 16:27:46 2012 (50393542)
    igdkmd64.sys                Wed Sep 26 15:49:04 2012 (50635C30)
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Thu Nov 15 07:45:12.524 2012 (UTC - 5:00)**************************
    HECIx64.sys                 Wed Nov  9 19:52:25 2011 (4EBB2049)
    igdkmd64.sys                Mon May 21 15:04:11 2012 (4FBA91AB)
    [/font]
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=amdxata.sys
    http://www.carrona.org/drivers/driver.php?id=rtl8192se.sys
    http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
    http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
    http://www.carrona.org/drivers/driver.php?id=k57nd60a.sys
    http://www.carrona.org/drivers/driver.php?id=ISCTD64.sys
    http://www.carrona.org/drivers/driver.php?id=WPRO_41_2001.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=ikbevent.sys
    http://www.carrona.org/drivers/driver.php?id=imsevent.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=iusb3hub.sys
    http://www.carrona.org/drivers/driver.php?id=iusb3xhc.sys
    http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
    http://www.carrona.org/drivers/driver.php?id=SbieDrv.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
     
  5. Versus13

    Versus13 New Member

    Joined:
    Nov 18, 2012
    Messages:
    10
    Likes Received:
    0
    Thanks for the extensive reply.

    Just when i was starting to think it was a RAM issue (i ran memtest86+ and got thousands of errors shortly after the test started), my Crucial M4 SSD stopped booting after the latest BSOD.

    The firmware was already the latest, updated a few days ago, but that didn't help. Both components (the RAM and the SSD) are just 3 months old and worked fine for about 2 months. I had Hard Disk Sentinel Pro installed and the SSD had a 100% health indication.

    Can the SSD failure be related to the RAM?
     
  6. mualarung76

    mualarung76 New Member

    Joined:
    Nov 13, 2012
    Messages:
    4
    Likes Received:
    0
    up up cho tin lên top!
     
  7. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
    Try running HDtune (link to download in signature) for 1 or 2 days - if the perf bar goes too low then it could be your SSD's problem.
     
  8. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    I was wondering if this set of dumps would become the poster child for SSD issues (it had that "feel" to me).

    Fix the RAM issues (start with step 6b in this procedure: Memory Diagnostics )
    Once they are fixed, see if that stops the BSOD's. If not, then we can look at the SSD again.
     
  9. Versus13

    Versus13 New Member

    Joined:
    Nov 18, 2012
    Messages:
    10
    Likes Received:
    0
    Actually i saw the HDTune's link in your signature before and had it run for 1,5 days or so. I ran all tests and everything looked fine. If i get the pc to boot i'll try it again.

    From what i've read, Crucial advises a power cycle when the BIOS fails to recognize the drive. I'll try that when i get back home, although i had the BSOD's happening way before the drive fail.

    Thanks guys.
     
  10. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
    Alright, try running HDTune once more if you can - it's better to get multiple tests.

    The Power Cycle looks like an answer though I'm not entirely sure (me having never used an SSD before).
     
  11. Versus13

    Versus13 New Member

    Joined:
    Nov 18, 2012
    Messages:
    10
    Likes Received:
    0
    Yesterday the pc booted perfectly fine again and i was able to run HDTune all day long. No warning signs there whatsoever.

    Today i was finally able to play around with the RAM's. I took one of them off and tried the other one on both slots. Both tests were faulty under memtest86+. I'm trying the remaining one for over 1h now and no errors thus far (the errors used to pop out of memtest86+ 1 second after i started it). I'm fairly confident the BSOD's were due to the faulty RAM.

    Thanks for the help guys.
     
  12. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
    Yes, if that's the case, they probably were.

    Get a whole new RAM set and try it out (or, for starters, use RAM sticks that you know to be working properly from another motherboard) with memtest - if it's the RAM problem then the new sticks should all be fine.
     

Share This Page

Loading...