W10 BSOD Errors 1101, 161, 6008

So every day my system is W10 crashing when I'm playing Call of Duty Warzone. This is entirely new and no hardware configuration change has been made which has triggered these crashes.

Context - I have no overclocking on anything, system is water cooled so temperature isn't an issue (even during the game when the crashes happens). It seems to happen only when I'm 1-2 hours into COD gaming.

System specs:
W10 pro V20H2 (OS Build 19042.867)
i7-9700K
Gigabyte Aorus Pro Wifi Z390
16GB Corsair Vengeance RGB Pro
Samsung 970 Evo NVME
MSI Gaming-X Trio 3080

I've re-installed the entire system and have bare-level programs installed. All drivers and bioses are updated.

zebal said:

I really like your system, but your network adapter drivers don't appear to be up to date.

Several services failed to start because some device is "not functioning properly"

For example your WI-FI driver is for Win10 ver.1909 but you're running Windows ver. 2004
Your LAN card isn't up to date too, it's from 2019 which is for Win10 ver.1809

Windows update KB4023057 failed because of some failure that I suspect may be bad network.
https://support.microsoft.com/en-us/...1-7e392450fb3a

These figures may be incorrect, but's that's what I see.

In any case there were no BSOD dump files collected, so it's all speculation.

- - - Updated - - -

btw. I compared your data with this:
Z390 AORUS PRO WIFI (rev. 1.0) Support | Motherboard - GIGABYTE U.S.A.

Thank you for looking this up. I usually don't update motherboard drivers but I'll update the lan one. I don't use the Wifi and have it disabled.

Can you tell me how to collect BSOD dump files so I can post them here?

zebal said:

Following link shows how to enable "Automatic" memory dump:
https://docs.microsoft.com/en-us/win...ectedfrom=MSDN

You should install all latest motherboard drivers that are essential to individual components, here is a must have list for stable system according to previous link:
1. Chipset
2. LAN
3. Audio
4. WLAN
5. Bluetooth (if you have it)

Other drivers are optional or recommended, installment goes like this:
1. close down all programs
2. chipset driver first followed by reboot
3. the rest of drivers followed by reboot

Ofc. avoid installing bloatware and utility software.

Thanks. Btw I have it enabled yet there is no Memory.dmp file in the root folder/drive :/

zebal said:

Please verify your page file settings are "managed by system" instead of manually:
Settings -> System -> About -> Advanced system settings -> Advanced -> Performance -> Advanced -> Virtual memory -> Change -> enable "Automatically manage..." checkbox

If you want to test whether creating dump file works or not download notmyfault:
https://docs.microsoft.com/en-us/sys...ads/notmyfault

You can use it create dummy BSOD, and then see if DMP file was made (do not share this one, it's just a test)

- - - Updated - - -

Btw. you said to be updating all drivers, if you didn't use motherboard site, then where did you get drivers from?

Thanks I'll try this. I guess what I meant by updating drivers - it was my gpu drivers. I've always been of the school that if there's no reason to update, don't touch the Mobo drivers. Obviously, I lost sight of this given the current situation. I updated the mobo drivers as suggested above. Let's see.

I'll check the RAM speed to but I updated the bios and loaded optimized defaults so i think it should sync the ram speed already.

When installing RAM it's best to use modules displayed on the Qualified Vendor List (QVL).
https://download.gigabyte.com/FileLi...ifi_191113.pdf


The currently installed RAM was not seen on the QVL: CMW16GX4M2C3200C16


The prior post was incorrect as the RAM speed was 2133.

How come the computer has a beta BIOS?

Code:

Enable Resizable Base-Address Register (Resizable-BAR) option to enhance GPU performance.
Update CPU microcode SA-00295 to solve potential security vulnerabilities in CPU, please refer to more information: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00295.html
Enhance RAID AIC compatibility
Fix CPU Vcore and power behavior
Workaround beta BIOS to improve Kingston DDR4-2666 stability concern on some specific memory chip suppliers

When a computer displays any instability it's best to use the most up to date non beta BIOS.


When available post tuneup results.

Boo - another crash. I had changed it to 2166 per your request but now flipped it down to 2133. Regarding this RAM, it has been working fine on this setup for 6 months now so it's not new.

Regarding the bios - I had the older version installed when the crashes were happening but upgrading to the new ones that has a beta note for this feature - "Workaround beta BIOS to improve Kingston DDR4-2666 stability concern on some specific memory chip suppliers." Still no difference.

Z390 AORUS PRO WIFI (rev. 1.0) Support | Motherboard - GIGABYTE U.S.A.

At what point do I suspect it could be a PSU issue?

I'm running Tuneup script now and will post that shortly.

- - - Updated - - -

###########################################################
# The following commands will be run in sequence. #
# The first 5 will take quite a while to run, be patient. #
###########################################################

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list
wmic Computersystem where name="DESKTOP-2OV8VKB" get AutomaticManagedPagefile
wmic Computersystem where name="DESKTOP-2OV8VKB" set AutomaticManagedPagefile=True
wmic Computersystem where name="DESKTOP-2OV8VKB" get AutomaticManagedPagefile

bcdedit /enum {badmemory}


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.19041.844

Image Version: 10.0.19042.870

[==========================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.19041.844

Image Version: 10.0.19042.870

[==========================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 ...
355840 file records processed.
File verification completed.
Phase duration (File record verification): 1.92 seconds.
6982 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.17 milliseconds.

Stage 2: Examining file name linkage ...
141 reparse records processed.
526912 index entries processed.
Index verification completed.
Phase duration (Index verification): 6.13 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 304.97 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.23 milliseconds.
141 reparse records processed.
Phase duration (Reparse point and Object ID verification): 2.08 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 33.68 milliseconds.
85537 data files processed.
Phase duration (Data attribute verification): 0.82 milliseconds.
CHKDSK is verifying Usn Journal...
37974368 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 90.71 milliseconds.

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

486012267 KB total disk space.
40251052 KB in 260655 files.
164784 KB in 85538 indexes.
0 KB in bad sectors.
476335 KB in use by the system.
65536 KB occupied by the log file.
445120096 KB available on disk.

4096 bytes in each allocation unit.
121503066 total allocation units on disk.
111280024 allocation units available on disk.
Total duration: 8.49 seconds (8494 ms).

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
TRUE


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

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


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

C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\Windows\system32>wmic pagefile list /format:list


AllocatedBaseSize=2944
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20210325172541.108413-240
Name=C:\pagefile.sys
PeakUsage=1
Status=
TempPageFile=FALSE




C:\Windows\system32>wmic Computersystem where name="DESKTOP-2OV8VKB" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\Windows\system32>wmic Computersystem where name="DESKTOP-2OV8VKB" set AutomaticManagedPagefile=True
Updating property(s) of '\\DESKTOP-2OV8VKB\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP-2OV8VKB"'
Property(s) update successful.

C:\Windows\system32>wmic Computersystem where name="DESKTOP-2OV8VKB" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


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

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

C:\Windows\system32>Echo off
###################################################################################
# How to capture batch file data and post in your thread in the BSOD forum #
# #
# Batch files and instructions for use in BSOD debugging[Part Two-Four] #
# #
# Press [V] to visit the above web page for detailed instructions. #
# Press [C] to close this window. #
###################################################################################


Press any key to continue . . .

- - - Updated - - -

New log too

- - - Updated - - -

Also not sure why I'm still not seeing crash dump even though I followed the direction above as you can see It's set to auto manage: