BSOD problem for months, getting worse, caused by ntoskrnl.exe

For around two or three months the system has been crashing on a weekly or biweekly basis and wasn't so much of a problem as to interfere and warrant investigation on my part. Within the past few days, however, it has gotten much worse and now crashes at least once daily. I have done what I can with my limited computer skills and determined ntoskrnl.exe is the culprit and followed some potential solutions found on this forum as well as other sites but to no avail. Although it may be mere coincidence, I feel it is worth noting that the vast majority of crashes (90%+) occur when the computer has been left on but I am not currently at the desk working on anything. Any help would be much appreciated, thank you!

Welcome to SevenForums.

A BCC F4 is common when SSD's are present.

Code:

Model	OCZ-SOLID3 ATA Device

Is the firmware for your SSD up-to-date?

Check for one and see if the stability returns.

What security software do you use?

Perform a System File Check:

1. Click on the start
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it:

• Disk Check

Reduce items at start-up. Nothing except anti-virus is required:

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

SUMMARY:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800e057b30, fffffa800e057e10, fffff80003bcc460}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

Followup: MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800e05db30, fffffa800e05de10, fffff80003be0460}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

Followup: MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800e0cfb30, fffffa800e0cfe10, fffff80003b94460}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

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

Code:

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800e057b30, Terminating object
Arg3: fffffa800e057e10, Process image file name
Arg4: fffff80003bcc460, Explanatory message (ascii)

Debugging Details:
------------------

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa800e057b30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`1139fe38 fffff800`03c54822 : 00000000`000000f4 00000000`00000003 fffffa80`0e057b30 fffffa80`0e057e10 : nt!KeBugCheckEx
fffff880`1139fe40 fffff800`03c00e0b : ffffffff`ffffffff fffffa80`0e0dbb50 fffffa80`0e057b30 fffffa80`0e057b30 : nt!PspCatchCriticalBreak+0x92
fffff880`1139fe80 fffff800`03b7ff04 : ffffffff`ffffffff 00000000`00000001 fffffa80`0e057b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6
fffff880`1139fed0 fffff800`038cc253 : fffffa80`0e057b30 fffff800`c0000006 fffffa80`0e0dbb50 00000000`00a20e40 : nt!NtTerminateProcess+0xf4
fffff880`1139ff50 fffff800`038c8810 : fffff800`03917b7f fffff880`113a0a38 fffff880`113a0790 fffff880`113a0ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`113a00e8 fffff800`03917b7f : fffff880`113a0a38 fffff880`113a0790 fffff880`113a0ae0 00000000`00a21b50 : nt!KiServiceLinkage
fffff880`113a00f0 fffff800`038cc642 : fffff880`113a0a38 00000000`0000d8ec fffff880`113a0ae0 00000000`00a21628 : nt! ?? ::FNODOBFM::`string'+0x488a4
fffff880`113a0900 fffff800`038cb1ba : 00000000`00000000 000007fe`fd79d8c0 00000000`00000001 00000000`0000d8ec : nt!KiExceptionDispatch+0xc2
fffff880`113a0ae0 00000000`77839c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00a21570 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77839c12


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

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

Let us know the results. Good luck.

Thank you for the quick response. At this time I am unable to update my SSD's firmware (though I can confirm it is out-of-date) as it is my boot drive and I do not have my Windows disk available at the moment. I will do this as soon as possible. Regardless, I ran a system file check and it found some issues which it was successful in fixing. The disk check did not find any issues. I have also reduced the number of start up programs to a bare minimum. I do not use any security software outside of what is default on the Windows OS. Are there any you might recommend for me? Thanks again!

Here are some links that may help you with updating the firmware of the SSD

• OCZ Technology
• Guide.pdf

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
  
  • Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer
    
    • Good and Free system security combination.

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.
Let us know how it went :)

As of now I have successfully updated my SSD's firmware to its latest version. I have also installed and updated MSE and Malwarebytes, though neither discovered any problems upon their first scan. Unless you have any other recommendations, I will give the system a week to see if BSOD occurs again. Obviously if it does I will report back, but if it can make it a week I'll go ahead and mark this as solved. Once again, thank you very much for your assistance in this matter.

No incidents for a week now, thank you very much! I really appreciate your willingness to assist and hope you continue to do so!

Thanks for letting us know.
Happy computing!