AMD 5000+ BE with Gigabyte MA78G-DS3H?

[Free888]

Hi,

Anyone is using with the above combination and is there any problem?

I actually need an "urgent upgrade" since my old PC system died. I believe using a good AM2+ board with the cheap 5000+ BE can buy me some time before lower power Phenoms will be out and got to decent prices.

But a tech guy from Gigabyte told me that although the above board should have no problem to support 5000+ BE, there is a chance that I will get a "buggy" chip. He said only 5600+ or above are "bug-free". I cannot find any such claim on the net

 

[dario77]

haven't heard squat about that before...
gigabyte's just got all kinds of stuff to say lately!!

dunno how much i trust it, either. only complaint i ever heard from anyone was that they didn't know how to oc it.

only my two cents...had to post, for i'm plotting the same purchase. though now i'm tempted to wait for 790gx, just for futureproofing.

but as far as dud 5kbe...just don't buy it.

 

[iggybeans]

Buggy 5000+BE processors? Nonsense! I've got two running at 2.1MHz on standard voltage settings in older motherboards. As of yesterday, these processors were going for $87 (at Newegg.com).
A 5000+BE in an AM2+ motherboard is a great low cost option and it makes perfect sense to wait for the 45nm Phenoms.
The motherboard you picked will work fine.

 

[iggybeans]

Sorry, I type too fast. That's 3.1MHz (not 2.1).

 

[Free888]

Thanks iggybeans, I really have the plan for wait for cheaper and more energy efficient Phenoms with this setup.

 

[dario77]

second the motion...move to ratify:
5k+be=theeee chip to get while planning for 45nm.
all agreed?
all opposed?

now...do we really want 780g/sb700 when we're at most 4 weeks from 790gx/sb750...?

 

[Free888]

Well, I can't wait that long really, as my old PC died

 

[Free888]

Built this machine and running at 2.8GHz for now. If it's stable for a week I'll move up to next level

 

[Free888]

I'm running at 2.9GHz now. However, the temps reported in CPUID Hardware Monitor seem to be wrong .... there is a TMPIN2 is 92C (I think it's the CPU) but the core temps are 13C and 19C. I wonder if it's a reporting problem by the CPU or the MB.

FYI, the background temp is around 27-28C I guess.

 

[Free888]

I notice another problem - CPU-Z reports CPU voltage as 1.328V but BIOS reports it around 1.38V .... which is true?

 

[Verillion]

TMPIN2 afaik is a dead sensor, meaning it's not really monitoring anything. 92C would be nuclear meltdown on your mobo =) The operating temperature of this Brisbane core should remain under 65C full load to not shorten it's life.

The voltage issue you are seeing is somewhat strange. I would try to get something else to monitor the voltage and compare it with Bios/CPU-Z. It is not uncommon to have some fluctuation, but anything more than +/- .125 is not very good.

Are there any bios features on that board for temperature management that might be adjusting the cpu multiplier/clock reference? On Asus boards they have an option called "Cool & Quiet" and it is bad news for overclocking.

I run the 5000+ BE with the M3A32 MVP Deluxe w/ Wi-Fi and so far the max OC I have been able to achieve is 3.2ghz, and my ram @ 5-5-5-15 1066 mhz... 24/7 stable. My memory is 2x2GB, and I know the larger amounts of memory the IMC has to address limits your OC.

Good luck on hitting higher numbers, this chip is capable of some crazy OC on air =)

 

[Free888]

Verillion: what voltage are you using for the CPU? Just curious.

 

[Free888]

Also another quick question: what is the stock voltage for 5000+BE?

P.S. Had a "display driver" crash and BSOD yesterday. I wonder if I need to increase my DDR voltage a tad or loosen the timings. I don't feel I am OCing the CPU that much, just up the multiplier to 14.5x. Display driver is Catalyst 8.5 already.

 

[Verillion]

Free-

Currently I am running 1.44V on the Vcore. I have heard a lot of people being able to run less, and still be stable, but I have had no luck at less than 1.44V. I have only been running this chip for about a month, and hopefully after burn-in I will be able to drop it a little bit. However, my temps are great, so I don't worry too much about the voltage.

One thing that I have noticed, is that the Brisbane core seems to be very pick about ram settings when going fast. If you are addressing a large amount of ram, more than 2GB, you will need to find the sweet spot to get the best timings out of both the Ram and CPU.

On you "display driver" crash/BSOD, what was the exact message. Typically problems with CPU/RAM will be MACHINE_CHECK_EXCEPTION BSODs, or if it is during Windows loading, there will be a wider array.

The stock voltage of the 5000+ BE is 1.3V, to the best of my knowledge....

Just as an FYI also, this processor will run stable in the 1.35-1.375 range stable at 3.1. So the jump to 1.4+ is a bit much to get faster than 3.2, but I have not seen any setups that are stable at less than 1.4V for 3.2ghz+.

 

[Free888]

Verillion:

Thanks for all your info!

My BSOD was like this - all of a sudden the screen blinked and Windows says the display driver has recovered from a serious problem. This repeated 2 or 3 times in a row, then BSOD and I believe the culprit is atixxxx something.

I have made some changes to Catalyst (alternative DVI operational mode) later, and so far it's fine. But I suspect that RAM may have also caused the problem. In CPU-Z, the SPD reports 4-4-4-12 settings should use 2.0V - I set 1.9V in BIOS only (but HWMonitor reports 1.95V). I'm using A-Data DDR2 800+ Extreme Edition which is supposed to work in 1.9V-2.1V. Maybe I should be a good boy and set to 2.0V later.

 

[Verillion]

Free,

There is no reason that you shouldn't run the ram at 2.1V. That's what the manufacturer recommends, and typically you can overvolt it 10%-15% and have no problems. With a decent cooling setup over the ram you can go higher, but unless you're really OC'ing the ram, then you shouldn't need to.

As far as the display driver crashing, I would just ensure that you have the latest driver. If you are already using the latest driver, when was it released? If it is a fairly new release, sometimes rolling back to the next most recent version is helpful, as sometimes the QA department lets a driver with a few bugs get by, and until many people complain, they won't say anything about it!

I have read a lot of good things about A-Data ram, so if you put the voltage up to 2.1, or 2.08 (if you may be worried about the difference between bios and HWmonitor) I would almost 100% rule it out of the equation.

Also, don't be afraid to get this CPU up another couple hundred of megahertz. Just make sure your temps are good (I use coretemp, very lightweight and accurate for core temps) and keep trying different settings =) However, if you BSOD a lot in the process, you will trash your Windows partition. Over the course of the last month, I have BSOD'd a couple hundred times, and I'm starting to notice my Windows not performing as fast as it did.

I am planning on getting a cold case of beer and using this new Crucial 512MB stick of Ram that I got in the mail yesterday to hit some new highs on the processor, then reloading my machine with my 24/7 OC of 3.2ghz, with my 2x2GB set of G.Skill (F2-8500CL5D-4GBPK) Ram running at 5-5-5-15 @ 1066.

 

[Free888]

Funny thing is, I just downloaded CoreTemp 0.99 today and found that my core temps are like 7-15C ... maybe this board doesn't give accurate readings in Windows. I did see it give just below 40C in BIOS for the CPU.

 

[Verillion]

Free-

Good point to bring up, why the difference in readings? Well after exhaustive research on my company time (WOOT) I've read quite a few articles, and now I'm a true forum warrior on the topics of temperature readings!

For Core temps read by coretemp:

AMD chips report the temperature by a special register in the CPU's NB. Core Temp reads that register and uses a formula provided by AMD to calculate the current temperature.

The formula for the K8 is: 'Core Temp = Value - 49'.
The formula for the K10* is: 'CPU Temp** = Value / 8'.

So, the temperature readings in the BIOS, and *most* programs are read from a different analog diode, on the underside of the CPU socket. This temperature is not near as important as the CPU core temps. So when AMD says "Keep it under 75C for longevity" for example, they are talking about Core Temps.

If anyone has good disproving material please post =)

EDIT: My "CPU" temp is currently 42C seemingly all the time. That again is at 1.44V in case you don't want to scroll.

But... as an FYI, I've seen the "CPU" temp as reported by Everest, PC Probe II, and others I've found totally unreliable. I took off the integrated heat sink, and lapped my Asus 92mm Silent Square EVO and the reported "CPU" temp actually went up, although the cores went down by 4C. Go figure

 

[Free888]

New developments:

Upped the multiplier to 15x this morning, default FSB and core voltage. Upped the DDR voltage to 2.0V.

All seem fine until I run the Prime95 test ... after 5 mins or so, one of the "worker threads" have ILLEGAL SUMOUT warnings.

Maybe I need to up the core voltage a tad even for 3GHz

Incidentally, found a new toy to play with, called OCCT: http://www.ocbase.com/perestroika_en/
It can both monitor and "torture" the PC quite well, it seems.

 

[Free888]

Upped the voltage to 1.35V and run the default test in OCCT, stable. During the test (the CPU is stressed to be 99%+ utilized), it reports my core voltage as 1.39V. When idle, it reports 1.34V. I suppose the different voltages are due to AMD Cool and Quiet kicking in.

BTW, I'm running the HD3200 onboard graphics only .... maybe when I get a good "gaming" card later, the CPU load won't need to be as high as those torture tests and be stable

 

[Verillion]

Upped the voltage to 1.35V and run the default test in OCCT, stable. During the test (the CPU is stressed to be 99%+ utilized), it reports my core voltage as 1.39V. When idle, it reports 1.34V. I suppose the different voltages are due to AMD Cool and Quiet kicking in.

BTW, I'm running the HD3200 onboard graphics only .... maybe when I get a good "gaming" card later, the CPU load won't need to be as high as those torture tests and be stable

Cool and Quiet = Bad for overclocking. It will make your CPU unstable, as the voltage varying is not a good deal. Turn this off and you'll be able to get 3.2 and be happy all day =)

 

[Free888]

Cool and Quiet = Bad for overclocking. It will make your CPU unstable, as the voltage varying is not a good deal. Turn this off and you'll be able to get 3.2 and be happy all day =)

Thanks for the tip, might try that later.

 

[Verillion]

Yeah sorry for not checking over the weekend, but I hardly troll the forums when I'm not at work. Good luck with getting the blackie a bit faster =)

 

[Free888]

Well, I can't get this baby to stable OC to 3.1 GHz even with 1.4V for the CPU. (I use OCCT for testing) My Ram is run at 400MHz 4-4-4-12 2T, maybe that's a problem, but I followed the Ram specs.

So I have backed down to 1.35V and 3 GHz and be happy with it, for now. Since it's a new PC for both work and play .... better not risk too much at this time

Waiting to get a 4850 or 4870 later and this system should be enough to play games

 

[Guest]

Hallo,

I´m using same mobo (with the last bios) and cpu and I have a small problem - AMD overdrive doesn´t show temp of cpu. BIOS shows temps OK.
I need some advice how to check temp in windows?

Thanks