Win 7 NT Kernel & System ntoskrnl.exe BSOD CRITICAL_OBJECT_TERMINATION

[ladylunnett]

Win 7 NT Kernel & System ntoskrnl.exe BSOD CRITICAL_OBJECT_TERMINATION

I've been through many of the threads here in hopes of finding a solution to the BSOD's I've had the past couple of weeks. My close friend built me my gaming rig and shortly thereafter starting the windows updates, I would receive a BSOD (was literally built 3-4weeks ago). I thought it was because the updates hadn't finished. So we updated everything and for a day or two everything would be fine.

A week later, my computer would either freeze up or BSOD when playing games such as League of Legends, Skyrim, Guild Wars 2, browsing, or even sitting idly. All my drivers are updated, and I just finished reinstalling the OS today in hopes that maybe that was the cause. I even tried following the one thread here in using the driver verifier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Sadly, when I restarted, my computer would freeze up on the desktop (mouse wouldn't move, could not ctrl+alt+delete, etc). I restarted 4 times, waited half an hour while the screen was frozen on main desktop and gave up (removing the presets of the verifier in safe mode).

Now after my monologue, please see the attached zip. I hope someone knows what is wrong because I'm ready to throw this contraption out the window (no, I won't - I love my gaming too much).

To the best of my knowledge, these are some of the driver specs:
Windows 7 Home Premium
AMD FX(tm)-8120 Eight Core Proccessor
ASUS M5A99FX Pro R2.0 Motherboard
AMD Radeon HD 7700 Series
AMD Sata Controller
Realtek PCIe GBE Family Controller Adapter and Wireless LAN

Please let me know if you need anything else

 

[Arc]

Welcome aboard.

This is a stop 0x05.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck F4[/COLOR], {3, fffffa8009190b30, fffffa8009190e10, fffff8000379d460}

Probably caused by : wininit.exe

Followup: MachineOwner
---------

This is usually a storage related stop code. So you have to do something there.

• Update your SSD's firmware.
• Update the Asmedia 106x SATA Host Controller Driver, from ASMedia Technology Inc. ????
• Go to your SSD manufacturer's site, and take their test, to make it sure that there is no corruption.

Let us know the result.