Frequent BSOD, most often upon login, WHEA_UNCORRECTABLE_ERROR,

axe0 said:

Very risky , but good to hear :)

Makes me think that the built in reset feature doesn't truly reset like a fresh format/install would. I had noticed some drivers from my previous install somehow carried over magically without an internet connection when using this feature. However when installing from USB I had to manually download my drivers... It's also a coincidence that the same BSOD occurred after doing a reset, but stopped after a format/reinstall. Maybe someone can shed some light on this?

axe0 said:

What drivers are you refering to?

Specifically graphics and audio. I know without an internet connection Windows 10 only has generic drivers. With a connection it will download the base Nvidia driver and Realtek driver + Control Panel . However in this instance when I reset I did not have an internet connection.

axe0 said:

Is your installation an upgrade or a clean install?
Please disable the GPU in the CPU and try running from the AMD graphics card.

It was an upgrade from Windows 8.1. Unfortunately, the GPU in the CPU is the AMD graphics card :\. It looks like the fresh install might be my only solution.

Aaron93 said:

MufB, try reinstalling Windows to confirm. Sounds like we may have a similar situation on hand, however the BSOD we both received usually points to hardware which is weird. The first thing I did was a full hardware test and everything came back fine. I then reinstalled Windows 10 using the new reset method built onto 10 -- however this still yielded the same BSOD message. What finally made it disappear was a fresh USB created with Windows 10. I then installed my drivers and ran Windows Update.

I'm going to go check the recovery settings now to make the bootable USB. Did you have any activation problems?

axe0 said:

In that case, it is certainly an option to do a clean install. With the upgrade there are bugs to face.

Sorry to sound ignorant, but where exactly do I go to create a bootable USB for a clean install?

A clean reinstall fixed everything. I was able to run Furmark for 30 minutes and no BSOD. I'll update the original post now. Thanks for all the help, axe0!

mufb said:

A clean reinstall fixed everything. I was able to run Furmark for 30 minutes and no BSOD. I'll update the original post now. Thanks for all the help, axe0!

I'm happy to hear that what I performed on my machine fixed your issue also. This is definitely something weird and I'm glad it's not my hardware.