Game mode: [Single-player]
Type of issue: [Crash]
Server type: [PvE]
Region: [Local Instance]
Hello there,
for quite some time i am experiencing “random” Bluescreen while playing Conan Exiles and exclusively Conan Exiles. All other Games run just fine for hours on end.
There is no pattern as of which i can deduce, what the Problem is. It happens at different times (right after starting the game, after a few hours of playing) and on different actions (in fight, when just walking to a destination, standing around, opening inventory).
Win7 64 Bit SP1
RAM: 8GB
AMD FX 8350 8 Core Processor
AMD Radeon R9 200 Series
Drivers are up to date
Log:
Is located at Pastebin: xbyPjv4Z
I cannot add URLs, therefore just adding the Paste ID. (Append the ID to the Pastebin Base URL “pastebin (dot) com”)
Mini Dump
Microsoft ® Windows Debugger Version 6.3.9600.17336 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\hasifee\Desktop\062319-24866-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRVC:\SymCache {MICROSOFT SYMBOL URL}
Symbol search path is: SRVC:\SymCache {MICROSOFT SYMBOL URL}
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.24475.amd64fre.win7sp1_ldr.190516-0600
Machine Name:
Kernel base = 0xfffff80003019000 PsLoadedModuleList = 0xfffff800
03252c90
Debug session time: Sun Jun 23 10:47:46.205 2019 (UTC + 2:00)
System Uptime: 0 days 1:43:01.375
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}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: ExceptionRecord ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: ContextRecord ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: ExceptionRecord ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: ContextRecord ***
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcVSyncCookie+e9 )
Followup: MachineOwner
6: 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:
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: ExceptionRecord ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: ContextRecord ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: ExceptionRecord ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: ContextRecord ***
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
DPC_STACK_BASE: FFFFF8800316EFB0
EXCEPTION_RECORD: fffff88003166f98 – (.exr 0xfffff88003166f98)
ExceptionAddress: fffff88004d04f7d (dxgmms1!VidSchiProcessDpcVSyncCookie+0x00000000000000e9)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
TRAP_FRAME: fffff88003167040 – (.trap 0xfffff88003167040)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004d04f7d rsp=fffff880031671d0 rbp=fffffa8009aa39a0
r8=0000000000000000 r9=0000000000000000 r10=fffffa8009aa21f0
r11=fffff88003167288 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9:
fffff880`04d04f7d 48f7f1 div rax,rcx
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030afcde to fffff800030aca70
STACK_TEXT:
fffff88003166088 fffff800
030afcde : 0000000000000002 fffff880
031677e8 fffff88003166800 fffff800
03079b70 : nt!KeBugCheck
fffff88003166090 fffff800
030b3ddd : fffff8000328f7fc fffff800
031dafe4 fffff80003019000 fffff880
03166f98 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880031660c0 fffff800
03078eb5 : fffff800031c2644 fffff880
03166138 fffff88003166f98 fffff800
03019000 : nt!RtlpExecuteHandlerForException+0xd
fffff880031660f0 fffff800
0319399e : fffff88003166f98 fffff880
03166800 fffff88000000000 fffffa80
00000004 : nt!RtlDispatchException+0x415
fffff880031667d0 fffff800
030baf42 : fffff88003166f98 fffffa80
098b5410 fffff88003167040 00000000
00000000 : nt!KiDispatchException+0x17e
fffff88003166e60 fffff800
030b5ddc : 0000000000000000 fffff880
1118f694 fffffa800d3012c0 00000000
0000000b : nt!KiExceptionDispatch+0xc2
fffff88003167040 fffff880
04d04f7d : fffffa80098b5410 00000000
00000000 fffffa8009aa2000 fffffa80
0d7a6af0 : nt!KiDivideErrorFault+0x2dc
fffff880031671d0 fffff880
04d04d24 : fffff88000000000 fffff880
00000021 fffff88000000000 00000000
00000000 : dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9
fffff88003167290 fffff880
04d04c88 : 000000f410000000 fffffa80
098b5410 fffffa800d3012c0 fffffa80
0d301580 : dxgmms1!VidSchDdiNotifyDpcWorker+0x80
fffff880031672e0 fffff880
04c0a1cf : fffffa8008bb7480 00000000
00000000 0000000000000001 fffffa80
0d301580 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff88003167330 fffff880
1118eaa9 : fffffa800d3012c0 fffffa80
0d3012c0 fffffa800d3012c0 fffff880
03167768 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff88003167360 fffffa80
0d3012c0 : fffffa800d3012c0 fffffa80
0d3012c0 fffff88003167768 00000000
00000000 : atikmdag+0xc2aa9
fffff88003167368 fffffa80
0d3012c0 : fffffa800d3012c0 fffff880
03167768 0000000000000000 fffff880
031673c0 : 0xfffffa800d3012c0 fffff880
03167370 fffffa800d3012c0 : fffff880
03167768 0000000000000000 fffff880
031673c0 0000000000000000 : 0xfffffa80
0d3012c0
fffff88003167378 fffff880
03167768 : 0000000000000000 fffff880
031673c0 0000000000000000 00000000
00000000 : 0xfffffa800d3012c0 fffff880
03167380 0000000000000000 : fffff880
031673c0 0000000000000000 00000000
00000000 0000000000000001 : 0xfffff880
03167768
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidSchiProcessDpcVSyncCookie+e9
fffff880`04d04f7d 48f7f1 div rax,rcx
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: dxgmms1!VidSchiProcessDpcVSyncCookie+e9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5b94676d
IMAGE_VERSION: 6.1.7601.24260
FAILURE_BUCKET_ID: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9
BUCKET_ID: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x1e_dxgmms1!vidschiprocessdpcvsynccookie+e9
FAILURE_ID_HASH: {563df3f2-b5ac-cd6b-d157-580c3b7f02da}
Followup: MachineOwner
From what i gather from the Dump File, there appears to be a Divide-by-Zero Exception in Module dxgmms1.
Although i am not sure, if this is correct, since i am missing quite a few Symbol Declarations it seems.
I appreciate any help on this issue, since it really cuts down the excitement of playing it.
Please provide a step-by-step process of how the bug can be reproduced. The more details you provide us with the easier it will be for us to find and fix the bug:
- None available, no clear pattern -