0x50 windows 2003

It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. Windows Server x64 R2 Standard Edition it's rebooting by itself. After uninstalled Paragon HDM 15 it stopped rebooting but it did it again.

This box it's a production box running SQL Server I have called Dell and they analyzed the the dump file. SYS and EX Unloaded modules: fffffade fffffade b ENG I have uninstalled SEP but the server keep crashing with the same error code.

This time shows something different. Using lmnt shows the following not more ENG SYS Wed Nov 27 fffffade fffffade update update. SYS Timestamp: unavailable Checksum: ImageSize: fffffade 5a67b fffffade 5a hidusb. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. Asked 6 years, 9 months ago. Active 6 years, 9 months ago. Active Oldest Votes. If you look here , you'll see the parameters of your bug check code: Parameter Description 1 Memory address referenced 2 0: Read operation 1: Write operation 3 Address that referenced memory if known 4 Reserved Windbg identified sptd.

I would definitely start by either upgrading or uninstalling that software. Improve this answer. Ryan Ries Ryan Ries Thanks for your help. I was able to find that sptd. It's an Exchange server with Blackberry server integration. That's it. What else could have caused this? What version of sptd. If it's lower than 1. It seems pretty apparent from the crash dump that it is what is causing your crashes.

Show 1 more comment. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Helping communities build their own LTE networks. Podcast Making Agile work for data science.

Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related 0. Resolving a faulty driver: Examine the name of the driver if that was listed on the blue screen or is present in the event log. Contact the driver vendor to see if an updated driver is available. Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update.

If the error occurs during system startup, investigate the Windows repair options. For more information, see Recovery options in Windows Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update. You must restart the system before the disk scan begins on a system partition.

Contact the manufacture of the hard driver system to locate any diagnostic tools that they provide for the hard drive sub system. Select the Start button, and then select the Control Panel. In the search box, type Memory, and then select Diagnose your computer's memory problems. Look for the MemoryDiagnostics-Results entry to view the results. Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs.

If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. For general blue screen troubleshooting information, see Blue Screen Data. Typically, the referenced address is in freed memory or is simply invalid.

This cannot be protected by a try - except handler -- it can only be protected by a probe or similar programming techniques. Use the!