Solved Getting random BSOD pretty much daily

ughel2048 · Jan 17, 2024

Hello, I had this issue for a while now. I do not know how to use WinDbg and BlueScreenView did not help me (since I am inexperienced).
The link to the files are below, I am asking for your help.

DESKTOP-ADMIN-(2024-01-17_19-11-11).zip

drive.google.com

Thank you in advance

Best Regards

ughel2048 · Jan 17, 2024

Uploaded the files to Google Drive

x BlueRobot · Jan 17, 2024

Please follow these posting instructions: BSOD - Posting Instructions

ughel2048 · Jan 17, 2024

x BlueRobot said:
Please follow these posting instructions: BSOD - Posting Instructions

Yep sorry, I have done that now.

zbook · Jan 17, 2024

Please see posting instructions to run the V2 log collector.

Sometimes it may be necessary to uninstall third party antivirus software and use Microsoft defender:

[KB146] Uninstallers (removal tools) for common Windows antivirus software

support.eset.com

zbook · Jan 17, 2024

Please perform the following steps:

1) Modify the default language to English so that log files can be scanned and read:

Add, Remove, and Change Display Language in Windows 10

How to Add or Remove Language Packs and Change Display Language in Windows 10

www.tenforums.com

Change Display Language in Windows 10

How to Change Display Language in Windows 10

www.tenforums.com

2) Run tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

3) Uninstall and reinstall the Nvidia GPU drivers using DDU / Nvidia

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU) download latest version 18.0.7.6

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

Download the latest official NVIDIA drivers

www.nvidia.com

4) Uninstall and reinstall:

nvrtxvad_waveextensible NVIDIA Broadcast c:\windows\system32\drivers\nvrtxvad64v.sys

Code:

Name    NVIDIA Broadcast
Hersteller    NVIDIA
Status    OK
PNP-Gerätekennung    ROOT\UNNAMED_DEVICE\0003
Treiber    C:\WINDOWS\SYSTEM32\DRIVERS\NVRTXVAD64V.SYS (1.0.1.9, 57,51 KB (58.888 Bytes), 17.01.2023 18:46)

5) Uninstall the software / drivers related to:

a) usbpcap USBPcap Capture Service c:\windows\system32\drivers\usbpcap.sys
USBPcap is an open-source USB sniffer for Windows

b)nldrv nldrv c:\windows\system32\drivers\nldrv.sys

NetLimiter - Support

NetLimiter, network monitoring and control tool

www.netlimiter.com

6) The BIOS-Version/-Datum American Megatrends Inc. 4007, 08.12.2020

Upgrade the BIOS: 4007 > 5302

ROG STRIX B450-F GAMING | Motherboards | ROG Global

ASUS ROG Strix B450-F Gaming Motherboard - Next-level performance: 2nd gen. AMD processors, 5-Way Optimization, Fan Xpert 4, Aura Sync. POWER.

rog.asus.com

7) Open administrative command prompt and copy and paste: chkdsk /b /v

Run these chkdsk switches on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E: etc.

Make sure that the chkdsk switches run on the Windows drive overnight while sleeping.

C:\WINDOWS\system32>chkdsk /b /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 as needed.

6) Run:

https://www.tenforums.com/attachments/bsod-crashes-debugging/317041d1612147952-batch-files-use-bsod-debugging-chkdskfromevent.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 531.6 GB
Total Space: 952.3 GB
File System: NTFS
      Model: WDC WDS100T2B0C-00PXH0

      Drive: D:
 Free Space: 0.2 GB
Total Space: 0.2 GB
File System: NTFS
      Model: WDC WDS100T2B0C-00PXH0

      Drive: E:
 Free Space: 98.3 GB
Total Space: 1907.6 GB
File System: NTFS
      Model: Samsung SSD 870 QVO 2TB

      Drive: J:
 Free Space: 884.1 GB
Total Space: 953.9 GB
File System: NTFS
      Model: Samsung SSD 980 PRO 1TB

Code:

Event[20043]
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2024-01-17T18:37:22.8210000Z
  Event ID: 98
  Task: N/A
  Level: Fehler
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT-AUTORIT─T\SYSTEM
  Computer: DESKTOP-Admin
  Description:
Volume "C:" (\Device\HarddiskVolume2) muss offline geschaltet werden, um eine vollstõndige chkdsk-Pr³fung auszuf³hren. F³hren Sie "CHKDSK /F" lokal ³ber die Befehlszeile oder "REPAIR-VOLUME <Laufwerk:>" lokal oder remote ³ber PowerShell aus.

ughel2048 · Jan 17, 2024

I attached the log file for the Tuneup.bat thing, will do all other steps and tell you when I am done.

ughel2048 · Jan 17, 2024

I have done all the steps; you can find the log file from the last step in the attachment.

zbook · Jan 17, 2024

Tuneup plus chkdsk /scan reported similar chkdsk problems

Code:

Windows has found problems that must be fixed offline.

Please run *chkdsk /f* to fix the issues.

Perform step #7 overnight on the Windows drive.

The other drives can run anytime.

Please post a new V2 share link when English is the default language.

ughel2048 · Jan 18, 2024

zbook said:
Tuneup plus chkdsk /scan reported similar chkdsk problems

Code:

Windows has found problems that must be fixed offline. Please run *chkdsk /f* to fix the issues.

Perform step #7 overnight on the Windows drive.

The other drives can run anytime.

Please post a new V2 share link when English is the default language.

Did Step 7 again, it scanned all the drives while the system was on, that took alot of time. When I entered the command to scan the C drive it told me it is going to do that at the next restart so I did that, when I restarted it said it is scanning the drive for like 10 seconds and then booted normally. DESKTOP-ADMIN-(2024-01-18_13-03-11).zip

ughel2048 · Jan 18, 2024

ughel2048 said:
Did Step 7 again, it scanned all the drives while the system was on, that took alot of time. When I entered the command to scan the C drive it told me it is going to do that at the next restart so I did that, when I restarted it said it is scanning the drive for like 10 seconds and then booted normally. DESKTOP-ADMIN-(2024-01-18_13-03-11).zip

I also just had 2 BSOD in around 2 hours

x BlueRobot · Jan 18, 2024

Please defer from quoting the entire post, it makes it far more difficult to read the thread.

ughel2048 said:
I also just had 2 BSOD in around 2 hours

Could you please upload the latest dump files?

ughel2048 said:
when I restarted it said it is scanning the drive for like 10 seconds and then booted normally.

It's very likely that a file system filter driver is locking the disk which is preventing CHKDSK from running over a reboot. However, I wouldn't worry about CHKDSK for now since it won't be the reason for your crashes.

Please remove NVIDIA Broadcast completely, reboot the system and then use the computer as you normally would. All your crashes have been Stop 0x133 with identical call stacks so the issue is more than likely related to one particular driver.

ughel2048 · Jan 18, 2024

Here is the dump file: 011824-17937-01.dmp

I removed Nvidia Broadcast, I will tell you when it happens again.

x BlueRobot · Jan 18, 2024

Thanks, looks another Stop 0x133 which I suspect was also caused by NVIDIA Broadcast. It might be worthwhile doing a quick FRST registry search to make sure that no remnants have been left behind too:

FRST Registry Search
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Copy and paste NVRTXVAD64V.SYS; NVRTXVAD64V into the Search box and click the Search Registry button.
4. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.

ughel2048 · Jan 18, 2024

Farbar Recovery Scan Tool (x64) Version: 16.01.2024
Ran by Admin (18-01-2024 21:52:33)
Running from C:\Users\Admin\Downloads
Boot Mode: Normal

================== Search Registry: "NVRTXVAD64V.SYS; NVRTXVAD64V" ===========

===================== Search result for "NVRTXVAD64V.SYS" ==========

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvrtxvad_WaveExtensible]
"ImagePath"="\SystemRoot\system32\drivers\nvrtxvad64v.sys"

===================== Search result for " NVRTXVAD64V" ==========

====== End of Search ======

Didn't find the file so I just wrote it here instead, seems like there are some traces left.

x BlueRobot · Jan 18, 2024

Could you please open an elevated command prompt and then enter the following commands:

Code:

sc stop nvrtxvad_WaveExtensible
sc config nvrtxvad_WaveExtensible start= disabled

You may need to reboot the machine for the changes to take effect. I would double check that it is disabled after a reboot by using:

Code:

sc query nvrtxvad_WaveExtensible

ughel2048 · Jan 18, 2024

Executed the first 2 commands and rebooted, after running the third command it outputs this:

C:\Windows\System32>sc query nvrtxvad_WaveExtensible
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.

x BlueRobot · Jan 19, 2024

It should still exist as a service, what is returned from the following:

Rich (BB code):

reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvrtxvad_WaveExtensible /v Start

ughel2048 · Jan 19, 2024

C:\Windows\System32>reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvrtxvad_WaveExtensible /v Start
ERROR: The system was unable to find the specified registry key or value.

x BlueRobot · Jan 19, 2024

I'm guessing you didn't reboot after running DDU earlier in the thread? That's the only reason I can think of as to why that key would be deleted. In either case, it doesn't particularly matter because we wanted to remove that driver anyway.