Windows 10: Windows 10 Creators Update Crashing Frequently

Please remove 1 of the RAM modules.
Almost always RAM modules should be in matched pairs as unmatched sticks are a frequent cause of BSOD.

 

I have been using these RAM modules together since I acquired this computer back in 2016. During this time I have had no issues with recurring crashes. I have run the computer crash-free for several months at a time, and what few crashes I had were sporadic and did not have the same characteristics as this issue. While not impossible, I question the likelihood that this is the source of my issues. Can you provide any diagnostic information or other concrete evidence that this is the reason for my crashing issues? While I understand that this point of advice is generally correct, I hope you understand that I am reluctant to spend $60 minimum on a change that is not guaranteed to solve any of my problems (I unfortunately do not have a lot of extra money these days). If you can demonstrate with greater certainty that this is the source of my problems and provide me confidence that it will resolve my issue, then I will be more willing to try this.

 

The removal of 1 RAM module was for testing purposes. No conclusions have yet been made.

There are several approaches that can be made:
1) remove one RAM module an observe the computer environment for approximately 1 week.
a) if there are no longer any BSOD the mismatched RAM was likely the source
b) if BSOD continue switch RAM modules and observe the computer environment for approximately 1 week.
c) test both RAM modules together with Memtest86+ version 5.01 for 8 or more passes.

Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 16 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials

Download and install CPU-Z
CPU-Z | Softwares | CPUID
open it and make screenshots of the following tabs
CPU
Mainboard
Memory
SPD*
Graphics


*SPD shows the details of each stick, you can show the details by choosing different slots in the left upper corner.
Please make screenshots of each stick.


Please post each screenshot in your next reply/replies.

 

I will run the tests and return with information when available.

 

Hello Irnova *Smile

I've just picked up this thread again. The event logs show that the BIOS update that you did has completely removed the hardware errors you were getting before so that is great confirmation and an improvement but clearly it has not cured these crashes and black screens. The two recent crashes are not causing BSODs so they are going to be more difficult to diagnose since we do not have any crash data to debug.

I can see that @zbook has been working with you and has confirmed that you are setup to capture BSOD crash data. This is good but doesn't help when you are not getting a BSOD in the first place.

I will wait to see what results you get from the memtest86+ diagnosis before commenting further but I am not convinced it is a memory problem.

 

I ended up running MemTest86+ for 42 hours, due to my schedule and the amount of time it took to complete the passes (8 passes completed sometime between 22 and 24 hours). In total, 13 passes completed with no errors.





Currently I am running my computer actively again with all RAM still installed. If a crash occurs I will run the DM log and see if there is any information that can help. Any other advice is welcome in the meantime.

 

Any further news on this?

 

Simple answer: no. I have run crash-free since the last update. I haven't done any other troubleshooting steps since then, so...it is possible that those two episodes were an aberration. I simply don't know, but I will mark this as solved, and if I develop another recurrent issue, I will return. Hopefully this is the end of it.