dxgmms2.sys Bluescreen

According to the literature for your motherboard, AI Suite II provides access to voltage and sensor readings. If you open this Asus provided software the information should be there.

 

I don't think I installed AI suite I do have MSI afterburner... I only installed the drivers for my MB and not all the bloatware. But it can't be hard to go check the Bios... I would just need to know exacly what you're looking for and a general idea of where to find it.

 

Important: Is this System Over clocked?

As Bill suggested the Suite will give you the information you seek.

Here is a Video for your Bios.
All 12v rail voltages and Temps, are found under the "Monitor Tab"
Tap "Delete" on boot to get into the Bios. Then select "advanced mode". Use arrow keys.
F10 to Save/exit.

.

Next time you get a
dxgmms2.sys Bluescreen it is important to copy down precisely the list of errors at the bottom of the Blue Screen and Post the error codes.
This will further help us determine where the problem lay.

 

I will go check the bios And as for the Error report I have an app that lets me view the report Will that give you more info if I go look in the report and paste it here?

 

I asked was this System Over Clocked?
My guess it is most likely.

 

no it's not its stalk but the GPU is an XFX I think it was overclocked out of thebox also.
MB temp 30C

CPU temp on desktop at idle 24C

Vcore@ 1.356V
3.3V @3.288V
5V@4.992V
12V@12.046V
VDDA 2.5 @2.508V

I got an amdFX8350@Stock clocking Cooled by Corsair H100I water cooler
Ram is 1600mhz Stock clocking. Running on 1 stick of 8GB atm but usually I had 2 stick of 8
SamsungSSD + Seagate firecuda


File name : dxgmms2.sys
Adress in stack :dxgmms2.sys+5b3fc
From address :fffff808`e9200000
To address :fffff808`e92a7000
Size : 0x000a7000
Time stamp : 0x584a7bb9
Time string: 12/9/2016 5:39:05 AM

This is from the last time it happened.. has not happened since.

031417-7796-01.dmp 3/14/2017 6:33:48 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff808`e9250406 ffffca80`f81e4558 ffffca80`f81e3d80 dxgmms2.sys dxgmms2.sys+5b3fc x64 dxgmms2.sys+50406 C:\Windows\Minidump\031417-7796-01.dmp 8 15 14393 277,957 3/14/2017 6:34:20 AM

^ yesterday morning

Now today I've watched some youtube and rebooted a few times so far no crash... I will probably game later to see if it does it again but usually it does it every 2 days or so.

 

Have a read here. May help.
This is your error.

http://www.thewindowsclub.com/system_thread_exception_not_handled-blue-screen-on-windows-10

 

in that case doe it's nvlddmkm.sys << NVidia I have an AMD card... I also updated my drivers... SO far it hasn't done it again SO you're saying it's my GPU?

it would make sense if it was...it also says to check to make sure I have enough disk space.. I don't evne have 1 terra taken from my 2 terra drive and my ssd is not even 1/4 full.SO possibly a bad harddrive?

I ran check disks on my drives both came out clean. But if it's the gpu then possibly Driver problem.. which I think I would of resolved by using DDU and doing a clean driver install. But could also be hardware GPU problems? I think what's left for me to do right now is just run the system for a while and see if it does it again?

 

Run chkdsk /r on that Drive to be sure. Save the log.
Note space between "k" and "forward slash"

 

Ok I will redo check disks I done it by right clicking o nthe drives and running a scan but the way you say I will need help on how to run that and save the logs please.

 

Only run CHKDSK from Command Prompt. CMD

How to run chkdsk from command prompt in Windows 10

https://www.tekrevue.com/tip/fix-hard-drives-chkdsk-windows-10/


To read the chkdsk log:

https://www.tenforums.com/tutorials/40822-chkdsk-log-event-viewer-read-windows-10-a.html

PS. I am very busy at the moment. Be back later.

 

Log Name: Application
Source: Chkdsk
Date: 3/15/2017 6:28:40 AM
Event ID: 26212
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Matrixone
Description:
Chkdsk was executed in read-only mode on a volume snapshot.

Checking file system on C:
The type of the file system is NTFS.
Volume label is Samsung SSD.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...


281600 file records processed.

File verification completed.


7782 large file records processed.



0 bad file records processed.


Stage 2: Examining file name linkage ...


359124 index entries processed.

Index verification completed.


0 unindexed files scanned.



0 unindexed files recovered to lost and found.


Stage 3: Examining security descriptors ...
Security descriptor verification completed.


38763 data files processed.

CHKDSK is verifying Usn Journal...


41860496 USN bytes processed.

Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

249479167 KB total disk space.
94156104 KB in 204092 files.
143492 KB in 38764 indexes.
0 KB in bad sectors.
398267 KB in use by the system.
65536 KB occupied by the log file.
154781304 KB available on disk.

4096 bytes in each allocation unit.
62369791 total allocation units on disk.
38695326 allocation units available on disk.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Chkdsk" />
<EventID Qualifiers="0">26212</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-15T10:28:40.366824300Z" />
<EventRecordID>7833</EventRecordID>
<Channel>Application</Channel>
<Computer>Matrixone</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is Samsung SSD.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...


281600 file records processed.

File verification completed.


7782 large file records processed.



0 bad file records processed.


Stage 2: Examining file name linkage ...


359124 index entries processed.

Index verification completed.


0 unindexed files scanned.



0 unindexed files recovered to lost and found.


Stage 3: Examining security descriptors ...
Security descriptor verification completed.


38763 data files processed.

CHKDSK is verifying Usn Journal...


41860496 USN bytes processed.

Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

249479167 KB total disk space.
94156104 KB in 204092 files.
143492 KB in 38764 indexes.
0 KB in bad sectors.
398267 KB in use by the system.
65536 KB occupied by the log file.
154781304 KB available on disk.

4096 bytes in each allocation unit.
62369791 total allocation units on disk.
38695326 allocation units available on disk.
</Data>
<Binary>004C04008DB403001135070000000000F0000000680000000000000000000000</Binary>
</EventData>
</Event>

 

I notice at the top my F drive ( 2terra Barracuda) it says it's not specified? is that bad?

 

You need to update your "Universal serial bus controller Driver.
Find it in Device Manager. Expand "Universal Serial Bus Controllers" and update Drivers.

 

OK and after do I need to redo the chkdsk?

up date just asi opened Device manager it re did it!

031517-8546-01.dmp 3/15/2017 7:02:34 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff802`42980406 ffff9481`391eb558 ffff9481`391ead80 dxgmms2.sys dxgmms2.sys+5b987 x64 dxgmms2.sys+50406 C:\Windows\Minidump\031517-8546-01.dmp 8 15 14393 278,581 3/15/2017 7:03:16 AM

it seems to always do it about at the same time in the morning and then doesn't do it for the whole day... Could it be an app that tries to update itself and when it starts it crashes?

Any how I will update the serial bus thing!

 

If your system recognizes the Drive.

 

if the system Recognizes the drive?

I updated all the devices in that list... all says it already had the best drivers

Also after the crash this morning I Swapped my ram stick to the other one...To see if it will do it again with this ram stick if it does then it would mean the ram is not at fault?

 

Ohh you mean if it finds the drives in device manager? well my ssd is displayed as "Samsing SSD Pro 256Gb"
But the firecuda is displayed as ST2000DX002-2dv164 << is this normal? maybe I din't setup my second drive right? I pretty much just plugged it and made windows create a drive letter for it and started to add my games to it..


P.S I was Googling my error and I came apon this


"If the OP or someone else could configure their installation to create a kernel (or complete) dump file instead of a minidump it could have the info needed to find out what is happening.

Here are some instructions to change Windows so that it creates a kernel (or complete) memory dump instead of a minidump in the event of a crash:

Privacy Notice: A complete memory dump means ALL the contents of memory at the time of the crash, this includes your applications and any PII from those applications residing in memory, if you choose this option make sure you don't have anything running that you wouldn't want your mother seeing when it crashes.

If you don't want PII being exposed consider setting it to Kernel dumps only."

Would this help us in any way?

 

Dermister, at this point 3 of us have at least looked at your set of problems and a couple of us have tried to help. Two of us think if we had the machine in front of us we'd solve the difficulties. But our recommendation now is for you to take the machine to a computer shop for inspection and repair.

 

Ok so at this point ihave nothing to loose by trying to reformat? if that fails then swap the video card and if that fails PC shop?

Thank you guys for trying to help me out! May you be free of BSOD's because they suck

On the positive side we narrowed it down a little bit!