windows 8.x system process does a lot of data integrity checks in the background, it does this to repair and prevent certain types of issues that occur on your drive, these can take some time to complete and should be done as a idle time background process. I have looked at several system that were stuck at !00% disk use, each one had problems in the drive subsystems.
- drive disconnection and reconnecting over and over
- bad outdated firmware on SSD drive (drive was taking too long to complete its TRIM functions/garbage collection and windows resets the sata port after 30 seconds)
- Bad SATA port software drivers
- bad SATA port connection, wrong firmware setting in BIOS
- errors in disk cache in the electronics of the drive (often can be fixed by turning off lazy writes on the disk)
- corrupted files in the OS (run sfc.exe /scannow of detect isssue and repair)
In most systems if you see 100% disk usage you have a problem and it is not your pagefile that is causing it.
it can be caused by where the pagefile is located on the disk though., in those cases you disable the pagefile, reboot,
delete the pagefile, let the OS clean up the space then make a new page file and reboot. it is a lot faster to clean up a file system and
do data integrity checks on a lot fewer files.
overall better to fix the root cause of the issue than disabling the subsystem that are effected.
-Windows 8.x will do a lot of checks on a new drive, OEM don't properly format a drive these days, they just drop a image of the operating system on it. Windows 8.x will attempt to read and locate sectors on the drive, when it finds sectors that can be read but have read errors, it will attempt to read the data over and over to get a good copy and then relocate the data to another location on the disk. This process takes time and is started 5 mins after the system goes idle. For most people, use control panel power settings to high performances and just leave the machine on for a day or so it should just work itself out and the "problem" will go away.
-There are other things that can cause the same 100% disk use for example the system tries to guess what you want to do and will load programs into memory before you actually attempt to run them. Some files that are selected may not actually be currently loaded on your disk, they may be in the process of being downloaded or streamed. For example, you might have a game service that stores your games for you and lets you play a game while it downloads the rest of your games or parts of games in the background. If windows tries to prefetch these files into memory it will end up spinning waiting on the disk to provide the file, the disk is waiting on the network to provide the file, but the game service is loading the file very slowly in the background so it does not tie up your network bandwidth or CPU.
-there are also bugs with corrupted file systems that are pretty easy to fix with a chkdsk /f /r
- there some malware that now hide in the file system file streams
I would think that some virus scanners and malwarebytes should find these and remove them.
- I have seen issues where a the search index searches your hard drive and builds a database index
but the drive is corrupted and the search ends up having a loop so it never gets to the end of the file search,
it just keeps building a bigger and bigger index until all of your hard drive space is used up.
(just run chkdsk /f /r and delete the search index to fix)
- for most people, the problem just goes away after a few day, except on laptops that go to sleep fast.
it might take 8 hours of real time to scan and fix a disk with errors, more for a large disk. On a laptop
that goes to sleep in 15 mins after idle the OS will have only 10min to work on the task on each wake cycle.
if you really want to see what your system is doing you should get a copy of the tool rammap64.exe this is a tool written by a company called sysinternals. Microsoft bought the company and has the tools for free on its website http://technet.microsoft.com/en-us/sysin...bb84206...
You can download the file and see all the files that are open on your system. you will be surprised what is getting preloaded into memory for you. I am looking at my list now and I see programs I have not run for almost a year and they are being preloaded. The system cache manager just fills the unused ram with what it thinks I might want to run. if one of these files were located on a disk with disk errors, it would take a lot of time to load the file into memory as the system attempts to read the disk over and over each time I boot.
even if I never requested the file to be run, the disk might queued up and running full speed because of this process. it is not really a bug in the cache manager that the disk has errors and causes the disk to spin at 100%, it is disk problem that has not crashed your system yet.
There can also be other problems that will slow a disk. Errors in the electronics, bugs in the chipset drivers, even a bad cable connection. thermal expansion/contraction on a cable connection can make and break a connection several times a second causing a drive to disconnect and auto reconnect several times a second. This really can cause your drive to slow down but it still works until the drive gets disconnected for 30 seconds then you get a logged error.
The same thermal contraction can cause circuits to fail. (brittle solder joints crack and lift off the circuit board)
I have looked into 100% disk usage on solid state drives and they have all been firmware related.
The operation of solid state drives really depends on having proper time to run their clean up routines. They really suffer on laptops that try to save their power. The drives have to run their garbage collection routines and their TRIM functions. When these get blocked because firmware bugs or lack of idle time while the machine is on the drive kind of gets wedged up to the point it can not function correctly. Often you just need to power on the machine and boot into BIOS and leave the machine alone overnight. The SSD will start its firmware internal garbage collection and can move bad blocks around and do its various repairs.
SSD have very limited ability to write to the drive. Figure 2000 writes to a block and that block is dead. It really does not take long to do that amount of writes. Just look at the amount of temp files being written by a browser like chrome to get a idea.
anyway, maybe what I said will give you a idea what the problem is.