If you have a bad modules you are going to know it.
Working with a bad module, defective RAM means wasting time and losing data.
A defective module causes corruption in RAM, not always freezes and BSODs.
I had checked systems that seemed working perfectly but there was some weird file corruption going on. The machines were up and running in, it happened in more than one office environment different places, the employees were using the machines like everything was good because they never got a freeze nor a BSOD.
But they started getting corrupted files, only big files usually got corrupted.
Well, I did a MemTest86 on those machines everytime and I always found defective RAM modules. Windows wasn't running in the defective chips area, so it kept running although then checking further revealed that OS files and system registry started getting corrupted too but no BSOD happened.
This behaviour happened multiple times on different machines in more than one office.
It's pretty common to find PCs with bad RAM modules and that happens because the ones assembling the system first and then the ones that should provide assistance inside an office to employees didn't bother using MemTest86 (or a similar reliable memory tester) to ensure that RAM modules were defective free and fully stable.
And it happens on PCs for SOHO too, not just large office environments.
I keep repeating to anyone to always check RAM on whatever system you assemble or you need to provide assistance for.
Checking RAM avoids further issues, data corruption and lost installations.