Firs of all, here's a bit of info regarding my situation.
Recently I've bought a Norton Security a couple of days ago and, well, strange things began to happen.
During the previous 2016 year I've experienced only 2 BSODs.
For the last two days - right after I've purchased NIS - I've experienced 7 of them already.
First one, while PC was in Idle state (maybe NIS started a full scan?): ntoskrnl.exe (address isn't listed for some reason).
That was the only BSOD with 7e.
Every next BSOD was 7a. Every one of them happened during in less than 30 minutes after the game starts.
I have my OS installed on C (SSD), Steam installed on D and game installed on H.
What I've tried already: checked for malware; checked HDDs and tried to fix if there were problems with them (chkdsk, SeaTools, CrystalDiskInfo, Victoria), checked GPU memory (VMT) and RAM (mdsched, memtest). Changed the SATA cable for H and connected it to different connector on a motherboard. Changed the game path from H to D.
Oh, and one more thing.
The last time I've launched a game there wasn't a BSOD this time, but as soon as I got to main menu HDDs started to 'click' (like when they are going online\offline) and to prevent any possible damage to the system I've closed the game (maybe there wasn't enough time for BSOD to pop up?).
Once back to the desktop, I've discovered that all HDDs except for SSD (where OS is installed) are gone from My Computer, Device Manager and Control Panel.
Considering all this and the fact that HDD or RAM tests haven't discovered any problems, or the fact that changing installation path of the game to the different HDD, and trying to launch it via new cable and port... could it actually be the Motherboard is the one to blame?
· OS - Windows 7 x64 Retail
· Age of system around ~3-4yrs
· Age of OS installation - have you re-installed the OS? Yes, around 1yr ago maybe, but can't tell for sure.
· CPU i5-4460
· GPU MSI gtx770 2gb
· MotherBoard MSI Z97 Gaming 5
· Power Supply - Cooler Master V650 650w
P.S. Forgot to say - tried 3 times, Sysnative always stuck at 'waiting for system info'. So collected data may miss something.
Edited by rayzi, 25 June 2017 - 01:38 PM.