Exchange 2013 VM on Hyper-V BSOD

Have you installed at least Cumulative Update 3 on your Exchange servers? Have a look at this article and see if it applies to you: http://support.microsoft.com/kb/2883203

If it does apply to you, look at upgrading to CU3 at the very least. Ideally though your environment would be up to date (I believe the most current is CU7)

Yes, exchange has the most current update CU7 so i don't think article applies...

Have you checked to see if it's the Managed Availability feature that's forcing the server reboots though?

The Managed Availability feature detects issues with your server and in the event of an issue attempts to fix the problematic component. Fixes can range from simple restarts of the component (e.g. restarting the service) to doing a bugcheck.  Bugchecks occur when the earlier simple fixes don't work.

To confirm if Managed Availability is the cause of the bugchecks, run the below command in PowerShell:

(Get-WinEvent -LogName Microsoft-Exchange-ManagedAvailability/* | % {[XML]$_.toXml()}).event.userData.eventXml| ?{$_.ActionID -like "*ForceReboot*"} | ft RequesterName

Select allOpen in new window

If you do find that the server is being bugchecked by the ActiveDirectoryConnectivityConfigDCServerReboot responder that's part of the Managed Availability service then run the below command to delay the responder for 60 days:

Add-GlobalMonitoringOverride -Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00

Select allOpen in new window

If you would like to do some more reading on the Managed Availability feature you can do so here: http://technet.microsoft.com/en-us/library/dn482056%28v=exchg.150%29.aspx

Thank you for your reply. I have tried that and it look like the ActiveDirectoryConnectivityServerReboot is causing the bugcheck and restart however the property value is not changing with override and stays on 1...

Sorry, forgot to mention that if you have multiple domain controllers then it's best to force replication, then wait about 10-15 minutes for the Microsoft Exchange Health Manager Service to pick up the override setting.

Thanks,

Yes, i tried that command to confirm and it's still on 1. Tried version override as well and same still on 1... :(
override.png

Try forcing AD replication then wait about 10-15 minutes. Re-run the command then to check if the override has taken effect.

Are you seeing clock drift warnings in the logs (blog post on the matter) as well?

If yes, is your PDCe physical or virtual as well?

Download finished.

Mbx and Cas DMP: WinInit.exe
A critical system process died
Arguments:
Arg1: ffffe00191cf2080, Process object or thread object

Both are the same.

I had some problems with the access list on the core switch and they are now fixed. Since then there was no reboot or crash of any kind. Could that be the issue from the beginning? No i do not have any clock drifts and all my DC are virtual.

Is the ActiveDirectoryConnectivityServerReboot responder disabled though?

No, ActiveDirectoryConnectivityServerReboot is not disabled.