I can’t afford to empty my pc due to works i have to do with school with unity. I’ll try to test that program. When i can, i’ll try to do a clean start of my pc
So i ran the test and everything seems fine. I noticed 2 things:
- the test doesn’t diagnose GPU
- sometimes i get some random ALT+TAB commands while playing, like the computer wants to switch to another window randomly.
Any program to test the GPU? Just for diagnosis though just like this BurnIn Test.
Edit: nevermind, just found out the BurnIn Test has also a test for GPU and running it right now.
Edit: Edit: just finished the test and no errors appeared. I guess ultimately it’s windows’s fault.
Funmark is what you seek
Did the test. It was Furmark, not Funmark actually. Can you guys spot if there is anything wrong in the stats?
Edit: did the 1080 preset since my monitor is maxed at 1920 x 1080 and i would never go above that resolution until i get a new monitor eventually
At first glance, no. It looks fine.
I’m honestly stumped. I might suggest you take all this to the PCMR subreddit. They’re way more knowledgeable and might have a better idea.
hey, you know what… a long time ago i had very stupid issues like this and it turns out MS loaded a driver that messed with my monitors refresh rate. you should investigate its settings.
The above pics is the area you want to poke around in. I am looking for that one area, (may of been color depth) that i believe caused the issue, but it was one stupid setting that MS moved and not myself and I remember it was directly related to that. (this happened to me in evolve, and the convo is somewhere here on the forums with the fix… but were talking long long ago)
wait before I go any further… since you can NOT do the system reset, have you uninstalled programs going backwards from your install order yet?
OH YEAH, ANY CREATOR WORTH THEIR SALT HAS A SYSTEM BACKUP AND CAN RESET ON A WHIM! BACK UP YOUR SYSTEM…
I mean, i could do that, if i had time to do that though xd
Also, why backup when i can use git for my projects? git is gud lul
just always keep a copy offline of work…
Backups saved Toy Story.
Always backup… Always.
@Kathryn_James has nuked this problem quite heavily, but I’ll add a few things.
if its consistent across games, its not related to the applications. Remaining options are os, drivers, configuration, or hardware.
700w is probably way way wayyyy overkill.
if it’s effecting network traffic AND offline traffic, its not wireless or wired performance.
you’re reporting a sporadic issue, a street test with performance over time graphs is ideal.
look into disabling virtual memory options with windows 10
disable windows 10 telemetry information.
install software such as fiddler, or monitor traffic with a netstat command. (Fiddler will be easier to read). Play an ONLINE game. Record your fps over time with a third party app (tonnes out there).
Look for a decrease in performance that lines up with a network call.
The linked source (especially if its Microsoft), will provide information. Its most likely a backgrounf process.
HDD will decrease in read effectiveness the longer they are used, and the more data that is stored on them.
You should probably back it up if we’re expecting hdd issues.
your GPU could have issues, check with the manufactor for driver/support information. GPU issues can get REAL weird. Just trust me on that one.
To verify, borrow a friends gpu and test. If the performance is consistent (on the other gpu.) Then It’s gpu related.
I could continue, but most of the steps I would suggest have already been done. If none of this works, it’s time to let a professional look at it. Sorry. (Most work places, if you use your personal pc for work stuff, the I.t. guys are usually nice )
There are some things that you probably dont have the tools to perform (I dont have the $600 tools either… Too expensive)…
The main goal is to isolate, and narrow down the cause. Look at it like solving a water pipe that’s blocked.
Nice rounding out… I still think the HDD is the culprit myself.
Okay, i’ll try one more desperate time and see what happens after following all your points. I have to point out however that i doubt it is gpu hardware related. As said, a quick reboot, which takes 10 seconds (god i love ssd), fixes the thing for 4/5 hours. So i highly doubt it is related to hardware as it would have persisted after a brief reboot. A little news though: it seems that there is a random program that activates for literally 3 frames and then disappears in the process list in task manager, causing, not always, an hiccup, but always causes to switch window focus to another program in background at random.
A hardware problem can be temporarily resolved by a reboot. Best of luck.
Oh come on at the moment i tried disabling telemetry and virtual memory. Nothing yet. Gonna try to monitor an online game.
Proto Indirizzo locale Indirizzo esterno Stato TCP 127.0.0.1:10501 DESKTOP-NIJS6OE:50598 ESTABLISHED TCP 127.0.0.1:10502 DESKTOP-NIJS6OE:50599 ESTABLISHED TCP 127.0.0.1:49836 DESKTOP-NIJS6OE:65001 ESTABLISHED TCP 127.0.0.1:50590 DESKTOP-NIJS6OE:50600 ESTABLISHED TCP 127.0.0.1:50590 DESKTOP-NIJS6OE:50606 ESTABLISHED TCP 127.0.0.1:50590 DESKTOP-NIJS6OE:50608 TIME_WAIT TCP 127.0.0.1:50590 DESKTOP-NIJS6OE:50609 ESTABLISHED TCP 127.0.0.1:50598 DESKTOP-NIJS6OE:10501 ESTABLISHED TCP 127.0.0.1:50599 DESKTOP-NIJS6OE:10502 ESTABLISHED TCP 127.0.0.1:50600 DESKTOP-NIJS6OE:50590 ESTABLISHED TCP 127.0.0.1:50603 DESKTOP-NIJS6OE:50590 TIME_WAIT TCP 127.0.0.1:50604 DESKTOP-NIJS6OE:50590 TIME_WAIT TCP 127.0.0.1:50606 DESKTOP-NIJS6OE:50590 ESTABLISHED TCP 127.0.0.1:50607 DESKTOP-NIJS6OE:50590 TIME_WAIT TCP 127.0.0.1:50609 DESKTOP-NIJS6OE:50590 ESTABLISHED TCP 127.0.0.1:65001 DESKTOP-NIJS6OE:49836 ESTABLISHED TCP 192.168.1.103:49714 188.8.131.52:https ESTABLISHED TCP 192.168.1.103:50589 184.108.40.206:https ESTABLISHED TCP 192.168.1.103:50592 220.127.116.11:https TIME_WAIT TCP 192.168.1.103:50610 a88-221-145-73:https ESTABLISHED TCP 192.168.1.103:50611 a88-221-145-73:https ESTABLISHED TCP 192.168.1.103:50613 a2-17-126-176:https ESTABLISHED TCP 192.168.1.103:50614 a88-221-145-73:https ESTABLISHED TCP 192.168.1.103:50615 a88-221-145-73:https ESTABLISHED TCP 192.168.1.103:50616 a88-221-145-73:https ESTABLISHED TCP 192.168.1.103:50618 mil04s26-in-f14:https ESTABLISHED TCP 192.168.1.103:50619 a88-221-145-73:https ESTABLISHED TCP 192.168.1.103:50620 18.104.22.168:https ESTABLISHED TCP 192.168.1.103:50623 mil04s03-in-f14:https ESTABLISHED TCP 192.168.1.103:50624 22.214.171.124:https TIME_WAIT TCP 192.168.1.103:50625 126.96.36.199:https ESTABLISHED TCP 192.168.1.103:50627 188.8.131.52:https TIME_WAIT TCP 192.168.1.103:50629 184.108.40.206:2099 ESTABLISHED TCP 192.168.1.103:50630 220.127.116.11:5223 ESTABLISHED TCP 192.168.1.103:50633 18.104.22.168:https ESTABLISHED TCP 192.168.1.103:50634 22.214.171.124:https TIME_WAIT TCP 192.168.1.103:50637 126.96.36.199:https TIME_WAIT TCP 192.168.1.103:50638 188.8.131.52:https ESTABLISHED TCP 192.168.1.103:50639 184.108.40.206:http TIME_WAIT TCP 192.168.1.103:50641 ec2-54-213-158-136:https CLOSE_WAIT TCP 192.168.1.103:50642 220.127.116.11:https ESTABLISHED TCP 192.168.1.103:50644 a2-20-251-18:https ESTABLISHED TCP 192.168.1.103:50645 a2-20-251-33:https ESTABLISHED TCP 192.168.1.103:50652 wk-in-f104:https ESTABLISHED TCP 192.168.1.103:50653 mil04s26-in-f106:https ESTABLISHED TCP 192.168.1.103:50654 mil04s24-in-f35:https ESTABLISHED TCP 192.168.1.103:50655 wo-in-f188:5228 ESTABLISHED TCP 192.168.1.103:50656 mil04s22-in-f77:https ESTABLISHED TCP 192.168.1.103:50657 mil04s26-in-f14:https ESTABLISHED TCP 192.168.1.103:50658 mil04s04-in-f33:https ESTABLISHED TCP 192.168.1.103:50659 mil04s22-in-f3:https ESTABLISHED TCP 192.168.1.103:50660 mil04s27-in-f130:https ESTABLISHED TCP 192.168.1.103:50661 mil04s24-in-f14:https ESTABLISHED TCP 192.168.1.103:50662 mil04s26-in-f14:https ESTABLISHED TCP 192.168.1.103:50663 mil04s04-in-f14:https ESTABLISHED TCP 192.168.1.103:50664 mil04s27-in-f130:https ESTABLISHED TCP 192.168.1.103:50666 mil04s27-in-f142:https ESTABLISHED TCP 192.168.1.103:50670 18.104.22.168:https ESTABLISHED TCP 192.168.1.103:50672 mil04s28-in-f14:https ESTABLISHED TCP 192.168.1.103:50673 22.214.171.124:https ESTABLISHED TCP 192.168.1.103:50674 mil04s03-in-f10:https ESTABLISHED TCP 192.168.1.103:50675 mil04s22-in-f3:https ESTABLISHED TCP 192.168.1.103:50676 mil04s22-in-f3:https ESTABLISHED TCP 192.168.1.103:50680 a2-23-14-238:https ESTABLISHED TCP 192.168.1.103:50681 a2-20-235-194:http ESTABLISHED TCP 192.168.1.103:50684 126.96.36.199:https ESTABLISHED TCP 192.168.1.103:50685 188.8.131.52:https ESTABLISHED TCP 192.168.1.103:50686 bingforbusiness:https ESTABLISHED TCP 192.168.1.103:50687 184.108.40.206:https ESTABLISHED TCP 192.168.1.103:50688 220.127.116.11:https ESTABLISHED
So this is what i got with netstat without playing. Gimme a sec and i’ll start a netstat while playing. However, i started noticing that the hiccups are synced way often with a program that randomly activates itself (still can’t recognize which since it’s for a split second). Lets see what else i discover.
Edit: here is the netstat check while playing LoL
> Proto Indirizzo locale Indirizzo esterno Stato > TCP 127.0.0.1:10501 DESKTOP-NIJS6OE:50598 ESTABLISHED > TCP 127.0.0.1:10502 DESKTOP-NIJS6OE:50599 ESTABLISHED > TCP 127.0.0.1:49836 DESKTOP-NIJS6OE:65001 ESTABLISHED > TCP 127.0.0.1:50590 DESKTOP-NIJS6OE:50600 ESTABLISHED > TCP 127.0.0.1:50590 DESKTOP-NIJS6OE:50606 ESTABLISHED > TCP 127.0.0.1:50590 DESKTOP-NIJS6OE:50609 ESTABLISHED > TCP 127.0.0.1:50590 DESKTOP-NIJS6OE:50749 ESTABLISHED > TCP 127.0.0.1:50590 DESKTOP-NIJS6OE:50753 ESTABLISHED > TCP 127.0.0.1:50590 DESKTOP-NIJS6OE:50754 ESTABLISHED > TCP 127.0.0.1:50598 DESKTOP-NIJS6OE:10501 ESTABLISHED > TCP 127.0.0.1:50599 DESKTOP-NIJS6OE:10502 ESTABLISHED > TCP 127.0.0.1:50600 DESKTOP-NIJS6OE:50590 ESTABLISHED > TCP 127.0.0.1:50606 DESKTOP-NIJS6OE:50590 ESTABLISHED > TCP 127.0.0.1:50609 DESKTOP-NIJS6OE:50590 ESTABLISHED > TCP 127.0.0.1:50749 DESKTOP-NIJS6OE:50590 ESTABLISHED > TCP 127.0.0.1:50753 DESKTOP-NIJS6OE:50590 ESTABLISHED > TCP 127.0.0.1:50754 DESKTOP-NIJS6OE:50590 ESTABLISHED > TCP 127.0.0.1:65001 DESKTOP-NIJS6OE:49836 ESTABLISHED > TCP 192.168.1.103:49714 18.104.22.168:https ESTABLISHED > TCP 192.168.1.103:50625 22.214.171.124:https ESTABLISHED > TCP 192.168.1.103:50629 126.96.36.199:2099 ESTABLISHED > TCP 192.168.1.103:50630 188.8.131.52:5223 ESTABLISHED > TCP 192.168.1.103:50655 wo-in-f188:5228 ESTABLISHED > TCP 192.168.1.103:50657 mil04s26-in-f14:https ESTABLISHED > TCP 192.168.1.103:50670 184.108.40.206:https ESTABLISHED > TCP 192.168.1.103:50694 220.127.116.11:https ESTABLISHED > TCP 192.168.1.103:50720 mil04s22-in-f3:https ESTABLISHED > TCP 192.168.1.103:50721 mil04s04-in-f33:https ESTABLISHED > TCP 192.168.1.103:50722 wk-in-f104:https ESTABLISHED > TCP 192.168.1.103:50724 mil04s24-in-f14:https ESTABLISHED > TCP 192.168.1.103:50727 mil04s27-in-f142:https ESTABLISHED > TCP 192.168.1.103:50728 mil04s27-in-f142:https ESTABLISHED > TCP 192.168.1.103:50734 mil04s27-in-f142:https ESTABLISHED > TCP 192.168.1.103:50739 mil04s22-in-f3:https ESTABLISHED > TCP 192.168.1.103:50740 mil04s03-in-f16:http TIME_WAIT > TCP 192.168.1.103:50746 18.104.22.168:https ESTABLISHED > TCP 192.168.1.103:50748 22.214.171.124:https ESTABLISHED > TCP 192.168.1.103:50751 126.96.36.199:https ESTABLISHED > TCP 192.168.1.103:50752 188.8.131.52:https ESTABLISHED > TCP 192.168.1.103:50755 184.108.40.206:https ESTABLISHED > TCP 192.168.1.103:50758 220.127.116.11:https ESTABLISHED > TCP 192.168.1.103:50759 18.104.22.168:https ESTABLISHED > TCP 192.168.1.103:50760 bingforbusiness:https ESTABLISHED > TCP 192.168.1.103:50761 22.214.171.124:https ESTABLISHED > TCP 192.168.1.103:50762 126.96.36.199:https ESTABLISHED > TCP 192.168.1.103:50763 188.8.131.52:https ESTABLISHED > TCP 192.168.1.103:50764 server-143-204-10-214:https ESTABLISHED > TCP 192.168.1.103:50765 a23-50-155-27:http ESTABLISHED
Found out the problem, still i have to figure how to fix it: the GPU simply gets a spike in Memory Clock and Core Clock every once in awhile. Any idea on how to fix this?
msi afterburner. Set the clocks slightly under what is causing the issue. Sounds a lot like why there are so many RTX cards “failing” They aren’t technically failing but the clock rates they are set to by the manufacture is slightly higher than the memory can handle. Some people say its the memory degrading. I’ve been overclocking anything and everything for years. Its just clocked to high. Lower it and you should be stable.
Ok, thank you very much!
I watched this video just yesterday. He explains how he fixes his 2080ti by simply under-clocking the memory. https://youtu.be/t5memuI5WD4
Hope this fixes all your issues!
Cool! Thanks! Now quick question as i can’t watch the video right now as i am ending to program a mobile game for school. If i give back my GPU and substitute it with another yet same GPU model, does this solve the problem or is it actually a problem by nature of the GPU model?