1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

BSoD about twice a day, help me decipher the dump file!

Discussion in 'Windows 7' started by Panzerpung, 2014/09/22.

  1. 2014/09/22
    Panzerpung

    Panzerpung Inactive Thread Starter

    Joined:
    2014/09/22
    Messages:
    16
    Likes Received:
    0
    Hi, I've been getting a BSoD every now and then with no symptoms as I can see. Temperatures are fine, and I'm not necessarily running heavy programs at times when it starts dumping. Please help me locate the problems and whatever action I need to take. :D

    Here is the dump file analysis:

    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
    Machine Name:
    Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`03043e50
    Debug session time: Mon Sep 22 21:29:58.182 2014 (UTC + 2:00)
    System Uptime: 0 days 1:21:19.103
    Loading Kernel Symbols
    .

    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.

    ..............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 3B, {c0000005, fffff960002cc9ed, fffff88009038110, 0}

    Probably caused by : win32k.sys ( win32k!MulAssociateSharedSurface+15 )

    Followup: MachineOwner
    ---------

    6: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff960002cc9ed, Address of the instruction which caused the bugcheck
    Arg3: fffff88009038110, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    win32k!MulAssociateSharedSurface+15
    fffff960`002cc9ed 4c8b98300d0000 mov r11,qword ptr [rax+0D30h]

    CONTEXT: fffff88009038110 -- (.cxr 0xfffff88009038110;r)
    rax=0000000000000000 rbx=fffff900c2269570 rcx=fffffa8008f24cc0
    rdx=0000000040002380 rsi=fffff900c2479ce8 rdi=fffff900c2269608
    rip=fffff960002cc9ed rsp=fffff88009038ae0 rbp=000000002d121a77
    r8=000000002d121a77 r9=00000040000000e8 r10=0000000000000000
    r11=fffff88009038b08 r12=fffff900c010e010 r13=0000000040002380
    r14=000000000287b5b0 r15=0000000000000001
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    win32k!MulAssociateSharedSurface+0x15:
    fffff960`002cc9ed 4c8b98300d0000 mov r11,qword ptr [rax+0D30h] ds:002b:00000000`00000d30=????????????????
    Last set context:
    rax=0000000000000000 rbx=fffff900c2269570 rcx=fffffa8008f24cc0
    rdx=0000000040002380 rsi=fffff900c2479ce8 rdi=fffff900c2269608
    rip=fffff960002cc9ed rsp=fffff88009038ae0 rbp=000000002d121a77
    r8=000000002d121a77 r9=00000040000000e8 r10=0000000000000000
    r11=fffff88009038b08 r12=fffff900c010e010 r13=0000000040002380
    r14=000000000287b5b0 r15=0000000000000001
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    win32k!MulAssociateSharedSurface+0x15:
    fffff960`002cc9ed 4c8b98300d0000 mov r11,qword ptr [rax+0D30h] ds:002b:00000000`00000d30=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: dwm.exe

    CURRENT_IRQL: 0

    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

    LAST_CONTROL_TRANSFER: from fffff960002777bd to fffff960002cc9ed

    STACK_TEXT:
    fffff880`09038ae0 fffff960`002777bd : 00000000`00000000 00000000`2d121a77 00000000`039ff6e0 fffff900`c010e010 : win32k!MulAssociateSharedSurface+0x15
    fffff880`09038b10 fffff960`0029a969 : 00000000`00000001 fffff880`09038c60 00000000`039ff6e0 00000000`0000a9ff : win32k!GreSetRedirectionSurfaceSignaling+0x125
    fffff880`09038b60 fffff800`02e75953 : fffffa80`06e983b0 fffff880`09038c60 00000000`003835e0 00000000`0dca37cc : win32k!NtGdiHLSurfSetInformation+0x209
    fffff880`09038be0 000007fe`fdad4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`039ff618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fdad4efa


    FOLLOWUP_IP:
    win32k!MulAssociateSharedSurface+15
    fffff960`002cc9ed 4c8b98300d0000 mov r11,qword ptr [rax+0D30h]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: win32k!MulAssociateSharedSurface+15

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0

    IMAGE_VERSION: 6.1.7600.16385

    STACK_COMMAND: .cxr 0xfffff88009038110 ; kb

    FAILURE_BUCKET_ID: X64_0x3B_win32k!MulAssociateSharedSurface+15

    BUCKET_ID: X64_0x3B_win32k!MulAssociateSharedSurface+15

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:x64_0x3b_win32k!mulassociatesharedsurface+15

    FAILURE_ID_HASH: {08b97eea-ad52-6762-8e6c-277f3c48177d}

    Followup: MachineOwner
    ---------
     
    Panzerpung,
    #1
  2. 2014/09/22
    Panzerpung

    Panzerpung Inactive Thread Starter

    Joined:
    2014/09/22
    Messages:
    16
    Likes Received:
    0
    Updated info: I was trying to re-install the newest nvidia driver for 780ti and got a unexpected shutdown right of the bat. No BSoD. I already have the driver but I thought I'd just try.
     
    Panzerpung,
    #2


  3. to hide this advert.

  4. 2014/09/22
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    7,157
    Likes Received:
    501
    Try a Rollback to previous Graphics driver and see if that was the cause. Neil.
     
    retiredlearner,
    #3
  5. 2014/09/22
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,901
    Likes Received:
    510
    Hi Panzerpung, Welcome to Windowsbbs! :)

    Your dump data log indicates the win32k.sys file as being the cause of the blue screens.

    See this link for a possible hotfix that could resolve the issue, Stop error 0x50 in the Win32k.sys driver after you install a font update.

    Also please enter your System Details. It helps us in answering your questions.

    Note: A common error is to forget to show your System Details in your profile:

    Make sure to do the above when entering your System Details, thanks.
     
    Evan Omo,
    #4
  6. 2014/09/23
    Panzerpung

    Panzerpung Inactive Thread Starter

    Joined:
    2014/09/22
    Messages:
    16
    Likes Received:
    0
    Updated system details!
     
    Panzerpung,
    #5
  7. 2014/09/23
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,901
    Likes Received:
    510
    You forgot the last step.

     
    Evan Omo,
    #6
  8. 2014/09/23
    Panzerpung

    Panzerpung Inactive Thread Starter

    Joined:
    2014/09/22
    Messages:
    16
    Likes Received:
    0
    Test, it should show now.

    I'll assume you guys can see it. Im really grateful for all the help I can get. Would a clean w7 install help at all?
     
    Panzerpung,
    #7
  9. 2014/09/23
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,901
    Likes Received:
    510
    Did you apply the hotfix from the link in post #4?
     
    Evan Omo,
    #8
  10. 2014/09/23
    Panzerpung

    Panzerpung Inactive Thread Starter

    Joined:
    2014/09/22
    Messages:
    16
    Likes Received:
    0
    Yes I did, have not been experiencing any BSoDs after that, however, I have only been using the comp for 2 hrs. Playing BF4 now, itll show if Im still affected. Can you tell whether its hardware or software from the analysis? Would a clean w7 install help, with a good chance of success?
     
    Panzerpung,
    #9
  11. 2014/09/23
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,901
    Likes Received:
    510
    From your first data log, no I can't tell if its hardware causing the issue since it indicated that the BSOD was caused by the win32k.sys file.

    If another blue screen occurs then let me know.

    Follow these instructions to post a Dump Data Log.

    If you do not have a dump, ensure that your machine is configured to write out a dump by following the directions from microsoft.
     
    Evan Omo,
    #10

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...