Web Hosting Talk : Web Hosting Main Forums : Hosting Security and Technology : Win2K3 Stop Errors. Please help.

[Map-Depot]

Greetings,

First post, yay!. Anyways, I'm having a problem with my colocated server. It's less than 2 weeks old and I'm having stop error problems. The server will reboot automatically after the stop error, but there are a few processes that I need running and have to start manually because they're not setup as services. It happens anywhere from 2 to 8 times a day. It seems random. The only consistancy is in the error messages logged in the event viewer. They all start with "Error code 100000be" and end with "parameter4 0000000b".

I had the server running for a week before I sent it to the colo host, and never had a problem with it. The problem only started about two or three days after being at the colo host.

Here is a copy of one of the error messages.

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 3/22/2005
Time: 6:32:36 PM
User: N/A
Computer: SERVER
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000be (0xf63d15ac, 0x3ff03121, 0xf66d8cac, 0x0000000b). A dump was saved in: C:\WINDOWS\Minidump\Mini032205-04.dmp.

I have searched Google, and other sites for this error code, but was unable to find anything that could pertain to my server. Mostly it was stuff involving ATI cards and Windows XP. I'm running Windows Server 2003, and have an nVidia MX4000 in it.

All the drivers are up to spec, and the OS has been completely updated. I even used the Microsoft Baseline Security Analyzer to double check my system, and everything is ok.

Any help or suggestions would be greatly appreciated.

Thanks!

[farpost]

check eventid comments:

http://eventid.net/display.asp?event...20Dump&phase=1

[sam_cogan]

From what I can find the 0x0000000be error code realates to a driver attempting to write to a read only memory segment. If it can, windows will identify the driver in the error message. Which by the looks of it, it hasn't in this case. I think initially it might be a case of updating and re-instaling drivers, or looking at a possible memmory problem. i would think it's more likely to be drivers than memmory.

[Map-Depot]

Thanks for pointing me in the direction of drivers. Last night just after I posted on here, I decided to check my video driver on the server. Turns out I hadn't installed one for my card. I was just using the generic Windows driver. I downloaded the latest nVidia drivers and installed them. So far we're up to 10 hours 30 minutes without a crash.

I guess the real test will be if by tonight it hasn't crashed then it should probably be safe to say that it's resolved.

Thanks again guys!

[Map-Depot]

Well it went 15 hours with no problems, then it crashed again. So I guess the drivers didn't fix the problem.

I really am at a total loss as to what to do, and honestly I'm starting to get a little worried that I may have to get the server shipped back to me so I can repair it. That will cost me a lot of money, that honestly I can't afford right now.

Does anyone have any other suggestions?

[sam_cogan]

have you changed any other drivers, it may have been one other than the graphics card. Is it still the same stop error? If you can maybe you should run a memmory test on the server. Let us know if there are any other symptons.

[Map-Depot]

I have updated all the drivers on the server. The stop error is the same as before. I cannot run a mem test on the server as it is in Dallas, and I'm in canada.

[ixnay]

Hello Map-Depot

Donwload Microsoft debug tools @ msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.4.7.2.exe and install it at your home pc.

Go to your Minidumps directory on the server: C:\WINDOWS\Minidump\ and grab the report you want.

Now again to your home pc.
Download the report, start Windebug (windbg.exe) and open that memory dump file (I guess there is a specific "Open Memory Dump File")

You'll see a lot of strange characters (almost non-readable), but you'll be able to see what file is making your server crash (probably some driver's file). Then reinstall whatever needs to be reinstalled

I had a similar problem and I was able to solve it with this procedures. It was a firewall's driver that was going crazy. Reinstalled the firewall and never had that nasty reboots again.

Good luck

[geekie246]

I suspect memory. seen this on a new server i installed and had the exact same error.

swapped ram and voila ... things have been great and been up for 56 days.

[Map-Depot]

ixnay, what firewall software were you running? I am running a software firewall.