-
Help me Please! 8KHA+
I hope someone can help, 8KHA+ motherboard that has decided to reboot by itself?? tought it might be a power poblem so i removed 1 stick of ram 2 case fans and 1 cd rom..still same problem..First time I switched it on it switched itself straight off??
Switched it back on then it came upto the boot screen..then just hang there debug tool had code 6 d on it and I can't find what this means anywhere??
Can anybody please please help me with this...
Thank you in advance
P.S Sorry if this had already been posted...
8KHA+ rev 2.0 with latest BIOS(The added support 2400+ etc)
1700+ XP
512MB DDR in 2 strips of 256MB
Geforce3 Ti200 64MB DDR
16x DVD
CD-RW
Soundblaster Live 5.1 Player
SMC Network card
Was Win2000 now 98(Thought it was 2000 was the problem)
It's better to burnout than fade away!
-
Is it a new build or are you just recently experiencing problems.
Am at work at the moment when I get home I'll check my manual for the error code.
Win XP Pro SP3
AMD Athlon 64 5000+ Black edition
2 Gb DDR2 Transcend Ram (2x 1 Gb)
Gigabyte GA-MA770-DS3
Peak Radeon HD3870
-
It's about 8 months old..and just started doing this in the last couple of weeks..
Worked fine without any problems at all..I have checked my manual and can't find any reference to the 6 d code and aslo checked Epox website which is as useful as a chocolate fireguard.
Any info would be greatly received
It's better to burnout than fade away!
-
Member
Wizard101uk:
Aside from C1 and a few other indicators, I've not found the "debug" tool all that helpful. And, likewise, I'm at work and can't check my manual until I get home. Have you checked the obvious stuff like fan failure? To verify if it were an o/s problem, you could just go into bios (or possibly DOS) and see if it locks up there. What's the temps/volts in bios? When you switched back to Win 98, did you try and load the 4 in 1s? I'd also consider reseating cards and touching the CPU heatsink to see if it were getting hot while running. If heat inside the box were a problem, you could remove the case cover and use a house fan to blow inside to see if that reduces the problem. If it does, then you know what needs to be done. If you don't get an answer about the code, there's an Epox tech who frequently visits amdmb.com under the Epox m/b forum. He might be able to explain it.
Biglaker
-
Can't find what the debug code 6 D means either, I'd try mailing Epox for an answer unless anyone else knows what it means.
Perhaps worth a shot, have you tried clearing the cmos and boot up again.
Win XP Pro SP3
AMD Athlon 64 5000+ Black edition
2 Gb DDR2 Transcend Ram (2x 1 Gb)
Gigabyte GA-MA770-DS3
Peak Radeon HD3870
-
Hi there folks,
I have emailed Epox tech asking them what's going on, but I'm not expecting a quick reply(If anything like Chaintech)
Temp inside is system is about 30 C and the CPU is 35 C under full load.
I haven't got the voltage yet, but when I do I post them .
I have loaded all the drivers all the latest I can find..still doing the rebooting thing.
CPU heatsink isn't getting that hot I can touch it and keep my hand on it..
No fan failures at all..also tried clearing cmos and loading fail safe settings...still nothing.
It's better to burnout than fade away!
-
Member
Wizard101uk:
Here's a link for 8kHA+ setup which may or may not help. It was originally written late last year but many people have added more detail. I used it when I setup mine. The one piece of info that I'm not sure it mentioned was making sure you set the jbat jumper for 133 if you're CPU is an XP. The manual says 100 is the default.
http://www.amdforums.com/showthread.php?threadid=79836
Anyway, seems like you would now have the opportunity to get the voltages since it doesn't want to load windows. What first needs to be determined is - is there a hardware problem or software. So, my earlier question about the machine's ability to not lockup while in bios (or even better in DOS) was an attempt to try and eliminate Windows setup/driver errors as the cause of the lockup. If the machine will load say DOS and continue to run, then we could be more comfortable about whether or not the problem is with the operating system and/or setup vs. a malfunctioning piece of hardware. Would you try doing that much if you can- run it in DOS for say 1/2 hour to see if it locks up or shuts down and we can go on from there.
By the way, what version do you have for bios? I know that earlier versions of the 8kha+ had problems that were sometimes solved with an updated bios.
Biglaker
-
Ah yes, the great old 8-KHA+. Reboots, eh? Check the ATX power connector. It spontaneously loosens itself up after a while; you may want to use needle-nose pliers to tighten the PSU's connector. Any small movement while the system is on will otherwise cause a disconnection and a reboot even if you don't touch the case at all
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Forum Rules
|
New Security Features Planned for Firefox 4
Another Laptop Theft Exposes 21K Patients' Data
Oracle Hits to Road to Pitch Data Center Plans
Microsoft Preps Array of Windows Patches
Microsoft Nears IE9 Beta With Final Preview
Simplified Analytics Improve CRM, BI Tools
Android Passes RIM as Top Mobile OS in 2Q
VMware Updates Hyperic System Management
File Monitoring Key to Enterprise Security
LinkedIn Snaps Up SaaS Player mSpoke
|
Bookmarks