Stupid high temps on R7 5700x just with vortex idling and me away from the computer for about 20 mins.

[Zacuscra]

Skip to 3 if you don't want to read my very long and hard to read ramble ( but it's got relevant info! ).

1. So, as mentioned above my CPU starts shooting up in temps as if I am using cinebench or any kind of stress test software to see how my cooling setup handles my CPU in terms of keeping it cool ( also I've just downloaded cinebench r23, ran it for 10 mins and the temps I get are 55-57°C with let's say 20-24 ambient temps). But what temps do I get when this happens? 67°C is the highest I've seen which is outrages and makes my blood boil. I've got a Scythe FUMA 2 Rev. B paired with 3 ARCTIC P12. If I see any responses with "MaYbE ITs YOuR cOOliNg ThAt iS tHE ProBLeM" Imma just ignore it and definitely not insult your intelligence while reading it. So to keep it short if I let Vortex open while my pc is idling at some point the temps start to rocket for no reason, it starts very fast, from 30-35(normal idle temps for my cpu) to 55°C in an instant (hence why I said it feels like I'm stress testing my cooling solution) and then it will only go up like all the youtubers drama lately. Closing Vortex won't stop this, only a pc restart will. Now I will admit I did not look in task manager to find a lonely Votex task sitting there having a grand old time with my CPU, but it doesn't make any sense, I close it (and no, I'm not MiNimiZinG it, again all responses like that will be treated just like the one example I mentioned above), looked at the CPU usage which was about 2-20%, the usual for me since I always have a browser opened with youtube on it. The CPU clock was about the same as always if a little high. Now, the only part that might be a problem is the fact that I'm using msi afterburner to check my cpu temps, which for amd is kinda "meh" since I can only see the whole package and not per core temp since it just mirrors the cpu package temp to all cores. But I also use amd ryzen master so It's fine when it comes to accurate temp reading coz it reports the same max temp I see in msi afterburner. Plus I know that amd rockets a random core to near max clock speeds when doing mundane tasks for efficiency reasons and that might report high temps since one core might reach 60°C for just a moment, but it isn't the case here. And now to the annoying part, the high temps, the low CPU usage which do me a big confusion but the cherry on top is that it slows my system down A METRIC BUTT TON. To add insult to injury is the fact that it only happens when I truly am afk, and I mean it, right now as I am rambling and not using my CPU in any intensive way, it will refuse to do the thing only doing it when the pc is truly "idle" with vortex open (hence why I wont post any screen shots as of posting this, but will do later so no worries, it's just too late and I don't wanna do it atm coz I want sleepy time).

2. Was this post hard to read? YES. Is this potentially a BIG PROBLEM? Idk, maybe for people with R7 5700x? Who knows? Did I say I will keep it short but in fact made it biblically long? HELL YE BROTHER! 

3. The truly short version: Vortex open, Pc is idling, temps start rocketing on CPU with no indication why, closing the application doesn't help, maybe process hunting in task manager will help if a vortex process lingers (which I shouldn't be doing in the first place if the app would work correctly). One Vortex reinstall didn't do the trick. Replicating the problem will be as easy as pie, so no worries there, screenshots will be posted as well, just wanna see if this is an isolated unfortunate set of events or if other people are experiencing the same and they can shed some light on the issue.

Edited October 20 by Zacuscra

[Nagev]

> closing the application doesn't help

If the application isn't running, there's no way for it to eat your resources. This isn't a Vortex issue.

[7531Leonidas]

Why did you choose not to check the CPU/memory use through Task Manager?  That seems like the best place to start.  It might well be some other process trying to hook in/fight with Vortex.  Maybe even some antivirus or other security stuff.

[Zacuscra]

33 minutes ago, 7531Leonidas said:

Why did you choose not to check the CPU/memory use through Task Manager?  That seems like the best place to start.  It might well be some other process trying to hook in/fight with Vortex.  Maybe even some antivirus or other security stuff.

I did, and nothing stood out in task manager, low usage on CPU (3-20 isn't something to make me worried, windows will always spikes the CPU usage with random background processes, also why would my temps rocket to 58-60°C and then just climb for no reason and with max CPU usage of a whopping 20%), memory doing fine and dandy. Malware or viruses? Well if eset online scanner, adwcleaner, malwarebytes and windows defender say all is good, I think I am ok on that part( plus why would you try and cook a CPU instead of trying to steal stuff with malware/viruses/etc, this ain't no movie where the baddies try and fry your stuff for fun and giggles). When temps shoot up, and it only does with vortex open, this is a dead giveaway for me, I know how I use my PC, the only variable is vortex. Why can I leave my PC on for hours idling with games, browsers and all kinds of stuff running and all will be fine but if vortex comes into play only the lord and a restart can save my CPU from cooking itself. Also, processes fighting? This ain't karate kid for The Task Manager Fighting Club. Let's say it does, first of all why? I only use vortex and it's tools( nemesis which I didn't even bother to setup in vortex, so yeah only vortex ), the games I use are only fo4 and skyrim ae, steam doesn't care about vortex, so who else could mess with it? No mo2 or other tool to say it might be fighting over a games file, if mods might be doing it fine, but not when just sitting there existing and not running any game to give them a reason to fight. But why when the PC is idling and NO game is opened? Why then? Is vortex doing shady stuff while you are away? Why would a different process try and fight vortex over something? Never had that happen in all my 16 years of operating computers, at least not to the point where the CPU wants to host a barbeque, but not with all it's mighty 76Watts, just 26Watts, no 100%, balls to the walls usage AAAAND with what seems to be one to maybe a few cores actually tripping. Again only when vortex is present, just existing, being opened without a purpose, just because I am eating or watching youtube and not touching anything on my PC. Crap development seems more of a problem here and the reason why this happens. At this point I'm getting tired of this mod manager and I see that reaching to a forum to get "help" won't get me anywhere. Would've been nice to see a response with something like "Did you check the vortex repair tool?" or something like that, coz I admit I was lazy and didn't want to bother with this buggy mess called vortex. Why would you assume in an instant it is something else but vortex? There where people having a problem oddly similar with the one I face, but I did not find an answer there. I guess Imma do the good thing for me and switch to a mod manager worthy of my trust and one that doesn't crap itself when installing big mods or collections of mods. One that doesn't freeze like it's winter all day everyday as if we were on Pluto. Thanks for the help, imma just let this bug slide, let others deal with it, since the moderator marked his "answer" as being the "solution" when no attempt was made to fix it in the first place.

[7531Leonidas]

17 hours ago, Zacuscra said:

Now I will admit I did not look in task manager to find a lonely Votex task sitting there having a grand old time with my CPU, but it doesn't make any sense

Sorry, but this is why I asked about Task Manager.  I hope that your new mod manager will be better for you.  Many swear by MO2, and there is also a revised community version of the older NMM.  IIRC, MO2 requires that it is running for its mods to be active in a game session.

And yes, some poorly written software does engage in 'fighting' - for reserved memory addresses, CPU core access, IRQ assignments (more noticeable in W98 and older).  I get tired of saying 'conflicts'.

Really, good luck finding a solution!

[Zanderat]

A better question to ask is why is this happening to only you?  I left my pc on with Vortex open for over an hour and never observed your described behavior.  Temps fluctuate between 28 and 31 degrees celcius (Ryzen 5600X for reference).