win 7 pro freezes then BSOD status 0xc0000010

Scans about half way. scans running really slow to normal.

I have a kernel memory dump which it is set on, or Small memory dump (256mb) cant find 64k.

Hi, no small memory dump (64k)

Under advanced system setting > startup and recovery > settings, I have two choices.

Kernel memory dump which it was set on.

And small memory dump (256kb) which I have changed it too.

Computer just froze again.

I'll have to do the 3 drives separately.

Thank you, Really appreciate your help.

Scan C & E complete and clear, just started the raid drive D.

Small memory dump is set at 256kb so when I get the BSOD I'll post an undated zip.

Hi,

Please find latest Zip after BSOD.

Different technical stuff on the screen this time.

Technical information.

Stop: 0x0000007A (0FFFFF6FC400039D0, 0XFFFFFFFFC0000056,
0X00000001C3076860, OXFFFFF8800173A944)

ntfs sys-address FFFFF8800173A944 base at FFFFF880164D000,
Datestamp 4D79997B

Finally got the Mbam to complete by moving a load of stuff to drive E.

All clear.

Notice the clock stops prior to it freezing and subsequent crash.

If I press the re-set button on the computer when it freezes and prior to the crash, when it re-boots the 00 drive is missing and I have to power down or use the recovery disk. Don't if that's any help or not

https://www.sevenforums.com/hardware-...ssd-2-5-a.html

Downloaded from their site Crucial.com Product Downloads - Firmware Updates

A friend found this in the M4 firmware release notes:

Correct a condition where an incorrect response to a SMART counter will cause the m4 drive to become unresponsive after 5184 hours of Power-on time. The drive will recover after a power cycle, however, this failure will repeat once per hour after reaching this point. The condition will allow the end user to successfully update firmware, and poses no risk to user or system data stored on the drive.
This firmware update is STRONGLY RECOMMENDED for drives in the field. Although the failure mode due to the SMART Power On Hours counter poses no risk to saved user data, the failure mode can become repetitive, and pose a nuisance to the end user. If the end user has not yet observed this failure mode, this update is required to prevent it from happening.

A big thank you to Anthony, for sending me in the right direction.