More VCore. Try 1.45V to start. That's very safe with decent air.
Your chip already OC's better than mine. That is, of course if it's Orthos stable at those settings.
Printable View
More VCore. Try 1.45V to start. That's very safe with decent air.
Your chip already OC's better than mine. That is, of course if it's Orthos stable at those settings.
dual prime for 4 hoursQuote:
Originally Posted by Brahmzy
i know thats not considered "stable by most" but i havnt had it crash doing anything so its good enough for me for the time being once i get to 3.2-3.4 ill run an 8-12 hour prime
whats temps should i be looking @ staying under?
which of my temp reading seems valid?
so vcore wise there the same as the AMD x2's they can take 1.5+ and still be somewhat safe? (my X2 4400 nedded to have 1.55 Vcore to run 3D mark @ 2.6)
Well I'm at the same stupid 3.2ghz dual prime stable limit as just about everyone else. I'm about to remove board & cpu now and give the msi a go.
http://img237.imageshack.us/img237/6...establenh6.jpg
NO probs here so far , I got one of the early series though, came with the 0401 BIOS-but after flashing to 0903 it s OK :D
IT would be interresting to have compared orthos stability at the same vcore /frequency ( Vdroop surely not the same )Quote:
Originally Posted by Brahmzy
Mykou, that s probably right :)
BIOS 1201 just posted on Asus' web site! Anybody try it???
P.S. How are you guys "Dual Priming"? I can only get one window to run.
for dual super pi
Copy the .exe into two executables and open both
Go to task manager and set the affinities so that one instance pertains to Core0 and the other to Core1
Run them simultaneously.
(copied txt from another post)
Thanks.
Now Asus' web site only lists 0801 as the most recent BIOS update. WTF?
Famich, that is a nasty OC. Your vcore for 3.6 is what my vcore is for 3.2 :(
Still no answer, I did all of the things in this thread...Quote:
Originally Posted by Mr.Kakarot
On another note, do you run 2 instances of orthos... or just one? If you run 2, is there a way to set them to each cpu (like in prime). Or do you just run the 2 instances... thx
OK check this out.
My specs:
c2d e6600
p5w dh
x1900 xt
So I have serious video problems. BIOS splash, POST info, Windows Logon screen, etc are all artifacted, skewed, etc. It is barely readable. I have 3 x1900 cards, and none have worked.
Now ocassionally, I get a normal screen. The last time I did, I loaded the Catalyst drivers, and now during Win logon, the video signal just dies. Any ideas?
I think that I have ruled out it being the gpus. Right now, I am stumped.
Thanks.
The new bios can be found here for those that are daring.....
ftp://ftp.asus.com.tw/pub/ASUS/mb/so...20DH%20Deluxe/:banana:
No kidding...I wish I had his Proc. :( 400MHz better!Quote:
Originally Posted by miochza
Just installed it bios 1201.. still cant boot @ 370FSB+ without having to enable SPD settings {auto} No mem timings options added. Conclusion...eh..it still sucks
This cold boot thing is killing my Vapo. When the p5w cold boot, it also turned off the Vapo. Is there a way to get around this?
thanks guys
Is what i'm experiencing below the so called 360-370fsb limit on async dividers only but not sync 1:1?
my P5W DH with 0801 bios with 2x1GB Gskill PC6400PHU2 HZ Micron D9GMH (0629) doesn't seem to like 4:5 upclock divider past 378fsb (gives 472mhz mem) for now :( Nor does it like 2:3 beyond 360fsb (gives 541mhz mem). This is with manually set timings of 4-4-4-12 regardless of vdimm used. Haven't tried setting SPD for memory to boot yet.
P5W DH i have doesn't seem to like 4-4-3 timings where tRP = 3 either, can't pass memtest86+ v1.65 higher than 460-472mhz 4-4-3 (manually set in bios) regardless of vdimm used or divider used. Same memory on Badaxe board did 488mhz 4-4-3-5 at 2.2v!
But 1:1 seems best for E6600 due to max fsb limitations I wonder how far i can go just for testing single Super Pi v1.50 32M :)
Testing max single Super Pi v1.50 32M:
vdimm = 2.3v (seems to help stable things due to tighter timings at 1:1 clocks especially when you get closer to P5W DH's max FSB wall)
Bios Settings:
vFSB = 1.3v
vMCH = 1.65v
vICH = AUTO
Performance mode = Standard
Hyperpath3 = Disabled
DDRAM Throttling = Disabled
* All tests are straight boot from bios with manual timings set at 4-4-4-8 4 at 2.3v
* All tests are untweaked with default P5W DH set timings. Have yet to even tweak with memset or drop tRP to 3 yet.
@3807Mhz - 9x423fsb at 1.55v bios vcore = 1.508 bios
32M = 13min 41.797s
@3897Mhz - 9x433fsb at 1.6v bios vcore
32M = 13min 16.672s
@3924Mhz - 9x436fsb at 1.625v bios vcore
32M = 13min 09.953s
@3942Mhz - 9x438fsb at 1.6375v bios vcore
32M = 13min 09.578s
Hit max FSB limit of vMCH 1.65v, raised vMCH to 1.75v
@3960Mhz - 9x440fsb at 1.65v bios vcore
32M = 13min 04.969s
@3987Mhz - 9x443fsb at 1.6625v bios vcore = 1.64v windows idle and 1.61-1.63v load
32M = 13min 00.750s
I'm using sata port 1 for my os hd and i've tried sata ports 3/4 for my backup hd. Intel ide connector for my dvd.Quote:
Originally Posted by zoob
I've tried a ps2 keyboard but my mb still has usb issues. It refuses to recognise my external usb hd.
I have this same problem, i rma'ed my 3d card still waiting for new one.Quote:
Originally Posted by FlimFlam00
But you now say it couldn't be the card, i hope it isn't the board :mad:
What bios are you using ? Do you have artifacts in windows safe mode ?
I only had artifacts in POST and in windows nothing but once i installed drivers i got black screen.
I have a 7950GX2.
Mine also booted while there was no plug from the psu connected to the 3d card, didn't even gave a warning about that.
I have seen other people with this problem and say its because memory of the 3d card is broken?
Quote:
Originally Posted by $oul
This sounds to me like the nasty PEG LINK mode option in the BIOS is affecting these cards even before any serious 3D Function calls are being made.
If you don't already know - PEG LINK is feature on nearly all boards, just called different things by different vendors, but it overclocks the card at boot-up and its handled by the motherboard. It handles nVidia and ATI cards differently. In my experience, it's never been a good thing. If you're running the "entire" system at stock/default levels - sure it can help. But, who the heck does that? Go into the BIOS and turn that nasty PEG LINK mode to NORMAL and see how things go then.
I'd like to know the answer to this too. I guess the easiest way would be to wire up the ChillControl board so that the power switch on your case switches the Vapo on, and the reset button switches your PC on (reset cable plugged into PWR-SW on motherboard). This would mean of course you wouldn't have a reset button, and you'd have to power off the Vapo manually after the PC has been switched off (using the power button).Quote:
Originally Posted by dragonhunter
That's the only way I can think of fixing it, unless there is some way of configuring the Vapo to wait at least 5-10 seconds before shutting itself down.
i see, I come from a AGP board i didn't know this.Quote:
Originally Posted by Khaotic
But i have to say i booted a few times fine and could install drivers, but running 3dmark gave heavy artifacts and all of a sudden i got those artis in post and black screen when in windows.
Could it be that the motherboard screwed the video card because of the oc?
Just a luck of the draw... bought in Germany :p:Quote:
Originally Posted by Brahmzy
That s why I don t believe in this crap about tray CPUS being worse than the retail ones
Sorry I did not reply. Here is the deal.Quote:
Originally Posted by $oul
I installed my OS, and then ran into the video problem. I tried everything I knew. The splash screen would be OK, then I would get severe flashing and skewed views of the screen. The aspect rato would be like 400 x 200.
I had two x1900s since I ran xfire but since Irun dual monitors and have sli on my other rig, running both was a moot point. So I sitched out cards in a single config. Then i RMA'd both. Anyway, I got a brand new card back, and still, same problems. Doh! I thought with my luck that i actually may have had two funky x1900s.
Anyway, I reinstalled the OS, and then I basically was able to get the CS drievrs in and the video drivers. Then the Windows splash would die. So I made ever basic fix noted in this thread in the BIOS.
I flashed to 1201. Also, I just reseated everything. I thought my dvi kvm may have been a problem. It is a Blekin that is temperamental and I don't know if it is the actual kvm hub or one of the cables.
Anway, it seems to be resolved. I don't know what fix did it. It got annoying, so I did not do a methodical pin point of the problem but doing individual changes.
it was exponentially annoying since I modded a Lian Li pc201, and spent a lot of time prepping the unit and waiting for parts etc. i spent a week building around work, school, modding, and parts coming in. so when i encountered problem after problem, it just got more irksome as things went along.
It always seems like with each new build i get a whole slew of new problems.
Nonetheless, it was worth it, because my mosheen is coming together. I'll post some pics again. I wish that i could provide some definitve answers right now, but it seems the 1201 bios is stable for me, and that about 90% of the BIOS settings recommended in this thread are relevant and vital.
hi,
i wanted to know that the temps for motherboard under "pc probe" or "everest" is for northbridge or the southbridge ? mine is alwayz @ 46~49C which i find pretty high....what temps do you guys get ?
i||uSi0n^