VOGONS


Reply 20 of 22, by Mondodimotori

User metadata
Rank Member
Rank
Member
AlexZ wrote on 2025-11-10, 21:17:

In my case updating drivers didn't help. I used the same drivers on another board and it worked. 1st 7600 GT had weird graphical glitches and froze (has 2 bloated capacitors), the 2nd just froze (all capacitors look fine). 3rd 7600 GT worked fine on all boards. Archer also saw similar issues with ATI.

Athlon 1400C is really only for KT133A to use for DOS/Windows 98 with ISA. I have a couple of 1200B as those work on KT133.

Lucky Star K7MKLE should work great with ESS Solo 1 in DOS. I have a KLE133 board with integrated Trident VGA and it has Sound Blaster emulation settings in BIOS.

Going back to the GPU (since today ram was stable).

I installed Windows 2000 on this system. Now, except some weird issues where the PC will reboot during Windows loading if I set in bios to initialize "PCI Video" first, If I leave AGP and install Radeon driver, It'll use all the GPUs in the system, showing video output even on the Radeon (not only the IGP). So I just set the 9250 as the main monitor, and just deal with not being able to see the POST screen (since it initialize that one on AGP first).

3dMark2000 still crashes.
Now, on WinMe I couldn't test 3dMark2001 because it would not start, crashing the whole system.
On Win 2000 it does start and... still crashes before completing.

For the LULZ I tested 3dMark 2000 on the Trident Blade 3D IGP. Those single digit frames are GLORIOUS. But, guess what, it still crashes.

So, after testing the GPU on the other 462 system with a 2600+ without issues in both benchmarks, and also confirming that even the IGP has the same issue, I can confidently conclude that the problem is Athlon 1600+ on this MOBO, probably the MOBO not supporting Athlon XPs that well.

Simply put, I don't think that Lucky Star did a great job of stabilizing this mobo for Athlon XPs, considering it was aimed at the low end market that would, probably, limit itself to a Duron (like we did 24 years ago), thus they dropped just a single BIOS update that made sure it POSTED, and called it a day.

Now, I still plan to get another PCI card (if I can find one for cheap enough), even for redundancy, but I'll keep in mind the possibility of getting a slightly slower Athlon 1200C, because while I don't feel that bad in using the 1400c in winter, during the hot summers + the 20 years old PSU, yeah, I sweat more than I should. On top of that, it appears to be quite the collectible CPU, so it would be a shame to cook it instead of preserving it.

PS:
Now I'm curious to know if even the new RAM throwing me temper tantrums was caused by the Athlon XP being not 100% stable. Gotta try that when I put back the old Athlon (or Duron) in.

Reply 21 of 22, by AlexZ

User metadata
Rank Oldbie
Rank
Oldbie

Why don't test the board with Athlon 1400C instead of Athlon XP?

Pentium III 900E,ECS P6BXT-A+,384MB,GeForce FX 5600, Voodoo 2,Yamaha SM718
Athlon 64 3400+,Gigabyte GA-K8NE,2GB,GeForce GTX 275,Audigy 2 ZS
Phenom II X4 955,Gigabyte GA-MA770-UD3,8GB,GeForce GTX 780
Vishera FX-8370,Asus 990FX,32GB,GeForce GTX 980 Ti

Reply 22 of 22, by Mondodimotori

User metadata
Rank Member
Rank
Member
AlexZ wrote on 2025-11-11, 21:14:

Why don't test the board with Athlon 1400C instead of Athlon XP?

Because it's the processor it had before the Athlon XP. I know it works because I've use it for more than a year in it.

I'll probably put it back in while I think what to do with the system.

Unless the motherboard borked itself only after putting in the 1600+, of course.