Random BSOD

[Robertjr114]

Computer BSOD at random, sometimes while doing tasks or even while just idling. Ran a memtest86 which came up 0 errors. Setting the ram below 6000mhz does not stop BSOD, have gotten BSOD while at speeds of 4800mhz. Any idea what could be causing the BSOD? 

 

BSOD dump files: https://drive.google.com/file/d/1T73kLlwc8HpjjMoWqjBty2f74kpkgnym/view?usp=sharing
MemTest86 results: https://drive.google.com/file/d/1d1-xVqxw0e3xDgir8ViGdM0EQ7gTSeiz/view?usp=sharing

• OS - Windows 8.1, 8, 7, Vista ?
• Windows 11
• x86 (32-bit) or x64 ?
  x64
• What OS was originally installed on the system?
  Windows 11
• Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from a retailer)?
  Preinstalled
• Age of system (hardware)
  3-4 months
• Age of OS installation - have you re-installed the OS?
  3-4 months, not reinstalled
• CPU model
  AMD Ryzen 9 7950X3D
• Video Card model
  Zotac RTX 4090
• MotherBoard - (if NOT a laptop)
  MSI MPG X670E CARBON WIFI (MS-7D70)
• Power Supply - brand & wattage (if laptop, skip this)
  CORSAIR HX1500i Platinum
• System Manufacturer
  Micro-Star International Co., Ltd.
• Exact model number (if OEM or laptop)
  N/A
• Laptop or Desktop?
  Desktop

[kb5zue]

Most BSOD errors will give an error code to indicate where the problem might be.  Did your machine give an error code when the BSOD occured and if so, what was the code given?  That code will provide a lot of insight as to where the problem could be located.

 

Take care and good luck.

 

[Robertjr114]

1 hour ago, kb5zue said:

Most BSOD errors will give an error code to indicate where the problem might be.  Did your machine give an error code when the BSOD occured and if so, what was the code given?  That code will provide a lot of insight as to where the problem could be located.

 

Take care and good luck.

 

Just gives the standard "DPC_WATCHDOG_VIOLATION". BlueScreenView says that the cause is "ntoskrnl.exe" and sometimes "aswVmm.sys" as well.

[Bjoolz]

Uninstall Avast and see if you still crash. You can't reliable debug DPC_Watchdog_Violation crashes with minidumps because Windows has removed all the other DPC queues except the one it thinks had the issue. And it's wrong about which thread the issue occurred in all the time. 

 

You would have to provide 3-4 full dumps if you still crash. Follow this guide to change it to Automatic Memory Dump. Note that with these, they are so large that Windows will just save the latest one so after every crash you have to copy it away to a different directory. Zipping will reduce the size by 50-90%. 

[Robertjr114]

5 hours ago, Bjoolz said:

Uninstall Avast and see if you still crash. You can't reliable debug DPC_Watchdog_Violation crashes with minidumps because Windows has removed all the other DPC queues except the one it thinks had the issue. And it's wrong about which thread the issue occurred in all the time. 

 

You would have to provide 3-4 full dumps if you still crash. Follow this guide to change it to Automatic Memory Dump. Note that with these, they are so large that Windows will just save the latest one so after every crash you have to copy it away to a different directory. Zipping will reduce the size by 50-90%. 

Thanks for the help, uninstalled Avast One using Revo Uninstaller and set my system to create automatic memory dumps. Will mark your answer as solution after the weekend if there is no more BSOD.

[Robertjr114]

Just had another crash, uninstalling Avast hasn't fixed the issue. Will continue to save the DMP files.

[Robertjr114]

Using WinDbg it says the file that caused the crash is "nvrtxvad64v.sys" with the FAILURE_BUCKET_ID being "0x133_OUT_OF_SYNC_PROCESSOR_nvrtxvad64v!unknown_function". From what I can find this is an Nvidia voice driver, not sure if it's from Nvidia Broadcast. Any suggestions? 

 

Edit: Viewing the properties of the driver it's labeled in details as "NVIDIA Broadcast Voice Driver".

Edited March 1, 2024 by Robertjr114
Extra detail

[Robertjr114]

After some testing and research I can confirm the issue was a Nvidia Broadcast driver. Running the computer non stop for about 3 days with Nvidia Broadcast fully closed, not running in background, I had 0 BSOD. Restarted the computer, launched Nvidia Broadcast, BSOD within 30 minutes with the memory dump reporting Nvidia Broadcast driver nvrtxvad64v+179c (nvrtxvad64v.sys) as the cause. This also seems to be an issue people have had over the years.

 

Will link the memory.dmp's as well as some other forum posts to hopefully help anyone else that stumbles upon this issue.

MEMORY.DMP: https://www.dropbox.com/scl/fi/b16qg1fs64230hb0ze6gp/BSOD-Full.zip?rlkey=ycgikdnmurc7t693p6p6l41ta&dl=0

Multiple forum posts with the same issue: https://www.nvidia.com/en-us/geforce/forums/broadcasting/18/496188/blue-screen-in-windows-11-when-using-nvidia-broadc/

https://www.nvidia.com/en-us/geforce/forums/broadcasting/18/503707/solved-dpcwatchdogviolation-while-playing-overwatc/

https://answers.microsoft.com/en-us/windows/forum/all/dpc-watchdog-violation/931e815c-c5dc-47a4-9d66-ae1ac5e5d653

[Bjoolz]

On 3/1/2024 at 3:53 AM, Robertjr114 said:

Using WinDbg it says the file that caused the crash is "nvrtxvad64v.sys" with the FAILURE_BUCKET_ID being "0x133_OUT_OF_SYNC_PROCESSOR_nvrtxvad64v!unknown_function". From what I can find this is an Nvidia voice driver, not sure if it's from Nvidia Broadcast. Any suggestions? 

 

Edit: Viewing the properties of the driver it's labeled in details as "NVIDIA Broadcast Voice Driver".

We don't get notifications if you don't tag/quote someone so I didn't see it until I randomly checked the thread. 

 

And you are quite correct, this looks like Nvidia Broadcast. Windows actually got it right in both dumps this time. DDU should fix you right up if you want to use Broadcast. 

[Robertjr114]

7 hours ago, Bjoolz said:

We don't get notifications if you don't tag/quote someone so I didn't see it until I randomly checked the thread. 

 

And you are quite correct, this looks like Nvidia Broadcast. Windows actually got it right in both dumps this time. DDU should fix you right up if you want to use Broadcast. 

Wasn't aware of that, thanks for informing me. And thanks for the help.