We have almost the same problem. My problem child core is Core 2.Quote:
Originally Posted by GunterFalstaff
We have almost the same problem. My problem child core is Core 2.Quote:
Originally Posted by GunterFalstaff
My 9850BE just stopped working. This time lm-senors detect was the cause. I booted the board with an 5000BE flashed the Bios and cleared the DMI area. But no louck with the 9850BE, stuck at C1, even with DDR2-800 memory. The 9600BE works. :mad:
I had the same problem with my first 9850, i sent it back and it was verified dead. Now my luck seems to be getting worse cause my new 0811bpkw wont even hit 2.6ghz without bsod'ing. It may be this m2r thats almost got me ready to switch to intel but im not sure yet. Another weekend of cursing will be the tell.Quote:
Originally Posted by justapost
You also trashed your cpu with sensors-detect under linux? I saw one user reporting the same issue here. Thought it is a random occuring phenomenon, so i tried it. 2.6GHz does not sound promising. Intel slowly becomes an alternative here also. :shakes:Quote:
Originally Posted by The Weedman
I'm using lm-sensors, no problem for me on MSI K9A2 Platinum and Abit AX78. Looks like a board specific happening :(
I'm sorry for you, I know what it feels, mine was after benching in Sandra. :(Quote:
Originally Posted by justapost
+1 , my "new" 9850BE 0809EPMW only boots at 2.6GHZ and vCore 1.36v in Vista x64, more it's a no go, doesn't matter what I do. Vista x86 2.7GHz at same vCore.Quote:
Originally Posted by The Weedman
Yeah, I ran lm-senonsor succesfully on the M3A with the 9600BE. It's the detection routine for SMbus that killed the chip.Quote:
Originally Posted by KTE
Time for RMA, 2xPhenoms for AMD, 3xHD for Western Digital, that saves shipping costs. :)
@aGeom: Thank you, looking at your and weedman's steppings 810's seem to be the best clockers atm.
Tssk , Tssk , Tssk:shakes: Why is it that I do not have any of these issues with DFI 790FX-M2R or 2 Phenoms now? Lets look at the common denominator here.....Ummmmm....thats right High HT and too much voltage:yepp: When are you guys gonna listen? I keep saying High HT means moot and AMD CPU's have a memory when it comes to voltage applied and the Phenom needs to be approached with a light and artful touch:rolleyes:
Perhaps this is my fault as I have not been able to dedicate the time to posting the necessary precautions associated with overclocking Phenom with this board:( You CANNOT leave the default Vcore of 1.31 set in Bios and work from there by leaning on the Voltage in attempts of overclocking Phenom guys! First agenda should be to get it to run stock at the lowest possible voltage settings and train you're CPU to run at such. AMD CPU's have a memory and if you train them to run stock at @1.31v then after a certain period of time they will not run stock at lower voltage and even more voltage will be required to overclock the CPU in Return, which from the start what I have seen on this forum in regards to Phenom Overclockig leads to failure in a hurry! Take the advice and release these old mundain thoughts associated with K8 Overclocking (High HT) as it means ...MOOT...and should only be used to fine tune you established Base Overclock which is achievable via CPU , NB ,HT , Ram all being able to clock independently HT Overclockig is DEAD...Get Over It already please:yepp:
My cpu died on an nearly unoverclocked system.
CPU: 13,5x200 = 2700MHz at 1,3125V
NB: 10x200 = 2000MHz at 1.3V
MEM: 400 4-4-4-12-20 75ns at 2V
It froze as sensors-detect tried to find SMBus devices and gives C1 since then. I'm sure it would ahve done the same at 2.5GHz.
:rofl: man, we are not talking about 9500/9600 vanillas, HTT/HT are set @200/2000 default, mine died @:Quote:
Originally Posted by Brother Esau
CPU=15x200=3000 vCore=1.36v
HTT=200
HT=10x2000/1.27
NB=12x2400/1.325
This new 9850 one, after I pop it in, my first set was 2500@1.25v, didn't even boot, stoped after build DMI and backup CMOS.:yepp: :p:
Hey Achim:) Don't worry brother I am not honing in on you're current misfortune with my statement it applies to One and all:D But seriously guys Please take the advice and test my theory out I really don't need to be right for my own vanity sakes I mean that but what I propose holds true with the Past 3 Current AMD CPU's that I have owned and I think that if enough would be willing to get past the old way of thinking and possibly take this suggestion we may be onto finding out the way this works effectively and efficiently in a much shorter time frame seeing how Phenom User Base has exploded since B3 Release;)
Thanks for Listening..........Campbell:)
I was trying to test this one http://www.rebelshavenforum.com/sis-...;f=29;t=000042Quote:
Originally Posted by Brother Esau
;)
Quote:
Originally Posted by aGeoM
Well then perhaps you may be inclined to test my theory out next go around? Perhaps we need to do as this thread is intended to do Debug Phenom Problems and if that means lowering the Voltage threshold of what not to exceed then so be it and we will be doing our parts so others don't experience the same anguish:up:
Quote:
Originally Posted by aGeoM
Polygon is very well respected by me and I hold his knowledge in high regard but......My intent is to get facts on what is going on and my suggestion is a common sense one ...DO NOT...Run Unnecessary Voltage into a Electronic component when its not needed and you most certainly never hear me saying what I propose will yield Higher Clocks:clap: I Propose Logic through Simplicity Nothing More!
Yes, it was the first thing I realize, on B3, he didn't like voltage at all, when testing 3.2GHz it booted to Windows vCore@default+107%~109% and didn't after it.Quote:
Originally Posted by Brother Esau
I know it was not high volts or HTT, was something else that overcomes my knowledge.
Hmm from what i have experienced with phenoms, they tend to have an upper voltage limit. Above you don't get it stable. So the top-down approach for overclocking will not work. Bottom-up is a long way if you really want to find all lowest voltages. Also knowing the lowest possible voltages does not help if you get in the idle freezing area, which seems to start at a individual cpu frequency.
I guess the fastet way is to test each core separate at say not more than 1.35V for B3's till the system starts to freeze idling and then use the multi of the weakest core.
During my first tests with the 9850BE it looked like the NB requires higher volts with higher cpu frequencies. This was a false impression it only took prime95 longer to fail with lower cpu frequency, so the nb voltage requirement is really independant from the cpu frequency. At 2.9GHz the system was alot more stable with a 2.4GHz NB frequency, but i could not get a stable 2.4GHz nb with a reasonable voltage (stopped at 1.4325V). So I think it's a good idea to test the capability of your nb first.
:2cents:
If someone finds a fix for the idle freezing I'd be glad to hear. :shrug:
I have Experienced no such Issues of Freezing or anything Esle for that Matter since O.C Phenom;) My system Runs 18hrs a day at a minimum:cool:.....Overclocking Minds Since...1986...:usa::surf::usa:
Just to prove my theory that Phenom can overclock with Low Voltage and requires a light and artful Approach, heres a 4hr Prime Run.
DFI LANPARTY UT 790FX-M2R (BIOS 4/15/2008 "Beta")
AMD Phenom 9850 Black Edition "B3"
Tuniq Tower 120
OCZ Reaper HPC (PC2-8500) 5-5-5-18 2X2GB
POWERCOLOR AX3870 X2 CROSSFIRE CATALYST 8.3
Auzentech XPlosion
Areca 1231 ML {Intel IOP 341} ~ 6 ~ 250gb Hitachi Sata II Raid 6 ~2~WD 74gb Raptors ~ Raid 0 ~
Plextor 750A
SilverStone OP1000
CM Stacker STC-T01
Code:>HT Link Control:
HT Link Width......................... - 16 bit
HT Frequency.......................... - 2GHZ MHz
IH Flow Control Mode.................. - Disabled
HT Link Tristate...................... - Disabled
2x LCLK Mode.......................... - Disabled
Unit Id Clumping...................... - Disabled
>CPU Feature:
CPU DID.............................. - 1
CPU FID.............................. - 0C
CPU-NB DID........................... - 1
CPU-NB FID........................... - 06
AMD CPU stepping..................... - P0
>DRAM Configuration:
MCT Memory Timing.................... - Manual
2T Mode.............................. - Auto
Cas Latency Time..................... - 5
Pre Charge Delay (tRAS).............. - 18
DRAM RAS# Precharge.................. - 5
DRAN RAS# to CAS# Delay.............. - 5
Bank to Bank Cmd (TRRD).............. - Auto
TRC.................................. - 23T
TRTP................................. - Auto
Write Recovery (TWR)................. - Auto
Write-Read Command (TWTR)............ - Auto
TRFC0................................ - 195ns
TRFC1................................ - 195ns
TRFC2................................ - 195ns
TRFC3................................ - 195ns
Trdrd................................ - Auto
TrwtT0............................... - Auto
Twrrd................................ - Auto
Twrwr................................ - Auto
CS/ODT Pin Fine Delay................ - Enabled
Bank Swizzle Mode.................... - Enabled
Auto Tweak Performance............... - Enabled
Optimal Performance Mode............. - Enabled
>ODC Control Mode:
DRAM Drivers Weak Mode.............. - Normal
Output Drivers Comp................. - Normal
>Channel A:
CPU On-die Termination.............. - 300 ohms +/- 20%
DQS Drive Strength.................. - 1.00x
Data Drive Strength................. - 1.00x
MEMCLK Drive Strength............... - 1.00x
Addr/Cmd Drive Strength............. - 1.50x
CS/ODT Drive Strength............... - 1.50x
CKE Drive Strenght.................. - 1.50x
>Channel B:
CPU On-die Termination.............. - 300 ohms +/- 20%
DQS Drive Strength.................. - 1.00x
Data Drive Strength................. - 1.00x
MEMCLK Drive Strength............... - 1.00x
Addr/Cmd Drive Strength............. - 1.50x
CS/ODT Drive Strength............... - 1.50x
CKE Drive Strenght.................. - 1.50x
>PWM Settings:
PWM Control.......................... - Enabled
CPU VID Control...................... - 1.23750v
CPU Vid Special Add.................. - Auto
CPU NB Vlotage Control............... - 1.23750v
CPU NB Vid Special Add............... - Auto
DRAM Voltage Control................. - 1.80v
SB PLL 1.2V Voltage.................. - 1.20v
NB Core Voltage...................... - 1.200v
NB PCI-E Voltage..................... - 1.120v
NB HT Voltage........................ - 1.270v
Genie BIOS Settings:
Timing Mode.......................... - Manual
Memory Clock value or Limit.......... - DDR 1066
PCIE 3,4 State....................... - Auto
PCIE 2 State......................... - x2
CPU TLB Cache Fix.................... - Disabled
AMD K8 Cool & Quiet control.......... - Disabled
CPU Clock Ratio...................... - Auto
Spread Spectrum...................... - Disabled
CPU Host/HTT Clock................... - 200mhz
CPU Host/HTT Boot Up Clock........... - 200mhz
CPU Host/HTT Adjustment Gap.......... - 5mhz
PCIE Clock........................... - 100mhz
Bro your chipset voltages are too high. My board ran stable with those at the lowest possible values. :) Four hours of prime95 do not mean that much, I ran prime96 for nine hours at 2.9GHZ/2.2GHz before it failed , 2.8GHZ/2.4GHz failed prime95 after ~13hrs. At 2.9GHz however i had the freezing issues, the setup i primed for hours froze after a few minutes just surfing the web, repeatable.
You plan to go above 2.8GHz? :rolleyes:
During my first testings i first had freezing issues at 2.9GHz with NB speeds below 2.4GHz. I thought i could fix the freezings with an 2.4GHz nb but this turned out to be impossible due to the high voltage the nb would have required.
Looking at my testings with nb at 2.4GHz i think >1.4V for ~30hrs was too much even at a cpu temperature around 60°C. I used the bottom-up-lowest voltage method here and started at 1.3V.
After that test I started to realize I get those idle freezings even at 2.8GHz in winxp 32bit. So I think i'd better tested the nb speed via ref HT increasement with an 11x multi.
I use the bottoms up method also.Quote:
Originally Posted by justapost
I find that drinking Captain Morgan before trying to overclock makes those pesky reboots less painful.
:-P
(Sorry... had to be said.)
I'm at 2.55G using 204x12.5 and Auto.
VCore 1.3 OV'd to 1.31 with a 12.19V supply.
HT on 1.8M
All else on auto.
I'm going to attempt to lower the voltage over a few days to around 1.275. 1.25 has never worked but may be attainable over time is Bro Esau is right about the learning part. I just want to know where the magic is?
Lol, that might also help. ;)Quote:
Originally Posted by keithlm
So is AOD a must when overclocking phenoms? Can you reach the same limits just using bios adjustments? Sorry I didnt see the answer to my original question in the thread
What do you mean chipset voltage is to high? Which setting? If you mean CPU-NB Voltage I set it the same as CPU Vid as suggested by DFI Engineers and have yet to have a issue. Also I find since doig that I was able to kick it down 1 notch with CPU CoreQuote:
Originally Posted by justapost
I will OC more when my cat is better and I have time right now it has to wait!
If you can go down with the cpu voltage after you upped the nb voltage it will fail, but after a longer time. That's what i found with the 9500 on the M3A. NB and CPU voltages operate completely independant, assuming that the cpu temperature does not exceed 60°C.Quote:
Originally Posted by Brother Esau
I have no clue why DFI-Engineers recommend the same settings for CPU-VID and NB-VID. I mean that is the benefit from split power planes. In CnQ if the cpu enters p-state-1 the cpu voltage will drop to 1.05V and the frequency to the half of the stock frequency, while the NB stays at stock frequency and voltage.For 2GHz NB-frequency my 9850BE required 1.175V NB-VID.
But I talked about the four SB/NB ... Voltages at the bottom of the PWM page. My system ran perfectly stable with all those at the lowest possible values, but i have a not so power consuming hd2600xt here.
@Jimmy411: Hmm how (un)usable AOD is (with the DFI board) was posted here a few times. It does not read the correct actual values and applies stock voltages to the cpu and the memory, that causes system hangup's if your already bios tweaked system does not run at those voltages.
You can enable some AutoXPress features via red-button mode whom can not be tweaked via the bios. Also you can easily modify single cpu multis with aod. Otherwise you'd need to tweak the p-state registers of the cpu to archieve the same effect. AOD's stability test and auto overclock function both do not find the idle freezing issue many phenom users get here.
Overclocking via the bios is definately more reliable atm.
Hey Achim, Just wanted to say thanks for the Avatar change!
Lemmy Rocks... :D
I'm buzzed again, but I kinda have to agree with Brother E...
Ya have to be gentle with Phenoms.