CHI-LTD
asked on
Windows 2012 R2 server BsoD after Windows updates
Hi
Windows Server 2012 R2 VM runnign on VMware esxi 6.0 fully windows patched.
Its decided to fall over.
I can get it into windows if i F8 and select the signing device driver option (second from bottom).
There after is continues to blue screen.
I've tried sfc, dism, disabling device driver signing etc.
Restored from backup
Any other suggestions?
Windows Server 2012 R2 VM runnign on VMware esxi 6.0 fully windows patched.
Its decided to fall over.
I can get it into windows if i F8 and select the signing device driver option (second from bottom).
There after is continues to blue screen.
I've tried sfc, dism, disabling device driver signing etc.
Restored from backup
Any other suggestions?
You restored from a backup made before the updates?
ASKER
Tried this and it booted up fine only to fail again
What about VMware Tools? Is it up to date or have you tried re-installing them?
Then it is extremely unlikely the updates are the cause. What is the specific blue screen error?
ASKER
Yes they are running and ive reinstalled them.
Critical service error: https://social.technet.microsoft.com/Forums/en-US/2c9b39c3-4cca-4de0-a988-28f2b4d03eb7/win-2012-r2-bsod-critical-service-failure?forum=winserver8setup
Critical service error: https://social.technet.microsoft.com/Forums/en-US/2c9b39c3-4cca-4de0-a988-28f2b4d03eb7/win-2012-r2-bsod-critical-service-failure?forum=winserver8setup
ASKER
sfc /scannow fails
ASKER
Tried:
https://social.technet.microsoft.com/Forums/en-US/811deebe-4f84-41cc-9403-c7c2d9f904b6/win2012-r2-criticalservicefailed-win8driverfault?forum=winserver8gen
https://social.technet.microsoft.com/Forums/en-US/2c9b39c3-4cca-4de0-a988-28f2b4d03eb7/win-2012-r2-bsod-critical-service-failure?forum=winserver8setup
https://social.technet.microsoft.com/Forums/windowsserver/en-US/063f7600-8e4b-404f-9d35-d3b55b474a2d/disable-driver-signature-enforcement?forum=winserver8gen
https://social.technet.microsoft.com/Forums/windowsserver/en-US/5e048b0f-83b2-4281-b5e9-533ef3de564d/disable-driver-signature-enforcement-permanetly-at-bootup-how?forum=winservergen
https://social.technet.microsoft.com/Forums/azure/en-US/bc5aabaa-a134-4763-bee2-0c5c4853b392/criticalservicefailed-blue-screen-in-windows-2012-r2?forum=winserverhyperv
https://social.technet.microsoft.com/Forums/en-US/2c9b39c3-4cca-4de0-a988-28f2b4d03eb7/win-2012-r2-bsod-critical-service-failure?forum=winserver8setup
https://support.microsoft.com/en-za/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness
https://searchwindowsserver.techtarget.com/tip/Enlist-Windows-SFC-and-DISM-tools-to-fix-server-OS-problems
https://social.technet.microsoft.com/Forums/en-US/811deebe-4f84-41cc-9403-c7c2d9f904b6/win2012-r2-criticalservicefailed-win8driverfault?forum=winserver8gen
https://social.technet.microsoft.com/Forums/en-US/2c9b39c3-4cca-4de0-a988-28f2b4d03eb7/win-2012-r2-bsod-critical-service-failure?forum=winserver8setup
https://social.technet.microsoft.com/Forums/windowsserver/en-US/063f7600-8e4b-404f-9d35-d3b55b474a2d/disable-driver-signature-enforcement?forum=winserver8gen
https://social.technet.microsoft.com/Forums/windowsserver/en-US/5e048b0f-83b2-4281-b5e9-533ef3de564d/disable-driver-signature-enforcement-permanetly-at-bootup-how?forum=winservergen
https://social.technet.microsoft.com/Forums/azure/en-US/bc5aabaa-a134-4763-bee2-0c5c4853b392/criticalservicefailed-blue-screen-in-windows-2012-r2?forum=winserverhyperv
https://social.technet.microsoft.com/Forums/en-US/2c9b39c3-4cca-4de0-a988-28f2b4d03eb7/win-2012-r2-bsod-critical-service-failure?forum=winserver8setup
https://support.microsoft.com/en-za/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness
https://searchwindowsserver.techtarget.com/tip/Enlist-Windows-SFC-and-DISM-tools-to-fix-server-OS-problems
It looks like you've went through a lot to get to a worse position than you were before.
My thoughts are have you tried DISM with a different repair source from a working system of the same build?
Also, I think it's likely a "hardware" issue. By chance are you using the VMXNET3 for a network adapter and if so have you considered changing it to E1000. This is just a shot in the dark but I've had issues with the network drivers and the virtual adapters that altering the card type helped.
My thoughts are have you tried DISM with a different repair source from a working system of the same build?
Also, I think it's likely a "hardware" issue. By chance are you using the VMXNET3 for a network adapter and if so have you considered changing it to E1000. This is just a shot in the dark but I've had issues with the network drivers and the virtual adapters that altering the card type helped.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What is the error message in the bluescreen? Can you upload a screen shot? One option is the boot from the Windows 2012 ISO and got to recovery options and copy the affected driver from the CD to the server
ASKER
Rebuilt the VM in the end.