Increasingly frequent BSODs, stop codes change each time

monkeymonk · 16 Apr 2023

I followed your instructions regarding the pagefile. It currently seems to be working (it set itself back to 10gb), but I'm not 100% sure. Is there any way I can check this? I'm curious as to why @zbook said my pagefile was on D: when it didn't appear to be on my end. I am also still getting the same issue when I tick "Automatically restart" in the options with "Automatic memory dump". Can I assume it's working fine despite the error, since it's still writing minidump files?

I downloaded Samsung Magician and after a bit of trouble initially was able to update the NVMe driver/firmware and this is now reflected as up to date in Magician. The 960 EVO doesn't support Diagnostic Scan however, if that is the scan you were asking me to do. The firmware update doesn't seem to have resolved the VSS errors - I am still unable to create a system restore point. Is this step 100% necessary to proceed with the other troubleshooting steps?

I also did install the Intel Driver & Support Assistant a few days ago, it said everything was up to date:

Increasingly frequent BSODs, stop codes change each time-intel1.png

Increasingly frequent BSODs, stop codes change each time-intel-2.png

Is there anything else I should do in regards to the NETIO.sys and tcpip.sys issues?

Regarding the VSS and system restore issues, so far I have tried:
- Googling the error code 0x80042318 but not much comes back related to system restore nor are they specific to Windows 10 (lots of results for something called macrium reflect? no idea)
- Setting Volume Shadow Copy Service and COM+ Event System in services.msc from Manual > Automatic, and ensuring it's running
- Turning System Restore/Protection off and back on
- sfc /scannow again
- Increasing System Restore limit to 10% (23gb)
If it's relevant at all the VSS Event IDs in Event Viewer are mostly: 8193, 13, 12342, 12346, 12347.

Can I proceed with zbook's other steps without a system restore point or is that a bad idea? ie. Memtest, the Windows 10 ISO thing etc.

And the latest BSOD attached - I had just restarted a few mins prior, after updating Realtek audio drivers, was looking at this thread in Chrome, Steam was not open this time. This time it was nvlddmkm.sys again (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED). The GPU drivers are up to date though :/

- - - Updated - - -

And another one - this time I had just opened Apex ~30 seconds or so, screen went black, I waited a few mins then restarted with power button. Got back in to a new minidump file, and a few new events in Event Viewer including BugCheck.

- - - Updated - - -

Andd another one lol - this time just browsing this thread in Chrome.

- - - Updated - - -

And another one - this time I was testing Overwatch to see if the same thing would happen as Apex. I tried about 4-5 times, each time a few mins after opening the game would crash and give an error message to send to Blizzard (would happen around 30-60 seconds after joining a match), however, the PC did not BSOD the first few times. On the last time, I had HWInfo64 open as well (not sure if relevant, but it wasn't open the first few tries), Chrome and B.Net. Joined a game, 30 secs later everything locked up, then black screen (couldn't see the blue screen, but I assume it happened), audio looping etc. Waited a bit as before, and restarted to new minidump (attached)... Is my GPU dying? Ahhh this is driving me nuts...

- - - Updated - - -

(8703) - browsing in chrome, nothing else

zbook · 16 Apr 2023

The V2 log collector will collect most of the needed log files.
When it ran it collected data.
The data from the opening post displayed: Page File D:\pagefile.sys

Tuneup plus displayed that the page file is currently on C:

1) Please make sure that these are selected for startup and recovery system failure and virtual memory:
a) System managed size (dot in circle)
b) Automatically manage paging file size for all drives (box checked)
c) Paging file on the Windows drive (C:)
d) Automatic memory dump
e) Automatically restart (box unchecked)

2) Reboot the computer after the above modifications

3) After the reboot please run these in sequence:
a) Tune up plus
b) V2 log collector
Post share links for each using one drive, drop box, or google drive.

4) Please do not post dump file share links into this thread.
Instead please run the V2 log collector to have it collect all log files at one time.

5) Create a folder on the desktop.
Label the folder Windows 10 MCT 04/16/2023 or Media Creation Tool.
Download the MCT to the folder on the desktop.

6) Later in the thread plan to perform an in place upgrade repair while in clean boot:

Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

Repair Install Windows 10 with an In-place Upgrade

7) Later in the thread plan to upgrade the BIOS to the most up to date non-beta BIOS:

GA-AB350N-Gaming WIFI (rev. 1.0) Support | Motherboard - GIGABYTE Global

Code:

System Model	AB350N-Gaming WIFI
System Type	x64-based PC
System SKU	Default string
Processor	AMD Ryzen 7 3700X 8-Core Processor, 3593 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date	American Megatrends Inc. F50a, 27/11/2019
SMBIOS Version	3.2
Embedded Controller Version	255.255
BIOS Mode	UEFI
BaseBoard Manufacturer	Gigabyte Technology Co., Ltd.
BaseBoard Product	AB350N-Gaming WIFI-CF
BaseBoard Version	x.x
Platform Role	Desktop
Secure Boot State	Off
PCR7 Configuration	Binding Not Possible
Windows Directory	C:\WINDOWS
System Directory	C:\WINDOWS\system32
Boot Device	\Device\HarddiskVolume2
Locale	United Kingdom
Hardware Abstraction Layer	Version = "10.0.19041.2728"
Username	DESKTOP-LFS2OGV\Gerald
Time Zone	AUS Eastern Standard Time
Installed Physical Memory (RAM)	16.0 GB
Total Physical Memory	15.9 GB
Available Physical Memory	8.39 GB
Total Virtual Memory	26.9 GB
Available Virtual Memory	16.4 GB
Page File Space	11.0 GB
Page File	D:\pagefile.sys
Kernel DMA Protection	Off
Virtualisation-based security	Not enabled
Device Encryption Support	Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not Modern Standby, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable

Code:

Restorehealth  Error: 0x800f081f

Code:

VSS  Error:  0x80042318

ubuysa · 17 Apr 2023

You can check the size of the pagefile by going to the dialog where you set the pagefile size. At the bottom are the max, min, and current pagefile sizes. If it's set to 'system managed' you really don't need to concern yourself with these values however, the Windows memory manager is very good at what it does.

I'm still not 100% happy that the 960 EVO can be eliminated completely. Does Magician give you the SMART values from the drive? If it does please post a screenshot. I've seen M.2 drives cause niggly issues because they weren't seated properly in the past, so it's worth removing the 960 EVO and then re-insert it fully.

A system restore point isn't necessary, but you do want to be sure any user data on that drive is regularly back up. What error do you get when you try to create a restore point? Can you post a screenshot? Please also run the 'get-psdrive -psprovider filesystem' (without the quotes) command again and post a screenshot of that.

Regarding the wireless card there is little more you can do if the driver is up to date. That we've seen several network related dumps might just be coincidence, or it might indicate a problem with the wireless card itself. The only way to check that would be to cable attach your PC to your router and see whether you still get those networking BSODs.

I think we need to fully eliminate RAM as a potential cause of these BSODs, and the only reliable way to do that is to run one RAM card at a time. Can you please remove one RAM card and run just on 8GB for a couple of days (or until you get another BSOD). Then swap cards and run just on the other 8GB RAM card for a couple of days (or until you get another BSOD).

If it BSODs on one card but not on the other then you've found the problem.
If it BSODs on both cards then it's not a RAM problem (and that's useful information).
If it doesn't BSOD at all on either card alone then run on both cards again and see how it goes.