Windows 10: WHEA_UNCORRECTABLE_ERROR during power down

This error is now occurring after enabling Hyper-V in the Win10 OS Features. All of the automatic patching and configuration that takes place after enabling Hyper-V seems to have processed normally with several reboots noted. There are NO virtual environments defined as yet, nothing has been configured, and the Hyper-V management screen displays normally when started.. The error only occurs during system shutdown and the screen that displays waiting process closure seems to flash by quickly. Any method of initiating a power shutdown will cause the crash and it will occur even if no user has logged into the machine. The machine automatically reboots after the crash so I currently need to manually power down the machine during the bios screen. The machine has never been in sleep mode and automatic sleep is disabled. Hybernation is disabled on the machine too. BUT THIS IS BAZAAR... If I reboot, the machine does NOT crash. If something requests the machine to reboot (eg: for a software change), everything processes normally.

:)

 

Blue Screens for the first time

WHEA_UNCORRECTABLE_ERROR means "hardware error" - so more than likely it was a short circuit, a failed device, or could even be not receiving enough voltage from the power supply. It can also happen when the
computer is overclocked.

 

Nokia 8910i powers down during calls???

I alos have the same problem. but there is no answer in this discussion form.

Edited out personal contact details

Message Edited by linwood on 20-Jan-2009 11:39 AM

 

Hi tgm,

Welcome to the 10forums.

Please check {windows partition}\windows\minidump and check if there are any dump files saved.
The zip is empty of dump files.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial

 

Now this is interesting... The dump was previously configured to Kernel Dump, so I changed it to Small Memory Dump as you requested. I then attempted a shutdown and the machine crashed with the WHEA error as expected. BUT after the reboot, the minidump directory is still empty! So I went back to check the config and it is still set to Small Memory Dump.

I've now unchecked the auto reboot to see if this changes anything. During a shutdown attempt... It did stop the auto-reboot but the minidump directory is still empty.

So as a possible alternative I've run both an AIDA OS report and a AIDA Full report and attached them in the hope that they may give you most if not all of the data you are looking for.

 

It looks like a log event from windows, which only says kernel event 41 (power problem) when you've had a bluescreen.

Please make sure your pagefile is correctly configured.

 

As I suspected, the pagefile is being managed by the system but it appears that W10 may NOT be allocating it correctly. See the screenshot:

 

What is the virtual memory when you go to the settings of the performance?

 

It's not clear to me what you are asking. What is "settings of the performance"?

 

This is in my VM, that is why the virtual memory is very low.
Attachment 36300

 

Now I understand what you are saying. It shows 768MB (same as the screenshot I sent). In fact, if you click on the "Change" button you get to the same place where my screenshot came from.

Getting back to the issues at hand... 768MB is significantly less than the 12GB of installed memory. Windows normally allocates at least the size of the existing memory when it is managing the pagefile. This is clearly a major bug with W10. I suspect that it is related to installing the Hyper-V functionality. I've gone ahead and manually configured the pagefile to 12288MB (minimum) to see what happens.

Changing the pagefile size requires a reboot which the machine performed without any error. Then I tried to shutdown the machine and it again crashed with the WHEA error. After booting back up again the minidump directory is still empty?! So I guess this is another major bug too.

The bottom line is that it appears that there is potentially a serious functionality problem with Hyper-V on W10 and it seems pretty clear that not much testing was performed @ M$ where my system is pretty vanilla.

 

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?

 

No, these forums are independent.

Yes it is indeed, hope your problem is solved *Smile
If you get any bluescreens within the next few days, please use the tool again and upload the zip file.

 

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.

 

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.