We're currently running Windows Server 2008 R2 SP2. After about 24 hours of operation, all applications will crash with the following error: 'Application popup: [Name of Application].exe - Application Error: The exception unknown software exception (0xc0000005) occurred in the application at location 0x764f50b9.

Click on OK to terminate the program' The application name and the location is the only thing that's different in the errors. A reboot is the only way to clear the issue up. Within 24 hours, the error manifests itself again, and we won't be able to continue working until we reboot.

During this time, SQL Server is still functional. No other applications will run. This server currently runs Windows SQL Server 2008 SP2, Trend Micro OfficeScan 10.5, eVault Backup Agent, and Automate 7. I've tried uninstalling OfficeScan and eVault, but the error persisted. I've also tried setting DEP to 'Turn on DEP for essential Windows programs and services only'.

Download crw32.exe crystal report 8.5. Issuu company logo. Stories Discover Categories Issuu Store. Free Download Crystal Report 8.5 Full Version (Serial Number + CD Key) - Gho Blog's. Crystal report merupakan salah satu product report designer yang banyak digunakan oleh para developer.

Dell Poweredge 2850 1x Intel Xeon 7030 2.8GHz CPU 16GB PC2-3200 DDR RAM Any help would be greatly appreciated! So comparing the list of modules loaded against a test machine that I've got, the only difference is the cptlwa64. Dll it looks like that module may be related to a piece of enterprise audit software called softrack. Is that piece of software installed here? If it is we could be looking at a regularly scheduled scan kicking off that causes an exception in the processes.

To double check you could look at some of the DLLs loaded by other processes that are crashing using process explorer to see if this module is loaded in all of them. Doug Kentner. It appears that, some of the system files have gone corrupt. You can try couple of things here 1. From elevated cmd (run as administrator ) run command sfc /scannow 2. If sfc/scannow doesn't help, try in-place upgrade of OS How to Perform an In-Place Upgrade on Windows Vista, Windows 7, Windows Server 2008 & Windows Server 2008 R2 P.S. As the server also runs SQL, take take full DB backup before doing in-place upgrade I do not represent the organisation I work for, all the opinions expressed here are my own.

This posting is provided 'AS IS' with no warranties or guarantees and confers no rights. You can check the following locations for dumps.

C: ProgramData Microsoft Windows WER (.mdmp and.hdmp if they exist will be in a reportarchive or reportqueue folder) C: Users XXX AppData Local Microsoft Windows WER (same caveat on location of files) If there aren't any dumps there's a process you could follow to enable dumps for app crashes located here: There are instructions on using WinDbg to analyze the dumps here: If you could post the output of a couple!analyze -v commands we could look at the call stacks to see if there's some commonality Doug Kentner. I'm curious if there may be a 3rd party dll being loaded into the process space of all these apps, can you attempt the following and paste the results?: 1. Install the Windows Debugging Tools (If you haven't already) 2. Launch notepad 3. Launch Windbg (x64 if this is an x64 system, x86 if it's x86 system) 4.

Choose File/Attach to process 5. Select notepad.exe from the list that displays 6. In the command window in Windbg type lm and press enter 7. Please paste the results here to the forum, This will tell us what modules are being loaded. If there's a 3rd party module loaded, we may be able to tell which one may be causing it based on comparison with another system Link with instructions on obtaining the debugging tools here: Doug Kentner.

Here's the results: Microsoft (R) Windows Debugger Version 6.2.8400.0 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

*** wait with pending attach Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use.symfix to have the debugger choose a symbol path.