BSOD on Startup or Randomly f4 code

[ghostridur]

Just built the pc about a month ago and have been having bsods frequently usually either at the login screen, or just under normal use. I ran a memtest for around 12 hours and had 0 errors, sea tools in windows also comes up a pass however it does not allow me to run any advanced tests.
Computer is a I5 4690k, msi frait mobo, 16gb crucial ballistic, mx100 ssd, sapphire r290 tri oc grahpics.

The bios and chipset/mobo drivers are the latest on the msi site and I attached the dumps.
Thanks for looking.

 

[cipley]

This is a very complicated error IMO...

STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION

Usual causes: ?

For starters, it looks like your current Working Set size is way beyond its maximum size setting:

2: kd> !process fffffa800e7deb30 3
GetPointerFromAddress: unable to read from fffff800030b8000
PROCESS fffffa800e7deb30
    SessionId: none  Cid: 0258    Peb: 7fffffdb000  ParentCid: 0174
    DirBase: 3b6bab000  ObjectTable: fffff8a0019f9240  HandleCount: <Data Not Accessible>
    Image: wininit.exe
    VadRoot fffffa800e7dca40 Vads 66 Clone 0 Private 475. Modified 1. Locked 2.
    DeviceMap fffff8a000008ca0
    Token                             fffff8a0019a5c50
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
    ElapsedTime                       00:00:00.000
    UserTime                          00:00:00.000
    KernelTime                        00:00:00.000
    QuotaPoolUsage[PagedPool]         0
    QuotaPoolUsage[NonPagedPool]      0
    Working Set Sizes ([B][COLOR="Red"]now[/COLOR][/B],min,[B][COLOR="red"]max[/COLOR][/B])  ([B][COLOR="red"]1294[/COLOR][/B], 50, [B][COLOR="red"]345[/COLOR][/B]) ([B][COLOR="red"]5176KB[/COLOR][/B], 200KB, [B][COLOR="red"]1380KB[/COLOR][/B])
    PeakWorkingSetSize                1294
    VirtualSize                       46 Mb
    PeakVirtualSize                   49 Mb
    [B][COLOR="red"]PageFaultCount                    1517[/COLOR][/B]
    MemoryPriority                    BACKGROUND
    BasePriority                      13
    CommitCharge                      608

        *** Error in reading nt!_ETHREAD @ fffffa800e7da060

Also notice the high amount of Page Fault that occurred...
:ar: Can you post screenshot from Resource Monitor? Here's how to open it.

Also I found that you have Optimizer Pro 4. I suggest to Uninstall it. In fact, you don't need any "optimizing" software at any kind since Windows 7 basically can do it itself.

Then, scan for any kinds of malware
:ar: Microsoft Security Essentials | Protect against viruses, spyware, and other malware
:ar: Windows Defender Offline
:ar: Anti-rootkit utility TDSSKiller

Let's see the results...

 

[Arc]

Hi ghostridur.

Update the Firmware of your SSD to version MU02.

• support-ssd-firmware | United States (USD)
• How to Upgrade Crucial SSD Firmware | StorageReview.com - Storage Reviews

Report us for any further BSOD after doing it.

 

[ghostridur]

Odd, I have never installed Optimizer Pro looks like a pretty shady program by a quick google search, it is not in the add remove list but it does have a folder in the program files with only an application file in it and a .dat in program data. Not sure what the deal with that is.

Microsoft security essentials and rootkit both come up clean. As fasr as the Working set size is that something that windows calculates and sets automatically?

The ssd firmware was updated to MU02 sometime on March 14th.

 

[ghostridur]

I just had 4 in a row, I couldn't past the initial desktop load after login.

 

[Arc]

I just had 4 in a row, I couldn't past the initial desktop load after login.

3 0xF4s in a row and then a stop 0x124 within 5 minutes. A stop 0x124 is hardware issue, and the just previous BSODs are indicating to your SSD. A combined impact goes to a storage failure.

Do you have access to any other HDD or SSD? If you have, do a clean install of windows on it, leave teh existing SSD aside, and observe if the 0x124 BSODs are coming back or not.

EDIT: Wait a bit! What have you said here??

The ssd firmware was updated to MU02 sometime on March 14th.

Then it is not just a coincidence that the issue started to occur from that very day.

View attachment 356908
​

You need to apply any other storage device there, to ensure that it was a failing attempt to update the SSD firmware which is the root of the issue.

 

[ghostridur]

I will do a fresh install on a platter drive. The dates line up because that was the day I reformatted and updated everything to try and stop the bsods.

 

[Arc]

So you tried a clean reinstall too.

Will wait to know how everything goes with the other HDD.

 

[ghostridur]

Quick update, fresh install on a platter drive known to be good yielded 2 bsods in a row. Have not run all of the windows updates but figured I would throw these up. I'm guessing updating will not be worth the time since it appears not to be an issue with the drive itself. This drive is also hooked up with a different sata cable just for kicks.

 

[Arc]

Still the same oxF4.

The next thing, check the cabling and connections on the motherboard. Open the computer. Remove and re-seat the items from the motherboard except the CPU. Graphics card, RAM sticks and SATA ports, remove and re-seat them all.

While re-seating, apply new SATA cables if possible, and use an unused SATA port on the motherboard.

See if it changes anything there.