Multiple, frequent BSODs playing full screen games.

Cptdraco · 02 Aug 2015

I have a computer here that has recently started getting BSoD very frequently. It seems to be happening more and more often now. The error varies and I have included as much information as I could in the upload. It always happens while running a full screen program like a game. I have tried memtest86, and the computer crashes and shuts down before the test can complete. I have uninstalled the graphics card drivers, ran Driver Sweeper, and reinstalled. The problem persists. Anyone who can check this bug report and give me a clue what to do would be appreciated. Thanks.

Laith · 06 Aug 2015

Hiya and welcome to SevenForums!

Code:

BugCheck D1, {fffff880ff0a2f59, 2, 8, fffff880ff0a2f59}

Probably caused by : usbohci.sys ( usbohci!OHCI_PollEndpoint+3f )

Code:

BugCheck 50, {fffffa8007ac4d60, 0, fffff8800f01d750, 2}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+6dc )

Run sfc /scannow and chkdsk /r.
Install the latest updates from Windows Update.

Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

SFC /SCANNOW Command - System File Checker

Cptdraco · 08 Aug 2015

Ran sfc, it says Windows Resource protection found corrupt files but was unable to fix them.

Here is an excerpt from the CBS.log

Code:

2015-08-08 00:05:31, Info                  CSI    00000325 [SR] Beginning Verify and Repair transaction
2015-08-08 00:05:31, Info                  CSI    00000326 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:hxHfXj427JxbVLpmOJKBMMwJ3nfvwV57qrOPwblWU6s=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-08-08 00:05:31, Info                  CSI    00000327 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-08-08 00:05:31, Info                  CSI    00000328 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:uJb1xc+7UfB0sWDxWhgMheOSADljkxkTslfhp7nidZg=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-08-08 00:05:31, Info                  CSI    00000329 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-08-08 00:05:31, Info                  CSI    0000032a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:hxHfXj427JxbVLpmOJKBMMwJ3nfvwV57qrOPwblWU6s=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-08-08 00:05:31, Info                  CSI    0000032b [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-08-08 00:05:31, Info                  CSI    0000032c [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-08-08 00:05:31, Info                  CSI    0000032d Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:uJb1xc+7UfB0sWDxWhgMheOSADljkxkTslfhp7nidZg=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
2015-08-08 00:05:31, Info                  CSI    0000032e [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-08-08 00:05:31, Info                  CSI    0000032f [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-08-08 00:05:31, Info                  CSI    00000330 Ignoring duplicate ownership for directory [l:92{46}]"\??\C:\ProgramData\Microsoft\Diagnosis\ETLLogs" in component Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

Laith · 08 Aug 2015

Hmm, have you installed the latest updates from Windows Update?

Cptdraco · 08 Aug 2015

Yes, all updates installed, and chkdsk /r passed perfectly. After these steps got another BSOD after and then the system froze completely. I also ran Memtest86 and it crashed at about 30% and shut down. I have ordered replacement RAM just in case. I am eligeable for a Windows 10 upgrade and I am considering taking it to see what happens. I can always revert back later.

Laith · 09 Aug 2015

And that's just MemTest86. in SevenForums we suggest running MemTest86+, it scans the DIMM slots aswell as the RAM. We'll wait and see what happens.

Cptdraco · 09 Aug 2015

Ok, well with the Windows 10 update it continues to lock up completely. I have to hard reset it each time. I am reverting the update because at least 7 gave me the BSODs. Memtest86+ gives the same result. That is the computer shuts down suddenly after about 30% of the test. It completely powers off. I wonder if that is the same thing causing it to freeze when the OS is booted, just happening with nothing running. I'll install the new RAM when it comes in and report back. Meantime, could bad memory cause this? Based on the bug reports shown?

Laith · 09 Aug 2015

In rare cases it can, but this sounds like a failing PSU. It shouldn't just power off like that.

Cptdraco · 09 Aug 2015

It only doess that during memtest, and always at the same point in the test. It doesnt power off by itself normally it literally locks up. The screen freezes completely then must be reset at the switch.

Laith · 10 Aug 2015

This could be a failing RAM. Replace the RAM and see what happens. If you want you can borrow a friends stick(s) aswell