Can anyone help me with my BSOD hell?


  1. Posts : 3
    Win 7 64 bit
       #1

    Can anyone help me with my BSOD hell?


    Hi folks - been recommended to register and ask for help here by a friend who found the forums very helpful. I have been having a wide variety of BSODs over the last few weeks - I have tried reverting and refreshing drivers, changing RAM, changing gfx card, pretty much everything short of building a new rig from scratch.

    I have followed the instructions on using the diagnostic tool - the output from which is attached. I'd be very grateful for any advice!

    Cheers
      My Computer


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

    Hi Kilohotel.

    A very frequent cause of stop 0x3B BSOD is the missing service pack. Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats including stop 0x3B BSOD.
    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

    Report us for any further BSOD after installing Service Pack 1.
    ______________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff96000134283, fffff88005b69060, 0}
    
    Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 )
    
    Followup: MachineOwner
    ---------
    
    0: 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: fffff96000134283, Address of the instruction which caused the bugcheck
    Arg3: fffff88005b69060, 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!HmgLockEx+a3
    fffff960`00134283 0fb7430c        movzx   eax,word ptr [rbx+0Ch]
    
    CONTEXT:  fffff88005b69060 -- (.cxr 0xfffff88005b69060;r)
    rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa800851bb60
    rdx=fffff900c0200000 rsi=0000000001eb0000 rdi=fffff900c0200000
    rip=fffff96000134283 rsp=fffff88005b69a40 rbp=0000000000000000
     r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
    r11=fffff88005b69aa8 r12=000000000384cf00 r13=0000000000000000
    r14=0000000000000001 r15=0000000000000000
    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!HmgLockEx+0xa3:
    fffff960`00134283 0fb7430c        movzx   eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
    Last set context:
    rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa800851bb60
    rdx=fffff900c0200000 rsi=0000000001eb0000 rdi=fffff900c0200000
    rip=fffff96000134283 rsp=fffff88005b69a40 rbp=0000000000000000
     r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
    r11=fffff88005b69aa8 r12=000000000384cf00 r13=0000000000000000
    r14=0000000000000001 r15=0000000000000000
    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!HmgLockEx+0xa3:
    fffff960`00134283 0fb7430c        movzx   eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
    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 fffff960002ec6b0 to fffff96000134283
    
    STACK_TEXT:  
    fffff880`05b69a40 fffff960`002ec6b0 : fffff900`c07d6ca0 00000000`00000001 00000000`22120d77 fffff900`c303b010 : win32k!HmgLockEx+0xa3
    fffff880`05b69ab0 fffff960`002ebbae : fffff900`c07d6ca0 00000000`00000000 00000d77`00000000 00000000`00000000 : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
    fffff880`05b69ae0 fffff960`002ecab3 : 00000000`00000000 00000000`22120d77 fffff900`c07d6ca0 00000000`0384cfb0 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
    fffff880`05b69b20 fffff960`002495ff : 00000000`00000000 fffff900`c00be010 fffff900`c07d6ca0 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
    fffff880`05b69b60 fffff960`0026a908 : 00000800`00000001 00000000`00000001 fffff880`05b69ca0 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
    fffff880`05b69ba0 fffff800`02c83153 : fffffa80`0851bb60 00000000`037ff500 000007fe`f948d610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
    fffff880`05b69c20 000007fe`fd214efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`037fef58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fd214efa
    
    
    FOLLOWUP_IP: 
    win32k!HmgLockEx+a3
    fffff960`00134283 0fb7430c        movzx   eax,word ptr [rbx+0Ch]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  win32k!HmgLockEx+a3
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0
    
    IMAGE_VERSION:  6.1.7600.16385
    
    STACK_COMMAND:  .cxr 0xfffff88005b69060 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3
    
    BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x3b_win32k!hmglockex+a3
    
    FAILURE_ID_HASH:  {8f81bb6a-de67-bc4d-99db-3f117a68551c}
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 3
    Win 7 64 bit
    Thread Starter
       #3

    Hi, thanks for your advice, i appreicate you taking the time. I have installed SP1 and am still getting the BSODs. I should possibly have mentioned earlier that I reinstalled win7 64 yesterday to see if that would help, but no difference. Here's my latest info:
      My Computer


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

    Kilohotel said:
    I have installed SP1 and am still getting the BSODs.
    The system does not have Service pack 1 installed till now.
    Code:
    OS Name    Microsoft Windows 7 Ultimate
    Version    6.1.7600 Build 7600
    If Service Pack 1 is installed, The Build will be 7601.
      My Computer


  5. Posts : 3
    Win 7 64 bit
    Thread Starter
       #5

    ok thanks - pretty sure i clciked install SP1 last night! but cheers, will get that done before posting again
      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 18:50.
Find Us