You guys on Vista will get lower HT clocks than on XP. Vista induces a HT wall itself, well known since Kyosen's tests with Barcelona (I've tried it, I know Lightman has aswell). 234-250 is it's best limit.
![]()
Nothing against what you observe but physically that doesn't make sense. None of mine even booted 55C. Maybe your sensors are fudged and what it shows you as 70C is actually 20C.![]()
![]()
100C real boot => no way. Dead chip over 80C real ran, TCC itself shuts down the chip auto at 70C -ish and it has a separate monitoring diode than the core readouts (hottest part). This looks like a case of fudged sensors, so far.
Tell me what your ambient temps are idling?
I'll try it tonight but there is a very large chance of having a dead chip this way. Basic electrical engineering (physics actually) decides that the chip will have a heat limit beyond which it will malfunction and become damaged. AMD has certified this as 70C, so it will be around that region for all these chips no doubt.Anyone can try to increase the temps and see if the overclock is better ?
Cat 8.2 I linked earlier
The chipset drivers are in every Catalyst release. Thanks for the link though.
You can try both.
One setting you can keep for running the 1:2 divider for now and another when the new BIOS with some of these FID/DID options returns, so you can then run 1:2.66 divider with that setting then.
Yeah I tried it on both BE's with that BIOS, no POST (stock everything). I had to do a deep clear CMOS routine or no boot each time. Tried it many times over the last 2 months. If yours does POST then obviously it has it working. I'm waiting for a decent BIOS because that 1.13 BIOS still had many bugs which can make your OC confusing and limited (inconsistent), so a new one where all of you can drop from 9x NB multi will show me whether it's my chip which was hardware limited or the BIOS.As far as the 8x NB, this chip WILL do it, at least AOD and CPU-z says that it does. IIRC, it will go down to 7x as well. I can post some screenies if you want.... Were you trying it on 1.13 Bios?
That's why I've still not tested the HT ref. singled out. My NB is always 9x or above.
I usually run Winbench 2000 Quality test to find the tiny instabilities after real stability testing is passed, and if that passes I first try the Firefox routine and then move on to downloading a video and repeat playing it back using VLC player and going away (6-20 hours). When I come back, that shows me whether the system is undergoing the "idle instability" disorder very well.Is it just me, or does it seem like the NIC drivers have some problems?
If I really want to test stability, seems like opening 4-5 tabs in IE and flipping back and forth or opening attachments/pics will cause a crash if the system is the least bit unstable.
My current setup (2640) doesn't have this problems for well over 35 hours testing now. Looks like it's time to move up a notch.![]()
I haven't experienced any NIC problems BTW, in fact this system gives me the best network connection and ping so far hence why I like to use it over the others. My Q6600 system gives me a very poor net connection for a driver related reason pretty obviously and doesn't let me connect using MSN/Trillian (both brand new OS installs); continuous source of frustration to me.
The servers were too slow, most were downloading at 3.5KB/s for a 195MB file. Server 5 is usually the quickest but that was slow till now (345KB/s now). Package traditionally contains the ATi AVIVO drivers, WDM drivers and the SB600 chipset drivers including for RAID. All the following marked in red:
The BE according to my experience;
-Runs sub 2.4GHz Nb with low volts
-Runs 2.4GHz Nb easily but requires a tad higher volts
-Runs 2.5GHz Nb but with a bigger jump in volts
-Requires high->very high volts and good cooling for above 2.53GHz NB. Sometimes maximum voltage and very good cooling. Phase/DICE/LN2 gets high Nb speeds especially.
Of course, every chip differs but this was with two separate chips.
Super Pi errors are usually memory related at those (low) CPU speeds, unless you've not given it around 1.28V CPU (which it may need).
If your chip can do 250HT stable (any multi), then try these combinations:
250x10x10x9 (IMC will have to be plus 1.4VID)
↑
[and all HT ref. in between]
↓
240x10.5x10x9
Set 1.25VID CPU, 1.416V CPU (1.392V real), 1.35VID Nb and try 240x11x10x9 too. See if it boots and runs.
Yep, thanks for the feedback. Orb works through the On Demand software installed on your PC, so you have to have it running to be connected to online. It acts as a server, so when I link anything from my system using On Demand, you're actually downloading directly from my PC.BTW, Looks like your ORB links don't work unless your machine is running. Gives the message "ERROR: Tell your friend to turn their machine on"![]()
![]()
That's why when I switch the program off it reads computer is off. They should work now... for a while, before I delete both the links and the linked source.
For over 2.45GHz Nb you need higher volts than those (on air). As you've seen before, mine needs 1.312V for 2400 Nb but after many hours that'll freeze and one notch above at 1.325V gets 2400 Nb fully stable.







Reply With Quote

Bookmarks