I see, that's a new one. Just a guess- and assuming, as is normally the case, perhaps it only occurs, e.g. , when some particular driver is loaded by a program.
So a clean boot is no different to booting normally as far as this is concerned in your case.
You will then have to carefully try to correlate this with a particular program or programs.
First off, generally updates only happen once per month, not every 2 days. Unless there is an extremely critical security issue, which by it's nature means you absolutely should update those because they put your computer at risk.
Secondly, as with my first point... monthly updates secure your computer from remote attacks. Personally, i find the security of my computer to be of higher importance than the inconvenience of a reboot. Considering that these are actively exploited vulnerabilities, are you ok with being the victim of a ransomware attacker where your entire hard drive is encrypted and possibly only restored after you pay a ransom? For me, even though I have regular backups, that is NOT an acceptable risk.
I've now have updates break my computer twice. So I have a bit of a distaste that goes beyond inconvenient reboots. I prefer to do updates on my schedule if at all, not have them forced down my gullet.
How would I be able to track everything that happens to a computer? Just of note, I was once watching a Youtube playlist, and I noticed the latency suddenly start up a few videos into the list, so I think it's something that is already running but gets worse and worse over time. That is what led me to think Chrome could be an issue. Here is a report from someone having issues over 2 years ago posting on Reddit, and the last post mentions DPC latency: Chrome Audio Desync, how to fix? : chrome
(As a note, no, closing and restarting Chrome does not fix it.)
I meant a careful and methodical pattern of launching programs and checking with Latencymon, starting with things you suspect.How would I be able to track everything that happens to a computer?
Plenty of (free) ways to make sure of that.not have them forced down my gullet.
That's complicated by the fact that everything I suspect is a driver. So I would have to use AutoRuns to disable everything. Also, after I let this latest update do its thing, I can go ahead and purge the Elgato driver; it only installed because I plugged in the device one day. However, its timestamp is May 23, 2019, so perhaps that is NOT related.
- - - Updated - - -
So doing more researching on the AutoRuns list,. I found my NVIDIA container under Services. Now, I note my first issue happened on December 7, 2019, and was - and remain - very specific about that. However, it was isolated, and didn't happen again...for a while. Sometime in March, I noticed it again, and from here on closing Chrome as I did in December didn't fix it; instead, I had to reboot the computer. This behaviour has not changed now for four months; after a brief few days, I am forced to reboot to fix it, and sometimes even the same day (one was two hours). And, in Services, I just found a NVIDIA container at Windows\System32\driverstore\filerepository\nvddi.inf_amd64_67eaef800e90954a\display.nvcontainer\nvd isplay.container.exe dated February 21 of this year. My suspicions have shifted to that based on the date because I have not done anything else that rings a bell now that I see the Elgato driver was actually done in in May of last year and I didn't have issues for months (other than the autorun module loading that I would have to close). I am looking at other things around the dates of early December and February/March, and I see nothing - NOTHING - else that could have possibly caused this problem. I am now extremely suspect that the nvdisplay.container.exe file is the cause and the date info in AutoRuns is causing me to think that after initially dismissing it on the driver reinstall. So if I go ahead and disable this little container, will I have any other particular issues? I think, for this first test, I have the golden egg so I want to just disable that for the time being.
What does Reliability History show with respect to your problem?
Have you checked---dxdiag---,in particular the audio pages?
Have you considered,or tried the basics---sfc /scannow---three times,then---dism /online /cleanup-image /restorehealth---?
The logs for those two are in---C>Windows>logs>CBS and DISM.The files can be large,so note date and time of use which allows you to quickly scroll to the event.
Forget System Restore,advised by Microsoft to use a third party replacement---recommended one is Macrium Reflect,paid or fre e.
Windows Defender is as good as any third party offering.
Reliability History of what, specifically? Of the container EXE? Also, what are these "basics" you speak of? I did locate both files in the Logs folder, and DSIM notably has activity from July 21, and not prior to that until July 10, July 9, then June 25, it was shut off for the period from the 17th to 22th so nothing after the morning of the 17th until I think the 22nd...and before the 17th, pretty much daily activity. Not sure why activity has turned into a periodic event, but it may be related to the fact that I'm using the laptop a lot more for things currently because it has the better Internet connection.
I already found BitDefender and System Restore do not get along. I don't see System Restore as the way to go for anything currently.
CBS is also open, and the 22nd is mostly marked by Windows update entries. Everything befor eJuly 19 does not exist.
Should I attach these to see if they reveal anything?
Reliability History of "1903 broke my computer",your words not mine.
Does Reliability History give any reports of anything or is it blank?
Did ---dxdiag--- give any reports?
The basics are ---sfc--- and---dism---did you run them or not,if you did then the logs show exactly what transpired If you did not run them,the logs are useless,as you reported.
Thanks for your PM notifying me you had updated this thread- however if everyone had sent me a PM to notify me of changes to a thread, I would have had around 44 messages from tenforums instead of 22 this morning- except actually my PM box would have been full. (P.S. I was asleep last night!)
If you're referring to Nvidia as a possible cause, note that at least 2 issues have now been attributed to an Nvidia driver said to have been rushed out for 2004, including a new one identified overnight. That said, you say you've had this problem from 1909.
Time to do some testing.
I have not run and SFC and DISM, I'm not even sure how to do that because, while you consider it a "basic" thing, it's certainly not something I'm familiar with so it's not so basic to me.
Not that they have been attributed directly, per se, as it's only a guess. But since, as you said, this is the second guess involving a NVIDIA driver (only based on an install date), it's a fairly solid one. It kind of hurts to think that could be the issue because NVIDIA never had any issues before I went onto 1903. And, if I'm right about February, technically also no issues until that even on 1903 (I might be able to blame the Skype install for messing up Chrome in December).
What I need to make sure at this time is that I am disabling the correct things to make sure I properly test it. Do I just want to disable this container, or do I want to run through the entire list of NVIDIA items and disable everythong in AutoRuns?
Quote