Has my SSD died?

I switched on the computer today and I got the message the system SSD
(C needed ''repair'' and then it went thru the ''scan & repair"
sequence, but it failed and I was left with a blue "could not fix"
blue message, with a suggestion I try ''system Restore''. This ran
but failed to complete.

I then went over to my other copy of Windows10 on a different SSD
(P on the same motherboard and did a Macrium backup of the failed
SSD. This backup ran normally.

The failed SSD (C was CHKDSK from there, (P but this failed to
find problems! I did a chkdsk /scan and a chkdsk /spotfix too with no
problems indicated.

Why does this problem not show up when C: is scanned from another SSD?

Anyway, I can rescue data from the Macrium backup of C: but....

Can I transfer failed C: SSD data and OS to a brand new SSD using the
above Macrium backup? And so fix the problem?

When buying a new SSD, is it worth while to invest in a
"military-grade one? They're dearer.

Peter Jason wrote:
I switched on the computer today and I got the message the system SSD
(C needed ''repair'' and then it went thru the ''scan & repair"
sequence, but it failed and I was left with a blue "could not fix"
blue message, with a suggestion I try ''system Restore''. This ran
but failed to complete.

I then went over to my other copy of Windows10 on a different SSD
(P on the same motherboard and did a Macrium backup of the failed
SSD. This backup ran normally.

The failed SSD (C was CHKDSK from there, (P but this failed to
find problems! I did a chkdsk /scan and a chkdsk /spotfix too with no
problems indicated.

Why does this problem not show up when C: is scanned from another SSD?

Anyway, I can rescue data from the Macrium backup of C: but....

Can I transfer failed C: SSD data and OS to a brand new SSD using the
above Macrium backup? And so fix the problem?

When buying a new SSD, is it worth while to invest in a
"military-grade one? They're dearer.

So all we know so far, is you have a C: drive that
failed to boot. You're claiming the file system is intact
and CHKDSK doesn't find a problem.

That means some boot information isn't correct.

Or alternately, your AV quarantined key system files,
turning your OS into luncheon meat (the ham loaf with
the olive slices).

Boot your Macrium Reflect emergency CD and make a backup of
the SSD now. That's in case any other step fails.

Macrium backups can be restored to brand-new storage devices.
The software even supports "resize-on-the-fly" and you can
shoehorn a bigger backup into a smaller space. If you have
20GB of files on a 1TB SSD, you can restore the 20GB of
files and structures to a 500GB SSD.

The Macrium Reflect CD also supports "clone" of one drive
to another, including the very same "resize-on-the-fly" capability.
When cloning, click "Next", then "Back", then click the partition
needing a size or alignment adjustment and a dialog with
size controls should appear. You can then adjust the partitions
to suit the available space.

Obviously, you cannot restore 1TB *of files* to a 500GB drive.
But if there is merely a different in "air space" between two
disks, Macrium has options you can use. It's not perfect, and
a Partition Manager (there are free ones) might well be
needed later to make it "neat and tidy".

You can see me using the resize control in these film strips.
Click to magnify.

http://s22.postimg.org/487zw4g1d/Clone_Disk.gif

This one is a bit better. I can no longer make these, as PostImg
just ruins them.

http://s9.postimg.org/gwn36sxhr/Macrium_Restore_CD.gif

*******

Now that you have your Safety Backup of the SSD made, it's
on to the next step...

Boot your Macrium Reflect emergency CD, and look in the miscellaneous
menu, where there is a "Boot Repair" item. Give that a try. Then
let Windows Boot repair do its thing and see if it comes back up.
It might.

A "semi-intelligent" way to do this, is boot a Win10 DVD and
use the Command Prompt window, run "bcdedit" and look for
"blank" entries for key boot parameters. Such blank entries ****
off Windows and cause stuff like this to happen. Don't ask me
what is editing the \boot\BCD and ruining it. There are actual
Microsoft utilities that can ruin it, as well as the usage
of EasyBCD (since it would be editing the BCD - it probably
keeps backups somewhere).

The Macrium boot repair on the CD, is better than the Windows
one. For whatever that is worth. I recommend making a Macrium
WinPE CD for that reason alone.

Paul

On Thu, 01 Mar 2018 19:01:06 -0500, Paul
wrote:

Peter Jason wrote:
I switched on the computer today and I got the message the system SSD
(C needed ''repair'' and then it went thru the ''scan & repair"
sequence, but it failed and I was left with a blue "could not fix"
blue message, with a suggestion I try ''system Restore''. This ran
but failed to complete.

I then went over to my other copy of Windows10 on a different SSD
(P on the same motherboard and did a Macrium backup of the failed
SSD. This backup ran normally.

The failed SSD (C was CHKDSK from there, (P but this failed to
find problems! I did a chkdsk /scan and a chkdsk /spotfix too with no
problems indicated.

Why does this problem not show up when C: is scanned from another SSD?

Anyway, I can rescue data from the Macrium backup of C: but....

Can I transfer failed C: SSD data and OS to a brand new SSD using the
above Macrium backup? And so fix the problem?

When buying a new SSD, is it worth while to invest in a
"military-grade one? They're dearer.

So all we know so far, is you have a C: drive that
failed to boot. You're claiming the file system is intact
and CHKDSK doesn't find a problem.

That means some boot information isn't correct.

Or alternately, your AV quarantined key system files,
turning your OS into luncheon meat (the ham loaf with
the olive slices).

Boot your Macrium Reflect emergency CD and make a backup of
the SSD now. That's in case any other step fails.

Macrium backups can be restored to brand-new storage devices.
The software even supports "resize-on-the-fly" and you can
shoehorn a bigger backup into a smaller space. If you have
20GB of files on a 1TB SSD, you can restore the 20GB of
files and structures to a 500GB SSD.

The Macrium Reflect CD also supports "clone" of one drive
to another, including the very same "resize-on-the-fly" capability.
When cloning, click "Next", then "Back", then click the partition
needing a size or alignment adjustment and a dialog with
size controls should appear. You can then adjust the partitions
to suit the available space.

Obviously, you cannot restore 1TB *of files* to a 500GB drive.
But if there is merely a different in "air space" between two
disks, Macrium has options you can use. It's not perfect, and
a Partition Manager (there are free ones) might well be
needed later to make it "neat and tidy".

You can see me using the resize control in these film strips.
Click to magnify.

http://s22.postimg.org/487zw4g1d/Clone_Disk.gif

This one is a bit better. I can no longer make these, as PostImg
just ruins them.

http://s9.postimg.org/gwn36sxhr/Macrium_Restore_CD.gif

*******

Now that you have your Safety Backup of the SSD made, it's
on to the next step...

Boot your Macrium Reflect emergency CD, and look in the miscellaneous
menu, where there is a "Boot Repair" item. Give that a try. Then
let Windows Boot repair do its thing and see if it comes back up.
It might.

A "semi-intelligent" way to do this, is boot a Win10 DVD and
use the Command Prompt window, run "bcdedit" and look for
"blank" entries for key boot parameters. Such blank entries ****
off Windows and cause stuff like this to happen. Don't ask me
what is editing the \boot\BCD and ruining it. There are actual
Microsoft utilities that can ruin it, as well as the usage
of EasyBCD (since it would be editing the BCD - it probably
keeps backups somewhere).

The Macrium boot repair on the CD, is better than the Windows
one. For whatever that is worth. I recommend making a Macrium
WinPE CD for that reason alone.

Paul



Thank you.

I have started to do as you say by inserting the Macrium Reserve Media
Rescue Disk of April 2016, hoping thereby to do a backup from it.
But I forgot to set the BIOS to CD boot and so the computer booted
from the system as usual, but without the Blue screen trouble, and all
seems normal. So it fixed itself. Too good to be true of course, so
I wait for the trouble to reappear.

Here is the Disk Management picture of the System SSD.....
https://postimg.org/image/ffn7e3yxh/

Is there any other diagnostic info I should check?

Peter Jason wrote:

Thank you.

I have started to do as you say by inserting the Macrium Reserve Media
Rescue Disk of April 2016, hoping thereby to do a backup from it.
But I forgot to set the BIOS to CD boot and so the computer booted
from the system as usual, but without the Blue screen trouble, and all
seems normal. So it fixed itself. Too good to be true of course, so
I wait for the trouble to reappear.

Here is the Disk Management picture of the System SSD.....
https://postimg.org/image/ffn7e3yxh/

Is there any other diagnostic info I should check?

Cool. It's got two Recovery partitions.

1) I'd still make sure I had a backup.

2) Once the backup is made (and only then),
would I run CHKDSK on it. Just the basic
CHKDSK without the /F. It would be better to run
that with the OS offline, to avoid any excuses about
"busy file systems". I would want to make sure it really
doesn't have any issues.

If the OS is "healthy" in the sense it boots and
seems to work, who are we to argue ? :-) Just more magic
beans I guess.

You should learn about the popup boot key. My two computers
here use Asus motherboards, and the key to use is F8. I get
a menu that would include a DVD, a USB stick, and all the
internal hard drives. I can cursor down in the menu and select
the DVD.

On my laptop, the key is F12. And the timing window on the laptop
(an Insyde BIOS design) is one second. You need ninja like reflexes
to press the F12 at just the right moment. And then I can select the
DVD drive if I want.

You can also enter the BIOS setup screen and put the removable media
devices before the hard drive. That's another way to set things up.
But I like my popup boot menu, and I hammer on that even when I
don't need to. It gives me an opportunity to check what drives
are connected inside the case.

Paul

On 3/1/2018 10:30 PM, Peter Jason wrote:
On Thu, 01 Mar 2018 19:01:06 -0500, Paul
wrote:

Peter Jason wrote:
I switched on the computer today and I got the message the system SSD
(C needed ''repair'' and then it went thru the ''scan & repair"
sequence, but it failed and I was left with a blue "could not fix"
blue message, with a suggestion I try ''system Restore''. This ran
but failed to complete.

I then went over to my other copy of Windows10 on a different SSD
(P on the same motherboard and did a Macrium backup of the failed
SSD. This backup ran normally.

The failed SSD (C was CHKDSK from there, (P but this failed to
find problems! I did a chkdsk /scan and a chkdsk /spotfix too with no
problems indicated.

Why does this problem not show up when C: is scanned from another SSD?

Anyway, I can rescue data from the Macrium backup of C: but....

Can I transfer failed C: SSD data and OS to a brand new SSD using the
above Macrium backup? And so fix the problem?

When buying a new SSD, is it worth while to invest in a
"military-grade one? They're dearer.

So all we know so far, is you have a C: drive that
failed to boot. You're claiming the file system is intact
and CHKDSK doesn't find a problem.

That means some boot information isn't correct.

Or alternately, your AV quarantined key system files,
turning your OS into luncheon meat (the ham loaf with
the olive slices).

Boot your Macrium Reflect emergency CD and make a backup of
the SSD now. That's in case any other step fails.

Macrium backups can be restored to brand-new storage devices.
The software even supports "resize-on-the-fly" and you can
shoehorn a bigger backup into a smaller space. If you have
20GB of files on a 1TB SSD, you can restore the 20GB of
files and structures to a 500GB SSD.

The Macrium Reflect CD also supports "clone" of one drive
to another, including the very same "resize-on-the-fly" capability.
When cloning, click "Next", then "Back", then click the partition
needing a size or alignment adjustment and a dialog with
size controls should appear. You can then adjust the partitions
to suit the available space.

Obviously, you cannot restore 1TB *of files* to a 500GB drive.
But if there is merely a different in "air space" between two
disks, Macrium has options you can use. It's not perfect, and
a Partition Manager (there are free ones) might well be
needed later to make it "neat and tidy".

You can see me using the resize control in these film strips.
Click to magnify.

http://s22.postimg.org/487zw4g1d/Clone_Disk.gif

This one is a bit better. I can no longer make these, as PostImg
just ruins them.

http://s9.postimg.org/gwn36sxhr/Macrium_Restore_CD.gif

*******

Now that you have your Safety Backup of the SSD made, it's
on to the next step...

Boot your Macrium Reflect emergency CD, and look in the miscellaneous
menu, where there is a "Boot Repair" item. Give that a try. Then
let Windows Boot repair do its thing and see if it comes back up.
It might.

A "semi-intelligent" way to do this, is boot a Win10 DVD and
use the Command Prompt window, run "bcdedit" and look for
"blank" entries for key boot parameters. Such blank entries ****
off Windows and cause stuff like this to happen. Don't ask me
what is editing the \boot\BCD and ruining it. There are actual
Microsoft utilities that can ruin it, as well as the usage
of EasyBCD (since it would be editing the BCD - it probably
keeps backups somewhere).

The Macrium boot repair on the CD, is better than the Windows
one. For whatever that is worth. I recommend making a Macrium
WinPE CD for that reason alone.

Paul



Thank you.

I have started to do as you say by inserting the Macrium Reserve Media
Rescue Disk of April 2016, hoping thereby to do a backup from it.
But I forgot to set the BIOS to CD boot and so the computer booted
from the system as usual, but without the Blue screen trouble, and all
seems normal. So it fixed itself. Too good to be true of course, so
I wait for the trouble to reappear.

Here is the Disk Management picture of the System SSD.....
https://postimg.org/image/ffn7e3yxh/

Is there any other diagnostic info I should check?

BACK UP YOU DISK NOW, before you do anything.

click the MS icon and type in "Troubleshooting", select Troubleshooting
, and run the appropriate test

--
2018: The year we learn to play the great game of Euchre

On 02/03/2018 03:30, Peter Jason wrote:
On Thu, 01 Mar 2018 19:01:06 -0500, Paul
wrote:

Peter Jason wrote:
I switched on the computer today and I got the message the system SSD
(C needed ''repair'' and then it went thru the ''scan & repair"
sequence, but it failed and I was left with a blue "could not fix"
blue message, with a suggestion I try ''system Restore''. This ran
but failed to complete.

I then went over to my other copy of Windows10 on a different SSD
(P on the same motherboard and did a Macrium backup of the failed
SSD. This backup ran normally.

The failed SSD (C was CHKDSK from there, (P but this failed to
find problems! I did a chkdsk /scan and a chkdsk /spotfix too with no
problems indicated.

Why does this problem not show up when C: is scanned from another SSD?

Anyway, I can rescue data from the Macrium backup of C: but....

Can I transfer failed C: SSD data and OS to a brand new SSD using the
above Macrium backup? And so fix the problem?

When buying a new SSD, is it worth while to invest in a
"military-grade one? They're dearer.

So all we know so far, is you have a C: drive that
failed to boot. You're claiming the file system is intact
and CHKDSK doesn't find a problem.

That means some boot information isn't correct.

Or alternately, your AV quarantined key system files,
turning your OS into luncheon meat (the ham loaf with
the olive slices).

Boot your Macrium Reflect emergency CD and make a backup of
the SSD now. That's in case any other step fails.

Macrium backups can be restored to brand-new storage devices.
The software even supports "resize-on-the-fly" and you can
shoehorn a bigger backup into a smaller space. If you have
20GB of files on a 1TB SSD, you can restore the 20GB of
files and structures to a 500GB SSD.

The Macrium Reflect CD also supports "clone" of one drive
to another, including the very same "resize-on-the-fly" capability.
When cloning, click "Next", then "Back", then click the partition
needing a size or alignment adjustment and a dialog with
size controls should appear. You can then adjust the partitions
to suit the available space.

Obviously, you cannot restore 1TB *of files* to a 500GB drive.
But if there is merely a different in "air space" between two
disks, Macrium has options you can use. It's not perfect, and
a Partition Manager (there are free ones) might well be
needed later to make it "neat and tidy".

You can see me using the resize control in these film strips.
Click to magnify.

http://s22.postimg.org/487zw4g1d/Clone_Disk.gif

This one is a bit better. I can no longer make these, as PostImg
just ruins them.

http://s9.postimg.org/gwn36sxhr/Macrium_Restore_CD.gif

*******

Now that you have your Safety Backup of the SSD made, it's
on to the next step...

Boot your Macrium Reflect emergency CD, and look in the miscellaneous
menu, where there is a "Boot Repair" item. Give that a try. Then
let Windows Boot repair do its thing and see if it comes back up.
It might.

A "semi-intelligent" way to do this, is boot a Win10 DVD and
use the Command Prompt window, run "bcdedit" and look for
"blank" entries for key boot parameters. Such blank entries ****
off Windows and cause stuff like this to happen. Don't ask me
what is editing the \boot\BCD and ruining it. There are actual
Microsoft utilities that can ruin it, as well as the usage
of EasyBCD (since it would be editing the BCD - it probably
keeps backups somewhere).

The Macrium boot repair on the CD, is better than the Windows
one. For whatever that is worth. I recommend making a Macrium
WinPE CD for that reason alone.

Paul



Thank you.

I have started to do as you say by inserting the Macrium Reserve Media
Rescue Disk of April 2016, hoping thereby to do a backup from it.
But I forgot to set the BIOS to CD boot and so the computer booted
from the system as usual, but without the Blue screen trouble, and all
seems normal. So it fixed itself. Too good to be true of course, so
I wait for the trouble to reappear.

Here is the Disk Management picture of the System SSD.....
https://postimg.org/image/ffn7e3yxh/

Is there any other diagnostic info I should check?


Check if the manufacturer of your SSD provides utility software that can
tell you the "health" of your SSD. This will give you an idea of whether
or not it's nearing the end of it's life.

--

Brian Gregory (in England).

On Thu, 01 Mar 2018 19:01:06 -0500, Paul
wrote:

The Macrium boot repair on the CD, is better than the Windows
one. For whatever that is worth. I recommend making a Macrium
WinPE CD for that reason alone.


+1

That repair function on the Macrium CD has proved very useful this
past week.

On Sun, 4 Mar 2018 03:21:40 +0000, Brian Gregory
wrote:

On 02/03/2018 03:30, Peter Jason wrote:
On Thu, 01 Mar 2018 19:01:06 -0500, Paul
wrote:

Peter Jason wrote:
I switched on the computer today and I got the message the system SSD
(C needed ''repair'' and then it went thru the ''scan & repair"
sequence, but it failed and I was left with a blue "could not fix"
blue message, with a suggestion I try ''system Restore''. This ran
but failed to complete.

I then went over to my other copy of Windows10 on a different SSD
(P on the same motherboard and did a Macrium backup of the failed
SSD. This backup ran normally.

The failed SSD (C was CHKDSK from there, (P but this failed to
find problems! I did a chkdsk /scan and a chkdsk /spotfix too with no
problems indicated.

Why does this problem not show up when C: is scanned from another SSD?

Anyway, I can rescue data from the Macrium backup of C: but....

Can I transfer failed C: SSD data and OS to a brand new SSD using the
above Macrium backup? And so fix the problem?

When buying a new SSD, is it worth while to invest in a
"military-grade one? They're dearer.

So all we know so far, is you have a C: drive that
failed to boot. You're claiming the file system is intact
and CHKDSK doesn't find a problem.

That means some boot information isn't correct.

Or alternately, your AV quarantined key system files,
turning your OS into luncheon meat (the ham loaf with
the olive slices).

Boot your Macrium Reflect emergency CD and make a backup of
the SSD now. That's in case any other step fails.

Macrium backups can be restored to brand-new storage devices.
The software even supports "resize-on-the-fly" and you can
shoehorn a bigger backup into a smaller space. If you have
20GB of files on a 1TB SSD, you can restore the 20GB of
files and structures to a 500GB SSD.

The Macrium Reflect CD also supports "clone" of one drive
to another, including the very same "resize-on-the-fly" capability.
When cloning, click "Next", then "Back", then click the partition
needing a size or alignment adjustment and a dialog with
size controls should appear. You can then adjust the partitions
to suit the available space.

Obviously, you cannot restore 1TB *of files* to a 500GB drive.
But if there is merely a different in "air space" between two
disks, Macrium has options you can use. It's not perfect, and
a Partition Manager (there are free ones) might well be
needed later to make it "neat and tidy".

You can see me using the resize control in these film strips.
Click to magnify.

http://s22.postimg.org/487zw4g1d/Clone_Disk.gif

This one is a bit better. I can no longer make these, as PostImg
just ruins them.

http://s9.postimg.org/gwn36sxhr/Macrium_Restore_CD.gif

*******

Now that you have your Safety Backup of the SSD made, it's
on to the next step...

Boot your Macrium Reflect emergency CD, and look in the miscellaneous
menu, where there is a "Boot Repair" item. Give that a try. Then
let Windows Boot repair do its thing and see if it comes back up.
It might.

A "semi-intelligent" way to do this, is boot a Win10 DVD and
use the Command Prompt window, run "bcdedit" and look for
"blank" entries for key boot parameters. Such blank entries ****
off Windows and cause stuff like this to happen. Don't ask me
what is editing the \boot\BCD and ruining it. There are actual
Microsoft utilities that can ruin it, as well as the usage
of EasyBCD (since it would be editing the BCD - it probably
keeps backups somewhere).

The Macrium boot repair on the CD, is better than the Windows
one. For whatever that is worth. I recommend making a Macrium
WinPE CD for that reason alone.

Paul



Thank you.

I have started to do as you say by inserting the Macrium Reserve Media
Rescue Disk of April 2016, hoping thereby to do a backup from it.
But I forgot to set the BIOS to CD boot and so the computer booted
from the system as usual, but without the Blue screen trouble, and all
seems normal. So it fixed itself. Too good to be true of course, so
I wait for the trouble to reappear.

Here is the Disk Management picture of the System SSD.....
https://postimg.org/image/ffn7e3yxh/

Is there any other diagnostic info I should check?


Check if the manufacturer of your SSD provides utility software that can
tell you the "health" of your SSD. This will give you an idea of whether
or not it's nearing the end of it's life.


Thanks, I used this, which showed the SSD to be OK.
http://www.samsung.com/semiconductor...ownload/tools/


It's starting to look like a Motherboard problem.