AMD Processors
Decrease font size
Increase font size
Topic Title: Overclocking a server MB S4985 Nforce 4
Topic Summary: Partial Success - Winxp ok Win 7 - major issues
Created On: 01/30/2010 06:03 AM
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
View similar topics View similar topics
View topic in raw text format. Print this topic.
 01/30/2010 06:03 AM
User is offline View Users Profile Print this message

Author Icon
ZippA
Lurker

Posts: 12
Joined: 03/11/2009

Hi sorry for the messy post...I just want to share my OC experience overclocking a server MB

I got this server Nvidia nforce4 based Tyan S4985 Quad socket motherboard really cheap and after a few weeks searchingonline shops for a suitable case I bought the CM-810 stacker with dual 120 mm exhaust fan outlets.

CM810 product specs
">http://global.coolerma...com.....te=17&id=13


It's the only towercase that I could find that would fit this motherboard.

Bought it from a CM affiliate shop in NL and paid some 40 euros for shipping to Denmark. AFAIK it's not being produced by CM anymore but they might still have some left in that online shop I bought it from.

I am having some fun overclocking this beast and had some success in windows XP and partial success in Windows 7.

I actually got the board running now in WinXP with two 8384 cpu's I got off ebay and can overclock it to above 3.3 GHz unstable 3.2 stable with two northQ all in watercooling sets. Unfortunately only in WinXP using ntune 3.0 or 2.5. Haven't tried XP64 bit...maybe it will work there as well.

RAM: Got 800Mhz ECC DDR2 ram that was originally SPD'ed to 667 (8 pcs of 1 GB kingston singlerank ECC) which I 'upgraded' to 800 Mhz by repgramming the SPD, otherwise the BIOS would'nt change the mem speed to 800 Mhz. (Used some SPD reprogramming proggy and did the reprogramming one stick at a time- woohoo 667 to 800 Mhz upgrade for free :-))


My water cooling setup is two times the NorthQ 3850... to get them fittet I had to use a dremmel to cut a little of the CM-810 but it isn't visible when the sidepanel is in place.

NorthQ 3850 Review:
">http://www.jonnyguru.c...dul.....ory&reid=86


It works like a charm, and I plan to get hold of two more 8384 Opterons or maybe hold out for the sixcore when I can find a ebay bargain. Only headache would be to fit two extra watercooling blocks like the NortQ thingy's, might have to buy some DIY blocks instead eeewh.

In Windows 7 I could only overclock with clockgen for nforce 4 on a couple off 8218, the program resets the comp. with the 8384 as soon as I try to change the speed of the HTT link.

I could OC the 8218's to around 3 Ghz stable.

Now my problem is that I wan't to OC in windows 7, but the BIOS is crap for OC'ing

You can't tune a single chpset item in the BIOS.

So I have during the last year scavenged the net for all kinds of information that could help in figuring out if I modify the BIOS (fx. to insert a custom option ROM with ability to changenforce4 chipset registers). but no...

Then looked into see if there was some kind of dos program that could be used as part of a grub chainloader so I could mess with the chipset just before launching the win7 OS...

Havn't found anything yet..

So Nvidia's ntune is the only program I can use...(also tried some of the old versions of AOD - AMD OVERDRIVE but can't find a version that supports changing the HTT speed for nforce4, newer versions is a no go) but the support in Windows 7 is horribile...

Newer versions of Ntune locks up windows and I can't remember which of the older versions I got to work (if any... )

Just got it working in winxp32 up untill version 5.00.04 something.. Using ntune version 3.

Maybe I could modify the nvsuoem.ini file to expose more options?? Tips appreciated :-)

Anyways... anybody out there having some tips for me...and yes I know it's a totally weird setup to OC...but it's cool...and expensive

Got the ATI 5870 and a 1200w PSU...

Might post soime pictures at some point...but really I just want to OC nforce4 in windows 7

HEEELP :-D

ps: my first issues with the board somewhat documented here :

http://forums.amd.com/forum/me...atid=28&threadid=91815

Edited: 01/30/2010 at 06:37 AM by ZippA
 01/30/2010 06:20 AM
User is offline View Users Profile Print this message

Author Icon
ZippA
Lurker

Posts: 12
Joined: 03/11/2009

Full system specs as of today:

Motherboard :S4985 MB
">http://www.tyan.com/pr..._SK.....U=600000043


Bios: 3.00 ">http://www.tyan.com/suppo...model=S.S4985-E


RAM: 8GB 800 Mhz ECC kingston 1gb sticks KVR667D2S8P5/1G single rank - SPD modded to 800 Mhz

CPU: 2x 8384 Opteron

GPU: 1x ATI asus 5870 radeon EAH5870
(Also have the EAH4890 and wanted to used it for Directcompute / Cl stuff but I think I will wait for the next Big Nvidia Gforce thing to hit me instead)

PSU: 1200w Monolith X LC1200 v2.9 (Have an extra High power HPC-1200-G14C for my next build)

Watercooling: 2x NorthQ Siberian tiger 3850

Case: CM-810 stacker
http://global.coolermaster.com...etail&tbcate=17&id=13

HDD: 1x intel X-25 SSD and 2x 500 GB seagate 32MB RAID plus some extra SATA HDD's

Monitor: Runnning this on a 27.5'' Hanns-G when I'm operating on it's inside, when not it's used on my Sony 46'' Bravia something.

Edited: 01/30/2010 at 06:26 AM by ZippA
 09/14/2010 02:41 PM
User is offline View Users Profile Print this message

Author Icon
ZippA
Lurker

Posts: 12
Joined: 03/11/2009

Yes!!

I succeeded in getting this board overclocked in windows 7 64 bit.

I installed a Nvidia GeForce 220 GT graphics card and voila I could then install the Ntune program from System Utility version 6.05

I can run the HTT @ 222 Mhz stable.

This gives me 3 Ghz on the two 8384 and 888Mhz on the ddr2 ram with CAS 6 latency.

I have to play around with the RAM CAS latency and the HTT multiplier in order to get higher.

Only issue is that I programmed the ram's SPD to run CAS 5 at 533 Mhz....

I wonder if there's some program that will be able to change the CAS latency as a boot/grub loader on this chipset... Or maybe I can add some options in the .nsu profile

Currently this is what Ntune wrote in the default .nsu profile

[BoardConfiguration]
Version=200
CPU=100f42
MCP=818
GPU=XGI Volari Z7-Z9-Z9s-Z11 v1.11.03

[ClockSettings]
FSBMHZ=222
AGPMHZ=2500
PCIe2MHZ=0
CpuCore0Mul=13.5
CpuCore1Mul=13.5
CpuCore2Mul=13.5
CpuCore3Mul=13.5
CpuCore4Mul= 0.0
CpuCore5Mul= 0.0
CpuCore6Mul= 0.0
CpuCore7Mul= 0.0
TRAS=13
TRCD=3
TRP=3
TRC=13
TWR=3
TRRD=1
TRWT=3
TWTR=2
TWRRD=0
TWRWR=2
TRDRD=1
TREF=0
GPUCOREMHZ0=625
GPUMEMMHZ0=400
GPUSHADERMHZ0=1360
HTMULTIPLIER=4

[VoltageSettings]
CPUVOLTAGE=-1
NFORCEVOLTAGE=-1
MEMVOLTAGE=-1
AGPVOLTAGE=-1
AUXVOLTAGE=-1
CPUFAN=-1
AUXFAN1=-1
HTCPUSPPVOL=-1
HTSPPMCPVOL=-1
NFORCEFAN=-1
AUX1FAN=-1
AUX2FAN=-1
GPUFAN3D0=25

[DeviceRule1]
Device=2
RuleEnable=0
RuleName=Arma 2
ControlElement=Memory frequency
ElementID=16416
InputSource=Memory utilization
SourceID=8224
DataSize=3
Data0=0,0
Data1=32640,0
Data2=65280,0
CurveData0=0.0,0.0
CurveData1=20.0,0.0
CurveData2=40.0,0.0
CurveData3=60.0,0.0
CurveData4=80.0,0.0
CurveData5=100.0,0.0
 09/14/2010 03:10 PM
User is offline View Users Profile Print this message

Author Icon
go_for
Alpha Geek

Posts: 3217
Joined: 01/21/2006

A64Info(v1.62) lets you adjust memory frequency and Command rate, can be set up in startup folder. A64 tweaker also has a wide range of memory setting options. But I doubt they will work in Win 7 64bit. I guess you have already tried clockgen for nforce4.

-------------------------
 09/17/2010 02:32 AM
User is offline View Users Profile Print this message

Author Icon
ZippA
Lurker

Posts: 12
Joined: 03/11/2009

Hi there.

Thanks for your suggestions. I already knew about those programs they only work with the second generation Opterons 82xx series AFAIK, I know a few other programs that can tune timing values on 3rd gen. Shanghai's.


But what I did instead was to reprogram the Ram I got with SPD Tool to report only one value 6 (six) CAS latency. And then Ntune disaster struck me.... Damnit and Aaaargh and so on.

This meant that I could change the Mem. speed from 400 Mhz to 800 Mhz and modify the Mem divider that way.

I actually succeeded in OC'ing the Opties to FSB 237 and also at the same time fiddling with the NB divider (Opty mem ctrl. =PCI bus #18 + 19 dev 3 offset (Dec) 212 bit 0 to 5) getting 3 GHZ on that.

Something borked my Ntune install after the SPD modification and I got the dreaded Ntune freeze shortly after login.

I had to go back to a restore point...and now for the life of it..the Ntune re-installation foobars. I noticed that Ntune stops when it tries to load some ring0 driver.

WHen it worked it almost correctly probed my system (The settings file I pasted above).

Now it creates a sysdflt.nsu file with a lot of binary crap instead.

Did 5 or 6 attempts on installing Ntune from nvidias 6.00 beta, 6.02, 6.05 system utility.. eevery time it freezes after loading some driver (think it's the nvclock64.sys) or something..

Anyhow...I'' do some more research later on...
 11/28/2010 06:27 AM
User is offline View Users Profile Print this message

Author Icon
ZippA
Lurker

Posts: 12
Joined: 03/11/2009

Back again

Managed to overclock using ntune 5.05.54 in windows 7 x64.

A month ago I wiped my OS drive and reinstalled win7. All powersaving features have been disabled in the BIOS and I then installed some version of ntune...I'm running stable 3.037 Ghz with a 225 MHz FSB/HTT. Can reach 3.2 ghz but it's not stable.

If I could figure how to override the CPU VID pwm signal and write firectly to the VRM that I want max VID I might be able to go higher.

I saw some softmods for changing the voltage for gfx cards through writing to the VRM over the ic2/smbus. I got 4x vt1115 sitting on this MB - one for each cpu socket.

Found the specs - but can't identify the ic2 bus address and which registers should be written to in order to override the cpus MaxVid of 1.35 v.

I speculate the reason for eariler screw ups is some conflict between ntune and the nvidia control panel application.




In the Ntune app the system details for the Nvidia Control Panel are 1.4.13.08.
 01/20/2012 04:36 AM
User is offline View Users Profile Print this message

Author Icon
ZippA
Lurker

Posts: 12
Joined: 03/11/2009

OP Back to post a bit about my progress.

A lot of time passed since I last fiddled around with OC this MB - Anyway - I'm now quadrobooting into different windows operating systems - and using windows server 2003 R2 x64 for my current OC OS as I'm still using Ntune (version 5.0.8.6 atm. with nvsuoem.ini from 6.05 )

The audence for my post is probably limited as this is now an obsolotete platform, but nevertheless...

The progress so far is a bit limited but in 2003 x64 I can now OC the HTx5 link to 233 MHz with the NB link set to x11 multi.

This OC gives the 8384 Optys a core speed of 3145 Mhz NB speed@2562 MHz and DDR2 cas5@776 MHz

http://postimage.org/image/3nohec675/


http://valid.canardpc.com/show_oc.php?id=2236322 (OC in WinXP x64)

I can run at HTT link speed @240 Mhz but this will crash some games....(more below HWMonitor dump)

Processor 1 ID = 0
Number of cores 4 (max 4)
Number of threads 4 (max 4)
Name AMD Opteron 8384
Codename Shanghai
Specification Quad-Core AMD Opteron(tm) Processor 8384
Package Socket Fr4 (1207)
CPUID F.4.2
Extended CPUID 10.4
Brand ID 2
Core Stepping RB-C2
Technology 45 nm
TDP Limit 117 Watts
Core Speed 3145.4 MHz
Multiplier x FSB 13.5 x 233.0 MHz
HT Link speed 1165.0 MHz
Stock frequency 2700 MHz
Instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, SSE4A, x86-64, AMD-V
L1 Data cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L1 Instruction cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 4 x 512 KBytes, 16-way set associative, 64-byte line size
L3 cache 6 MBytes, 48-way set associative, 64-byte line size
FID/VID Control yes
FID range 4.0x - 13.5x
Max VID 1.300 V P-State FID 0xB - VID 0x14 - IDD 23 (13.50x - 1.300 V)
P-State FID 0x4 - VID 0x1C - IDD 20 (10.00x - 1.200 V)
P-State FID 0x10E - VID 0x20 - IDD 18 (7.50x - 1.150 V)
P-State FID 0x100 - VID 0x20 - IDD 16 (4.00x - 1.150 V)

Package Type 0x0
Model 84
String 1 0x0
String 2 0xF
Page 0x0
CmpCap 4
ApicIdCoreSize 4
TDC Limit 92 Amps
Attached device PCI device at bus 0, device 24, function 0
Attached device PCI device at bus 0, device 24, function 1
Attached device PCI device at bus 0, device 24, function 2
Attached device PCI device at bus 0, device 24, function 3
Attached device PCI device at bus 0, device 24, function 4

Processor 2 ID = 1
Number of cores 4 (max 4)
Number of threads 4 (max 4)
Name AMD Opteron 8384
Codename Shanghai
Specification Quad-Core AMD Opteron(tm) Processor 8384
Package Socket Fr4 (1207)
CPUID F.4.2
Extended CPUID 10.4
Brand ID 2
Core Stepping RB-C2
Technology 45 nm
TDP Limit 117 Watts
Core Speed 3145.4 MHz
Multiplier x FSB 13.5 x 233.0 MHz
HT Link speed 1165.0 MHz
Stock frequency 2700 MHz
Instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, SSE4A, x86-64, AMD-V
L1 Data cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L1 Instruction cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 4 x 512 KBytes, 16-way set associative, 64-byte line size
L3 cache 6 MBytes, 48-way set associative, 64-byte line size
FID/VID Control yes
FID range 4.0x - 13.5x
Max VID 1.300 V
P-State FID 0xB - VID 0x14 - IDD 23 (13.50x - 1.300 V)
P-State FID 0x4 - VID 0x1C - IDD 20 (10.00x - 1.200 V)
P-State FID 0x10E - VID 0x20 - IDD 18 (7.50x - 1.150 V)
P-State FID 0x100 - VID 0x20 - IDD 16 (4.00x - 1.150 V)

Package Type 0x0
Model 84
String 1 0x0
String 2 0xF
Page 0x0
CmpCap 4
ApicIdCoreSize 4
TDC Limit 92 Amps
Attached device PCI device at bus 0, device 25, function 0
Attached device PCI device at bus 0, device 25, function 1
Attached device PCI device at bus 0, device 25, function 2
Attached device PCI device at bus 0, device 25, function 3
Attached device PCI device at bus 0, device 25, function 4

Processor 3 ID = 2
Number of cores 4 (max 4)
Number of threads 4 (max 4)
Name AMD Opteron 8384
Codename Shanghai
Specification Quad-Core AMD Opteron(tm) Processor 8384
Package Socket Fr4 (1207)
CPUID F.4.2
Extended CPUID 10.4
Brand ID 2
Core Stepping RB-C2
Technology 45 nm
TDP Limit 117 Watts
Core Speed 3145.4 MHz
Multiplier x FSB 13.5 x 233.0 MHz
HT Link speed 233.0 MHz
Stock frequency 2700 MHz
Instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, SSE4A, x86-64, AMD-V
L1 Data cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L1 Instruction cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 4 x 512 KBytes, 16-way set associative, 64-byte line size
L3 cache 6 MBytes, 48-way set associative, 64-byte line size
FID/VID Control yes
FID range 4.0x - 13.5x
Max VID 1.200 V P-State FID 0xB - VID 0x1C - IDD 23 (13.50x - 1.200 V)
P-State FID 0x4 - VID 0x20 - IDD 20 (10.00x - 1.150 V)
P-State FID 0x10E - VID 0x20 - IDD 18 (7.50x - 1.150 V)
P-State FID 0x100 - VID 0x20 - IDD 16 (4.00x - 1.150 V)

Package Type 0x0
Model 84
String 1 0x0
String 2 0xF
Page 0x0
CmpCap 4
ApicIdCoreSize 4
TDC Limit 92 Amps
Attached device PCI device at bus 0, device 26, function 0
Attached device PCI device at bus 0, device 26, function 1
Attached device PCI device at bus 0, device 26, function 2
Attached device PCI device at bus 0, device 26, function 3
Attached device PCI device at bus 0, device 26, function 4

Processor 4 ID = 3
Number of cores 4 (max 4)
Number of threads 4 (max 4)
Name AMD Opteron 8384
Codename Shanghai
Specification Quad-Core AMD Opteron(tm) Processor 8384
Package Socket Fr4 (1207)
CPUID F.4.2
Extended CPUID 10.4
Brand ID 2
Core Stepping RB-C2
Technology 45 nm
TDP Limit 117 Watts
Core Speed 3145.4 MHz
Multiplier x FSB 13.5 x 233.0 MHz
HT Link speed 233.0 MHz
Stock frequency 2700 MHz
Instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, SSE4A, x86-64, AMD-V
L1 Data cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L1 Instruction cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 4 x 512 KBytes, 16-way set associative, 64-byte line size
L3 cache 6 MBytes, 48-way set associative, 64-byte line size
FID/VID Control yes
FID range 4.0x - 13.5x
Max VID 1.250 V P-State FID 0xB - VID 0x18 - IDD 23 (13.50x - 1.250 V)
P-State FID 0x4 - VID 0x20 - IDD 20 (10.00x - 1.150 V)
P-State FID 0x10E - VID 0x20 - IDD 18 (7.50x - 1.150 V)
P-State FID 0x100 - VID 0x20 - IDD 16 (4.00x - 1.150 V)


I did have to change some things in order to attain this new OC limit.

I figured that the CPU's have been binned for different voltages at 2700 Mhz as is apparent above.

This presented me with an issue - Since I had not considered the physical placement of the cpus in the sockets when I first started to set up the system I had the 1.2 volter going into the boot BSP cpu (0) socket and a 1.3 hanging in socket 3.

Switching these two ensured I had a little more headroom. But by looking at the volt's I should also switch cpu 1 with cpu 2 since It would probably give me just a little more juice having the two 1.3 volters in socket 0 and 1.

But it's quite a cable mess and a bit time consuming to do this swapping as you can witness here

<br ">http://postimage.org/image/638vzi53r/

]http://postimage.org/image/638vzi53r/
<br [/L]

Basically what I have been searching for is a way to override the cpu's reported VID's to the Volterra VRMs driving vcore voltage.

Tyan's BIOS does not expose any programmability of the VRM's to the OS (Ntune) so I've been scouring the net for information about the VT1165 VRM and found a lot of discussions about this VRM chip being used to control the vcore for GPU's which gives me some hope.

I've been using HW monitor to probe the devices on the SMBUS interface but have yet to identify the Master VRM chip driving the four slave VRM's. Or if the individual VRM driving each cpu's vcore can be addressed (found) on the SMBUS.

I checked out a google code project derivate of rivatuners vt1165 plugin - and research is ongoing... (found some datasheet's on the volterra chips - but the ones I found don't reveal how to program the VID's in anyway - maybe there is a standard PM protocol that I overlooked, that every VRM chip adheres to??)

The following regulator control capabilities are supported
over the SMBus interface:
. Override the VID code settings to program the output
voltage

Hints for my next steps will be appreciated (Register Data for the VT1165M would be super cool to have and also how to identfy I got the right address forthe VRM).

I also thought about a wire pinmod that would be driving the VRM to supply 1.55 to the opty's. I just don't know if the VID's pins on the Opty/VRM are multiplexed or latched (one time programmed after bootstrapping)

Anyway I have more than one SMBUS and there are some device that I can identify as SPD and some others I can rule out as being the VRM's.

Here's a adress/register dump:

CPUID SMBus Report
-------------------------------------------------------------------------

Binaries
-------------------------------------------------------------------------

HWMonitor version 1.1.8.0

SMB device I/O = 0xA000, address 0x50, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 80 08 08 0E 0A 60 48 00 05 25 45 06 82 08 08 00
10 0C 08 60 01 01 04 03 30 45 3D 45 3C 1E 3C 2D 01
20 20 27 10 17 3C 1E 1E 00 06 3C 7F 80 18 22 0F 00
30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 11
40 7F 98 00 00 00 00 00 00 04 4B 00 00 00 00 00 00
50 00 00 00 00 00 00 00 00 00 00 00 00 00 0B 0F 2D
60 1D C3 02 00 00 00 00 00 00 00 00 00 00 00 00 00
70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0 39 39 36 35 33 34 31 2D 30 30 39 2E 41 30 30 4C

SMB device I/O = 0xA000, address 0x18, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
10 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
20 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
30 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
40 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
50 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
60 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
70 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
80 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
90 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
A0 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
B0 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
C0 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
D0 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
E0 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00
F0 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00 F8 08 F0 00

SMB device I/O = 0xA000, address 0x51, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 80 08 08 0E 0A 60 48 00 05 25 45 06 82 08 08 00
10 0C 08 60 01 01 04 03 30 45 3D 45 3C 1E 3C 2D 01
20 20 27 10 17 3C 1E 1E 00 06 3C 7F 80 18 22 0F 00
30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 11
40 7F 98 00 00 00 00 00 00 04 4B 00 00 00 00 00 00
50 00 00 00 00 00 00 00 00 00 00 00 00 00 08 33 81
60 CC D1 38 00 00 00 00 00 00 00 00 00 00 00 00 00
70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0 39 39 36 35 33 34 31 2D 30 30 39 2E 41 30 30 4C

SMB device I/O = 0xA040, address 0x51, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 36 E2 79 81 E0 00 FF FF FF FF FF FF FF FF FF FF
10 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
20 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
30 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
40 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
50 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
60 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
70 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
80 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
90 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
C0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

SMB device I/O = 0xA040, address 0x19, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
10 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
20 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
30 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
40 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
50 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
60 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
70 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
80 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
90 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
A0 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
B0 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
C0 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
D0 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
E0 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00
F0 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00 F0 00

SMB device I/O = 0xA000, address 0x52, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 80 08 08 0E 0A 60 48 00 05 25 45 06 82 08 08 00
10 0C 08 60 01 01 04 03 30 45 3D 45 3C 1E 3C 2D 01
20 20 27 10 17 3C 1E 1E 00 06 3C 7F 80 18 22 0F 00
30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 11
40 7F 98 00 00 00 00 00 00 04 4B 00 00 00 00 00 00
50 00 00 00 00 00 00 00 00 00 00 00 00 00 08 33 82
60 CC AF 38 00 00 00 00 00 00 00 00 00 00 00 00 00
70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0 39 39 36 35 33 34 31 2D 30 30 39 2E 41 30 30 4C

SMB device I/O = 0xA000, address 0x53, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 80 08 08 0E 0A 60 48 00 05 25 45 06 82 08 08 00
10 0C 08 60 01 01 04 03 30 45 3D 45 3C 1E 3C 2D 01
20 20 27 10 17 3C 1E 1E 00 06 3C 7F 80 18 22 0F 00
30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 11
40 7F 98 00 00 00 00 00 00 04 4B 00 00 00 00 00 00
50 00 00 00 00 00 00 00 00 00 00 00 00 00 08 33 82
60 CC AF 38 00 00 00 00 00 00 00 00 00 00 00 00 00
70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0 39 39 36 35 33 34 31 2D 30 30 39 2E 41 30 30 4C

SMB device I/O = 0xA040, address 0x2D, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
10 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
20 77 7B CE BA 5E 63 4B 39 FF FF FF FF 00 FF 00 ED
30 B0 77 FF AF 4F DE 63 67 FB 7D 85 DF E3 6A 00 00
40 01 C8 0E 00 00 00 00 5F 2D 03 01 44 00 95 00 A3
50 FF FF 00 FF FF FF 00 80 21 70 FF FF 11 00 FF 05
60 75 7A CE BB 5C 63 4A 38 FF FF FF FF 00 FF 00 ED
70 B0 77 FF AF 4F DE 63 67 FB 7D 85 DF E3 6A 00 00
80 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
90 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
A0 75 7A CE BB 5C 63 4A 38 FF FF FF FF 00 FF 00 ED
B0 B0 77 FF AF 4F DE 63 67 FB 7D 85 DF E3 6A 00 00
C0 01 00 02 00 00 00 00 5F 2D 03 01 44 00 95 00 A3
D0 FF FF 00 FF FF FF 00 80 21 70 FF FF 11 00 FF 05
E0 75 7A CD BB 5C 62 4A 3A FF FF FF FF 00 FF 00 ED
F0 B0 77 FF AF 4F DE 63 67 FB 7D 85 DF E3 6A 00 00

SMB device I/O = 0xA040, address 0x48, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 3C E0 4B E0 3C E0 4B E0 3E E0 4B E0 3D E0 4B E0
10 3E E0 4B E0 3E E0 4B E0 3D E0 4B E0 3E E0 4B E0
20 3D E0 4B E0 3D E0 4B E0 3F E0 4B E0 3C E0 4B E0
30 3E E0 4B E0 3D E0 4B E0 3D E0 4B E0 3D E0 4B E0
40 3D E0 4B E0 3C E0 4B E0 3D E0 4B E0 3D E0 4B E0
50 3E E0 4B E0 3F E0 4B E0 3D E0 4B E0 3D E0 4B E0
60 3F E0 4B E0 3C E0 4B E0 3E E0 4B E0 3E E0 4B E0
70 3F E0 4B E0 3D E0 4B E0 3E E0 4B E0 3E E0 4B E0
80 3D E0 4B E0 3D E0 4B E0 3E E0 4B E0 3E E0 4B E0
90 3E E0 4B E0 3F E0 4B E0 3E E0 4B E0 3C E0 4B E0
A0 3C E0 4B E0 3D E0 4B E0 3D E0 4B E0 3F E0 4B E0
B0 3F E0 4B E0 3D E0 4B E0 3C E0 4B E0 3D E0 4B E0
C0 3D E0 4B E0 3F E0 4B E0 3E E0 4B E0 3D E0 4B E0
D0 3D E0 4B E0 3D E0 4B E0 3E E0 4B E0 3D E0 4B E0
E0 3D E0 4B E0 3D E0 4B E0 3D E0 4B E0 3F E0 4B E0
F0 3F E0 4B E0 3F E0 4B E0 3C E0 4B E0 3F E0 4B E0

SMB device I/O = 0xA040, address 0x49, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 3B E0 4B E0 3B E0 4B E0 39 E0 4B E0 3A E0 4B E0
10 3A E0 4B E0 3A E0 4B E0 3A E0 4B E0 3A E0 4B E0
20 3A E0 4B E0 3A E0 4B E0 3A E0 4B E0 39 E0 4B E0
30 39 E0 4B E0 39 E0 4B E0 38 E0 4B E0 3A E0 4B E0
40 3A E0 4B E0 3A E0 4B E0 3A E0 4B E0 39 E0 4B E0
50 3B E0 4B E0 3A E0 4B E0 3A E0 4B E0 39 E0 4B E0
60 3A E0 4B E0 3A E0 4B E0 3A E0 4B E0 3B E0 4B E0
70 3A E0 4B E0 39 E0 4B E0 39 E0 4B E0 38 E0 4B E0
80 39 E0 4B E0 39 E0 4B E0 39 E0 4B E0 3B E0 4B E0
90 3A E0 4B E0 39 E0 4B E0 38 E0 4B E0 38 E0 4B E0
A0 3A E0 4B E0 39 E0 4B E0 3A E0 4B E0 3A E0 4B E0
B0 39 E0 4B E0 3A E0 4B E0 38 E0 4B E0 38 E0 4B E0
C0 39 E0 4B E0 38 E0 4B E0 3A E0 4B E0 3A E0 4B E0
D0 3A E0 4B E0 3A E0 4B E0 39 E0 4B E0 39 E0 4B E0
E0 39 E0 4B E0 39 E0 4B E0 3B E0 4B E0 39 E0 4B E0
F0 39 E0 4B E0 3A E0 4B E0 39 E0 4B E0 39 E0 4B E0

SMB device I/O = 0xA000, address 0x78, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
10 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
20 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
40 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
50 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
60 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
70 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
80 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
90 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
A0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
B0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
C0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
D0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
E0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
F0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30

SMB device I/O = 0xA000, address 0x79, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
10 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
20 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
40 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
50 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
60 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
70 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
80 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
90 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
A0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
B0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
C0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
D0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
E0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
F0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30

SMB device I/O = 0xA000, address 0x7A, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
10 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
20 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
40 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
50 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
60 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
70 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
80 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
90 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
A0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
B0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
C0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
D0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
E0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
F0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30

SMB device I/O = 0xA000, address 0x7B, channel = 0
SMBus registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
10 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
20 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
40 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
50 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
60 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
70 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
80 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
90 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
A0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
B0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
C0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
D0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
E0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30
F0 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30

Edited: 02/08/2012 at 05:34 AM by ZippA
 02/08/2012 05:40 AM
User is offline View Users Profile Print this message

Author Icon
ZippA
Lurker

Posts: 12
Joined: 03/11/2009

I've searched the CPU-Z validator DB for other S4985 overclocks (google -> site:valid.canardpc.com S4985)

And others are hitting 250 Mhz on the board - I am quite sure that my issues are related to my RAM SPD settings - So I'll have to reprogram them in order to be able to hit 250 on the HTT and keeping the ram within their CAS and other timing tolerances.

I've identified Ntune 3 as working in Windows XP SP2 x64 + 2003 R2 SP2 x64 and two others. Anyway I just wanted to post this as a reminder to self
Statistics
112018 users are registered to the AMD Processors forum.
There are currently 0 users logged in.

FuseTalk Hosting Executive Plan v3.2 - © 1999-2014 FuseTalk Inc. All rights reserved.



Contact AMD Terms and Conditions ©2007 Advanced Micro Devices, Inc. Privacy Trademark information