Constant BSODs with Ryzen and Windows 10 Creators

Windows driver verifer is a tool designed to find misbehaving drivers.
It will repetitively produce bsod until all misbehaving drivers are uninstalled or it is turned off.
For each bsod you will need to open the windows recovery or advanced troubleshooting menu to turn off windows driver verifier.
When you turn off windows driver verifier you will reboot to the desktop.
On the desktop you will use two software programs designed to analyse bsod.
Download and install Bluescreenview and Whocrashed.
One may add information that is different from the other.
When the misbehaving driver is identified you will uninstall the driver or the application using the control panel or device manager.
Then you will restart windows driver verifier and find the next misbehaving driver/application.
Once there are no longer any bsod you will then reinstall drivers and retest for bsod.
An alternative method is to reinstall drivers as soon as they are uninstalled.
It is personal preference. The end result should be the same. All misbehaving drivers should be uninstalled.
Some software applications may not work in the current computer environment. In these cases the software is uninstalled and possibly another company's software is installed.
Before using windows driver verifier you will want to make sure that you can view the bsod windows. You will turn off automatic restart: Keyboard: win + r keys simultaneously > type or copy and paste: sysdm.cpl > click advanced tab > under startup and recover click settings > under system failure uncheck automatically restart See this link: BSOD Finding and fixing them - Microsoft Community: BSOD Finding and fixing them - Microsoft Community

While using windows driver verifier each bsod windows will display a stop code typically driver verifier detected violation. It may also display the misbehaving driver in the form *.sys. If you see the misbehaving driver displayed please record it.

To turn off windows driver verifier you will either navigate to safe mode with command prompt or command prompt. These are the commands for each:
safe mode with command prompt: verifier /reset
command prompt with X:\windows\system32\cmd.exe: verifier /bootmode resetonbootfail
If neither of the above two methods turn off windows driver verifier then select windows restore. This though does not allow you to save the mini dump file for debugging.
To practice navigating in the windows recovery or advanced troubleshooting menu open administrative command prompt and type or copy and paste this command: shutdown /r /o /f /t 00

When you have time to use windows driver verifier and process the bsod, remove drivers/applications, reinstall drivers, etc then you will start windows driver verifier by typing verifier in the left lower corner search. In the pop up you will customize the tests, and select all non-Microoft drivers as per this link:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

When you have bsod please post a new zip so that we can guide you through the troubleshooting: BSOD Crashes and Debugging - Windows 10 Forums

Verifier is what locked me into an endless BSOD boot loop that I could not get out of last time. I hesitate to use it at all after the disaster that happened. Ill get to work on the other stuff though.

There have been a lot of misbehaving drivers in the computer environment.
Without running windows driver verifer it would seem that the underlying problems would be unaddressed.
At a minimum you need to perform an in place upgrade repair.
This is done with a bootable windows 10 iso:
Download Windows 10
You should be able to save files and applications.
These are the steps:

1) find a flash drive that you can format
2) create a bootable windows 10 iso
3) power on the computer
4) open file explorer
5) click this PC
6) click on the usb drive with the windows 10 iso
7) find the file/folder setup or setup.exe and launch it
8) do not click on install
9) instead look in the lower left and click on repair
10) choose language, time, currency, and keyboard
11) follow the repair install using the text and images in this link:
Repair Install Windows 10 with an In-place Upgrade Windows 10 Installation Upgrade Tutorials

I am afraid to run Verifier after the last disaster, being locked into an endless series of BSOD reboots where I was unable to get into my system at all. Thanks, I will try the repair, and let you know how it goes.

Please update the zip or post a new one when you have a bsod so that they can be debugged.
BSOD - Posting Instructions - Windows 10 Forums

It will not allow me to upload. The previous files are listed, and cannot get deleted.

Lets try this once more:

The bsod debugging is displaying WHEA which is typically related to problem hardware.
It is also indicating problems with Xbox.
The Nvidia driver was replaced with the most up to date driver and may need to be rolled back or replaced again.

The computer that you have is new
There was a boot loop.
A clean install was performed
Memory.dmp was debugged
DDU was used and the Nvidia driver was replaced
GPU stress testing was performed but was terminated at 67 degrees
Malwarebytes was uninstalled
Killer networking driver was uninstalled
Xbox controller driver was updated?
Windows driver verifier was not run
Memtest86+ was run but no image was posted in the thread

Consider the following:
1) perform a clean install of the windows 10 operating system as a "vanilla installation"
Only the operating system will be installed and no applications, no files, and no additional drivers keeping the computer disconnected from the internet unless software for testing hardware needs to be downloaded.
Enable or Disable Driver Updates in Windows Update in Windows 10 Windows 10 Windows Update Activation Tutorials
2) run memtest86+ for 8 passes and post an image into the thread
3) test CPU with Prime95
4) test GPU with Furmark
5) test drive with HD Sentinel, Crystal DIsk, or HD Tune


Run Prime95 - Stress Test Your CPU
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Please use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials


Run memtest86+ version 5.01 for at least 8 runs.
This may take hours so plan to run it overnight.
Memtest86+ - Advanced Memory Diagnostic Tool
Memory problems. - Microsoft Community
When Memtest86+ has completed 8 or more runs make an image of the results to post into the thread.
MemTest86+ - Test RAM Windows 10 BSOD Tutorials



Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
All of these test should be done with the bios reset and no over clocking.
For each of the above tests please record maximum temperatures.
And please make sure that you use the Microsoft snipping tool to post images of each into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials


Run one of the SMART tests on your drives:
CrystalDiskInfo - Software - Crystal Dew World: CrystalDiskMark - Software - Crystal Dew World
Software - Crystal Dew World
HD Tune: http://www.hdtune.com/
Hard Disk Sentinel - HDD health and temperature monitoring: Hard Disk Sentinel - HDD health and temperature monitoring
When the SMART test has completed open the Microsoft snipping tool and make images of the results to post into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

Code:

BugCheck A, {180309b, 2, 1, fffff80318d1fe65}Probably caused by : memory_corruption

Code:

BugCheck 124, {0, ffffda097bf3a8f8, 0, 0}Probably caused by : AuthenticAMD

Code:

WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffda097bf3a8f8, Address of the WHEA_ERROR_RECORD structure.Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Code:

Common Platform Error Record @ ffffda097bf3a8f8-------------------------------------------------------------------------------Record Id     : 01d3002df037c1d9Severity      : Fatal (1)Length        : 928Creator       : MicrosoftNotify Type   : Machine Check ExceptionTimestamp     : 7/19/2017 1:25:45 (UTC)Flags         : 0x00000002 PreviousError===============================================================================Section 0     : Processor Generic-------------------------------------------------------------------------------Descriptor    @ ffffda097bf3a978Section       @ ffffda097bf3aa50Offset        : 344Length        : 192Flags         : 0x00000001 PrimarySeverity      : FatalProc. Type    : x86/x64Instr. Set    : x64Error Type    : Cache errorOperation     : GenericFlags         : 0x00Level         : 0CPU Version   : 0x0000000000800f11Processor ID  : 0x0000000000000000===============================================================================Section 1     : x86/x64 Processor Specific-------------------------------------------------------------------------------Descriptor    @ ffffda097bf3a9c0Section       @ ffffda097bf3ab10Offset        : 536Length        : 128Flags         : 0x00000000Severity      : FatalLocal APIC Id : 0x0000000000000000CPU Id        : 11 0f 80 00 00 08 10 00 - 0b 32 d8 7e ff fb 8b 17                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00Proc. Info 0  @ ffffda097bf3ab10===============================================================================Section 2     : x86/x64 MCA-------------------------------------------------------------------------------Descriptor    @ ffffda097bf3aa08Section       @ ffffda097bf3ab90Offset        : 664Length        : 264Flags         : 0x00000000Severity      : FatalError         : GCACHEL0_ERR_ERR (Proc 0 Bank 5)  Status      : 0xbea0000000000108  Address     : 0x0101f8022b686a67  Misc.       : 0xd00a0fff01000000

Code:

BugCheck 50, {ffffc01ac41e8e80, 0, fffff803614fd14c, 2}Could not read faulting driver nameProbably caused by : memory_corruption

Code:

BugCheck A, {38, 2, 0, fffff8038f329ff8}Probably caused by : memory_corruption

Code:

BugCheck 1E, {ffffffffc000001d, fffff800bf526b0a, fffff8024a214a40, fffff800bfbac578}*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sysProbably caused by : nvlddmkm.sys ( nvlddmkm+6b0a )

nvlddmkm.sys

nVidia Video drivers

http://www.nvidia.com/Download/index.aspx Get from OEM for laptops

xboxgip.sys

Xbox related driver

https://www.microsoft.com/hardware/e...er-for-windows

xinputhid

Attachment 145119

Attachment 145120

The CPU test showed no errors, but my fan was running really hard. I will run Memtest tonight.