Windows Server 2003 R2 SP1 2Gz CPU. Users started losing connection to Server, cannot ping Server, switch/cabling good, display shows"no signal". hard reset brings the server back online...may work fine for 5-8 hours. Event log shows "unexpected shutdown" at time long before actual hard reset (If server is unresponsive at 9:00 am and is hard reset then the event log shows there was an unexpected shutdown well before...like 7:00pm the day before.) No other errors in event viewer around time of unexpected shutdown. All fans working in Server and UPS tested good (unplugged and it powered the Server). TIA

Hello, first step is to update the server to SP2 and all latest patches, so all already solved problems are excluded. Then go on with the drivers of the server to exclude them also. If this doesn't help and no errors are shown in the event viewer of the server let's go on with the basic configuration settings and post an unedited ipconfig /all from the server and a problem machine. Additional give a description how your network is built.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Hi, I would like to suggest you update the BIOS and the hardware drivers first. If the issue persists, would you please send me more information for analyzing. For your convenience, I have created a workspace for you. You can upload the information files to the following link. (Please choose "Send Files to Microsoft") Workspace URL: https://sftasia.one.microsoft.com/choosetransfer.aspx?key=9554ac53-5284-468b-97c2-ca985e6274a1 Password: 2%nHGi*u$O+^pvK Note: Due to differences in text formatting with various email clients, the workspace link above may appear to be broken. Please be sure to include all text between '(' and ')' when typing or copying the workspace link into your browser. Meanwhile, please note that files uploaded for more than 72 hours will be deleted automatically. Please ensure to notify me timely after you have uploaded the files. Thank you for your understanding. Collect Minidump Files ================= 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”. If the Blue Screen appears again, please refer to the following steps to collect memory dump files: 1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”. 2. Go to your Desktop, right-click on it and create a new folder named "Dump". 3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder. 4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder". 5. Please send the ZIP file to us. You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB article below: How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263 If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 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.