Windows 10 Blue Screen after update/rollback

My Windows 10 installation has started to blue screen frequently.  It started after upgrading to build 1803.  I reverted back to 1708 but it keeps blue screeining.  Attached is a recent minidmp file.
051918-7968-01.dmp
c_mayAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
Blue Screen View (Nirsoft.net) implicates Memory Management.

1. Get memtest86.exe and run this to see if you have memory hardware issues.

2. If no, run a Windows 10 Repair Install and keep everything.

https://www.microsoft.com/en-us/software-download/windows10

Windows 10 is running, so click on the Download button (not Upgrade Button, select Open (Run) but NOT Save. Allow the program to run. Allow drivers to update. Then select Keep Everything.
0
nobusCommented:
i use memtest86+
mostly from the UBCD,
Hardware diagnostic CD    UBCD
---------------------------------------------------
go to the download page, scroll down to the mirror section, and  click on a mirror to start the download
Download the UBCD and make the cd   <<==on a WORKING PC, and boot the problem PC from it
Here 2 links, one to the general site, and a direct link to the download

since the downloaded file is an ISO file, eg ubcd527.iso - so you need to use an ISO burning tool
if you don't have that software, install cdburnerXP : http://cdburnerxp.se/

If you want also the Ram tested - run memtest86+ at least 1 full pass,  - you should have NO errors!
direct download :  http://www.memtest.org/
 
For disk Diagnostics run the disk diag for your disk brand (eg seagate diag for seagate drive)  from the HDD section -  long or advanced diag !  (runs at least for30 minutes)

http://www.ultimatebootcd.com/      

**  you can make a bootable cd - or bootable usb stick
*** note *** for SSD drives  use the tool from the manufacturer, like intel 's toolbox :
https://downloadcenter.intel.com/download/18455/Intel-Solid-State-Drive-Toolbox

for completeness -here's how i handle disk problems : http://www.experts-exchange.com/Storage/Hard_Drives/A_3000-The-bad-hard-disk-problem.html

==>>****in order to be able to  boot from CD or usb - you may have to disable secure boot in the bios
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
c_mayAuthor Commented:
Thanks for the replies.  I tried recovering from a previous Acronis backup but it failed, leaving my OS unbootable, so I ended up reinstalling Windows fresh yesterday.  

The machine is still crashing overnight so I went on with your memory advice.

I have run memtest86 from a bootable usb I made.  I think there were 10 tests, 1-3 no errors, but hundreds or thousands of errors for the rest of the tests.  

So does this mean it is for sure a stick of bad ram?  It could be the motherboard also I know, but any other possibilities?

And does memtest86 have the ability to show which ram stick is bad? (or if its the mobo?) Or is it just a process of elimination by taking out one stick at a time?

Thanks for the help.
0
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

c_mayAuthor Commented:
I couldn't find a way to determine from software which stick was bad, so I started pulling them out one by one (had four sticks).  Of course I found it to be the very last stick I tried, but I found the problem!!!  Feeling lucky it wasn't a bad CPU or motherboard.  I did try to reseat the bad module in case it just wasn't set right, but it still had errors.

Thanks so much for the help.
0
c_mayAuthor Commented:
I couldn't find a way to determine from software which stick was bad, so I started pulling them out one by one (had four sticks).  Of course I found it to be the very last stick I tried, but I found the problem!!!  Feeling lucky it wasn't a bad CPU or motherboard.  I did try to reseat the bad module in case it just wasn't set right, but it still had errors.

Thanks so much for the help.
0
JohnBusiness Consultant (Owner)Commented:
You are very welcome and I was happy to help
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.