Recent Bsods happening at random

It freezes before it even displays a blue screen.

will provide the memory.dmp after it has uploaded its 460 mb or so, will take some time I guess:P

Here it is: http://goo.gl/bisZE

Yeah, this crashdump is completely corrupt and incomplete. I have to assume something seriously wrong is going on with your hard drive. Actually, I looked at the screenshot you took of CrystalDiskInfo, and while it says it's good, the raw value for UltraDMA CRC Error Count shows up something that appears to tell otherwise. Usually if errors crop up of this type, it means there's an issue with the data cable to your drive. Reattach the SATA cable from both mobo & drive ends or use another cable if available. Do the same for power cable for the drive as well just in case.

I'm not sure if you have already, but run Short DST, SMART and Short Generic tests on Seatools if checking the cabling does not fix the problem.

I honestly cannot think of anything else. Without raw data to work with, I can't really see where to go here. I did notice you haven't provided a full report as mentioned here, only the crashdumps. Please do so. Perhaps something in the syslog/applog may hint to something. Not sure how much help it'll be in a different language, though.

I will do this, but about the full report, I did it in my very first post right?

I'm afraid you haven't, Robert. All you've been providing is CBS logs, MSInfo, and crashdumps. We'll want the full generated report.

Also, Noel has a good point. If the CBS shows the problems keep persisting on these files, than an infection is the most obvious cause. You'll want to direct attention to it at the security subforum here in its own separate thread. Once you're sure the system is clean, but the instability still persists, then you can return here at this thread.

Reattached the cables to my hard drive. I passed all the tests u told me to do of seatools aswell and attached the files from the SF diagnostic tool. I will go to the subforum of security if u can't do much with the files of the SF diagnostic Tool then (and ofcourse if the problem is fixed with reattaching the hard drive cables, but small chance I think).

Tell me if there is anything more that needs to be attached, I think i have got everything of the tool now but I am not sure.

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.