Hi @Zirilian  please run check disk to get reoccurrence of BSOD (Blue Screen) with the stop code NTFS_FILE_SYSTEM and hopefully this time, the problematic driver(s) will be identified. Remember to disable Driver Verifier as shown in the video. 

If you have a bluescreen with NTFS on it with the troubleshoot code then I say its a OS file system error that either needs a reinstall or just some commandline code that can fix it.

The recent update from Zirilian with system in Safe Mode (only the most essential settings and services) produced blue screen NTFS but seemingly without error code or corrupt driver identification. Running System File Checker (SFC) and then Check Disk (chkdsk) did not report any problems. Windows Recovery Environment (WinRE) in Safe Mode reported "repairing disk errors", but system continues to have boot problems. Event Viewer has previously not logged error code and not sure if Event Viewer logged this blue screen NTFS with error code. The absence of an error code is very odd.

If the error code and corrupted driver(s) can be identified, the Windows OS can be fixed.

If not, then a fresh install would be true.

Hi @Zirilian  as the source of this Windows OS Safe Mode's blue screen NTFS problem continues to be very elusive, a fresh install of Windows OS is the most prudent solution. 

Basically WHEA_UNCORRECTABLE_ERROR only occurs to me on my 15 r1 when I undervolt the cpu which is a 4710HQ to something above -50mV and that’s because the processor literally drops it voltage to 0.876mV and that’s why it crashed.

Also you can restore with your files as it’s not going to make a difference.

Hi @crimsom,

I continued working on this over the weekend, but wasn't able to boot even into safe mode again. I got more BSODs, each with a different stop code. One read "machine check exception," while another had "WHEA on correctable error." Like you say, it seems like this may be a driver issue, but it's hard to ascertain which one.

One of the first things I did when I started having this problem was to reinstall Windows (via the WinRE "Reset this machine" option); however, I had it keep my files. (I do have a backup, but if you can get away with keeping them, why not?) My question is, do you think it would make a substantial difference to reinstall without keeping the files vs keeping them? That initial reinstall didn't solve the problem.

Hi @Zirilian  thank you for sharing the update and investing your time troubleshooting this problem.

From what you have found, I doubt that the root cause of all these Windows OS problems will be revealed. Postulate that your drive is corrupt and/or failing, because even Windows OS Safe Mode has a multitude of problems that are not automatically fixed.

Please use another computer to install your Windows OS onto a new drive. This will give you a flawless drive to use in the M17 R2 and there will be no driver problems. 

Hi @crimsom,

I've seen things about creating boot media and indeed have created a USB drive using Microsoft's online utility. But I did this on my laptop at one point when I had gotten it to boot up. Will that download still be viable, or does the bootable media need to be created from another computer?

More to the point, how can I get the laptop to use the USB to install Windows? As far as I can tell, this involves changing the BIOS over to Legacy Boot Mode, which sounds like it might not actually be a very good idea in the long run. (Currently the laptop doesn't appear to "see" the USB key for purposes of booting when I plug the USB key in.)

Hi @crimsom,

Thanks very much for the clarification. However, my question isn't about where to get the files for the Windows reinstall, but rather how to make the laptop see the USB on which they're saved. My only option at the moment seems to be to reset/reinstall from WinRE's "Reset this Computer" option, which I believe uses files already available on the problematic machine. (Unless I'm wrong about this?) How do I cause the laptop to see/use the bootable USB?

Hi @Zirilian   thank you for sharing observations on how to proceed with the current unstable status of the m17 R2 and its Windows OS. We have previously advocated a clean, fresh Windows OS installed on a new drive to get the m17 R2 up and running without any pre-existing problems. This should restore your m17 R2 hardware status to "as new" without any problems.

Having created a USB with just the Windows OS activation files, there should be no installation of corrupt files onto the new drive. With the m17 R2 hardware capabilities diminishing, the use of a different computer is the best way forward. There are other options, such as getting a new drive with Windows OS pre-installed, etc.

A small number of drives fail early, but most last their declared lifetime of read/write. Disaster recovery may include a "gold" drive with a copy of the drive that came with the system. A "sliver" drive with a copy of the current Windows OS and all its updates. The home files on the second drive, backed-up onto a copy drive. 

Hi @Zirilian   thank you for sharing an update.

From the investigation you have already conducted, the Windows OS Safe Mode files are corrupted. WinRE will use the Safe Mode files, so this will not fix these Windows OS driver(s) problems to restore all the hardware functions. The m17 R2 + Windows OS system is unrecoverable. Trying to use this unstable system should be abandoned.

Get a fully operational new replacement drive with your Windows OS and install this, to restore m17 R2 hardware function. 

Hi @crimsom,

>Get a fully operational new replacement drive with your Windows OS and install this, to restore m17 R2 hardware function.

Thanks, I understand this advice. I've downloaded the OS to a USB key using Microsoft's online tool for creating bootable Windows recovery media. The issue is that I don't know how to get the laptop to boot from the USB key or otherwise use it to reinstall Windows. The laptop doesn't seem to know it's there or otherwise be willing to use it to boot.