New
#710
John,
You might check this below to see if it may be related.
Windows OS security update block for some AMD based devices - Windows 10 Forums
https://support.microsoft.com/en-us/...-screen-errors
John,
You might check this below to see if it may be related.
Windows OS security update block for some AMD based devices - Windows 10 Forums
https://support.microsoft.com/en-us/...-screen-errors
Thanks Brink.
The first is not applicable to me - I'm on a Core i7 965 EE machine.
Running through the second one now - but I'm probably going to go ahead and just clean install (again) and see if that makes it go away.
Oh, and after having disconnected all peripherals, even then starting in Safe Mode was causing a GSOD - it might just have some bad hardware issues going on....
Even a BIOS Reset (removing the Dummy OC as well as Turbo Mode) hasn't helped. Next, I'm going to get MemTest going to see if I might have flaky (7 year old) RAM
If you're talking about Build 17063, I have it on this machine now and it's running OK. Except for the fact that sound is broken in my default browser Firefox, which is rather inconvenient. To get around that, I copy the link, open another browser, paste the link in and go from there.
If you're talking about the Build that wouldn't install on AMD systems, I didn't try it because I think we were told Microsoft had excluded all AMD machines.
So far, no green screens (bugcheck?). And no blue ones either! :)
Happened to look in Reliability Monitor (also mentioned in Event Viewer, though they're obscured there):
All proper restarts (Start menu) for this build are recorded there as "Windows was not properly shutdown." That is, "The previous system shutdown at X on Y was unexpected."
Anyone else seeing this? Not something that I saw in previous builds certainly.
Bunch of security updates for Office 2013 and MSRT + WD update that wouldn't install until l updated it from WD itself.
I've been surprised to see that no one else is concerned about this:
Tweet
— Twitter API (@user) View on Twitter