BSOD when taking a system image of C: OS

I had high hopes tonight having freed up a lot of space on the HD (20% now free) and uninstalling literally the only new software in months (other than iTunes updates and windows updates) but it happened again at 95% mark. I guess thinking back I've taken successful images before and I've teetered around the 10% mark in free space for a good couple years. But it now still fails with 20% left.

It just seems weird that with less to image it still failed at the same 95% point if that makes sense. If before it fails at 95% when 609 out of 679 gb is used, then I would expect it to fail at a latter percentage if 545 out of 679 gb used. I could be talking twoddle but it indicates me it's not failing at the exact same point on the HD during the image because 95% with less space used would be at a different point/stage. So it makes think software/the OS itself is to blame. A bad Windows update at some point? But isolating these would be difficult given the amount of updates since the last successful image in early May 2015 (I let it slide for a long time). Maybe a recommended disk defragmenter to try and order the data in a better way on the HD (although I believe Windows does this automatically and in the screenshot it's only 3%).

It still baffles me why in normal use the OS is solid as a rock. Anyway I just thought I'd share my findings. If it helps at all here is the latest BSOD screenshot and disk management. Unfortunately no minidump as that still fails to initialise.

Cheers,
Wayne

Hello axe0,
I'm not a BSOD expert, but i noticed the memory dumps failed with different status codes in the previous BSOD screen prints.
Do you think RAM tests should be run to rule out bad memory ?
tyia, David

From Post #21:
Attachment 381415

From Post #7:
Attachment 381416

Hi, thanks for the continued interest. I will try and do the pics in next few days. I just need to get suitable tools and spare time before opening her up. I'll snap away as best I can, have a rough idea what to picture but am not really geared up on the internals.

I did some googling and tried disabling the page file this evening and then running disk defragmenter with the intention of then re enabling the paging file back to system managed. It's only because that was a success story for somebody else. Alas it froze on pass 6 and BSOD mentioning a fatal error but no codes this time. Then a ran memory diagnostics tool in Windows (well it restarted and then ran them outside Windows) but no errors were detected.

I intend to run Seatools for DOS Long Generic Test either tomorrow or the following evening as instructed

Cheers, Wayne

fyi, Your SF specs show Desktop, but this is a laptop you are using, right ?
I don't know if that matters for the pics axe0 wants.

If you never opened the laptop, you can search for videos on your specific laptop model.
Or check the manufacturer website to see if they have a service manual available.

Oops, your right. I've updated that now. Thanks I'll look into the info. I guess I'll do that whilst the Seagate long generic test runs.

Sorry I mislead you. Have to admit I'm losing hope of it turning out ok. I will do the sea tools in next couple days but i might have to replace it. It's out of warranty by a couple years and I guess the cost of getting HD plus someone to replace it might not be economical given the age of the entire thing. Under warranty it had two separate gpu failures too which dell fixed, so maybe the HD gets changed it'll only be a matter of time before something else goes