Dataserver Application Crash.

I own a mmorpg server and 1 application crashes and i get this error" Dataserver has stop working" i never had this problem it's something new... i think is a windows issue.

In event viewer it shows me this error ":

Faulting application name: DataServer.exe, version: 0.7.0.4, time stamp: 0x49f803ce
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xffffffff
Faulting process id: 0x36c4
Faulting application start time: 0x01cc689c24718bc6
Faulting application path: D:\MuServer\DataServer1\DataServer.exe
Faulting module path: unknown
Report Id: 8af06cf7-d48f-11e0-89f2-00270e15f606

Any one have any clue what causing this crash?

zfklwmspdfkzi said:

I own a mmorpg server and 1 application crashes and i get this error" Dataserver has stop working" i never had this problem it's something new... i think is a windows issue.

In event viewer it shows me this error ":

Faulting application name: DataServer.exe, version: 0.7.0.4, time stamp: 0x49f803ce
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xffffffff
Faulting process id: 0x36c4
Faulting application start time: 0x01cc689c24718bc6
Faulting application path: D:\MuServer\DataServer1\DataServer.exe
Faulting module path: unknown
Report Id: 8af06cf7-d48f-11e0-89f2-00270e15f606

Any one have any clue what causing this crash?

That exception code is a memory exception. Usually caused by a driver. We really need the dmp file to be sure

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

Since it seems to be a memory exception please run these two tests.



1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Driver Verifier - Enable and Disable

This is the dump from the blue screen i got when i enabled driver verifier and i had to boot in safe mode to disable it.
And the weird thing is my data server didnt crash after this. In the future if my data server crashes i will reply with the dump file.

zfklwmspdfkzi said:

This is the dump from the blue screen i got when i enabled driver verifier and i had to boot in safe mode to disable it.
And the weird thing is my data server didnt crash after this. In the future if my data server crashes i will reply with the dump file.

Driver verified and Related to umpserenum.sys Serial Port Enumerator from Texas Instruments Inc.. Yours dated 6/2009. Upadte to newest win7 complaint driver

Also old drivers needing update

Code:

HECIx64.sys    3/28/2008 3:42:14 PM        fffff880`05364000    fffff880`05375000    0x00011000    0x47ed4a16                        
stwrt64.sys    5/22/2008 5:26:53 PM        fffff880`03eef000    fffff880`03f63000    0x00074000    0x4835e51d                        
e1y60x64.sys    8/18/2008 5:45:05 PM        fffff880`05375000    fffff300`053be000    0xfffffa8000049000    0x48a9ed61

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads