Yeah, I'd just get the memory replaced by the company.
Latest crash is showing this, but it is likely to be from faulty memory. If there is an update, of course install it, but I do not suspect much gain to be made. If it does in fact fix things, then more power to ya, but I wouldn't place a large bet on it:
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000228, Handle value being referenced.
Arg3: ffffcf8041022900, Address of the current process.
Arg4: fffff802408345d5, Address inside the driver that is performing the incorrect reference.
I didn't review the thread, so I don't know if I mentioned or not:
nvhda64v nvhda64v.sys Thu Nov 28 08:38:09 2013 (52974741)
nvlddmkm nvlddmkm.sys Thu Dec 19 12:02:52 2013 (52B326BC)
nvvad64v nvvad64v.sys Fri Dec 27 11:41:28 2013 (52BDADB8)
Razer drivers are iffy under the best of circumstances. Until the machine is stable perfect, Razer hardware should be removed from the system and software uninstalled.
You also can attempt to use Driver Fusion to clean the machine of all NVIDIA video files/settings. Reboot and re-install latest driver from them.
If that .exe shown is to some feature you do not use, attempt to disable it in services (if it is in fact a service there.) Nobody else is having this issue that I have seen, so that at least says something that the issue is not widespread.
A possibility too is a faulty video card or power to it, but that's unlikely, especially because you already found errors in memory.