New/Sudden BSOD DXGMMS1.SYS

[lupodwdm]

So recently in the past few weeks I have been getting a BSOD that shows dxgmms1.sys. It happens totally randomly. This is my CUDA box do it's running SETI on 6 cores/12 threads and 3 GPU's at about 70%. Thing is that it will still BSOD even without CUDA running. I have saved my dump files and I would really appreciate any help you all may offer.

I am a MCSE 2003 and a MCITP SA/EA, but my expertise is in building enterprise domains, not fixing BSOD .

Can anyone tell me how to get started uploading the dump and what the normal protocol is on these forums.

Thanks,

Adam

 

[yowanvista]

Follow these instructions
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html


dxgmms1.sys suggest the Nvidia driver was involved in the crash


- Boot into safe mode with networking
- Uninstall the Nvidia drivers
- Use driver sweeper to remove leftover Nvidia display driver files Guru3D - Driver Sweeper
- Install the latest drivers http://www.nvidia.com/object/win7-winvista-64bit-260.99-whql-driver.html
- Reboot into normal mode

 

[lupodwdm]

Ok. I posted the report HTML and the BSOD. I tried downgrading to an earlier version of driver to see if that fixed the issue but it didn't help. I will be happy to compensate someone for their time in helping me figure this out.

 

[yowanvista]

nvlddmkm.sys, the Nvidia driver was the cause
Follow the instructions listed above for reinstalling it

BugCheck D1, {58, a, 0, fffff880052084c6}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessIsrCompletedPacket+46 )

 

[lupodwdm]

How do you get into safe mode in windows 7 again? F8?

I'm assuming your referring to these steps:
"Follow these instructions
Blue Screen of Death (BSOD) Posting Instructions


dxgmms1.sys suggest the Nvidia driver was involved in the crash


- Boot into safe mode with networking
- Uninstall the Nvidia drivers
- Use driver sweeper to remove leftover Nvidia display driver files Guru3D - Driver Sweeper
- Install the latest drivers http://www.nvidia.com/object/win7-wi...ql-driver.html
- Reboot into normal mode"

 

[yowanvista]

How do you get into safe mode in windows 7 again? F8?

I'm assuming your referring to these steps:
"Follow these instructions
Blue Screen of Death (BSOD) Posting Instructions


dxgmms1.sys suggest the Nvidia driver was involved in the crash


- Boot into safe mode with networking
- Uninstall the Nvidia drivers
- Use driver sweeper to remove leftover Nvidia display driver files Guru3D - Driver Sweeper
- Install the latest drivers http://www.nvidia.com/object/win7-wi...ql-driver.html
- Reboot into normal mode"

Here is a tutorial for this http://www.sevenforums.com/tutorials/69585-safe-mode.html

View attachment 126185


Follow these instructions concerning the Nvidia driver

- Boot into safe mode with networking
- Uninstall the Nvidia drivers
- Use driver sweeper to remove leftover Nvidia display driver files Guru3D - Driver Sweeper
- Install the latest drivers http://www.nvidia.com/object/win7-wi...ql-driver.html
- Reboot into normal mode

 

[lupodwdm]

Well, I tried all the steps you listed. Thanks so much to talking the time to look at the dump file. Hopefully this will fix it and I can hammer the hell out of this system and use ti for what it was designed for.
Thanks,

Adam

 

[lupodwdm]

You know, another question; how would this happen in the first place? Could a windows update have caused this?

 

[yowanvista]

You know, another question; how would this happen in the first place? Could a windows update have caused this?

Never let Windows Update download install hardware drivers, switch it to ' Check for updates but let me choose whether to download and install it'

Always use drivers from the manufacturer's website

 

[lupodwdm]

You know, another question; how would this happen in the first place? Could a windows update have caused this?

Never let Windows Update download install hardware drivers, switch it to ' Check for updates but let me choose whether to download and install it'

Always use drivers from the manufacturer's website

Didn't seem to do it. Problem came back today. I'll try the steps again and let you know.

 

[lupodwdm]

Oh, one more quick thing, I noticed that when I uninstalled the drivers and rebooted into safe mode to reinstall the new drivers, windows tried to install it's won drivers an it;'s own. Is there a way to stop this from happening?

 

[lupodwdm]

I posted the two dump files again. Maybe they will help. Let me know if you want the full 559 MB dump file. I can find a file sharing website and get it you that way.

Thanks again so much.

Adam

 

[yowanvista]

Dumps still blames your GPU drivers
This type of error can be caused by bad drivers, defective GPUs or bad RAM
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Disable SLI just to check if you still get the BSOD or use each GPU separately to identify the bad one

BugCheck D1, {50, 8, 0, fffff880053a3071}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextRunningTimeAtISR+21

 

[lupodwdm]

Still crashing in the same way. Performed the same steps again. Any more thoughts? This is a wast of an expensive system

 

[yowanvista]

Still crashing in the same way. Performed the same steps again. Any more thoughts? This is a wast of an expensive system

One of the GPU may be defective, use each one separately

 

[lupodwdm]

Here's something i don't understand. I don't think it's the cards. I can enable SLI and play games for hours without a BSOD. I can turn off SLI and run another CUDA project like DNET for HOURS without an issue. (Cards all at 99-100%). This must be something with BOINC or the drivers or something.

 

[lupodwdm]

It seems that turning off hyper-threading on the CPU solved the issue.