Windows 10
I am posting my V2 logs here. Any help is greatly appreciated.
Thanks
- - - Updated - - -
Cannot attach files.
- - - Updated - - -
CS-COMP-SAVI-02-(2023-10-20_10-38-13).zip - Google Drive
There were multiple blank files.
Please make sure that third party cleaning software and Windows cleaning is not performed during the troubleshooting.
Windows management files were reported moved or missing.
Run:
https://www.tenforums.com/attachment...p_plus_log.bat
Batch files for use in BSOD debugging
post a link
Run V2 while in safe mode > post a new link
Uninstall:
NewTek_AudioPortClass_Multi
Download NewTek NDI Audio Sound, Video, and Game Controller Drivers for Windows 11, 10, 8.1, 8, or 7 - 64-bit and 32-bit - Treexy
Viewed some of the data quickly.
Will need to view much later today.
This device is deployed remotely so a little difficult but I will see what I can do. Thanks.
- - - Updated - - -
Here's a new run at it. I may have stopped the process before it was done last time:
CS-COMP-SAVI-02-(2023-10-20_14-35-02).zip - Google Drive
I did remove the NewTek Audio. Had suspicions about that from another device. We use NDI a lot so that would be interesting.
Thanks
When available post a tuneup plus result share link.
Manually collect msinfo32 > save as NFO > post a separate share link
The latest V2 appeared to have been run in normal boot.
The same files were missing.
If possible run V2 in safe mode (shift + restart) > post a new link.
An older dump file (Aug 28) had misbehaving Nvidia GPU drivers nvlddmkm.
Monitor the computer for several days.
For new BSOD post a new V2 share link.
If there are no new BSOD for three days then that will complete the troubleshooting.
Since removing NewTek Audio, it's been up for 18 hours. It hasn't been up that long for over 60 days. Not saying it's fixed but a good sign.
See if you're able to monitor the computer using:
Reliability Monitor is the Best Windows Troubleshooting Tool You Aren't Using
View Reliability History in Windows 11 Tutorial | Windows 11 Forum
I didn't initially download your latest V2 log because it was reported to be corrupted. After reading your latest post howver, I've downloaded what there is and the dumps (or most of them at least) agree with you that New Tek Audio was the problem. The dumps show that the driver NewTek_AudioPortClass_Multi.sys was at fault in some of the dumps...
See how it goes now, post a new (complete) V2 log if it BSODs again.Code:FAILURE_BUCKET_ID: AV_CODE_AV_PAGED_IP_NewTek_AudioPortClass_Multi!unknown_function
Quote