BSOD dxgmms1.sys, error 0x...03b, 0x...07f, etc

Hello,

I have bought a new PC and it began BSOD-ing on the second day. I've installed Skype, Steam, Dota 2, OBS programs only by that time. After trying different suggestions I've decided to reinstall Windows 7. So today I've installed Windows 7 Ultimate x64. Installed Skype, Steam, Dota 2, OBS and it BSOD again.

After BSOD windows shows info about it:

Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1049

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF880101B512B
BCP3: FFFFF88003281558
BCP4: FFFFF88003280DB0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\032314-8034-01.dmp
C:\Users\user\AppData\Local\Temp\WER-9656-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Besides BSOD my PC monitor can freeze and only mouse is moving and only reboot is working. I've disabled second monitor so far and tried to change Nvidia setting from "maximize 3d performance" to "disable SLI" and it didn't help too. If you need more info just ask, cause I don't really know what I am might missing. Thanks in advance a lot!

I've attached the file from DM log collector.
Attachment 311486

I am having different errors (7e, 10e, 7f, 3b) so I could not mention one.

Harribo2014 said:

Hello theses are to errors that i have found they seem to be cause by the driver.

dxgmms1.sys
ntoskrnl.exe

ntoskrnl.exe or ntkrnlmp.exe are not actually anything responsible for a BSOD, it is the kernel on which the BSOD occurred. When the crash dump recording mechanism fails to point a probable cause out, it blames the kernel itself, which is a wrong information actually. When you see something similar is said, it is to understand that something deeper is to be done to point out the actual cause.

Apparently the culprit behind the dxgmms1.sys failure is the display driver.

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff880101b512b, fffff88003281558, fffff88003280db0}

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

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

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

But the display drive is the latest. Version 335.23 WHQL.

Code:

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f454000 fffff880`100ac000   nvlddmkm   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue Mar 04 16:37:52 2014 (5315B408)
    CheckSum:         00C20523
    ImageSize:        00C58000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If the BSODs started to occur after updating the display driver, roll it back to a previous working one.

Also stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results. There may be some more work, will go for those after seeing the results.

Thank you for responding!

I've made a Furmark test and I didn't discover any artifacts (made it to ~20 000 frames). Temperature of GPU1 - 87C, GPU2 - 34C, avg fps 26

And I've installed BlueScreenView program that shows .dmp files info. So, there are files of BSOD so far:
-ntoskrnl.exe
-dxgmms1.sys
-watchdog.sys
-win32k.sys
-hal.dll
Attachment 311647

First two are more often to appear.

If you want to report a BSOD, click on it ....



It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip in your next post.

Good news!