Asus a8n-e..

[endizs]

Hmm, funny you say that. I did disable the floppy... will check this out tomorrow and post results!

Thanks for the help.

Quick question though, I was reading that I should pump the DRAM voltage. Should I be doing this? If so, where should I start?

*edit* Shouldn't I keep the HTT at 5x?

 

[endizs]

SWEET! Can I kiss you now, or later...

HTT @ 250, Stock voltage (1.40), divider at 333, stock HT multiplier (5x), stock HSF.

CPU @ 2.25ghz. Trying prime for the night.

Thanks dude, I really appreciate it.

Any other good tips? =D

 

[chronokefka]

You should push the HT multi down to x4... standard HT is 1GHz, running the board above that may cause stability issues. For your ram, I'd only push up the voltage if once you start going above the stock speeds, or trying to get tighter timings. Run MemTest86+ and see if any errors crop up after a full test, and only increase the voltage if they do. No point in making your ram live less if there is no need.

My own ram is pissing me off though, 2-2-2-5 stock voltage at 203, but the next divider up is 250, and it won't post at any timings tighter than 3-3-3-5, max voltage.

 

[kawsy]

I don't have a floppy in my system. What exactly is the problem this causes? Would I perhaps be able to overclock higher if I added a floppy to the system or at least told it there was one?

 

[endizs]

No, you don't exactly have to add a floppy. Just don't disable it in bios.

 

[pedramrezai]

The new 1010.004 caused some instablity for me. in farcry I experienced frequent vpu recover as my sapphire X550 is quite sensitive to oc'ing and PEG link caused the issue.Disabling PEG link did not solve the problem with 1010.004.Downgrading to 1010.003 resolved the issue.I wonder if anyone else has same problems.

 

[Victek]

Originally posted by: pedramrezai
The new 1010.004 caused some instablity for me. in farcry I experienced frequent vpu recover as my sapphire X550 is quite sensitive to oc'ing and PEG link caused the issue.Disabling PEG link did not solve the problem with 1010.004.Downgrading to 1010.003 resolved the issue.I wonder if anyone else has same problems.

Yes, I have some mouse lag, BSOD indicating ftdisk.sys fails (I'm runing RAID0) and finaly the sytem frozen. Back to 1010.03 and everything smoth. No OC.

 

[con4cyn]

I was just wondering if anyone else has heard of this. I just built my new system about three weeks ago, and I just decided to update my chipset drivers. I tried to update the drivers from both the Asus website and Nvidia site. But, after I reboot after the install my computer loads windows, but then says there's a hardware problem where it dumps physical memory. Then it reboots. And, it will continue to do this unless I go into Safe Mode, and disable the DHCP Client Service in msconfig. Then I'm unable to get online. The only way I can fix this problem is by reinstalling the drivers fromt he CD I got with my board. Has anyone else heard of this? Is there a way to update my drivers without this problem happening?

Asus A8N-E
AMD 64 3200+ 2.0ghz
Windows XP Service Pack 2
Nvidia Geforce MX400

 

[GoeniGoeGoe]

yeah you probably need to upgrade to a newer bios version. Had the same problem with sata/raid drivers. they wouldnt work with older bios-es.

 

[Gerbil333]

Okay, here's my first "problem," if it can be called that. My A8N-E v2.0 began overclocking itself yesterday. I've had it for about six months and I'm still using BIOS 1005, which I loaded after building the system. It's been running stock since day 1.

Yesterday I updated the drivers for the first time to eliminate a simple Java/ATI bug (which worked, btw). I installed the Catalyst 5.12 drivers along with the required .NET framework 1.1, and the latest nForce 6.70 chipset drivers, minus the IDE drivers.

The computer is running fine. However, I noticed a large 3DMark 2001 score increase of about 1100 points. It turns out my Venice 3200+ was running at 10x217 according to every program I tried. I rebooted and it returned to its stock speed.

Just now I installed some updates and when I rebooted I noticed that System Properties reported my CPU speed to be 2.16GHz. Everest shows this. I rebooted again and it had no effect, so I'm typing with the CPU at 2.16GHz.

What the heck!? I haven't even looked at the BIOS settings since June! At least my hardware seems to be able to handle it. I might run some stress testing and ignore the bug...

Update #1: I've now rebooted at least five times and checked my BIOS settings. It's still set to 10x200Mhz, yet the computer is consistenty booting up at 10x215.98MHz. I can't get it to return to stock speed!

Edit #2: The OS/drivers have nothing to do with the bug. I used memtest86+ to verify this. I rebooted and let memtest86+ run for {0 < x 60} seconds. I repeated this, and on the seventh try, memtest reported the CPU speed as 2160MHz instead of the usual 2010 or 2015MHz. Further reboots resulted in 2160MHz as well. I ran 45 minutes of memtest at the OC'ed speed and it did okay...so at least I know it's stable enough for general tasks.

I flashed to BIOS 1008 using a floppy disc and the commands to totally rewrite the BIOS as discussed way, way above in this thread. That didn't help either. Using memtest86, my computer booted up at 2160MHz right after flashing the BIOS and entering my settings.

My hypothesis: Over the semester, I've booted my computer up and left it running 24x7 until I left my dorm for the weekend. Often, it stayed on constantly for 2-3 weeks.
It always booted up at stock speeds throughout the semester, but I only booted it once. It seems to OC itself after rebooting--but not on cold boots.

I did a short experiment. The system was running Windows at 2160MHz. I shut the computer down, waited roughly 30 seconds, and turned it back on. It's now at 2010MHz.

 

[con4cyn]

Originally posted by: GoeniGoeGoe
yeah you probably need to upgrade to a newer bios version. Had the same problem with sata/raid drivers. they wouldnt work with older bios-es.

So, even though it states on the Asus site to install the chipset first I need to update my bios first then update my chipset driver?

 

[corsa]

Ok, just for curiosity's sake, I have a temp probe (Bell digi-thermo) very accurate..... so i thought I might like to see what my Zalman heat sink was reading, as I do notice it is hot too touch, running stock.
So probe is about 100mm long, and i push it into the heat sink, not quite touching the base where it sits comfortably, case door is off, now onto my finding's

Ambient temp : 27C
Ambient temp inside case : 29C
Asus PC Probe : 34C
Bell digi-thermo : +50C :shocked: (probes max range is 50C)

The temp when measured rises quickly and I would think its atleast in the high 50's
Now this is not what I would call accurate? should we be worried about this? I would think so as we are talking up to +50C on the heat sink, why are we being fooled here, I would hate to know what its reading on die......any thoughts?

 

[blurp]

Originally posted by: corsa
Ok, just for curiosity's sake, I have a temp probe (Bell digi-thermo) very accurate..... so i thought I might like to see what my Zalman heat sink was reading, as I do notice it is hot too touch, running stock.
So probe is about 100mm long, and i push it into the heat sink, not quite touching the base where it sits comfortably, case door is off, now onto my finding's

Ambient temp : 27C
Ambient temp inside case : 29C
Asus PC Probe : 34C
Bell digi-thermo : +50C :shocked: (probes max range is 50C)

The temp when measured rises quickly and I would think its atleast in the high 50's
Now this is not what I would call accurate? should we be worried about this? I would think so as we are talking up to +50C on the heat sink, why are we being fooled here, I would hate to know what its reading on die......any thoughts?

Corsa,

I read many times that the temp sensor for most NF4 MoBos like the A8N-E is not placed on the Chipset. It is more of an ambient mobo sensor and it is worth nothing as you very well pointed out. Many guys noticed that when touching the Zalman HS, noting it was fairly hot.

 

[Plester]

love this board - 3200+ venice stable at 333x8.5(2.83ghz), 1.62v, mem divider at 333 - 2T (ddr 514), HT multiplier 3x, watercooled.

 

[pedramrezai]

My bios ca go up to 1.55v. how 1.62 is possible.maybe hard mod.

 

[cabroker]

Originally posted by: pedramrezai
My bios ca go up to 1.55v. how 1.62 is possible.maybe hard mod.

I don't believe any of the bios versions went above 1.55v. At least all that I have tried.

 

[Unkno]

I need help, I keep getting random BSOD and freezes during bootup.

Specs:
A8N-E Rev. A02 w/ ZN-47J NB cooler
Bios: 1008
Chipset Version: Nvidia 6.70
X2 3800+ Currently set to stock
ATI X800GTO2
OCZ EL Platnium 2X1024mb (memtest stable for 16hours)
Antec Sonata II w/ 450W PSU


My system would sometimes get BSOD during bootup and i would have to restart it a few times and it would be able to get into windows. Once i get into windows, everything seems to be stable (can pass prime95). I have tried setting the floppy to enable or disable but no difference. I've tried fresh installation of windows xp with SP2 around 5 times and it always ends up BSOD....

 

[pedramrezai]

final 1010 is finally out.

 

[Unkno]

anyone know what the differences the new 1010 compared to 1008 are?

 

[blurp]

Installed 1010 Final. Works fine ... as 1010 beta 4 did for me. Way to go Asus. No problem at All.

 

[Unkno]

does the new bios 1010 fix any stability problem or any other features?

 

[imported_vernsh]

I have a problem with 2GB of memory. With 1G installed, the POST message says the memory is DDR400, but with 2G installed, it says 333. I'm using the new 1010 BIOS. Is there a setting in BIOS to correct this? The system is a lot more stable with 1G.

 

[imported_vernsh]

I should probably give my complete configuration

System runs great with 1GB MEM at DDR400
Many BSODs with 2GB memory at DDR333





----------------------------------------
AMD 64 X2 4400+
MSI NS7800 GTX
2GB DDR Corsair Memory
300GB SATA HD
SoundBlaster Audigy 2 Platinum

 

[ProviaFan]

Originally posted by: vernsh
I have a problem with 2GB of memory. With 1G installed, the POST message says the memory is DDR400, but with 2G installed, it says 333. I'm using the new 1010 BIOS. Is there a setting in BIOS to correct this? The system is a lot more stable with 1G.

Are you using 2GB as four 512MB modules? When four modules are used, the memory has to drop down to DDR333 speed due to the physical limitation of the memory controller. However, you should not experience instability with four modules unless perhaps one of them is bad...

 

[imported_vernsh]

QUOTE
Are you using 2GB as four 512MB modules? When four modules are used, the memory has to drop down to DDR333 speed due to the physical limitation of the memory controller. However, you should not experience instability with four modules unless perhaps one of them is bad...

Yes, I have 4-512 sticks. Is the limitation in the hardware or software? It's very disappointing if it's hardware. I was having a lot of instability problems before upgrading my bios and drivers. I really haven't tried using 4 sticks since I noticed the DDR333 message. Do you know what if any performance hit the problem causes?