BSOD death problem please help

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by smitco, Jan 8, 2012.

  1. smitco

    smitco New Member

    Joined:
    Jan 8, 2012
    Messages:
    2
    Likes Received:
    0
  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Two memory management;
    Code:
    BugCheck 1A, {41201, fffff683ff758108, 7c3000001d83b005, fffffa800748bac0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+14382 )
    Followup: MachineOwner
    [U][B][COLOR=#ff0000]MEMORY_MANAGEMENT (1a)[/COLOR][/B][/U]
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041201, The subtype of the bugcheck.
    Arg2: fffff683ff758108
    Arg3: 7c3000001d83b005
    Arg4: fffffa800748bac0
    Code:
    BugCheck 1A, {41790, fffffa800059be30, ffff, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
    Followup: MachineOwner
    [B][U][COLOR=#ff0000]MEMORY_MANAGEMENT (1a)[/COLOR][/U][/B]
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041790, The subtype of the bugcheck.
    Arg2: fffffa800059be30
    Arg3: 000000000000ffff
    Arg4: 0000000000000000
    And one Memory Corruption:
    Code:
    BugCheck 4E, {99, 398b4, 2, 39cf3}
    [COLOR=#ff0000][U][B]Probably caused by : memory_corruption[/B][/U][/COLOR] ( nt!MiBadShareCount+4c )
    Followup: MachineOwner
    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000099, A PTE or PFN is corrupt
    Arg2: 00000000000398b4, page frame number
    Arg3: 0000000000000002, current page state
    Arg4: 0000000000039cf3, 0
    Please;
    Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD.
    Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
    See this Guide to using Memtest 86+
    And since PFN was identified and associated with memory corruption you should also run chkdsk on your system drive
    Open an elevated command prompt and type
    chkdsk C: /R
    hit enter
    answer yes "Y" to the prompt
    reboot
    let it complete all five stages and if you miss the summary at the end you can examine the log file in Event Viewer.
    Regards
    Randy
     

Share This Page

Loading...