Nothing responding on pc

agrinnall

Is the scan in a folder (mine go into Documents | My Scans | yyyy-mm)? If so are there any other scans in that folder? If not, try deleting the folder. If there are, copy the other scans to another location then delete the folder.

Cross posted - glad to hear it's resolved now.

charlies_mum

Spoke too soon. Computer is running really slowly, so I am running Malwarebytes and it's working on the file system Objects, but it's been stuck on object 41482 for more than five minutes

Gave up on the Malwarebytes as it hadn't moved for over 10 minutes. I have tried running a full scan on McAfee, but it crashed after almost an hour at 31% complete with the error message "the instruction at 0x0000000076CD8F45 referenced memory at 0x000007FEEB25D090. The required data was not placed into memory because of an I/O error status of 0xc0000185. Click on Ok to terminate the program"

Is is a trip to the repair shop ?

Cycrow

It sounds very much like your hard drive is failing.

The freezing would be happening when it attempts to read the damaged part of the drive but cant.

which is also why the scanners are having problems.

you could try a disk check including a surface scan

Fightsback

Cycrow wrote: »

It sounds very much like your hard drive is failing.

The freezing would be happening when it attempts to read the damaged part of the drive but cant.

which is also why the scanners are having problems.

you could try a disk check including a surface scan

Does sound like it, back up your data ASAP.

Ed_Jogg

Agreed. This really does sound like a failing hard drive.
(I should know -- now on my fourth on this PC!)

The kind of 'stuck' behaviour could be that a programme tries to read from a bad disk sector, fails, and either keeps retrying or doesn't know how to continue because the software hasn't allowed for that problem.

Back up your data ASAP and start working out how you will replace the drive (who, where, etc).
Don't panic if it stops booting -- the disk may still be readable.
(My first failing disk could not be read by Windows, but an Ubuntu boot disk was less fussy and allowed me to recover everything important.)

And in response to your original post, the scanned documents may have been written to part of the disk that has gone bad, so accessing them could fail in an unpredictable manner.