http://blogs.dootdoot.com/mike

Back in February I started a proejct to move my WHS to be a Virtual Machine running under Windows Server 2008 and Hyper-V. Originally I thought this would be the ideal setup, as I could have an excuse to play with Server 2008, and also take advantage of its disk pass-through feature to give WHS the best running conditions, while still having plenty of resources to dedicate to other Virtual Machines.

Unfortunately, lately I have been running into some issues with performance. The problem has been difficult to resolve, as I am receiving random BSOD’s under heavy disk usage. Mainly, when transferring large volumes from or to any virtual machine running under Hyper-V.

Right now I really have no leads, it could be a driver problem, a faulty disk, a bad stick of memory… who knows. The problems seemed to have started around the time I upgraded the memory from 4gb to 6gb (after 8gb wouldn’t boot).

I will have to see about removing the additional 2gb, and seeing if that makes a difference, which is a bummer becuase my current setup is using around 5.5gb memory at any given time. Ultimately though, I think I am going to just reinstall back on my original Virtual Machine server and separate WHS from my Home Virtual Server again. WHS just seems to important to continue trying to run as a VM. I guess am ok with it being its own dedicated server, especially if it stops my random crashes.

Comments

7 Responses to “Home Server BSOD”

  1. seth on June 16th, 2009 10:03 am

    Have you considered trying a different motherboard?

    Non-ideal I know, but you just have had random issues the last 6 months and your server is running less stable than midget’s cable.

  2. mike on June 17th, 2009 3:11 pm

    I removed the extra memory, and did a quick load test on the server, that killed it. So I am checking that off the list that it was not the memory expansion.

    I have not tried a new motherboard, and my research on the STOP 0x0000000A I receive points to it being a potential driver issue.

    However, I don’t have any more real information to go off of, other than reinstalling every driver I can find. I wish there was a better indication as to what is crapping out. :/

  3. phil on June 17th, 2009 10:51 pm

    Did you try running some off-line diags on the hardware? If you suspect the memory you should probably run memtest86+ for a few full passes and make sure you are not taking in random bit errors.

  4. mike on June 18th, 2009 10:06 am

    I do plan on running memtest, but I have to take some time and take down keyboard/monitor/etc from another computer to hook it up to that one.

    However, the BSOD STOP message I was receiving still points to a driver issue. It’s quite possible that there is an easy to miss component in my setup that is just not Server 2008 friendly.

  5. PE2800 Fail : dsu | Mike on July 3rd, 2009 2:36 am

    [...] Windows Server 2008 and running Windows Home Server in a virtual machine, I have been having stability issues. As I do not appreciate this, I have been meaning to move my Windows Home Server back to a [...]

  6. Update: Home Server Success : dsu | Mike on July 24th, 2009 6:07 pm

    [...] around mid-May I had been having random BSOD/reboot problems with my main server that runs my home virtual machines, including my windows home server. While I [...]

  7. P35-DS3P v1.1 – 8GB (4x2GB) : dsu | Mike on August 8th, 2010 10:40 pm

    [...] try. At first it wasn’t going so hot, but eventually I re-checked and apparently last June, a few months after I gave up on it, there was another BIOS update [...]

Leave a Reply