The division open beta is doing something very strange to my CPU, The game is hammering it, its NEVER been over 50% in any game before, including witcher 3. Its also making my core clocks go crazy, im running a smooth 60-70fps all high. My normal clock is 3.85Ghz Nothing else does this, even stress testing, any help or ideas to why this is happening?
Could just be the way the Beta has been programmed. Reports on forums suggest it just eats resources.
I have the same CPU. Its behaviour depends how you have it configured in BIOS, and you should really have things like C1E, C-states and EIST disabled so that your clock speed doesn't change depending on the load. My guess would be that you have c-states enabled, which is why your CPU clocks down to 3GHz at 0%. I'm on the lappy just now, but when I get on my PC later I can check my CPU settings and share them here. EDIT: Just noticed that one of the readings is 4900MHz. LOL. Something's not right, so as TheMadDutchDude said there's probably something up with the software. It's worth remembering that you have a non-standard CPU and this can cause confusion for your motherboard.
All power saving and turbo options are off. When idle and playing anything else the CPU sits at its clock, 3.85ghz. Even with the frequencies dancing about in game I have a very smooth and stable 60-70fps on high. If it really was jumping up to 4.9ghz I would crash. So do we think these are false readings? Anyone recommend any other software to monitor core clocks?
Why do you want to monitor the clocks? If your system reports 3.85 GHz in CPUZ and does not crash under Prime 95 ... there's nothing wrong.
The burning question: what software are you using to report & log the CPU info? And why would you need to monitor CPU clock speed if you have power saving features disabled and you know what the clock speed is?
Hwmonitor, I guess I'm panicking over nothing. I do know because in don't have a super high end board I'm getting current throttled in stress tests, but there's nothing I can do about that on this board unless I wanted to risk doing some crazy BIOS cross flashing.
Stress tests are only really valuable if you're likely to do something that takes your CPU close to 100% usage, like folding etc or rendering. I do 3D rendering on my PC and I need the assurance that it won't crash due to instability; for gaming, I think you can get away without extreme stress testing. Edit: and after having tried the Beta for myself, I've come to the conclusion that it was a waste of my time and a waste of 27.8GB of HDD space. Initially I couldn't even run the game because the servers were down; I tried again later when the servers were back up and I managed to get into the game for a whole 3 minutes before it crashed and I had to hard reset my PC. First impressions? Not great, lol!
Pleasure. And I should also mention that it is one of these extremely annoying games that requires a restart if you want to change video settings. Why can't game developers just stop doing that already?
Might be to do with different assets being required by different graphical features and perhaps different loading techniques tied in with the game loop is my best guess. But I only had a stab at game dev once...It's very hacky.
