WHEA_UNCORRECTABLE_ERROR during power down

This machine is NOT overclocked and the AIDA Full Report performs full benchmarking on the hardware and is included in that report.

I cloned my hard disk before I added the Hyper-V functionality. I just booted up on it and everything is working fine. The pagefile virtual memory is system allocated at 12GB and the machine powers down properly. So it's pretty clear that Hyper-V is a problem.

Unfortunately, I'm retired these days, so I don't have the same ability to connect with M$ support anymore. Previously I was an IT type with a Fortune 500. I wonder if M$ monitors these forums?

But it's still clear that there are major bugs with Hyper-V with W10 none the less. The pagefile allocation is totally bogus for example. The reason I'm doing this stuff is due to my circle of friends that are asking all sorts of questions about W10. I'm sure glad that I didn't migrate my own production machine to W10 and I'm NOT recommending that anyone else do so either. M$ has again released an OS that's not ready for prime time.

axe0 said:

There are lots of bugs in the first few months after the release of a new OS.
I don't say windows 10 is bad, but I am saying to wait a few months so the software and drivers can be made compatible and the bugs solved.
It usually takes 3 to 4 months for the most problems to be solved properly.

Let's be specific... This is true when you speak of Microsoft products and saying that they last for 3 or 4 months is being VERY generous. RTM really means "Rush To Market". To compare: you never see Cisco IOS come to market with serious bugs like I've seen with every M$ product. I don't work with Apple products, so I'm not sure about theirs. But even public supported software like Linux variants are far cleaner out of the box during a new distribution.

To put it plainly; W10 appears to be a big patch job to get W7 functionality back into the OS that should have been there already. It's really sickening having to drill down to W7 functions to do common, simple adjustments though. This stuff should have all been FULLY integrated into the finished product.

So in the end I'll need to do some more testing to see if Hyper-V functionality on W10 is even more corrupted than I've found already. Will they ever fix it? Have they ever even documented all their error messages?