LCSLouisJJames
asked on
System Failure: Stop error Reason Code: 0x805000f
I have a Windows 2003 Server R2 Standard that has been rebooting without warning. After the reboot, I have the following event logged:
--------------------------
Event Type: Warning
Event Source: USER32
Event Category: None
Event ID: 1076
Date: 1/12/2009
Time: 2:28:11 PM
User: LCSSERVER\ljames
Computer: LCSSERVER
Description:
The reason supplied by user LCSSERVER\ljames for the last unexpected shutdown of this computer is: System Failure: Stop error
Reason Code: 0x805000f
Bug ID:
Bugcheck String: 0x000000d1 (0x00000010, 0xd0000002, 0x00000000, 0xf723c1a0)
Comment: 0x000000d1 (0x00000010, 0xd0000002, 0x00000000, 0xf723c1a0)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 05 08 ....
--------------------------
I suspect many things but really have not found a pattern. The server is basically acting as a fileserver but it is receiving files via an application (called Powerfolder). Powerfolder is simply to Microsoft's Foldershare in that it sends receives files (file sharing for back up purposes.
The files are not typically large.
The server can run for minutes, hours or days before it reboots. Some days it reboots every 10 minutes. Other days it goes for days.
It has one SATA drive (500 Gb).
Any guidance would be appreciated. Thank you.
--------------------------
Event Type: Warning
Event Source: USER32
Event Category: None
Event ID: 1076
Date: 1/12/2009
Time: 2:28:11 PM
User: LCSSERVER\ljames
Computer: LCSSERVER
Description:
The reason supplied by user LCSSERVER\ljames for the last unexpected shutdown of this computer is: System Failure: Stop error
Reason Code: 0x805000f
Bug ID:
Bugcheck String: 0x000000d1 (0x00000010, 0xd0000002, 0x00000000, 0xf723c1a0)
Comment: 0x000000d1 (0x00000010, 0xd0000002, 0x00000000, 0xf723c1a0)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 05 08 ....
--------------------------
I suspect many things but really have not found a pattern. The server is basically acting as a fileserver but it is receiving files via an application (called Powerfolder). Powerfolder is simply to Microsoft's Foldershare in that it sends receives files (file sharing for back up purposes.
The files are not typically large.
The server can run for minutes, hours or days before it reboots. Some days it reboots every 10 minutes. Other days it goes for days.
It has one SATA drive (500 Gb).
Any guidance would be appreciated. Thank you.
ASKER
Pab;otp70:
Thank you for your reply. My original suspicion was and still is hardware but yet to discover which.
My first thought was the hard drive although you would think that an ST3500630AS would be a good drive. And yet every test run seems to indicate the drive is ok.
Another one of our techs ran Belarc (although I'm not familiar with the program) and tells me that memory seems to be ok.
I had not thought about the NIC and I believe BIOS is up-to-date.
Interestingly, the "backup" application is not running currently and it the server "seems" to be stable, I have not seen a reboot. Unfortunately, that again leads me to believe that either the app is killing the hard drive (either the SATA controller or the drive itself) or it's a memory problem.
So I guess, back to testing.
Hopefully others will chime in with ideas.
Thanks again.
Louis James
Thank you for your reply. My original suspicion was and still is hardware but yet to discover which.
My first thought was the hard drive although you would think that an ST3500630AS would be a good drive. And yet every test run seems to indicate the drive is ok.
Another one of our techs ran Belarc (although I'm not familiar with the program) and tells me that memory seems to be ok.
I had not thought about the NIC and I believe BIOS is up-to-date.
Interestingly, the "backup" application is not running currently and it the server "seems" to be stable, I have not seen a reboot. Unfortunately, that again leads me to believe that either the app is killing the hard drive (either the SATA controller or the drive itself) or it's a memory problem.
So I guess, back to testing.
Hopefully others will chime in with ideas.
Thanks again.
Louis James
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Good Morning Pabilto70
Well, more info. Regarding the USB. No. No USB devices attached. In fact not even a keyboard or mouse. I had an external USB floppy but that has been long gone.
Memory: I ran a mem test all night and did not get any errors. However, that mem test was under windows. I'm running Microsoft's Memory tester now which boots off a CD so the OS is out of the way.
If the memory test passes, I'm starting to think either hard drive but more likely the SATA controller. Which then begs the question can I install another controller and disable the onboard... hmmm?
Anyway, I do appreciate your thoughts. Your input is either confirming or pushing me in directions to consider. So I do look forward to more input.
Thanks again
Louis James
Well, more info. Regarding the USB. No. No USB devices attached. In fact not even a keyboard or mouse. I had an external USB floppy but that has been long gone.
Memory: I ran a mem test all night and did not get any errors. However, that mem test was under windows. I'm running Microsoft's Memory tester now which boots off a CD so the OS is out of the way.
If the memory test passes, I'm starting to think either hard drive but more likely the SATA controller. Which then begs the question can I install another controller and disable the onboard... hmmm?
Anyway, I do appreciate your thoughts. Your input is either confirming or pushing me in directions to consider. So I do look forward to more input.
Thanks again
Louis James
Check to see if you have a APC unit and see what is going on with that. That could be bad causing intermitant shut downs.
have you checked the hardware? May be an hw issue, if you are not running particular services on server.
My personal checklist:
- scanning with an up to date antivirus/spyware (I'm using SAV, but my best is AVG 8 network edt)
- change memory ram
- change network card pci slot
- update server bios
HTH