Random BSOD

Page 1 of 7 123 ... LastLast

  1. Posts : 30
    Windows 7 Ultimate X64
       #1

    Random BSOD


    Been dealing with this for the past 2 months. One memory stick failed memtest, RMA'd, and harddrive failed Seatools, RMA'd. Still getting problems...

    Today - uninstalled and reinstalled graphics drivers, USB drivers, and mouse drivers. Still getting random BSOD and usually nothing very taxing (surfing, working in Word/Excel documents, etc.). I do not play games on here anymore as I never know when things are going to crash.

    Attached is the requested dump file along with CPU-Z text file. Anything else, please let me know. Included 4 minidumps I have gotten this afternoon, with differing codes. Anything else you need, please let me know.

    Thanks in advance for your help!
      My Computer


  2. Posts : 10,994
    Win 7 Pro 64-bit
       #2

    Hello mp1cass0 and welcome to Seven Forums.

    From the dmp files you've submitted it still appears to be a memory related issue which led to a stop 0x05A "critical service failed" issue. I know you've RMAed your memory sticks but have you tested each individual slot? Also, have you checked for damaged or corrupt system files? You can run a system file checker scan from an elevated command prompt (option two.) If problems are found, run the scan 3 times and reboot the computer after each scan.

    SFC /SCANNOW Command - System File Checker

    You may also want to run through these troubleshooting steps, particularly the part about running a clean boot (step 3).

    Troubleshooting Steps for Windows 7

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: 0000000000000002, A list entry was corrupt
    Arg2: 000000000019929b, entry in list being removed
    Arg3: 000000000022ffff, highest physical page number
    Arg4: 0000000000000001, reference count of entry being removed
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_2
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002c9487d to fffff80002c841c0
    
    STACK_TEXT:  
    fffff880`0330fac8 fffff800`02c9487d : 00000000`0000004e 00000000`00000002 00000000`0019929b 00000000`0022ffff : nt!KeBugCheckEx
    fffff880`0330fad0 fffff800`02cbc5cc : 00000000`00000000 fffff800`02daf1de 00000000`00000000 fffffa80`00000007 : nt!MiUnlinkPageFromLockedList+0x8d
    fffff880`0330fb50 fffff800`02cbd078 : 00000000`00000000 fffffa80`088ae010 fffffa80`088ae0a8 00000000`00000000 : nt!MiGatherMappedPages+0x104
    fffff880`0330fc50 fffff800`02f1ae6a : fffffa80`07482400 00000000`00000080 fffffa80`069e25f0 00000000`00000000 : nt!MiMappedPageWriter+0x198
    fffff880`0330fd40 fffff800`02c74ec6 : fffff880`009ea180 fffffa80`07482400 fffff880`009f4f80 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0330fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiUnlinkPageFromLockedList+8d
    fffff800`02c9487d cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+8d
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x4E_2_VRF_nt!MiUnlinkPageFromLockedList+8d
    
    BUCKET_ID:  X64_0x4E_2_VRF_nt!MiUnlinkPageFromLockedList+8d
    
    Followup: MachineOwner
      My Computer


  3. Posts : 30
    Windows 7 Ultimate X64
    Thread Starter
       #3

    Tried to run sfcnow twice and got BSOD's both times. Going to run memtest+ today and test out the memory cards. Once I have done (or at least attempted multiple times), will repost what I find, along with any dmp files created.
      My Computer


  4. Posts : 10,994
    Win 7 Pro 64-bit
       #4

    Take as much time as you need. I'll keep monitoring this thread.

    It's my understanding that memtest may not distinguish between a bad memory stick and a bad slot. If I remember correctly you have 8GB RAM installed. If the motherboard has only two slots and you're running (2 x 4GB) RAM, put one 4GB stick in slot one. Boot your computer. If it boots the stick and slot are probably good. Test the remaining stick. If they both check out, test slot two the same way, one stick at a time.

    If you have 4 slots and you're running (2 x 4GB) RAM it's a bit more complicated. Depending on the mobo, slots 1 and 3 may be the primary slots for two sticks rather than slots 1 and 2. Check the mobo owners manual for proper configuration. But you should still be able to check individual sticks in slot one and dual sticks in slots 1 and 3 or 2 and 4 (or whichever slots are paired together.)
      My Computer


  5. Posts : 30
    Windows 7 Ultimate X64
    Thread Starter
       #5

    ASUS M4A89GTD PRO/USB3 - 4 slots on motherboard. Planning to run 2 slots together, then if they fail, will go 1-by-1. Find a slot/stick that does not fail and use that as my reference, testing each slot/each stick.

    Ran SFC and keeps telling me "Windows Resource Protection found corrupt files but was unable to fix some of them." Will run repair from Windows disc and report back findings as they come.

    Thanks in advance for all of your help!
      My Computer


  6. Posts : 30
    Windows 7 Ultimate X64
    Thread Starter
       #6

    Ran repair, 1st time said it found and fixed corrupted files, 2nd time, no problems found. 2 passes complete on memtest, 80% done on 3rd, no problems on slots 1&3. Going to do 7 passes unless you suggest otherwise.

    Thanks in advance.
      My Computer


  7. Posts : 10,994
    Win 7 Pro 64-bit
       #7

    The folks on this Forum most experienced with Memtest usually recommend that it run overnight. That seems to give it about 8 passes. I think 7 passes should be a pretty good indicator.
      My Computer


  8. Posts : 30
    Windows 7 Ultimate X64
    Thread Starter
       #8

    11 passes on slots 1&3, with no errors. Switching to 2&4 and letting it run all day/night as well to see. Will report findings tomorrow.
      My Computer


  9. Posts : 30
    Windows 7 Ultimate X64
    Thread Starter
       #9

    Update - kept getting BSOD, freezes of my keyboard/USB, and loss of internet. Uninstalled and reinstalled drivers for mouse/keyboard/network card, with no improvement. Did a clean install of Windows and have added everything back in other than phone software (iTunes and Android SDK).

    Attached is requested file. To date, memtest has only been used on slots 1&3, with no problems (recommended slots). Should I also try running on 2&4, just to see?
      My Computer


  10. Posts : 10,994
    Win 7 Pro 64-bit
       #10

    Just to make sure I'm understanding correctly, even after doing a clean install you're still getting BSODs?

    I'm going to ask some more folks for their input. Perhaps they'll see something I missed. It may take a while due to different time zones but hang in there.
      My Computer


 
Page 1 of 7 123 ... LastLast

  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 01:37.
Find Us