Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Harddisk woes

Go to solution Solved by 133DK,
4 hours ago, Kilrah said:

What about the actually readable description at the bottom?

There was none, just the sad smiley face, a message that a problem had occurred and restart was required, and that error code along side a QR code that just leads to a generic Microsoft webpage..

 

4 hours ago, Kilrah said:

Don't really thing how that could be unless you had done a weird config e.g. with storage spaces or RAID, or had somehow installed critical system things or autolaunching programs on that drive...

No raid, no auto launching programs from that disk..

 

I have just reinstalled Windows, I saw no other way

 

Thanks for all the help!

Having trouble with an old HDD.

I have 4 drives connected to my PC, 2 m.2s and 2 HDDs, all was fine and dandy (for years) until yesterday when I powered it on and windows did it's scan and repair thing on drive F, the oldest of the two HDDs.

When booting up drive F shows up in explorer, but any attempt to interact with the drive causes explorer to either prompt that the drive cannot be accessed, or explorer restarts entirely.

 

So far I have tried disconnecting the other HDD and using the cables from that. Computer does the exact same thing. Seemingly not a cable issue.

 

However, as I had resigned myself to having lost an old drive out of the blue, a new problem arises.

Disconnecting the failing drive. This causes Windows to BSOD on startup.

Disconnecting both the failing drive and the other HDD does the same.

 

So now I am stuck with a failing drive I for some reason can't pull from my system. Any help would be appreciated!

Link to post
Share on other sites
2 minutes ago, 133DK said:

Having trouble with an old HDD.

I have 4 drives connected to my PC, 2 m.2s and 2 HDDs, all was fine and dandy (for years) until yesterday when I powered it on and windows did it's scan and repair thing on drive F, the oldest of the two HDDs.

When booting up drive F shows up in explorer, but any attempt to interact with the drive causes explorer to either prompt that the drive cannot be accessed, or explorer restarts entirely.

 

So far I have tried disconnecting the other HDD and using the cables from that. Computer does the exact same thing. Seemingly not a cable issue.

 

However, as I had resigned myself to having lost an old drive out of the blue, a new problem arises.

Disconnecting the failing drive. This causes Windows to BSOD on startup.

Disconnecting both the failing drive and the other HDD does the same.

 

So now I am stuck with a failing drive I for some reason can't pull from my system. Any help would be appreciated!

This is cost for installing windows with HDD's installed in the system. I would just backup while HDD is installed and then reinstall windows. 

I would also try using some other sata ports. Many boards have an extra sata chip.

CPU: i7 9700K@5ghz all core (silence + summer)

cache x47, AVX offset 0

Motherboard: Asus Maximus XI Hero

RAM: Patriot Viper Steel 2x8gb@3733mhz @jedec cl15

PSU: EVGA SuperNova 750 G3

Mon:  LG 27GL850-B, 144Hz Nano IPS - G-Sync compatible/Freesync

GPU: EVGA 1080ti SC Black Edition w/ G12 bracket

Sound: Odac + Fiio E09K

Case: Fractal Design R6 TG Blackout

Storage: MP510 960gb and 860 Evo 500gb

Cooling: CPU: Kraken X62 - GPU: Kraken X42(RIP) -> X53 (From RMA)

Link to post
Share on other sites
58 minutes ago, 133DK said:

Any help would be appreciated!

When you install Windows from now on, disconnect all other drives. Windows a dumb in a lot of ways, its probably put boot files on the hard drive that is failing. Meaning without that drive connected, those files are gone. Ive seen this happen on a Windows 7 install once upon a time. Which is why I never have other drives hooked up when installing Windows. 

I just want to sit back and watch the world burn. 

Link to post
Share on other sites

Normally when it's the case it wouldn't get to the point where it can generate a BSOD.

 

What's the error on that BSOD?

Can you try the drive on another system? Might be the mobo failing instead.

F@H
Desktop: i7-5960X 4.4GHz, Noctua NH-D14, ASUS Rampage V, 32GB, RTX3080, 2TB SX8200Pro, 2x16TB Ironwolf RAID0, Corsair HX1200, Thermaltake Overseer RX1, Samsung 4K curved 49" TV, 23" secondary, Mountain Everest Max

Mobile SFF rig: i9-9900K, Noctua NH-L9i, Asrock Z390 Phantom ITX-AC, 32GB, GTX1070, 2x1TB SX8200Pro RAID0, 2x5TB 2.5" HDD RAID0, Athena 500W Flex (Noctua fan), Custom 4.7l 3D printed case

 

Dell XPS 2 in 1 2019, 32GB, 1TB, 4K

 

GPD Win 2

Link to post
Share on other sites
32 minutes ago, Kilrah said:

 

What's the error on that BSOD?

Can you try the drive on another system? Might be the mobo failing instead.

0xc000021a

I don't think it's the mobo, as the other HDD works with both headers, as long as the failing harddisk is also plugged in

Link to post
Share on other sites
52 minutes ago, 133DK said:

0xc000021a

What about the actually readable description at the bottom?

 

53 minutes ago, 133DK said:

I don't think it's the mobo, as the other HDD works with both headers, as long as the failing harddisk is also plugged in

Don't really thing how that could be unless you had done a weird config e.g. with storage spaces or RAID, or had somehow installed critical system things or autolaunching programs on that drive...

F@H
Desktop: i7-5960X 4.4GHz, Noctua NH-D14, ASUS Rampage V, 32GB, RTX3080, 2TB SX8200Pro, 2x16TB Ironwolf RAID0, Corsair HX1200, Thermaltake Overseer RX1, Samsung 4K curved 49" TV, 23" secondary, Mountain Everest Max

Mobile SFF rig: i9-9900K, Noctua NH-L9i, Asrock Z390 Phantom ITX-AC, 32GB, GTX1070, 2x1TB SX8200Pro RAID0, 2x5TB 2.5" HDD RAID0, Athena 500W Flex (Noctua fan), Custom 4.7l 3D printed case

 

Dell XPS 2 in 1 2019, 32GB, 1TB, 4K

 

GPD Win 2

Link to post
Share on other sites
4 hours ago, Kilrah said:

What about the actually readable description at the bottom?

There was none, just the sad smiley face, a message that a problem had occurred and restart was required, and that error code along side a QR code that just leads to a generic Microsoft webpage..

 

4 hours ago, Kilrah said:

Don't really thing how that could be unless you had done a weird config e.g. with storage spaces or RAID, or had somehow installed critical system things or autolaunching programs on that drive...

No raid, no auto launching programs from that disk..

 

I have just reinstalled Windows, I saw no other way

 

Thanks for all the help!

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×