Printable View
I have a question to all owners of this motherboard. My buddy got one of these and we were trying to OC. I nevered used an ASUS board before and he doesnt know anything about OCing A64. So anyways, I could not find the HT Link settings... If someone could tell me which option is for HT multi, i would be very greatful. I think its holding back our OC because we could go above 265 HTT with his X2 4400.
Well unless u have another SLI mobo I think its time to RMA the mobo - sorry for the stupid questionsQuote:
Originally Posted by mussadek
Another CnQ utility is RMClock, you guys should really give it a try !
I tried RMClock as well. I did not like the interface as well and I thought it was a little confusing. You should post how you config it and some pics in case someone wants to compare:up:Quote:
Originally Posted by ReelMonza
It is a great utility indeed but the developer kinda screwed up the interface in version 2.0...
version 1.8 has better interface imho... if you can get ahold of it...
one of the main features of this utility is the possibility to choose more stages (p-states) instead of just min/mid/max (you have to choose direct amd transitions under advanced tab) and set voltages accordingly
I made the exact same question on page 53, refering to the A8N32-SLI and nowone answered it...Quote:
Originally Posted by CODE 4
The best thing I´d got was a kind pm from Ben805 disadvising the use of the booster in boards that have 24 pin Atx conector...
However here goes a good tip on the matter directly from OCZ
Thanks you for the HELP I have solved the problem by adjusting the relay in the PSU to get 12v stable when SLI enabledQuote:
Originally Posted by Zeus...
Good to c have got it sorted:)Quote:
Originally Posted by mussadek
i, like many here, have experienced the warm boot issues first hand. even though i am prime stable, often times doing a soft boot, or even a simple power reset will cause the mobo not to post properly. on 2 different cpu's now (both opty 165's overclocked to 2.7GHz), the fix for me was to increase vcore voltage a little bit. I have tried every other thing in the settings to no avail except this. hope this helps some folks out there...
p.s. interestingly enough i also gained a little stability on one of the 165's i own by just connecting up the EZ-PLUG (a la the DFI boards). Anyone else with this experience as well?
So, going back to page 52 (sorry, was on vacation in Vegas). I'm no alone with trying to resume from S3 Standby while overclocked, and having my FSB revert back to Stock FSB? Yes, I know a restart will fix it, and i"ll be overclocked once again. Isn't this annoying to anybody else? What can be done to fix this? Bios update? or Hardware. Thanks again!
Ranger
In my case, using the latest bios has fixed the reboot, softboot problem. I didn't see any relation to this problem and Vcore.
I have the latest bios and still gets warm boot :stick: .. What the hell, can't asus fix that with some proper bios update, instead of 'stupid' vcore incresment and stuff like that ..
ASUS A8N32-SLI Deluxe: Love at Second Sight :
http://www.xbitlabs.com/articles/mai...xe-update.htmlQuote:
"In our recent review of the Nvidia nForce4 SLI X16 chipset and of the ASUS A8N32-SLI Deluxe mainboard based on it we met a number of problems resulting in low performance in synthetic as well as gaming tests. We are making our amends now by publishing fresh test data we have achieved with correct HyperTransport bus settings and with the latest version of the nForce4 SLI X16 chipset driver."
Quote:
Originally Posted by ReelMonza
That's weird. They show a 3DMark05 "Total" score of only 7730 - with 2 7800GTXs.
Not sure what test result that is. Because using 2 7800GT's I get close to 12,000 on the free version of 3DMark05.
Anyone know?
they more than likely ran it at a higher resolutionQuote:
Originally Posted by dbett
...with all the eye candy
At least they have the guts to addmit they were wrong the first time.Quote:
Originally Posted by ReelMonza
Although this is was a review of P5N32-SLI, it was interesting to note nevertheless:
http://www.hothardware.com/viewartic...&articleid=729
"Unfortunately, getting the system booted was not always that easy. In many cases, booting up the P5N32-SLI resulted in a blank monitor screen and we had to manually shut down the board using the kill-switch on the power supply. Originally, we thought this might have been a heat-related issue, as the system typically would not reboot after running benchmarks and the like. After checking fans and airflow, we were convinced that the setup, at least, was not at fault. We also noticed that the next boot after using the PSU kill-switch, would invariably halt during POST with the message that "overclocking failed or overvoltage failed". The problem with this is that in just about every case, we were neither overclocking nor overvolting any of the components. Investigating the issue, we found that in the Hardware Monitoring section of the BIOS, that the CPU was consistently undervolted, usually by a solid volt off of the expected value. That is, even if we raised the voltage elsewhere, the VCORE Voltage would be one volt lower. We managed to gain a bit of stability by manually raising the CPU voltage, but still found that the system became unresponsive from time to time."
I might bust out an RTA and monitor the CPU voltage values during operation and after a reboot to see what it is outputting to the CPU...
Not quite. They're still trying to shift the blame by saying that this MB has a problem resetting the SB>NB to 2X after clearing CMOS or updating the BIOS. I have seen that just once, right after flashing to 903. And even then, loading the set-up defaults changed it to 5X.Quote:
Originally Posted by Marios
I don't know about you, but the very first thing I do after flashing or clearing CMOS is to load set-up defaults, reboot and go through the whole BIOS making all my adjustments--it's that last little bit they didn't do.
Then (in the first review from December) they confused many of us by trying to explain their odd results claiming that this MB gets its extra PCIe GPU bandwidth by robbing it from the HTT (8 up, 8 down instead of 16/16.) I don't know how many read the old review but it caused a stir many places.
At least their new review has very good data showing how important it is for SLI performance to get the SB>NB settings right.
This is common knowledge to load setup defaults.
XbitLabs had to give an excuse.
Any way... LOL.
That's why I said "at least".
I read their first article.
No comments on that one ...
Restarts when playing 3D games with Dual Core CPUs?
I believe this is an existing 3D gaming problem with dual core CPUs.
The background
Issues specific to a Dual x16 SLI systemQuote:
Open Issues in Version 84.12
NVIDIA Issues—Single GPU
There may be intermittent application compatibility issues with dual core CPUs.
If you experience this issue, you can work around it by toggling off multi-thread optimizations using the following instructions:
1. Launch regedit and determine the current primary display card by looking in
HKey_Local_Machine\Hardware\DeviceMap\Video
and note the GUID (global unique identifier assigned by Windows), which is the long string in brackets { } at the end of the entry
\device\video0
2. Look in
HKey_Local_Machine\SYSTEM\CurrentControlSet\Contro l\Video\{GUID}\0000
where {GUID} is the number derived from the previous step.
3. Open the "0000" directory and create a new DWORD called OGL_ThreadControl and give it a value of 2.
This will disable multithreading in the driver for all OpenGL applications.
4. If you want to disable driver multithreading for all Direct3D applications
In the same "0000" directory, create a new DWORD called WTD_EXECMODEL and give it a value of 0.
A8N32-SLI Dlx is a Dual x16 SLI system.Quote:
Issues Resolved in Version 81.85
Single GPU Issues Resolved
GeForce 7800 GTX/GT, GeForce 6600, SLI: The system hangs when running 3D applications on a Dual x16 SLI system.
This issue is resolved with an update to the nForce4 430/410 motherboard BIOS. Contact your motherboard manufacturer for the update.
SLI-Related Issues Resolved
3DMark05 and Far Cry experience poor performance on a dual x16 SLI system compared to a Dual x8 SLI system.
The mentioned fix requires a BIOS update.
I never saw any ASUS BIOS update mentioning this fix. :slapass:
This is my story.
I have installed the latest Windows XP SP2 updates, the latest DirectX (I think it is January 2006 edition), the dual core fix, I've checked the presence of the M$ updates with QFE check and I use sfc/scannow, checkdisk and defrag from time to time.
This way, I never had any issues in the past with games and I always thought the DUAL CORE problem as a personal problem.
I believe I was wrong.
When I first installed "Counter Strike Source" I got a few game crashes with looping sound even though I checked the integrity of the game with STEAM.
The problems did not appear right away.
I had to play the game for a while to get the error.
I have two Athlon64 CPUs. One single Core 3500+ and one dual core 4400+
- With my single core 3500+ I can play for hours without any problems with 5.1 speakers.
- With my dual core 4400+ I could smooth (not solve) the problem by setting "stereo" sound. This gave me only one crash after a few hours of gaming.
To permanently solve the looping sound crash problem with the dual core 4400+:
1. Dissable the dual core optimizations the Nvidia way OR
2. Set the affinity to one core or
To set the affinty to one core
Start the game
Press ALT-CTRL-DEL to open the Windows Task Manager
Go to process tab,
Right click the "game".exe process
Set the affinity to single core
(no matter which core it works).
The affinity change is not permanent.
You have to be able to minimize the game to access the Windows tak Manager.
There are programs to set the affinity permanently but do not use them.
I have no problems with other games.
I hope this helps.
I guys!
Can someone help me to configure my BIOS?
I already have problems with my memories... but now, I discover this topic and help me alot! I have dual channel working now! I never did It!
But I only change the memory settings, because if I do the same like that topic, my computer reboots in the windows logo.
So, can someone help me changing the other settings? Or I dont need It?
This is my computer:
And this is my BIOS:Code:NZXT Lexa
AMD OPTERON 64 175 DENMARK SOCKET 939
Zalman CNPS 9500 Led
SEASONIC S12-600 600W SLI SUPERSILENT
Asus A8N32-Sli Deluxe nForce4Sli SK939
G.SKILL 2x1GB PC4000 HZ SERIES DUAL CHANNEL
Western Digital Disco Rigido 250gb 16MB Sata II
EVGA 7800GT CO 256MB DDR3 PCIe
http://pwp.netcabo.pt/divertidos/bios/im001108.jpg
http://pwp.netcabo.pt/divertidos/bios/im001109.jpg
http://pwp.netcabo.pt/divertidos/bios/im001110.jpg
http://pwp.netcabo.pt/divertidos/bios/im001111.jpg
http://pwp.netcabo.pt/divertidos/bios/im001112.jpg
http://pwp.netcabo.pt/divertidos/bios/im001113.jpg
P.S. Please sorry my poor english... :rolleyes:
There are other games that need the single core affinity fix also. For me it's NHL2006. I've read that other EA Sports games (Madden and FIFA) need it as well but I don't have those.Quote:
Originally Posted by Marios
please, anyone? :rolleyes:
Quote:
Originally Posted by Divvy
change the following and see if it helps:
Read Preamble: 7ns
Async latency: 9ns
TREF: 15.6