change one timing at the time and see which one casues the reboot!Quote:
Originally Posted by Divvy
Printable View
change one timing at the time and see which one casues the reboot!Quote:
Originally Posted by Divvy
Can anyone please help?Quote:
Originally Posted by MrSlacker
iirc Look for this setting :
FSB ---> K8 x5
Lower it to x3 or 600 (depending on which bios version you have).
Hi ben805! Thanks for your reply|Quote:
Originally Posted by ben805
But change where? in my actual bios or with this settings:
http://www.xtremesystems.org/forums/...15&postcount=1
Can anyone please confirm? He is using the latest BIOS, 1103 IIRCQuote:
Originally Posted by Ic3man
The images are showing? Can everyone see the images?Quote:
Originally Posted by Divvy
Please help... and sorry for my poor english...
Check your memory with memtest86+.
Since you are not overclocked you should be able to work with the above settings.
So there is something wrong with your hardware.
just keep the rest of the setting and change those three I'd gave you...YES IN THE BIOS!! :lol:Quote:
Originally Posted by Divvy
by the way, the link you'd provided can't' show any pictures so I don't know what they were.
Here are the images:
The last one:
not your images, I was refering to the GSKILL Tech link man.
nevermind....
For those who are having issues with Serious Sam II, there is another cause of this type of issue.Quote:
Originally Posted by Marios
From http://forums.seriouszone.com/forumdisplay.php?f=381:
That has solved my problems with crashes to the desktop and restarts after playing for awhile. At least it has in a few hours of playing since I changed those options. [Knock on wood]Quote:
I see some of you with dual-core has a brand new problem (like it wasn't enough already!).
I managed to repro the lock-up issue with dual-core system (I guess it's only on dual-core!), and nVidia drivers 81.xx.
[code-junkie stuff]
Debugging showed that Direct3D never returned occlusion query result, altho it should have, which made our engine waiting in infinite loop.
[/code-junkie stuff]
Since ATI driver and 7x.xx NV driver is fine, it leads to a conclusion that it has something with dual-core support in 81.xx drivers (one of new feature of rel 80 drivers is dual-core support, so there you have it!).
Anyway, just wanted to let you know that we're working closely with NV on addressing this issue.
In the meantime, the workaround is to downgrade to 70 series driver, but if that's not handy for you (because of other games), you can disable lens-flares and occlusion culling with cvars:
'efx_iLensFlareQuality = 0' (3 is default), and
'ren_bOcclusionCulling = 0'.
Hopefully, that will do the trick.
And btw, you change those in the .ini file - forget what its called. If anyone can't find it, post back and I'll take a look on my other computer.
The 1103 BIOS gives me loads of memtest86+ errors on test 8 no matter what speed/timing or voltage I set the ram and CPU to. Even below stock :stick:
I have G.Skill FF ram, so its a crap BIOS for sure. I flashed back to 703 and test 8 shows no errors at all now :)
Asus really need to pull their finger out and create a decent BIOS, as this motherboard and us end users deserve better.
Cheers
I've been expericing some crashes too since i've "upgraded" to 1103 BIOS... And besides that, i got random errors when i use "Par2" files to fix "Rar's", and when i decompress some big "Rar" files, even when i have my system overclocked a little... I thought that my ballistix were dying, but hell no, i'll try 1009 BIOS and see if it helps like it did to you... Shame on you ASUS :slapass:Quote:
Originally Posted by Marios
BIOS ver. 1103 AND O/C PROBLEMS?
As I said I had a few restarts lately while playing HL2 DOD Source with my dual core CPU.
To isolate the problem, I had set the FSB at 201 and the DRAM at 2T from the very first day.
The solution I found was to set the Steam.exe affinity to one core.
I checked it for a few days and everything was OK.
Since the "solution" to my DOD source problem, was working, I decided to restore my overclocked BIOS settings.
Hell. Now I got random restarts without doing anything. :slapass:
The only thing I changed right before I installed DOD Source was the BIOS (from 1009 to 1103).
So I installed the BIOS once again, loaded system defaults and configured everything the right way.
Nothing changed.
My next step was to revert the BIOS to 1009.
MAGIC :woot:
This time I could overclock without those random restarts.
And the most amazing thing?
I can play DOD Source for hours without the affinity trick.
So, in case you have problems ....
DO NOT HESITATE TO REVERT TO 1009 BIOS
You are going to save yourselves from a lot af troubles.
Shame on ASUS for a "crapy" 1103 BIOS, or did I do something wrong?
I am not sure.
I did a few more things since I reverted to 1009 BIOS.
I gave a bit more vcore (from 1.38 to 1.4) and I installed the latest pure video decoder.
I can understand the vcore might be mandatory to stop having restarts.
Though 1.36v was the vcore I always had with 1009 BIOS, because I was overclocked with Cool n Quiet enabled.
Any way I can try the same vcore with 1009 BIOS and come back.
On the other hand I must admit that either the latest pure video decoder solved my dual CPU gaming problem or the BIOS revert.
What do you think?
this is the bios i'm using (1103)
which one is the better ? 703 1009 ?
Do you have any restart or O/C problems with your dual core Opteron with 1103 BIOS?
memory crap @ 260ishQuote:
Originally Posted by Marios
OK this may sound really stupid ( which is my area of expertise for sure :p: ) but has anyone else noticed that this board seems to run cooler when the overvolt options are enabled?
It may be me, but I was messing around with different settings in the bios and clocking the rig differently and I forgot to put the overvolt options to off.
Now the PC's NB is running a good few C's below what it used to at the same speeds as before :confused:
Has anyone else experienced this, or am I just delusional :slap: :stick:
Cheers
Well that's interesting, I think I'll try that. I'm using the CPU overvolt at the moment (board on the bench, x2 3800 @ 2470 @ 1.2625v + 0.2v) because it's more stable and uses all 8 phases. I just wonder from what you say if making the overvolt present in the chipset also helps even if it doesn't necessarily need it.Quote:
Originally Posted by Mickey Padge
How did you get the temp of the NB?Quote:
Originally Posted by Mickey Padge
I think it's about time to change the thread title to "Asus A8N32-SLI General Discussion" eh? ;)
Well it's not the NB so to speak lol, but Asus PC probe MB temp reading.
I am just calling it the NB out of habit. :p:
It is stange how the boards voltages seem more stable when overvoltages are enabled though and the PC probes MB temps are a few C cooler.
The vcore for example has less fluctuations when running 1.3v with the overvoltage enabled than when just running at 1.5v.
Strange, but on my board very much true.
Cheers
EDIT: Ben805 it's true, our initial impressions have lasted for quite a long time lol :D
I think thats becuase the 8-phase power comes into effect when the overvolt options are enabled. Dunno why it would be cooler, I'll give this a test when I get home:p:Quote:
Originally Posted by Mickey Padge
Hmm. Maybe it is spreading out the heat load on the motherboard?
Where is the temp reading being taken from?