Windows 10: Chronic 100 percent disk and CPU usage on older hardware

It wasn't eMachine's drive that died as I was installing, but another higher spec'd Acer x1300 desktop,. I took that WD out of the eMachine to put into the Acer as a test and it hasn't continued with the issue. But when I imaged it over to an older IDE drive in the same eMachine it started up with the problem until I uninstalled the Mail app as several others did to solve this.

It's interesting that when moved to the Acer the eMachine's HD started Win10 apparently with some soft of built-in adjustment, while Win7 on the same HD would not start on such changed hardware, as expected. This makes me wonder if 10 has hardware adjustability built in. We know it has a much huger driverstore due to inexcusable lack of Win7 SP2, but often it is the HID and SID difference that kills starting on other hardware.

 

Are you sure the hdd died sounds roughly familiar to these reports,
https://www.tenforums.com/general-dis...lder-hdds.html

 

Mike - I followed those reports, too. But neither failed Hitachi HD is detected in BIOS or Diskpart in that or another desktop, so assume it's gone unless there is another way to try to force it to be detected.

These two HD's were bought about the same time in the Acer X1300 Slimlines and had pretty heavy usage for 7 years.

 

Boot up a live linux iso and see if they are detected.

 

From what I've read only Linux can see the drives for some people ?
Woofgang might need to be summoned *Wink

 

I can't post a direct link but posted by Beerisgood :/

 

Very confusing results. I boot from Linux Partition Wizard disk and drive is detected with files intact. Passed surface test and Rebuilt MBR. Was then able to boot into it, at least until I unplugged the other drive and installed the problem drive. It wouldn't start again. Why it required the other drive attached to even be seen I don't know. Tried different cables and SATA ports. The other drive is IDE.

Now it's playing weird games showing up in BIOS storage and boot listings as a selectable blank under whatever port I plug it into.

I'm going to try Seatools and Data Lifeguards on CD now. Hitachi DFT will not run, probably because there is no ability to toggle to IDE in BIOS on this PC.

Drive passed both short tests, Quick Wiped to see if it will detect.

Could this possibly be related to the "dirty bit" scenario caused by Fast Boot?

 

Because the drive is set not to spin on power up but to wait for a spin command to spin up you need to set the drive to spin on power up.

 

If it's the only drive plugged in then wouldn't it spin by default? How would you do this?

I've wiped with Data Lifeguard Quick wipe to see if that helps clear something in the partition table or boot sector - possibly a "dirty bit?" Then I'll try installing TP. If it takes it then I'll put the Macrium Image on here.

Other suggestions?

 

Link

 

Thanks.
*Smile

Is he saying the Permanent solution works unless Sleep is used?. If Sleep can stay then I'll run that fix and reinstall.

 

You need to run the command so you can install later and yes he is saying disable drive sleep in W10.

 

Welcome to unattended windows 10TP *Smile

 

Yeah I thought I should put my roommates off another few months but they were chomping at the bit to try 10, and were enthusiastic 7 beta testers so want to get in early. Each still has 7 in a Dual Boot but I doubt they'll go back unless there's disaster - for which there's plenty of backup images, drives and machines. Right now I'm finishing Macrium images of both of their finished Dual Boots to backup machines which will sit on the shelf.

I'm leaving Tues to travel for a month each at my other home and Hawaii so don't want to leave anything possibly unstable. I think I'll put this scuzzy drive aside until I get back so I don't get behind.

I notice the drive is labeled SCSI but has SATA connectors. I wonder if this is related.

 

Yep that feature is mandatory for SCSI arrays so as not to overload the power supply on power up..