Blue screen.

I was greeted with one today.

The day before I had done numerous Windows (rather
slow) searches.

I ran CHKDSK which gave the following....
************
C:\chkdsk /f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by
another
process. Chkdsk may run if this volume is
dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE
INVALID.
Would you like to force a dismount on this volume?
(Y/N) y
Volume dismounted. All opened handles to this
volume are now invalid.
Volume label is GENERAL.

Stage 1: Examining basic file system structure ...
Deleting corrupt attribute record (0x80, "")
from file record segment 0x13185.
Correcting total allocated size in attribute
record (80, $J)
of file 2000000015218.
Deleted corrupt attribute list entry
with type code 80 in file 15218.
Deleting corrupt attribute record (0x80, $J)
from file record segment 0xB1E5.
605696 file records processed.
File verification completed.
Deleting orphan file record segment B1E5.
13011 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
Correcting sparse file record segment 86552.
13899 reparse records processed.
Deleting index entry
2748E0D469F4990D7C56E98869FE1542 in index $I30 of
file 5E0F.
Deleting index entry 2748E0~1 in index $I30 of
file 5E0F.
Deleting index entry
EEAA0AE84307852E8D8D4132091B1369 in index $I30 of
file 9488.
Deleting index entry EEAA0A~1 in index $I30 of
file 9488.
Deleting index entry AdwCleaner[S01].txt in index
$I30 of file 9E26.
Deleting index entry ADWCLE~3.TXT in index $I30 of
file 9E26.
Deleting index entry View3d in index $I30 of file
B1E3.
Deleting index entry V32IK6RK in index $I30 of
file 16D86.
Deleting index entry
microsoft.system.package.metadata in index $I30 of
file 2544B.
Deleting index entry MICROS~1.MET in index $I30 of
file 2544B.
Deleting index entry SC7735~1.ETL in index $I30 of
file 48C91.
Deleting index entry
ScreenOnPowerStudyTraceSession-2019-02-27-15-31-20.etl
in index $I30 of file 48C91.
Deleting index entry UPA364~1.ETL in index $I30 of
file 4918B.
Deleting index entry UpdateUx.027.etl in index
$I30 of file 4918B.
742952 index entries processed.
Index verification completed.
CHKDSK is scanning unindexed files for reconnect
to their original directory.
Recovering orphaned file {4FA98~1 (A4CE) into
directory file 24.
Recovering orphaned file
{4fa98527-3a3b-11e9-a975-001986003b69}{3808876b-c176-4e48-b7ae-04046e6cc752}
(A4CE) into directory file 24.
Recovering orphaned file AD25F6~1 (B1E7) into
directory file D844.
Recovering orphaned file ad25f6c128ee551b_0 (B1E7)
into directory file D844.
Recovering orphaned file {9A0E2~1 (2154C) into
directory file 17A39.
Recovering orphaned file
{9A0E2663-D514-485E-8A0E-1B24B920F84D} (2154C)
into directory file 17A39.
Recovering orphaned file {FF60A~1 (24E2E) into
directory file 24.
Recovering orphaned file
{ff60aed4-3702-11e9-a973-1c6f6538de4a}{3808876b-c176-4e48-b7ae-04046e6cc752}
(24E2E) into directory file 24.
Recovering orphaned file {931DB~1 (25092) into
directory file 24.
Recovering orphaned file
{931db67c-393d-11e9-a974-1c6f6538de4a}{3808876b-c176-4e48-b7ae-04046e6cc752}
(25092) into directory file 24.
Skipping further messages about recovering
orphans.
13 unindexed files scanned.
9 unindexed files recovered to original
directory.
CHKDSK is recovering remaining unindexed files.
4 unindexed files recovered to lost and found.
Lost and found is located at \found.002

13899 reparse records processed.
Fixing incorrect information in file record
segment 15218.
Inserting an index entry into index $I30 of file
B.

On 3/1/19 2:07 PM, Peter Jason wrote:
I was greeted with one today.

The day before I had done numerous Windows (rather
slow) searches.

I ran CHKDSK which gave the following....
************
C:\chkdsk /f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by
another
process. Chkdsk may run if this volume is
dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE
INVALID.
Would you like to force a dismount on this volume?
(Y/N) y
Volume dismounted. All opened handles to this
volume are now invalid.
Volume label is GENERAL.

Stage 1: Examining basic file system structure ...
Deleting corrupt attribute record (0x80, "")
from file record segment 0x13185.
Correcting total allocated size in attribute
record (80, $J)
of file 2000000015218.
Deleted corrupt attribute list entry
with type code 80 in file 15218.
Deleting corrupt attribute record (0x80, $J)
from file record segment 0xB1E5.
605696 file records processed.
File verification completed.
Deleting orphan file record segment B1E5.
13011 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
Correcting sparse file record segment 86552.
13899 reparse records processed.
Deleting index entry
2748E0D469F4990D7C56E98869FE1542 in index $I30 of
file 5E0F.
Deleting index entry 2748E0~1 in index $I30 of
file 5E0F.
Deleting index entry
EEAA0AE84307852E8D8D4132091B1369 in index $I30 of
file 9488.
Deleting index entry EEAA0A~1 in index $I30 of
file 9488.
Deleting index entry AdwCleaner[S01].txt in index
$I30 of file 9E26.
Deleting index entry ADWCLE~3.TXT in index $I30 of
file 9E26.
Deleting index entry View3d in index $I30 of file
B1E3.
Deleting index entry V32IK6RK in index $I30 of
file 16D86.
Deleting index entry
microsoft.system.package.metadata in index $I30 of
file 2544B.
Deleting index entry MICROS~1.MET in index $I30 of
file 2544B.
Deleting index entry SC7735~1.ETL in index $I30 of
file 48C91.
Deleting index entry
ScreenOnPowerStudyTraceSession-2019-02-27-15-31-20.etl
in index $I30 of file 48C91.
Deleting index entry UPA364~1.ETL in index $I30 of
file 4918B.
Deleting index entry UpdateUx.027.etl in index
$I30 of file 4918B.
742952 index entries processed.
Index verification completed.
CHKDSK is scanning unindexed files for reconnect
to their original directory.
Recovering orphaned file {4FA98~1 (A4CE) into
directory file 24.
Recovering orphaned file
{4fa98527-3a3b-11e9-a975-001986003b69}{3808876b-c176-4e48-b7ae-04046e6cc752}
(A4CE) into directory file 24.
Recovering orphaned file AD25F6~1 (B1E7) into
directory file D844.
Recovering orphaned file ad25f6c128ee551b_0 (B1E7)
into directory file D844.
Recovering orphaned file {9A0E2~1 (2154C) into
directory file 17A39.
Recovering orphaned file
{9A0E2663-D514-485E-8A0E-1B24B920F84D} (2154C)
into directory file 17A39.
Recovering orphaned file {FF60A~1 (24E2E) into
directory file 24.
Recovering orphaned file
{ff60aed4-3702-11e9-a973-1c6f6538de4a}{3808876b-c176-4e48-b7ae-04046e6cc752}
(24E2E) into directory file 24.
Recovering orphaned file {931DB~1 (25092) into
directory file 24.
Recovering orphaned file
{931db67c-393d-11e9-a974-1c6f6538de4a}{3808876b-c176-4e48-b7ae-04046e6cc752}
(25092) into directory file 24.
Skipping further messages about recovering
orphans.
13 unindexed files scanned.
9 unindexed files recovered to original
directory.
CHKDSK is recovering remaining unindexed files.
4 unindexed files recovered to lost and found.
Lost and found is located at \found.002

13899 reparse records processed.
Fixing incorrect information in file record
segment 15218.
Inserting an index entry into index $I30 of file
B.

Stage 3: Examining security descriptors ...
Repairing the security file record segment.
Deleting an index entry with Id 2852 from index
$SDH of file 9.
Deleting an index entry with Id 2855 from index
$SDH of file 9.
Deleting an index entry with Id 2864 from index
$SDH of file 9.
Deleting an index entry with Id 2854 from index
$SDH of file 9.
Deleting an index entry with Id 285C from index
$SDH of file 9.
Deleting an index entry with Id 2865 from index
$SDH of file 9.
Deleting an index entry with Id 285B from index
$SDH of file 9.
Deleting an index entry with Id 2869 from index
$SDH of file 9.
Deleting an index entry with Id 286A from index
$SDH of file 9.
Deleting an index entry with Id 2868 from index
$SDH of file 9.
Deleting an index entry with Id 2860 from index
$SDH of file 9.
Deleting an index entry with Id 2867 from index
$SDH of file 9.
Deleting an index entry with Id 2859 from index
$SDH of file 9.
Deleting an index entry with Id 2857 from index
$SDH of file 9.
Deleting an index entry with Id 2866 from index
$SDH of file 9.
Deleting an index entry with Id 2853 from index
$SDH of file 9.
Deleting an index entry with Id 2856 from index
$SDH of file 9.
Deleting an index entry with Id 285F from index
$SDH of file 9.
Deleting an index entry with Id 285D from index
$SDH of file 9.
Deleting an index entry with Id 2862 from index
$SDH of file 9.
Deleting an index entry with Id 285A from index
$SDH of file 9.
Deleting an index entry with Id 2858 from index
$SDH of file 9.
Deleting an index entry with Id 2861 from index
$SDH of file 9.
Deleting an index entry with Id 2863 from index
$SDH of file 9.
Deleting an index entry with Id 285E from index
$SDH of file 9.
Replacing invalid security id with default
security id for file 57DC.
Replacing invalid security id with default
security id for file 1DD51.
Replacing invalid security id with default
security id for file 1DD55.
Replacing invalid security id with default
security id for file 24EEE.
Replacing invalid security id with default
security id for file 4A7FD.
Replacing invalid security id with default
security id for file 18C6E.
Creating default security descriptor for undefined
security ID 2864.
Cleaning up 310 unused index entries from index
$SII of file 9.
Cleaning up 310 unused index entries from index
$SDH of file 9.
Cleaning up 310 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 13185.
68630 data files processed.
CHKDSK is verifying Usn Journal...
Creating Usn Journal $J data stream
Usn Journal verification completed.
Correcting errors in the master file table's (MFT)
BITMAP attribute.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

487411698 KB total disk space.
322279916 KB in 364549
***********************

But thiis did not fix the Blue Screen.

I went to the Startup blue screen and selected (1)
"Enable Debugging".

On restart the computer booted up as normal.

QUESTIONS:
1/ Did the "Debugging" fix the problem or just
bypass it?

2/ If I do an image backup now, will this backup
the problem too?

Peter



Peter!

You have a bad hard drive.

:'(

All is not lost though, this is a good excuse to upgrade
to a Samsung SSD!

:-)

Clonezilla has a rescue flag in its advanced setting. I
have had it work past all but one bad hard drive.

-T

But thiis did not fix the Blue Screen.

I went to the Startup blue screen and selected (1)
"Enable Debugging".

On restart the computer booted up as normal.

QUESTIONS:
1/ Did the "Debugging" fix the problem or just
bypass it?

2/ If I do an image backup now, will this backup
the problem too?

Peter



Peter!

You have a bad hard drive.

:'(

All is not lost though, this is a good excuse to upgrade
to a Samsung SSD!

:-)

Clonezilla has a rescue flag in its advanced setting. I
have had it work past all but one bad hard drive.

-T

I fear it IS a Samsung SSD.
Should I buy some other sort, such as a "military"
grade?

Peter Jason wrote:
But thiis did not fix the Blue Screen.

I went to the Startup blue screen and selected (1)
"Enable Debugging".

On restart the computer booted up as normal.

QUESTIONS:
1/ Did the "Debugging" fix the problem or just
bypass it?

2/ If I do an image backup now, will this backup
the problem too?

Peter


Peter!

You have a bad hard drive.

:'(

All is not lost though, this is a good excuse to upgrade
to a Samsung SSD!

:-)

Clonezilla has a rescue flag in its advanced setting. I
have had it work past all but one bad hard drive.

-T

I fear it IS a Samsung SSD.
Should I buy some other sort, such as a "military"
grade?

Do you have a military budget ?

An Enterprise drive has an ultracap to cushion the drive
on power loss.

And some have "RAIN", a kind of chip RAID
inside the drive that is intended to cover you if an
entire Flash chip fails. In this article, they describe a
product that waters the scheme down so much as to make
it pretty well pointless. Another name for such schemes
is RAISE.

https://www.tomshardware.com/reviews...ew,3772-3.html

A lot of Enterprise drives use standard NAND flash. And are
just expensive consumer drives. It's not always easy to find
a detailed spec sheet with the necessary details (like why is
it so expensive, is it actually superior, and so on).

*******

This one, instead of writing in large pages, is I think,
byte addressable. It uses a fair amount of DC power, because
it's not NAND Flash, it's based on a different physical material.

Intel 375GB Optane DC P4800X PCI Express 3.0 x4 Internal Solid State Drive $1200
20.5 PBW (60x a normal SSD lifetime). Latency 12us.

https://www.newegg.com/Product/Produ...2U3-0001-00032

There are some NAND Flash NVMe drives which are faster than
that thing. But that thing can take a beating on write cycles.
Since I have a couple 256GB SSDs with windows on them, the
375GB capacity should be workable as a boot drive. Even if
the device is overkill in terms of technical capability.

To boot from it, presumably requires the right kind of
BIOS support. Without good BIOS support, it will be a data drive,
or need help booting via a regular SSD (to hold System Reserved
or maybe the ESP).

Those Optane are even used as RAM extenders on certain Xeon motherboards.
You can get a driver that automatically pages memory out (i.e. not
an OS pagefile as such, better than a pagefile), and the device has
sufficient life to withstand doing stuff like that.

But it's a silly usage of $1200.

*******

What kind of environment is the computer in ?

Is the AC power dirty ? (Heavy equipment in the
building that "puts pulses" into all the other
electrical devices.)

A UPS (Uninterruptable Power Supply) can provide some protection.
I run my computers on a UPS, and the UPS is there for "short"
transient events. (By the time the UPS lets out a "beep" to indicate
it's flipped to battery, the power has already come back.)

Paul

On 3/2/19 2:43 PM, Peter Jason wrote:

But thiis did not fix the Blue Screen.

I went to the Startup blue screen and selected (1)
"Enable Debugging".

On restart the computer booted up as normal.

QUESTIONS:
1/ Did the "Debugging" fix the problem or just
bypass it?

2/ If I do an image backup now, will this backup
the problem too?

Peter



Peter!

You have a bad hard drive.

:'(

All is not lost though, this is a good excuse to upgrade
to a Samsung SSD!

:-)

Clonezilla has a rescue flag in its advanced setting. I
have had it work past all but one bad hard drive.

-T

I fear it IS a Samsung SSD.
Should I buy some other sort, such as a "military"
grade?



Okay, Samsungs's better quality is their SSD 860 EVO line
and has a five year warranty. They build it for "Endurance".
I would not go cheaper.

https://www.samsung.com/us/computing...mz-76e1t0b-am/

I use EVO's in RSTe RAID arrays.

You should have at least a 3 or 5 year warranty on yours.

Samsung Tech Support: 800-726-7864. Get a replacement!

On 3/2/19 9:55 PM, T wrote:
On 3/2/19 2:43 PM, Peter Jason wrote:

But thiis did not fix the Blue Screen.

I went to the Startup blue screen and selected (1)
"Enable Debugging".

On restart the computer booted up as normal.

QUESTIONS:
1/ Did the "Debugging" fix the problem or just
bypass it?

2/ If I do an image backup now, will this backup
the problem too?

Peter



Peter!

You have a bad hard drive.

:'(

All is not lost though, this is a good excuse to upgrade
to a Samsung SSD!

:-)

Clonezilla has a rescue flag in its advanced setting.Â* I
have had it work past all but one bad hard drive.

-T

I fear it IS a Samsung SSD.
Should I buy some other sort, such as a "military"
grade?



Okay, Samsungs's better quality is their SSD 860 EVO line
and has a five year warranty.Â* They build it for "Endurance".
I would not go cheaper.

https://www.samsung.com/us/computing...mz-76e1t0b-am/


I use EVO's in RSTe RAID arrays.

You should have at least a 3 or 5 year warranty on yours.

Samsung Tech Support: 800-726-7864.Â*Â* Get a replacement!


Oh, and spec out your new SSD drive with twice the space you
think you will ever need. This makes the wear leveling a
lot more reliable. (Got this from Advanced Level Samsung
memory support.)

Let us nosey poeple know how things go!

In article , wrote:


Oh, and spec out your new SSD drive with twice the space you
think you will ever need. This makes the wear leveling a
lot more reliable. (Got this from Advanced Level Samsung
memory support.)

they just wanted to sell you a more expensive part.

wear leveling reliability is not dependent on how much free space there
is. if it was, then full ssds would fail more often, and they do not.
blocks are constantly being moved around, whether or not they have user
data on them.

ssds are extremely reliable and it's simply not worth worrying about
anymore.

nospam wrote:
In article , wrote:

Oh, and spec out your new SSD drive with twice the space you
think you will ever need. This makes the wear leveling a
lot more reliable. (Got this from Advanced Level Samsung
memory support.)

they just wanted to sell you a more expensive part.

wear leveling reliability is not dependent on how much free space there
is. if it was, then full ssds would fail more often, and they do not.
blocks are constantly being moved around, whether or not they have user
data on them.

ssds are extremely reliable and it's simply not worth worrying about
anymore.

I'm surprised you have no debugging advice for Peter.

Something is corrupting information on his machine.

It might not actually be the fact it's an SSD.

It could be a dirty shutdown that's doing it.

If it was a bad SATA cable, then there are performance
counters (one of which is in SMART) which would note
the transmission errors.

There is a fairly powerful error corrector inside the
SSD. It uses perhaps 50 bytes of checksum for every
512 bytes of user data stored in Flash.

But if the memory on the computer is bad, the data
could be corrupted in memory, before being written to
disk. (This is why "real" computers have ECC, but
Intel won't let us have that.) This could include
information which is part of the file system, perhaps
screwing up metadata in the process.

Before throwing out the SSD, I'd go through the
standard procedures of "proving it's a computer"
first. If it is something other than the SSD itself,
then placing an HDD in the machine for a while might
also end up corrupted. I would sooner test with
a junker HDD in the machine for a few days, then
buy a new SSD for nothing.

Paul

In article , Paul
wrote:

Oh, and spec out your new SSD drive with twice the space you
think you will ever need. This makes the wear leveling a
lot more reliable. (Got this from Advanced Level Samsung
memory support.)

they just wanted to sell you a more expensive part.

wear leveling reliability is not dependent on how much free space there
is. if it was, then full ssds would fail more often, and they do not.
blocks are constantly being moved around, whether or not they have user
data on them.

ssds are extremely reliable and it's simply not worth worrying about
anymore.

I'm surprised you have no debugging advice for Peter.

Something is corrupting information on his machine.

It might not actually be the fact it's an SSD.

ssds don't corrupt on their own.

It could be a dirty shutdown that's doing it.

could be, or more likely a buggy app, or any number of other things.

however, i was only commenting on buying twice the capacity. it's
always nice to have a additional capacity, but wear leveling is not a
reason to do so.

On Sun, 03 Mar 2019 09:43:12 +1100, Peter Jason wrote:


You have a bad hard drive.

:'(

All is not lost though, this is a good excuse to upgrade to a Samsung
SSD!

:-)

Clonezilla has a rescue flag in its advanced setting. I have had it
work past all but one bad hard drive.

-T

I fear it IS a Samsung SSD.
Should I buy some other sort, such as a "military"
grade?

I prefer Western Digital, myself.

On 3/4/19 1:18 PM, ray carter wrote:
On Sun, 03 Mar 2019 09:43:12 +1100, Peter Jason wrote:


You have a bad hard drive.

:'(

All is not lost though, this is a good excuse to upgrade to a Samsung
SSD!

:-)

Clonezilla has a rescue flag in its advanced setting. I have had it
work past all but one bad hard drive.

-T

I fear it IS a Samsung SSD.
Should I buy some other sort, such as a "military"
grade?

I prefer Western Digital, myself.


WD's drives seem pretty good to me too. And they get good
rating for reliability from the Cloud Storage folks I have
read. But their tech support in foreign based and sucks.

I have had a bad Blue drive, but no bad red ones as of yet.

In article , lid says...

On 3/4/19 1:18 PM, ray carter wrote:
On Sun, 03 Mar 2019 09:43:12 +1100, Peter Jason wrote:


You have a bad hard drive.

:'(

All is not lost though, this is a good excuse to upgrade to a Samsung
SSD!

:-)

Clonezilla has a rescue flag in its advanced setting. I have had it
work past all but one bad hard drive.

-T

I fear it IS a Samsung SSD.
Should I buy some other sort, such as a "military"
grade?

I prefer Western Digital, myself.


WD's drives seem pretty good to me too. And they get good
rating for reliability from the Cloud Storage folks I have
read. But their tech support in foreign based and sucks.

I have had a bad Blue drive, but no bad red ones as of yet.

Both Seagate and WD seem to have at least reasonable return methods for
bad warranteed drives. Never a problem with either and in fact once
Seagate went above and beyond by replacing a 2nd external was out of
warranty while doing one that was. (And it's still works fine years
later

I've not kept track but I've returned fair number of hard disk drives
over last few decades to both companies.

I don't like the cost to ship it back as it adds 20% or more to cost to
yourself of owning the drive. But that seems true of anything now-a-
days. Part of why I prefer brick and mortar and always will.

One reason always liked Logitech. They'd just send you a new one and
said do what you want with the old one. Got me a 2nd racing wheel when I
was able to repair defective on, both now still work fine.