Via EPIA M 10000 Long Beep codes.

**IntellaWorks** · 05-20-2005, 07:02 AM

Hey guys, just looking for a few suggestions here.

I was messing around with my carpc in the house, primarily with the OS when I decided to call it a night. I changed something in my nLited OS trying to get a USB-2.5" drive to work which killed the OS (sending it into a restarting loop) So I shut my pc down for the night as it was getting late.

I started working on the machine a day or two later except the machine gives long never ending beep codes, which is a different condition than the one I previously thought i'd be working on.

I've cleared the CMOS settings by shorting pins 1 & 2, checked all my video connections. I've reseaded the RAM (even though I know it was previously working in its spot.)

I'm looking for more suggestions here, Could the system board really have died on me ?? This board is like 2 mo. old and has been rarely used. I blew an EPIA M 10000 I had for about a year that took so much abuse with testing and all, and when I blew the board it was my fault completely, I find it hard to belive this one died after shutting it off. I guess I could try adding some new RAM ?? Any other suggestions ?? I'm all ears !

**Peoples** · 05-20-2005, 09:42 AM

"Could the system board really have died on me ?? "

i'm pretty sure the answer to this question is yes. But just to be sure look for a busted/buldging cap on your motherboard. I'm sure you've seen the threads about all VIAs having a 100% cap failure rate over time. Also usb and constant reboots are symptoms of the bad caps on the VIA mobos.

**IntellaWorks** · 05-20-2005, 09:47 AM

I forgot to mention on my first thread that I did indeed check for bad/blown caps and everything seems fine. The reason why I think it went into a restart loop is because of the wrong type of driver for the USB 2.5" device.

I wasn't aware of the VIA's issues you brought up though, so I will research that some more. I think in any event I should be able to get an RMA out of VIA.

edit: after reading your post again, you mean that USB not working properly is a sign of bad caps ?? That would make more sense, because honestly I thought the USB 2.5" drive wouldnt have a problem being seen with my configuration. The device doesn't needs drivers and has never had a problem on ANY XP/98 SE machine (I stole it from work) The only thing that was throwing me off was nLite, its tough to put your finger on the problem with an nLited machine...

**DarquePervert** · 05-20-2005, 01:59 PM

Beep codes indicate something isn't working on a hardware level.
Google for beep codes for your brand of bios (Phoenix, Award, etc.) and you should be able to get a list.

Beep codes are NEVER a good sign.

**linuxguy** · 05-20-2005, 02:02 PM

Originally Posted by DarquePervert

Beep codes are NEVER a good sign.

Nah, beep codes are good, they let you know that the POST was actually able to run. Beep codes tell you something else is wrong...LOL

**Gobby** · 05-20-2005, 02:14 PM

Remove everything from the system hardware wise, reseat the memory and try to boot again with no hard drive or anything connected, only VGA and Keyboard. See if it then boots.

Sounds like maybe dodgy RAM???

**IntellaWorks** · 05-20-2005, 02:19 PM

Originally Posted by UK_MP3Car

Remove everything from the system hardware wise, reseat the memory and try to boot again with no hard drive or anything connected, only VGA and Keyboard. See if it then boots.

Sounds like maybe dodgy RAM???

Did that one too, even reseaded the RAM I researched a bit this morning on the long beep code and it says "memmory" so I'm going to throw a few different sticks in tonight and see what happens.

I hope its just dodgy RAM, its just weird that it happend right in front of me.

**nl4jy** · 05-20-2005, 02:23 PM

switch to a different memory. Maybe the memory is dead on that stick.

**IntellaWorks** · 05-21-2005, 07:55 AM

BAD RAM was the problem, first time I've ever seen RAM DIE in my lap.

**gizmomkr** · 06-12-2005, 11:55 AM

I run into a similar problem but the cause seems strange....

If I use the software menus to shutdown my VIA - everything is fine.
If I use hardware (I.E. ACPI sent by power switch / power supply) the unit still shuts down fine, but the next power up - I get that same LOG bios beeb - stranger yet, If I cintinue to hit the reset button, it will eventually boot.... and everything is fine till the next "hard" power cycle.

I have traded the ram with my dasktop, and both machienes run fine with ethier stick of ram.... The desktop has never had problems boothing... I guess it could be a thermal related issue... I also know the EPIA is VERRY PICKY about ram... someone told me to try some "Coarse AIR" brand... Maybe ill give it a shot.

Intella works - What brand RAM did you replace with ?