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

Please post camera pictures of the 8 passes.

 

Just as soon as they are done, tomorrow morning. Second stick, no errors, starting on 3rd stick.

 

No errors

 

Crashed and I had to push reset. I am going back to the bad old days of winders, and format/reinstall. I hate this. DESKTOP-V8L96QB-Fri_07_28_2017__82756_59.zip

 

The Memtest86+ done one RAM module at a time have all passed with 8 or more passes.
Today's bsod mini dump debugged indicates an Intel misbehaving driver.
e1i63x64.sys Intel(R) PRO/1000 PCI
Download and install a new copy of this driver.
Drivers & Software

Code: BugCheck 1E, {ffffffffc0000005, fffff802fea36375, 0, ffffffffffffffff}Probably caused by : NTFS.sys ( NTFS!NtfsFindPrefixHashEntry+1e5 )[/quote] e1i63x64.sys Intel(R) Gigabit Adapter NDIS 6.x driver Drivers & Software

Code: ffff9a80`13e46528 fffff803`00000000Unable to load image e1i63x64.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for e1i63x64.sys*** ERROR: Module load completed but symbols could not be loaded for e1i63x64.sys e1i63x64+0x80000[/quote] Code: e1iexpress Intel(R) PRO/1000 PCI Intel(R) PRO/1000 PCI Kernel Manual Running OK TRUE FALSE 4,096 425,984 0 3/4/2016 15:46:29 C:\WINDOWS\system32\drivers\e1i63x64.sys 4,096[/quote]

 

That is just annoying. Oh well, I am formatting and re-installing Winders right now. I am using my linux laptop to post while I wait. I am doing a completely clean, fresh winders install and going to see what happens. If it keeps crashing, then I replace the motherboard.

 

That was misbehaving driver #7.

 

???? SO maybe a clean install will help? If not a new motherboard.

 

You had had a prior problem with windows driver verifier.
Now you are doing a clean install (deleting partitions, formatting the drive, making an unallocated drive, and installing a new windows 10 version 1703 with the windows 10 iso.
This is a good time to use windows driver verifier.

If you are willing to give it another try we can go over the 3 methods to turn it off.
It will be useful in years to come so its a good time to get accustomed to using it as it likely will come in handy for troubleshooting in the future.

 

Go ahead. It killed my system last time and apparently corrupted my windows installation. It scares me since the last time. So how do I run it safely? I am loading only the Winders drivers for everything. It will be a vanilla installation for a little bit. I am going to install office, itunes, firefox and chrome, that is all.

 

Ok, up and running on the Ryzen desktop now. Let us see if it is stable.

 

Please don't install anything except windows default drivers.
No applications, drivers, files, etc with 2 exceptions:
Install Bluescreenview and Whocrashed
Resplendence Software - WhoCrashed, automatic crash dump analyzer
Blue screen of death (STOP error) information in dump files.
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

BSOD Finding and fixing them - Microsoft Community




Open administrative command prompt and type or copy and paste this command:
shutdown /r /o /f /t 00
It will reboot to the windows recovery or advanced troubleshooting menu.
Navigate through the menu to startup options
It will restart.
Then choose option #6 safe mode with command prompt.
Then type or copy and paste this command:
shutdown /r
It will reboot to the desktop

The above step is the most critical step when using windows driver verifier.
Getting to safe mode with command prompt will allow you to type:
verifier /reset
to turn off Windows driver verifier.
In case safe mode with commmand prompt command verifier /reset does not turn off windows driver verifier navigate in the windows advanced trouble shooting menu to command prompt.
This is where you will see X:\windows \system32\cmd.exe
Enter the command: verifier /bootmode resetonbootfail to turn off windows driver verifier.


Summary on how to turn off windows driver verifier using windows recovery or windows advanced troubleshooting menu:
1) startup options (not startup repair) > select #6 safe mode with command prompt > type: verifier /reset
2) command prompt or Administrator X: \Windows\system32\cmd.exe > type: verifier /bootmode /resetonbootfail
3) if the above two methods fail use restore. Unfortunately restore most often leads to loss of the bsod minidump file and little progress is made in the troubleshooting

To get comfortable using the windows recovery or windows advanced recovery menu open administrative command prompt and type or copy and paste: shutdown /r /o /f /t 00
On reboot you will boot into the windows recovery or advanced troubleshooting menu.


When a bsod occurs with windows driver verifier there will be a stop code. Typically it is driver verifier detected violation. Sometimes it will also display the misbehaving driver: *.sys
If you see the driver on the bsod please record it.

The system settings need to be modified to not automatically restart so that you have ample time to view the bsod window. Follow the settings in this link:
BSOD Finding and fixing them - Microsoft Community

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


To setup and start using Windows driver verifier use the settings in this link:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community


Windows driver verifier is designed to repetitively produce bsod until all misbehaving are uninstalled or until it is turned off.
Each time you return to the desktop you will run both Bluescreenview and Whocrashed.
Then you will uninstall the misbehaving driver.
You can restart windows driver verifier or replace the misbehaving driver.
Either method should lead to the same result removing all misbehaving drivers.
Some drivers or applications cannot work in some computer environments and alternative drivers or applications need to be used.

This link has the method to turn on windows verifier with the custom settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

 

Looks pretty arcane, but ok. I printed it out so I have hard copy.

 

Before you start using windows driver verifier create a brand new restore point.

 

Thanks, I will.