BSOD after startup and loading my programs (Did a system restore)

New BSOD today. All programs slowly started closing. WoW disconnects, then WoW closes, then Bnet client closes, and then I BSOD.


I Have also performed a Memtest on my RAM for around 8 hours over night and passed all tests. I
have done a disk check also and have passed both on the SSD and the HDD.

I have Malwarebytes ready to be installed if need-be, however, I feel a malware is unlikely.
Did a scan and found nothing

I also want to thank you for your time axe0. You're help throughout all this as made me feel more as ease in a sense when it comes to these BSOD. Whomever also replies, you're awesome.


Zip attached.

A combo of 0x7A & 0xF4 is indicative to hard drive problems.

I would recommend the following
1. Remove MSI software, software from the motherboard manufacturer is in most cases known for causing issues,
2. Check your SSD for firmware updates,
3. Run below tests,
4. Reseat the sata cables, if possible a temporary replacement of the sata cables.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Make a photo of the result and post it.

Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the error scan,
• the health,
• the benchmark incl. following
  
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Do I read it correctly that you ran Fix All Fast with SeaTools? Did you run the long test in DOS?
For the rest it looks good :)

Should I try moving the SSD to a new Sata port?

You could try it :)

I'll be waiting for the chkdsk log :)

A motherboard can't be easily blamed, you need to do a lot of troubleshooting first before you can think of it as a possibility.