As I suspected, I can't really do much with the event logs because they're in another language.
Unfortunately, I can't help any further on this. Without a kernel dump to work with (cuz they're corrupted), without Driver Verifier being able to produce a crashdump, and without being able to read the event logs, I can't do much of anything here. Only thing I can suspect is a corrupt Windows installation and/or an actual malware infection, so try and take care of that.
All I can recommend at this time is to just do a heavy cleanup of your system. Remove any and all unnecessary applications and drivers for stuff you don't use, as well as update any and all drivers for stuff you do use. Also you may wanna try changing to another antivirus like Microsoft Security Essentials or Avast since it may even be a bug in the AV you're using.
Or you can backup your current drive and then reinstall Windows and see how stable that goes. If problems still arise, must likely you have some sort of hardware failure we aren't seeing.
Actually, speaking of hardware, we may wanna run a couple more hardware tests just to see. If you haven't already, run
Memtest86+ for at least 7 passes on your memory. Then, follow up with
Prime95 on Torture Test on Large FFTs setting overnight. Make sure to test your CPU temperature first by checking it with
Hwinfo with
Sensors only option. If temperature is stable below 65C, then it should be ok to run overnight. Regardless of how that test runs, you should run it another night but on Blend settings instead. This'll make sure we test both RAM-to-CPU crosstalk (Blend) as well as internal CPU caches (Large FFTs).
Of course, you can also be checking up at our security subforum to make sure your system is clean. If there's an infection causing the problem, it won't so easily be discovered, especially without us being able to access any strong data.