SSD Went Down after KB4512506 (Monthly Rollup) So Did New One

Hello there

I have been trawling the internet, and reading many posts on here, but can't seem to find an answer to the problems I have been facing.

Brief History

Windows 7 64 Pro was running perfectly until I installed the Microsoft August 13 KB4512506. After restart I got the Windows is Loading files page. Tried the recovery on the installation CD, which tried but failed. When I tried it again I received a message telling me it could not run because it was not compatible with the installed OS?

So I tried the cmd of fixmbr etc. One weird thing was it found one instance of Win 7 and asked if I wanted to add it, I clicked Y and it told me the resource could not be found.

So I bit the bullet, ordered a new SSD and cradle. Installed the new SSD with Win 7 64 pro, and used the cradle to recover all files from the previous SDD (all files were there)

So all was good, new SSD running nicely. I needed to partition the drive so used a program I have used numerous times before, it went into the cycle, and then I received the same error as before on the old SSD.

So I partitioned the drive prior to installation again and all was fine.

Yesterday I was installing programs again and some I do not want connecting to the internet so I use the ESET firewall to block them. I noticed that I kept receiving a message telling me that it could not create the rule. Then the system rebooted and once again I have the windows loading files page.

I am not running on an older HD which had a copy of Windows on which I imaged onto an SSD a few years ago. So far this is working fine, but I am not going to do anything on it other than use it for internet.

I tried everything I oculd, diskpart, fixmbr, a linux boot disc. Looking int the BIOS I do see Windows Boot which is selected, but ti doesn't work.

So I now wonder if the problem is hardware related. But then wonder if it isn't as the system is running now on the old HD and I can read all drives using the cradle.

The only thing I did not do after the system crashed after I tried to partition it was to completely wipe the SSD before install, so I assume it would have still had the old MBR on the hidden partition. I wondered if that confused it. But as this has happened on two SSD's over the last 7 days I must look elsewhere.

I did wonder if the CMOS battery might be the culprit, but as the crash happens when the machine is working I'm not sure. Also when I enter the BIOS all times and dates are correct and all settings are still as they were.

Maybe the MB is on the way out, bad track causing a moment interruption of signal, or bad memory stick.

Just wondered if anyone had similar at any point as it is confusing when you have all the symptoms and try all the cures that work..............but don't. It's almost as though the MBR is there but nothing else knows it is and no amount of CMDs make it better.

Many thanks indeed

When you clone a hd to SSD other settings are needed and that may be the start of the problems what are the settings in the BIOS for the drive is it set to legacy?

Thanks for the reply. This happened on a clean install of Win 7 on a new SSD, but also happened on a previous install of Windows on an older SSD. The BIOS is not set to legacy, but did try that and made no difference. As this has now happened twice in the space of 7 days, once to existing install on existing SSD and once to clean install on new SSD I am confused as to what is causing it