boot problem
in [Hardware]
|
Prev: beep code error
Next: P4 Bus Speed ???
From: kony on 15 May 2005 08:20 On Sun, 15 May 2005 10:46:38 GMT, spam(a)spamcop.com (Bob) wrote: >On Sun, 15 May 2005 02:59:50 GMT, kony <spam(a)spam.com> wrote: > >>CPUs simply do not fail >>on their own > >I fried a K6-II once. Dust in the heat sink. > ... goes back to what I wrote, that there is some external problem already present, causing it's failure. Such things are almost always obvious upon visual inspection of the box.
From: kony on 15 May 2005 08:26 On Sun, 15 May 2005 10:49:10 GMT, spam(a)spamcop.com (Bob) wrote: >On Sun, 15 May 2005 06:19:49 -0400, "/\\/\\UF/-\\S/-\\" ><aviator2k(a)netscape.net> wrote: > >>I agree with kony. Check the mobo for leaky caps! If by chance you have an >>EpoX mobo, look no further... > >Please elaborate. I have an Epox MB and it has been acting flaky - or >at least that is the best opinion thus far. It seems to behave flaky >when it gets hot. > >Mine is the Epox EP-MVP3G-M. > Ironicially bad caps actually work better when too hot (though die even quicker, towards the end that they don't work well cool). Temp related changes would likely be a mechanical problem, like memory, card or cable contacts, or an overheating north or southbridge of not CPU or video card. MVP3 is a pretty old board at this point though, if it had been used in a dirty environment previously then the contacts could easily be fouled at this point in time, or due to it's lower-cost (relative to some other contemporary boards of that era) construction it could indeed have bad caps too... most suspect would be those on the top corner near the CPU socket. Super-7 was also picky about video cards, if the AGP bus is flaky then little extra heat could be enough... you didn't mention exactly what "flaky" means, how that's manifested.
From: Bob on 15 May 2005 09:11 On Sun, 15 May 2005 12:26:59 GMT, kony <spam(a)spam.com> wrote: >>Mine is the Epox EP-MVP3G-M. >you didn't >mention exactly what "flaky" means, how that's manifested. I discussed it at length in the thread entitled Error: INACCESSIBLE BOOT RECORD" According to the experts, the MB is the likely culprit. Briefly what happened is it started getting hot and humid but not enough to run the a/c that morning. The mouse stopped working and the POST report of RAM was one stick short. Then I noticed certain INI files being corrupted. I had to use the keyboard to navigate, which is really lame. So I shut down and took the last stick of RAM out. I also tried a different mouse. Nothing helped. So I quit working on it and got another box to rebuild. The next day, after the house cooled off from running the a/c, I tried the machine and this time it worked. I put the stick of RAM back in and it worked. I then proceeded to recover the boot drive from an archive I had created the week before on a removable drive using Drive Image Pro 4.0. That's when I ran into the inaccessible boot device error and had to use Win2K IPU to get running again. I thought it was the power supply since I cleaned it with compressed air and it was exceptionally dirty. The MB was not all that dirty since I had cleaned it about a month earlier. I am decommissioning that old machine and building a new one which will be ready this coming week. I may use the old machine as a backup - I have a spare port on my router. I am going to evaluate the Enermax 352 RAID backup system. It may work in which I will keep it. If it doesn't then it goes back. I hope it works because it is a very handy way to make disaster recovery archives using hard disks. -- Map of the Vast Right Wing Conspiracy http://home.houston.rr.com/rkba/vrwc.html "Our country's a place of limitless hopes and possibilities, and nowhere is that spirit more alive than in the great nation of Texas." --GW Bush, U.S. President from Texas "One thing that makes George Bush such a great president is that he does not govern according to public opinion polls." --John Cornyn, U.S. Senator from Texas
From: "Christo" <lessthanchris666no on 15 May 2005 20:26 "kony" <spam(a)spam.com> wrote in message news:l46d81pu7dufl1hg6pi9u1ajqjfiornf82(a)4ax.com... > On Sun, 15 May 2005 07:29:29 +0800, "jg" > <jgs(a)westnet.com.au> wrote: > >>My computer has suddenly refused to boot up. (Athlon 1.2Gh, XP Pro) >>The power lights and fans go on but thats it. No beeps or anything. >>Nothing on the monitor except "DPMS going to sleep", then black. >>I tried several other monitors and the same thing. >>All cables are ok. >>So ..... does it look like motherboard or CPU? or something else? >>Thanks for any opinions. >> >> > > Not CPU unless the heatsink had fallen off or it's fan had > failed. With an obvious problem a CPU almost never fails > before (most of a system). > Kony, i got an MSI board and it came with D-Bracket LEDs that indicate whats up with system, dont know if your aware of it? I had a similar problem, My computer was powering on good but no bios beeps at startupm and a no signal to monitor So i spent 30 minutes reading board manual and remembered the d-bracket, i checked it and it indicated something up with the CPU (AMD 2600+) anyhow i took the CPU out and re seated it and plopped HS/fan back on and it worked, all worked good. So... CPU is a possibility, anything is when it comes to hardware issues, I wouldn't rule things out, however saying that I know your a genius when it comes to this kinda stuff... and just had to point out my past experience, it might be an idea for the OP to try re seating the CPU and memory, to fault find. > Check the motherboard for failed capacitors. Signs include > domed or vented tops, leaky liquid or residue on top or > bottoms. If there is no outward sign of cap problems then > I'd begin focusing on the power supply, taking voltage > readings with multimeter and replacing it with a spare if > you have one available. > > Also clear CMOS as Mickey suggested.
From: kony on 15 May 2005 23:59
On Mon, 16 May 2005 00:26:55 +0000 (UTC), "Christo" <lessthanchris666no span(a)hotmail.com> wrote: >Kony, i got an MSI board and it came with D-Bracket LEDs that indicate whats >up with system, dont know if your aware of it? I've had some, they're just an oversimplified POST code LED display, kinda like what Epox did but Epox did it one better by having the segmented LED numeric display. > >I had a similar problem, My computer was powering on good but no bios beeps >at startupm and a no signal to monitor > >So i spent 30 minutes reading board manual and remembered the d-bracket, i >checked it and it indicated something up with the CPU (AMD 2600+) anyhow i >took the CPU out and re seated it and plopped HS/fan back on and it worked, >all worked good. > >So... So that's an indicator that it wasn't the CPU, probably a bios glitch, maybe a poorly designed, dirty or defective socket. > >CPU is a possibility, anything is when it comes to hardware issues, I >wouldn't rule things out, however saying that I know your a genius when it >comes to this kinda stuff... and just had to point out my past experience, >it might be an idea for the OP to try re seating the CPU and memory, to >fault find. Well I am making a distinction when it comes to "CPU". That distinction is that the CPU wouldn't typically "fail" by itself. That doesn't necessarily mean something related to the CPU isn't at issue, nor that a CPU can't fail with external forces or deficiencies. I suppose my main point should be that these external forces are almost always obvious upon inspection of the system. Of all the things that might go wrong that a user can't discern with conventional troubleshooting methods, the CPU is among the last part to suspect when nothing related appears amiss. |