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

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: HD Tune website
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[/quote] Code: BugCheck 124, {0, ffffda097bf3a8f8, 0, 0}Probably caused by : AuthenticAMD[/quote] 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.[/quote]

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[/quote] Code: BugCheck 50, {ffffc01ac41e8e80, 0, fffff803614fd14c, 2}Could not read faulting driver nameProbably caused by : memory_corruption[/quote] Code: BugCheck A, {38, 2, 0, fffff8038f329ff8}Probably caused by : memory_corruption[/quote] 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 )[/quote] nvlddmkm.sys nVidia Video drivers Download Drivers | NVIDIA
Get from OEM for laptops
xboxgip.sys Xbox related driver https://www.microsoft.com/hardware/e...er-for-windows


xinputhid

 

c drive image.docx





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

 

On the web sites that test drives they perform analysis of the whole drive displaying images of the disk and have values and thresholds recorded. The part of the crystal disk that is needed is this section: Software - Crystal Dew World
When it is completed please post images of all of the data and drive. (When above is done please make screenshots of the following the health, the error scan, transfer rate, access time, burst rate,cpu usage.) As an alternative you can use HD tune or HD Sentinel.
For the graphics testing what was the highest temperature and what was the duration of time for the testing? Were there any artifacts?

 

No artifacts, 70C. c drive image (1).docx

 

Run HDTune to
check the health,
scan for errors, no quick scan but full scan
run a benchmark.

HD Tune website


It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark incl. following
transfer rate,
access time,
burst rate,
cpu usage.

 

This morning while I was downstairs. Running the check you requested right now.

 

For the BSOD there have been 6 different misbehaving drivers.
mbamchameleon.sys
farflt.sys
RfeCo10X64.sys
dc1-controller.sys
nvlddmkm.sys
xboxgip.sys
Two of the drivers have been recurrent.
Please remove the XBOX and all of its applications and software from your computer as it is producing one of the recurrent BSOD.
Please post the SMART studies of the drives including the data and error scans.
Please consider a clean install of the operating system with a "vanilla reinstallation" and completing the testing of the hardware for the WHEA bsod.



Code: BugCheck D1, {fffff80d91646200, 2, 0, fffff80da16197ab} Probably caused by : dc1-controller.sys ( dc1_controller!DccCompleteReceiveAgainstRequest+49 ) Followup: MachineOwner[/quote] dc1-controller.sys xbox related driver https://www.microsoft.com/hardware/e...er-for-windows

Code: fffff800`3ae38348 fffff80d`a49a6afcUnable to load image nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x1d6afc[/quote] nvlddmkm.sys nVidia Video drivers Download Drivers | NVIDIA
Get from OEM for laptops

 

Ten minutes into my using the system this morning, it died. New BSOD I have not seen:
I am going to format and re-install Windows AGAIN! this friday. After that I if it does not behave within a month, I am going to Mint Linux. No Xbox controller is attached. No front USB is attached. I am going to get a new motherboard this friday as well most likely an ASUS Crosshair Hero VI.

Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 7/25/2017 05:44:49 your computer crashed
crash dump file: C:\WINDOWS\Minidump\072517-8859-01.dmp
This was probably caused by the following module: wcifs.sys (wcifs+0x4205)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80E7DDA4205, 0xFFFFD301FF777460, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\wcifs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Container Isolation FS Filter Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

DESKTOP-V8L96QB-Tue_07_25_2017__54856_92.zip









SSD Boot Drive:

 

When the WHEA dump occurred was there any hardware attached to the desktop that is no longer attached?
Are the USB problems related to USB2 or USB3 or both?


Code: BugCheck 3B, {c0000005, fffff80e7dda4205, ffffd301ff777460, 0}Probably caused by : memory_corruption[/quote]

 

No, nothing at all. Ran Memtest for 14 hours yesterday, and after the three 1/4 passes it found no errors. I started it at 0730 and ended at 2130 and it only did 3+ passes.

[/quote]

 

please post a camera image into the thead

 

OK done

 

To rule in or rule out memory problems it is not a time based test but a number of passes test.
Insufficient testing produces false negatives.
A false negative leads to believing that a test was done that demonstrated no problems with the memory when in fact there could be problems because the testing was inadequate.
To reduce the false negative results a minimum of 8 passes are required.
See these links for more information:

http://www.memtest.org/https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/memory-problems/21c3f63f-f570-4522-b2ef-ecc7b7ff6461

When Memtest86+ has completed 8 or more passes make an image of the results to post into the thread.

MemTest86+ - Test RAM

Memtest86+ needs to be run for at least 8 complete passes for conclusive results.

Remove all but one RAM stick if the testing is long and test one RAM stick at a time in the same DIMM.
Set it running before you go to bed and leave it overnight.
We're looking for zero errors here.
Even a single error will indicate RAM failure.
Make a photo of the result and post it.

 

The test with three passes took over 14 hours. I'll work at it.

 

Stick one, 8 passes, no errors, working on #2.