• Competitor rules

    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.

Intel to launch 6 core Coffee Lake-S CPUs & Z370 chipset 5 October 2017

humbug said:
Read this ^^^, the only two Ryzen owners in this thread who clearly have an issue with it think boot loops are normal CPU behaviour. it explains everything.
Click to expand...

Boot loops happen a lot, especially if you are being super aggressive with timings, or pushing the speed limits of your RAM. Bear in mind I've build systems since the R7 launch, all the way up until two to three weeks ago, so I don't think all of those CPU's were faulty.
 
humbug said:
At anyone reading this, if you see his ^^^^^ CPU on the MM don't buy it, its broken.
Click to expand...

This is what happens when people don't read.
Its fine at <3200, its a limit of the IMC. Google it, I supposed adored or hardware unboxed haven't covered it though so you wouldn't have seen it.

I'd offer it you but your too tight.
 
Journey said:
Boot loops happen a lot, especially if you are being super aggressive with timings, or pushing the speed limits of your RAM. Bear in mind I've build systems since the R7 launch, all the way up until two to three weeks ago, so I don't think all of those CPU's were faulty.
Click to expand...

Probably why I haven't seen them, the only thing I got was the RAM defaulting back to 2133 when I tried to overclock it too far with too tight timings.

Does a boot loop mean you have reset the BIOS back to default to stop it ?
 
Journey said:
Boot loops happen a lot, especially if you are being super aggressive with timings, or pushing the speed limits of your RAM. Bear in mind I've build systems since the R7 launch, all the way up until two to three weeks ago, so I don't think all of those CPU's were faulty.
Click to expand...

Anyone who has 30 minutes experience of overclocking knows this, the difference between them and these two is they don't. they think its something or at least are trying to make out CPU overclock failure is unique to Ryzen.
 
gavinh87 said:
Yup, right up to the point is saw it bottlenecking a 1070 in destiny. And getting beat by i3's in games. No i disagree with anyone that hasn't even owned a ryzen. It'd be nice if one of the people talking it up actually had one and we could have an informed conversation.....
Click to expand...
I didn't buy one that is correct.... I didn't but one because I have one of those haswell you are talking about. Even though I was tempted and admire AMD for what they have managed to achieve from the position they were in and resorces they have available to them, I knew it wouldn't be worth the investment for my needs.

Now Zen 2 is a different matter all together and barring any unforeseen problems I will no doubt be buying one.

Sorry Gavin I respect your opinion and you as a person but your tune changed rather rapidly and you should have known better.
 
Last edited:
"Due to the way DRAM settings are implemented by AMD, we currently have no way to apply anything but default voltages at boot after removing standby power from the board. On top of that, if DRAM training fails (showing F9 on the Q-code display), all AMD CBS settings are currently reset to defaults and we're currently not detecting when this happens. This can result in the user suddenly running at default memory speed and timings, without being aware of what happened. Additionally any settings in AMD CBS like Global C-states or custom P-state settings will have to be entered again. We have a workaround microcontroller firmware which always starts the system with 90 MHz REFCLK and 1.35V DRAM voltage which should help most systems to successfully boot from a full power off without issues. To test it, first make sure your system boots up without problems after setting 90 MHz REFCLK on you current BIOS. If that works, clear CMOS and flash BIOS 0003 (SHA256 85a89c66813a0369dd2718a4f5e11d957ffae80410445155758b4f1a3a39899f) using either EZFlash or USB BIOS Flashback. It will show the "Bios is updating" message which became synonymous with boards bricking, but don't worry, it will flash successfully this time. After the process is complete and you're booted into BIOS, you can revert to whatever previous BIOS was working well for you. This fix will still be applied. Just make sure you're manually setting REFCLK (BCLK Frequency) 100 MHz or your preferred setting. If left at Auto you might end up still running at 90 MHz."

^^Posted by elmor from ASUS.




They are all dud. Everyone with a cold boot bug has a dud CPU.
I guess AMD need to up their QC :)
 
DarkHorizon472 said:
Probably why I haven't seen them, the only thing I got was the RAM defaulting back to 2133 when I tried to overclock it too far with too tight timings.

Does a boot loop mean you have reset the BIOS back to default to stop it ?
Click to expand...

Depends on the board manufacturer, I tend to stick with ASRock at present, and you can set the number of times you want it to retry the speed/timings before it defaults it back to 2133/2400. I've once or twice had to reset the BIOS via jumper/button, but not at all often. Also it's much less infrequent than it used to be with newer AGESA versions, but from time to time on a cold boot, you'll get dumped in to the BIOS after the selected number of retries .
 
Journey said:
Depends on the board manufacturer, I tend to stick with ASRock at present, and you can set the number of times you want it to retry the speed/timings before it defaults it back to 2133/2400. I've once or twice had to reset the BIOS via jumper/button, but not at all often. Also it's much less infrequent than it used to be with newer AGESA versions, but from time to time on a cold boot, you'll get dumped in to the BIOS after the selected number of retries .
Click to expand...

Thanks, I was assuming it was a problem with the older BIOS versions more but have never had a boot loop when the BIOS gets stuck in a loop booting.
 
humbug said:
Anyone who has 30 minutes experience of overclocking knows this, the difference between them and these two is they don't. they think its something or at least are trying to make out CPU overclock failure is unique to Ryzen.
Click to expand...

I have posted over and over that my system is stable, 4000% HCI and OCCT passes with avx enabled. With screenshots, so go search for them.

Asus know there is a cold boot bug, hence the 90mhz refclock bios "mod"
 
DarkHorizon472 said:
Thanks for the reply, I understood the memory training, I was wondering what a boot loop was ?
Click to expand...

He overclocked the CPU too far, but he doesn't want to tell you that, he's trying to make out Boot Loops are normal for Ryzen, as if they are fundamentally flawed, which explains his vitral behaviour around here.

A Boot Loop is where it will keep trying to boot but never does, its typical if you overclock to high. if you overclock ANY CPU to high.
 
humbug said:
He overclocked the CPU to far, but he doesn't want to tell you that, he's trying to make out Boot Loops are normal for Ryzen, as if they are fundamentally flawed, which explains his vitral behaviour around here.
Click to expand...

Watch this that andrei posted. https://youtu.be/vZgpHTaQ10k?t=870

You are making assumptions on a platform you know nothing about.
Yes, my cold boot issue could be fixed by using <3200 ram, but why should I when 3466 is stable?
The IPC is bad enough let alone running it any lower lol.

Please, stop posting fud. You know nothing about the ryzen platform.
 
humbug said:
He overclocked the CPU too far, but he doesn't want to tell you that, he's trying to make out Boot Loops are normal for Ryzen, as if they are fundamentally flawed, which explains his vitral behaviour around here.

A Boot Loop is where it will keep trying to boot but never does, its typical if you overclock to high. if you overclock ANY CPU to high.
Click to expand...

I see what you mean, I stop going higher when temps and volts needed start to rapidly accelerate.
 
@DarkHorizon472 Ah, misunderstood you then. My board for example has a setting for it, I have it at 5 retries. So it just goes from the shutdown state to initializing the BIOS and if the memory settings don't work, after the 5th try it just reverts back to defaults and initializes the BIOS normally.
I had it happen when I tried some very aggressive RAM timings at 3200, but after I loosened a few subtimings everything was stable and no boot loops.

@humbug Stop, you're embarrassing yourself.
 
You must log in or register to reply here.
Back
Top Bottom