BSODs while gaming

Hi

I recently upgraded my motherboard+cpu and I've been getting BSODs ever since, mainly while playing Borderlands 3.
The minidumps all show ntoskrnl.exe as the cause.

OS: Windows 10 version 1803
CPU: AMD Ryzen 3600
GPU: GTX 770
RAM: 16GB DDR4 3200MHz
Motherboard: MSI B450 Tomahawk Max

Any help would be appreciated.

Thanks

Attachment 250462

Have you recently reinstalled Windows or used some sort of disk cleaner to clean everthing? I ask because there's only 1 minidump included in the uploaded reports. The MSINFO32 report shows 8 BSOD events (along with approx 10 Live Kernel Events).

What is the make, model, wattage and age of your PSU?
I ask because you may have a lot of hardware attached (I see 4 hard drives presnt).

This driver dates from 2005 and may not be compatible w/Windows 10:

Code:

ssgdio64.sys                Fri Sep  9 14:40:54 2005 (4321D736)

MSINFO32 shows it as this:

Code:

ssgdio	Showshock Softnology Generic Driver	\??\c:\windows\syswow64\drivers\ssgdio64.sys	Kernel Driver	Yes	Auto	Running	OK	Normal	No	Yes

A Google search shows it may be related to an ATI Hardware diagnostic software tool
Please:
- uninstall the software program that uses this driver
- update ALL of your ATI/AMD software

In the event that you can't get rid of it that way, we'll try other steps after you let us know.

Please uninstall MSI Afterburner and RivaTuner.
In the past they were known to cause BSOD's with the RTCore64.sys driver
After we're finished testing, feel free to reinstall these programs if they're needed.

The lone memory dump is most often associated with driver problems.
If the BSOD's continue after following the above steps, then please run Driver Verifier according to these instructions:
Enable and Disable Driver Verifier in Windows 10
The purpose of Driver Verifier is to cause a BSOD and capture a memory dump that has evidence of the faulty driver.
Zip up that memory dump (found in C:\Windows\Minidump) and upload it with your next post.

While waiting for a reply, please try these free hardware diagnostics (in case this is a hardware problem):

1) Memtest86 (not 86+): MemTest86 - Official Site of the x86 Memory Testing Tool

2) SeaGate SeaTools for Windows (test ALL hard drives - HDD/SSD/USB/etc): How to use SeaTools for Windows | Seagate Support US

3) Intel Processor Diagnostic Tool: Download Intel(R) Processor Diagnostic Tool
Disregard if not using an Intel processor

4) Furmark stress test for GPU: FurMark > Downloads
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

5) OCCT: OCBASE / OCCT
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall
Be sure to also run it's PSU test

I'm not using any disk cleaners, but I did notice that the minidumps keep disappearing after a few days. I managed to copy a couple before they disappeared.

Attachment 250497

These 2 BSODs happened with different RAM. I actually thought the RAM was the problem so I switched it out but the BSODs are still happening.

My PSU is EVGA Supernova 650 G3 which I bought 2 weeks ago.

As for the ssgdio64 driver, I'm not sure what uses it. I couldn't find the ATI hardware diagnostic tool, and all of my AMD software is up to date.

I uninstalled Afterburner and RivaTuner. I'll be back with updates after I do the hardware tests.

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

9) 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

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



11) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot


12) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10


13) Post a share link using one drive, drop box, or google drive for: PdcLockWatchdog-20190925-1812.dmp

Code:

Name                              LastWriteTime          Size (MB)
----                              -------------          ---------
PdcLockWatchdog-20190925-1812.dmp 2019-09-25 6:12:28 PM      995.7

14) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

15) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

16) Consider Upgrading Windows (current 1803 or 10.0.17134)

Microsoft Windows [Version 10.0.17134.1040]
(c) 2018 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 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.

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

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.1040

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

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

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.1040

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

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 did not find any integrity violations.

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.
9223 large file records processed.
0 bad file records processed.

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

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

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

267985919 KB total disk space.
110603140 KB in 171251 files.
127012 KB in 34668 indexes.
0 KB in bad sectors.
342531 KB in use by the system.
65536 KB occupied by the log file.
156913236 KB available on disk.

4096 bytes in each allocation unit.
66996479 total allocation units on disk.
39228309 allocation units available on disk.

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

C:\Windows\system32>

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Repeat scannow displayed no corruption.

Code:

Event[1490]:
  Log Name: System
  Source: Ntfs
  Date: 2019-09-25T18:14:58.575
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-GG8A1VQ
  Description: 
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x4000000015835.  The name of the file is "\Users\h_g92\AppData\Local\Microsoft\Windows\Notifications\wpndatabase.db-wal".

I ran the hardware tests suggested earlier and SeaTools, Furmark, and OCCT all came back clean. I couldn't run Memtest86 since I kept getting a black screen every time I tried booting from the USB.

I'll be doing the chkdsk overnight and I'll post the results in the morning.

Here are the screenshots and a link for the PdcLockWatchdog-20190925-1812.dmp as requested.
Dropbox - PdcLockWatchdog-20190925-1812.dmp - Simplify your life

Attachment 250535
Attachment 250536

Please post images of all hardware tests into the thread.

For chkdsk fix and recover switches run on all drives: C:, D:, E:, F:

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 155.7 GB
Total Space: 261.7 GB
File System: NTFS
      Model: Crucial_CT275MX300SSD1

      Drive: D:
 Free Space: 342.1 GB
Total Space: 953.9 GB
File System: NTFS
      Model: ST31000528AS

      Drive: E:
 Free Space: 815.2 GB
Total Space: 1907.7 GB
File System: NTFS
      Model: ST2000DM006-2DM164

      Drive: F:
 Free Space: 235.7 GB
Total Space: 476.9 GB
File System: NTFS
      Model: ST500DM002-1BD142

I stopped Furmark after 5 mins since I was worried about the temperature. I didn't notice any artifacts during this time.

Attachment 250571
Attachment 250572
Attachment 250573

- - - Updated - - -

Here is the chkdsk report

Dropbox - chkdsk.txt - Simplify your life