Windows Server 2003 Crashes Intermittently

By janus08 ·
I have a Server which seems to be crashing for no reason. The error I get seems to point to Hardware or driver errors but im pretty sure its neither as none of the drivers have been updated recently. In the event log I get the following:

Source: System Error, Cat: 102, EventID 1003

Error Code 1000008e, Param1 80000003, Param2 8086cf34, Param3 808934c0, Param4 00000000.

After sending the error report to MSoft I got a webpage telling me to try new hardware drivers, Scan for viruses and check harddrive for errors. The hard drive has been checked thoroughly several time when the Server was brought down over night for this purpose and I am certain there are no viruses as I have AVG Network on the Server which scans daily. As I said before, I don't think its a faulty driver but maybe its something to do with a microsoft update that is conflicting with an older driver.

Finally, the Server is at a small Outdoor Centre with very little money and cannot afford to have the server down for too long. I do not have the money myself to provide a replacement so any work has to be done when the Server is still on or within an hour or two when the server can be off.

If anyone has any ideas I would be very grateful as I am totally stumped on this one, its been happening for months now with now possible reason.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

If you find anything with these tools, run them again in Safe Mode

by Jacky Howe In reply to Windows Server 2003 Crash ...

Download Spybot - Search & Destroy and install it. Update it.

Download Malwarebytes Anti-Malware, install it and update it.

<a href="" target="_blank"><u>Malwarebytes</u></a>

* Double-click mbam-setup.exe and follow the prompts to install the program.
* At the end, be sure a checkmark is placed next to Update Malwarebytes' Anti-Malware and Launch Malwarebytes' Anti-Malware, then click Finish.
* If an update is found, it will download and install the latest version.
* Once the program has loaded, select Perform Quick Scan, then click Scan.
* When the scan is complete, click OK, then Show Results to view the results.
* Be sure that everything is checked, and click Remove Selected.

If you encounter any problems while downloading the updates, manually download them from here and just double-click on mbam-rules.exe to install.
<a href="" target="_blank"><u>mbam-rules</u></a>

I would keep scanning with it until it is clean by closing out and rebooting and running it again.

Run this Rootkit Revealer GMer
<a href="" target="_blank"><u>Gmer</u></a>

<a href="" target="_blank"><u>FAQ</u></a>

Let us know how you get on.

Collapse -

Seeing as you have to access WinDBG anyway

by Jacky Howe In reply to If you find anything with ...

1. Press the WinKey + Pause
2. Click Advanced and under Startup and Recovery select Settings.
3. Uncheck Automatically restart.
4. Click on the dropdown arrow under Write debugging information.
5. Select Small memory dump (64 KB) and the output is %SystemRoot%\Minidump.
6. Restart the PC normally as this will allow the System to Blue Screen and create the Minidump.

Minidump Files can be found here. C:\WINDOWS\Minidump\Mini122707-02.dmp

How to read the small memory dump files that Windows creates for debugging

To download and install the Windows debugging tools, visit the following Microsoft Web site:

Instructions on using Windbg.

Open Windbg and select file, Symbol file path and browse to the Symbol folder that you have downloaded and installed Symbols to, select OK.
Close the workpage and save the Workspace information. This should lock in the Symbol path.
Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
Ctrl + a will let you copy the information and paste it into notepad.

Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.




PROCESS_NAME: logon.scr

LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea

f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585

STACK_COMMAN .thread 0xffffffff864f6a98 ; kb

bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)


SYMBOL_NAME: sgiul50!DrvBitBlt+585


MODULE_NAME: sgiul50

IMAGE_NAME: sgiul50.dll


FAILURE_BUCKET_I 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

BUCKET_I 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

I also run MalwareBytes on my SBS2003 server. They can always be uninstalled afterwards.

Collapse -

Lots of ideas

by BFilmFan In reply to Windows Server 2003 Crash ...

Are there any firmware or Windows driver updates from the hardware vendors for the server hardware?

You might want to use WhoCrashed (free) to track down what is in the mini-dump files.

You said it is a Windows server, but what role is this server playing? Is it an application, domain controller, Exchange server or file and print server?

Which version of Windows OS is on it?

What service packs are installed?

What hot fixes are installed?

What is in the Application and System event logs besides this error?

Really need a lot more information to troubleshoot this issue.

Collapse -

cheers, will look into more

by janus08 In reply to Lots of ideas

thanks guys, I will look into this further with WhoCrahsed, not keen on putting too many progs on the server but im happy with S&amp. The server is 2003 Standard with all updates (SP1 i think). Only hotfixes are those installed as updates as I have not installed any manually.

As for the Servers role...its a multi-role server as it is a small company. File & Print, Backup, RAS (when I get it fully secured) and DC. No exchange or apps running off it. This was the first server I setup myself after doing MCSA course so it might not be up to 'industry standards' but im pretty sure its secure and virus free.

There wasn't anything significant in the event logs apart from this error. Only other thing was one of the W2k PC's trying to be the master browser but will check again for other problems and get back to you.

Related Discussions

Related Forums