[SOLVED] Windows 10 corrupts files after SSD upgrade

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
C

Chehab.Ibrahim

Reputable
Jan 1, 2019
32
1
4,545
I recently upgraded my computer (HP Compaq 6200 SFF)'s hard drive to an SSD (G-skill falcon II). I installed all the storage controller drivers and everything. For some reason, my system keeps getting files corrupted. sfc /scannow can't complete (Error:Windows Resource Protection could not perform the requested operation. ) and stops at 26%, and chkdsk doesn't seem to help either. It scans up until ~20%, then locks up and skips to 100% This is my 5th windows install with this issue. Please help
 
Solution
Darkbreeze
That's BS. I've used Seatools and WD lifeguard tools for MANY, MANY years, and have never seen anything like that happen. I've never once seen a drive pass the DST or Long tests and actually be a faulty drive.

Which is not to say that Hard disk sentinel is particularly bad either. ALL these drive testing utilities use the same basic tests, in the same basic way. The only real differences are the packaging and branding of the utility and some minor variations in implementation.

In fact, your assumption that those tools are "less" capable than HDS has been called out, and disproven, on many occasions in the past.

Here is just one example. Again, HDS is fine too, but it's not "better" in any meaningful sense of the word. They all run...
Sort by date Sort by votes


I can't seem to find my drive on G Skill's website, and I can't go back for warranty because my father bought this SSD for my birthday and he bought it from his friend that fixes and sells PC's
 
Upvote 0 Downvote
A lot of moving parts in this thread.
Do you happen to still have your old hard drive hanging around? Can you remove the SSD, put it back in, and run some stability tests, hard drive mfg. tests, etc.?
Did the issues start when you added the extra RAM from the other system? Also, those RAM sticks use the same HP part # so they're *supposed* to be compatible.
 
Upvote 0 Downvote


Yes, I still have my old hard drive. I'll try that. I added the RAM back when I had my hard drive, and it worked fine.
 
Upvote 0 Downvote


Any time you mix ANY memory, even two kits that are the same identical model/part number, there is always a degree of uncertainty when it comes down to whether or not they will play nice together. From one production run to the next memory manufacturers may make BIG changes while continuing to use the same part number for the kit or sticks. Or even if they ARE identical, same ICs used, same number of ranks, rows, etc., sometimes one batch of modules simply won't work well or at all with another set that you'd THINK are exactly the same.

Case in point. Three different completely different memory configurations on sticks that ALL share the same model number.

http://www.tomshardware.com/answers/id-3610013/amd-ram-compatibility.html#20562100


And that's when they ARE the same. When they are NOT, the chances of there being problems just goes up. That being said, I and many other people HAVE run completely different sticks on the same system with varying levels of success or even with no problems at all. It's not that they CAN'T work together, it's just that often they DON'T.

Testing the configuration is the only way to be sure.

 
Upvote 0 Downvote
@darkbreeze, I completely agree. There is always a risk. I was being somewhat tongue-in-cheek with the asterisks.

However, looking at the picture of the two sticks posted, and the fact that OEM HP boards are normally okay with slight differences in ICs across the same model number, I was making a guess that they would work.

In the end, the best route will always be a 'test it and see' methodology.
 
Upvote 0 Downvote
UEFI mode? Did you create bootable media on a USB drive and boot to the USB drive in order to run Memtest? That is the way it should be done.

As far as not being able to run it in parallel mode, I haven't seen that issue before.

Is your motherboard BIOS version up to date?

Regardless, it just takes longer to run the 4 passes of Memtest with a single core rather than in parallel mode, but if it passed all the tests for four passes then the memory configuration is not the problem and we are back to it likely being either a bad cable or bad drive. Might even be a bad power supply.
 
Upvote 0 Downvote
Yes I did make a bootable USB drive. I'm pretty sure I updated my BIOS to the latest, but I'll double check. I'll see if I can get my hands on a new cable, and I have another power supply from the other PC I was talking about.
 
Upvote 0 Downvote
Hello all! Thank you for your continued support. Over the past couple of weeks, I have been running all the tests you have recommended, and came to the conclusion that the SSD was bad. I have ordered a brand new SSD and am awaiting it's arrival. Thank you all once again
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom