Possible SSD failure/Windows problems

Toggle sidebar Toggle sidebar
J

JeanPi

Honorable
Jul 30, 2015
35
0
10,530
Hi. I tried looking around for info on my problems, but can't seem to find anything, so i thought i'd ask for opinions here.

Recently, i've had to wipe and re install Windows on my SSD (OCZ Vector 150 240gb) about 10 times in the span of about 2 weeks. Thing is, i've encountered many errors on my windows install. First time it wouldn't let me delete a file from the recycle bin, would not do a system restore and then failed to boot until i wiped. Next, it would refuse to install .net framework. Most recently, i tried to launch something and it gave me an error saying that it had blocked loading of a file located in system32, which was directx related if im not mistaken. I tried a simple restart, but then it would boot up to a black screen. Tried turning off and on, then it started turning off by itself the moment it tried to load Windows. One last thing, everytime it does a chk dsk, it gives me a bsod.

I am currently running windows on an old, slow 70gb hdd i had on an old laptop to see if i can recreate the problems on it, just to make sure it's truly an ssd problem or if it's a virus, which i really doubt because i have nothing installed besides gpu drivers, steam, discord, avg and chrome.

Any ideas? Anything would be appreciated. Thanks.

Quick edit: i forgot to add that one of the symptoms is that games start to stutter before all kind of errors start showing up.

System specs are:

Intel i5 6600k
Gigabyte 980ti
Asus z170-a atx
Kingston hyperX fury 4gb 2666 (x2)
Xfx core edition 850 psu
Ocz vector 150 240gb ssd
Wd blue 1tb 5400 rpm
Wd blie 3tb 5400 rpm
Noctis 450 case
3 140mm fans
3 120mm fans
Cooler master hyper 212 evo
 
Sort by date Sort by votes
C

CratusPlant

Prominent
Aug 8, 2017
1
0
510
Hi, if it were me, to check the fitness of the ssd I would download and burn the 'Ultimate Boot CD' from;

http://www.ultimatebootcd.com/

Obviously you would boot from this CD on your ssd system and check if your ssd has any hardware errors.
The 'Parted Magic' is the HDD utilty you need to run, if you are ready to delete all data on your ssd and reinstall windows (if you have downloaded and created a reinstall media from Microsoft and have the relevant Win7 or win 10 key).
When the Windows ultility fails to manage the hdd properly, 'Parted Magic' has never failed me. It is an invaluable tool.
 
Upvote 1 Downvote
J

JeanPi

Honorable
Jul 30, 2015
35
0
10,530


Ok, great. Will try that after work. I had already checked with Toshiba's SSD utility and it says the ssd's health is at 95%. From your knowledge, does that mean that it's impossible the ssd is bad?
 
Upvote 0 Downvote
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
Assuming you haven't as yet diagnosed and corrected the problems you've encountered...

1. Just for starters, ensure that you've tested your SSD with the OCZ SSD diagnostic program - their SSD Utility SSD Management Software. I assume you would have already done so but in case you haven't, do so.

2. Ditto for the Microsoft Windows Memory Diagnostic tool or other memory diagnostic you may use.

3. While you're at it check the CPU with the Intel Processor Diagnostic Tool.

3. We'll assume the problems you've been experiencing occur even if the ONLY DRIVE connected in the system is your SSD boot drive. If that's NOT the case, stop right here.

4. Assuming none of the above appear to be the problem...the only reasonable approach at this time is to "start over" as it were.

5. The basic approach would be along the following lines...
A. Get inside your desktop computer case (after disconnecting the A/C plug from your wall socket) and determine that the CPU, heat sink, memory modules & graphics card are all properly seated and all connections appear secure. Remove (disconnect) ALL peripheral devices including all HHD & SSD drive(s), optical drive(s), sound card, etc. Disconnect ALL storage devices, printers, and any other devices connected to the machine.

(As an aside, if it's not too onerous, it would be even better if your would remove the motherboard + components from the case and work with it outside of the case - perhaps on the cardboard case the MB was packaged in if you still have it or some other non-electric conducting surface, e.g., cardboard, wood, etc.)

B. In any event, all you'll be working with is your motherboard, processor, heat sink, RAM, graphics card, power supply, keyboard & mouse. Better yet, should your motherboard have onboard graphics capability, disconnect your graphics/video card from the system. Just ensure that following access of the BIOS/UEFI interface, if there is a BIOS setting for onboard graphics display that BIOS setting is enabled since that setting is frequently disabled as the default setting.

C. Reconnect your A/C cord and power on the system. What happens? Do you get a "normal" screen display? No error messages or strange notations from the system?

D. Can you access your BIOS/UEFI without any difficulty at this point and review the CMOS-BIOS settings? In particular, ensure that the SATA controller mode is set to AHCI (which should be the default setting). Check the hardware monitor/PC Health in the BIOS to determine that all temps are within normal range?

E. Assuming all is well at this point leave the system powered on for the next hour or so, checking to see if anything untoward shows up. Using your reset button, try powering down & up a few times to determine if there are any problems there.

F. Now you can install your graphics card in case it hasn't as yet been installed.

G. Along the way of the above steps if there's any indication of a faulty PSU, test that component with a PSU power tester (assuming you have one) or better yet, substitute a known non-defective PSU should one be available.

H. Should all appear well at this point this is an indication that there's nothing wrong with the basic components of your system. While not absolutely definitive this is so, it's a very strong indication that something else is amiss.

All this, of course, is to rule out at least to some degree) that the problem is not hardware-related insofar as the basic components currently installed in the PC.

Finally, install any BIOS update.

6. At this point install the SSD boot drive in your system and boot to the OS. Hopefully the system will boot & function problem-free. Work with the boot drive as the ONLY drive installed for some time to determine no problems exist.

7. Install one of your secondary HDDs and similarly work with the system to determine all is well.

8. Then the other HDD.

I just don't see any other practical series of troubleshooting steps at this point but perhaps you have some other ideas. In any event keep us apprised of your progress (or lack of!). Good luck!
 
Upvote 0 Downvote
J

JeanPi

Honorable
Jul 30, 2015
35
0
10,530


First and foremost, thanks for your answer. I ran the first 4 steps after a clean install on my ssd, but this time, i used the latest iso provided by the windows media creation tool. I ran the cpu tests and the windows memory diagnostics and both came out fine. So right now i'm just using the pc and re downloaded the same exact apps i had before. One thing i noticed is that i used the "dism check health" command to check for store corruption and no corruption was detected where as before, after every wipe, it would still show up as repairable. Is it possible that a corrupt windows iso was the culprit? It was installed with an usb boot disk.
 
Upvote 0 Downvote
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
While it's highly doubtful that a "corrupt" Windows 10 ISO (DVD installation media) is the source of the problem, (I'm assuming that Win 10 is the OS and you downloaded the installation media files from the Microsoft website), it might be practical to reinstall the OS, this time using a USB flash drive (Media Creation Tool) containing the Win 10 setup files just on the off-chance that was the problem or for some reason the original installation process went awry.

As a general proposition when we encounter a problem similar to yours we follow the procedure I outlined on a step-by-step basis up to step 6. It's only at this point that we would install (or reinstall, if practical) the OS (if we hadn't already discovered the component/item that was the probable cause of the problem we had been experienced). Obviously there are differences (slight or otherwise) in the nature of users' problems and one has to make allowances for them in pursuing these troubleshooting steps.
 
Upvote 0 Downvote
J

JeanPi

Honorable
Jul 30, 2015
35
0
10,530


So i was running windows with only my ssd plugged in, and left it downloading some stuff overnight and woke up to a bsod. Had toi boot from another hdd to access the log files and this came up:

Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎8/‎9/‎2017 3:55:47 AM (GMT)
Number of repair attempts: 3

Session details
---------------------------
System Disk = \Device\Harddisk1
Windows directory = D:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 94 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code = 0x0
Time taken = 1375 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Setup state check
Result: Completed successfully. Error code = 0x0
Time taken = 62 ms

Test Performed:
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code = 0x0
Time taken = 641 ms

Test Performed:
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
---------------------------
Boot critical file d:\windows\system32\drivers\vdrvroot.sys is corrupt.

Repair action: File repair
Result: Failed. Error code = 0x2
Time taken = 1265 ms

---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 78 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code = 0x0
Time taken = 1375 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Setup state check
Result: Completed successfully. Error code = 0x0
Time taken = 63 ms

Test Performed:
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code = 0x0
Time taken = 609 ms

Test Performed:
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
---------------------------
Boot critical file C:\Windows\System32\drivers\vdrvroot.sys is corrupt.

---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 78 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code = 0x0
Time taken = 5203 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Setup state check
Result: Completed successfully. Error code = 0x0
Time taken = 63 ms

Test Performed:
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code = 0x0
Time taken = 609 ms

Test Performed:
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
---------------------------
Boot critical file c:\windows\system32\drivers\vdrvroot.sys is corrupt.

Repair action: File repair
Result: Failed. Error code = 0x2
Time taken = 1297 ms

---------------------------
---------------------------


See anything there? Thanks in advance.
 
Upvote 0 Downvote
J

JeanPi

Honorable
Jul 30, 2015
35
0
10,530


I've already done about 12 fresh installs, so i'm placing my bets now on it being a faulty ssd. Memtest came out ok, CPU tests came out fine. Only thing i saw was the ssd being at 94% health instead of 100%. I will keep troubleshooting and keep you informed. Thanks for your help, much appreciated.
 
Upvote 0 Downvote
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
I can sympathize with your frustration. Perhaps it is a defective SSD although I'm really not convinced that's the problem. I take it for one reason or another you did not undertake all the steps I outlined in steps 5. through 8. above.

Anyway, please keep us informed as to what progress you make and how you (hopefully!) resolved the problem. It will be informative to us for future reference. Good luck.
 
Upvote 0 Downvote
J

JeanPi

Honorable
Jul 30, 2015
35
0
10,530


Haven't been able to due to work, so i've resorted to doing 1-4 which were the fastest ones. Hopefully tonight, i'll be able to go more in depth.
 
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