-
December 13th, 2018, 06:02 PM
#1
Windows 10 (x64) crashes pointing towards dxgmms2.sys
I just ran through my last dump file and found that after a generic blue screen saying KMode Exception Not Handled with nothing else. That right away put me on a search for my video driver so I went for the dump file and that popped up. The dxgmms.sys. I have a MSI 1050 TI in it right now...I know, I know, With the latest drivers.
This only happens when I'm playing Graphic intensive games. Destiny II, Skyrim etc..
Any hope? This is a brand new install so there is no chance of a driver being left behind when I installed this one. Maybe get an older driver?
Well the basics of my output from the dbg look like this
Code:
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80341acbb64, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
KEY_VALUES_STRING: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804
SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
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: FD
BIOS_DATE: 02/26/2016
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: 970A-D3P
BASEBOARD_VERSION: To be filled by O.E.M.
DUMP_TYPE: 2
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80341acbb64
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff
READ_ADDRESS: fffff80341eed388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffffffffffffff
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
FAULTING_IP:
nt!KxWaitForLockOwnerShip+14
fffff803`41acbb64 48890a mov qword ptr [rdx],rcx
EXCEPTION_PARAMETER2: ffffffffffffffff
BUGCHECK_STR: 0x1E_c0000005_R
CPU_COUNT: 6
CPU_MHZ: 1017
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 2
CPU_STEPPING: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: Battle.net.exe
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: DESKTOP-NTVI15M
ANALYSIS_SESSION_TIME: 12-13-2018 14:38:01.0392
ANALYSIS_VERSION: 10.0.17763.132 amd64fre
DPC_STACK_BASE: FFFFF80343C64FB0
LAST_CONTROL_TRANSFER: from fffff80341ce0b5a to fffff80341c4a0a0
STACK_TEXT:
fffff803`43c63198 fffff803`41ce0b5a : 00000000`0000001e ffffffff`c0000005 fffff803`41acbb64 00000000`00000000 : nt!KeBugCheckEx
fffff803`43c631a0 fffff803`41c5294d : fffff803`41e91000 fffff803`41aa0000 00058254`00953000 00000000`00000000 : nt!KiFatalExceptionHandler+0x22
fffff803`43c631e0 fffff803`41b5eb16 : fffff803`43c63310 fffff803`43c637d0 00000000`00000000 fffff803`43c640e8 : nt!RtlpExecuteHandlerForException+0xd
fffff803`43c63210 fffff803`41b60613 : fffff803`43c640e8 fffff803`43c63e30 fffff803`43c640e8 fffff803`43c643a0 : nt!RtlDispatchException+0x416
fffff803`43c63900 fffff803`41c5ad42 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1f3
fffff803`43c63fb0 fffff803`41c5749c : 00000000`00000000 00000172`524cf087 ffff988b`81172700 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff803`43c64190 fffff803`41acbb64 : 00000000`00000000 fffff803`41e838c0 00000000`4b677844 00000000`00000002 : nt!KiGeneralProtectionFault+0x2dc
fffff803`43c64320 fffff803`41b39d1b : ffff988b`826001e0 00000000`00000002 00000000`00000211 fffff803`00000000 : nt!KxWaitForLockOwnerShip+0x14
fffff803`43c64350 fffff803`41d8b65c : ffff988b`825ff000 fffff803`43c644f8 00000000`00000000 00000000`00000000 : nt!ExFreeLargePool+0x93b
fffff803`43c64400 fffff806`6fc79992 : ffff988b`80146010 28ec8348`00000004 4c8d4838`24548d00 ffff988b`4b677844 : nt!ExFreePoolWithTag+0x5fc
fffff803`43c644e0 fffff806`6fc79069 : ffff988b`7b3e5690 fffff803`00000000 00000000`00000000 ffff988b`00000000 : dxgmms2!VidSchiProcessCompletedQueuePacketInternal+0x302
fffff803`43c64700 fffff806`6fc7f4a2 : ffff988b`7b3e5602 00000000`00000001 ffff988b`78dde030 00000000`00000000 : dxgmms2!VidSchiProcessDpcCompletedPacket+0x689
fffff803`43c648a0 fffff806`6f051b82 : fffff803`43c64999 ffff988b`7bfc4000 ffff988b`78dde660 00000000`00000000 : dxgmms2!VidSchDdiNotifyDpc+0x202
fffff803`43c64950 fffff806`719fa1f4 : ffff988b`78dde030 00000000`00000000 ffff988b`78dde030 ffff988b`79149000 : dxgkrnl!DxgNotifyDpcCB+0x72
fffff803`43c64a00 ffff988b`78dde030 : 00000000`00000000 ffff988b`78dde030 ffff988b`79149000 fffff806`719fa187 : nvlddmkm+0x11a1f4
fffff803`43c64a08 00000000`00000000 : ffff988b`78dde030 ffff988b`79149000 fffff806`719fa187 ffff988b`79149000 : 0xffff988b`78dde030
THREAD_SHA1_HASH_MOD_FUNC: 4c886272a13b8876a24a1cded43e38e41ac8a5de
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 4f36b1f25f62f39a71f308a0b29b69a97b6800d2
THREAD_SHA1_HASH_MOD: 675143bb7874a40547d080d33e09d9f3cfa7a743
FOLLOWUP_IP:
dxgmms2!VidSchiProcessCompletedQueuePacketInternal+302
fffff806`6fc79992 4c89b320010000 mov qword ptr [rbx+120h],r14
FAULT_INSTR_CODE: 20b3894c
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: dxgmms2!VidSchiProcessCompletedQueuePacketInternal+302
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 602e95ff
IMAGE_VERSION: 10.0.17134.471
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 302
FAILURE_BUCKET_ID: 0x1E_c0000005_R_dxgmms2!VidSchiProcessCompletedQueuePacketInternal
BUCKET_ID: 0x1E_c0000005_R_dxgmms2!VidSchiProcessCompletedQueuePacketInternal
PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_dxgmms2!VidSchiProcessCompletedQueuePacketInternal
TARGET_TIME: 2018-12-13T20:02:28.000Z
OSBUILD: 17134
OSSERVICEPACK: 471
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: 2018-12-08 01:36:08
BUILDDATESTAMP_STR: 180410-1804
BUILDLAB_STR: rs4_release
BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804
ANALYSIS_SESSION_ELAPSED_TIME: 1bbe
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_dxgmms2!vidschiprocesscompletedqueuepacketinternal
FAILURE_ID_HASH: {1caa7376-f61e-8227-ff18-6dc640bfb7de}
Followup: MachineOwner
-
December 13th, 2018, 06:16 PM
#2
-
December 13th, 2018, 06:37 PM
#3
-
December 13th, 2018, 07:53 PM
#4
You could try a previous driver version to see if that fixes anything. You would need to make sure that Microsoft doesn't "helpfully" re-upgrade you again.
-
December 13th, 2018, 07:58 PM
#5
Ya know? It is kind of funny. I didn't notice it until I updated it yesterday either.
Downgrade to upgrade, story of my life.
-
December 17th, 2018, 05:52 AM
#6
This was on a fx-6300 on a new video driver. It was OC'd and backed down, that's when I got the crashes. It's just going to be playing with it for a while (drivers and such) I guess to get it back up there. It's not that big of an increase though. I may leave it. I don't even think the boy notices. He'll sure take notice when he gets the 8350. Swapping in a 970a-ud3p for it. It should clock nicely.
Last edited by Ashalon1; December 17th, 2018 at 05:55 AM.
-
December 18th, 2018, 05:33 AM
#7
wrong no ud3p. I couldn't get it.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|