Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
You could probably disable speedstep and leave turbo enabled. But I would leave it as is, Counterstrike source is probably not demanding enough for that CPU to even register it nots idling! We used to play on some CS:S 32 man servers that ran on 1.6ghz celerons back in the day![]()
Aytacaksel isn't that vcore is a bit high for 4.5 isn't it? Mine does 4.5ghz @1.31.
I think ive thought of away round it, bascially this turbo way is good but not so much for me![]()
I only get to see my 4.9 overclock if i use stress test lol.
So i was thinking how about i turn off turbo and EIST, Set multi to 49 and enable all energy features that way, im thinking it should idle at around 1.6GHz or whatever and then soon as i do anything it should shoot upto 4.9?
That is exactly what it should be doing anyway with those settings it'll only up the voltage and frequency when its under load, and it'll scale as needed to achieve maximum performance while remaining efficient - is the frequency scaling actually impacting performance for you or is it just anmental thing that it doesnt feel like its performing to its full potential because it hasnt hit its peak turbo frequency?
I seem to have sorted it nowI have turned off turbo put multi to 48 and also turned off EIST... This seems to work better as all my games will run @ 48 and when im idling it will drop to 1.6.
It SEEMS that this board if you run flat out without any energy features on, It will BSOD randomly, I would suspect that a bios update will sort this....
BUT...
If i run anything slightly demanding it will just run @ 4.8GHz...
If im just surfing it will just sit at 1.6
Bonus works well.
There is a new MSI beta bios 1.8b7 btw
Has it been said to have fixed this issue?