Getting Various BSOD's Since

Hello People of Windows 10 Forums,

Since Saturday April 6th I have been getting blue screen of deaths including "system Service Exception", "Memory Management", "Critical Structure Corruption" and "Kernel Security Check Failure" etc. These BSOD don't just happen when I turn my PC on but while I'm gaming. While gaming I usually have Discord, Spotify and Twitch open on my left screen and a game on my right screen (games include Fortnite, Hearthstone, Overwatch, R6 Siege). The BSOD's don't pop up right away but after an hour to a couple hours of gaming with the setup above. I have been trying to solve this with the great help of the Tom's Hardware Forums users but to no avail. They actually said I should try my luck here so I hope we can tackle this together. I am going to post my specs, mini dumps, and beta log below. Any help is appreciated, Thanks!

PS- If I'm missing stuff or posted wrong please let me know!

-I've passed memtest68 on both and each Ram individually up to 4 passes.
-HDD Tested with Sentinel, all Perfect

My System:
Intel i7-8700k (not overclocked)
ASUS PRIME Z390-A
Nvidia GeForce GTX 1080 (ROG Strix A8G)
Corsair Vengence 16GB (2x8GB) DDR4 3000MHz C15
1 SunDisk SSD Plus 480GB (Windows Installed on this)
1 Samsung 860 evo 1TB SSD
1 WD 1TB HDD

Mini Dumps-
050619-9156-01.dmp - Google Drive
050519-9218-01.dmp - Google Drive
050419-8906-01.dmp - Google Drive

Logs-
DESKTOP-309EVP1-(2019-05-06_20-53-20).zip - Google Drive

- - - Updated - - -

Just got another BSOD while turning my PC on.
050719-8593-01.dmp - Google Drive

I guess it varies when they appear but it usually happens after an hour+ of gaming.

There are no obvious clues from the crash dumps so we have to tackle this by making sure everything is set up correctly and then starting with a clean boot to begin with the minimum configuration, eliminating a lot of the non-Microsoft software. By a process of gradually adding things back you can hopefully find which item is causing the BSOD. At this stage I'm assuming it is a driver related issue rather than hardware but if the clean boot gives a BSOD we can revisit the hardware possibility.

Step one - make sure the BIOS settings are all at default. Memory speeds can run faster than you have them set but do not go faster than 2666MHz.

Step two - start with a clean boot - see Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

Some of the ASUS and Corsair bloatware has been known to trigger BSODs in the past. Even with the graphics drivers it is sometimes best to only install the driver and not the full set of software tools.

Thank you for the information. When I get home from work tonight I will try these two steps. Is it ok to play games to try to bait the BSOD to pop up? or do I just have to have the PC sit there after I restart while testing with the clean boot approach?

- - - Updated - - -

If I get BSOD's should i still post the mini dumps or just follow the clean boot instructions to try to pin point the driver(s) that is/are acting up?

- - - Updated - - -

Just in case anybody wants to know what I have tried so far with the help of the Tom's Hardware forums so we don't repeat certain techniques that were already attempted.

Question - Getting Various BSOD's | Tom's Hardware Forum

Yes after the clean boot use the PC as you normally would, making a note of any programs that you load.

Post a new set of logs after every BSOD.

I have my PC start up with a clean boot and I have half of my services running. I have had my PC like this since Tuesday and I played games for about an hour on Thursday, Friday and a little today on Saturday. I did get my first BSOD since using the clean start up and it happened while using chrome after playing some Rainbow six Siege. Log file is below:

DESKTOP-309EVP1-(2019-05-11_21-13-50).zip - Google Drive

Hello,

I followed the steps from your post zbook. CMD promtpt results below:
Microsoft Windows [Version 10.0.17763.475]
(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 did not find any integrity violations.

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.475

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

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

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

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

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

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

468219903 KB total disk space.
52347076 KB in 183153 files.
122364 KB in 49287 indexes.
0 KB in bad sectors.
362027 KB in use by the system.
65536 KB occupied by the log file.
415388436 KB available on disk.

4096 bytes in each allocation unit.
117054975 total allocation units on disk.
103847109 allocation units available on disk.

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

C:\Windows\system32>

Start up & Recovery-
https://drive.google.com/file/d/13aj...ew?usp=sharing

Virtual Memory-
https://drive.google.com/file/d/1hSW...ew?usp=sharing

Not sure what is meant by "9) Download and Install: Everything"

Not sure what I was doing by step 9 but see if this is right?
https://drive.google.com/file/d/16c_...ew?usp=sharing

I turned off the fast startup option.

For startup and recovery system failure:
a) for write debugging information change small memory dump to automatic memory dump
b) the directory should change from mini to memory dump
c) reboot to maintain settings

For Virtual memory:
a) Highlight C: and make sure the dot is in system managed size
b) reboot to maintain settings

Everything: voidtools

Launch the application > search for: ResourceTimeout-20190430-1839.dmp > zip > post a share link into the thread

Code:

Event[10492]:
  Log Name: System
  Source: nvlddmkm
  Date: 2019-05-12T13:32:05.958
  Event ID: 14
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-309EVP1
  Description: 
N/A

Event[10493]:
  Log Name: System
  Source: nvlddmkm
  Date: 2019-05-12T13:32:06.036
  Event ID: 14
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-309EVP1
  Description: 
N/A

Dommer said:

I have my PC start up with a clean boot and I have half of my services running. I have had my PC like this since Tuesday and I played games for about an hour on Thursday, Friday and a little today on Saturday. I did get my first BSOD since using the clean start up and it happened while using chrome after playing some Rainbow six Siege. Log file is below:

DESKTOP-309EVP1-(2019-05-11_21-13-50).zip - Google Drive

The crash dumps that occurred during the clean boot tend to suggest that there is a memory hardware problem. This is most likely the RAM but could be related to hard disk/motherboard. Let's begin by focussing on the RAM. Unfortunately the memory diagnostic testing for DDR4 is not as reliable as we would like and so my recommendation is to test the system by using it as normal with just one of the RAM modules inserted at a time. If the system BSODs with one RAM module and not the other that is the best way of determining that one of them is faulty.

@zbrook - I changed my start up and virtual memory to the options you listed above and i hope i did the ResourceTimeout correct.
ResourceTimeout-20190430-1839.rar - Google Drive

ResourceTimeout-20190430-1839.dmp - Google Drive


@philc43 - I will try to do normal PC activities with one RAM module later when i get home from work.