F5F Stay Refreshed Hardware Desktop Your operating system drive is experiencing sudden shutdowns, zero performance, and an unresponsive system.

Your operating system drive is experiencing sudden shutdowns, zero performance, and an unresponsive system.

Your operating system drive is experiencing sudden shutdowns, zero performance, and an unresponsive system.

T
Tommygirl123
Junior Member
33
09-15-2025, 08:31 AM
#1
Sure thing! Here’s a rephrased version of your message:

Hey all, I really hope you can assist me in figuring out this persistent issue with my PC. It’s been causing major headaches, making the system super unreliable. Essentially, there’s a problem with the system drive—like it’s being hit repeatedly.

Details:
- Operating System: Windows 11 Pro (just reinstalled cleanly)
- CPU: Intel Core i5-12400
- Motherboard: Gigabyte H610M
- RAM: 19.78GB (mixed setup: 16GB G.Skill + 4GB “Golden Empire”)
- GPU: NVIDIA RTX 2060
- Storage: WD Green 2.5" 240GB SSD (no RAM), plus a 1TB Seagate HDD and a 2TB Western Digital HDD

What’s happening in real time? Randomly, without warning, the drive fails—whether I’m playing games, browsing, or just sitting still. The C: drive is always at maximum activity, but it’s practically not reading anything. It feels like the OS is struggling to function properly. Even when I try to open files or folders, it takes ages and sometimes feels like moving through thick digital sludge. Clicks are slow, and launching programs is a nightmare. Occasionally, I can drag my mouse around, but everything slows down drastically.

The problem isn’t a complete crash; it’s more of a slowdown. The system still runs, but everything feels sluggish and unresponsive. It’s like the drive is stuck in a kind of digital limbo.

What I’ve tried so far:
- Ran `sfc /scannow` and `chkdsk`, both cleaned up fine.
- Turned off Superfetch (SysMain), but it didn’t fix anything.
- The drive is up to date, so it’s probably not a simple software glitch.

My budget is tight—no money for a new SSD right now. I’m stuck with what I have. My main concern is stability over speed. If I switch the OS to one of my existing HDDs, I’ll get a more reliable setup. But I need advice on which one to pick based on S.M.A.R.T. data.

What are the two drives?
1. WD Green 2.5" 240GB SSD (current) – decent but has some red flags.
2. Seagate 1TB HDD – clean records, no issues.

My main questions:
- Which one should I choose for reliability?
- Should I clone my current setup or do a fresh install on the HDD?
- Any tips to make an HDD-based OS more stable right now?

Thanks for going through this—this is really frustrating!
T
Tommygirl123
09-15-2025, 08:31 AM #1

Sure thing! Here’s a rephrased version of your message:

Hey all, I really hope you can assist me in figuring out this persistent issue with my PC. It’s been causing major headaches, making the system super unreliable. Essentially, there’s a problem with the system drive—like it’s being hit repeatedly.

Details:
- Operating System: Windows 11 Pro (just reinstalled cleanly)
- CPU: Intel Core i5-12400
- Motherboard: Gigabyte H610M
- RAM: 19.78GB (mixed setup: 16GB G.Skill + 4GB “Golden Empire”)
- GPU: NVIDIA RTX 2060
- Storage: WD Green 2.5" 240GB SSD (no RAM), plus a 1TB Seagate HDD and a 2TB Western Digital HDD

What’s happening in real time? Randomly, without warning, the drive fails—whether I’m playing games, browsing, or just sitting still. The C: drive is always at maximum activity, but it’s practically not reading anything. It feels like the OS is struggling to function properly. Even when I try to open files or folders, it takes ages and sometimes feels like moving through thick digital sludge. Clicks are slow, and launching programs is a nightmare. Occasionally, I can drag my mouse around, but everything slows down drastically.

The problem isn’t a complete crash; it’s more of a slowdown. The system still runs, but everything feels sluggish and unresponsive. It’s like the drive is stuck in a kind of digital limbo.

What I’ve tried so far:
- Ran `sfc /scannow` and `chkdsk`, both cleaned up fine.
- Turned off Superfetch (SysMain), but it didn’t fix anything.
- The drive is up to date, so it’s probably not a simple software glitch.

My budget is tight—no money for a new SSD right now. I’m stuck with what I have. My main concern is stability over speed. If I switch the OS to one of my existing HDDs, I’ll get a more reliable setup. But I need advice on which one to pick based on S.M.A.R.T. data.

What are the two drives?
1. WD Green 2.5" 240GB SSD (current) – decent but has some red flags.
2. Seagate 1TB HDD – clean records, no issues.

My main questions:
- Which one should I choose for reliability?
- Should I clone my current setup or do a fresh install on the HDD?
- Any tips to make an HDD-based OS more stable right now?

Thanks for going through this—this is really frustrating!

L
lemons9
Member
56
09-15-2025, 08:31 AM
#2
I’d choose the slower 5400 WD because it’s likely just a temporary fix until you install an SSD.
A YouTube tutorial demonstrated several free tools for migrating OSes; DiskGenius is one they mentioned and performed well.
Turn off Bitlocker if enabled, disable search indexing, and turn off power-saving settings on the HDD to prevent constant spinning. Consider using KeepAliveHD instead.
Create a text file and remove it every couple of minutes—research may be needed if the HDD firmware has its own inactivity timer.
You could also strip out background applications that rely heavily on the HDD. I haven’t tried Win Aero Tweaker, but JayTwocents posted a short video about it.
Sal
L
lemons9
09-15-2025, 08:31 AM #2

I’d choose the slower 5400 WD because it’s likely just a temporary fix until you install an SSD.
A YouTube tutorial demonstrated several free tools for migrating OSes; DiskGenius is one they mentioned and performed well.
Turn off Bitlocker if enabled, disable search indexing, and turn off power-saving settings on the HDD to prevent constant spinning. Consider using KeepAliveHD instead.
Create a text file and remove it every couple of minutes—research may be needed if the HDD firmware has its own inactivity timer.
You could also strip out background applications that rely heavily on the HDD. I haven’t tried Win Aero Tweaker, but JayTwocents posted a short video about it.
Sal

K
Kitten645321
Member
181
09-15-2025, 08:31 AM
#3
These SSD flash cells may lose charge and struggle to read properly, causing delays or data loss if ignored. Consider imaging your device; performing a secure erase and re-loading could assist. It would add another data point if successful.
K
Kitten645321
09-15-2025, 08:31 AM #3

These SSD flash cells may lose charge and struggle to read properly, causing delays or data loss if ignored. Consider imaging your device; performing a secure erase and re-loading could assist. It would add another data point if successful.

I
imnotben
Member
67
09-15-2025, 08:31 AM
#4
It's important to note that these terms describe opposing conditions, making it impossible for them to coexist simultaneously.
I
imnotben
09-15-2025, 08:31 AM #4

It's important to note that these terms describe opposing conditions, making it impossible for them to coexist simultaneously.

P
PigiGo
Junior Member
4
09-15-2025, 08:31 AM
#5
Here’s a rephrased version of your detailed account:

Your prompt was incredibly valuable and insightful. The explanation you provided about SMR versus CMR drives perfectly captures the nuanced nature of this issue, offering a clear direction for addressing it. You also highlighted the need to examine my SSD more closely. You’re correct that the challenge goes beyond what I initially described—it’s much more intricate and specific. As requested, I’ve compiled a thorough overview of the core issue and the extensive troubleshooting process I’ve undertaken. This detailed record may help clarify the unusual behavior you’re encountering. I’m hoping this broader perspective can shed light on what might be happening with my drive.

The central concern: A distinct pattern emerges
When things slow down significantly, especially after a long idle period, the situation becomes clear. The drive behaves unusually during cold starts, entering a severely limited state where performance drops to almost nothing for 2 to 4 minutes. After that brief lull, it briefly returns to normal, only to reset when I trigger any substantial activity. This cycle repeats, making the problem persistent and frustrating.

The temporary pause: Once the system cools down, disk operations drop sharply, allowing the computer to respond again. But any sudden load—like opening a large folder or launching an app—can instantly restart the cycle.

The persistent block: At times, the drive remains stuck in this high-activity mode for several minutes, sometimes never fully releasing. This often necessitates a full system reboot to resolve.

In summary, the situation appears to stem from a combination of factors rather than a single cause. The low free space on my SSD seems to be playing a key role, as it severely restricts the drive’s ability to function efficiently. While I’ve checked software updates, driver versions, and various system settings, the recurring pattern suggests a hardware limitation is at play.

I’m eager to hear your thoughts: Does this align more with a drive that’s being pushed to its limits due to insufficient space, or does the ongoing strain point toward an imminent hardware failure of the controller or NAND cells? Your expert guidance has been invaluable in navigating this complex scenario.
P
PigiGo
09-15-2025, 08:31 AM #5

Here’s a rephrased version of your detailed account:

Your prompt was incredibly valuable and insightful. The explanation you provided about SMR versus CMR drives perfectly captures the nuanced nature of this issue, offering a clear direction for addressing it. You also highlighted the need to examine my SSD more closely. You’re correct that the challenge goes beyond what I initially described—it’s much more intricate and specific. As requested, I’ve compiled a thorough overview of the core issue and the extensive troubleshooting process I’ve undertaken. This detailed record may help clarify the unusual behavior you’re encountering. I’m hoping this broader perspective can shed light on what might be happening with my drive.

The central concern: A distinct pattern emerges
When things slow down significantly, especially after a long idle period, the situation becomes clear. The drive behaves unusually during cold starts, entering a severely limited state where performance drops to almost nothing for 2 to 4 minutes. After that brief lull, it briefly returns to normal, only to reset when I trigger any substantial activity. This cycle repeats, making the problem persistent and frustrating.

The temporary pause: Once the system cools down, disk operations drop sharply, allowing the computer to respond again. But any sudden load—like opening a large folder or launching an app—can instantly restart the cycle.

The persistent block: At times, the drive remains stuck in this high-activity mode for several minutes, sometimes never fully releasing. This often necessitates a full system reboot to resolve.

In summary, the situation appears to stem from a combination of factors rather than a single cause. The low free space on my SSD seems to be playing a key role, as it severely restricts the drive’s ability to function efficiently. While I’ve checked software updates, driver versions, and various system settings, the recurring pattern suggests a hardware limitation is at play.

I’m eager to hear your thoughts: Does this align more with a drive that’s being pushed to its limits due to insufficient space, or does the ongoing strain point toward an imminent hardware failure of the controller or NAND cells? Your expert guidance has been invaluable in navigating this complex scenario.

M
MiguelZipfel
Junior Member
40
09-15-2025, 08:31 AM
#6
Your message remains the same. The core idea hasn't shifted. Free space shouldn't impact the situation because it's the unchanged data—like the operating system and programs—that causes the slow startup.
M
MiguelZipfel
09-15-2025, 08:31 AM #6

Your message remains the same. The core idea hasn't shifted. Free space shouldn't impact the situation because it's the unchanged data—like the operating system and programs—that causes the slow startup.