smpross
asked on
BSOD on Win 2003 server
Hi All,
We have had a Windows 2003 server up and running as a terminal server for about 5 months. We have not added any hardware to the server in about a year. Lately, every 3-4 days, the server displays the BSOD and reboots. When it come back up, the following event in logged in the System log:
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 5/2/2006
Time: 1:21:06 PM
User: N/A
Computer: SERVER1
Description:
Error code 0000000a, parameter1 f488effc, parameter2 000000ff, parameter3 00000000, parameter4 808208a6.
This feels like a memory problem. I am using all four slots on the motherboard and the system has 1.5 GB of memory. Is there a way to troubleshoot the issue further? How can I obtain further information regarding the cause of the BSOD.
Any help would be greatly appreicated.
Scott
We have had a Windows 2003 server up and running as a terminal server for about 5 months. We have not added any hardware to the server in about a year. Lately, every 3-4 days, the server displays the BSOD and reboots. When it come back up, the following event in logged in the System log:
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 5/2/2006
Time: 1:21:06 PM
User: N/A
Computer: SERVER1
Description:
Error code 0000000a, parameter1 f488effc, parameter2 000000ff, parameter3 00000000, parameter4 808208a6.
This feels like a memory problem. I am using all four slots on the motherboard and the system has 1.5 GB of memory. Is there a way to troubleshoot the issue further? How can I obtain further information regarding the cause of the BSOD.
Any help would be greatly appreicated.
Scott
You need to analyse the dump file to see what's going on. Have a look at the following:
How to solve Windows system crashes in minutes
http://www.networkworld.com/news/2005/041105-windows-crash.html
Debugging Tools for Windows - Overview
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
How to solve Windows system crashes in minutes
http://www.networkworld.com/news/2005/041105-windows-crash.html
Debugging Tools for Windows - Overview
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@smpross...did you forget us?
What usually causes this is a program on startup looking for a resource and failing. First step is to check the event log and findout what is failing. It's usualy a program that is in the startup folder or is marked to auto start on boot.
post back what that is.