BSOD Problem! See Attached File!


  1. Posts : 1
    Windows 7 Ultimate 64x
       #1

    BSOD Problem! See Attached File!


    Attached is the SF Diagnostic Tool i run today. Please do help me?

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 50
    BCP1: FFFFF900C00C0770
    BCP2: 0000000000000000
    BCP3: FFFFF96000726D15
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\021514-17050-01.dmp
    C:\Users\Mak\AppData\Local\Temp\WER-28267-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi markbartowski.

    Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.
    Code:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Learn how to install Windows 7 Service Pack 1 (SP1)
    Service Pack and Update Center - Microsoft Windows

    Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then 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.

    Also test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

    Let us know the results.
    _____________________________________________________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff900c00c0770, 0, fffff96000726d15, 0}
    
    
    Could not read faulting driver name
    Probably caused by : cdd.dll ( cdd!DrvAssociateSharedSurface+51 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff900c00c0770, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff96000726d15, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb00e0
    GetUlongFromAddress: unable to read from fffff80002eb0198
     fffff900c00c0770 
    
    FAULTING_IP: 
    cdd!DrvAssociateSharedSurface+51
    fffff960`00726d15 399f50070000    cmp     dword ptr [rdi+750h],ebx
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  dwm.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    TRAP_FRAME:  fffff88006295920 -- (.trap 0xfffff88006295920)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff96000726cc4 rbx=0000000000000000 rcx=fffff900c0749ce8
    rdx=00000000400018c0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff96000726d15 rsp=fffff88006295ab0 rbp=fffff900c0749ce8
     r8=000000006f12135a  r9=0000000000000040 r10=000000000391f760
    r11=fffff88006295b08 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cdd!DrvAssociateSharedSurface+0x51:
    fffff960`00726d15 399f50070000    cmp     dword ptr [rdi+750h],ebx ds:00000000`00000750=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002cf91e4 to fffff80002c79f00
    
    STACK_TEXT:  
    fffff880`062957b8 fffff800`02cf91e4 : 00000000`00000050 fffff900`c00c0770 00000000`00000000 fffff880`06295920 : nt!KeBugCheckEx
    fffff880`062957c0 fffff800`02c77fee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42907
    fffff880`06295920 fffff960`00726d15 : 00000000`000006a0 00000000`00000000 00000000`6f121312 00000000`00000020 : nt!KiPageFault+0x16e
    fffff880`06295ab0 fffff960`002277bd : 00000000`00000000 fffff900`c2b3f260 00000000`0391f800 00000040`00000215 : cdd!DrvAssociateSharedSurface+0x51
    fffff880`06295b10 fffff960`0024a969 : 00000000`00000001 fffff880`06295c60 00000000`0391f800 00000000`00007b3c : win32k!GreSetRedirectionSurfaceSignaling+0x125
    fffff880`06295b60 fffff800`02c79153 : fffffa80`0f75d9a0 fffffa80`0f75d060 fffffa80`00000000 fffffa80`0f75d060 : win32k!NtGdiHLSurfSetInformation+0x209
    fffff880`06295be0 000007fe`ff9e4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0391f738 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`ff9e4efa
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    cdd!DrvAssociateSharedSurface+51
    fffff960`00726d15 399f50070000    cmp     dword ptr [rdi+750h],ebx
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  cdd!DrvAssociateSharedSurface+51
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: cdd
    
    IMAGE_NAME:  cdd.dll
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bde94
    
    IMAGE_VERSION:  6.1.7600.16385
    
    FAILURE_BUCKET_ID:  X64_0x50_cdd!DrvAssociateSharedSurface+51
    
    BUCKET_ID:  X64_0x50_cdd!DrvAssociateSharedSurface+51
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x50_cdd!drvassociatesharedsurface+51
    
    FAILURE_ID_HASH:  {f68106cd-f369-54d5-12e1-a446775e9bb6}
    
    Followup: MachineOwner
    ---------
      My Computer


 

  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 23:52.
Find Us