Solved win 7 pro freezes then BSOD status 0xc0000010

[thescruff]

Hi guys and gals, I'll keep it short in case I get cut off again.

Ok win 7 pro, run as normal up to an hour before it freezes the crashes.

I put most of the computer info in my profile when I registered via the other computer.

technical information.

Stop: 0x000000F4 (0x0000000000000003, 0xFFFFFA800B14A740, 0xFFFFFA800B14AA20, 0xFFFFF80003398510)

Physical memory dump failed with status 0c0000010.

Ask any question and information please, I can stick it in word then copy and paste in this thread to save time between crashes.

Pss, zip attached, I have also uninstalled avast and installed ms essentials as recommended by you good people.

 

[thescruff]

Any clues good people.

 

[Anthony]

No dump files?

 

[Anthony]

Can you please Uninstall this Program Advanced System Care 4 While we Trouble Shoot your problem

Thanks

 

[thescruff]

Hi, Thanks you for any guidance.

No, In SFDiagnostic under minidump it says "No dump found"

I uninstalled 4 and upgraded to 5, would you like that uninstalled and a new log

 

[Anthony]

Check System Dump Settings:

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. In the Write debugging information list, click Small memory dump (64k).

Wait for BSOD then post New SFDiagnostic Files



Thanks

 

[thescruff]

Hi, have uninstalled advanced system care, and added an updated zip.

Additional info if it helps.

A couple of times it crashed last night when I pressed the re-set button "drive 00" was missing and I had to boot from the recovery disk.

Just read your last post the zip is before that, I'll tun through the test and post again.

 

[Anthony]

Can you Scan your System Using this: http://www.filehippo.com/download_malwarebytes_anti_malware/

 

[thescruff]

Full scan running as requested.

Having problems finding the small memory dump (64k)

There's a small memory dump (254mb) or memory dump it is set on the later, shall I change it to the 254mb

The computer just froze lol, I have to re-boot and start again.

 

[Anthony]

Small memory dump (64k)

 

[thescruff]

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.

 

[thescruff]

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.

 

[Anthony]

Sorry 256kb is right

 

[thescruff]

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.

 

[thescruff]

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

 

[thescruff]

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

All clear.

 

[thescruff]

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

 

[thescruff]

http://www.sevenforums.com/hardware-devices/248106-crucial-m4-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.