I am running Windows Hyper-V Server 2012 R2 (Server Core) on three servers. Unfortunately none of them have identical hardware configurations - thus I can't easily tell if there is some compatibility problem between a Microsoft update and my hardware. All three systems are setup to automatically download updates.
A few weeks ago one of the systems seemed to be rebooting regularly. After connecting a monitor I saw a BSOD with a message "Critical Process Died." I'm not 100% certain of this, but these BSOD reboot problems seemed to have started shortly after getting a recent automatic update(s)?
I have checked the Event Logs and looked for dumps or other logs, but haven't been able to locate anything that explained the chronic BSOD failures on the one server. Nor have I found anything that tells me what critical process died.
After various attempts to fix the problem were unsuccessful I reformatted the drive and reinstalled Hyper-V Server 2012 R2. The server seems to work okay with the intial re-installation of Hyper-V Server 2012 R2.
I configured the server and then start to download all the availlable patches. After one (or two?) reboots I typically find only a single patch (KB2919355) left to be installed. This seems to be the equivalent of the Windows 8.1 Update (and thus a required patch to get further patches)?
Typically when I try and install KB2919355 I'll get a BSOD during the installation process. I have also tried rebooting and looking for new patches, after the initial BSOD, and I'll get a list of some other patches. KB2919355 seems to be a group of fixes? And it seems as though some part of KB2919355 got installed, but then I get the BSOD. And after the reboot what I'm seeing is the list of the group (from KB2919355) which did not get installed due to the BSOD?
I continued on (rebooting if a BSOD occurred) and eventually got all patches installed. But I still get occasional BSOD failures with Critical Process Died message. The message says something about writing information to disk with 0% complete, but that number never changes. After a while the system simply reboots.
After all patches were installed I came across the following commands and tried to use them. The first time I attempted to use DISM I got a BSOD failure. But I was eventually able to run both SFC and DISM. Neither seemed to show any problems were found.
sfc /scannow
dism /online /cleanup-image /restorehealth
In one (of several) attempts to re-install Hyper-V Server 2012 R2 I made sure my BIOS was updated to the latest version and got the most recent driver for my Areca ARC-1222 controller. Of the three servers one has the Areca RAID6 controller, one has an LSI RAID6 controller, and one is using Storage Spaces. The LSI and SS systems have the same type of CPU, motherboard, and RAM. My Areca system has an older type of CPU, motherboard, and RAM.
This morning I tried to re-install Hyper-V Server 2012 R2 again. After the first group of patches were installed and a reboot I got another large list of patches. I don't recall off hand if this was the exact same order of patches that happened on prior attempts or not? I had thought there was only one large list of patches, reboot, and then KB2919355 was the only remaining patch? While trying to install this second large list of patches I got a BSOD. I didn't notice whether or not KB2919355 was included in this second list or not? These kind of inconsistent results/observations are why I'm not 100% sure that KB2919355 is causing my BSOD problems. I believe KB2919355 is installed and working on my other two systems? Which might imply some type of a hardware problem with this system?
Unless someone has a better suggestion then later tonight I'll try re-installing Hyper-V Sever 2012 R2 again, but stopping before KB2919355 gets installed. It seems to me the system is stable at this point, but I'll leave it that way for several hours to verify I don't get another BSOD. If I don't have any problems without KB2919355 installed that implies my hardware is okay. Although I suppose there could be some incompatibility between KB2919355 and my hardware and not simply a software problem with KB2919355?
I would appreciate suggestions others may have on how to rectify this problem. Especially any thoughts on how to determine what critical process is failing and causing the BSOD.
I did come across a webpage about a whole list of symptoms related to KB2919355, but my specific problem didn't seem to be mentioned.
http://social.technet.microsoft.com/Forums/en-US/c203334f-7ae5-4716-aeb5-0fa3d60da216/kb2919355-issues-being-investigatedtracked?forum=winserver8gen
Thanks for any assistance.
A few weeks ago one of the systems seemed to be rebooting regularly. After connecting a monitor I saw a BSOD with a message "Critical Process Died." I'm not 100% certain of this, but these BSOD reboot problems seemed to have started shortly after getting a recent automatic update(s)?
I have checked the Event Logs and looked for dumps or other logs, but haven't been able to locate anything that explained the chronic BSOD failures on the one server. Nor have I found anything that tells me what critical process died.
After various attempts to fix the problem were unsuccessful I reformatted the drive and reinstalled Hyper-V Server 2012 R2. The server seems to work okay with the intial re-installation of Hyper-V Server 2012 R2.
I configured the server and then start to download all the availlable patches. After one (or two?) reboots I typically find only a single patch (KB2919355) left to be installed. This seems to be the equivalent of the Windows 8.1 Update (and thus a required patch to get further patches)?
Typically when I try and install KB2919355 I'll get a BSOD during the installation process. I have also tried rebooting and looking for new patches, after the initial BSOD, and I'll get a list of some other patches. KB2919355 seems to be a group of fixes? And it seems as though some part of KB2919355 got installed, but then I get the BSOD. And after the reboot what I'm seeing is the list of the group (from KB2919355) which did not get installed due to the BSOD?
I continued on (rebooting if a BSOD occurred) and eventually got all patches installed. But I still get occasional BSOD failures with Critical Process Died message. The message says something about writing information to disk with 0% complete, but that number never changes. After a while the system simply reboots.
After all patches were installed I came across the following commands and tried to use them. The first time I attempted to use DISM I got a BSOD failure. But I was eventually able to run both SFC and DISM. Neither seemed to show any problems were found.
sfc /scannow
dism /online /cleanup-image /restorehealth
In one (of several) attempts to re-install Hyper-V Server 2012 R2 I made sure my BIOS was updated to the latest version and got the most recent driver for my Areca ARC-1222 controller. Of the three servers one has the Areca RAID6 controller, one has an LSI RAID6 controller, and one is using Storage Spaces. The LSI and SS systems have the same type of CPU, motherboard, and RAM. My Areca system has an older type of CPU, motherboard, and RAM.
This morning I tried to re-install Hyper-V Server 2012 R2 again. After the first group of patches were installed and a reboot I got another large list of patches. I don't recall off hand if this was the exact same order of patches that happened on prior attempts or not? I had thought there was only one large list of patches, reboot, and then KB2919355 was the only remaining patch? While trying to install this second large list of patches I got a BSOD. I didn't notice whether or not KB2919355 was included in this second list or not? These kind of inconsistent results/observations are why I'm not 100% sure that KB2919355 is causing my BSOD problems. I believe KB2919355 is installed and working on my other two systems? Which might imply some type of a hardware problem with this system?
Unless someone has a better suggestion then later tonight I'll try re-installing Hyper-V Sever 2012 R2 again, but stopping before KB2919355 gets installed. It seems to me the system is stable at this point, but I'll leave it that way for several hours to verify I don't get another BSOD. If I don't have any problems without KB2919355 installed that implies my hardware is okay. Although I suppose there could be some incompatibility between KB2919355 and my hardware and not simply a software problem with KB2919355?
I would appreciate suggestions others may have on how to rectify this problem. Especially any thoughts on how to determine what critical process is failing and causing the BSOD.
I did come across a webpage about a whole list of symptoms related to KB2919355, but my specific problem didn't seem to be mentioned.
http://social.technet.microsoft.com/Forums/en-US/c203334f-7ae5-4716-aeb5-0fa3d60da216/kb2919355-issues-being-investigatedtracked?forum=winserver8gen
Thanks for any assistance.
Theokrat