Results 1 to 10 of 10

Thread: Via EPIA M 10000 Long Beep codes.

  1. #1
    FLAC IntellaWorks's Avatar
    Join Date
    Jun 2004
    Location
    NH
    Posts
    1,173

    Via EPIA M 10000 Long Beep codes.

    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 !
    Progress [I will seriously never be done!]
    Via EPIA MII
    512MB RAM
    OEM GPS (embedded)
    nLite WinXP pro on
    1GB Extreme III CF card
    Carnetix 1260 startup/ DC-DC regulator
    Software: Still, re-Writing my existing front end in .Net

  2. #2
    My man uses Levitra. Peoples's Avatar
    Join Date
    Dec 2004
    Location
    Maryland
    Posts
    2,024
    "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.
    PC Components:
    Lilliput; XPC/FLEX mobo; 1.7 ghz P4 Mobile;512 DDR; 160 gb HDD; opus 150; slot usb dvd-rw
    My work log

  3. #3
    FLAC IntellaWorks's Avatar
    Join Date
    Jun 2004
    Location
    NH
    Posts
    1,173

    .

    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...
    Progress [I will seriously never be done!]
    Via EPIA MII
    512MB RAM
    OEM GPS (embedded)
    nLite WinXP pro on
    1GB Extreme III CF card
    Carnetix 1260 startup/ DC-DC regulator
    Software: Still, re-Writing my existing front end in .Net

  4. #4
    Neither darque nor pervert DarquePervert's Avatar
    Join Date
    Apr 2004
    Location
    Elsewhere
    Posts
    13,948
    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.
    Have you looked in the FAQ yet?
    How about the Wiki?



    Under normal circumstances, a signature would go here.

  5. #5
    Low Bitrate linuxguy's Avatar
    Join Date
    Dec 2004
    Location
    Alabama
    Posts
    78
    Quote 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
    I had a perfect quote to go here,
    but hell only knows what I did with it....

  6. #6
    Raw Wave
    Join Date
    Jun 2004
    Location
    On the beach
    Posts
    2,223
    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???

  7. #7
    FLAC IntellaWorks's Avatar
    Join Date
    Jun 2004
    Location
    NH
    Posts
    1,173
    Quote 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.
    Progress [I will seriously never be done!]
    Via EPIA MII
    512MB RAM
    OEM GPS (embedded)
    nLite WinXP pro on
    1GB Extreme III CF card
    Carnetix 1260 startup/ DC-DC regulator
    Software: Still, re-Writing my existing front end in .Net

  8. #8
    Maximum Bitrate
    Join Date
    Feb 2004
    Location
    NYC
    Posts
    597
    switch to a different memory. Maybe the memory is dead on that stick.

  9. #9
    FLAC IntellaWorks's Avatar
    Join Date
    Jun 2004
    Location
    NH
    Posts
    1,173

    Solution.

    BAD RAM was the problem, first time I've ever seen RAM DIE in my lap.
    Progress [I will seriously never be done!]
    Via EPIA MII
    512MB RAM
    OEM GPS (embedded)
    nLite WinXP pro on
    1GB Extreme III CF card
    Carnetix 1260 startup/ DC-DC regulator
    Software: Still, re-Writing my existing front end in .Net

  10. #10
    Maximum Bitrate gizmomkr's Avatar
    Join Date
    Dec 2000
    Location
    Smyrna, Ga, USA
    Posts
    778
    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 ?
    Gizmo-
    Techonlogy on Wheels
    http://www.hjnetworks.com/car

Similar Threads

  1. Embedding BSPlayer
    By Needstorage in forum Software & Software Development
    Replies: 17
    Last Post: 01-29-2007, 03:15 AM
  2. Programming Question in VB
    By az1324 in forum Software & Software Development
    Replies: 8
    Last Post: 10-01-2004, 09:24 PM
  3. How do i accomplish this?
    By Danceheaven in forum Software & Software Development
    Replies: 11
    Last Post: 07-19-2004, 04:48 PM
  4. never lose focus
    By marsjell in forum Software & Software Development
    Replies: 21
    Last Post: 08-12-2002, 01:18 PM
  5. serial port shutdown signal
    By moahdib in forum Power Supplies
    Replies: 12
    Last Post: 08-03-2001, 08:52 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •