New
#670
After a restart of my computer earlier I got a message about my Insider settings. When I checked I found out that I had been changed to the slow ring. When I use the reg red hack I get changed back to the Skippy ring. When I restart my desktop I get changed back to the slow ring. I'm going to make sure I'm in the fast ring and see what happens when I do a restart.
Umm, Meltdown was released to the public after 17063 was released. But it has been known about for much, much longer. The researchers responsible for discovering Meltdown reported it to Intel back in June 2017. And everyone was working on patches as far back as November (as reported) but IMO probably as far back as late August
Sorry for the confusion lol - but I am curious if the original bugcheck caused in AMD devices was because this was version 1 of the proposed patches to the NT kernel by Microsoft, which were being tested by us Insiders.
I did a restart while set to fast ring and it stayed in the fast ring. Then I did the reg hack again and did a shut down startup and the setting stayed on Skippy. I'll keep checking to see if it resets back to slow.
No harm done on your part. It was the trouble of my own making. I just have to look more closely. One of those moments where I sat back in my chair and laughed at myself.
So far as the bugcheck and the AMD block with 035, I was under the impression it was a UUP delivery flaw, but then again one couldn't install even with an ISO. I'm quite sure members have tried that. So far as I know my/our IP 17063 doesn't/don't have the data of the KB patch that FCU was given as seen below. Not sure why some say it does.
Attachment 171486