Crucial M4 128GB SSD - master boot record frequently becoming corrupt

schmutz06

schmutz06

schmutz06

Associate
Joined
19 Jun 2011
Posts
52
I built my new system last week:

CPU: i7 2600K
RAM: Kingston HyperX Blu 1333mhz (16GB)
GPU: Gigabyte GTX 560 ti (SLI)
Mobo: Asrock z68 extreme 4
SSD: Crucial M4 128GB

OS: Windows 7 Ultimate x64

experiencing the following problem:

Computer restarts -> launches into startup repair -> startup repair fails -> cannot boot into operating system (stuck in an infinite startup repair loop)

Solution:

Enter command prompt in the recovery environment and use:

bootrec /fixmbr

= enables me to boot into my operating system again

My problem:

The "mbr" data is frequently becoming corrupt and stopping me from being able to boot into my OS until I rebuild it. In addition, all events that take place during the power cycle beforehand are lost next time I am able to boot into the OS. This means any programs installed/adjustments to firefox favourites or profile settings in applications are seemingly being reset to an older state.

Does this sound like an SSD issue? From extensive research I am yet to find any solid evidence on what can cause this problem. It has been suggested that the motherboard/RAM/PSU can also cause data corruption. I would like to narrow it down to either the motherboard or the SSD as I have already tested the RAM and PSU in a stable system. I can isolate between the SSD and mobo by installing Windows to another HDD and seeing if the problem still exists.

Sadly, I do not know how to replicate the problem. It has occured five times while I was not at the computer/computer was idle. This is frustrating because I have been using the computer for 90% of the time it has been on, but I am yet to actually see it restart-->go into startup repair. For this reason I am reluctant to test between the motherboard and SSD as it could take a long time to replicate the problem.

1) Do you think I have enough evidence to suggest the SSD is the culprit?

2) Has anyone else experienced similar issues before with regards to data loss/mbr corruption?

3) Anything else I should look into? Viruses/bad drivers/BIOS?

4) For reference, I have tried formatting/reinstalling windows to no avail and the disk I am using to install Windows 7 works fine on other machines
 
Last edited:
It could be simple as a corrupted Windows installation. Personally, I would just reinstall Windows and see if the problem continues.

The Crucial M4's are very reliable drives. Also, you say it was only built last week, so unless it was damaged during shipping or installation, or you're just unlucky, it is unlikely to be the SSD. If you could get another HDD and test it on the same system, then you would be able to narrow your search down.

It could be a driver issue, although I have never come across anything like this before, check to make sure all of your drivers are up to date and see if the problem continues.

I doubt it would be a virus causing this problem, there aren't actually very many viruses out there that actually damage the computer in anyway and make it unusable. Although you should do a thorough virus scan to make sure.
 
oh I tried a reformat to no avail, for reference I have added this to the original post. I will try an installation on a different Hard drive as a last resort (this process will take a very long time since I cannot actively replicate the crash). I am quite convinced that another HDD will not have the same problem though. Of course if it were to have the same problem I would be inclined to believe my motherboard is the culprit for the corrupt mbr.
 
Jordan97 said:
You say the RAM has been tested, but how?

I would recommend running Memtest for a bit.
Click to expand...

Actually I would like to do this to be sure. I have just attempted to boot memtest from a USB but it didn't work. I recall being able to launch memtest from another, easier means though... something in windows 7 and you will be asked to restart/run memtest? could memtest be launched from a windows 7 recovery disk?

Also, to be 100% sure I have took my Crucial M4 out of the equation and made a new OS installation on a spare 1TB HDD. Due to the nature of my symptoms and the way in which flash memory operates I am 99% certain I got a bad SSD. I can give it the weekend and if I do not get any "startup repair" infinite loops via mbr corruption then I will get the SSD replaced. The weekend is definately enough time for my "corrupt mbr" problem to reoccur since it has happened 5 times in the past 6 days (each time has been when I am not at the computer, computer in idle state).
 
Last edited:
I've had the same symptoms with having an old win XP install hanging over a previous drive. Even after a complete format of that drive. I had to disconnect the drive, repair the MBR which got moved to the SSD, and reconnect the HD, wipe it again.
 
olivier renault said:
I've had the same symptoms with having an old win XP install hanging over a previous drive. Even after a complete format of that drive. I had to disconnect the drive, repair the MBR which got moved to the SSD, and reconnect the HD, wipe it again.
Click to expand...

The SSD was brand new and was operating as part of a new build (I later added my other Hard drives). No existing installs to worry about on the SSD it was a perfect/clean OS installation (Windows 7 ultimate 64bit). By the same symptoms, do you mean you were frequently losing MBR data on an SSD drive? And was the SSD drive also seemingly "forgetting" events that took place in the power cycle before it crashed?
 
I had.

1 SSD (vertex 2E 60GB).
1 500GB (with a previous Win XP install).
2x 1TB data drives (Samsung F3).

I installed win 7 on the SSD.
I wiped out the 500 GB drive.

I experience MBR corruptions.
Win 7 repaired the MBR, then failed again.

I then disconnected the 500GB drive.
Win 7 repair installed a MBR on the SSD.

I reconnected the 500GB drive.
I re-formated the 500GB drive.

problem solved. :)
 
olivier renault said:
I had.

1 SSD (vertex 2E 60GB).
1 500GB (with a previous Win XP install).
2x 1TB data drives (Samsung F3).

I installed win 7 on the SSD.
I wiped out the 500 GB drive.

I experience MBR corruptions.
Win 7 repaired the MBR, then failed again.

I then disconnected the 500GB drive.
Win 7 repair installed a MBR on the SSD.

I reconnected the 500GB drive.
I re-formated the 500GB drive.

problem solved. :)
Click to expand...

Interesting because my other HDD's do have previous OS installation data on them. Although I made a point of installing my OS with the other drives unplugged. This created a 100MB boot partition at the start of my SSD drive.

1) relative to the corrupt mbr did you experience any data loss on your SSD? (seemingly reverting to the state from the previous power cycle as if no data had been saved)

2) were the mbr corruptions resolved automatically? Mine are unable to be repaired without using the bootrec /fixmbr command.

3) Did the computer crash/restart and then fail to boot into OS or did the data get corrupted after a normal restart/shutdown?
 
1) No. Although I did recall a restore after a windows update.
2) At first it repaired all right, then failed to repair the MBR. And yes, I had to use the command line utility.
3) I had corruptions on some files on one of the Samsungs. I had to repair TF2 once, but I don't think that was related.
 
Jordan97 said:
The Crucial M4's are very reliable drives. Also, you say it was only built last week, so unless it was damaged during shipping or installation, or you're just unlucky, it is unlikely to be the SSD.
Click to expand...

UPDATE: the Crucial M4 128GB SSD drive has been confirmed faulty and I am getting a replacement. I searched the web high and low for more cases and didn't find anything I was actually convinced these SSD's were invincible. I lost a week testing different hard drives/SATA cables/ports when it was the SSD all along. In hindsight I think it was naive to rule out the SSD as the culprit. Especially given the nature of my problems and the way flash memory works.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom