0x0000007 BSOD drive not booting

**HipHoper** · December 18th, 2011, 02:23 PM

Hi all,

Had 2nd BSOD in the past week on my win7 system with 0x0000007 error.
After hard reset the bios didn't recognised my main SSD drive. Only a full power off and then on made the bios recognise the SSD.
Do you think it is a failing SSD drive according to this data ? From my experience it is a failing drive behaviour, Just wanted to confirm it....

**cookin chef** · December 18th, 2011, 05:09 PM

That's a clear pattern of something going on with the SSD if you have to do a cold power shutdown to get it working again.
The 0x0000007 BSOD can refer to almost anything.
If you have a spare SSD or HD and copy an image if still ok to determine the issue, then that should confirm your suspicions.

**HipHoper** · December 18th, 2011, 05:37 PM

Thanks Chef.
I was working with a different main drive a month ago without any problems before i changed it to this SSD.
I posted a ticket at OCZ and hopefully they will RMA it.

**slgrieb** · December 18th, 2011, 07:03 PM

A few months ago, I had an OCZ Vertex 2 180 GB drive that did about the same thing after exactly 1 month and 10 days of use. I found that OCZ was slow to process the RMA, but once they had done so and they had the old drive in the RMA center, I had a new drive in 2days, even though it was shipped directly from Taiwan. Overall, a pretty good RMA experience.

The determining factor in SSD life appears, over all , to be the firmware. So, generally, I would suggest that you update the firmware on the drive before it is put into service. OCZ's updater will not update a drive that's being used as a system drive, so if you do the update later, you'll need to connect the drive to another computer. And you really want to have a full backup in hand first.

Still, my replacement OCZ Vertex 2 and other Vertex 2, Vertex 3, and Agility drives I've used to build systems have all been trouble free. I'd say that given decent frimware, that a SSD will problably last about like a standard HDD, because the electronics in the controller are likely to be the first component to fail.

**HipHoper** · December 19th, 2011, 01:05 AM

Oh that's a great idea to update the firmware Slg. Thanks. Will do it right now and will see how the drive behaves after that.

**HipHoper** · December 19th, 2011, 06:04 PM

Update :

http://techreport.com/articles.x/21934

According to this article, It seems that latest SSD firmware addresses my BSOD problem : "Fixed a rare condition that may cause Windows Blue Screen error when the drive was configured as primary with OS installed"
Just updated the drive and will see if it solved the problem.

Thanks again Slg for your great insights and sharing your experience

**JohnSmith420** · November 9th, 2013, 10:46 AM

This problem appears due to problematic system files and settings. There is a tool called Windows Memory Diagnostic which conducts memory tests to identify RAM problem. Run the tool and check if that solves your problem. You can use a hotfix available online. Alternatively, the steps given below can be very useful for you. Follow them until your issue is completely fixed:

Run Windows Memory Diagnostic

1. Open the Start Screen.
2. Type Windows Memory Diagnostic.
3. Press ENTER.
4. Click Restart now and check for problems.

Use System Restore

1. Open the Start Screen.
2. Type System Restore.
3. Press ENTER.
4. Click Next, select a restore point and then continue the wizard.

Run System File Checker

1. Open the Start Screen.
2. Type Command Prompt.
3. Press ENTER.
4. Type SFC /SCANNOW in the window and press ENTER.
5. Restart your computer when you're done.

**HipHoper** · November 9th, 2013, 01:12 PM

Hi John,

It is a very old post and I think the cause of the problem was sandforce SSD firmware bug.
Anyway thanks for your input.

**JohnSmith420** · November 9th, 2013, 07:19 PM

Thanks for your comment.

I thought my answer would be helpful for anyone who visit the post and experience the same problem.

Originally Posted by HipHoper

Hi John,

It is a very old post and I think the cause of the problem was sandforce SSD firmware bug.
Anyway thanks for your input.

***SpywareDr*** · November 10th, 2013, 01:06 PM

Originally Posted by JohnSmith420

This problem appears due to problematic system files and settings.

Nope. It was due to a firmware issue:

Here's the skinny direct from the release notes (PDF):

Fixed a rare condition that may cause Windows Blue Screen error when the primary configured drive woke up from either a SATA slumber mode or S3/S4 mode
Fixed a rare condition that may cause Windows Blue Screen error when the drive was configured as primary with OS installed
Fixed a corner-case issue that may cause the drive to stutter or Windows freezing screen when a media read error occurred

Originally Posted by JohnSmith420

There is a tool called Windows Memory Diagnostic which conducts memory tests to identify RAM problem. Run the tool and check if that solves your problem. ...

How would running "Windows Memory Diagnostic" resolve "problematic system files and settings"?

**JohnSmith420** · November 10th, 2013, 06:21 PM

@SpywareDr: I never mentioned running Windows Memory Diagnostic would solve problematic system files and settings. WMD is a memory troubleshooting tool. As long as system file corruption is concerned, there is another tool called System File Checker (SFC).

***SpywareDr*** · November 11th, 2013, 07:46 AM

Here's what you said:

Originally Posted by JohnSmith420

This problem appears due to problematic system files and settings. There is a tool called Windows Memory Diagnostic which conducts memory tests to identify RAM problem. Run the tool and check if that solves your problem.