BSOD BCCode 116 Intermittent issue

writhziden said:

Memory errors do not always show up in Memtest86+ on a first run. I have seen instances where it had to be run for 21 passes just to get one error. Windows stresses the memory in different/more ways than Memtest86+ does and can sometimes be a better test for Memory modules just by swapping the modules out and testing individual modules and slots by running Windows normally. It may be your problem was the memory module all along and it was not detected initially.

How is the system currently responding with the bad stick removed?

Yeah, I'm hoping it's just the memory stick that's the problem. The thing is, my original problem was an intermittent BSOD related to BCCode 116 when I left my pc running for long periods of time. And I had tested with everything possible back then and never had memory show up as an issue. Assuming it's the memory stick that was the problem, it looks like the more frequent rebooting forced the memory stick to outright fail.
Anyways, the pc is running good so far with one stick. I've got an RMA with Corsair, so I'm going to have to get a spare set of memory sticks as I can't have my machine down and I'm sending both sticks back as I bought them as a pair. Once I've got the extra sticks, I'm going to run the machine for long periods again and see if the 116 BSOD's return. If they don't, then I can safely say it was the memory stick. If not ... back to the drawing board *sigh*

Actually, it may be that the frequent rebooting made the memory problem easier to spot. Sometimes, memory will not show errors if it has been running for a while, but if it is cold, there is a slight voltage issue or current issue that becomes prevalent through the stress testing. That may be why the frequent boots helped to spot it.

Having the system up for a while also increases memory corruption problems, so a bad module could definitely result in a 0x116 crash after a long up time if you do graphics intensive tasks.

Thanks to writhziden and zigzag for your input and help. Looks like it was a memory issue only. Systems been running stable ever since the memory got swapped out.

You're welcome. Glad to see the problem is solved.

Good job, and good luck.