SBS 2003 random shutdowns

Status
Not open for further replies.
I've got a win2003 sbs that is shutting down randomly, usually about 2 weeks apart... I've been following my eventlogs and have retrieved some information, and even taken action on some of the trails that emerged, but still having the same issue... Here are the two main events that seem related...

Event Type: Warning
Event Source: USER32
Event Category: None
Event ID: 1076
Date: 12/28/2006
Time: 7:00:45 AM
User: MEA\Administrator
Computer: SERVER
Description:
The reason supplied by user MEA\Administrator for the last unexpected shutdown of this computer is: System Failure: Stop error
Reason Code: 0x805000f
Bug ID: 12-28-06
Bugcheck String: 0x00000050 (0xea5effe0, 0x00000001, 0xbaf96105, 0x00000000)
Comment: 0x00000050 (0xea5effe0, 0x00000001, 0xbaf96105, 0x00000000)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 05 08 ....


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/28/2006
Time: 7:02:33 AM
User: N/A
Computer: SERVER
Description:
Error code 00000050, parameter1 ea5effe0, parameter2 00000001, parameter3 baf96105, 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 30 30 30 30 30 30 35 0000005
0020: 30 20 20 50 61 72 61 6d 0 Param
0028: 65 74 65 72 73 20 65 61 eters ea
0030: 35 65 66 66 65 30 2c 20 5effe0,
0038: 30 30 30 30 30 30 30 31 00000001
0040: 2c 20 62 61 66 39 36 31 , baf961
0048: 30 35 2c 20 30 30 30 30 05, 0000
0050: 30 30 30 30 0000

I'm in the process of learning how to read dump files, but some help would be appreciated... Attached is the dump file from the last shutdown.
 
And I have run ramtest, chdsk, cleaned out the case, cleaned the ram, etc... It does not appear to be a disk, ram, or overheating issue...
 
Status
Not open for further replies.
Back