ChuckBradley
New Member
- Joined
- Aug 6, 2016
- Messages
- 6
- Thread Author
- #1
My wife has an HP laptop, model 14-1023cl if I can read the faded label correctly. If runs Windows 8 with one of the add-ons to make it look more like earlier versions. Maybe 8.1 instead? Sorry, I don't know. Avast runs daily. A few days ago it was very slow, and froze with a blank dull blue screen, not the BSOD. Rebooting was very slow, but I finally got into process manager and discovered MS had removed all the useful information, or I could not find it. I tried to run AVAST. After about 24 hours, it thought it was 18% done. The next time I looked, the system had frozen again.
I removed the disk and plugged it into a USB port on another computer, through an adapter I have. Windows Explorer does not see the disk. Avast does not see the disk. MBAM sees the disk, scans it in just a few minutes, much faster than usual, and reports no problems. Device manager sees the disk and reports it as empty. HDtune sees the disk and reports all the chunks are bad. A chunk is a bunch of sectors that depends on the capacity of the disk.
I expect this problem is not Microsoft's fault. Agreed?
I have never seen a disk go this completely bad or this quickly bad. Do you think it is safe to put a new disk in the computer? Or could a hardware fault in the system be causing the disk failure?
I removed the disk and plugged it into a USB port on another computer, through an adapter I have. Windows Explorer does not see the disk. Avast does not see the disk. MBAM sees the disk, scans it in just a few minutes, much faster than usual, and reports no problems. Device manager sees the disk and reports it as empty. HDtune sees the disk and reports all the chunks are bad. A chunk is a bunch of sectors that depends on the capacity of the disk.
I expect this problem is not Microsoft's fault. Agreed?
I have never seen a disk go this completely bad or this quickly bad. Do you think it is safe to put a new disk in the computer? Or could a hardware fault in the system be causing the disk failure?