| |||||||
| Register | FAQ | Members List | Calendar | Arcade | Search | Today's Posts | Mark Forums Read |
| EPoX MotherBoards EPoX Intel and AMD Motherboards. |
![]() |
| | LinkBack | Thread Tools | Rate Thread |
| |||
| No Display & Mobo Failure Codes Hi all, Mobo model: EP-9NPA+Ultra I've been having a problem. At first, I thought the fan was it, so I got a new one, but that didn't fix it. The real problem is that when I start up my computer, nothing shows up on the monitor, nothing at all. Not even the boot screen. Looking on the motherboard, I see the following codes on the 7-segment display as soon as it starts up: FF - for a half second 44 - for a half second FF - for a half second 44 - for a half second C1 - it stops here and doesn't change. I've taken out all the RAM, disconnected all IDE cables, taken out all PCI cards. So the only things that are connected to the motherboard now are power and the graphics card in the PCI-x slot. I'm really stumped and would really like to get this resolved as quickly as possibe. Is the motherboard toasted? Is there something I can fix? Thanks for any help, Walter
__________________ |
| |||
| Just tried your suggestion. I have 4 sticks of RAM, and I tried at least 2 of them in each slot, individually. I tried some in pairs, in different slots. Each time I got the exact same error behavior. Same error codes, same symptoms (eg. no video). What else can I try? And thanks for your help. -Walter
__________________ Last edited by whiskeybravo : 31st March, 2008 at 08:49 PM. |
| ||||
| Pull the video card, so that all you have is the CPU and the power, then power the machine up and see if you get a beep or POST code complaining about the lack of video card or RAM. Every mobo I've seen in the last 15 years will give you a POST code for one of those two conditions.
__________________ Avatar and sig graphic by Pitch. Subscribers! Ask about a custom graphic or avatar today! Gizmo Thermal Diode Mod and Direct-Die Water Block 8-Cheetah 18GiB U-2 SCSI MegaRAID Enterprise 1500/128MiB Samsung SyncMaster 955DF TTGI/Superflower TTS-520 PSU ![]() ![]() ![]() |
| ||||
| BTW, your manual should tell you what those codes mean....
__________________ Avatar and sig graphic by Pitch. Subscribers! Ask about a custom graphic or avatar today! Gizmo Thermal Diode Mod and Direct-Die Water Block 8-Cheetah 18GiB U-2 SCSI MegaRAID Enterprise 1500/128MiB Samsung SyncMaster 955DF TTGI/Superflower TTS-520 PSU ![]() ![]() ![]() |
| |||
| As soon as I get home from work I'll try your suggestion. As for the manual telling me the definition of the codes... it wasn't very helpful. It's been awhile since I looked at it, but C1 said something about memory. None of the codes were very specific. So that's why I'm here ![]() Thanks again for your help, and if you have any other ideas, please let me know!
__________________ |
| |||
| Ok. I did what you suggested Gizmo. I removed the video card and I got a beep. Now what? Also, I looked at the manual again... to see what the codes mean. So let's take this code by code: POST Code FF Possible Problems 1. BIOS chip inserted incorrectly 2. Incorrect BIOS update version 3. Mainboard problem 4. Add-on card inserted incorrectly Solution 1. Reinsert the BIOS chip 2. Download the correct BIOS version update from the manufacturer's Web site. 3. Replace mainboard 4. Remove and replace the add-on card Alrighty then... I've never touched the BIOS chip so problems (1) and (2) are unlikely. (4) is also out of the loop because I removed everything. So we're left with (3), how descriptive. As for the solutions, I'll admit I have not tried (1) or (2). I have done (4), and (3) is obviously something I'm trying to avoid, especially since this company apparently doesn't exist anymore. ------------ POST Code C1 Possible Problems 1. Memory module inserted incorrectly 2. Memory compatibility problem 3. Memory module damaged Solutions 1. Reinsert memory module 2. Replace memory with correct type 3. Replace memory module Problem (2) isn't likely since this computer has been running fine since the day I built it 3 years ago. Plus I made sure to get compatible RAM. (1) and (3) are unlikely, but let's test them out anyway. I reinserted the memory modules in a whole bunch of different configurations with no change in error behavior (1). (2) is unnecessary. And (3) I have not done because it seems very unlikely to me that all 4 memory modules simultaneously stopped working and all 4 memory slots on the mainboard simultaneously stopped working. ------------ POST Code 44 is listed as "Reserved" in the Appendix. So besides replacing all of my RAM or my mainboard, I was wondering what other problems I might have. If you think that I just need to suck it up and replace my mainboard, let me know, great excuse to get a new system I suppose. Thanks again for the ideas, W
__________________ |
| ||||
| Ok, the FF code is actually a reset code. It is what the machine sets the LED code to when it performs a reset or first starts up. It is only relevant if you never get the machine to change the status of that display. Since that is not the case here, it is irrelevant. The beep tells me that at the very least, the CPU is coming up and executing the BIOS POST code, so we know that at least SOME of the mobo is actually working. C1 tells us that it's not able to properly access the RAM, but I suspect that it's more a symptom than the actual problem, given the troubleshooting steps you've described above, and what I have seen other people report with Epox boards in the past. It's probable that the 'reserved' (I love those ) 44 POST code is telling you that it wasn't able to initialize some chipset register properly.Basically, it sounds to me like your mobo is toast. One thing you might do is look around on the mobo for any bulging capacitors that have brown stuff oozing out of them. If you do, then you might be able to resurrect the board with a cap change.
__________________ Avatar and sig graphic by Pitch. Subscribers! Ask about a custom graphic or avatar today! Gizmo Thermal Diode Mod and Direct-Die Water Block 8-Cheetah 18GiB U-2 SCSI MegaRAID Enterprise 1500/128MiB Samsung SyncMaster 955DF TTGI/Superflower TTS-520 PSU ![]() ![]() ![]() Last edited by Gizmo : 1st April, 2008 at 08:56 PM. |
| ||||
| LOL Cloasters must have posted while I was editing my post, 'cause we were both apparently thinking along the same lines....
__________________ Avatar and sig graphic by Pitch. Subscribers! Ask about a custom graphic or avatar today! Gizmo Thermal Diode Mod and Direct-Die Water Block 8-Cheetah 18GiB U-2 SCSI MegaRAID Enterprise 1500/128MiB Samsung SyncMaster 955DF TTGI/Superflower TTS-520 PSU ![]() ![]() ![]() |
| |||
| Thanks both of you for your responses. I did already look for blown capacitors with a fine tooth flashlight and did not find any goo ![]() So I guess it's time to upgrade! Quick question then... all the mobos these days are DDR2 capable at a minimum, can I still use my old DDR RAM? Thanks again for the help, W
__________________ |
| ||||
| DDR RAM won't even fit in a DDR2 slot, so the answer to that would be no. However, I believe there are some mobos that have both DDR and DDR2 slots, allowing you to use either type of RAM. They tend to be rather more expensive and rather less feature rich than their DDR2-only counterparts, though, from what I've read.
__________________ Avatar and sig graphic by Pitch. Subscribers! Ask about a custom graphic or avatar today! Gizmo Thermal Diode Mod and Direct-Die Water Block 8-Cheetah 18GiB U-2 SCSI MegaRAID Enterprise 1500/128MiB Samsung SyncMaster 955DF TTGI/Superflower TTS-520 PSU ![]() ![]() ![]() |
| ||||
| I really wouldn't think so..........then again, I HAVE seen a hosed CMOS cause some pretty strange things to happen......
__________________ Avatar and sig graphic by Pitch. Subscribers! Ask about a custom graphic or avatar today! Gizmo Thermal Diode Mod and Direct-Die Water Block 8-Cheetah 18GiB U-2 SCSI MegaRAID Enterprise 1500/128MiB Samsung SyncMaster 955DF TTGI/Superflower TTS-520 PSU ![]() ![]() ![]() |
| |||
| Have you tried resetting the cmos with the jumper. I had a similar prob with a newer board the other day and ended up getting a new processor over the ordeal and when I woke up the next morning I reset the cmos again for the umpteenth time and it finally took. I now have an extra CPU for a new build for my pops though.
__________________ |