BSOD again. Bugcheck 0xF4 Unknown Critical Object.

Attachment 200995Once again I humbly approach the alter of debuggers.


BSOD have begun again at random times. I've run Malewarebytes and found nothing.

Whocrashed doesn't help much:

crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800F565B30, 0xFFFFFA800F565E10, 0xFFFFF800073CE8B0)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown CRITICAL_OBJECT_TERMINATION

My event viewer hasn't pointed me at anything either.

The only recent change was the installation of Nvidia 295.73 driver. It wasn't a pretty process getting the driver in.. it didn't go willingly.



windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17155633152 total
VM: 2147352576, free: 1857101824

No DMP files included in upload. Please try this method.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

I get this..when I try to attach the dmp file.

Your submission could not be processed because a security token was missing.

If this occurred unexpectedly, please inform the administrator and describe the action you performed before you received this error.

Gromit1710 said:

I get this..when I try to attach the dmp file.

Your submission could not be processed because a security token was missing.

If this occurred unexpectedly, please inform the administrator and describe the action you performed before you received this error.

Did you zip (compress) it?

zigzag3143 said:

Gromit1710 said:

I get this..when I try to attach the dmp file.

Your submission could not be processed because a security token was missing.

If this occurred unexpectedly, please inform the administrator and describe the action you performed before you received this error.

Did you zip (compress) it?

yes, unfortunately.

I must apologize for the confusion..

I had set my VM Pagefile size to 0 on the SSD OS C: drive.

This had the unintended effect of preventing minidumps from being created.

Alas.. I have no minidump to share so I will create a new thread once I have it all together this time. I've enabled pagefile sizing on the SSD drive again so I should have a minidump next time.

Sorry about that.