VOGONS


First post, by Rolling

User metadata
Rank Newbie
Rank
Newbie

I'm trying to resurrect an old Asus CUV4X board, which i found in the basement! 😁

The attachment P1270731.JPG is no longer available

Installed a Pentium III 866 MHz and 128MB SD RAM PC133 but it's stuck with post code C1, no beeps at all.

The attachment P1270732.JPG is no longer available

Without CPU installed, the diagnostics card gives FF, so i assume it's a RAM issue. I tried different slots, cleaned everything and measured the voltage on the ram slots (3.38v). I also tried different SD-RAM modules, but no success. It doesn't matter if a RAM module is plugged in or not, the error stays at C1.

The attachment P1270733.JPG is no longer available

Any hints would be appreciated 😀

Reply 1 of 11, by Karbist

User metadata
Rank Member
Rank
Member

I would check those 3 black capacitors close to the inductor for the memory rail with an ESR meter.
I would also check back of the board for any scratches on the traces between the northbridge and ram slots.
also corrupted bios can cause this issue.

Reply 2 of 11, by zuldan

User metadata
Rank Oldbie
Rank
Oldbie

Try flashing the BIOS

Reply 3 of 11, by Rolling

User metadata
Rank Newbie
Rank
Newbie

I couldn't find any broken traces at first glance. The capacitors will have to wait, since my ESR meter is currently lent to an colleague. 🙁

The corrupted BIOS hint is interesting. I removed the BIOS chip...

The attachment P1270751.JPG is no longer available

...cleaned the pins and tried to reseat it...

The attachment P1270753.JPG is no longer available

...but now i'm only getting FF diagnostics code. It seems the board won't even go to C0/C1 anymore. It doesn't matter if a cmos battery or the chip itself is present.

The attachment P1270752.JPG is no longer available

Is this an indicator, that maybe the chip is toast?

EDIT: Just saw zuldan's post right now. Hate to say, but at the moment i don't even have an EEPROM programmer, so i'll have to finde someone who can flash the latest BIOS for me.

Reply 4 of 11, by SDumas

User metadata
Rank Newbie
Rank
Newbie

What is the voltage on the CR2032 battery ?

I know this is a shot in the dark but try this :

With the motherboard turned off, remove and insert the video card 2 or 3 times to clean any oxidation on the contacts.

And you can try to reset the bios.

Sometimes there are weird things with no logic explanation...

Reply 5 of 11, by Rolling

User metadata
Rank Newbie
Rank
Newbie

Sorry for the late response. I had to find someone in Germany who could flash the BIOS chip for me! 😀

Anyway - even with a newer BIOS version (which should support the installed CPU), i can't even get the Board back to C0/C1 diagnostic error. It doesn't matter if the chip is inserted or not (or CMOS battery is present), it just hangs at FF.

At this point i'm really lost becaus it seems i'm one more step behind than when i started. 😁

Reply 6 of 11, by Rolling

User metadata
Rank Newbie
Rank
Newbie

Progress of some sort...

I cleaned all ports again, reinserted the CMOS chip a coulple of times and now the system seems to at least recognize the chip again. Unfortunately i'm now stuck again at C1 error:

The attachment P1270764.JPG is no longer available

So i'm basically back to square one... 😒

Reply 7 of 11, by analog_programmer

User metadata
Rank Oldbie
Rank
Oldbie

Maybe this link will help: https://blog.theretroweb.com/2024/01/20/award … /#Version_600PG

C0 is for "Early chipset initialization: Disable shadow RAM, L2 cache (socket 7 and below), program basic chipset registers".
C1 id for "Detect memory: Auto detection of DRAM size, type and ECC, auto detection of L2 cache (socket 7 and below)".

I don't know if your POST diagnostic card shows last code of the step at which is triggered the problem or the code for the next step.

I think you can't do anything if the problem is chipset related, so check for any possible problems with SD-RAM - if RAM sticks are healthy/working, contacts of the RAM sticks, contacts in RAM slots, etc.

The word Idiot refers to a person with many ideas, especially stupid and harmful ideas.
This world goes south since everything's run by financiers and economists.
This isn't voice chat, yet some people overusing online communications talk and hear voices.

Reply 8 of 11, by Deunan

User metadata
Rank l33t
Rank
l33t

My 2 cents: The manual for this mobo is oddly specific about RAM sticks: "SDRAMs used must be compatible with the current Intel PC133 SDRAM specifications."
I would suggest trying a different RAM stick. Also I noticed on the photos your JEN jumper is in different positions, so which way is it now? If you disabled the software CPU configuration then you must set DIP switches properly. I don't remember if P3 will allow multiplier changes but with all DIP switches off you are set to 133MHz and 2.0, which it might not like.

Reply 9 of 11, by Rolling

User metadata
Rank Newbie
Rank
Newbie

Sorry for the late response - had some "real life" problems getting in the way of the not so important "fun problems" with retro hardware. ^^ Anyway - i'm still on this project! 😀

The JEN jumper is different in the pictures, because i tried automatic setting or manual setting of bus and CPU frequency but that didn't change anything. I'm convinced that it is a RAM issue, but since i tried couple of different PC133 ram sticks i' starting to think there might be a problem with the slot or some capacitors, as Karbist mentioned.

At the moment the board is a a friends house who is better equipped with tools (and skill) and he's checking some components. I'll post an update, if i know anything new.

Reply 10 of 11, by PcBytes

User metadata
Rank l33t
Rank
l33t

Have you tried PC100/66 sticks too? I know it sounds a bit funny, but I've had PC100 sticks work and PC133 fail with VIA 694.

"Enter at your own peril, past the bolted door..."
Main PC: i5 3470, GB B75M-D3H, 16GB RAM, 2x1TB
98SE : P3 650, Soyo SY-6BA+IV, 384MB RAM, 80GB

Reply 11 of 11, by Rolling

User metadata
Rank Newbie
Rank
Newbie

Just a small updated to give some kind of closure on the issue.

My friend did some more reasearch and we could identify the Northbridge to be at least part of the issue. Reballing the chip solved the problem but now it seems the Southbridge is completely toast and needs to be replaced. Very annoying!

Since at the moment i don't have a suitable replacement part at hand, the project will be put on ice. Will keep you guys updated if anything changes. Would really love to get the board up and running again, but right now the reasonable part of my brain says to keep my hands of that stubborn thing! xD