AnsweredAssumed Answered

BSOD and frequent driver crashes in games

Question asked by youssefk on Dec 16, 2017
Latest reply on Jan 14, 2019 by debosheer

For the past few months or so my PC has been crashing and even BSODing. The minidumps all say the culprit is atikmpag.sys which I assume has something to do with the drivers. I have completely clean installed drivers before you ask and I have gone back to older versions and nothing is working. Before we go any further my specs:

 

i7 6850k

DDR4 16GB RAM

r9 270x 2gb

256ssd

1tb HDD

GA-X99-UD3P

 

Minidump from BSOD:

 

 

Loading Dump File [C:\Windows\Minidump\121617-18688-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

 

 

 

************* Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526

Machine Name:

Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`032a2890

Debug session time: Sat Dec 16 21:25:27.516 2017 (UTC - 5:00)

System Uptime: 0 days 5:28:38.732

Loading Kernel Symbols

...............................................................

................................................................

...........................

Loading User Symbols

Loading unloaded module list

............

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

 

Use !analyze -v to get detailed debugging information.

 

 

BugCheck 119, {1, 2e98f0, 2e98f2, 2e98f1}

 

 

*** WARNING: Unable to verify timestamp for atikmpag.sys

*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys

Probably caused by : atikmpag.sys ( atikmpag+48ae3 )

 

 

Followup:     MachineOwner

---------

 

 

6: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

 

VIDEO_SCHEDULER_INTERNAL_ERROR (119)

The video scheduler has detected that fatal violation has occurred. This resulted

in a condition that video scheduler can no longer progress. Any other values after

parameter 1 must be individually examined according to the subtype.

Arguments:

Arg1: 0000000000000001, The driver has reported an invalid fence ID.

Arg2: 00000000002e98f0

Arg3: 00000000002e98f2

Arg4: 00000000002e98f1

 

 

Debugging Details:

------------------

 

 

 

 

DUMP_CLASS: 1

 

 

DUMP_QUALIFIER: 400

 

 

BUILD_VERSION_STRING:  7601.18741.amd64fre.win7sp1_gdr.150202-1526

 

 

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

 

 

SYSTEM_PRODUCT_NAME:  Default string

 

 

SYSTEM_SKU:  Default string

 

 

SYSTEM_VERSION:  Default string

 

 

BIOS_VENDOR:  American Megatrends Inc.

 

 

BIOS_VERSION:  F23

 

 

BIOS_DATE:  06/07/2017

 

 

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

 

 

BASEBOARD_PRODUCT:  X99-UD3P-CF

 

 

BASEBOARD_VERSION:  Default string

 

 

DUMP_TYPE:  2

 

 

BUGCHECK_P1: 1

 

 

BUGCHECK_P2: 2e98f0

 

 

BUGCHECK_P3: 2e98f2

 

 

BUGCHECK_P4: 2e98f1

 

 

CPU_COUNT: c

 

 

CPU_MHZ: e10

 

 

CPU_VENDOR:  GenuineIntel

 

 

CPU_FAMILY: 6

 

 

CPU_MODEL: 4f

 

 

CPU_STEPPING: 1

 

 

CPU_MICROCODE: 6,4f,1,0 (F,M,S,R)  SIG: B00001D'00000000 (cache) B00001D'00000000 (init)

 

 

CUSTOMER_CRASH_COUNT:  1

 

 

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

 

 

BUGCHECK_STR:  0x119

 

 

PROCESS_NAME:  chrome.exe

 

 

CURRENT_IRQL:  b

 

 

ANALYSIS_SESSION_HOST:  YOUSSEF-PC

 

 

ANALYSIS_SESSION_TIME:  12-16-2017 21:30:44.0158

 

 

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

 

 

LAST_CONTROL_TRANSFER:  from fffff880019e022f to fffff800030d2ec0

 

 

STACK_TEXT: 

fffff880`0ac9ca78 fffff880`019e022f : 00000000`00000119 00000000`00000001 00000000`002e98f0 00000000`002e98f2 : nt!KeBugCheckEx

fffff880`0ac9ca80 fffff880`04129eb9 : fffff880`03349180 00000000`002e98f0 00000000`00000000 00000000`002e98f2 : watchdog!WdLogEvent5+0x11b

fffff880`0ac9cad0 fffff880`0412a1e6 : fffffa80`0e79b000 fffff880`0ac9cbe0 00000000`000011ac 00000000`00000000 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad

fffff880`0ac9cb00 fffff880`04129f76 : fffffa80`002e98f0 fffff880`0ac9cbd0 fffffa80`0e79b000 fffffa80`0dd25040 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x25e

fffff880`0ac9cb50 fffff880`0403113f : fffffa80`0de39480 00000000`00c44eb0 00000000`0020b7c8 fffffa80`00c44eb0 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e

fffff880`0ac9cb80 fffff880`03f39ae3 : fffff800`0330fac0 00000000`00000000 fffff880`0ac9cc30 fffff8a0`114ba540 : dxgkrnl!DxgNotifyInterruptCB+0x83

fffff880`0ac9cbb0 fffff800`0330fac0 : 00000000`00000000 fffff880`0ac9cc30 fffff8a0`114ba540 00000000`00000000 : atikmpag+0x48ae3

fffff880`0ac9cbb8 00000000`00000000 : fffff880`0ac9cc30 fffff8a0`114ba540 00000000`00000000 00000000`00000000 : nt!MmFreePageListHead

 

 

 

 

THREAD_SHA1_HASH_MOD_FUNC:  af7b2cd79350eeb75348f384f58c6a580c0814c1

 

 

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  51c3152586687dbd5c9e19eb523a11fa4299b095

 

 

THREAD_SHA1_HASH_MOD:  602f1944afa4c1ed9416645239b55ba959677b79

 

 

FOLLOWUP_IP:

atikmpag+48ae3

fffff880`03f39ae3 ??              ???

 

 

SYMBOL_STACK_INDEX:  6

 

 

SYMBOL_NAME:  atikmpag+48ae3

 

 

FOLLOWUP_NAME:  MachineOwner

 

 

MODULE_NAME: atikmpag

 

 

IMAGE_NAME:  atikmpag.sys

 

 

DEBUG_FLR_IMAGE_TIMESTAMP:  59d6992e

 

 

STACK_COMMAND:  .thread ; .cxr ; kb

 

 

FAILURE_BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+48ae3

 

 

BUCKET_ID:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+48ae3

 

 

PRIMARY_PROBLEM_CLASS:  X64_0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_atikmpag+48ae3

 

 

TARGET_TIME:  2017-12-17T02:25:27.000Z

 

 

OSBUILD:  7601

 

 

OSSERVICEPACK:  1000

 

 

SERVICEPACK_NUMBER: 0

 

 

OS_REVISION: 0

 

 

SUITE_MASK:  272

 

 

PRODUCT_TYPE:  1

 

 

OSPLATFORM_TYPE:  x64

 

 

OSNAME:  Windows 7

 

 

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

 

 

OS_LOCALE: 

 

 

USER_LCID:  0

 

 

OSBUILD_TIMESTAMP:  2015-02-02 21:25:01

 

 

BUILDDATESTAMP_STR:  150202-1526

 

 

BUILDLAB_STR:  win7sp1_gdr

 

 

BUILDOSVER_STR:  6.1.7601.18741.amd64fre.win7sp1_gdr.150202-1526

 

 

ANALYSIS_SESSION_ELAPSED_TIME:  3c9

 

 

ANALYSIS_SOURCE:  KM

 

 

FAILURE_ID_HASH_STRING:  km:x64_0x119_1_driver_reported_invalid_fence_id_atikmpag+48ae3

 

 

FAILURE_ID_HASH:  {8f57f408-741b-1244-c164-e68ac6a8e878}

 

 

Followup:     MachineOwner

---------

Outcomes