Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\081017-15600-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbole*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.23864.amd64fre.win7sp1_ldr.170707-0600
Machine Name:
Kernel base = 0xfffff800`03059000 PsLoadedModuleList = 0xfffff800`0329b750
Debug session time: Thu Aug 10 17:58:28.271 2017 (UTC + 2:00)
System Uptime: 0 days 11:58:21.676
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+2520c1 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - Operacja uko czona pomy lnie.

FAULTING_IP: 
+3734353763313633
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  opera.exe

CURRENT_IRQL:  b

EXCEPTION_RECORD:  fffff880009aff48 -- (.exr 0xfffff880009aff48)
ExceptionAddress: fffff88004e700c1 (atikmdag+0x00000000002520c1)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff880009afff0 -- (.trap 0xfffff880009afff0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa800a872010
rdx=fffff880009b01d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004e700c1 rsp=fffff880009b0180 rbp=fffff880009b0180
 r8=0000000000000000  r9=fffffa800a871440 r10=0000000000000000
r11=fffff880009b01b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
atikmdag+0x2520c1:
fffff880`04e700c1 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030c037e to fffff800030c8950

STACK_TEXT:  
fffff880`009af038 fffff800`030c037e : 00000000`00000000 00000000`00000000 fffff880`009af7b0 fffff800`030f4cd0 : nt!KeBugCheck
fffff880`009af040 fffff800`030f499d : fffff800`032dbde0 fffff800`0321951c fffff800`03059000 fffff880`009aff48 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009af070 fffff800`030f3775 : fffff800`0321cae8 fffff880`009af0e8 fffff880`009aff48 fffff800`03059000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009af0a0 fffff800`03104cfd : fffff880`009aff48 fffff880`009af7b0 fffff880`00000000 fffff880`00000004 : nt!RtlDispatchException+0x415
fffff880`009af780 fffff800`030c800e : fffff880`009aff48 00000000`10000002 fffff880`009afff0 fffff880`009b0228 : nt!KiDispatchException+0x17d
fffff880`009afe10 fffff800`030c615f : fffff880`009afff0 00001f80`00000b0b fffffa80`0800b900 fffffa80`00000000 : nt!KiExceptionDispatch+0xce
fffff880`009afff0 fffff880`04e700c1 : fffff880`009b01b0 fffff880`04e678ba 00000000`00000000 0000000f`007f8000 : nt!KiInvalidOpcodeFault+0x11f
fffff880`009b0180 fffff880`009b01b0 : fffff880`04e678ba 00000000`00000000 0000000f`007f8000 fffffa80`00000008 : atikmdag+0x2520c1
fffff880`009b0188 fffff880`04e678ba : 00000000`00000000 0000000f`007f8000 fffffa80`00000008 00000000`00000000 : 0xfffff880`009b01b0
fffff880`009b0190 00000000`00000000 : 0000000f`007f8000 fffffa80`00000008 00000000`00000000 fffff880`009b02b0 : atikmdag+0x2498ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+2520c1
fffff880`04e700c1 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  atikmdag+2520c1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  517f274d

FAILURE_BUCKET_ID:  X64_0x1E_0_atikmdag+2520c1

BUCKET_ID:  X64_0x1E_0_atikmdag+2520c1

Followup: MachineOwner
---------