Random BSOD 0x0F4 and 0x07A with memory dump failure 0xC0000010

Hello and thanks for the welcome!

Yes, I know it does not include a dump and that's because one is not being made when crashes occur.

I followed the instructions in that thread and used the SF Diagnostics Tool late last night, but as I wrote in the original post every time I get a BSOD it states “memory dump failed status 0xC0000010” at the end of the blue screen, which I assume is the reason for dumps not being made.

I've checked the minidump folder in \windows, and it's empty, I've searched for any .dmp file on the hard drive and it comes up with nothing.

I've also triple checked and verified that all of the settings are correct to record dumps and I still get nothing.

I think this issue of not getting dumps is actually a bigger part of the problem, but I'm not sure of what else can be done or to do.

On a side note I decided to perform a “clean startup” and the systems been running for about two hours with no problem, but again I've had this happen before where it's fine for some time, even a couple days, then suddenly crash several times within an hour.

Nevertheless I'll uninstall Avast and install MSE.

If there's any other thoughts or information that can be found in my zip or about not getting dumps please let me know.

Thanks again!

Thanks again, but I've already done that and verified the settings multiple times.

Unless I shouldn't be using “Small memory dump (256 KB)”, then which setting should I use?

Craig

1. Go to Advance System Setting
2. Under Performance .. click on setting ...
3. Go to Advanced Tab and then under virtual memory click change
4. check "Automatically Manage paging file size for all drives"..... click Ok and ok
5. and if asked to restart do so....

Now you should be able to create a minidump..

Craig

Since you are using an SSD.... do remember to set your paging file to another HDD once we finish with resolving this problem.....It would decrease the life of the SSD on the long run

Hello and thanks for the input!

I had looked into the virtual memory/paging file when this issue originally started and all settings seemed to already be correct.

It is checked to “Automatically manage paging file size for all drives” and “system managed size”.

Two notes just to make sure of though, for now there should only be a paging file for the OS Drive and not one for each of the other Drives, correct?

And with it being “system managed size” is shows:

Minimum allowed: 16 MB
Recommended: 9106 MB
Currently allocated: 6071 MB

Does that all seem correct or should I set a “custom size”?

And yes I did look into “moving” the paging file to another HDD when I had originally installed the SSD, but found some conflicting information at the time so I decided to leave it be.

I'll look into it again when this is all figured out though, I'm sure a lot has changed in the last year or two .

Craig In HD said:

Two notes just to make sure of though, for now there should only be a paging file for the OS Drive and not one for each of the other Drives, correct?

And with it being “system managed size” is shows:

Minimum allowed: 16 MB
Recommended: 9106 MB
Currently allocated: 6071 MB

Does that all seem correct or should I set a “custom size”?

Yes that is correct

And yes I did look into “moving” the paging file to another HDD when I had originally installed the SSD, but found some conflicting information at the time so I decided to leave it be.

I'll look into it again when this is all figured out though, I'm sure a lot has changed in the last year or two .

Yes we can look at them at a later stage....

Ok.... from the looks of it... here are some possibilities for dump not working

1. The error code 0XC0000010 means (STATUS_INVALID_DEVICE_REQUEST) is caused when windows cannot dump the files to the storage device and usually the storage controller driver is corrupted in such cases.. Now you need to update the chipset drivers as well as the SSD firmware which for you SSD is at 1.7 .. to resolve this...
   
2. The other possibility could very well be due known bug in Windows 7 SP1 for which the hotfix is available as well

Secondly a quick glance at the evenlogs looks like the last Bluescreen was caused on 7th of June 2012 and all the bluescreen dating way back to 2011 was all related to

Bugcheck 0x116 : VIDEO_TDR_ERROR caused by your graphics driver...nvlddmkm.sys.. Try updating the graphics to the latest from here

This could very well be the cause now as well.....no sure until we have the dumps to confirm it

And stop using drivermax to update your drivers !!


Let me know how it goes

Okay great, thanks for the info!

I had looked into updating most of the drivers when this originally started happening, but had trouble finding one for the chipset. I'll look again though.

I also looked into the SSD firmware update and actually downloaded it yesterday, but didn't install it, so I'll do it now.

The errors related to the graphics (nvidia drivers) I believe were due to the card not seating correctly, but that was fixed at the time (back in June), and already have the drivers up-to-date with the most current ones. Also, this had all happened before the current string of issues and BSOD crashes.

Another odd thing is that you say according to the log my most recent BSOD was on June 7th 2012. I've had at least 4-5 BSOD crashes happen yesterday, not to mention at least a couple dozen others from the last few weeks. What could be the reason for that, I guess since dumps aren't being made?

And yes I know drivermax is probably not the best, but I really only use the program to see what it says is available for updating, then search for it from the manufacture, and very, very, rarely use it to install drivers (maybe once or twice). This is also the reason I haven't updated the chipset driver yet .

So I'll do these updates and post what happens. Thanks again!