locked
Random Blue Screen RRS feed

  • Question

  • I keep getting random bluescreens with just Chrome open. It happens twice a day or so.

    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.256.1
      Locale ID: 1033

    Additional information about the problem:
      BCCode: 1000007e
      BCP1: FFFFFFFFC0000005
      BCP2: FFFFF8800F141DBB
      BCP3: FFFFF88003C43228
      BCP4: FFFFF88003C42A80
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 256_1

    Here are my dump files:

    https://onedrive.live.com/redir?resid=CDCBE0F24E7C3ED6!312&authkey=!AF31UZqGqW1DUCs&ithint=file%2c.dmp

    https://onedrive.live.com/?cid=CDCBE0F24E7C3ED6&id=CDCBE0F24E7C3ED6%21311

    Thanks!

    Friday, July 11, 2014 1:17 AM

Answers

  • JA

    These were Related to atikmdag.sys ATI Radeon Kernel Mode Driver.  I would start by installing the newest driver available even if it is the same date as drivers do become corrupt.  If that doesnt fix the issue I would roll the driver back to one at least 6 months old.

    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\071014-19562-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    OK                                             C:\Users\Ken\Desktop
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Users\Ken\Desktop
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`03058000 PsLoadedModuleList = 0xfffff800`0329b890
    Debug session time: Thu Jul 10 20:46:09.246 2014 (UTC - 4:00)
    System Uptime: 0 days 4:15:46.448
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    ........
    *** 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, fffff8800f141dbb, fffff88003c43228, fffff88003c42a80}
    
    Probably caused by : atikmdag.sys ( atikmdag+c7dbb )
    
    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: fffff8800f141dbb, The address that the exception occurred at
    Arg3: fffff88003c43228, Exception Record Address
    Arg4: fffff88003c42a80, 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`0f141dbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]
    
    EXCEPTION_RECORD:  fffff88003c43228 -- (.exr 0xfffff88003c43228)
    ExceptionAddress: fffff8800f141dbb (atikmdag+0x00000000000c7dbb)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 00000000000006a8
    Attempt to read from address 00000000000006a8
    
    CONTEXT:  fffff88003c42a80 -- (.cxr 0xfffff88003c42a80;r)
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000140000 rdi=0000000000000002
    rip=fffff8800f141dbb rsp=fffff88003c43460 rbp=fffffa800b39a120
     r8=0000000000000002  r9=000000f41cf50000 r10=0000000000000000
    r11=fffff88003c43690 r12=fffffa800b373f40 r13=fffffa80083fe040
    r14=fffffa80071f0740 r15=fffff8800f07a000
    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`0f141dbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
    Last set context:
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000140000 rdi=0000000000000002
    rip=fffff8800f141dbb rsp=fffff88003c43460 rbp=fffffa800b39a120
     r8=0000000000000002  r9=000000f41cf50000 r10=0000000000000000
    r11=fffff88003c43690 r12=fffffa800b373f40 r13=fffffa80083fe040
    r14=fffffa80071f0740 r15=fffff8800f07a000
    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`0f141dbb 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 fffff80003305100
    GetUlongFromAddress: unable to read from fffff800033051c0
     00000000000006a8 Nonpaged pool
    
    FOLLOWUP_IP: 
    atikmdag+c7dbb
    fffff880`0f141dbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]
    
    BUGCHECK_STR:  0x7E
    
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    
    LAST_CONTROL_TRANSFER:  from 0000000700000030 to fffff8800f141dbb
    
    STACK_TEXT:  
    fffff880`03c43460 00000007`00000030 : fffff880`00000008 fffffa80`0b8d78a0 fffffa80`0b8d75e0 fffffa80`071f0740 : atikmdag+0xc7dbb
    fffff880`03c43468 fffff880`00000008 : fffffa80`0b8d78a0 fffffa80`0b8d75e0 fffffa80`071f0740 fffff880`0f1a2f6f : 0x00000007`00000030
    fffff880`03c43470 fffffa80`0b8d78a0 : fffffa80`0b8d75e0 fffffa80`071f0740 fffff880`0f1a2f6f 000aadef`00000030 : 0xfffff880`00000008
    fffff880`03c43478 fffffa80`0b8d75e0 : fffffa80`071f0740 fffff880`0f1a2f6f 000aadef`00000030 00000000`00000016 : 0xfffffa80`0b8d78a0
    fffff880`03c43480 fffffa80`071f0740 : fffff880`0f1a2f6f 000aadef`00000030 00000000`00000016 00000000`00000000 : 0xfffffa80`0b8d75e0
    fffff880`03c43488 fffff880`0f1a2f6f : 000aadef`00000030 00000000`00000016 00000000`00000000 fffff880`0f0fad01 : 0xfffffa80`071f0740
    fffff880`03c43490 000aadef`00000030 : 00000000`00000016 00000000`00000000 fffff880`0f0fad01 00000000`00400b11 : atikmdag+0x128f6f
    fffff880`03c43498 00000000`00000016 : 00000000`00000000 fffff880`0f0fad01 00000000`00400b11 00000000`00000000 : 0x000aadef`00000030
    fffff880`03c434a0 00000000`00000000 : fffff880`0f0fad01 00000000`00400b11 00000000`00000000 00000000`ffffffff : 0x16
    
    
    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 0xfffff88003c42a80 ; 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
    ---------
    
    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: fffff8800f141dbb, The address that the exception occurred at
    Arg3: fffff88003c43228, Exception Record Address
    Arg4: fffff88003c42a80, 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`0f141dbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]
    
    EXCEPTION_RECORD:  fffff88003c43228 -- (.exr 0xfffff88003c43228)
    ExceptionAddress: fffff8800f141dbb (atikmdag+0x00000000000c7dbb)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 00000000000006a8
    Attempt to read from address 00000000000006a8
    
    CONTEXT:  fffff88003c42a80 -- (.cxr 0xfffff88003c42a80;r)
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000140000 rdi=0000000000000002
    rip=fffff8800f141dbb rsp=fffff88003c43460 rbp=fffffa800b39a120
     r8=0000000000000002  r9=000000f41cf50000 r10=0000000000000000
    r11=fffff88003c43690 r12=fffffa800b373f40 r13=fffffa80083fe040
    r14=fffffa80071f0740 r15=fffff8800f07a000
    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`0f141dbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
    Last set context:
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000140000 rdi=0000000000000002
    rip=fffff8800f141dbb rsp=fffff88003c43460 rbp=fffffa800b39a120
     r8=0000000000000002  r9=000000f41cf50000 r10=0000000000000000
    r11=fffff88003c43690 r12=fffffa800b373f40 r13=fffffa80083fe040
    r14=fffffa80071f0740 r15=fffff8800f07a000
    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`0f141dbb 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:  00000000000006a8 Nonpaged pool
    
    FOLLOWUP_IP: 
    atikmdag+c7dbb
    fffff880`0f141dbb 488b83a8060000  mov     rax,qword ptr [rbx+6A8h]
    
    BUGCHECK_STR:  0x7E
    
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    
    LAST_CONTROL_TRANSFER:  from 0000000700000030 to fffff8800f141dbb
    
    STACK_TEXT:  
    fffff880`03c43460 00000007`00000030 : fffff880`00000008 fffffa80`0b8d78a0 fffffa80`0b8d75e0 fffffa80`071f0740 : atikmdag+0xc7dbb
    fffff880`03c43468 fffff880`00000008 : fffffa80`0b8d78a0 fffffa80`0b8d75e0 fffffa80`071f0740 fffff880`0f1a2f6f : 0x00000007`00000030
    fffff880`03c43470 fffffa80`0b8d78a0 : fffffa80`0b8d75e0 fffffa80`071f0740 fffff880`0f1a2f6f 000aadef`00000030 : 0xfffff880`00000008
    fffff880`03c43478 fffffa80`0b8d75e0 : fffffa80`071f0740 fffff880`0f1a2f6f 000aadef`00000030 00000000`00000016 : 0xfffffa80`0b8d78a0
    fffff880`03c43480 fffffa80`071f0740 : fffff880`0f1a2f6f 000aadef`00000030 00000000`00000016 00000000`00000000 : 0xfffffa80`0b8d75e0
    fffff880`03c43488 fffff880`0f1a2f6f : 000aadef`00000030 00000000`00000016 00000000`00000000 fffff880`0f0fad01 : 0xfffffa80`071f0740
    fffff880`03c43490 000aadef`00000030 : 00000000`00000016 00000000`00000000 fffff880`0f0fad01 00000000`00400b11 : atikmdag+0x128f6f
    fffff880`03c43498 00000000`00000016 : 00000000`00000000 fffff880`0f0fad01 00000000`00400b11 00000000`00000000 : 0x000aadef`00000030
    fffff880`03c434a0 00000000`00000000 : fffff880`0f0fad01 00000000`00400b11 00000000`00000000 00000000`ffffffff : 0x16
    
    
    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 0xfffff88003c42a80 ; 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
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Wade__Liu Monday, July 14, 2014 5:37 AM
    • Marked as answer by ZigZag3143x Thursday, July 17, 2014 12:25 PM
    Friday, July 11, 2014 2:04 AM