|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
January 9th 17, 07:39 AM
posted to alt.windows7.general
|
|||
|
|||
Defraggle Rock
I am using W10. Yesterday I tried to defrag and it got stuck at 85%
defragmented and crashed the machine. When I switched it back on it had not defragged at all. Any ideas? -- Myth, after all, is what we believe naturally. History is what we must painfully learn and struggle to remember. -Albert Goldman 
|
| Ads |
|
#2
January 9th 17, 08:34 AM
posted to alt.windows7.general
|
|||
|
|||
|
Defraggle Rock
En el artículo , Martin Edwards
escribió: I am using W10. so why are you asking this in a Win7 newsgroup? -- (\_/) (='.'=) systemd: the Linux version of Windows 10 (")_(")
|
|
#3
January 9th 17, 08:48 AM
posted to alt.windows7.general
|
|||
|
|||
|
Defraggle Rock
Martin Edwards wrote:
I am using W10. Yesterday I tried to defrag and it got stuck at 85% defragmented and crashed the machine. When I switched it back on it had not defragged at all. Any ideas? Check Event Viewer, see if there is anything "interesting" logged at that instant in time. Check the SMART statistics for the hard drive. See if the drive is sick, and it actually died on a delayed write failure due to bad sectors. The defragmenter API is power-safe, so an instant crash like that, the file system should survive. You may still want to run CHKDSK /f C: on it to fix any problems. I could find some other reports, which involved computers with incorrect CPU cooling, and the CPU loading from the defrag run tipped them over. You might also want to share your "crash history" with us. If the computer has been crashing at other times, then that's important. And if the machine has been well behaved (can run a stress tester without tipping over), that's important too. Paul
|
|
#4
January 9th 17, 02:55 PM
posted to alt.windows7.general
|
|||
|
|||
|
Defraggle Rock
On Mon, 9 Jan 2017 07:39:43 +0000, Martin Edwards wrote:
I am using W10. Yesterday I tried to defrag and it got stuck at 85% defragmented and crashed the machine. When I switched it back on it had not defragged at all. Any ideas? I'm guessing that it's a hardware storage issue. It could be either worn out disk, or loosened data cable due to heat.
|
|
#5
January 10th 17, 07:46 AM
posted to alt.windows7.general
|
|||
|
|||
|
Defraggle Rock
On 1/9/2017 2:55 PM, JJ wrote:
On Mon, 9 Jan 2017 07:39:43 +0000, Martin Edwards wrote: I am using W10. Yesterday I tried to defrag and it got stuck at 85% defragmented and crashed the machine. When I switched it back on it had not defragged at all. Any ideas? I'm guessing that it's a hardware storage issue. It could be either worn out disk, or loosened data cable due to heat. Thanks to all who replied. -- Myth, after all, is what we believe naturally. History is what we must painfully learn and struggle to remember. -Albert Goldman
|
|
#6
January 11th 17, 07:50 AM
posted to alt.windows7.general
|
|||
|
|||
|
Defraggle Rock
On 1/9/2017 7:39 AM, Martin Edwards wrote:
I am using W10. Yesterday I tried to defrag and it got stuck at 85% defragmented and crashed the machine. When I switched it back on it had not defragged at all. Any ideas? It worked okay yesterday. Must have been a temporary fault. -- Myth, after all, is what we believe naturally. History is what we must painfully learn and struggle to remember. -Albert Goldman
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Linear Mode
