Random BSOD


  1. Posts : 268
    Windows 7 Pro SP1 x64
       #1

    Random BSOD


    Had nothing open except a web page on youtube was not even watching a video and poof blue screen what gives?
      My Computer


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

    Hi Ascendents.

    Uninstall your installed version of the display driver.


    Then clean up any possible leftover.


    Then install version 13.9 WHQL only.


    When the drive is properly applied, Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Let us know the results.
    ________________________________________
    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, fffff8800f4dadbb, fffff880009d7228, fffff880009d6a80}
    
    Probably caused by : atikmdag.sys ( atikmdag+c7dbb )
    
    Followup: MachineOwner
    ---------
    
    1: 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: fffff8800f4dadbb, The address that the exception occurred at
    Arg3: fffff880009d7228, Exception Record Address
    Arg4: fffff880009d6a80, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    atikmdag+c7dbb
    fffff880`0f4dadbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]
    
    EXCEPTION_RECORD:  fffff880009d7228 -- (.exr 0xfffff880009d7228)
    ExceptionAddress: fffff8800f4dadbb (atikmdag+0x00000000000c7dbb)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 00000000000006a8
    Attempt to read from address 00000000000006a8
    
    CONTEXT:  fffff880009d6a80 -- (.cxr 0xfffff880009d6a80;r)
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000870000 rdi=0000000000000002
    rip=fffff8800f4dadbb rsp=fffff880009d7460 rbp=fffffa800faa2960
     r8=0000000000000002  r9=000000f41cae8000 r10=0000000000000000
    r11=fffff880009d7690 r12=fffffa80108d3f40 r13=fffffa800f754c00
    r14=fffffa800d659740 r15=fffff8800f413000
    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`0f4dadbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
    Last set context:
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000870000 rdi=0000000000000002
    rip=fffff8800f4dadbb rsp=fffff880009d7460 rbp=fffffa800faa2960
     r8=0000000000000002  r9=000000f41cae8000 r10=0000000000000000
    r11=fffff880009d7690 r12=fffffa80108d3f40 r13=fffffa800f754c00
    r14=fffffa800d659740 r15=fffff8800f413000
    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`0f4dadbb 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%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  00000000000006a8
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038c7100
    GetUlongFromAddress: unable to read from fffff800038c71c0
     00000000000006a8 Nonpaged pool
    
    FOLLOWUP_IP: 
    atikmdag+c7dbb
    fffff880`0f4dadbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]
    
    BUGCHECK_STR:  0x7E
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from 00000000040b0000 to fffff8800f4dadbb
    
    STACK_TEXT:  
    fffff880`009d7460 00000000`040b0000 : 00000000`040cdfff fffffa80`108d3f40 00000000`00000003 fffffa80`0d659740 : atikmdag+0xc7dbb
    fffff880`009d7468 00000000`040cdfff : fffffa80`108d3f40 00000000`00000003 fffffa80`0d659740 fffff880`0f53bf6f : 0x40b0000
    fffff880`009d7470 fffffa80`108d3f40 : 00000000`00000003 fffffa80`0d659740 fffff880`0f53bf6f 00000000`00000100 : 0x40cdfff
    fffff880`009d7478 00000000`00000003 : fffffa80`0d659740 fffff880`0f53bf6f 00000000`00000100 fffffa80`0faa1820 : 0xfffffa80`108d3f40
    fffff880`009d7480 fffffa80`0d659740 : fffff880`0f53bf6f 00000000`00000100 fffffa80`0faa1820 00000000`00000098 : 0x3
    fffff880`009d7488 fffff880`0f53bf6f : 00000000`00000100 fffffa80`0faa1820 00000000`00000098 000ddf83`00000098 : 0xfffffa80`0d659740
    fffff880`009d7490 00000000`00000100 : fffffa80`0faa1820 00000000`00000098 000ddf83`00000098 00000000`00000000 : atikmdag+0x128f6f
    fffff880`009d7498 fffffa80`0faa1820 : 00000000`00000098 000ddf83`00000098 00000000`00000000 00000000`00000001 : 0x100
    fffff880`009d74a0 00000000`00000098 : 000ddf83`00000098 00000000`00000000 00000000`00000001 00000000`ffffffff : 0xfffffa80`0faa1820
    fffff880`009d74a8 000ddf83`00000098 : 00000000`00000000 00000000`00000001 00000000`ffffffff fffff880`009d7730 : 0x98
    fffff880`009d74b0 00000000`00000000 : 00000000`00000001 00000000`ffffffff fffff880`009d7730 fffff880`009d75e0 : 0x000ddf83`00000098
    
    
    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 0xfffff880009d6a80 ; 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
    ---------
    
    1: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f413000 fffff880`10323000   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 : 268
    Windows 7 Pro SP1 x64
    Thread Starter
       #3

    Uninstalled the driver installed the 13.9 Driver did the driver sweep and ran the furmark for 10 minutes maxed out temp of 70c everything looks good so far.
      My Computer


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

    OK, let us know for any further issue.
      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 12:33.
Find Us