MS Windows Server 2003 R2 is crash (restart) when is under a burden.

The system crash and restart. This happened when the system is uder a burden. We need to run some (quite memory consuming) software on this machine.
We run's this sowftare also on others servers (of the same kind) but these servers are stable.
We tried to reinstall whole server. But the result of this step is that the server is now restarting instead of freezing - required start up the server.

The server has Intel® Xeon® Processor E5420 @ 2.50GHz and 7.75 GB of RAM that should be enought.

There are no logs in system or in software that we use.
The following logs are after the server is restarted.

In Application log is this record.

Source: EventSystem
Category: (52)
The COM+ Event System failed to create an instance of the subscriber {58FC39EB-9DBD-4EA7-B7B4-9404CC6ACFAB}.  StandardCreateInstance returned HRESULT 8000401A.

This is in the System Log.

Source: System error  
Category: (102)

Error code 000000d1, parameter1 00001002, parameter2 d0000002, parameter3 00000001, parameter4 8ae10056.

Does anyone have any thoughts what could be the problem?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Tony GiangrecoCommented:
Try restarting the server in safe mode, check for application or memory dumps and determine what they reveal, possibly remove some un-needed applications, check msconfig and uncheck anything you don't need.

Also check to make sure you have the proper amount if ram as compared to the other servers.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ATSNLSupportAuthor Commented:
Thank you very much for your comment.

We were trying to startup the server into a safe mode. But we wasn't able to do that because the server is virtual. Also there isn't any application for removing because the server was reinstalled from scratch.

The server sometimes falls and is restarted. This happend more often when is under a burden.
We set also some memory loging but it is fine, there aren't huge numbers.

Does anyone have any idea?
ATSNLSupportAuthor Commented:
Our server crashed again.
The error code in system log is now looking like this.

Source: System error
Category: (102)

Error code 000000d1, parameter1 00001002, parameter2 d0000002, parameter3 00000001, parameter4 8a6b570e

We sent the Microsoft error report and we received the message where is written that problem could be connected with some hardware driver.

Stop (blue screen) error caused by a device or driver
You received this message because a hardware device, its driver, or related software has caused a stop error, also called a blue screen error. This type of error means the computer has shut down abruptly to protect itself from potential data corruption or loss. In this case, we were unable to detect the specific device or driver that caused the problem.

Any help will be appreciated.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.