Thanks Informal.
You don't happen to play Urban Terror 4.1, do you?
It really depends from chip to chip. I definitely agree there is a weak-er core within Phenoms compared to the other three, but it's not always core2, it's been core1 and core3 aswell.Originally Posted by Oc-Ghost
Disabling it should allow higher MHz, higher MHz benchable, higher stable MHz, high MHz at lower volts or a combination of these if it really is the setback. It's up to the user to test and find out whether it is.
The problem is, with Phenoms each core has a separate PLL, they are independent clockers. You can use AOD to keep one poor clocker at stock when oc'ing and you can see very clearly if you will get more MHz (etc) on the other ones. With most users there isn't much increase at all. The ASUS RD790 already has users doing this with their oc's.
Not sure really. Don't have the board here to check either and from memory, I think you're referring to two pins? I haven't seen any documentation on them that I recall. Will checkup later when I get back to flat. It won't be a BIOS backup though.Does anyone know what the extra set of pins next to the CMOS reset jumper is? I couldn't find any docs on it. I was really hoping you guys were going to tell me it was a static/backup bios...
You guys all flashed the same file it seems, because others haven't had this problem yet (many I know who have flashed it). I've flashed/re-flashed it at least 8/9 times. I flash the files on my disk (originals) and I've had zero problems with P0H but you will get these problems with many BIOSes on all boards if you don't set defaults before flashing, if you don't use the switches and if you don't CMOS clear and then power down after flashing (for BETA's) before starting up. You're all encountering pretty much the same problem here.
Let me know if you've both flashed the file aGeoM linked and I'll hunt him down.
I'm kidding.
I'll flash the file myself and see if it's the file that's corrupt.
Also, clear CMOS and then power down, i.e. switch the power supply off or disconnect it. Leave it like that for an hour. Then connect again and restart with a minimal build. Does it POST (keep pressing Del)?
I always use the failsafe and established stable method and through good [nightmare] experience across boards too.KTE: Yes, I reset to stock speeds/no OC before I flashed, but I didn't use those switches... The wierd thing is I used the same method to flash as Jesterone (USB drive).
Many boards react differently but FDD flash is always set to work right. You should always use the pbnc switches or you're setting yourself up for error, especially with BETA's. The good thing about FDD's is that you can access them on all systems in all ways.
Behind the scenes the amount of troubleshooting I do is really ridiculously tedious when dealing with a new platform, like this. It comes part and parcel of "BETA testing" though.
I strongly hope he was talking out of his rear there.
I'm now planning on getting rid of the board actually and maybe swapping to see if other boards have made any progress.
BTW, those replies are pretty poor. Maybe you should tell him that we pay not the other way round.
Nice, looking forward to it.Very interesting together with the comparison of intel cpu's. Got an qx6850 ES today, rest of the system arrives tomorrow. Will have that stuff for about two weeks. During all my ocing I ran cinebench 10's opengl and multi-cpu benchmark and noted points/time used and temps and power consumption during the cpu benchmark, so i can do a similar comparison between my be9600 and that qx6850.
BTW: Also an 5000be arrived here today, so much to play with.
The QX6850 is hot though, you'll need a good cooler or it'll start throttling under loads as it reaches plus 85C with many aftermarket air coolers. So results might be less than accurate if it does.
Reply With Quote
Bookmarks