BSOD, not sure how it happened. Have error codes.


  1. Posts : 5
    Windows 7 64-bit
       #1

    BSOD, not sure how it happened. Have error codes.


    So I don't know how this happened at all as I came down stairs and saw this screen but I was able to capture a picture of the screen with the technical information.




    Here are the errors that I typed manually from the picture if the picture doesn't show up.

    stop: 0x0000007e (oxffffffffc0000005, 0xfffff800034f158d, 0xfffff88005283db8, 0xFFFFF88005283610
    Last edited by ritwikb2; 31 May 2015 at 12:15. Reason: attaching debug
      My Computer


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

    The crash dump reports a display failure.

    Uninstall the installed display driver using Display Driver Uninstaller. Then install the CCC 14.4 WHQL only.

    When done, stress test the Graphics Card using Furmark.Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.
    ______________________________________________________________
    Code:
    BugCheck 1000007E, {ffffffffc0000005, fffff800034f158d, fffff88005283db8, fffff88005283610}
    
    Probably caused by : atikmdag.sys ( atikmdag+136523 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800034f158d, The address that the exception occurred at
    Arg3: fffff88005283db8, Exception Record Address
    Arg4: fffff88005283610, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
    
    FAULTING_IP: 
    nt!KeAcquireGuardedMutex+1d
    fffff800`034f158d f00fba3100      lock btr dword ptr [rcx],0
    
    EXCEPTION_RECORD:  fffff88005283db8 -- (.exr 0xfffff88005283db8)
    ExceptionAddress: fffff800034f158d (nt!KeAcquireGuardedMutex+0x000000000000001d)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000001
       Parameter[1]: 0000000000000000
    Attempt to write to address 0000000000000000
    
    CONTEXT:  fffff88005283610 -- (.cxr 0xfffff88005283610;r)
    rax=fffff8a022827580 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffa800b8faf58 rsi=fffff8a022827708 rdi=fffffa800aee4b50
    rip=fffff800034f158d rsp=fffff88005283ff0 rbp=fffff8a022827708
     r8=0000000000000000  r9=0000000000000000 r10=fffff8800f4d2390
    r11=fffff8800f4740cb r12=fffff8a022827580 r13=fffffa8006d0ba01
    r14=fffffa800b8faf01 r15=fffffa8009a60228
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    nt!KeAcquireGuardedMutex+0x1d:
    fffff800`034f158d f00fba3100      lock btr dword ptr [rcx],0 ds:002b:00000000`00000000=????????
    Last set context:
    rax=fffff8a022827580 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffa800b8faf58 rsi=fffff8a022827708 rdi=fffffa800aee4b50
    rip=fffff800034f158d rsp=fffff88005283ff0 rbp=fffff8a022827708
     r8=0000000000000000  r9=0000000000000000 r10=fffff8800f4d2390
    r11=fffff8800f4740cb r12=fffff8a022827580 r13=fffffa8006d0ba01
    r14=fffffa800b8faf01 r15=fffffa8009a60228
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    nt!KeAcquireGuardedMutex+0x1d:
    fffff800`034f158d f00fba3100      lock btr dword ptr [rcx],0 ds:002b:00000000`00000000=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000001
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003717100
    GetUlongFromAddress: unable to read from fffff800037171c0
     0000000000000000 Nonpaged pool
    
    FOLLOWUP_IP: 
    atikmdag+136523
    fffff880`0f3be523 ??              ???
    
    BUGCHECK_STR:  0x7E
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8800f3be523 to fffff800034f158d
    
    STACK_TEXT:  
    fffff880`05283ff0 fffff880`0f3be523 : 00000000`00000000 fffffa80`0af41ba8 fffffa80`0b8ed198 00000000`00000000 : nt!KeAcquireGuardedMutex+0x1d
    fffff880`05284020 00000000`00000000 : fffffa80`0af41ba8 fffffa80`0b8ed198 00000000`00000000 000000f4`12d40000 : atikmdag+0x136523
    
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  atikmdag+136523
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  546ea3c3
    
    STACK_COMMAND:  .cxr 0xfffff88005283610 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+136523
    
    BUCKET_ID:  X64_0x7E_atikmdag+136523
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag+136523
    
    FAILURE_ID_HASH:  {9fda3dcd-27e6-662c-c000-ae4057e4fb08}
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f288000 fffff880`1050c000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Nov 21 08:00:27 2014 (546EA3C3)
        CheckSum:         0121F198
        ImageSize:        01284000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      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 11:36.
Find Us