Long DST Failure ID: UAGFV-7SQ95S-PXPJL1-618J03

[tubadave969]

Diagnostic test UEFI ended up in Long DST Failure ID: UAGFVR-7SQ95S-PXPJL1-618J03.

Once started, the PC works fine. 

Suggestions? Feedback?

(Failure ID# corrected in edit)

[CherylG]

Failing the long DST usually indicates the drive is failing- still able to boot but probably not for much longer. Best to get your files backed up now while you can- and start shopping for a new drive at some point in near future.

[tubadave969]

Well, unfortunately, I agree with you. The problem is that I just had a new drive put in last week. I'm beginning to think the drive was actually used. The person installing gave a year warranty so if I don't get some feedback for some options or exactly what the code means here in the forum, I'm just going to take it back to him. I just want to exhaust as many options as I can before I take it back. 

I was really hoping that I could just type in the failure ID# somewhere on the HP support site and it would tell me exactly what the ID# means. 

But, thank you for the reply. I'm going to keep this up for a bit and see if anyone else has any input.

[CherylG]

@tubadave969

Actually your code is one character short in the first set. Should be 4 sets of 6 each.

[tubadave969]

Thanks for noticing that. I'll edit it now.

[CherylG]

@tubadave969

You can use the HP Failure ID decoder to enter  the error code-under More Solutions.. Unfortunately all it will tell you is the hdd failed the long DST test.

[tubadave969]

Okay...I was temporarily marked as spam. 

The ID decoder gave the expected repsonse. 

I also ran chkdsk and used the OS check in the HP Support Assistant and they showed everthing was fine. 

I'm still leaning towards the "new" drive having a real issue and I need to take it back to the guy that installed it.

The complete failure number is below if anyone has any additional ideas.

[CherylG · Accepted solution]

@tubadave969

It is not unheard of for even a new drive to be faulty. The long DST (Disk Self Test) does the same things a short DST does such as check major components of a drive-read/write heads,controller,etc but goes further and tests for bad/corrupted areas  and works to reallocate and re-map the damaged portions so they are not used.  That may explain why OS check didn't see any problems after running long DST.

I have seen some posters who couldn't boot but managed to boot after running the test.That didn't mean the drive was healed- just patched up by reallocating the bad areas so they aren't used.