memory management bsod, windows 10 fall creators update 1709

I doubt if the memory manufacturer mismatch is a problem in this case since it does not look as if this motherboard runs dual channel memory.

I notice that there is a big gap in the thread, were you running trouble free since the posts in November? Was the black screen problem posted the other day the first time you ran into a problem again? There is nothing in the logs that can help us pinpoint the cause for this so we really need to wait and see if it happens again and hope that we can gather more data on the problem.

While far from ideal there are instruments or tools that can be used to release the ram and remove it and replace it.
See if you have any instruments or whether you have a friend or neighbor or relative or local computer store that may have an instrument that could be used to unseat and re-seat the RAM modules.

The builds for Windows are based on date:
1511: November 2015
1607: July 2016
1703: March 2017
1709: September 2017
The Windows builds have been upgraded every 6 to 8 months.
So the next build could be 1803, 1804, 1805 or 1806

The event viewer critical entry occur:
1) a crash without BSOD
2) a crash with BSOD
3) a power off.
So if Windows hangs, or freezes, and is unresponsive to control + alt + delete, and a power off is performed all it will produce the same message as a BSOD or a crash without BSOD. So more information is needed than that one entry when troubleshooting.

Please run the beta log collector and post a zip into the thead:
log collector v2-beta08.zip

xraiderv1 said:

I am unsure as to when fall creators update 1709 was released exactly, but I have here my event viewer logs, showing EVERY SINGLE occurrence of this problem since 1709 was installed.

the very first instance...was nov 24, 2017. the day AFTER I received the update. therefore, given a lack of occurrences in the two years preceeding...I posit it could not be a ram issue.

I posit it is in fact a memory leak in the os itself.
its been three days since the last one, so some of the events noted are not actual occurrences of the issue, yet they're all flagged with the same exact info..

I have many of the same events show up in my event viewer too. In my case I can trace them back to when the computer was previously shut down with fast start-up turned on. The use of fast start-up seems to create a higher proportion of these critical errors and can be traced to the use of hyberfile.sys which stores the windows kernel and all loaded drivers during the shutdown and then uses this hyberfile.sys file for a faster start-up time by loading them directly from the hyberfile when your system turns back on.

If you have not turned off Fast Startup I would do so and see if it makes a difference.