The attached DMP file is of the IRQL_NOT_LESS_OR_EQUAL (a)
A kernel-mode driver or process attempted to access a protected memory location it does not have permission for, or a kernel interrupt request level (IRQL) attempted to access a memory address that is too high.
This bugcheck usually occurs when a driver uses an incorrect memory address. Other possible causes of this error include: bug in a device driver, system service, the BIOS, an old Anti-virus program or backup tool, or possibly memory issues.
1: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffff880`075e4778 fffff800`032801a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`075e4780 fffff800`0327ee20 : fffff8a0`2483e120 00000000`00000040 fffff8a0`3b0b5f58 fffffa80`1386c748 : nt!KiBugCheckDispatch+0x69
fffff880`075e48c0 fffff800`03286e42 : fffffa80`1386c6d0 fffffa80`0c6bc410 00000000`00000000 fffffa80`11d8bd30 : nt!KiPageFault+0x260 (TrapFrame @ fffff880`075e48c0)
fffff880`075e4a50 fffff800`03285246 : 00000000`00000000 fffff880`0636c1cc 00000000`00000000 fffffa80`0c6bc410 : nt!KiSignalSynchronizationObject+0x42
fffff880`075e4aa0 fffff880`0637c36b : fffffa80`00000000 00000000`00000000 fffffa80`19194a00 fffff880`075e4b60 : nt!KeSetEvent+0x106
fffff880`075e4b10 fffff880`0639a16d : fffffa80`00000000 fffffa80`0c6bc410 00000000`6d4d6956 fffff880`00000174 : dxgmms1!VidMmiProcessTerminationCommand+0x5f
fffff880`075e4b60 fffff880`063993f8 : fffff880`031dbf40 fffffa80`124f8d50 00000000`00000000 fffffa80`0c6bc410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`075e4b90 fffff880`06398e96 : 00000000`00000000 fffffa80`124f8d50 00000000`00000080 fffffa80`0c6bc410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`075e4bc0 fffff800`0351eede : 00000000`03d76bc7 fffffa80`09f1e8b0 fffffa80`0700d040 fffffa80`09f1e8b0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`075e4c00 fffff800`03271906 : fffff880`031d7180 fffffa80`09f1e8b0 fffff880`031e1fc0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`075e4c40 00000000`00000000 : fffff880`075e5000 fffff880`075df000 fffff880`075e4540 00000000`00000000 : nt!KxStartSystemThread+0x16
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )
We're seeing some dxgmms1 calls in the stack, possible video driver, video card or memory issues could cause dxgmms1.sys issues (DirectX MMS).
Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.
If video drivers are okay, let's run a Memtest for NO LESS than ~8 passes (several hours):
Download Memtest86+ here:
Memtest86+ - Advanced Memory Diagnostic Tool
Which should I download?
You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
How Memtest works:
Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.
The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.
Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.
Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.
This information, if available to the program, can be displayed via a menu option.
Any other questions, they can most likely be answered by reading this great guide here:
FAQ : please read before posting