I am glad that it worked out for you. Still, you should analyse how it came that the modules were deconfigured. There are only two reasons i can think of:
a) someone has done it
In this case there must have been some reason for it and you do yourself a big favour when you find out what that reason was. Otherwise it might come back to bite you.
b) the system has done it
This is entirely possible when some hardware problems related to this memory exist. This should have been noted in the logs you just cleaned. Yes, they are ridiculous to read and not very forthcoming but if there was (or maybe *is*) somehardware problem you sure want to know that. Better to have 16GB memory dactivated than to have a system crashing because some bit-stuck-type error.