BSOD even in safe mode

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Water640, Dec 8, 2011.

  1. Water640

    Water640 New Member

    Joined:
    Dec 8, 2011
    Messages:
    24
    Likes Received:
    0
    Hey everybody,

    So last night I updated my computer (which I don't often do). Then today I go to play a game and I bsod. Try again, same thing. I boot in safe mode. Bsod again. I boot in safe mode once again and revert to a restore point from three days ago. I go to play the game again, bsod.

    There's only the most recent bsod saved from all of it, which I've uploaded here:
    http://dl.dropbox.com/u/36215190/dump.zip

    I didn't write down the information to "find solutions" for, unfortunately, suffice to say that the error given was just BlueScreen.

    The updates I installed were:
    KB2588516
    KB2617657
    KB2620704
    KB2641690
    KB890830
    As well as a small handful of office 2010 updates.
    I searched and found nothing relating bsod's and these updates to my situation.

    Any help would be greatly appreciated.
    Thanks!
     
  2. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,873
    Likes Received:
    284
    Hi Water640 and Welcome to The Forum.

    STOP 0x0000004E: PFN_LIST_CORRUPT
    Usual causes:
    Device driver, ?memory.

    Your dump file lists ntkrnlmp.exe as the probable cause. This is a Windows System file and for it to be the cause of your crash is highly unlikely.
    Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes. Random stop codes can often indicate hardware issues.

    As a Priority:

    Please see: http://windows7forums.com/blue-screen-death-bsod/38837-how-ask-help-bsod-problem.html Following Method 2:

    Download and run the SF Diagnostics Tool. Right click the SF Diag tool and select Run as Administrator before running. When the reports have been created, zip them up and attach to a post.


    Download and run CPU-Z. Take screenshots**/snips of the Mainboard tab, Memory tab and all the slot #'s under the SPD tab.
    Go to Post Reply, click on the Go Advanced button and attach the screenshots**/snips to your post for all the RAM experts to see by using the paper clip you will find on the top toolbar. Do not zip them up.
    **If screenshots, please crop.


    The sptd.sys driver is notorious for causing BSOD's with Windows 7. It's a driver used and installed along with Daemon Tools and Alcohol 120 which you'll also have to uninstall.
    Then use the correct (32bit or 64bit) download from Duplex Secure - Downloads to uninstall the SPTD.SYS driver.
    Make sure to select the uninstall button! DO NOT SELECT INSTALL!!


    Bugcheck Analysis:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {7, 13ecff, 1, 0}
    
    Unable to load image \SystemRoot\System32\Drivers\aswTdi.SYS, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for aswTdi.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
    Unable to load image \SystemRoot\system32\drivers\bckd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for bckd.sys
    *** ERROR: Module load completed but symbols could not be loaded for bckd.sys
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+175b6 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000007, A driver has unlocked a page more times than it locked it
    Arg2: 000000000013ecff, page frame number
    Arg3: 0000000000000001, current share count
    Arg4: 0000000000000000, 0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  digsby-app.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80003327108 to fffff800032c7c40
    
    STACK_TEXT:  
    fffff880`09e253b8 fffff800`03327108 : 00000000`0000004e 00000000`00000007 00000000`0013ecff 00000000`00000001 : nt!KeBugCheckEx
    fffff880`09e253c0 fffff800`03338856 : 0000000f`ffffa800 fffff880`012a507d fffffa80`0542b255 fffff880`012a507d : nt! ?? ::FNODOBFM::`string'+0x175b6
    fffff880`09e25400 fffff800`032cae48 : fffffa80`050f0004 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x37875
    fffff880`09e25490 fffff800`032ad876 : fffffa80`050ffae0 00000000`00000000 fffffa80`05149460 00000000`00000000 : nt!IopfCompleteRequest+0x168
    fffff880`09e25580 fffff880`01295b26 : fffffa80`050ffc88 00000000`00000002 fffffa80`050ffae0 fffffa80`0515ac50 : nt!IopInvalidDeviceRequest+0x16
    fffff880`09e255b0 fffffa80`050ffc88 : 00000000`00000002 fffffa80`050ffae0 fffffa80`0515ac50 00000000`00000002 : aswTdi+0x1b26
    fffff880`09e255b8 00000000`00000002 : fffffa80`050ffae0 fffffa80`0515ac50 00000000`00000002 fffff880`012aca3b : 0xfffffa80`050ffc88
    fffff880`09e255c0 fffffa80`050ffae0 : fffffa80`0515ac50 00000000`00000002 fffff880`012aca3b fffffa80`050ffae0 : 0x2
    fffff880`09e255c8 fffffa80`0515ac50 : 00000000`00000002 fffff880`012aca3b fffffa80`050ffae0 fffffa80`0521a180 : 0xfffffa80`050ffae0
    fffff880`09e255d0 00000000`00000002 : fffff880`012aca3b fffffa80`050ffae0 fffffa80`0521a180 00000000`00000000 : 0xfffffa80`0515ac50
    fffff880`09e255d8 fffff880`012aca3b : fffffa80`050ffae0 fffffa80`0521a180 00000000`00000000 fffffa80`050ffae0 : 0x2
    fffff880`09e255e0 fffffa80`050ffae0 : fffffa80`0521a180 00000000`00000000 fffffa80`050ffae0 fffffa80`0521a180 : bckd+0x8a3b
    fffff880`09e255e8 fffffa80`0521a180 : 00000000`00000000 fffffa80`050ffae0 fffffa80`0521a180 fffffa80`045976a8 : 0xfffffa80`050ffae0
    fffff880`09e255f0 00000000`00000000 : fffffa80`050ffae0 fffffa80`0521a180 fffffa80`045976a8 fffffa80`050ffae0 : 0xfffffa80`0521a180
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+175b6
    fffff800`03327108 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+175b6
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    FAILURE_BUCKET_ID:  X64_0x4E_7_nt!_??_::FNODOBFM::_string_+175b6
    
    BUCKET_ID:  X64_0x4E_7_nt!_??_::FNODOBFM::_string_+175b6
    
    Followup: MachineOwner
    ---------
    
    1: kd> msmtn
    *** ERROR: Module load completed but symbols could not be loaded for intelide.sys
    *** WARNING: Unable to verify timestamp for amdxata.sys
    *** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
    *** WARNING: Unable to verify timestamp for TVALZ_O.SYS
    *** ERROR: Module load completed but symbols could not be loaded for TVALZ_O.SYS
    *** WARNING: Unable to verify timestamp for spldr.sys
    *** ERROR: Module load completed but symbols could not be loaded for spldr.sys
    *** WARNING: Unable to verify timestamp for aswMonFlt.sys
    *** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
    *** WARNING: Unable to verify timestamp for aswFsBlk.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswFsBlk.SYS
    *** WARNING: Unable to verify timestamp for peauth.sys
    *** ERROR: Module load completed but symbols could not be loaded for peauth.sys
    *** WARNING: Unable to verify timestamp for secdrv.SYS
    *** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
    *** WARNING: Unable to verify timestamp for spsys.sys
    *** ERROR: Module load completed but symbols could not be loaded for spsys.sys
    *** WARNING: Unable to verify timestamp for SynTP.sys
    *** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
    *** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
    *** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
    *** WARNING: Unable to verify timestamp for aswRdr.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswRdr.SYS
    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    *** WARNING: Unable to verify timestamp for asz6cmvx.SYS
    *** ERROR: Module load completed but symbols could not be loaded for asz6cmvx.SYS
    *** WARNING: Unable to verify timestamp for aswSP.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
    *** WARNING: Unable to verify timestamp for rimmpx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for rimmpx64.sys
    *** WARNING: Unable to verify timestamp for rimspx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for rimspx64.sys
    *** WARNING: Unable to verify timestamp for netw5v64.sys
    *** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
    *** WARNING: Unable to verify timestamp for rixdpx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for rixdpx64.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *** WARNING: Unable to verify timestamp for drmk.sys
    *** ERROR: Module load completed but symbols could not be loaded for drmk.sys
    *** WARNING: Unable to verify timestamp for hamachi.sys
    *** ERROR: Module load completed but symbols could not be loaded for hamachi.sys
    *** WARNING: Unable to verify timestamp for RtHDMIVX.sys
    *** ERROR: Module load completed but symbols could not be loaded for RtHDMIVX.sys
    *** WARNING: Unable to verify timestamp for Lycosa.sys
    *** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
    *** WARNING: Unable to verify timestamp for SmSerl64.sys
    *** ERROR: Module load completed but symbols could not be loaded for SmSerl64.sys
    *** WARNING: Unable to verify timestamp for RTKVHD64.sys
    *** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
    *** WARNING: Unable to verify timestamp for TSDDD.dll
    *** ERROR: Module load completed but symbols could not be loaded for TSDDD.dll
     
    #2 Elmer, Dec 9, 2011
    Last edited: Dec 9, 2011
  3. Water640

    Water640 New Member

    Joined:
    Dec 8, 2011
    Messages:
    24
    Likes Received:
    0
    SPD slot#2. SPD slot#1. Memory. Mainboard.
    Here are the screen shots from CPU-Z
    Attached is the diagnostic reports.
    http://dl.dropbox.com/u/36215190/Reports.zip

    I also just uninstalled Daemon tools and uninstalled sptd.sys driver and am now restarting my computer.

    Thank you so much for your help, Elmer!
     
  4. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,873
    Likes Received:
    284
    #4 Elmer, Dec 9, 2011
    Last edited: Dec 9, 2011
  5. Water640

    Water640 New Member

    Joined:
    Dec 8, 2011
    Messages:
    24
    Likes Received:
    0
    Hamachi wouldn't cause it, I'm pretty sure. I haven't even used it in about a month, let alone affecting anything in safemode.
    The link you gave wouldn't work due to "incompatable hardware" but I went into my device manager to update it and it turns out there was a new driver available, so I got that update.
    I haven't used the Razer mouse in quite a while, and I've had the Lycosa keyboard for about two years.

    Now that I've updated my graphics driver we'll see if that was the problem. If another BSOD occurs I'll be sure to update here and to get all the information from the cause.

    Thanks again for your help, man.
     
  6. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,873
    Likes Received:
    284
    You might not be using it but it's loading drivers into your system at start up.
     
  7. Water640

    Water640 New Member

    Joined:
    Dec 8, 2011
    Messages:
    24
    Likes Received:
    0
    Fascinating. Well if I get another blue screen I'll upload the .dmp and then disable it, because I've had it for quite a while, too and I've never heard of it causing anything like this before...
     

Share This Page

Loading...