Frequent BSOD while playing League of Legends [ntoskrnl.exe]

[ThatBenderGuy]

This has been happening numerous times within the past few months and it usually happens mostly when I am playing League of Legends and I have skype running. It has crashed a couple of time with only Aptana and Google Chrome open.

Graphics: NVIDIA GeForce GTX 650 Ti BOOST (EVGA)
Ram: 12.0GB Dual-Channel DDR3
Motherboard: ASUSTek P8Z77-M

I have attached my dmp files to this thread.

According to blue screen view the culprit for my latest BSOD was AgileVpn.sys with a "SYSTEM_SERVICE_EXCEPTION" bug check string.

The 2nd latest one was rdpbus.sys also with a "SYSTEM_SERVICE_EXCEPTION"

and the 3rd latest was cdrom.sys with "SYSTEM_SERVICE_EXCEPTION" as well.


I have taken a look into my device manager and it appears the only thing that has a warning on it is the hlnfd driver with this device status: "This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)" I don't know if this has anything to do with my bsod's but thought I would share that just in case it does.

A similar thing has happened before with all these bsods while playing League about a month ago and I ran memtest and found out it was 1 bad ram-chip. I ran each individual chip (out of 4) for 2-3 hours each and found the bad one, removed it, and that had fixed my bsods for about a month. Now they are popping up again but not as frequent as before. You don't think it's possible another ram chip already went bad again do you?

Any help would be appreciated on the subject

-Cheers, Jacob

 

[Thedoctor44]

Please remove AVg as it can cause BSODs.
Replace it with Microsoft Security Essentials and Malwarebytes.

Microsoft Security Essentials - Microsoft Windows

Malwarebytes | Free Anti-Malware & Internet Security Software

   Warning

Make sure you don't activate the free trial of malwarebytes

Stress test your graphics card with Furmark

I recommend running it for around 30 minutes

   Warning

Furmark will increase the temperature of your GPU rapidly so keep and eye on your temperatures

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

If everything passes and the AVG removal doesn't fix the issues then try rolling back your GPU driver to 314.22

Here's some useful instructions.

http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html#post2740806

Let us know how everything goes.

 

[ThatBenderGuy]

Ok so I uninstalled AVG and installed the 2 anti-virus software you recommended and ran both memtest86 and Furmark and they both returned no errors.

It seems like they are possibly progressing in terms of how often they happen. Here are the 10 most recent BSODs I have gotten in the past 2 days, Maybe these can give a hint at what's causing them?

 

[Thedoctor44]

It seems your video capture software by Creative Technologies is causing memory corruption.
Please remove it.

*** WARNING: Unable to verify timestamp for V0690Vid.sys
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="Red"]V0690Vid.sys[/COLOR]
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )

 

[ThatBenderGuy]

Thank you, I uninstalled it and I will post back here in a couple days and if it hasn't blue screened i'll mark it as solved. I just want to make sure it doesn't blue screen in the next couple days before i mark it solved.

 

[ThatBenderGuy]

Alright since the uninstalling of the Creative Technologies application I've only had 1 bsod so far, which is significantly less then how often I was getting them, I looked up the driver that caused it and it was a driver called HECIx64.sys which seems to be Intel Management Engine Interface. I've attached the dump file to this reply. I'm not sure if I should be looking for that driver or if there's another cause.

EDIT:
I did a little research as well as using device manager to look at a few things. I noticed that there doesn't appear to be any errors next to IMEI in device manager but it is version 8.1.0.1263 while the latest version is 9.5.24.1790 (IMEI V 9.5.24.1790). Should I download the newer one and install it?

 

[Thedoctor44]

Yes download the latest Intel Management Engine Interface drivers. I'm on my mobile so I can't look at the dumps at the moment.

 

[Thedoctor44]

Can you also enable driver verifier but only enable the options: Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Reuqests

Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, and so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there are no points, make a System Restore Point Manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[ThatBenderGuy]

Ok I ran DV and got a crash here is the dump.

 

[Thedoctor44]

There is nothing in the dump file that points to anything, can you leave it running again for 24 hours.

 

[ThatBenderGuy]

Here are some dumps from the past few days

 

[Thedoctor44]

Can you switch to Kernel Memory Dumps.

Follow these instructions on how to change your dump files to Kernel Memory Dumps.

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Once your dump file creation has changed, reboot the computer and wait for another BSOD.
When a new BSOD has occurred go to this directory:
C:/Windows/memory.dmp

Copy that dump file to the desktop, then upload it to a program like OneDrive, once uploaded post the link in your next reply and I'll take a look.

 

[ThatBenderGuy]

Okay here is the link to the memory.dmp file that was created after I recieved a BSOD after switching to kernal memory dump

https://onedrive.live.com/redir?resid=8C505EA5D4F258D1!107

 

[Thedoctor44]

Your realtek network driver is out of date.

fffff880`0426f000 fffff880`04322000   Rt64win7   (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        [COLOR="Red"]Tue Jun 12 15:00:29 2012[/COLOR] (4FD74B7D)
    CheckSum:         000B8CFC
    ImageSize:        000B3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I need your msinfo32 file.

Click on this button.



Once downloaded run the file as administrator then upload the folder created on your desktop.

 

[ThatBenderGuy]

Here's the folder that was given to me from the application, i'm looking up the updated drivers right now for realtek network driver

 

[Thedoctor44]

Download the driver here:

Realtek

Make sure you choose the right version for your OS.

Just to make sure, create a restore point by following these instructions.

 

[ThatBenderGuy]

Alright I installed the driver after creating a restore point. Why was it you needed that msinfo32 file?

 

[ThatBenderGuy]

Ok so I got another BSOD but I decided to look at memory.dmp with WindDbg and it's telling me that chrome.exe was probably the cause. That's odd that it would be my browser causing BSODs

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffffa8009ffbbd0, Object whose reference count is being lowered
Arg3: 0000000000000002, Reserved
Arg4: c100000000000002, Reserved
	The reference count of an object is illegal for the current state of the object.
	Each time a driver uses a pointer to an object the driver calls a kernel routine
	to increment the reference count of the object. When the driver is done with the
	pointer the driver calls another kernel routine to decrement the reference count.
	Drivers must match calls to the increment and decrement routines. This bugcheck
	can occur because an object's reference count goes to zero while there are still
	open handles to the object, in which case the fourth parameter indicates the number
	of opened handles. It may also occur when the object’s reference count drops below zero
	whether or not there are open handles to the object, and in that case the fourth parameter
	contains the actual value of the pointer references count.

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


DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x18

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8000302fe14 to fffff80003089bc0

STACK_TEXT:  
fffff880`089efa08 fffff800`0302fe14 : 00000000`00000018 00000000`00000000 fffffa80`09ffbbd0 00000000`00000002 : nt!KeBugCheckEx
fffff880`089efa10 fffff800`0333ea7d : fffff880`089efb60 00000000`00000000 00000000`00000000 00000000`73947b00 : nt! ?? ::FNODOBFM::`string'+0x48de1
fffff880`089efa70 fffff800`03088e53 : fffffa80`0a29a060 00000000`00000000 00000000`00000000 fffffa80`0a244101 : nt!NtReleaseSemaphore+0xcd
fffff880`089efae0 00000000`73912e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`035bee58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73912e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+48de1
fffff800`0302fe14 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+48de1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_VERSION:  6.1.7601.18409

FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+48de1

BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+48de1

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x18_corrupt_ref_count_nt!_??_::fnodobfm::_string_+48de1

FAILURE_ID_HASH:  {d3af5bf2-5e99-93a2-1458-fbf7f0106024}

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

here is the link to the dump on my oneDrive

https://onedrive.live.com/redir?resid=8C505EA5D4F258D1!109

 

[Thedoctor44]

You didn't roll back your display driver as requested earlier.
Roll back to 314.22 as directed previously.

fffff880`0f0ca000 fffff880`0fd22000   nvlddmkm   (export symbols)       nvlddmkm.sys
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="Red"]Tue Mar 04 11:07:52 2014 [/COLOR](5315B408)
    CheckSum:         00C20523
    ImageSize:        00C58000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The latest driver is looping a lot,

fffff880`089edd68  fffff880`0f2b6152 [COLOR="red"]nvlddmkm+0x1ec152[/COLOR]
fffff880`089edd70  00000000`00000000
fffff880`089edd78  fffff880`089ede20
fffff880`089edd80  fffffa80`0972e000
fffff880`089edd88  fffff880`0f2b5da5 [COLOR="red"]nvlddmkm+0x1ebda5[/COLOR]
fffff880`089edd90  00000000`00000000
fffff880`089edd98  00000000`006100bc
fffff880`089edda0  00000000`00000000
fffff880`089edda8  fffff880`0f2b5da5 [COLOR="red"]nvlddmkm+0x1ebda5[/COLOR]
fffff880`089eddb0  00000000`00000000
fffff880`089eddb8  fffff880`089ede60
fffff880`089eddc0  fffffa80`0972e000
fffff880`089eddc8  fffff880`0f2b6152 [COLOR="red"]nvlddmkm+0x1ec152[/COLOR]
fffff880`089eddd0  00000000`00000000
fffff880`089eddd8  fffff880`0f2b5da5 [COLOR="red"]nvlddmkm+0x1ebda5[/COLOR]
fffff880`089edde0  00000000`006100bc
fffff880`089edde8  fffff880`0f295b14 [COLOR="red"]nvlddmkm+0x1cbb14[/COLOR]
fffff880`089eddf0  00000000`006100bc
fffff880`089eddf8  fffff880`0f2dcfd0 [COLOR="red"]nvlddmkm+0x212fd0[/COLOR]
fffff880`089ede00  00000000`00000000
fffff880`089ede08  fffff880`0f2b5da5 [COLOR="red"]nvlddmkm+0x1ebda5[/COLOR]
fffff880`089ede10  fffffa80`0972e000
fffff880`089ede18  fffff880`0f2b6152 n[COLOR="Red"]vlddmkm+0x1ec152[/COLOR]

 

[ThatBenderGuy]

I apologize, I thought I rolled back my GPU driver but I must have accidentally updated it.

Well after I rolled it back I got another BSOD

https://onedrive.live.com/redir?resid=8C505EA5D4F258D1%21110

it looks like it might have something to do with audiodg.exe.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880048a2798, fffff8800a7c4e90, 0}

Probably caused by : ksthunk.sys ( ksthunk!CKernelFilterDevice::DispatchIrp+90 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880048a2798, Address of the instruction which caused the bugcheck
Arg3: fffff8800a7c4e90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
ksthunk!CKernelFilterDevice::DispatchIrp+90
fffff880`048a2798 ff5038          call    qword ptr [rax+38h]

CONTEXT:  fffff8800a7c4e90 -- (.cxr 0xfffff8800a7c4e90)
rax=92fff880048a4770 rbx=0000000000000001 rcx=fffffa800aff9180
rdx=fffffa800d505bd0 rsi=fffffa800aff9180 rdi=fffffa800d505bd0
rip=fffff880048a2798 rsp=fffff8800a7c5870 rbp=fffffa800d505fb8
 r8=0000000000000000  r9=fffff8800a7c58e0 r10=0000000000000028
r11=0000000000000006 r12=0000000000000003 r13=0000000000000001
r14=0000000000000000 r15=fffffa800b928b70
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
ksthunk!CKernelFilterDevice::DispatchIrp+0x90:
fffff880`048a2798 ff5038          call    qword ptr [rax+38h] ds:002b:92fff880`048a47a8=????????????????
Resetting default scope

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033aee67 to fffff880048a2798

STACK_TEXT:  
fffff880`0a7c5870 fffff800`033aee67 : fffffa80`0a3f94d0 fffff880`0a7c5b60 fffffa80`00000000 fffffa80`0a3f94d0 : ksthunk!CKernelFilterDevice::DispatchIrp+0x90
fffff880`0a7c58d0 fffff800`033af6c6 : 00000000`0331f6a0 00000000`00000995 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0a7c5a00 fffff800`03090e53 : fffffa80`0dd14b50 00000000`0331f688 fffff880`0a7c5a88 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`0a7c5a70 00000000`76ee132a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0331f658 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ee132a


FOLLOWUP_IP: 
ksthunk!CKernelFilterDevice::DispatchIrp+90
fffff880`048a2798 ff5038          call    qword ptr [rax+38h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ksthunk!CKernelFilterDevice::DispatchIrp+90

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ksthunk

IMAGE_NAME:  ksthunk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bca93

STACK_COMMAND:  .cxr 0xfffff8800a7c4e90 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_ksthunk!CKernelFilterDevice::DispatchIrp+90

BUCKET_ID:  X64_0x3B_ksthunk!CKernelFilterDevice::DispatchIrp+90

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

0: kd> lmvm ksthunk
start             end                 module name
fffff880`048a2000 fffff880`048a7200   ksthunk    (pdb symbols)          c:\symbols\ksthunk.pdb\A58068C2E5CB41E6B685D3866CA394141\ksthunk.pdb
    Loaded symbol image file: ksthunk.sys
    Image path: \SystemRoot\system32\drivers\ksthunk.sys
    Image name: ksthunk.sys
    Timestamp:        Mon Jul 13 17:00:19 2009 (4A5BCA93)
    CheckSum:         0000AF92
    ImageSize:        00005200
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I'm updating my audio driver right now. I'll let you know if BSOD again



-----------------------------------------------------
EDIT
-----------------------------------------------------

Ok got another one this time it's for dxgmms1.sys

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff880043ac10e, fffff88004034558, fffff88004033db0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+86 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: fffff880043ac10e, The address that the exception occurred at
Arg3: fffff88004034558, Exception Record Address
Arg4: fffff88004033db0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+86
fffff880`043ac10e 8b4810          mov     ecx,dword ptr [rax+10h]

EXCEPTION_RECORD:  fffff88004034558 -- (.exr 0xfffff88004034558)
ExceptionAddress: fffff880043ac10e (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x0000000000000086)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88004033db0 -- (.cxr 0xfffff88004033db0)
rax=c2fffa800b6c3990 rbx=fffff8a011f38010 rcx=fffff8a011f38010
rdx=0000000000000000 rsi=fffffa800d6cc2b0 rdi=fffffa800c7d2000
rip=fffff880043ac10e rsp=fffff88004034790 rbp=0000000000000000
 r8=fffffa800d6cc300  r9=0000000000000001 r10=0000000000000000
r11=fffffa800c7d33e8 r12=0000000000000038 r13=0000000000000000
r14=fffffa800a117140 r15=00000000000000d5
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x86:
fffff880`043ac10e 8b4810          mov     ecx,dword ptr [rax+10h] ds:002b:c2fffa80`0b6c39a0=????????
Resetting default scope

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+86
fffff880`043ac10e 8b4810          mov     ecx,dword ptr [rax+10h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880043a99d3 to fffff880043ac10e

STACK_TEXT:  
fffff880`04034790 fffff880`043a99d3 : 00000000`00000000 fffffa80`0a3231c0 00000000`000000d5 fffffa80`0daec548 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x86
fffff880`040347d0 fffff880`043c37d9 : 00000000`00000000 fffff8a0`05b04cc0 fffffa80`00000000 fffffa80`0a117140 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`040349a0 fffff880`043c3514 : fffff880`02fdbf40 fffff880`043c2f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04034b90 fffff880`043c3012 : 00000000`00000000 fffffa80`0dce8d50 00000000`00000080 fffffa80`0ae1b410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04034bc0 fffff800`0331b73a : 00000000`040b1e34 fffffa80`0b6c3b50 fffffa80`0970c990 fffffa80`0b6c3b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04034c00 fffff800`030708e6 : fffff880`02fd7180 fffffa80`0b6c3b50 fffff880`02fe1fc0 00000000`00000004 : nt!PspSystemThreadStartup+0x5a
fffff880`04034c40 00000000`00000000 : fffff880`04035000 fffff880`0402f000 fffff880`04034540 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+86

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

STACK_COMMAND:  .cxr 0xfffff88004033db0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+86

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+86

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

The memory dump uploaded to my onedrive is still the previous one. Let me know if you want the memory dump from this BSOD