• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Hyper-V VM BSOD issue

R

rhouck

2[H]4U
Joined
Apr 15, 2002
Messages
3,597
Not entirely sure where to put this, but seems like it may be distinct to it being a VM.

My current setup is Win Server 2008 R2, with two Hyper-V VMs: one Windows Home Server, the other Windows 7. The main hard drives are two RAID 1 SATA drives (this is where the 2008R2 OS as well as the VMs reside) -- the rest of the drives are storage and added to WHS via passthrough.

Starting yesterday, my WHS VM started BSODing. It boots up, runs for maybe 5 minutes, then BSOD. Rinse repeat. Restarting into safe mode made it more stable (last for closer to an hour it seemed), but still same BSOD.

No software changes have been made recently. No hardware changes have been made recently. Windows updates are not automatically applied.

What is strange to me is that the main 2008R2 server itself as well as my Win7 VM are still perfectly stable. Uptime is currently 50+ days and last reboot was manual (not a crash).

I have received two different BSODs:
1. http://i.imgur.com/JJeiH.jpg
2. http://i.imgur.com/2TR94.jpg

The second appears to be the most common.


It is odd to me because there are no recent software or hardware changes, and the main OS and other VM are still stable (suggesting to me that hardware failure should not be an issue).

Any ideas on resolving this issue? Thanks in advance.
 
Physical Memory
Total 6133
Cached 807
Available 1201
Free 437

It's 6gb with 2gb assigned to each VM. (I should add this is the hardware setup I've been running for a couple years now without any changes except an occasional new hard drive or two)

Unless you're looking for something from Resource Monitor specifically.
 
Also, check the health of the passthrough drives. Run a checkdisk /r from the host. You may need to powerdown your vms to release the resources.
 
tmillszero1 said:
what's the uptime of your host? and if it is a bit excessive can you bounce it?
Click to expand...

50 or so days (9/13/2012). I can reboot it. Was waiting in case stability issue might affect rest of machine (the VM is unusable right now, as most of the 5 minutes before it crashes is taken up by booting to the desktop -- very difficult to even troubleshoot)


I'll check re doing chkdsk as well. I did it within the VM and from host originally without issue, but just checked root drive.
 
tmillszero1 said:
So I should have asked this earlier... Does it blue screen on safe boot? (The VM)
Click to expand...

Yes, it does. It is significantly more stable (in fact, I originally thought it might have fixed the issue). But it crashes probably after about an hour (maybe more/less -- harder to confirm with such a longer gap between crashes). Same BSOD error as #2.
 
I'd remove the shared drives from the problematic VM... see if that stabilizes things.
 
tmillszero1 said:
I'd remove the shared drives from the problematic VM... see if that stabilizes things.
Click to expand...

Ill add this to queue of things to check.

Now Disk Management in host OS is showing my RAID 1 has failed redundancy and one of the OS drives has Errors. (though CHKDSK comes back clean)

I'm not sure how to force a check for errors on one drive within a RAID 1 array. My current plan is to physically unplug one and run CHKDSK separately on both (to figure out which has errors).
 
I'm leaning toward there being corruption of the software the WHS VM is running. Can you step back to a previous snapshot or reload from backup? That'd at least confirm that "the same" software is or isn't causing a BSOD.

As to how the software might have gotten corrupted, that's anyone's guess. But I'd certainly see about getting a new drive to replace that failed unit. Some drive errors are just transients and might never come up again. Or you can buy a new one and avoid proving it's the drive. If it's in warranty then now's the time to RMA it.
 
UPDATE:

Broke RAID 1 mirror. Ran CHKDSK on each. A ton of errors on one, and some on other. The drives are now 38 months old, so I just missed any available warranty...

Unfortunately, after fixing them all and rebooting, VM still has same BSOD.

It does sound like that the VM is corrupted. I will check to see if there is a snapshot I can roll back to.
 
You must log in or register to reply here.
Back
Top