random reboots

[imported_ROMOS]

My 3-week old computer has been rebooting itself randomly. Here is the machine config:

Shuttle SN95G5 nFORCE3 XPC RT
CPU AMD 64 |3000+ ATHLON 64 939P%
HD 250GB|WD2500SD RAID Edition%
HD NTBK 60GB|HITC 08K0939 7200RPM
MUSHKIN DUAL V2 1G(512X2) DDR400 R
DVD±RW | PLEXTOR PX-716A/SW RT

Here are the error messages:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 3/19/2005
Time: 3:01:57 PM
User: N/A
Computer: BLACKBOX
Description:
Error code 00000024, parameter1 001902fe, parameter2 f79937ec, parameter3 f79934e8, parameter4 805442f1.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 32 0000002
0020: 34 20 20 50 61 72 61 6d 4 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 31 39 30 32 66 65 2c 20 1902fe,
0038: 66 37 39 39 33 37 65 63 f79937ec
0040: 2c 20 66 37 39 39 33 34 , f79934
0048: 65 38 2c 20 38 30 35 34 e8, 8054
0050: 34 32 66 31 42f1



AND


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 3/20/2005
Time: 10:47:59 AM
User: N/A
Computer: BLACKBOX
Description:
Error code 10000050, parameter1 8c5f6a28, parameter2 00000000, parameter3 aa33b2e3, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 35 1000005
0020: 30 20 20 50 61 72 61 6d 0 Param
0028: 65 74 65 72 73 20 38 63 eters 8c
0030: 35 66 36 61 32 38 2c 20 5f6a28,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 61 61 33 33 62 32 , aa33b2
0048: 65 33 2c 20 30 30 30 30 e3, 0000
0050: 30 30 30 30 0000


What could be the problem/what should I do?

Thanks in advance!

Ryan

 

[amdskip]

What power supply (brand/model) are you using?

 

[KGB]

Skip,

That system is one of those Shuttle SFF "shoebox" units.
It has a proprietary form-factor PSU.

Ryan,

What kind of temps are you getting for the CPU?

Have you run Memtest86 to check your DIMMs?

 

[imported_ROMOS]

I have not- how can I easily check temps?

 

[KGB]

In your BIOS there should be a section call PC Health or something like that.
This monitors temp sensors built into your MB.

 

[imported_ROMOS]

Here are the results of PC Health (memtest86 is currently running):

CPU Voltage 1.36V
AGP Voltage 1.44V
3.3 VIN 3.24V
+5 VIN 4.86V
+12 VIN 11.71V
-12 VIN -12.19V
RAM 2.56V
5V SBVIN 4.56V
Voltage Battery 3.02V

CUP Temp 46 C
System Temp 49 C

Everything looks okay, right?

 

[imported_ROMOS]

Everything seems to pass with memtest86...

 

[compusaguy]

The easiest way to figure this out would be to reinstall/reformat windows.

If you continue to have random reboots, you definitely have a hardware problem. Then it is going to be either the RAM or the motherboard that is the culprit.

 

[imported_ROMOS]

Other ideas? I think thats a little drastic for a new computer, no?

 

[compusaguy]

I wouldn't think so. If you can rule out the OS and know its a hardware problem, then you'll be able to RMA the hardware and get a perfectly working computer rather than spending many futile hours ignoring the real problem.

 

[KGB]

Romos,

How long did you run Memtest?
Looking at your posts, it appears to be for 23 minutes.

Let it run for at least 3-4 full passes.

 

[imported_ROMOS]

It was about 35 minutes or so...is there anything specific I should be looking for?

 

[KGB]

Yes... it will log the errors and give you a total for each test.

Keep in mind, memtest is a good tool but it's not perfect. Generally if it finds errors you have a problem. Sometimes the problem can be solved by changing DIMM slots, re-seating the modules in the same slot or even increasing the VDIMM in the BIOS. And, of course, the possibility that the RAM is bad if none of those items work.

However, even if it passes memtest, it doesn't mean you're "clean".

I build many systems and this happened to me recently:

I was installing Win2K on a newly built system and when the install was supposed to let me partition/format the HD, it would just freeze... always at the same point.
I have enough experience to know that 99.9% of problems during a clean install are memory related (given that the system was properly assembled from "known compatible" components). I ran memtest and it found some errors so I tried the tricks mentioned above until memtest ran without any errors. The Win2K install, however, would still hang at the same point. Only after I again re-seated the DIMM was I able to get past the install hangup and the system has never had a problem since.

Moral of the story: When memtest gives you errors; believe that you have a problem.
When memtest doesn't give you errors; don't believe you're clean.

Film at 11:00 :roll: