Frequent BSOD due to dxgmms1.sys? (Win 7 Pro)

P

PandaDiPanda

Member
Joined
Jan 30, 2020
Posts
18
Hello,

I’m urgently looking for some help because of frequent BSOD. Yesterday the system I work with crashed 10 times (BSOD) within 8 hours.

What happened before: I did a last attempt to fix the update problems with SURT [see my thread: “Trouble with KB3172605 among others (Windows 7 Pro)”]. Its preliminary installation tasks took one and a half hours - without final success because the system crashed:


INTERRUPT_EXEPTION_NOT_HANDLED
0x0000 003D
dxgmms1.sys


“dxgmms1.sys” is very often listed in BSOC reports thereafter:

0x0000 007E
dxgmms1.sys

SYSTEM_SERVICE_EXCEPTION
0x0000 003B
fltmgr.sys

0x0000 001E

0x0000 007F
dxgmms1.sys

PAGE_FAULT_IN_NONPAGED_AREA
0x0000 001A
dxgmms1.sys

memory management
0x0000 001A

SYSTEM_SERVICE_EXCEPTION
0x0000 003B


two times:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x0000 00D1
dxgmms1.sys



If the update problems were solved, would the dxgmms1.sys problem vanish, too?



Running SysnativeBSODCollectionApp.exe Kaspersky reported a trojan infection of your application:

Trojan.Win32.Generic
Trojan.Multi.GenAutorunReg.a

I canceled the BSOD analysis. Would a *dmp file also serve the purpose?



Thanks a lot for your reply.
 
Hi PandaDiPanda,

Welcome to Sysnative!

If the update problems were solved, would the dxgmms1.sys problem vanish, too?
Click to expand...
Most BSOD Analysts are in no position to judge, including myself, because most of us don't assist with Windows Update problems.
The helper in your first Windows Update thread, @softwaremaniac, might be able to answer your question.


From time to time there are some issues with the Sysnative BSOD Collection tool and antivirus software, but rest assured that the detection is a false positive.
I just downloaded the tool and used VirusTotal to scan the file, zero detections.
VirusTotal
I would like to mention that the engine of the antivirus in VirusTotal might be slightly different from the engine of the antivirus you have locally, but I can't say how or why it might be different. Regardless, it's perfectly safe to run the tool, as hundreds or even thousands of other users have done before you.

Would a *dmp file also serve the purpose?
Click to expand...
Unfortunately not, while dumps are one of the most important elements in the analysis we also need other information such as installed programs, Windows Error Report logs, event logs, and hardware information for example.
 
Thank you very much for your reply.

I ignored the warnings by Kaspersky and did not cancel the Sysnative BSOD Collection tool. I tried it twice. Both times the system crashed. So, the attached files are probobly not complete.
 

Attachments

I'll do the RAM test.

Besides that, following the instructions given in Sysnative BSOD manual I tried to create a restore point – without success: path not found (0x80070003) // start create “not found”. So, I was wondering if it might be possible for you to tell me whether it is possibly a problem of set value, or how to change the value, respectively?
 
I would like to have a look at the health of the drives.
Please go to Download and click the blue zip button which will download a portable version of CrystalDiskInfo. Extract the zip file and run diskinfo64.exe which will ask for administrator rights, please allow it.
CrystalDiskInfo uses 3 colors for indication

  • Blue = good
  • Yellow = warning
  • Red = bad

A little below the menu you'll see drives with each a circle with a color, if any of these is NOT blue please click it.
Before making a screenshot, please do the following
- Go to function > Advanced feature > raw values, change it to 10 [DEC]
- Make sure all attributes are clearly visible
Make a screenshot of CrystalDiskInfo and post this screenshot in your next post.
Rich (BB code): 


 2020-02-04T14:52:18.953Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-04T14:52:16.972Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-04T09:11:44.826Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-04T09:11:42.845Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-04T01:56:18.830Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-04T01:56:16.848Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-04T00:47:51.610Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-04T00:47:49.644Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-04T00:23:51.001Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-04T00:23:49.020Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-04T00:08:58.003Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-04T00:08:56.037Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T23:39:50.670Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T23:39:48.689Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T23:25:51.859Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T23:25:49.862Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T22:46:15.608Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T22:46:13.642Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T21:58:22.812Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T21:58:20.831Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T21:54:30.344Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T21:54:28.363Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T21:46:27.674Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T21:46:25.661Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T21:20:12.468Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T21:20:10.471Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T17:18:33.984Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T17:18:32.034Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T15:22:04.968Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T15:22:03.018Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T13:31:23.776Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T13:31:21.764Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T11:31:28.188Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T11:31:26.114Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T10:02:10.095Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T10:02:08.114Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T00:45:07.672Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T00:45:05.691Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T00:23:30.984Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-03T00:23:28.956Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T23:03:52.577Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T23:03:50.596Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T20:45:46.468Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T20:45:44.502Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T20:39:50.842Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T20:39:48.892Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T20:32:20.943Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T20:32:18.931Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T20:24:06.452Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T20:24:04.440Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T20:04:05.486Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T20:04:03.505Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T14:58:13.954Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T14:58:11.942Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T11:36:10.986Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T11:36:09.020Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T09:33:17.939Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-02T09:33:15.942Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-01T22:28:21.783Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-01T22:28:19.848Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-01T22:20:48.248Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-01T22:20:46.251Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-01T21:46:22.343Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 2020-02-01T21:46:20.346Fehlerhafter Block bei Gerät \Device\Harddisk0\DR0.
 
Thank you for the screenshot, the drive's health appears to be better than I expected.
Let's see if we can bring down the count of current pending sectors, open an administrative command prompt or powershell (right click > run as administrator) and enter either of the following commands

For powershell:
Code: 
chkdsk D: /r; chkdsk C: /r

For command prompt:
Code: 
chkdsk D: /r & chkdsk C: /r

For C you will have to schedule the task to run at boot, allow it and reboot.

Although you have an SSD, chkdsk can be used on SSDs as well as HDDs. Depending on what chkdsk has to do this may take a few hours even though it's an SSD.
After the commands are finished, please run the following tool by SleepyDude and copy and paste the log in your post: ListChkdskResult.exe
 
Last edited:
Hi,
concerning the RAM test. There is no memtest86-usb.iso file to select. Just a *.img file. I'm not sure, that it would serve the purpose. Oh, I'm afraid bits and bytes are not my favorite things... ...
 
An img file is for Linux.

Assuming you have UEFI, click the green button at MemTest86 - Download now!
If you don't, search 'MemTest86 V4.3.7 (OLD RELEASE)' and click on any of the first 3 links below it.
 
Hi axe0,

I did my best to get memtest86 run. Without success. USB stick does not boot. I know, it is not the same, because parts of RAM can not be tested, but I started Window's own memory check: No damage detected.

Might it be possible to tackle the update problem first?

Thanks a lot.
 
It's suspected that potential memory issues contribute to the update problem.

In my previous post, I did not check the specifications of your motherboard yet and made an incorrect assumption. MemTest86 v8.* doesn't support systems who don't have UEFI and therefore it won't boot.
After checking the manual of your motherboard I realized my mistake, please make sure that you download Memtest86 V4.3.7 for Windows.
 
The following steps are copied from the detailed steps for burning memtest86 on a USB stick from the MemTest86 tutorial.

Launch the included application: imageUSB.exe.
  • Click Yes in the user account window that should appear, if you didn't disable UAC settings (Control Panel\User Accounts\User Accounts).
  • Step 1: Select your USB stick from the list.
  • Step 2: (if it is not already selected) Select 'Write image to USB stick'.
  • Step 3: (if it is not already selected) Select the included image file: memtest-usb.iso.
  • Step 4: Click 'Write'.
    Click Yes to confirm the operation and Yes to the final warning (it says it will delete all data in the USB stick).
    After it completes, the USB stick should be ready to be used.
    It takes about 30 seconds on my system.
 
Oh, axe0, what shall I do? It is impossible to select the memtest-usb.iso file because there is no such file in the unzipped folder of "Image for creating bootable USB Drive". ... ... I was wondering if it might be possible to you to attach the missing memtest-usb.iso file at your reply? It would be great!
 
Try it, although there's no ISO file it should work just fine. As soon as I open imageUSB.exe the .img file is automatically selected and everything else is just the same.
 
Thank you very much for your patience. After 5 more attempts to get it work, the system gave up all its resistance ... memtest86 started.

After "Pass 1 completed" a warning was shown: "CPU over temperature", the system crashed. Software like CPUcool does not work during memtest, does it?
 
No, within the test there's not really any other software available you could use.

When was the last time your computer was cleaned from dust?
 
axe0 said:
When was the last time your computer was cleaned from dust?
Click to expand...
It so happened yesterday. I remembered, dust makes all worse.

Concerning memtest: It found quiet a few errors in test #6 and #7 (all in all 640) as well as some bit errors. I'll have to run memtest overnight once more, because I forgot to change the number of passes.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top