BSOD Custom build help


  1. Posts : 2
    Windows 7 Home Premium x64
       #1

    BSOD Custom build help


    Hey Peeps!

    I just had my first BSOD on my custom build. Any help in figuring out what caused this would be greatly appreciated.

    It happened when I was away from my machine, while playing a playlist on youtube and having other windows open on 2 separate browsers; Chrome & Firefox.

    Jonezy
      My Computer


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

    CCC 14.12 WHQL works better with R9 cards, as far as I have seen. Get it from Download Drivers and see how it goes.

    Let us know.
    ________________________________________
    Code:
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff8801111fdbb, fffff880081d2228, fffff880081d1a80}
    
    Probably caused by : atikmdag.sys ( atikmdag+c7dbb )
    
    Followup: MachineOwner
    ---------
    
    6: 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: fffff8801111fdbb, The address that the exception occurred at
    Arg3: fffff880081d2228, Exception Record Address
    Arg4: fffff880081d1a80, 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: 
    atikmdag+c7dbb
    fffff880`1111fdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]
    
    EXCEPTION_RECORD:  fffff880081d2228 -- (.exr 0xfffff880081d2228)
    ExceptionAddress: fffff8801111fdbb (atikmdag+0x00000000000c7dbb)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 00000000000006a8
    Attempt to read from address 00000000000006a8
    
    CONTEXT:  fffff880081d1a80 -- (.cxr 0xfffff880081d1a80;r)
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=00000000003c0000 rdi=0000000000000002
    rip=fffff8801111fdbb rsp=fffff880081d2460 rbp=fffffa80088b6060
     r8=0000000000000002  r9=000000f416368000 r10=0000000000000000
    r11=fffff880081d2690 r12=fffffa80088c5c80 r13=fffffa8007b19f00
    r14=fffffa800b6ca010 r15=fffff88011058000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    atikmdag+0xc7dbb:
    fffff880`1111fdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
    Last set context:
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=00000000003c0000 rdi=0000000000000002
    rip=fffff8801111fdbb rsp=fffff880081d2460 rbp=fffffa80088b6060
     r8=0000000000000002  r9=000000f416368000 r10=0000000000000000
    r11=fffff880081d2690 r12=fffffa80088c5c80 r13=fffffa8007b19f00
    r14=fffffa800b6ca010 r15=fffff88011058000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    atikmdag+0xc7dbb:
    fffff880`1111fdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    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:  0000000000000000
    
    EXCEPTION_PARAMETER2:  00000000000006a8
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003304100
    GetUlongFromAddress: unable to read from fffff800033041c0
     00000000000006a8 Nonpaged pool
    
    FOLLOWUP_IP: 
    atikmdag+c7dbb
    fffff880`1111fdbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]
    
    BUGCHECK_STR:  0x7E
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8801111fdbb
    
    STACK_TEXT:  
    fffff880`081d2460 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0b6ca010 : atikmdag+0xc7dbb
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  atikmdag+c7dbb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53508a3c
    
    STACK_COMMAND:  .cxr 0xfffff880081d1a80 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+c7dbb
    
    BUCKET_ID:  X64_0x7E_atikmdag+c7dbb
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag+c7dbb
    
    FAILURE_ID_HASH:  {1bce3716-c561-7934-01c3-535369bb657c}
    
    Followup: MachineOwner
    ---------
    
    6: kd> lmvm atikmdag
    start             end                 module name
    fffff880`11058000 fffff880`11f68000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Apr 18 07:43:16 2014 (53508A3C)
        CheckSum:         00EAEEE6
        ImageSize:        00F10000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 2
    Windows 7 Home Premium x64
    Thread Starter
       #3

    Thanks for the help! I've went ahead and updated my CCC and graphics driver. If I get another BSOD, I'll be back.

    Jonezy
      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 05:56.
Find Us