• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Asus A7V333 and Athlon XP chips : Important

G

Genocidus

Junior Member
I bought an Asus A7V333 and an Athlon XP 1700+ and its given me no end of trouble.

Firstly it wont let me clock it above 1100 (10x100) , if you try and place it at 1466 hz (11x133) it hangs and the vocal thing says that the CPU is erroring cos its overclocked. At 1100 its stable (or so youd think)

The Windows Xp that was already on the hard drive gives me a BSOD so i try to reinstall XP. I get as far as the terms and conditions and withotu fail the machine powers itself off.

I have looked in thsi forum and found that ASUS boards seems to be complete C*ap when it comes to Athlon XP chips. Apparently im not teh only one experienceing this kind of instability. I flashed teh bios up to 1004 and it still gives me the same problems.

Can anyone help? Or do i have to send it back?

Any advice would be greatly appreciated
 
isn't there a jumper on the motherboard to change FSB to 133
on the kt133a board it surely was a jumper for that
that would also explains the message that the pc is overclocked :-?
 
I cant seem to find it in the manual? ISnt the jumperfree feature supposed to allow you to change that without having to mess around with jumpers?
 
Sounds like you have a heat issue if you flashed the BIOS already, make sure you have that hsf on there right. If all else fails just get a new board,and or a differnt brand. Either way the KT333 is a new chipset, and new chipsets almost always have bugs that need to be worked out.
 
i'm sure its a fsb setting on the motherboard...you probably have to find the jumper to move it from the 100 to the 133mhz

i had the same problem with my fic an11...the default jumper that was set was on 100mhz then i changed it and it recognized my cpu as xp1700

hold on...i'm downloading the manual and see if i could find it for you.

EDIT Seems like asus' ftp website is down and i can't download the manual...but just look carefully through the manual...good luck! hmmm...maybe it doesn't have the jumpers...good luck anyways.

If you still can't find it...try setting the fsb manually with the dip switches
 
yes u can run the mem asyc with the bus 166/133 - performance isn't as good as when using 133/133. if u have unlocked u'r xp or u got an mp u can run it @ 166/166
open u'r case up and find the jumper! there will be some dialogue near the jumper telling your the diff settings. i had the same trouble with my kta3.
 
Here is some more information

The motherbaord temp is 21 degrees
The CPU is 44 degrees

So that blows out the overheat theory (unless 44 is a bit high)

The DDR settings are

sdram config BY SPD
CAS latency 2.5T DDR
RAS to CAS delay 3T
RAS PRecharge 3T
Active precharge 3T

i have discerned that the board multiplier is set at x11. If i go to jumper mode and place the dips switches to 11hz the system powers up, if i change the switches to 133 (133x11) then the chip is running at its true speed of 1.45ghz. But this stops the machien booting up and once more i have to revert to 100hz before the machine boots properly. It refuses to recongise the 133 setting, period.

its looking a lot like im gonna have to send it back arent I? 🙂
 
I've never heard of Asus boards having many problems at all, not to mention athlon XPs. Mine is stable.

Have you tried to replace the memory? Maybe you got a bad stick, asus boards are often picky about what type they get.
 
i live in the UK and its been out here just recently, its looking like im gonna have to send it back. I cant tell if is the chip that wont allow itself to be set to 133 or teh board 🙁
 
before you send it back, did you go through the manual step by step and make sure everything is done? Did you swap your memory with someone elses to check?

I highly doubt its the board or the cpu, the problem is in the set up or something else.
 
Could you please let us know if it was the board or cpu? I'm asking because we just put together a A7V333 + Raid, 1900 XP, 256mb Mushkin 2700 and the thing won't run at anything but 1200. If we set it at anything other than 1200 we get the "System failed due to cpu overclocking" message. I'm starting to think it's maybe a heat (running at 69 C) or power supply issue, but I'm not totally sold on it yet since it isn't locking up, and even when it's cold it refuses to boot at anything other than 1200 (if you check the temperature following that blasted "system failed" message it will only be around 40 C.)
 
Hi Genocidus

In case you decided to switch to MSI, you will be freed from jumpers problem.

I just bought MSI KT3-Ultra ARU with VIA KT333 chipset, however, getting the system up till now @ 5056 via 3dmark2001se (for Xp with DirectX8.1), is not without problem. Somehow the score is not the only test, the real test is you must pass the Demo test!

Just like to share some pain that I had gone through.

first, after loading the win xp, must download and install all the critical updates from MS window updates, there are 16 of them, better have broadband to save some pain.

then, you must download direct X 8.1 , make sure is for xp, with these 2, my initial 3dmark score improve from 1500 to 45xx.

System overclock 136 x 12 at the moment for Athlon 1700+, still filling unhappy about only able to oc to 1800+ (using ddr sram, CAS 2522)

Then I went to overclocking my AGP nVidia GF2 Ti 200 DDR 64Mb, core frequecy 266, mem speed 433, still trying to find the sweet spot.

Nice thing about this MSI KT3 is its Fuzzy logic, helps to overclock automatically, it will not hang but reset computer automatically while system is not stable.

Xp is still a very difficult OS to work with, it is not hardware friendly though.

Happy tuning....


 
I just put together a system last night with the A7V333 / Athlon XP 1900 / Corsair Memory. Everything seems to boot up fine. CPU is recognized with no problems. I am having a problem getting the RAID to work with my 2-WD 120GB drives, but that is for another thread. I am also using the stock heatsink and fan that came with the CPU. I haven't had a chance to burn it in to make sure there aren't any problems.

Just my $0.02 worth.
 
Ive been reading the problems people were having with this board, and was a little nervous because I had just ordered one. Well all the parts came in yesterday: 1800XP chip, AsusA7V333, and 256 kb Samsung 2700 memory. Put everything in a generic case with generic PS. Left all settings and jumpers on default. Fired up board, bios opened and gave me choice of 1533 or 1150. Choose 1533. Saved bios. Put XP os in CD drive, FDisk and format HD. Installed and start XP OS. Radeon 8500 video card drivers installed. Everything running fine... Start 3dMark 2001 run benchmarks.... results: 8758. Took 1 hour 30 min from the time I get the parts home till the time 3D mark quits. Been running Sisoft Sandra burnin and 3dmark 2002 most of today with no hiccups.

This board provided a very easy and straightfoward build for me and is very stable. I have not tried to overclock or change any of the default settings but I am very pleased with this MB.
 
Agreed w/ Davidwiz. This board has been fantastic to work with. Just tried some simple FSB overclocking and hit 1812 (12.5x145) with my 2000+ with no effort. Got flaky after that, but I haven't played with Vcore or unlocked CPU yet.

RAID setup can be tricky on this board, also using the RAID IDE for other drives not in RAID configuration is kind of a pain. Check out the Asus forums at Amdmb.com for help with this.
 
....Ok i also had problems when I got my A7v333-r. Now...I eventually pinned it down to where I put my ram. I had it in slot 1 and 2 (2 x256 ddr) and I would error after error after error. Eventually after mcuh frustration I took out the one in slot 2 and put it in slot 3. Seemed to have fixed it (as I had no errors yet). Well..maybe this can help someone.

chuta
 
Chuta, I had the identical problem. Personally, I think the first memory bank is too close to the HSF and gets too hot. Did the same as you and all is well so far. 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top