If you attach any minidumps back, I'll take it a look at them when I can. ;)
If you attach any minidumps back, I'll take it a look at them when I can. ;)
I renamed it to .txt, couldnt upload it otherwise. So rename it to .dmp when you get it. This is just one of today.
Thx in advance
K, I found a site where all those error codes are listed.
As far as I remember I get these, some multiple times: 0x1e, 0x1d, 0xc4.
Looks like it's bad driver stuff although Ive no clue what driver really. And still I dont understand why a higher clocked CPU might cause this sooner than a lower clocked CPU:shrug:
i think drivers crash first because they are very closely related to hardware..
In the past four months I've managed to Build 4 790FX MOBOs. The ASUS, Gigabyte and two DFI Models. The DFI models have died, having memory issues (GSKILL) in all built systems. DFI seems to only have a problem with it, then it would not boot on the first cold start, had to reboot, just to run it. The LED works if you have the Phoenix codes manual that lists the meaning of '88'. The other ASUS and Gigabyte 790FX boards are still running very might I add. Sorry DFI just stating the Facts.:down:
If it means anything AMDkid1 my DFI was defective on arrival. Not dead since it sorta worked, but certainly not right :rolleyes:
Hopefully the replacement works fine.
@ rammsteiner: no i think not bugged drivers will error at first if overclocked too high because of their hardware relation.. otherwise you would get errors even at stock speed.. thats what i can think of not sure really..
@ amdkit: mine runs fine with gskill..
260~262 with CPU=x11; HTT/NB=8/8.Quote:
Great, yeah, you have one of the better Phenoms around. What was max HT on the DFI with low NB/CPU Multi?
I wonder whats happening with the 3GPU setup and the lower oc
Me too lol..., 3-GPU's CFX are reported to work well performance wise in Intel X38 chipsets, not with AMD 790FX chipset, I tested in both MSI/DFI boards, and with MSI I had more troubles for Cat 8.3 recognise the 3-GPU's for enabling CF, it have 4 PCIE slots, bridge connections order depends on PCIE slots used, eg. PCIe1-PCIe3-PCIe2 or PCIe4.
The lower OC, I hope that's BIOS NB/HT 2250MHz limitation, need some feedback from regular Phemons users with this board, or my board is defective in some way. :(
ATM I'm playing with an 5000+ BE, found some Mem divider change at some CPU multi's.
In this case I only manualy changed CPUFID from Default (13) to 15, and Memory timingns to EPP values (CL4 4-3-5 2T) all the other settings are default.
Well I bought this Phenom for Bios Testing so I will do my part to see whats going on with all of this but its going to take some time to get up to speed so I will contribute when its available on my end anyways;)
24.14 (64bit) seems to work.. will test further with your chip be :D
I checked it out, it's almost certainly a software driver but I couldn't get details on it since the actual file was corrupt (incomplete details). :(
Some notes on stress testing to keep in mind:-
*In XP/Vista 32b, 2GB installed, nothing in background, not even AV, I can never run plus 1450MB with any stress test, it'll fail at stock or just not run.
*If you start stress testing reserving an area of memory and then you open applications which try to access that reserved space, you will very likely start getting errors in that stress test, even though nothing hardware wise is wrong (even BSoDs). ;)
OK ...Need some advice for my First Vista 32 Bit install on this Board Please:)
Whats the Story with Installing NET Framework on a Fresh Vista 32 Bit Install so that I can Install CATALYST 8.3 ????? Does Vista have NET included into the O.S or is it a separate Installation required like Windows XP????
Vista has .net 2 and .net 3 already installed. Nothing you need to do there, just install the drivers and go.
Wow thats cool:D Hows about some advice on Vista in general? Is there still the Issue with it consuming a large portion of HDD space for what ever reason?
Not sure about the issue, wasn't even aware of it actually :shrug: I have 250GB so I don't care much :D
I am using about 38GB, that is running vista ultimate 64 bit (which I'm sure ultimate takes more), office 2000 installed, 3.5GB game installed, a couple gig or so of other programs installed, some downloaded files...
Yeah vista takes more than xp by quite a bit, but it IS a bigger OS. Also, someone here reported getting some more HD space available after installing SP1, maybe there is a glitch in pre-SP1 vista in space reporting? I don't know for sure :shrug:
Shoot I am referring to something that was a issue quite a while ago like last year when it first became Public Market
Honestly Brother,
To me its about the same as Xp in as far as installation.
Runs some games like crap. Besides that it works fine, does like 4g though. Seems to run allot smoother with more memory. Not sure if Vista 32 will see 4g though. I have Vista 64.
You have done a great job thus far and look forward to your Phenom posts.
I'll have a phenom as soon as the B3 show up or the tri-core with my DK M2RS :)
Thx a lot for checking KTE.
I did a complete fresh install on my 2nd Raptor (had it only plugged in comepletely new, didnt even format lol). Right after I installed .NET 2.0, SB600 drivers from DFI site, went to MS page and did all updates (except for IE7, I hate that. Also deselected Outlook updates, dont use that). Then installed GPU and sound drivers.
After that, Prime95 25.5. OC'd CPU to 16x219 and ran Prime95. And it's still running:shocked: . So most likely it was indeed faulty software stuff then. It's running 2.5 hours now, not super long so Ill keep it going over night. But it didnt last Prime95 so long in days so looks fine untill now.
To examine the issue... D9's not dieing, CPU looks to be fine. Same with mobo then, BIOS 1/30 most likely didnt corrupt the BIOS chip then. I start to think more and more it's due my RAM OC attempts. I had to repair Windows like three times a day due to corrupted/missing files (like NTLDR etc) after attempts. One time just as I pressed enter to log in I received a warning about corrupted registry. But didnt notice anything from that at that moment, but that could be a good candidate too for all the crap. But Ill see tomorrow morning if it's still going.
After that move a few files from old HDD to new HDD, install some games, OC to 14x251 RAM 1:1 4-4-4 again and have some fun. Ill just forget about running ram 1:1 293 then:rolleyes:
...
Still I think it's the friggin Drive Strengths:p:
Found this over at OCW. 9600 BE to 3.25ghz on air. Wonder what the secret sauce was.
http://my.ocworkbench.com/bbs/showth...threadid=72267
That Dude so stole my Phenom 9600 BE:slapass: :slap: ....Bastage!:D
z0mfg, I got a BSOD on the Frsh install after 4 hours of Priming:confused: ... When I was asleep:shakes:
Debug said this:
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\WINDOWS\Minidump\Mini032608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.070321-2337
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
Debug session time: Wed Mar 26 00:03:21.421 2008 (GMT+1)
System Uptime: 0 days 3:53:28.259
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Loading Kernel Symbols
.................................................. .................................................. .....................
Loading User Symbols
Loading unloaded module list
..................................................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffadb9040f938, 0, fffff97fff0d9508, 2}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!xxxReadPostMessage+2da )
Followup: MachineOwner
---------
1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffadb9040f938, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff97fff0d9508, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: fffffadb9040f938
FAULTING_IP:
win32k!xxxReadPostMessage+2da
fffff97f`ff0d9508 8b4708 mov eax,dword ptr [rdi+8]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffffadf9040f5d0 -- (.trap 0xfffffadf9040f5d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8002acf560 rbx=fffffadf9040f720 rcx=fffffadf9c5b7110
rdx=fffffa80013546a0 rsi=0000000000000001 rdi=0000000000000000
rip=fffff97fff0d9508 rsp=fffffadf9040f760 rbp=fffffadf9be34ed0
r8=fffffa8002acf560 r9=500026a8d4000000 r10=500026a8d57e0004
r11=fffff97ff7ba0280 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
win32k!xxxReadPostMessage+0x2da:
fffff97f`ff0d9508 8b4708 mov eax,dword ptr [rdi+8] ds:0010:00000000`00000008=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800010a5c1c to fffff8000102e890
STACK_TEXT:
fffffadf`9040f4f8 fffff800`010a5c1c : 00000000`00000050 fffffadb`9040f938 00000000`00000000 fffffadf`9040f5d0 : nt!KeBugCheckEx
fffffadf`9040f500 fffff800`0102d459 : 00000000`000007ff fffffadf`9b94cbf0 fffff800`011b4f00 00000020`9d92f628 : nt!MmAccessFault+0x435
fffffadf`9040f5d0 fffff97f`ff0d9508 : fffffa80`01406d80 00000000`00000000 fffffa80`01406d80 fffffadf`9040f930 : nt!KiPageFault+0x119
fffffadf`9040f760 fffff97f`ff0d6c86 : fffffa80`01406d80 fffffadf`9040f930 00000000`00000000 00000000`00000000 : win32k!xxxReadPostMessage+0x2da
fffffadf`9040f7e0 fffff97f`ff05c22c : fffffadf`00000001 fffffadf`00000001 fffffa80`00000000 00000000`ffffffff : win32k!xxxRealInternalGetMessage+0x439
fffffadf`9040f8a0 fffff97f`ff0161df : 00000000`00000000 00000000`00000000 fffffadf`9040fcf0 00000000`00000004 : win32k!xxxDesktopThread+0x4e0
fffffadf`9040fc10 fffff97f`ff0a3800 : 00000000`00000004 fffffadf`9b94cbf0 00000000`00000000 00000000`00000022 : win32k!xxxCreateSystemThreads+0xba
fffffadf`9040fc40 fffff800`0102e33d : 00000000`00000002 00000000`00000000 fffffadf`9b94cbf0 00000000`00000020 : win32k!NtUserCallOneParam+0x3c
fffffadf`9040fc70 000007ff`7c7d802a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
00000000`0085ffa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff`7c7d802a
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!xxxReadPostMessage+2da
fffff97f`ff0d9508 8b4708 mov eax,dword ptr [rdi+8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!xxxReadPostMessage+2da
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310
FAILURE_BUCKET_ID: X64_0x50_win32k!xxxReadPostMessage+2da
BUCKET_ID: X64_0x50_win32k!xxxReadPostMessage+2da
Followup: MachineOwner
---------
1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffadb9040f938, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff97fff0d9508, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: fffffadb9040f938
FAULTING_IP:
win32k!xxxReadPostMessage+2da
fffff97f`ff0d9508 8b4708 mov eax,dword ptr [rdi+8]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffffadf9040f5d0 -- (.trap 0xfffffadf9040f5d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8002acf560 rbx=fffffadf9040f720 rcx=fffffadf9c5b7110
rdx=fffffa80013546a0 rsi=0000000000000001 rdi=0000000000000000
rip=fffff97fff0d9508 rsp=fffffadf9040f760 rbp=fffffadf9be34ed0
r8=fffffa8002acf560 r9=500026a8d4000000 r10=500026a8d57e0004
r11=fffff97ff7ba0280 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
win32k!xxxReadPostMessage+0x2da:
fffff97f`ff0d9508 8b4708 mov eax,dword ptr [rdi+8] ds:0010:00000000`00000008=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800010a5c1c to fffff8000102e890
STACK_TEXT:
fffffadf`9040f4f8 fffff800`010a5c1c : 00000000`00000050 fffffadb`9040f938 00000000`00000000 fffffadf`9040f5d0 : nt!KeBugCheckEx
fffffadf`9040f500 fffff800`0102d459 : 00000000`000007ff fffffadf`9b94cbf0 fffff800`011b4f00 00000020`9d92f628 : nt!MmAccessFault+0x435
fffffadf`9040f5d0 fffff97f`ff0d9508 : fffffa80`01406d80 00000000`00000000 fffffa80`01406d80 fffffadf`9040f930 : nt!KiPageFault+0x119
fffffadf`9040f760 fffff97f`ff0d6c86 : fffffa80`01406d80 fffffadf`9040f930 00000000`00000000 00000000`00000000 : win32k!xxxReadPostMessage+0x2da
fffffadf`9040f7e0 fffff97f`ff05c22c : fffffadf`00000001 fffffadf`00000001 fffffa80`00000000 00000000`ffffffff : win32k!xxxRealInternalGetMessage+0x439
fffffadf`9040f8a0 fffff97f`ff0161df : 00000000`00000000 00000000`00000000 fffffadf`9040fcf0 00000000`00000004 : win32k!xxxDesktopThread+0x4e0
fffffadf`9040fc10 fffff97f`ff0a3800 : 00000000`00000004 fffffadf`9b94cbf0 00000000`00000000 00000000`00000022 : win32k!xxxCreateSystemThreads+0xba
fffffadf`9040fc40 fffff800`0102e33d : 00000000`00000002 00000000`00000000 fffffadf`9b94cbf0 00000000`00000020 : win32k!NtUserCallOneParam+0x3c
fffffadf`9040fc70 000007ff`7c7d802a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
00000000`0085ffa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff`7c7d802a
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!xxxReadPostMessage+2da
fffff97f`ff0d9508 8b4708 mov eax,dword ptr [rdi+8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!xxxReadPostMessage+2da
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310
FAILURE_BUCKET_ID: X64_0x50_win32k!xxxReadPostMessage+2da
BUCKET_ID: X64_0x50_win32k!xxxReadPostMessage+2da
Followup: MachineOwner
---------
Does this mean it's win32k.sys this time? And how to fix it? What does it do? Or is it csrss.exe?:confused:
After two weeks of qx6850 i'm back on my phenom system now. And as other reported earlier it feels snappier at 2.3GHz than an qx6850 at 3.0GHz even if it looses all benchmarks.
Anyway, I tried to optimize the memory. Had 4-4-4-12@1066@2,3V working on the intel system. Now on the DFI/Sapphire the minimum i can set in the bios is 4-5-5-16. With memset I can optimize that to 4-5-5-15 that's it.
I ran hdtach and hdtune on winxp32 sp2 and sp3rc2 with two WD 500GB RE2 HD's in Raid0 . Both get better results that the same hd's as raid0 in the p5k-e with an qx6850, well the burst max is better on the Intel system but the average is higher on the AMD machine.
I'll have this setup running for this week and I can do further raid testings if needed.
AMD
http://www.abload.de/img/hdtunez7n.jpg
Intel
http://www.abload.de/img/hdtuneerz.jpg
AMD
http://www.abload.de/img/hdtachj06.jpg
Intel
http://www.abload.de/img/hdtachbu2.jpg
CrystalMark HDD:
AMD
24020 Pts.
Intel
16995 Pts.
Next thing is the RightMark MT test, check those screenies, cores 1 performs more then twice as fast as the other cores.
Ganged - Unganged
http://www.abload.de/thumb/rightmark-gangedwyp.jpghttp://www.abload.de/thumb/rightmark-ungangedo80.jpg
Also I tried to run the HT at 2 GHz (10x) with CPU multi 13 and NB multi 11. But CPU-Z reports it is running at 1.8GHz and Memset calculates the NB speed wrong in that case. If I set it to 1.8 GHz memset still calculates a wrong NB speed (should be 2.2GHz).
http://www.abload.de/thumb/setup-ht2xly.jpg
EDIT: Above testings where done with the latest stable dfi bios from jan 08. Will do some 3850 testings today and try the beta tomorrow to see if some of my issues are gone.
@ justapost: nice results!!
I'm totaly stuck.
Situation: DFI LanParty UT 790FX-M2R / AMD phenom 9500 2,2Ghz.
When i did give my bios the optimized settings and i do 2 crements HTT to above, there is an O/S-freeze.
The only thing to do was push the reset-button. The tlb fix enabled but the freeze still goes on.
More Vcore doesnt matter.
RAM-divider at the lowest..
(everything on stock)
Is there someone who Please give me one suggestion?
What bios version are you using? Sounds like an old bios related problem.
I'm using BIOS 6.00PG 12/11/2007 original.
I'd update to the latest stable bios from Jan 08.
Have not yet played much with the ref HT cuz i have an be but 220MHz was no problem.
Here's an example:
CPU Multi 12x
NB multi 9x
HT multi 9x
ref HT: 220
boot ref HT: 205
CPU Voltage: 1,4V
SB Voltage: 1,3V
NB CPU V: 1,29V
NB PCIe V: 1,16V
NB HT V: 1,32
Mem at 800 mode 5-5-5-15 2,12V ganged or unganged.
Everything else stock or auto.
EDIT: I recommen using a lower CPU multi and lower CPU voltage first.
I've been lurking here for a while. Just changed out my Asus MVP for the DFI M2R after the Asus spontaneously combusted and burnt both itself and one of the 3870s I had.
Anyway, Vista is pretty cool. I just built up a new 780G machine with it (my daily desktop), also brought the DFI 790FX up on 64 bit initially as well (my gamer). 32 bit for me for now. I may move the gamer back to 64 bit, but there are still a touch too many glitchy things with 64 bit that I found. I was running 64 bit on the Asus, and brought it up first with the DFI. It is definitely STABLE like a rock, but...big but, there are still some driver issues here and there for me at least. 64 bit has many things that run in kernel mode that disagree with certain drivers (like my sound card for one!), and also disagreed with 3 way Crossfire initially. I'm sure it will iron itself out over time, and I will definitely go back to 64 bit for the gamer!
32 Bit didn't have those issues.
As far as Vista goes, I kinda like it. I shut off 50% of the dopey services they have in there, and changed lots of the user interface stuff, and now its definitely livable, and pretty snappy. I do like Aero quite a bit too.
blackviper.com has a nice list of services that can go in the trash heap, I used his list as somewhat of a reference, but made some other changes too.
I have a hardware firewall, so I killed EVERY SINGLE dopey security service that microsoft jammed in there. Way too many. UAC, defender, security center, firewall, security alerts, crypto, key management, all the IPV6 crapola, etc etc. I took back nearly 400MB of memory when I was done killing services, and it ran better too.
Thing runs great now. Very stable.
Check out what this guy was able to achieve with this board and a phenom!
http://my.ocworkbench.com/bbs/attach...7&d=1206502762
yeah these numbers go round the world at the moment :D
thats the headroom we'd want for all phenom but primestable and without tlb-patch and with x64-os as well..
phenom @ 3,2Ghz = :love: :banana:
http://www.xtremesystems.org/forums/...88&postcount=7
Can anyone comment on this? Just here is fine, but why isnt the CPU stable at 14x251 anymore (it has been) but is it at 14x249 now? Doesnt make much sense:confused:
I'm picking my gear up tomorrow.
I will report asap when i got things up and running.
What bios must i flash, 30 jan 2008?
Any recommendations on OC-ing the BE settings and stuff?
THX guys.
Thx undersea,
Now using 3/07. Upgraded from 1/30 with latest winflash from the DFI site with "Clear CMOS" and "Update All" flags set. Worked flawless.
2/12 seems to use an older (vers 2) raid-rom so i skipped it.
3/07 updates the Raid Rom to version 3.0.1540.30, 1/30 had 3.0.1540.21.
I allways use an xp install cd with driver packs stuff integrated, so i used the sb600 drivers from diver packs. Version of "ATI AHCI Compatible Raid Controller" and "ATI RAID Console" is 2.5.1540.39 from 03/06/07 here.
HD-Tach results
3/07 - 1/30
http://www.abload.de/thumb/hdtachp9k.jpghttp://www.abload.de/thumb/hdtachj06.jpg
Still no better options than 4-5-5-16 in 1066 mode with that bios.
But it can run at 615MHz with 5-5-5-16 and 2,31V (bios). :)
http://www.abload.de/thumb/rm615gangedva6.jpghttp://www.abload.de/thumb/rm615unganged8e5.jpg
The power consumption still raises around 20W AC if i plug in an usb memory stick. An USB mouse does not trigger a higher load btw.
Can be there is an difference beside colors between the sapphire and the dfi version. Does an DFI user have an power meter and can check if his mobo behaves like mine?
Been with my cat of 16 years thats dying past few days:( Can some of you post some Bios setting for Overclocking Phenom very mildly maybe 2,4ghz at first with some decent Ram Bandwidth and some pointers for me in general with Bios set up with this thing screen shots of Bios would be nice guys:)
@BrotherEsau sry bout your cat, that can hurt more than expected.
About ocing the phenom. My 9600BE requires
0.7V CPUV and 1.0625V CPU-NBV for 2,5x200 / 9x200
1.175V CPUV and 1.0625V CPU-NBV for 12x200 / 9x200
1.21875V CPUV and 1.0625V CPU-NBV for 12,5x200 / 9x200
1.375V CPUV and 1.3V CPU-NBV for 13x200 / 11x200
those results primed for 10-12hrs at least.
max i could get was ~2650GHz atm with ~1.425V CPU.
So at stock 1.25V CPUV and CPU-NBV you should be save till 2.5-2.55GHz.
I used most of your 6400 bios settings at the beginning, only lowered nb and sb voltages to the minimum.
I found that it's better to use the CPU multi setting than the CPU FID/DID, FID's did not work for a 13 multi.
If you lower the nb multi (NB FID + 4 with NB DID 1) make sure you also lower the ht multi cuz he can't be higher (by k10 design).
To disable the TLB-Fix enable TLB-Caching in DRAM-Config section.
I'm away from the system atm, can post bios screenshots tomorrow if nobody did.
Thanks for the positive words guys I appreciate it!;) Marshall is doing better 2day and will be taking him to get IV Drip of Vitamin /Minerals /Amino Acids /Anti Oxidants / Fluids to Re- Hydrate him so he can fight whats going on with him. Its my firm belief the drugs they gave him had bad negative side effects:mad: and I will get him treated the proper way through Nutrition as it all starts there regardless of what modern medicine says!:up:
Got the gear installed.
installing OS is a diffent story
Vista 64 HP on raid 0 2 x raptor no go.
Flashed to latest official bios from dfi.
setting up an array goes fine it detects the array at startup.
when installing OS it sees no drive array???
in bios sata is set to raid
what is going on??
You probably need a driver like with XP you needed a disk when using raid. Might need to put it on a flash drive though... I really am not sure how to go about it.
although my time is limited today what I would suggest is that you go to DFI download site and get the 002 Revision Raid Zip Package as it is required with Installing Raid with updated SB600 Raid Rom in newer Bios if you already have that and are having problems then I don't know what to tell you as I use a Raid Controller and don't bother with onboard Raid for quite some time now:clap:
Yes i'm up and running.
I did make a RAID driver disk only i put all filles in a directoy.
Vista could not see the drivers.
Made a new disk with only Visat 64 drivers on it.
Im happy running vista on raid 0. Only the preformance is a bit a bummer.
Average 108 burst 183 MB/s.
Hi guys, finally I managed to do 11x250 @HTT/NB x9 in this board, not quite stable, but I'd been playing AAO for 3h, zero problems.
To get the system to boot I'd to set CPU HTT boot @250, and manually set HTT to 1800MHz (auto doesn't boot, C1 error).
http://img413.imageshack.us/img413/2721/dfi250sk2.jpg
Raid benching in Vista X64 (non SP1) with the SB600 controler, see Sig for HDD info.
http://img413.imageshack.us/img413/786/hddbenchpb3.jpg
PS. Hope for your Cat's recover, with good food, Brother.
Your raid setup seems fine compared to mine. (see post above you)
Is that because of your HDD's being SATAII and my Raptors are SATA1
Can be, the SATA/RAID rom in your bios 3-07 is the same one as mine 3-12.
very nice raid numbers indeed..
@Campbell, non native english speaking me thought your cat already died. ;)
@aGeom: Impressive raid results indeed, what raid drivers version do you use?
And thx for the boot ref note, with CB Tracers i managed to boot at 280MHz but I had to reduce the HT and NB multi to 7-8 but I can run mem at 1066 like speed with 4-4-4-12 timings now.
Cam, man, good luck with your cat there :)
aGeoM, beware, those temps are actually in the 45's idling :yepp:
But tell me.. where the heck did you get that wallpaper from, I've been after it for eons :confused:
Mind passing it over here for my Phenom system too please :D
Also with 4-4-3, what bw are you getting?
No actually Marshall has improve dramatically since 2 days ago:) I took him to the Emergency Animal Hospital after the Vet had him on IV and they have continued the treatment over night and he is Eating like a champ and has perked right up when I called last night at 11:00PM ;) I have to pick him up in about 2hrs and take him to the Vet again for updated check up but the Vet said in addition to me that Marshall has made a big improvement :up:
thats good news indeed..
Here are some modest bios settings first
CPU 2.4GHZ
NB 1.8 GHz
HT 1.8 GHz
MEM 533 MHz 4-5-5-16
SB and NB voltages might be too low for your 3870 X2 crossfire setup, not sure about your memory also. 5-5-5-16 at 2.12V are save i guess.
Now with a higher ref HT (225MHz)Code:Genie Bios Settings
===================
Timing Mode Manual
Memory Clock value or Limit DDR 1066
PCIE 3,4 State Auto
PCIE 2 State x2
AMD K8 Cool&Quiet control Disabled
CPU CLock Ratio 12x
Spread Spectrum Disabled
CPU Host/HTT Clock 200MHz
CPU Host/HTT Boot Up Clock 200MHz
CPU Host/HTT Adjust Gap 5MHz
PCIE Clock 100MHz
DRAM Configuration
------------------
DCTs Mode Unganged
MCT Memory Timings
MCT Memory Timing Manual
2T Mode Auto (Enabled)
CAS Latency Time 4 CLK
Precharge delay (tRAS) 16 CKL
DRAM RAS# Precharge 5 CLK
DRAM RAS# to CAS# Delay 5 CLK
Bank to Bank Cmd (TRRD) Auto (4 CLK)
TRC 24T
TRTP Auto (2 CLK)
Wrtite Recovery (TWR) Auto (8 CLK)
Write-Read Command (TWTR) Auto (7 CLK)
TRFC0 75.0ns
TRFC1 75.0ns
TRFC2 75.0ns
TRFC3 75.0ns
Trdrd Auto (2 CLK)
TrwtTO Auto (6 CLK)
Twrrd Auto (0 CLK)
Twrwr Auto (1 CLK)
CS/ODT Pin Fine Delay Enabled
TLB Cache Mode Enabled
Bank Swizzle Mode Enabled
Auto Tweak Performance Disabled
Optimal Performance Mode Disabled
ODC Controll Mode
DRAM Drivers Weak Mode Normal drive
Output Driver Comp. Auto
HT Link Control
---------------
HT Link Width 16 bit
HT Link Frequency 1.8 GHz
IH Flow-COntrol Mode Disabled
HT Link Tristate Disabled
2x LCLK Mode Disabled
UnitID Clumping Disabled
CPU-Feature
-----------
CPU-NB DID 1
CPU-NB FID 05
AMD CPU Stepping P0
PWM-Setting
-----------
PWM Control Enabled
CPU VID COntrol 1.25000V
CPU VID Specil Add Auto
CPU NB Vlotage Control 1.10000V
CPU NB VID Special Add Auto
DRAM Voltage Control 2.31V
SB PLL 1.2V Voltage 1.2V
NB Core Voltage 1.120V
NB PCIE Voltage 1.120V
NB HT Voltage 1.040V
CPU 2.475GHZ
NB 2.025 GHz
HT 2.025 GHz
MEM 600 MHz 5-5-5-16
Somewhat highest stable ref HT here atm (280MHz)Code:Genie Bios Settings
===================
Timing Mode Manual
Memory Clock value or Limit DDR 1066
PCIE 3,4 State Auto
PCIE 2 State x2
AMD K8 Cool&Quiet control Disabled
CPU CLock Ratio 11x
Spread Spectrum Disabled
CPU Host/HTT Clock 225MHz
CPU Host/HTT Boot Up Clock 225MHz
CPU Host/HTT Adjust Gap 5MHz
PCIE Clock 100MHz
DRAM Configuration
------------------
MCT Memory Timings
MCT Memory Timing Manual
2T Mode Auto (Enabled)
CAS Latency Time 5 CLK
Precharge delay (tRAS) 16 CKL
DRAM RAS# Precharge 5 CLK
DRAM RAS# to CAS# Delay 5 CLK
Bank to Bank Cmd (TRRD) Auto (4 CLK)
TRC 24T
TRTP Auto (2 CLK)
Wrtite Recovery (TWR) Auto (8 CLK)
Write-Read Command (TWTR) Auto (7 CLK)
TRFC0 75.0ns
TRFC1 75.0ns
TRFC2 75.0ns
TRFC3 75.0ns
Trdrd Auto (2 CLK)
TrwtTO Auto (6 CLK)
Twrrd Auto (0 CLK)
Twrwr Auto (1 CLK)
CS/ODT Pin Fine Delay Enabled
TLB Cache Mode Enabled
Bank Swizzle Mode Enabled
Auto Tweak Performance Disabled
Optimal Performance Mode Disabled
ODC Controll Mode
DRAM Drivers Weak Mode Normal drive
Output Driver Comp. Auto
DCTs Mode Unganged
HT Link Control
---------------
HT Link Width 16 bit
HT Link Frequency 1.8 GHz
IH Flow-COntrol Mode Disabled
HT Link Tristate Disabled
2x LCLK Mode Disabled
UnitID Clumping Disabled
CPU-Feature
-----------
CPU-NB DID 1
CPU-NB FID 05
AMD CPU Stepping P0
PWM-Setting
-----------
PWM Control Enabled
CPU VID COntrol 1.30000V
CPU VID Specil Add Auto
CPU NB Vlotage Control 1.30000V
CPU NB VID Special Add Auto
DRAM Voltage Control 2.31V
SB PLL 1.2V Voltage 1.2V
NB Core Voltage 1.200V
NB PCIE Voltage 1.200V
NB HT Voltage 1.270V
CPU 2.520GHZ
NB 1.960 GHz
HT 1.960 GHz
MEM 560 MHz 4-4-4-12
Code:Genie Bios Settings
===================
Timing Mode Manual
Memory Clock value or Limit DDR 800
PCIE 3,4 State Auto
PCIE 2 State x2
AMD K8 Cool&Quiet control Disabled
CPU CLock Ratio 9x
Spread Spectrum Disabled
CPU Host/HTT Clock 280MHz
CPU Host/HTT Boot Up Clock 280MHz
CPU Host/HTT Adjust Gap 5MHz
PCIE Clock 100MHz
DRAM Configuration
------------------
MCT Memory Timings
MCT Memory Timing Manual
2T Mode Auto (Enabled)
CAS Latency Time 4 CLK
Precharge delay (tRAS) 12 CKL
DRAM RAS# Precharge 4 CLK
DRAM RAS# to CAS# Delay 4 CLK
Bank to Bank Cmd (TRRD) Auto (3 CLK)
TRC 24T
TRTP Auto (3 CLK)
Wrtite Recovery (TWR) Auto (6 CLK)
Write-Read Command (TWTR) Auto (3 CLK)
TRFC0 75.0ns
TRFC1 75.0ns
TRFC2 75.0ns
TRFC3 75.0ns
Trdrd Auto (2 CLK)
TrwtTO Auto (6 CLK)
Twrrd Auto (0 CLK)
Twrwr Auto (1 CLK)
CS/ODT Pin Fine Delay Enabled
TLB Cache Mode Enabled
Bank Swizzle Mode Enabled
Auto Tweak Performance Disabled
Optimal Performance Mode Disabled
ODC Controll Mode
DRAM Drivers Weak Mode Normal drive
Output Driver Comp. Auto
DCTs Mode Unganged
HT Link Control
---------------
HT Link Width 16 bit
HT Link Frequency 1.4 GHz
IH Flow-COntrol Mode Disabled
HT Link Tristate Disabled
2x LCLK Mode Disabled
UnitID Clumping Disabled
CPU-Feature
-----------
CPU-NB DID 1
CPU-NB FID 03
AMD CPU Stepping P0
PWM-Setting
-----------
PWM Control Enabled
CPU VID COntrol 1.30000V
CPU VID Specil Add Auto
CPU NB Vlotage Control 1.30000V
CPU NB VID Special Add Auto
DRAM Voltage Control 2.31V
SB PLL 1.2V Voltage 1.2V
NB Core Voltage 1.200V
NB PCIE Voltage 1.200V
NB HT Voltage 1.270V
hi guys,
during RAID setup i selected raid 0 and 128kb size is that good or should i selected the 64kb size. my pref. is on par but i thought it would be better
what program should i use to read out the temperature. guardian says in 15-20 celcius idle and load 30-35?
hummm, i can only select 64 or 128KB.
What do you suggest? 64 or 128Kb
Cat 8.3 drivers. I can't have HT<>NB multis, C1 error.:shrug:
I just finish to install Vista x64 SP1 @2750 speed, only one freeze on the 1st reboot, but voltages are lower than what I had before, I'll try to post some BIOS photos later.
CB Tracers are these ones?
Not quite idling, that post was just after finnish 3h gaming.
http://img358.imageshack.us/img358/2821/tempgu4.th.jpg
I took from a earlier SPIDER Plataform review some time ago.
22 inch
24 inch
30 inch
You mean this (taken with no drivers at all, Vista SP1 x64)?
http://img87.imageshack.us/img87/2471/cachememjt1.jpg
nice temps, little too low even..
I know, with MSI/ASUS had no problem setting HT<NB, but with DFI even if I set HT to AUTO and NB to 05(x9) I got C1 errors @ HTref 250. I have the feeling that my DFI have problems, or maybe I need more time to know it better, I also have 2 more Lanparty's 939 Expert-Opteron170@3000/UltraD-X2 3800+@2700 and had no problems at all, overcloking wise.
They go well with DFI, color wise. :)Quote:
I've been thinking if I should go 2Gb 1066 or 4Gb 800, and I have been targeting those Tracers. :yepp:
CPU/MOBO are OK, GPU 69/-1 LOL, no drivers yet.
Edit:
Installed Vista SP1 x64 with this Genius bios settings:
http://img149.imageshack.us/img149/1...0475ms1.th.jpghttp://img149.imageshack.us/img149/6...0476xd6.th.jpghttp://img440.imageshack.us/img440/3...0477xv0.th.jpghttp://img149.imageshack.us/img149/1...0479oh4.th.jpghttp://img440.imageshack.us/img440/9...0478pj3.th.jpghttp://img149.imageshack.us/img149/6...0480wa8.th.jpghttp://img440.imageshack.us/img440/3...0481ir5.th.jpghttp://img440.imageshack.us/img440/9...0482zr7.th.jpg
Running system:
http://img440.imageshack.us/img440/5...0483ka1.th.jpghttp://img149.imageshack.us/img149/8...0484oe0.th.jpghttp://img149.imageshack.us/img149/7...0485ip7.th.jpg
I tried G-Skill's 2x2GB DDR2-1000 kit and it works in 1066 mode at 2,12V. Does ~550MHz at 2,2V. Unstable at 560MHz at 2,3V.
Also updated the SB600 drivers to those available on the DFI Site. I get 111MB/s instead of 109B/s average now and ~20MB/s higher burst.
@BrotherEsau: Did you manage to oc your phenom with above settings?
@aGeom: :yepp: the 2GB kit matches perfect to the DFI mobo colorwise. The 4GB Kit would fit perfect in my sapphire version. :)
How much did you gain from weak mode? Did not help here in terms of cpu frequency. Tried to boot at 13,5x200 with 1,45V CPUV, managed to get into windows but the system freezes imediate after starting prime.
Also I think you should replace your RFC0 and RFC1 settings with each other, 75nm might even work for both.
Finaly, what are your load temps running prime at 2,75GHz? I get ~58°C CPU and 46°C core temps at 2.6GHZ/1.375V and ~62° CPU and 48° core temps at 2.6GHZ/1.45V.
Hey, all you gents running Phenom Processors could you please tell me if any of you with Phenom are having Issues Running AMD Overdrive the Newest version on the DFI 790FX -M2R please?
I have installed the new version 2 times now once with my 6400+ BE and now with Phenom 9600 BE it detects the Phenom just fine but just opening it up to look at AOD and without making any adjustments what so ever in AOD I click OK and in previous versions it just closed the Application now in this version clicking OK it says AMD Overdrive is Applying Settings Please Wait:confused: and then it will just freeze and say its applying settings which was never requested to begin with and I have to end up closing it down through Task Manager 10 minutes later:rolleyes: :down:
So the real question here has AMD Overdrive Ever worked for any DFI 790FX-M2R /Phenom Owners? At any point:rolleyes:
Please leave you're feed back because I am believing that its a Bios Issue because this Program has Locked up and wreaked havoc on any version of the Program with every Bios at least through my experiences:rolleyes:
Thanks for the pic links. :up:
That b/w is low, must be SP1, its very low for those timings.
About temps, what I meant is: if you have 1.4v real on Phenom at any MHz, 20C ambient, TRUE 2xDeltas, you can forget about being below 40C idle (without CnQ). Those software values you're seeing aren't temps, we've covered this a while ago. That's just Tcontrol. Actual temps will definitely be idling above 40C, very rarely below 45C at those volts. Hence, be careful :yepp:
You're talking about 155W TDP there, it'll be very hot on air.
Try 1.44V 2.9-3.1G on Q6600/Q6700, that'll give it the same temps your Phenom is at as a comparison.
Actually tried the first template you put up before the others and it would not boot! I really need to do allot of reading on what Tony wrote on the Phenom situation with Overclocking and also threads from KTE, AussieFX, DaveBurt, Lightman and others to try to grasp the approach on working with the Bios settings with this Phenom:yepp:
What would be the best 2X2GB 1066MHZ Ram kit for this Board that should have no problems running at low voltage @1066 in Bios please?
AOD in the newest Version works over here with the x2, but disables c'n'q and sets a somewhat lower voltage..
@BrotherEsau: Odd, here are manual settings for stock without CnQ. Your systems gets stuck at C1 or 25 ?
As an alternative leave "CPU Clock Ration" at AUTO, CnQ enabled and use a "CPU FID" of 07 with an "CPU DID" of 1 in the "CPU Feature" section first. Reboot disable "CnQ", reboot and use "CPU Clock Ratio" now.Code:Genie Bios Settings
===================
Timing Mode Manual
Memory Clock value or Limit DDR 800
PCIE 3,4 State Auto
PCIE 2 State x2
AMD K8 Cool&Quiet control Disabled
CPU CLock Ratio 11,5x
Spread Spectrum Disabled
CPU Host/HTT Clock 200MHz
CPU Host/HTT Boot Up Clock 200MHz
CPU Host/HTT Adjust Gap 5MHz
PCIE Clock 100MHz
DRAM Configuration
------------------
DCTs Mode Ganged
MCT Memory Timings
MCT Memory Timing Manual
2T Mode Auto (Enabled)
CAS Latency Time 5 CLK
Precharge delay (tRAS) 16 CKL
DRAM RAS# Precharge 5 CLK
DRAM RAS# to CAS# Delay 5 CLK
Bank to Bank Cmd (TRRD) Auto (4 CLK)
CS/ODT Pin Fine Delay Enabled
TLB Cache Mode Enabled
Bank Swizzle Mode Enabled
Auto Tweak Performance Disabled
Optimal Performance Mode Disabled
ODC Controll Mode
DRAM Drivers Weak Mode Normal drive
Output Driver Comp. Auto
HT Link Control
---------------
HT Link Width 16 bit
HT Link Frequency 1.8 GHz
IH Flow-COntrol Mode Disabled
HT Link Tristate Disabled
2x LCLK Mode Disabled
UnitID Clumping Disabled
CPU-Feature
-----------
CPU-NB DID 1
CPU-NB FID 05
AMD CPU Stepping P0
PWM-Setting
-----------
PWM Control Enabled
CPU VID COntrol 1.25000V
CPU VID Specil Add Auto
CPU NB Vlotage Control 1.25000V
CPU NB VID Special Add Auto
DRAM Voltage Control 2.12V
SB PLL 1.2V Voltage 1.2V
NB Core Voltage 1.200V
NB PCIE Voltage 1.200V
NB HT Voltage 1.290V
It's like with memory timings, sometimes you can not do it in one step.
EDIT: Planet3dNow made an oc guide for phenom, they took alot of info out of tony's thread. Here is a translated version.
Did not look at Post Code on LED actually was early in the AM and had been up all night worried about my little Buddy Marshall and this was just prior to walking out the Door too. Probably not the best time in the world to be doing overclocking on unfamiliar ground:p:
What Bios are you guys with the Phenom Processors on anyways?
Personally I think its a POS but the fact here is that Bios on this board has never properly supported the stupid thing and its one of the Key components to the new Platform and it would be nice to be able to use it to monitor your system without it taking it down for no good reason.
I think it's due to the mobo uses slam vid mode. That means the CPU VID set via MSR registers are not used. The CPU VID in the registers stays at 1.25V.
Now AOD starts reads 1.25V CPU VID and tries to apply an appropriate CPU voltage.
If posted the MSR registers at page ~#24 here.
where is the driver disk for the latest bios Raid Rom
Latest Raid Driver Package from DFI is
790FX-RAID-F6
Includes SIL and SB600 drivers and is recommended for raid bios version above 3.1.
The SB600 drivers are from 08/2007.
Well i'm ocing now.
Got 3,2 at 1,375V in bios bus it not stable and gives an rounding error at 4 min. Other voltage setting have a minor increase. Mem is @ stock.
I will be wokring on this. I want 3,2Ghz....
Another thing. when i shut Vista down it restarts it self and boots up to vista startscreen. i looked to the connectors and the are ok connected and working. anyone having the same problems.
@ final8ty look on:
http://us.dfi.com.tw/Support/Downloa...FLAG=A&SITE=US
F6 is the latest and works ok
koekerwauz: two possible reasons: you get an bsod during shutdown which you do not see because of the os is set to restart at errors (default with home versions)
or you have set some wol- or other wake-up settings in bios.
i had this problem with my cfx and only way to get rid of was using the other lan-port..
Thanks all :)
Hi oese I have finaly been able to do that test with half en round multipliers,
ddr 1042 @ multi 10 clock 2610mhz gives:
8560mhz read
with ddr1000 @ multi 11.5 = 2998mhz gives
9091 read
So I guese G2 brisbanes are not sensitive for half multi problems!
As you can see higher trfc have solved my oc problems 308+mhz htt is no problem any longer since I use 3oh6 settings for this ram! Thank you very very much for that!
@ all has any one noticed if changing from k8 to k10 does lower the squeeling noices of the bord? the lower vcore of phenom does it help reducing this sound? Or is this noice related to the changing memory speeds on k8 when changing multi?
greetz
You should not be getting any noise period:yepp: I have had a 6400+BE in this board and the Phenom is new past few days and I have had 2 boards and neither one of them made any kind of noise under load or due to RAM MHZ Or voltage change:)
@ DPeter: Nice, thank you... It would have been horrible if brisbanes which often come with half multipliers would show this behaviour.. and Phenoms have half multipliers often too...
It's true you "shouldn't" get any sound from the board although it happens quite often on any component when stressed more.
I had both an X800Pro ViVi @ XT PE and a X1800XT @ XT PE which made noise underload only. Also my previous DFI nF4 Ultra-D board made noise, Epox 'somthing' made noise and this one does as well.
As you said, it shouldn't however it's not a sign of dieing hardware or anything. So if you can live with it just leave it be.
G.Skill SPD have support for Weak Mode, when BIOS have that option I enable it, I just use NORMAL to cut some variables when debugging, a non boot situation. All RFC's can be set to 75nm, about gains didn't bench WEAK/NORMAL, I'm still fighting to level this board at same MSI/ASUS OC level, to start real benching. (I'm tempted to flash M3A32 bios in this board, with some mods :rofl: ).
I'm running Prime ATM:
http://img340.imageshack.us/img340/3...me95ta3.th.jpg
Yea, changing tabs or set Turbo mode, got video corruption (color stripes all over) mouse sometimes move sometimes don't.
Welcome, :yepp: bw to low, SP1 it's not TBL fix killer but also general performance killer, I will be back to non SP1 soon.
I will not argue with that, but the fact is, if I touch the HS heatpipes near CPU when at full load I bearly feel it warm, if I touch PWM HS then I feel it more hot.:shrug:
How can I know the real temp, by software? All progs I have, show me aprox same results. Please check Thumbnail, thx.
I'm alergic to the Dark side. :rofl:
Real temps are not possible with software with AMD Phenom. :(
Check the new AOD they were supposed to calibrate the readings better (?)
The 1.4V+Phenom temp statement I made a long time ago in MSI thread because of details from AMD.
Tcontrol works by reading "too low" when it's below a "certain temperature point" but then "too high" when above that same "certain temperature point". The temperature point looking at documents seems to be near 55C real Tcase.
So;
Before that value you'll have temp. values given back that are -<54 while the real temp is higher.
After that value you'll have temp. values given back that are >55- while the real temp is lower.
Hence, the temp. feedback is designed to read lower than ambient and even negative values on air cooling. :yepp:
If you have enough air moving on the HSF, it will feel cold to the touch. Only the direct base will feel heat near to the real temperature. Also metal feels cold to human touch if you're hands are above its temperature, its a relative thing. Just be careful, your load temps will be high, very high, on air at 1.4v. ;)
Ok, so if I got it, 55C its the "breaking" point, Tcase(real temp)<55 Tcontrol read low temps. So my readings are "low" Tcontrol=CPU 57C; Cores 48C full load, can I make an logical conclusion that my Tcase<55C?Quote:
Tcontrol works by reading "too low" when it's below a "certain temperature point" but then "too high" when above that same "certain temperature point". The temperature point looking at documents seems to be near 55C real Tcase.
As you can see some posts before I got photos from my system running, the white fan is at 110CFM and blow air over PWM HS, and i feel the difference between PWM/CPU, I know is far from be accurate reading, but reflects the software reading difference values, in bios CPU temp reads 28 and PWM 45.
Only the MSI runned fine 2750 @1.3v.
Well, I have some temp probes cables, and still have an K7M board with pins to connect, so if I put the probe between CPU and the socket (I have one able to insert there, just don't know here), can I read Real temp in the K7M system?
THX
I noticed that my board has a high pitch squealing noise too and it seems to be coming from the PWM area. I don't know if this is normal or not but everything seems to be working fine so far.
OK...... Was able to finally get the OC working on this thing:D only problem is that for some reason I am baffled to why the computer wont Boot with Ram at 1066 set in Bios:confused: is it the Ram or is it me? My Ram does over 1200MHZ
Thats a fact:rolleyes: guess its me:p: or does some Ram just not get detected when set to 1066 max value in Bios? Also from what I see my board responds better to being set through FID/DID not by CPU Multi:yepp: any words of wisdom on the 1066 Ram setting in Genie Bios and why my PC wont boot with it set on that?
Modest OC
@ 2420MHZ @ 220 Bus Speed X11 Multi HT Link Frequency @1980mhz NB Frequency @ 2200mhz / Ganged Mode all at stock Voltage:up:
Cmon fellas help a brother out and lay some info on me:yepp:
Brother I did your settings with mems @1066 system booted fine.
Bios 307.
That's a guess by me and that's only Tcase (center of IHS). Tjunction (internal diode) temp. is higher. But yeah 55C seems very close to what it is. The diodes in k10h also have an errata where they read too low temps.
You just have to use common sense and basic physics knowledge to discern whats correct and not; 1.4V/155W on a 1.23V/95W TDP chip is going to be very high load temps. In the 70-75C region Tjunction with a TRUE and 2x 105CFM Deltas, 20C ambients, which is not far from the throttling temp. ;)
Brother, you'll need to read quite a lot for Phenom, it 'aint that simple as X2/C2. Spend some useful time now and quit messing around :slapass:
:D
Achim and aGeoM should know all there is to it without you needing any other material. ;)
Drop your NB to 6x and the MEM to 667 mode, blast coolers on full then try oc'ing Phenom. :yepp:
I have massive trouble with it even with the BE5000 in my board. It does not like the M2R near as I can tell. Actually, I haven't found a board that it works well with yet. I had an Asus M3A32, it worked poorly with that (actually, it reset the board by itself constantly).
I'm typing this on a Gigabyte 780G board, and it works poorly there too (even with the new version specifically FOR the 780G). It registers voltage and temps incorrectly, doesn't baseline most settings at all, and is generally faulty.
If I run it, and I have Everest running at the same time, clock speeds start bouncing around in Everest. AOD is pretty lame.....:down:
:confused: ok, I give up. I was lucky not melting the board when I did 2900Mhz @1.53v :rofl:
KTE, OCing in my point of view, isn't lowering nothing, more CPU/NB/HT/MEM MHz @ the most stable configs, finding the balance (G spot :D ) it's my gold, for 24/7 use and smooth as silk gaming. When targeting some hwbot's scores then I clock someting down to achive it. For me Phenom in some way isn't different from X2 or K6-2, only have more variables to play. :)
That's why I'm a litlle frustraded with DFI compared with ASUS/MSI, she's cold like Artic waters, maybe that's why I'm getting so low temps. :rofl:
:toast:
So your ram is not yet supported. KTE mentioned some time go that modules without 1066 JEDEC mode need to be prepared by the bios developers in a more manual way.
Nevermind 4-5-5-16 are the best timings i could choose in the bios in that mode, unfortunatel i could not yet reach a 300MHz ref HT. :D
I tried it the FID/DID way here first and it did not boot with a 13x multi using the cpu clock multiplicator worked, so I thought it's the better way.
Seems sometimes the DID's and FID's are not set to proper defaults.
What made you boot finaly, 800 mode or FID/DID?
:clap: There ya go, 2.2GHz for the NB is abit high for stock (1.25V).