BSOD At random times different drivers.


  1. Posts : 1
    Windows 7 Ultimate x64
       #1

    BSOD At random times different drivers.


    I scanned the RAM first thing as i had some time to kill and the RAM seems fine, but im getting BSOD at random times, happened 1 time with no games opened and twice when i was playing a game, i attached the logs like the posting instructions asked.

    Thanks!
      My Computer


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

    Dont use a BETA display driver.

    Uninstall the installed display driver using DDU. Then install the CCC 14.4 WHQL only.

    Let us know for any further BSOD after doing it.
    _______________________________________
    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, fffff8800f175160, fffff88004f2bf18, fffff88004f2b770}
    
    Probably caused by : atikmdag.sys ( atikmdag+cd160 )
    
    Followup: MachineOwner
    ---------
    
    0: 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: fffff8800f175160, The address that the exception occurred at
    Arg3: fffff88004f2bf18, Exception Record Address
    Arg4: fffff88004f2b770, 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+cd160
    fffff880`0f175160 488b4130        mov     rax,qword ptr [rcx+30h]
    
    EXCEPTION_RECORD:  fffff88004f2bf18 -- (.exr 0xfffff88004f2bf18)
    ExceptionAddress: fffff8800f175160 (atikmdag+0x00000000000cd160)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000030
    Attempt to read from address 0000000000000030
    
    CONTEXT:  fffff88004f2b770 -- (.cxr 0xfffff88004f2b770;r)
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000002 rsi=fffff8a00ab63708 rdi=0000000000000001
    rip=fffff8800f175160 rsp=fffff88004f2c158 rbp=fffff8a00ab63708
     r8=0000000000000003  r9=0000000000000000 r10=fffffffffffffffe
    r11=fffff880079c23d0 r12=fffff8a00ab63580 r13=0000000000000000
    r14=0000000000000001 r15=fffff8a00aa2b708
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    atikmdag+0xcd160:
    fffff880`0f175160 488b4130        mov     rax,qword ptr [rcx+30h] ds:002b:00000000`00000030=????????????????
    Last set context:
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000002 rsi=fffff8a00ab63708 rdi=0000000000000001
    rip=fffff8800f175160 rsp=fffff88004f2c158 rbp=fffff8a00ab63708
     r8=0000000000000003  r9=0000000000000000 r10=fffffffffffffffe
    r11=fffff880079c23d0 r12=fffff8a00ab63580 r13=0000000000000000
    r14=0000000000000001 r15=fffff8a00aa2b708
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    atikmdag+0xcd160:
    fffff880`0f175160 488b4130        mov     rax,qword ptr [rcx+30h] ds:002b:00000000`00000030=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    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:  0000000000000030
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f160e8
    GetUlongFromAddress: unable to read from fffff80002f16198
     0000000000000030 Nonpaged pool
    
    FOLLOWUP_IP: 
    atikmdag+cd160
    fffff880`0f175160 488b4130        mov     rax,qword ptr [rcx+30h]
    
    BUGCHECK_STR:  0x7E
    
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8800f1de539 to fffff8800f175160
    
    STACK_TEXT:  
    fffff880`04f2c158 fffff880`0f1de539 : 00000000`00000000 fffff880`04f2c410 fffffa80`07d82040 00000000`00000000 : atikmdag+0xcd160
    fffff880`04f2c160 00000000`00000000 : fffff880`04f2c410 fffffa80`07d82040 00000000`00000000 fffffa80`05de2010 : atikmdag+0x136539
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  atikmdag+cd160
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  546ea3c3
    
    STACK_COMMAND:  .cxr 0xfffff88004f2b770 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+cd160
    
    BUCKET_ID:  X64_0x7E_atikmdag+cd160
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7e_atikmdag+cd160
    
    FAILURE_ID_HASH:  {cad8ac66-9a19-b808-09ab-072337b957bb}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f0a8000 fffff880`1032c000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\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 22:03.
Find Us