Michael wrote: > On Saturday, 8 November 2025 08:27:51 Greenwich Mean Time Dale wrote: >> >> No power problems that I know of. My power supply is plenty big >> enough. Likely to big. I think it is a 750 watt or something. >> According to the UPS, it pulls about 200 watts, which included two >> monitors, modem, router, little audio amp and such which isn't powering >> the computer itself. >> >> I checked the logs just now, while my onion rings cook. No problems at >> all. Just the normal stuff. Best I can figure, my ISP was having some >> issue maybe??? Odd that it started when I had to twist my rig around >> and take the sides off tho. That is what was so confusing about this >> error. It didn't make sense. I didn't even touch the mobo itself. >> Turned out I had enough power and a couple SATA cables already >> available. I guess from when I switched to larger drives. >> >> I have to say tho, this much larger case is coming in handy. ;-) I >> still have a couple drive holes in the bottom and a few more in the >> stack area. I can add more drives and store more data if needed. :-D >> >> Dale >> >> :-) :-) > Does 'ip -s -s link' reveal transmission errors? Either way, as you say NIC > queueing errors should not make a difference in playing a video locally. Is > the stuttering recurring if you play the same video again?
Well, since yesterday, there has been no errors. I have no idea how a network error can cause the video to stutter. Even yesterday when it was doing this weird thing, I could hit the left arrow to go back 15 seconds or so, when the video would get to where it stuttered before, it would play fine that time. That's when I knew it was the network error that was causing the video to stutter. The only thing I can figure, it mentions the CPU in the error. Maybe the CPU got busy or something due to the network error and that made the video stutter, it to stop seeing what I type etc etc. Maybe something to do with the time out part. Out of something that makes little sense, that's the best sense of it I can come up with. Either way, not a single problem since yesterday. I ran the above command. No errors. Last night tho, I did turn off my modem and router, shutdown the network and reseated all my network cables. I also put a little silicone dielectric on them to prevent corrosion over time. Just to be sure. Since this is such a weird problem. I think me posting about the problem to get ideas is what fixed it. After all, it stopped shortly after I posted. ROFL Dale :-) :-)
