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.
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
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
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).
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)
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
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.
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
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
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.
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.
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.
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.
drive.google.com
