cancel
Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

lexus-3141
Journeyman III

atikmpag.sys BSOD 116 on Ryzen 2500u

Hi! I have installed Win10 PRO on notebook HP ENVY x360 15-bq101ur (Ryzen 2500u) and enabled virtualizaion in bios.  Than I have installed Hyper-V.

After reboot system is not starting with virtualization.  Only if I disabling virtualization windows started successfully.

The system has lastest updates. (1709)

About minidump WinDbg says:

-----

BugCheck 116, {ffff990402398010, fffff8066343f624, ffffffffc0000001, 3}

*** 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+f624 )

-----

0 Likes
3 Replies
lexus-3141
Journeyman III

Re: atikmpag.sys BSOD 116 on Ryzen 2500u

Version 23.20.817.0 at 08.01.2018 fix it.

Download here: Microsoft Update Catalog

0 Likes
harmandeep
Journeyman III

Re: atikmpag.sys BSOD 116 on Ryzen 2500u

Hi,

Still getting the same Error.

Windows 10 1809 (10.0.17763.615) crashes with same Bugcheck (VIDEO_TDR_FAILURE (116)) once I enable Hyper-V.

Same error also occurs with Windows 10 1903.

System Specs: Ryzen 5 3400g | Asrock DeskMini A300

Latest drivers are installed. I had refreshed OS thrice and I get the same error everytime.

atikmpag.sys version on my PC: 26.20.11022.3001

atikmpag.sys version on the aforementioned Windows KB patch (outdated version): 23.20.817.0

We are evaluating ClientsPCs for our Developers. We plan to deploy AMD Ryzen based PCs if the POC Evaluation passes. Hyper-V is really important for our Developers.

I can upload memory dumps if necessary. Can you please investigate and update us.

Crashdump WinDBG automatic analysis can be seen below:

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffce85c0274060, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8077f6c053c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\u0344396.inf_amd64_67c52840945228eb\B344356\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.

SYSTEM_SKU: To Be Filled By O.E.M.

SYSTEM_VERSION: To Be Filled By O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: P3.50

BIOS_DATE: 05/15/2019

BASEBOARD_MANUFACTURER: ASRock

BASEBOARD_PRODUCT: A300M-STX

BASEBOARD_VERSION:

DUMP_TYPE: 2

BUGCHECK_P1: ffffce85c0274060

BUGCHECK_P2: fffff8077f6c053c

BUGCHECK_P3: ffffffffc0000001

BUGCHECK_P4: 3

FAULTING_IP:
atikmpag+1053c
fffff807`7f6c053c 48895c2408 mov qword ptr [rsp+8],rbx

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CPU_COUNT: 8

CPU_MHZ: e74

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 18

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-1UCMQQ3

ANALYSIS_SESSION_TIME: 07-12-2019 08:02:58.0559

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

STACK_TEXT:
ffffdf0d`d8f5d9f8 fffff807`7fa4d5e6 : 00000000`00000116 ffffce85`c0274060 fffff807`7f6c053c ffffffff`c0000001 : nt!KeBugCheckEx
ffffdf0d`d8f5da00 fffff807`7fa0031b : fffff807`7f6c053c ffffce85`c0120000 ffffce85`c01200d8 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfa
ffffdf0d`d8f5da40 fffff807`7fa00f0f : 00000000`00000101 00000000`01000000 ffffce85`c0120000 ffffce85`c0120000 : dxgkrnl!DXGADAPTER::PrepareToReset+0x1a3
ffffdf0d`d8f5da90 fffff807`7fa4cd25 : fffff807`74190140 ffffce85`c01209c0 ffffce85`c00220c0 fffff807`74604240 : dxgkrnl!DXGADAPTER::Reset+0x293
ffffdf0d`d8f5db10 fffff807`7fa4ce87 : 00000000`00000000 ffffce85`b84aca60 fffff807`744b55c0 ffffce85`b8464cf0 : dxgkrnl!TdrResetFromTimeout+0x15
ffffdf0d`d8f5db40 fffff807`7411abfa : ffffce85`bbe34040 fffff807`7fa4ce60 ffffce85`c2cfbfd0 ffffce85`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffdf0d`d8f5db70 fffff807`740e3b35 : ffffce85`bbe34040 ffffce85`b84af280 ffffce85`bbe34040 00000065`b8bbbdff : nt!ExpWorkerThread+0x16a
ffffdf0d`d8f5dc10 fffff807`742613cc : ffffe780`e9480180 ffffce85`bbe34040 fffff807`740e3ae0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffdf0d`d8f5dc60 00000000`00000000 : ffffdf0d`d8f5e000 ffffdf0d`d8f58000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c


THREAD_SHA1_HASH_MOD_FUNC: 3aa6aac2005fb728aff349df2b5f504893184b97

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: c28d45a3a6a4b82f719a9c19df7c6106ac633fbc

THREAD_SHA1_HASH_MOD: 3225689ea8bf23dca00cdfd517975e0703e07271

FOLLOWUP_IP:
atikmpag+1053c
fffff807`7f6c053c 48895c2408 mov qword ptr [rsp+8],rbx

FAULT_INSTR_CODE: 245c8948

SYMBOL_NAME: atikmpag+1053c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5d1ec238

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys

BUCKET_ID: 0x116_IMAGE_atikmpag.sys

PRIMARY_PROBLEM_CLASS: 0x116_IMAGE_atikmpag.sys

TARGET_TIME: 2019-07-12T14:47:38.000Z

OSBUILD: 17763

OSSERVICEPACK: 615

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2020-05-15 09:13:35

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 4f8f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x116_image_atikmpag.sys

FAILURE_ID_HASH: {e300aa8c-6915-3f37-7957-d2e4fc30a6fd}

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

0: kd> lmvm atikmpag
Browse full module list
start end module name
fffff807`7f6b0000 fffff807`7f742000 atikmpag T (no symbols)
Loaded symbol image file: atikmpag.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\u0344396.inf_amd64_67c52840945228eb\B344356\atikmpag.sys
Image name: atikmpag.sys
Browse all global symbols functions data
Timestamp: Thu Jul 4 20:21:28 2019 (5D1EC238)
CheckSum: 0009717C
ImageSize: 00092000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

0 Likes
harmandeep
Journeyman III

Re: atikmpag.sys BSOD 116 on Ryzen 2500u

We ended up returning AMD POC System in lieu of Intel Bean Canyon NUCs.

As a platform, NUCs were more stable.

Sad that AMD APUs don't work well with Hyper-V.

0 Likes