VERY puzzling question!

  • Thread starter Thread starter Doug
  • Start date Start date
D

Doug

Hey group,

I built this system for a person they keep having the problem of random
reboots. It's like it gets into a reboot cycle where it will do it like 4
or 5 times in a row and finally you just have to shut it down.
==================
Original system:
WinXP Pro SP1
ASUS P3V4X S370
PIII 850 Celery
128 Crucial RAM CL3
SB16 Snd Card
Realtek 10MB LAN
24 CD-ROM
NEC Floppy
ATI 4MB video
Old 10 gig Maxtor (used)
All these parts were just stuff I had laying around. USED
===================
I re-installed the OS thinking that might be it. Nope
I tried to get into the BIOS to see if it was a setting, it then rebooted
while in BIOS, so its not software.
I then figured it was the Motherboard, nope
thought it might be the processor, nope
replaced the RAM with NEW, nope
Figured maybe since the video card was so dated, it might be it, nope
Audio card swapped, nope
LAN card swapped, nope

Basically to cut to the chase, I have swapped EVERYTHING but the case and
the HDD
====================
System is now:
WinXP Pro SP1
DFI CA64 Tulatin Capable (new)
PIII 667 (used)
256 Kingston CL3 RAM (new)
SB Live! (new)
Lynksys LNE100TX (used)
Pioneer 16X DVD (new)
NEC Floppy (new)
ASUS 128 MB 8X AGP (new)
Old 10 gig Maxtor (used)
=====================
I thought about flashing the BIOS thinking that might be it, but it reboots
in the BIOS, I would hate to be in the middle of a flash and have it reboot,
so that's a negative on doing that at this point. I have run out of idea's
on what it could be or what it MIGHT be. I would not think that a HDD
would cause something like this would it? Maybe a shorting case, bad
ground? What in the hell could this be causing this reboot loop hell I'm
in?? It might run perfect for a day or 2 then all of a sudden, reboot,
reboot, reboot, reboot, reboot...........

Any insight as to what this might be would be very very much appreciated!
 
my guess is the adapter for the cpu
if you could get your hands on a slot 1 processor
that would be a way to test it.
 
Both the boards used are S370 and I have replaced the CPU with a proven good
one @667. Both processors are or were S370 also. The processor cooling
seems to be fine also, tempatures all seem normal and the fan keeps on
spinning.

Thanx for the thought though, but I'm sure that's not it, but if you still
think it could be, could you elaborate more?

ANY and ALL thoughts are welcome, keep them coming!! ;)

Doug
 
No, I stand corrected, I did have to use a Slotket on the P3V4X, and
eliminated that with the new board, the DFI CA64 and went with the straight
S370. It's been a couple months since I swapped the board, had to think
about that again.

Regards,

Doug
 
I would remove every single card in the system, install a single memory
module and reset the bios to setup default. If you have a different video
(preferably a PCI) i would also change this. Reboot the system and see what
happens. If it still does it, I would swap memory and do the whole thing
over again. I would also make sure the bios is the latest version. Oh, one
other thing... is the machine doing this from the beginning or did this
happen after a period of time? It could also be a virus.
 
in cases like this, you install with a bare minimum of components eg no hd
or cards except video and memory. Then run it for a while to see if it
reboots. If it doesn't you keep continuing with the cards until you're sure
it isn't any of them. Then you install hd and do it with the os etc..
process of elimination.
 
Hey group,

I built this system for a person they keep having the problem of random
reboots. It's like it gets into a reboot cycle where it will do it like 4
or 5 times in a row and finally you just have to shut it down.
==================
Original system:
WinXP Pro SP1
ASUS P3V4X S370
PIII 850 Celery
128 Crucial RAM CL3
SB16 Snd Card
Realtek 10MB LAN
24 CD-ROM
NEC Floppy
ATI 4MB video
Old 10 gig Maxtor (used)
All these parts were just stuff I had laying around. USED
===================
I re-installed the OS thinking that might be it. Nope
I tried to get into the BIOS to see if it was a setting, it then rebooted
while in BIOS, so its not software.
I then figured it was the Motherboard, nope
thought it might be the processor, nope
replaced the RAM with NEW, nope
Figured maybe since the video card was so dated, it might be it, nope
Audio card swapped, nope
LAN card swapped, nope

Basically to cut to the chase, I have swapped EVERYTHING but the case and
the HDD
====================
System is now:
WinXP Pro SP1
DFI CA64 Tulatin Capable (new)
PIII 667 (used)
256 Kingston CL3 RAM (new)
SB Live! (new)
Lynksys LNE100TX (used)
Pioneer 16X DVD (new)
NEC Floppy (new)
ASUS 128 MB 8X AGP (new)
Old 10 gig Maxtor (used)
=====================
I thought about flashing the BIOS thinking that might be it, but it reboots
in the BIOS, I would hate to be in the middle of a flash and have it reboot,
so that's a negative on doing that at this point. I have run out of idea's
on what it could be or what it MIGHT be. I would not think that a HDD
would cause something like this would it? Maybe a shorting case, bad
ground? What in the hell could this be causing this reboot loop hell I'm
in?? It might run perfect for a day or 2 then all of a sudden, reboot,
reboot, reboot, reboot, reboot...........

Any insight as to what this might be would be very very much appreciated!
Click to expand...

Switch off the silly XP,"Atomatically Restart".
My computer/Right click/Properties/Advanced/Startup and recovery
HTH :)




--
Free Windows/PC help,
http://www.geocities.com/sheppola/trouble.html
remove obvious to reply
email (e-mail address removed)
Free songs to download and,"BURN" :O)
http://www.soundclick.com/bands/8/nomessiahsmusic.htm
 
ahh yes the P3V4x.......how many memory slots filled? and are you
using the proper slot?

you confused me about the slocket are you using it? Asus was very
picky about what slocket was used.
 
Well I built the system, loaded everything and all seemed fine. Ran if for
a day or 2 and then delivered it and a couple days later, the guy calls me
and says he's got problems. It all started from there.

I don't have the system here with me, its at the guy's house, but I will
however take Shep's advice and call him and see if that works. I didn't
even think of that menu for this problem. We'll go from here and see what
happens.

Thanx to all that replied thus far!@!!!

Doug


<<
<<Switch off the silly XP,"Atomatically Restart".
<<My computer/Right click/Properties/Advanced/Startup and recovery
<<HTH :)
 
Longshot, but it could be a short in the power switch in the Pc Case.
My other suspect would be the RAM chips.
 
Doug said:
No, I stand corrected, I did have to use a Slotket on the P3V4X, and
eliminated that with the new board, the DFI CA64 and went with the straight
S370. It's been a couple months since I swapped the board, had to think
about that again.
Click to expand...

It would seem you've covered most logical possibilities.

What I'd do is remove everything but the bare minimum in case you have a
card conflict, although I rather doubt it from what you've described. But
then, when all the logical options fail then it must be something illogical ;)

But here's one that is seldom thought about but WAS the problem with a real
hair puller I had: the wall outlet. Or rather, in my case, it was a bad
outlet strip.

Try a completely different AC mains connection from the power strip, if
any, to which circuit it's on (in case some other device on that circuit is
creating noise spikes). Even better would be a UPS, if you have one.
 
I eliminated the Slotket when I upgraded to the DFI CA64..... I only had
one memory slot used even though irrelavant and yes, it was in the proper
slot, DIMM 1.

Thanx for the reply none the less,

Doug
 
<I only had
one memory slot used even though irrelevant>

irrelevant? not hardly, ESPECIALLY with a P3V4x, I have had that
board for years, many memory conflicts....but seeing how your have
only one module............and that it meets the spec of the board, it
appears that it would not be the source, but hardly irrelevant.

what about the VIA 4 in1's or are those irrelevant too?
 
Switch off the silly XP,"Atomatically Restart".
My computer/Right click/Properties/Advanced/Startup and recovery
Click to expand...


hmmm.... I just tried this on my xp home edition laptop, there is no
advanced tab after RC/properties???
 
this is a long shot, heat sink not on cpu right. I installed one 180 out
and the pad caught just the edge of the cpu, about 1/16th on an inch of it,
and the system would run and then shut down and reboot due to high temp of
cpu. But wait!, you said your temps were ok.

This is something basic, that is being over looked. how about a bent pin on
the cpu or dirt on the memory module fingers?

alby
 
What I was saying was irrelevant was the fact that I used two entirely
different sticks of RAM with the same problem, one Crucial and the new one,
Kingston.... I can see your point though, what if I used a CL2 mixed with
a CL3 for instance is what your saying, or two different types or a variety
of other differences in sticks. I did indeed only use 1, a single stick, in
this particular system.

Later into my original post however, I did post that I updated the board to
the DFI CA64 and still encountered the same problem. So what are the odds
that I would have the same problem even if I had the latest and greatest VIA
4 in 1's? I think my chances of getting hit by lightning is better.

I didn't mean to get into a pissin' match and don't want that. I do
appreciate your time so please don't take offense JAD...

Have a nice day and again, thank you for your time,

Doug
 
is there any common denominator between what you have now and the
earlier system? what ever it is/are then remove it/them. I have seen a
funky optical drive cause a reboot....along with just about every
other piece of hardware at one time or another. No offence taken what
so ever.
 
Well, what I decided to do it just get a whole new case, rip the dang thing
apart and rebuild it from scratch putting one card in at a time, run it for
a day or 2, put another card in, run that for a day or 2 until I find
what's wrong. What I don't understand is that I've replaced EVERYTHING
that could be the cause except MAYBE the case. I've built several systems
and have never had this much of a problem, EVER. Maybe some of the parts
came from near the Bermuda Triangle or something....
Regardless, I really do appreciate everyone's input and time with this and
will keep you all posted when I find the problem. It's probably something
really simple, like a loose screw on the ground from the board to the case
or something. Who knows......

Thanks much group!!

Doug
 
Back
Top