Hyper-V Blue Screens when uninstalled
The setup of Hyper-V requires one NIC to be set without IPv4 or IPv6. When a vhd is reconnected, it may be changing the state of the NIC. When resetting the state back to no IPv4 or IPv6, the screen freezes on the NIC reset - as a side symptom,
the Virtual connected to the non-ipv4/ipv6 configured card will go into a non=stopped state (it will freeze on stopping). In order to reset the HYPER-V so that all functionality of the server is restored, the role, Hyper-V can be removed. Upon
removal, a restart is requested - restart. Eventually hyper-v machine will Blue Screen during the uninstall of HYPER-V. This sequence more closely approximates what I have seen happening repeatedly on my HYPER-V.
Faulting application name:VDeck.exe, version: 7.6.0.30, time stamp: 0x4ae7ac7f
The time service encountered an error and was forced to shut down. The error was: 0x80070005: Access is denied
Installation Failure: Windows failed to install the following update with error 0x800706ba: Update for Windows Server 2008 R2 x64 Edition (KB252422).
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events
cannot be delivered through this filter until the problem is corrected.
Session "" failed to start with the following error: 0xC0000043
Warnings for timeserver are
NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 3473457 minutes and double the reattempt interval thereafter. The error was: The entry is not found. (0x800706E1)
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033
Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA80082BFA10
BCP3: FFFFF8000161A518
BCP4: FFFFFA800943EB20
OS Version: 6_1_7601
Service Pack: 1_0
Product: 274_3
Files that help describe the problem:
C:\Windows\Minidump\052111-32869-01.dmp
C:\Users\xxx\AppData\Local\Temp\WER-80122-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If
R, J
May 21st, 2011 3:16pm
Bug Check Code 0x9F: http://msdn.microsoft.com/en-us/library/ff559329(VS.85).aspx
Pleqse use Microsoft Skydrive to upload C:\Windows\Minidump\052111-32869-01.dmp dump file. Once done,
post a link here.
You can also contact Microsoft CSS.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2011 4:45pm
Please set the folder for public access.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
May 21st, 2011 7:04pm
Hello,
are you sure that this is the correct link? Please verify. I am unable to access it.
I need to get the dump to determine the cause of the BSOD.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2011 12:16am
While I am at it, I see what appears to be another, difficult to understand, issue. Part of why I am getting the BSOD is that I have a virtual vhd that needs to be remounted. There is data on the SQL Server Backup directory that needs to be aquired
and studied so it is critical that I remount the VM and give it access to the domain (to copy the bak file), but it was the VM that originally burnt out the first gigabit adapter that is the required vhd to remount (subsequently replaced). There
were a few other VM's on this virtual... trying to remount them seems to result in the same error. The only VM that needs to be captured is the SQL VM.
Here are the steps:
1) Create the HYPER-V Role with adapter one "Local Area Connection" set to the domain (host machine dedicated adapter) and adapter two "Local Area Connection 2" set without IPv6 or IPv4 (dedicated VM adapter).
2) Open the Virtual Network Manager and define the Local Area Connection 2 as the virtual NIC. Create a new virtual and use the image from the SQL VM.
3) SQL VM opens with everything running except the public connection to the domain. (minus the ability to navigate the domain network or this would be finished - I would delete the VM and start again)
4) Checking the adapter on the SQL VM seems to be changing the state of the Virtual Network manager because when the VM hangs on shutdown,
http://blogs.msdn.com/b/virtual_pc_guy/archive/2011/01/11/shutting-down-a-virtual-machine.aspx, somehow the host Local Area Connection 2 gets reset with the IPv6 and IPv4 turned back on. Then the host itself goes into a mode where the Local Area
Connection 2 cannot be reset and thus the problems above.
Since the virtual will not shut down, it is necessary to remove the role and start from the top again. The BSOD occurs during this reiteration - I wait for the Local Area Connection 2 to reset with IPv4 and IPv6 unchecked. This process goes on
for a good half hour or more and at this point, I expecting another BSOD.
I am guessing there is something wrong in the old VM that must be remounted... somehow the Network Connection there is expecting something to exist that doesn't and the VM has some control over the host network adapter that I am missing. If during
the iteration (1-4 above), I could figure out what to do on the VM side to thwart the BSOD, I might actually accomplish the goal of capturing the SQL backup that is on the VM.
R, J
May 22nd, 2011 3:04pm
You uploaded sysdata file. I said upload C:\Windows\Minidump\052111-32869-01.dmp file.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2011 3:13pm
Hi,
Since Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a third-party device drivers, backup software or anti-virus services (buggy services).
The system goes to a BSOD because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case
some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).
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. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that
a dedicated Support Professional can assist with your request. 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:
Microsoft - Help and Support
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If
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.
May 24th, 2011 11:43am
Turns out it was something simple. All the problems went away when I disabled Large Send Offload on the NIC.R, J
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2011 4:39am