Freak rebooting?

  • Thread starter Thread starter petermcmillan_uk
  • Start date Start date
P

petermcmillan_uk

I've just had the weirdest thing happen to me. I powered up my
computer, and went in the other room. When I walked back in as the
Windows (2000) login window was being displayed the computer just
rebooted for no reason :-o. It's the second time it's happened now,
and last time I just thought I must've imagined it.

It's only happened twice so far, but it started when I replaced my
northbridge cooler. My new cooler is a passive Zalman one, and I have
my 120mm CPU fan hanging over it too, so it should be cooler. I've
also used thermal grease, the original Abit cooler didn't have any
thermal compound. So I would expect it to be running cooler. The
reboots have also been on cold starts, and today the room was colder
than usual, so it's probably <30C case, and <40C CPU (internal
thermistor).

It also seems to be in the same place during the boot sequence, which
is unusual. What do you think? Windows 2k is slightly corrupt? I
damaged something when I replaced my n/b cooler? Leaky capacitors on
my Abit board? Actually I did check the capacitors when I installed
the n/b so it's quite unlikely that they are leaking.

After my exams/coursework I'm gonna wipe my drive and put XP on it
anyway.
 
I've just had the weirdest thing happen to me. I powered up my
computer, and went in the other room. When I walked back in as the
Windows (2000) login window was being displayed the computer just
rebooted for no reason :-o. It's the second time it's happened now,
and last time I just thought I must've imagined it.

It's only happened twice so far, but it started when I replaced my
northbridge cooler. My new cooler is a passive Zalman one, and I have
my 120mm CPU fan hanging over it too, so it should be cooler. I've
also used thermal grease, the original Abit cooler didn't have any
thermal compound. So I would expect it to be running cooler. The
reboots have also been on cold starts, and today the room was colder
than usual, so it's probably <30C case, and <40C CPU (internal
thermistor).

It also seems to be in the same place during the boot sequence, which
is unusual. What do you think? Windows 2k is slightly corrupt? I
damaged something when I replaced my n/b cooler? Leaky capacitors on
my Abit board? Actually I did check the capacitors when I installed
the n/b so it's quite unlikely that they are leaking.

After my exams/coursework I'm gonna wipe my drive and put XP on it
anyway.
Click to expand...
Open case and check PSU connector to motherboard is secure(give it a
good pull). Check mains cable fully fitted to PSU. How old is PSU? What
wattage? What is sytem spec? When PSU 2 or 3 years old, can develop int
problems due to aging caps etc.
Mike.
PS try http://www.jscustompcs.com/power_supply/ to check PSU upto job.
 
Leaky capacitors on
my Abit board? Actually I did check the capacitors when I installed
the n/b so it's quite unlikely that they are leaking.
Click to expand...

Wild goose chase. Don't fix it 'til it is broke. Back up.

johns
 
Michael said:
Open case and check PSU connector to motherboard is secure(give it a
good pull). Check mains cable fully fitted to PSU.
Click to expand...

I'll check the PSU power lead!
How old is PSU? What wattage?
Click to expand...

It's just over 2.5 years old, and it's 300W. AOpen, so it is decent.
What is sytem spec?
Click to expand...

Athlon XP 1700+, 512Mb, Geforce FX5500 128Mb, 120Gb Seagate 7200.7,
Abit KD7, Soundblaster Audigy 2 ZS, LG DVD-ROM, LG DVD-RW, AOpen case
with 300W PSU and just one 120mm fan.
When PSU 2 or 3 years old, can develop int
problems due to aging caps etc.
Click to expand...

Oh, I think I'll check that over the summer, after my exams!
PS try http://www.jscustompcs.com/power_supply/ to check PSU upto
Click to expand...
job.

Oh it says 228W, it may actually be fairly accurate :-o
 
I've just had the weirdest thing happen to me. I powered up my
computer, and went in the other room. When I walked back in as the
Windows (2000) login window was being displayed the computer just
rebooted for no reason :-o. It's the second time it's happened now,
and last time I just thought I must've imagined it.

It's only happened twice so far, but it started when I replaced my
northbridge cooler. My new cooler is a passive Zalman one, and I have
my 120mm CPU fan hanging over it too, so it should be cooler. I've
also used thermal grease, the original Abit cooler didn't have any
thermal compound. So I would expect it to be running cooler. The
reboots have also been on cold starts, and today the room was colder
than usual, so it's probably <30C case, and <40C CPU (internal
thermistor).

It also seems to be in the same place during the boot sequence, which
is unusual. What do you think? Windows 2k is slightly corrupt? I
damaged something when I replaced my n/b cooler? Leaky capacitors on
my Abit board? Actually I did check the capacitors when I installed
the n/b so it's quite unlikely that they are leaking.

After my exams/coursework I'm gonna wipe my drive and put XP on it
anyway.
Click to expand...

I've just got some more info. I looked in the event log and it says

"The computer has rebooted from a bugcheck. The bugcheck was:
0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000). Microsoft
Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini041105-01.dmp."

Doesn't really tell me much, but it looks like it rebooted
automatically due to a bug. I thought auto reboot was just an XP
thing, but obviously not.
 
[email protected] said:
I've just got some more info. I looked in the event log and it says

"The computer has rebooted from a bugcheck. The bugcheck was:
0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000). Microsoft
Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini041105-01.dmp."

Doesn't really tell me much, but it looks like it rebooted
automatically due to a bug. I thought auto reboot was just an XP
thing, but obviously not.
Click to expand...

Just found what it means. 0x8 means that it was a 'double exception'.
I think that means that there was an exception in the exception
handler. It could be due to damage on the m/b, but is most likely to
be memory. I suppose it could quite easily just be an error on the
hard disk though.

I think it's gonna be like finding a needle in a haystack though. I'll
probably run a memory test before I install XP. This error seems to
have happened once, but in January it had a similar error twice, which
was even more likely to be memory.
 
[email protected] said:
I've just got some more info. I looked in the event log and it says

"The computer has rebooted from a bugcheck. The bugcheck was:
0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000).
Microsoft

Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini041105-01.dmp."

Doesn't really tell me much, but it looks like it rebooted
automatically due to a bug. I thought auto reboot was just an XP
thing, but obviously not.
Click to expand...


Just found what it means. 0x8 means that it was a 'double exception'.
I think that means that there was an exception in the exception
handler. It could be due to damage on the m/b, but is most likely to
be memory. I suppose it could quite easily just be an error on the
hard disk though.

I think it's gonna be like finding a needle in a haystack though. I'll
probably run a memory test before I install XP. This error seems to
have happened once, but in January it had a similar error twice, which
was even more likely to be memory.
Click to expand...

time for memtest86 then? There's a cd image if your machine has no
floppy drive:

http://www.memtest86.com/#download0


--
spammage trappage: replace fishies_ with yahoo

I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. Complications in
hospital following this resulted in a serious illness. I now need a bone
marrow transplant. Many people around the world are waiting for a marrow
transplant, too. Please volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/
 
spodosaurus said:
[email protected] said:
I've just got some more info. I looked in the event log and it says

"The computer has rebooted from a bugcheck. The bugcheck was:
0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000).
Microsoft

Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini041105-01.dmp."

Doesn't really tell me much, but it looks like it rebooted
automatically due to a bug. I thought auto reboot was just an XP
thing, but obviously not.
Click to expand...


Just found what it means. 0x8 means that it was a 'double exception'.
I think that means that there was an exception in the exception
handler. It could be due to damage on the m/b, but is most likely to
be memory. I suppose it could quite easily just be an error on the
hard disk though.

I think it's gonna be like finding a needle in a haystack though. I'll
probably run a memory test before I install XP. This error seems to
have happened once, but in January it had a similar error twice, which
was even more likely to be memory.
Click to expand...

time for memtest86 then? There's a cd image if your machine has no
floppy drive:

http://www.memtest86.com/#download0
Click to expand...

Yeah, that's what I was thinking. I'll do it once I've got my exams
out of the way. It'll be a bit annoying if that's what it is because
my memory's only just a year old. Fortunately I bought the memory when
it reach it's lowest price. The price of memory didn't went up
slightly after I bought the module, and it was almost 6 months until it
go back to the price I payed. It's gone down a lot lower now though.
 
Back
Top