BSODs while gaming

The logs had displayed the recovered entry before the Windows upgrade.
There were no entries in the post upgrade logs.

It can occur as a secondary event or a primary event.

If the problem continues post Windows 10 upgrade:

The GPU hardware testing was incomplete.
Testing was aborted due to temperatures.

Testing of GPU problems can be performed by:

a) software: Furmark
b) removing dGPU on computers that have iGPU and connecting the display to the motherboard
c) swapping the GPU

The AMD chip did not display integrated GPU.
See if you can find a friend, neighbor, relative, or local computer store to swap the GPU.
The swap can be Nvidia or AMD.

Make two tests:
1) test the GPU card from the problematic computer in another computer
2) test a new card in the problematic computer

Code:

Event[4310]:
  Log Name: System
  Source: Display
  Date: 2019-10-06T10:44:58.814
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-GG8A1VQ
  Description: 
Display driver nvlddmkm stopped responding and has successfully recovered.

Event[4311]:
  Log Name: System
  Source: Display
  Date: 2019-10-06T10:45:09.789
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-GG8A1VQ
  Description: 
Display driver nvlddmkm stopped responding and has successfully recovered.

The black screen issue happened again after updating windows. Here's the log

Attachment 251013

I managed to get my hands on an old GTX 570. The black screen issue isn't happening after swapping the GPU. Is there any further testing I should do to confirm that my GPU was causing the BSODs?

The swap of 770 to 570 in the problematic computer eliminates problems related to the motherboard and motherboard ports as there was normal performance of the 570.
The test duration though is important as there were no problems seen in the logs with the 770 after the Windows 10 upgrade.
So see what happens during a week of testing.

The best testing is to swap with the identical hardware in the problematic computer: 770 > 770
If there are no performance problems this confirms a problem with the initiall 770.

Swapping 770 > 570 supports problems with the 770 if there are no performance problems.
Best testing is to test the 770 in another computer.
If there are problems in performance in the second computer this support problems with the 770.
If there are no problems after testing for one week then other testing needs to be done.

Testing could include:
a) a fresh install of new Nvidia drivers
b) test older Nvidia drivers
c) placing the computer in clean boot > evaluate for performance problems
d) placing the computer in safe mode > evaluate for performance problems
e) make a backup image > perfor a clean install > evaluate for performance problems >
if there are none > restore the image > retest for performance problems
if there are continued performance problems > replace the card


1) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
2) re-install the Nvidia GPU driver from the Nvidia website
3) make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller Download version 18.0.1.5 (or newer version if available)
Official Display Driver Uninstaller DDU Download

Display Driver Uninstaller: How to use - Windows 7 Help Forums
Display Driver Uninstaller: How to use - Windows 7 Help Forums

Download Drivers | NVIDIA
Download Drivers | NVIDIA

It was the graphics card. After a few days of using the 570 with no issues, I switched back to the 770 and the computer became unstable again, crashing every now and then. I bought a new graphics card, and so far everything seems to be working fine. Thank you for your help.

That's great news.

Glad to see it sorted.

You are very welcome.

Unfortunately the BSODs are back. I can't get the log collector to work. The command prompt window closes immediately every time I try running it. Here is a link for the memory.dmp file.

Dropbox - MEMORY.zip - Simplify your life

1) List all installed AV (always on and manual)

2) Open administrative command prompt and type or copy and paste:
3) sfc /scannow
4) dism /online /cleanup-image /scanhealth
5) dism /online /cleanup-image /restorehealth
6) sfc /scannow
7) chkdsk /scan
8) wmic recoveros set autoreboot = false
9) wmic recoveros set DebugInfoType = 7
10) bcdedit /enum {badmemory}

11) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

12) Make sure that there is no over clocking while troubleshooting.

13) Place the computer in clean boot:
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

14) Run each V2 and DM while in clean boot
BSOD - Posting Instructions

15) If V2 is problematic while in clean boot then run while in safe mode:
Boot into Safe Mode on Windows 10

Microsoft Windows [Version 10.0.18362.418]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.418

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.418

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>
C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

The system file repair changes will take effect after the next reboot.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
227072 file records processed.
File verification completed.
5211 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
169 reparse records processed.
309752 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
169 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
41341 data files processed.
CHKDSK is verifying Usn Journal...
36916240 USN bytes processed.
Usn Journal verification completed.

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

267955199 KB total disk space.
212333276 KB in 155592 files.
111888 KB in 41342 indexes.
0 KB in bad sectors.
340775 KB in use by the system.
65536 KB occupied by the log file.
55169260 KB available on disk.

4096 bytes in each allocation unit.
66988799 total allocation units on disk.
13792315 allocation units available on disk.

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-ML84T3L\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition4"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-ML84T3L\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition4"'
Property(s) update successful.

C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\Windows\system32>

- - - Updated - - -

I have no AV software installed.
I'm not sure if XMP is considered an overclock. Should I disable it?

Attachment 253850
Attachment 253851

Attachment 253939Attachment 253940Attachment 253941Attachment 253942Attachment 253943Attachment 253944Attachment 253945Attachment 253946Attachment 253947Attachment 253948Attachment 253949Attachment 253950Attachment 253951Attachment 253952Attachment 253953Attachment 253954Attachment 253955Attachment 253956Attachment 253957Attachment 253958Attachment 253959Attachment 253960Attachment 253961Attachment 253962