3 BSOD in a row; New SSD, RAM and Video Card

Page 1 of 3 123 LastLast

  1. Posts : 26
    Windows 7
       #1

    3 BSOD in a row; New SSD, RAM and Video Card


    I recently (last weekend) replaced my RAM, OS HDD and Video Card. Today is the first time I've experienced any problems but I've had three BSOD in a row. The first two were while watching videos in VLC and the third was while trying to post here. Attached is my system info from the sevenforums tool for the first 2 BSOD problems.
      My Computer

  2.    #2

    Code:
    BugCheck 24, {1904fb, fffff8800bf13ed8, fffff8800bf13730, fffff800038a1915}
    
    Probably caused by : ntkrnlmp.exe ( nt!FsRtlLookupPerFileObjectContext+a5 )
    Code:
    Usual causes:  Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
    Code:
    2: kd> .trap fffff8800bf13f80;knL
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=88fffa80105a8da8 rbx=0000000000000000 rcx=fffffa80508ba4b8
    rdx=fffffa800abade70 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800038a1915 rsp=fffff8800bf14110 rbp=0000000000000000
     r8=0000000000000000  r9=fffffa801fe53ac0 r10=fffffa800ab98b90
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    nt!FsRtlLookupPerFileObjectContext+0xa5:
    fffff800`038a1915 48395810        cmp     qword ptr [rax+10h],rbx ds:88fffa80`105a8db8=????????????????
      *** Stack trace for last set context - .thread/.cxr resets it
     # Child-SP          RetAddr           Call Site
    00 fffff880`0bf14110 fffff880`012eab1f nt!FsRtlLookupPerFileObjectContext+0xa5
    01 fffff880`0bf14150 fffff880`012e8852 fltmgr!FltpGetStartingCallbackNode+0x3f
    02 fffff880`0bf141e0 fffff800`038a06a3 fltmgr!FltpPreFsFilterOperation+0xa2
    03 fffff880`0bf14270 fffff800`03b56fe4 nt!FsFilterPerformCallbacks+0xd3
    04 fffff880`0bf142d0 fffff800`038c2427 nt!FsRtlAcquireFileForCcFlushEx+0xd0
    05 fffff880`0bf14570 fffff800`038c19bc nt!MmFlushSection+0x1c3
    06 fffff880`0bf14630 fffff880`014dd654 nt!CcFlushCache+0x7bc
    07 fffff880`0bf14730 fffff880`014d34cd Ntfs!NtfsFlushUserStream+0xb4
    08 fffff880`0bf147b0 fffff880`014dbf48 Ntfs!NtfsFlushVolume+0x2ad
    09 fffff880`0bf148e0 fffff880`014dc63c Ntfs!NtfsCommonFlushBuffers+0x444
    0a fffff880`0bf149c0 fffff880`012e9bcf Ntfs!NtfsFsdFlushBuffers+0x104
    0b fffff880`0bf14a30 fffff880`012e86df fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    0c fffff880`0bf14ac0 fffff800`03b8ba9b fltmgr!FltpDispatch+0xcf
    0d fffff880`0bf14b20 fffff800`03b20781 nt!IopSynchronousServiceTail+0xfb
    0e fffff880`0bf14b90 fffff800`0387fe13 nt!NtFlushBuffersFile+0x171
    0f fffff880`0bf14c20 00000000`77c0176a nt!KiSystemServiceCopyEnd+0x13
    10 00000000`0191f548 00000000`00000000 0x77c0176a
    The last instruction which was called, and where the interrupt handler broke in to save the context of the thread, and then produce a bugcheck was FsRtlLookupPerFileObjectContext, which is used by filter drivers to receive the context of a previous file object; a file object can refer to an actual file or physical hard disk. The IRQL level is fine here, so no functions were being called at the incorrect IRQL level.

    Code:
    2: kd> !irql
    Debugger saved IRQL for processor 0x2 -- 1 (APC_LEVEL)
    For crashes involving filter drivers, it is usually related to anti-virus programs or programs which perform interaction with FSD drivers.

    From another bugcheck (Stop 0x1E):

    Code:
    0: kd> lmvm sptd
    start             end                 module name
    fffff880`0108b000 fffff880`011fe000   sptd     T (no symbols)           
        Loaded symbol image file: sptd.sys
        Image path: sptd.sys
        Image name: sptd.sys
        Timestamp:        Sat Mar 03 16:45:52 2012 (4F524AC0)
        CheckSum:         0008CE54
        ImageSize:        00173000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Arc said:
    Download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

    • Double click to open it.
    • Click this button only:
    • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
    Daemon Tools uses a driver called sptd.sys, which is known to cause BSODs with Windows 7. It is recommend you remove this program, and use Windows own in-built features or ImgBurn.

    Reduce the number of programs at startup, to avoid any driver or program conflicts:
      My Computer


  3. Posts : 26
    Windows 7
    Thread Starter
       #3

    Hey BlueRobot,

    Thanks. I uninstalled daemon tools as per your suggestion and used the SPTD installer to fully uninstall SPTD. I am confused as to if there is any action I should take with regards the first bugcheck. Currently I don't have an antivirus installed. I'm just running Windows Defender (Which is now having errors starting since the SPTD and Daemon tools uninstall...related?) and Microsoft Security Essentials.

    Thanks
    -Rob
      My Computer


  4. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #4

    If you have installed Microsoft Security Essential for your anti virus it should of turned off the built in Defender.

    Go to Start Orb and type in Defender and then tick on it. I should indicate it is turned off.
    Have you completed all Windows Updates? This should be done.
      My Computer


  5. Posts : 26
    Windows 7
    Thread Starter
       #5

    Layback Bear said:
    If you have installed Microsoft Security Essential for your anti virus it should of turned off the built in Defender.

    Go to Start Orb and type in Defender and then tick on it. I should indicate it is turned off.
    Have you completed all Windows Updates? This should be done.
    Ah, okay. It is turned off. For some reason it autostarted at my last reboot.

    -Thanks
      My Computer

  6.    #6

    Any more problems? :)
      My Computer


  7. Posts : 26
    Windows 7
    Thread Starter
       #7

    x BlueRobot said:
    Any more problems? :)
    Hey, thanks for following up. Thinks looked to be going fine for a while but today I got another bluescreen, all the goods attached. I wasnt doing anything out of the ordinary, just web browsing and boom.

    Anyway, I asked a friend and he seems to think that it's because I havent manually set the voltage and timing for my new RAM, but I've read that "Auto" settings are fine and the voltage and timing just effects the performance. Anyway, thanks.

    Edit: mere moments after posting this I got another blue screen while shutting down my computer that said SYSTEM SERVICE EXCEPTION 0x0000003b

    Another edit: Since my friend insisted, my RAM in now running at the recommended timings, voltage and frequency. So if that was indeed the problem, hopefully it wont be anymore
    Last edited by Bizarro181; 05 Oct 2013 at 22:59.
      My Computer

  8.    #8

    Okay, hopefully your system will remain stable, but I'll look at the dump file for your nonetheless.
      My Computer

  9.    #9

    Code:
    BugCheck 1A, {5002, fffff70001080000, 3970, b003971fffffffe}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2902c )
    Code:
    6: kd> !stack
    Call Stack : 8 frames
    ## Stack-Pointer    Return-Address   Call-Site       
    00 fffff88009eee798 fffff800038efd34 nt!KeBugCheckEx+0 
    01 fffff88009eee7a0 fffff80003897ece nt!MiCompleteProtoPteFault+49e44 (perf)
    02 fffff88009eee830 fffff800038a5d05 nt!MiResolveDemandZeroFault+93e 
    03 fffff88009eee920 fffff800038a44f3 nt!MiResolveProtoPteFault+4f5 
    04 fffff88009eee9b0 fffff80003894179 nt!MiDispatchFault+1c3 
    05 fffff88009eeeac0 fffff80003885cae nt!MmAccessFault+359 <-- Demand Zero Fault?
    06 fffff88009eeec20 000000006ec382ed nt!KiPageFault+16e
    The subtype error of this bugcheck is not publicly documented by Microsoft, but looking at the call stack, I see regular maintenance going on. The most interesting frames are 2 and 3. Prototype PTES and PTEs are the same, apart from Prototype PTEs add a additional layer to address translation. So, from what has happened, a demand zero Prototype PTE was accessed, and then the Access Fault handler was executed to resolve this fault, by writing a page with 0's.

    Do you have the latest WHQL version of your nVidia graphics card driver installed?
      My Computer


  10. Posts : 26
    Windows 7
    Thread Starter
       #10

    Hey BlueRobot,

    My nVidia drivers are current. I just ran the update check now and they are from 9/19/2013 and listed as 327.23 WHQL on the nividia site.

    Thanks
    -Rob
      My Computer


 
Page 1 of 3 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 16:43.
Find Us