Hi I have a Windows 2008 R2 server running in a remote location so I prefer the automatic restart option. I have this checked in advanced -> startup and recovery. Randomly I get BSOD errors due to an application I run, happens randomly once a month however when this occurs the system just halts and I need to remote reboot the machine to get it up and running. With "automatic restart" checked why is the system not recovering automatically ? Is there anything I can do ? thanks

What's on the screen at the time this happens? Might not be sitting at the screen dump? Also navigate to HKEY_LOCAL_MACHINE\SYSTEM\Select and look in the Reg_Dword value of "Current", this is the current controlset, then navigate to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00x\Control\CrashControl Where x = the value of "Current" (found above) and check the values as follows "AutoReboot"=dword:00000001 http://technet.microsoft.com/en-us/library/cc976049.aspx Regards, Dave Patrick .... Microsoft Certified Professional -Microsoft MVP [Windows]

thanks for the response Dave Yes it is set to 1 I could not see what was on the screen as I dont have a remote KVM, I just remote reboot the sucker and it comes back up. Did you wanna see the minidump or is it imperative to see whats on the screen ?

No. Just thinking it may not be a dump screen at all. Might be something related to cmos setup or in the case of some proliant DL380's I have it was buggy firmware that caused this. (sometime hung at the white proliant screen) Regards, Dave Patrick .... Microsoft Certified Professional -Microsoft MVP [Windows]

No. Just thinking it may not be a dump screen at all. Might be something related to cmos setup or in the case of some proliant DL380's I have it was buggy firmware that caused this. (sometimes hung at the white proliant screen) Regards, Dave Patrick .... Microsoft Certified Professional -Microsoft MVP [Windows]

Its a Supermicro X7SBL board,

Not sure that means anything. Bottom line is someone is going to need to look at the screen to see the machine state. Regards, Dave Patrick .... Microsoft Certified Professional -Microsoft MVP [Windows]

Follow the below steps Click Start, and then click Control Panel. Click System. On the Advanced system Setting tab, click Settings under Startup and Recovery. Select small memory dump and restart refer the below link for more details . http://support.microsoft.com/kb/130536 http://support.microsoft.com/kb/254649

Hi, By default, if you have “Automatically restart” box checked, the computer restarts when system fails. But sometimes, it fails to restart, such as BSOD. The system die and cannot perform the restart command. Based on the current situation, you’d better troubleshoot the BSOD issue. 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=19264c0a-53ec-43f2-a97b-4329984c5474 Password: {Tq7duahDt1wj 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: How to read the small memory dump files that Windows creates for debugging. 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.

Arthur, I had the issue again 2 days ago and I would like to upload the minidump. Can you create the workspace for me again please. Here is what I got from the win debug, the cause is always the same process, the "monitor service". This is a custom application that runs game servers in the background as a service. These game servers are just .exe files, games such as halo and counterstrike. I brought up the issue with the developer and they say it may be a compatibility issue with .net Framework 1.1. Would you guys be able to assist at all ? Here is what I see on screen when I get BSOD: 1. Black screen no VGA signal 2. If I remotely reboot the server Windows comes up to the login screen but no network connectivity. I have to manually uninstall and reinstall the network card driver (Intel pro 100/1000 PL) to regain connectivity. I reinstalled the network card drivers and chipset drivers and ran some more remote reboot tests (shut power off and on) and it seems to be working now. But I would like to know from you guys if possible please: 1. How can I prevent this BSOD 2. Is there any program or setting that will restart the server instead of getting this lookup (black screen) and having to remote reboot it. =============== Here is the snippet from the minidump =============== ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck F4, {3, fffffa80077c1060, fffffa80077c1340, fffff80001b885d0} Probably caused by : _ Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. Arguments: Arg1: 0000000000000003, Process Arg2: fffffa80077c1060, Terminating object Arg3: fffffa80077c1340, Process image file name Arg4: fffff80001b885d0, Explanatory message (ascii) Debugging Details: ------------------ PROCESS_OBJECT: fffffa80077c1060 IMAGE_NAME: _ DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: _ FAULTING_MODULE: 0000000000000000 PROCESS_NAME: MonitorService BUGCHECK_STR: 0xF4_MonitorService CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001c09652 to fffff8000187d740 STACK_TEXT: fffff880`0707ab08 fffff800`01c09652 : 00000000`000000f4 00000000`00000003 fffffa80`077c1060 fffffa80`077c1340 : nt!KeBugCheckEx fffff880`0707ab10 fffff800`01bb23e3 : ffffffff`ffffffff fffffa80`0975e7d0 fffffa80`077c1060 fffffa80`086885f0 : nt!PspCatchCriticalBreak+0x92 fffff880`0707ab50 fffff800`01b3a80c : ffffffff`ffffffff 00000000`00000001 fffffa80`077c1060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17946 fffff880`0707aba0 fffff800`0187c993 : fffffa80`077c1060 00000000`ffffffff 00000000`7ef2d001 fffffa80`0975e7d0 : nt!NtTerminateProcess+0x20c fffff880`0707ac20 00000000`7788001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0474e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7788001a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0xF4_MonitorService_IMAGE__ BUCKET_ID: X64_0xF4_MonitorService_IMAGE__ Followup: MachineOwner --------- 3: kd> !process fffffa80077c1060 3 GetPointerFromAddress: unable to read from fffff80001ab5000 PROCESS fffffa80077c1060 SessionId: none Cid: 01dc Peb: 7fffffdf000 ParentCid: 01d4 DirBase: 21820c000 ObjectTable: fffff8a0016b66f0 HandleCount: <Data Not Accessible> Image: csrss.exe VadRoot fffffa80077bed90 Vads 58 Clone 0 Private 334. Modified 101. Locked 0. DeviceMap fffff8a000008c10 Token fffff8a0016b6a60 ReadMemory error: Cannot get nt!KeMaximumIncrement value. fffff78000000000: Unable to get shared data ElapsedTime 00:00:00.000 UserTime 00:00:00.000 KernelTime 00:00:00.000 QuotaPoolUsage[PagedPool] 0 QuotaPoolUsage[NonPagedPool] 0 Working Set Sizes (now,min,max) (971, 50, 345) (3884KB, 200KB, 1380KB) PeakWorkingSetSize 971 VirtualSize 42 Mb PeakVirtualSize 42 Mb PageFaultCount 1131 MemoryPriority BACKGROUND BasePriority 13 CommitCharge 449 *** Error in reading nt!_ETHREAD @ fffffa80077c7b60