Windows 10: memory management bsod, windows 10 fall creators update 1709

On the image that was posted under virtual memory please click change. A new window should open. That will be the virtual memory window. Please post an image of the virtual memory window into the thread.

There were no BSOD.
There were unexpected restarts or crashes.
The computer has mismatched RAM modules.
Mismatched RAM modules can cause unexpected crashes.
Mismatched RAM can pass RAM testing and still behave in this unexpected fashion.
RAM testing can be used to determine whether one of the modules is malfunctioning.
If there is a malfunctioning module it can be removed.
If neither module is malfunctioning then the 4 GB module should be removed to check system stability /instability with just the 8 GB module..

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.
a) 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 12 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.
b) 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 Windows 10 Tutorials

 

my hands are too big and I cannot physically reach the latches to eject the ram..

so what you're saying is its a mismatch issue on the ram sticks? shouldnt this have been a problem in that case well before the 1709 update?

cause post 1709 is when this first started to happen.

 

The challenge with mismatched RAM is that it is an unknown or a potential confounding factor.
There is no stress test that reliably confirms the problem or has a high accuracy.
It is always recommended to use RAM with identical pairs (same SKU).
If there are misbehaving hardware or software drivers identified they are replaced.
If there is malfunctioning hardware identified it can be swapped for testing and then replaced if it is faulty.
For the mismatched RAM it is a confounding factor. So if it can be eliminated it becomes easier to evaluate the rest of the computer.

 

and as I cannot get at the ram sticks...

 

Then proceed with the RAM testing with Memtest86+ version 5.01 with 8 or more passes.
At the completion of the test please use a camera or smart phone camera to take a picture and post an image into the thread.

 

how long will this test take?

 

Memtest86+ version 5.01 takes 1 -2 hours / GB RAM
The testing must be continuous for 8 or more passes.
There is 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.
It sometimes takes passes into the 20s to find malfunctioning RAM.
Just 1 error is a fail and you can abort testing.
Counting the number of errors is unnecessary.
Where there are multiple RAM modules and there is an error the RAM modules are removed from the computer and 1 RAM module is tested for 8 or more passes in the same DIMM.
This should differentiate the good from the bad RAM modules.
When memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
There are multiple software products used to test RAM. The software product that we use is Memtest86+ version 5.01.
Please use this link to make sure that you use the proper software:
Memtest86+ - Advanced Memory Diagnostic Tool
MemTest86+ - Test RAM Windows 10 Tutorials
It is best to run a significant portion of the testing overnight.

 

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.

 

I've been trying to work with my pc's manufacturer, and they say without screenshots or something that can show the problem..I'm more or less up a creek.

I intend to set aside time this sunday to run the memory test program..when I will be doing absolutely nothing else.

I cant actually get at the ram module to remove it, big bear paw hands and too small a space to work in..so this presents a 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.

 

and it just smacked me in the face with another incident.....I'm going to set this thing to run overnight....off a bootable flash drive.

 

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..

 

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.

 

considering all the warning I get that a problem has occurred is a black screen and the darned thing acting like its been freshly booted right after? how exactly am I supposed to get further information?

 

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