However, they still suck in some areas, and I'm going to show you exactly how I play them back in that statement up today's video sponsored by dropping the Sun Heizer HD six xx professional grade reference headphones.

But when the 50,000 units sold, the HD six X X is by far the most popular headphone ever sold to drop the severe build.

Quality, comfort and lightweight features make the HD six X X is among the best headphones available for their price.

If you're curious to see how high end audio sounds without high end pricing, then click the link in the description below.

So recently on, Twitter follower reached out to me, asking if I'd seen any of the temperature issues that allowed people were reporting with the 3900 ex.

Apparently, there's been a lot of controversy like apparently, it's 50 megahertz lower than advertised or something like that.

I mean, a lot of straw grasping going on people just wanting to be mad at brands for whatever reason.

And there's another one going right now, which is the fact that the sea pews are running super freaking hot.

And that's not something that we didn't experience at the time of doing our build here, which you guys might remember.

This is our dark night build, one of the cleanest aesthetic builds I've ever done.

I'm glad we kept it together because we're gonna do some testing here today, and we're going to show you exactly what I mean with there are just problems when it comes to adopting new platforms.

This being no exception.

Now, when we did our 1st 3900 ex review, we used the crosshair motherboard.

The new issues across there remember the exact number was of it or whatever, but they called it something else, was really expensive board and we noticed very high temperatures, even with a Iose.

And we also saw that the BIOS was pumping way too much voltage to the CPU and having some back and forth with a sucess sentences on the board.

We were experiencing very similar results, and it was then basically like, well, the C B is the problem until in giving the voltage of CP is asking for.

So whether or not it's a micro code problem or not, I have no idea.

I'm seeing a lot of people talk about extreme temperatures.

It's not just the core density, the fact that there's 12 cores and 24 threads on.

And, of course, those core modules being seven.

Animator.

Very focused Heat two of those crammed under N I.

H s, including an input output controller.

That's a lot of heat focused under one area.

But that's not the problem.

The problem, quite honestly, is the amount of voltage it's being pumped through it now.

Whether things I planned on doing here with this x 5 70 god like M E g Godlike board from a mess, I would show you how we've kind of gone around that and some manual changes there.

But the first thing I always recommend that people do when they're dealing with issues in terms of wonky bios settings, take your bios.

Unfortunately, we were blocked.

You can add a word in front of blocked if you want.

I'm moving forward with that particular video we start to shoot this one because updating the bios now is effectively bricked our system and a sigh.

You make great hardware, but you're up there with the ranks of Gigabyte in the fact that your BIOS team sucks.

Donkey balls.

I'm sorry.

Oh yeah, and it's RGB puke, because again, I Q doesn't have any has volatile memory, which means that when you turn it off, there's no controller until you're back in Windows and are able to control your lighting's.

That's why we have RGB people.

Check that out.

CPU error.

Guys, this is the fresh by this install we got to the BIOS once.

And so what I'm gonna do now is I'm just gonna do a simple, clear Seamus, and we may or may not get into the BIOS.

This is what I've been experiencing all morning, a system that was working perfectly fine until I did nothing but installed there.

Stability improvements, bios, the ab 01 which apparently everyone's loving, and I'm now getting a system that gives me absolutely no post because it's just like, oh, you do a clear sea.

Moss is a lot more stuff that happens when it boots back up memory training, all that sort of stuff.

So it takes a lot longer than he was a postcode.

There we go.

So here's the thing.

We're now in bios.

What?

I want to show you right here.

Devices changed memory or Seamus has been cleared.

Yeah, I know.

I did it.

All right, so we're going into bios right here.

Previous bios was actually running 1.35 volts on its own, set to auto in the new BIOS 1.498 volts.

No one in their right mind should be running 1.5 volts on this.

I don't care if 95 c is appropriate.

I don't care what the max temperature is.

1.5 volts is absolutely ridiculous now.

Yeah, maybe showing that the CPU temperatures running a 29 c.

But this is all factory settings.

Okay, fine.

Good enough, right?

That's fine.

Factory settings, F five.

No, because it's different there.

F six is little optimized defaults.

Once again.

F 10 saved exit.

Let's see if it'll even post.

This is what I experienced last time.

Where would immediately give me a CPU air?

And I don't know if that has something to do with the amount of volts that it's just shoving down the Si pues throat or four actually get a good post or not.

Now this is not.

This is not isolated to the 3000 Siri's.

This happened with the 1000 Siri's.

This happened with 2000 Siri's, and it's continuing with the 3000 serious.

So I have I have no doubt brands gonna reach out to me whining and complaining that that look at that.

See, Pierre, this is it.

This one's animus.

I honestly, this could be voltage related.

I don't know.

Let me go ahead and power cycle us again, see if we get to come back.

The one thing I will tell you the M aside does right is at least the RGB values will sustain through a power restart, whereas apparently Corsair can't figure that one out.

That's actually the Corsair block plug directly into the Corsair J header on the scene.

Now we booted.

I'm not feeling very Zen right now because uses saw what I had to go through to get into Windows V Corps is Amanda voltages.

That's like, that's like, then on Ah, intel, which is the voltage in and then each of your cores also look for their own gold.

That's the V I.

D.

But look at this.

The I D 10 is like, I need 1.5 in the restaurant.

One point.

So clearly we have one corps doing something right now, which is probably loading on the background tasks And what?

Not like that.

All the course right now we're looking for 1.5 volts.

That's insane.

Our actual CPU package temp right now is that 46 c at the desktop.

Now, this is what a lot of people are complaining about.

And look, we're back to white now because like, you find it loaded up.

So we are gonna go ahead and run.

Cinna bench are 20 in Luke mode.

I don't think we're going to do very many passes before we start finding our temperatures go completely through the roof.

So what's gonna happen here?

Waltz running Because so much resources air going to our 20 you're gonna notice this is taking awhile to update.

So we're at 61.

See videos at 1.250 vic or dropped down to 1.264 so that's actually not too bad.

All right, so we got a 7074 in our 20 so our max temperature was 63.

See, now that's actually not so bad.

So basically, what happened here is as a c P one under load, that was kind of load line calibration that reduces the voltage.

Now that's what happens when a lot of people do over clocking Leave these settings on stock is the amount of reduction could bring it below.

Stability we're noticing with our ace use board is that wasn't happening.

It was not reducing the voltage.

If anything, it was saying exactly what was it like The 1.47 to 1.5, which is making us see a plus.

See underwater.

So fortunately, the new biosphere did give us a scenario.

We were where we were able to actually see a reduction in voltage where it wasn't terrible.

63 see underwater.

I think that's exactly where I would expect this CP to be given its core density and all that sort of stuff.

I think one test is fine to see what the spikes are going to be, because this if you having an issue of temperature regarding bolted spiking.

It's gonna happen regardless of how long you let the temperatures equalize.

And that's because the amount of voltage being pounded into the chip is not even making it to the cooler to begin with, it's just completely overpowering.

So let's go ahead now and go into the BIOS and I'm gonna show you, at least on this Meg board what some of the changes I would make our Ah, God, Vaughn.

Yeah, that's the reason why I'm making this video is I know for a fact there's a lot of people that built their first systems specifically because A and B came out with the 3000 Siri's, and you may or may not have been dealing with this or are dealing with this, and you're just a you just completely at a loss of what to do next.

You might think you're si pues, bet you might be contacting motherboard support our you know, whoever you support us for your particular motherboard or even Andy and they're all telling you, Okay, we'll send it back Army.

You could get a new C few, put it in and get the exact same problem.

This is unacceptable.

There is no reason with a $700 motherboard in this case in a $500 seep you that this sort of problem should be happening.

And if I sound pissed, it's because of the fact that these companies almost prey on the fact that people are going to go out and buy this new hardware and they build new systems and stuff.

And they're doing half ass saree like this where they're not putting enough effort into the stability of their systems.

And I'm sick and tired of this boat.

This has been happening now, as long as I've been dealing with product launches.

Unfortunately, it's always the worst with a nd I'm now gonna get on my intel system to download a new bride was for this.

Fortunately am aside, does make the BIOS flashback fairly simple in flashback.

Oh God, That mouse leg.

And then what's gonna do is just gonna restart in the BIOS flash utility if it doesn't give a CPU air first some actually rolling back to the previous version.

But I had to do what four restarts, four restarts, and then I just randomly worked anyway, So we're just rolling back one version, toe 10.1 for Oh, I think we were on 00.130 which was like the July build, which was the one that actually launched with.

So we're going with this, do its thing, and then hopefully that see Pierre will start.

We know it's bias related because the problems started with the BIOS.

So with the BIOS update anyway, all right, so the first boot on the old bios with one version old bios so far is a good book.

So well, the screen came on for a second.

Anyway, we get a blue light, but no signal.

Is it?

During a second thing?

I mean, little stupid logo still going?

Ah, there it is again.

See, Pierre?

Uh huh.

When I want to make sure here, game, boost function, patrol bios, options I don't want anything happening there that boost control is set to zero.

We're not even ex MP or any of that.

So I want to make sure everything is just a solid.

It's horrible to just set to auto.

And as you see right there, it's still pushing that super high numbers for money, right?

now Go override.

I'm just gonna hard code and 1.35 volts.

I know that that's fine.

CPU North Ridge.

Eso si voltage.

I'm going to set that at 1.1.

That's fine.

That's a slight nodal point of all.

I do know that there was going and set voltages that I know we're fine, which are much lower than this thing's trying to do from the factory.

And let's just see if this will get into Windows.

It's just frustrating because it was working perfectly fine until they updated the BIOS for the sake of this video.

And there it is, all right, So it's all stock behavior like we expect a couple, of course, and one of the 4.5 this shows are 1.352 V Corps on there.

There are videos you can see.

It's still pulling all of its 1.45 So let's just go ahead and run this again.

Oh, I dropped only done one volt did.

Oh, yeah, I see.

The core clock dropped way down.

That's probably it's under bolting now, and that's expected behaviour because we've seen that happen with Steve.

Steve did a very good video.

Gamers nexus about how the voltage and core clock definitely are connected.

So because we pulled the voltage down, Arvid went way too low, and so we should see a significant reduction right now in a score.

Oh, yeah, look out for that drop down 58 65 7000.

So let's go ahead now with this BIOS, I just hit Restart.

Let's see if it'll boot or not.

Go back to the factory defaults and see what happens with the voltage in there.

But if this video has served any purpose, it's not to fix your problem because you can't fix the problem that's taking place at the BIOS levels.

Because the BIOS and many of these instances are the problem, you can go in there, make manual changes.

But if you're dealing with, like the problem deal with here, which is the CPU error on freakin restart when it worked just fine.

That's on a Masai.