I have a Server 2008 (not R2) box that is an all-in-one with Exchange 2007. All software is fully patched. BIOS is up to date. MoBo is an Intel S5000VSA, 2x CPU's, 8GB RAM, 2x 160GB WD RE3's (RAID 1) and 2x Seagate 500GB (RAID 1). The system has been running perfectly for 2 years now, but all of a sudden the system has started to hang. No errors are present at the time of hang in any of the Event Logs and the system does NOT BSOD, so no dump files are created. System is using ESET A/V and hangs with or without the A/V running. No updates where installed at time of first lock up. So far, I have changed the PSU, MoBo, CPU's and RAM. RAID controller reports no problems with HDD's. SFC reports all clear too. So does CHKDSK. Rebuilding is a last option, as the company is 24x7, so downtime is critical. Please, has anyone got any ideas?Dominic

Hello, sorry but "hang" is not helpful, please describe more detailed how exactly you realize this if no errors are shown. Aren't you able to use the mouse/keyboard, so the screen is complete locked or do you mean it react slow of input or for browsing folders or web?Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Hi Meinolf, Thanks for the quick reply. The system just comes to a sudden halt - whatever was on the screen stays on the screen (but frozen), mouse/keyboard are unresponsive. Num Lock does not work. You cannot PING the server from the rest of the network.Dominic

dominic, you need to capture the complete memory dump for analysis and it is not possible to use any utilities to diagonise this issue, the reason is that most of the utlities gets tied down to process. In your scenario if you can find out the process which is causing the hang it would be useful, it process explorer / task manager doesnt show you any activity, then you should go for complete memory dump ( neither kernel dump would help ).

Hi, I would like to suggest you test the issue in Clean Boot to check if there is any third party software conflicts. To perform a Clean Boot: 1. Click the "Start" Button, type "msconfig" in the search bar and press Enter. Note: Please click the Continue if the "User Account Control" window pops up. 2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray). 3. Click the "Startup" tab, click "Disable All" and click "OK". Then, restart the computer. When the "System Configuration Utility" window appears, please check the "Don't show this message or launch the System" 4. Test if the issue reoccurs in Clean Boot. Note 1: Temporarily disabling the Startup Group only prevents the startup programs from loading at startup. This shouldn't affect the system or other programs. We may still manually run these programs later. Note 2: We can check on Normal Startup in the General tab to roll back to Normal Mode after we get this issue resolved. What’s the result in Clean Boot? Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks all for getting back to me. After much head scratching, I tracked it down to the A/V. When I uninstalled the A/V, it left a folder (in Program Files) with a load of files in. One must have been still trying to access the system somehow. Deleting the folder and rebooting the Server seems to have cured the problem. I will punt this to Eset. Again, many thanks for all your suggestions.Dominic