Windows 10: Constant BSODs with Ryzen and Windows 10 Creators [SOLVED]

Ok will do, it is about to finish pass two....

 

I tried to screenshot it, but was unable to do so. 8 passes and no errors found. I tried to unlock dc1-controller.sys, and Windows will not allow me to unlock it. I tried everything I possibly could do to unlock it so it could be deleted. The system did not crash during Memtest86+, which was good. It took forever to run though.

 

Played some Civilization V, YouTube, surfed the net, and so far, so good. I am starting to get worried that it is going too well....

 

Nice.
Do you have all of your files backed up?
Have you made an image of your drive using Macrium?
Have you created a restore point?

 

Yes
No
Yes
I'll keep this open for a few days, but Thank you very much for the help, it is much appreciated.

 

This is to make an image using Macrium:
Macrium Software | Macrium Reflect Free

Download and install the latest version of the HP UEFI diagnostics:
HP PC Hardware Diagnostics | HP® Official Site

Power on the computer clicking repetitively the F2 or the F10 key.
Navigate to the UEFI diagnostics.
Run extensive or loop until failure testing. Plan to run this overnight as it may take 4 to 6 hours depending on the RAM and the size of the disk.
If there is a failure it will stop automatically and display an error code.
If you use loop until failure you will click the escape key.
View the UEFI log to confirm the pass results.
Reboot.
Report the results into the thread.

 

Ok, done. Correction crashed BSOD right before it finished. Here is the dump file. [Insert much foul language here]
Cant get it to boot to the UEFI. Been trying for the last twenty minutes. No joy.

 

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.

 

I think that I have a motherboard issue. Crashes seem to happen when something is plugged into the front USB ports on my Corsair C70 case. It seems stable otherwise.... Several more BSODs all Windows Kernel issues per what crashed software. However as long as nothing is plugged into the front USB is seems more stable. I am probably going to ditch the Gigabyte Gaming K7 X370 board for an ASUS Crosshair Hero VI board as soon as I can afford it.

Also I noticed that plugging in USB drives to the front ports, do not autoplay, and my 128 gb drive which had 97 gb free, was not able to load anything, since it kept telling me that the drive was full. Also my 64 gb San Disk USB drive was not recognized at all on the front ports.

 

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: