Now.

Recently, my reasons right caller has started to sound like a wheezing donkey.

The variable rpm is accompanied by odd changes.

Inaudible tone.

This recent occurrence finally encouraged me to treat myself to an after market solution.

But until that arrives, I wanted to find a temporary fix setting thesis E.

P u fan profile to Silent in the BIOS helped.

But as you would expect, the effect on temperature was negative.

I then under clocked the CPU to 3.2 gigahertz, and this kept the now near silently called 3600 under 35 degrees Idol.

Everything was fine and stable.

This is when curiosity got the better of me.

I'd like to reiterate that word curiosity.

You shouldn't do the following because there's no point unless you want a lover power consumption.

But in that case, you should just buy a low power process, sir.

So, back in the bios, I just kept dropping the clock ratio, rebooting into windows, restarting and then repeating with the clock speed, getting lower every time until I just thought, Let me just put five in this box that didn't work an eight was the lowest week ago.

This then meant that after saving, the settings and exiting are rising, 5 36 100 would be running at just 800 megahertz or no 8000.8 gigahertz.

Bear in mind that the minimum speed recommended by Microsoft for Windows 10 is one gigahertz, so this should be interesting.

After a quick check on our new clock speed in CPU said it was time to assess performance.

Actually, booting into Windows and navigating the desktop felt pretty much the same until it came to Internet browsing.

There were a couple of freezes here and there, which occurred in EJ Chrome and Firefox.

YouTube video playback was also fine on browsing Facebook, checking email and what not was still acceptable.

I then fight up Cinna Bench are 20 the latest software version in which my stock 3600 scores 3489 points at no 34890.8 gigahertz.

Things are surely going to be interesting, to say the least.

Remember, we do still have six cause and 12 threads at our disposal, but I'm not sure how much they'll help.

Eight minutes and six seconds later on the run was complete with a new multicourse score of 689 This is about 80% slower.

Our 800 megahertz horizon could still handle a bit of video editing, though.

I opened up a new project in Premiere Pro 2015 whereby I rendered a 32nd 10 80 p 60 f PS game play clip of rage to rendering Thesis Clip took about one minute and 10 seconds on the under clock horizon, which is still respectable, if you ask me.

But it does pale in comparison to the 18 2nd Render time off.

The stock clocked trip, right?

So now it was time for some gaming and opening up steam and origin actually caused a bigger than expected hinderance.

Both were sluggish to navigate, taking a while to launch my games, and in some instances, the games didn't launch it all.

Eventually, though, things work themselves out, and it was time to start.

First up, it was the turn of some well known CPU hogs, namely Battlefield five and C s Go Battlefield five ran, but it was a bit of a stuttering mess at times to be expected.

I guess the average was actually 49 F p s a 10.

80 p higher with one and 10.1% lows of 15 and 10 respectively, compared to the stock horizon.

And it was, of course, the improvement in percent old figures that helped us out the most.

I'm using a G Tex 9 80 in the system today as I'm making sure all this card works, probably for another time.

So bear in mind that you will see even better results with a more powerful GPU, and the difference will, of course, be larger.

C.

S Cho also suffered a bit as far as a smooth frame rate was concerned.

54 f.

P.

S, on average isn't bad, but we were seeing a lot of stuttering and dips, et cetera, even at 10.

80 p very low.

When you compare this to the standard clock speed results, you can see just how much CSKA relies on process of power.

Still, it was a playable experience at 800 megahertz.

To some extent, kingdom come deliverance also took a beating, but not as much as my character.

It was obvious from the start that things were going to be affected Is the normally instantaneous loading process took a very long time.

Once we were in the game and after I had managed to wind up the whole town.

10 80 p medium granted us an average frame ary of 40 with lows off 23 three.

It didn't feel as bad as those numbers make it seem.

However, some games couldn't care less about our processes speed, especially if they are more GPU dependent rage to, for example, run very similar both times round.

But again, bear in mind, the 9 80 was still maxing out.

So if I had a 10 80 in here or something, the Gap would likely be even bigger, still focusing on the CPU.

And it's clear that Nor 0.8 gigahertz is of no negative concern to this title, and the game just ran very well.

The same can nearly be said for Resident Evil seven.

This game presented a nice average frame right, though there were some instances of drops, most noticeably when going through doors, something that wasn't present at stock CPU speeds.

So I guess there we have it.

This has probably been one of the most pointless videos your watch, the seer, or perhaps ever.

But curiosity just got the better of me here.

I did something similar a few years ago where I undercooked a G 30 to 58.

I believe it was 21 gigahertz.

And that being a two core CPU anyway wasn't exactly the best performer with the standard clock speeds, at least not towards the end of its life.

Nonetheless, I hope you've enjoyed watching this.

Please do not repeat anything you've seen in this video.

Especially that terrible donkey impression at the start.

If you enjoyed it, leave alike on it down below.

Leave a dislike.

If you didn't subscribe to the channel if you haven't done so already and hopefully I'll see all of you in the next one.