random hangs/shutdowns, even with new mobo / cup?!

[navyblue2000]

I'm thinking something on/of/within the hard drive is kooked.

but i can't tell for sure if it's software or hardware related.

I had a new mobo/processor on order when i thought i started having overheating problems...
but now, with the new board and cpu, and an open case, it still likes to randomly restart with no warning....just sitting here, and BANG. black screen back to POST.
any ideas?

[3.4 [deployed]]

it's your Z, it's effing everything up. go back to a six & get a mataching Pentium chip. Don't you have any extra hdd around? Nachius might ;)

[Dan Vincent]

Well, first of all, having a CPU and not a cup would help. [img]smile.gif[/img]

Make sure the HSF is seated properly w/ thermal goo... also, having the side of the case off doesn't help airflow, it actually hinders it. No obstructions, etc. Make sure your BIOS settings aren't too aggressive either and that you have the proper FSB, etc.

[ka50]

do a virus scan... some viruses reboot comp randomly.

[98Camaro3.8]

Do you know what the CPU temp is? Like Dan Vincent said, check your BIOS to make sure the memory timings aren't set too agressive. It could also be bad memory...do you have 1 stick or 2? If 2, try taking one of them out and see if you still get it. How long after startup does it reset?

[Rob@USC]

When you installed a new mobo and cpu, was the new mobo exactly like the old one (same model and all)? I found out through experience that by not reinstalling windows when you put in a different mobo, windows does not like it at all. Just one possiblity you may want to think about.

[Turbo V6 Camaro]

Originally posted by Dan Vincent:
Well, first of all, having a CPU and not a cup would help. [img]smile.gif[/img]

[img]graemlins/rofl.gif[/img] [img]graemlins/rofl.gif[/img] [img]graemlins/rofl.gif[/img] [img]graemlins/rofl.gif[/img] [img]graemlins/rofl.gif[/img]

[Tyler]

SASSER worm is a *****..

hit CTRL ALT DEL> and see under running programs... look for LSASS.EXE... see if that is running.

if so.. then you got sasser worm..

search on google how to get rid of it.. but unfortunately there is no way to avoid getting it back

[L32Projekt]

I agree with making sure you've used thermal past, heatsink seated properly and fan is getting power. Other cause that I agree with is possible bad memory. Virus would be a distant third...

[98Camaro3.8]

Originally posted by Tyler:
hit CTRL ALT DEL> and see under running programs... look for LSASS.EXE... see if that is running.

if so.. then you got sasser worm..

Let me be the first to [img]graemlins/slap.gif[/img]
LSASS.EXE is not a virus. LSASS is the Local Secutiy Authentication Server, built into windows. Your computer should have it running. Sasser exploits this service, but the virus itself runs under a different name.

This applies only to the Sasser worm. Other viruses such as Nimos name themselves as lsass.exe, but are run from a different location than the correct one. Others may even inject their code into lsass.exe. But saying you're infected if you have lsass running is not right.

[ August 07, 2004, 09:11 PM: Message edited by: 98Camaro3.8 ]

[zlexiss]

Umm, LSASS.exe in %systemdir% is a legitimate windows file and should be running. If the running copy is sitting in %windir%, that could be the worm.

-Jeff

Originally posted by Tyler:
SASSER worm is a *****..

hit CTRL ALT DEL> and see under running programs... look for LSASS.EXE... see if that is running.

if so.. then you got sasser worm..

search on google how to get rid of it.. but unfortunately there is no way to avoid getting it back

[navyblue2000]

here i am again, after about 10 unsuccessful reboot attempts :rolleyes:

sometimes it'll kick back before it even gets to the XP boot screen...other times i'll go for hours on here...
memory? mayhaps. Hard drive a POS, mayhaps.

The cpu/board are TOTALLY different than the old.... this is a ABIT KV7 with an AMD XP 2700+. the old was a 2.4ghz celeron with a PC Chips board (crap i know)...

[3.4 [deployed]]

I thought you had like, 20 hdds hanging around. Maybe even the SCSI one too [img]graemlins/stickpoke.gif[/img]

[98Camaro3.8]

Is it possible you're getting a Blue Screen of Death before the reboot? By default, Windows, being the wonderful software it is, will automatically reboot before you have time to read a BSOD. From System Properties, Advanced Tab, Startup And Recovery Settings, uncheck Automatically Restart. If there is a BSOD, you'll now be able to read the error.

[MTMike]

Look into the power supply. A power supply that isn't supplying enough voltage or amperage can and will cause random reboots.