8150 bad overclock

[Shadow-R]

Terve!

My situation is eventually a little confusign, but I'll do my best to explain it to you.

I do run a work-PC that has an AMD FX8150 on a Crosshair V Formula Z.

This Mainboard alredy died twice, but now I am confused.

I wanted to re-overclock this thing (just got it back from the 2nd RMA), because the CPU was alredy running at over 4.9GHz in the past - though there was high voltage included.

Now, the system freezes fast after starting intel burn test, when I am on 4.3 GHz (haven't tried lower things yet).

Can someone give me an advice what I did wrong?

I'll post the pics of the BIOS, so you can imagine.

Tell me, if you need more.

Thanks already.

Sayonara!

P.S. one of the pics displayed an error while uploading, I'll redo it and upload it then.

[Totally-A-Hero]

Luck of the draw and you lost.

[helping]

Luck of the draw and you lost.

He was already running it at 4.9.

 

Try giving CPUNB, NB, and VRAM a bit more voltage.

 

Turn off C6 state.

Try multi-only clock, that FSB clock might be unstable for a copious amount of reasons. CPUNB and HT look pretty high.

[Shadow-R]

He was already running it at 4.9.

 

Try giving CPUNB, NB, and VRAM a bit more voltage.

 

Turn off C6 state.

Try multi-only clock, that FSB clock might be unstable for a copious amount of reasons. CPUNB and HT look pretty high.

Terve!

Well, I do not know so I will try...

But the tutorial I saw (JayztwoCentz) mentioned that Core C6 can be enabled and you should use the FSB over the Multiplier (I hope I got you right that you mean I should use the multiplier when you said "multi only clock").

Also, I can remember that I was getting the stable frequency on 18.5x265 (multiplier x FSB).

Thank you anyways, I'll tell you my results.

An other option I considered was buying an FX 8350, but it would be worthless if the mainboard is "bottlenecking" the overclock.

P.S. 4.2 Wasn't stable eighter.

Sayonara!

[-rascal-]

Do did notice there is "Print Screen" function within the UEFI BIOS that can be saved....(I've got a Crosshair V Formula myself)

 

First thing I see:

• You have an unlocked multiple CPU. Why are you even touching the CPU Bus Frequency?
• HT Link speed is quite high. That may be contributing to your issue.
• See if increasing your CPU/NB voltage helps in any way.
• Enable HPC Mode (High Performance Computing)
• Disable APM Master Mode (Application Power Management)
• Disable C6 State

And...

• What is your CPU Load Line Calibration Set to?
• CPU/NB Load Line Calibration?

[Shadow-R]

 

Do did notice there is "Print Screen" function within the UEFI BIOS that can be saved....(I've got a Crosshair V Formula myself)

 

First thing I see:

• You have an unlocked multiple CPU. Why are you even touching the CPU Bus Frequency?
• HT Link speed is quite high. That may be contributing to your issue.
• See if increasing your CPU/NB voltage helps in any way.
• Enable HPC Mode (High Performance Computing)
• Disable APM Master Mode (Application Power Management)
• Disable C6 State

And...

• What is your CPU Load Line Calibration Set to?
• CPU/NB Load Line Calibration?

 

Terve!

So, I'll try to answer your questions:

I touch the FSB Frequency because I heard that in Jayz' tutorial and well ... 4.9GHz this way - why doing it different then?

Also I tried using the multiplier and I did not get anywhere near the 4.9GHz of the FSB-technique.

I can say, that the stock 2600MHz is also instable, so its probably not that.

I'll see to that soon. Just re-set everything. I've got these feeling I screwed something up in the settings.

Also, I set the load lines to extreme. I don't think that this MB should have a problem with it.

Even if I am pulling the near 200W of my "old" 4.9 GHz setup, there was the 9000 series that pulled 220W stock.

Lets see, what the new stock test will tell me...

Thank you for the help.

Sayonara!

[Shadow-R]

Terve!

I think, I could rename this topic now.

As I ran a longer "standard" test, I saw that the system was not stable eigter.

Well, Step 1: don't overclock - I'll have to consider this one more serious next time.

I'll run an other stability test, but this time I'll undo the RJ45 Cable from the rear IO to see, if I still got the same problem, as before I RMAed the MB.

Sayonara!

[Shadow-R]

Terve!

Hopefully I can help out other with this, since I do not think that anyone checks this anymore.

With several tests, the purchase of a new CPU for upgrade and diagnostic reasons and Hardware from my friend I was able to find out that I appear to have flaw within Windows.

I would never expect something like that to be possible, but now I know...

Sayonara!

[-rascal-]

Terve!

Hopefully I can help out other with this, since I do not think that anyone checks this anymore.

With several tests, the purchase of a new CPU for upgrade and diagnostic reasons and Hardware from my friend I was able to find out that I appear to have flaw within Windows.

I would never expect something like that to be possible, but now I know...

Sayonara!

 

Happy to hear you found the root of the problem.

[Priller]

I'm glad you found the issue but for future reference I would drop the HT Link speed down 1 step and increase CPU/NB voltage to 1.25.

 

That will give you a good be of flexibility in terms of overclocking and raising the ram speed.

[Shadow-R]

Happy to hear you found the root of the problem.

Terve!

So, if someone appears to be looking into all this, I have to correct.

Because I have a spare system with the same chipset I was able to put both storage devices on an other PC.

It was stable...

Now, I can only guess that the problem is that my mainboard is dead again and I can tear apart my liquid cooled thing again.

Can you imagine how nerving it is, if you get two ASUS RoG Mainboards that are dead out of the box (error in RAID function and instability with more than one starage device)?

Not that I would not test my stuff before I build the liquid cooled stuff around it, but comeon, I do not test the stuff that detailed...

Hope I was able to give someone who needs help a little tip.

Sayonara!