BSOD Critical Operation Terminated while watching video

[bitplayer]

Hey everyone. Im new here and just built a new machine. REALLY hoping these BSODs werent caused by faulty hardware as Im past the return period on everything at the store (bought the parts over a month ago and just now built)

Can you give me an idea what caused these? Specifically the one on 1/14. the one on 1/10 was right after overclocking and running prime 95. The one on 1/14 happened while surfing on chrome.

 

[BorisTheAnimal]

Hi bitplayer and welcome to Sevenforums!

Your latest BSOD was probably caused by overheating hardware, a few seconds after the crash on 1/14 there was an entry in the Eventlog saying that CPU hit over 100 Celsius.

So what I would recommend you to do is to open up the case and check if you have enough fans and check the CPU cooler, if you installed the cooler that Intel/AMD have bundled with their CPUs as they aren't really made for cooling(yes there are some exceptions), I would really recommend buying a new one, example the Hyper Evo 212 is a very nice and cooler.

Cheerio /Boris

 

[bitplayer]

That just doesnt sound right. I have a Hyper 212 with 2 Corsair HP 2500 rpm fans on there. I cant imagine that was the issue. I top out at about 80 on prime 95 on my highest cores.

I realized I had the drivers from the mobo disc installed (2014 drivers). I have since installed the updated sound, lan, INF, usb 3.0, intel Sata, intel ME ect.... drivers.

Could that have been the issue?

 

[BorisTheAnimal]

Hi well I'm only telling you what I found looking through the Eventlog file:

Event[16196]:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2016-01-14T18:17:26.467
Event ID: 41
Task: N/A
Level: Critical
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: ALICE-V
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

And two seconds later:

Event[16202]:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2016-01-14T18:17:28.620
Event ID: 89
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: ALICE-V
Description:
ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated.
_PSV = 0K
_TC1 = 0
_TC2 = 0
_TSP = 0ms
_AC0 = 353K
_AC1 = 328K
_AC2 = 323K
_AC3 = 318K
_AC4 = 313K
_AC5 = 0K
_AC6 = 0K
_AC7 = 0K
_AC8 = 0K
_AC9 = 0K
_CRT = 378K
_HOT = 0K
_PSL - see event data.

Event[16203]:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2016-01-14T18:17:28.620
Event ID: 89
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: ALICE-V
Description:
ACPI thermal zone ACPI\ThermalZone\TZ01 has been enumerated.
_PSV = 381K
_TC1 = 1
_TC2 = 5
_TSP = 1000ms
_AC0 = 0K
_AC1 = 0K
_AC2 = 0K
_AC3 = 0K
_AC4 = 0K
_AC5 = 0K
_AC6 = 0K
_AC7 = 0K
_AC8 = 0K
_AC9 = 0K
_CRT = 378K
_HOT = 0K
_PSL - see event data.

And if we look at the picture below we can see that there was a massive heat buildup.

View attachment 379864

I'm not saying that I'm 100% right nor that you are wrong, I'm simply stating that I think it was due to overheating hardware.

 

[axe0]

A question would then be if the airflow is proper for cooling, if the airflow is improper it still can cause overheating.

Going to the dumps, a process was terminated because there were problems with accessing data to the hard drive(s).
As you have 2 SSD's and 1 HDD, I suggest to first try some tests on the SSD's and HDD and after that updating the firmware if the SSD's do not have any problems.

Samsung SSD 840 Series
Samsung SSD 850 EVO 250G
WDC WD10EZEX-00RKKA0

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

1. Short Drive Self Test
2. Short generic
3. Long generic

If the short generic fails, no need for the long generic.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

*******************************************************************************
*                                                                             *
*                        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: fffffa80081aeb10, Terminating object
Arg3: fffffa80081aedf0, Process image file name
Arg4: fffff800031d3750, Explanatory message (ascii)

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

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

PROCESS_OBJECT: fffffa80081aeb10

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - De instructie op 0x%p verwijst naar geheugen op 0x%p. De benodigde gegevens zijn niet in het geheugen geplaatst vanwege een I/O-foutstatus van 0x%x.

BUGCHECK_STR:  0xF4_[COLOR="red"]IOERR[/COLOR]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`0744ae38 fffff800`03262c02 : 00000000`000000f4 00000000`00000003 fffffa80`081aeb10 fffffa80`081aedf0 : nt!KeBugCheckEx
fffff880`0744ae40 fffff800`031866ab : ffffffff`ffffffff fffffa80`08e04500 fffffa80`081aeb10 fffffa80`081aeb10 : nt!PspCatchCriticalBreak+0x92
fffff880`0744ae80 fffff800`03183234 : ffffffff`ffffffff 00000000`00000001 fffffa80`081aeb10 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29c66
fffff880`0744aed0 fffff800`02ecae93 : fffffa80`081aeb10 fffff800`c0000006 fffffa80`08e04500 00000000`00980d40 : nt!NtTerminateProcess+0xf4
fffff880`0744af50 fffff800`02ec7450 : fffff800`02f4cae9 fffff880`0744ba38 fffff880`0744b790 fffff880`0744bae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0744b0e8 fffff800`02f4cae9 : fffff880`0744ba38 fffff880`0744b790 fffff880`0744bae0 00000000`77b19004 : nt!KiServiceLinkage
fffff880`0744b0f0 fffff800`02ecb282 : fffff880`0744ba38 00000000`009c0000 fffff880`0744bae0 00000000`77b3e6bc : nt! ?? ::FNODOBFM::`string'+0x48154
fffff880`0744b900 fffff800`02ec9dfa : 00000000`00000000 00000000`77b19007 00000000`00000001 00000000`009c0000 : nt!KiExceptionDispatch+0xc2
fffff880`0744bae0 00000000`77a18996 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00981460 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a18996


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0xF4_[COLOR="red"]IOERR[/COLOR]_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_[COLOR="red"]IOERR[/COLOR]_IMAGE_csrss.exe

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xf4_[COLOR="Red"]ioerr[/COLOR]_image_csrss.exe

FAILURE_ID_HASH:  {183378f4-a174-8cab-8ad7-e5d860a58439}

Followup: MachineOwner

 

[bitplayer]

I just opened my case and noticed the power cable to one of my SSDs (The 850 evo I keep a few games on) was a little loose. Could this have been the issue?

 

[axe0]

Loosy cables could certainly cause input/output errors, the data can't be accessed proper when something isn't connected proper.
Test your system for some days to see if the cable was the problem, if it is NOT then you may expect bluescreens within the testing period.

Please let us know how it goes

 

[bitplayer]

Also, it may have been BOTH. SO i got in there and really shoved my cables in 2 days ago and havent had anymore bsod and have been playing witcher 3 pretty hard core (5-6 hours a day) since. Also, I did notice that one of the scews was not very tight on my cooler. I took it off (the artic silver was spread really nicely (only a week old) so I didnt reapply, but screwed the cooler down nice and tight. Will let yall know.

But in youre opinion axe0 does it sound like a loose cable?

 

[axe0]

Also, it may have been BOTH. SO i got in there and really shoved my cables in 2 days ago and havent had anymore bsod and have been playing witcher 3 pretty hard core (5-6 hours a day) since. Also, I did notice that one of the scews was not very tight on my cooler. I took it off (the artic silver was spread really nicely (only a week old) so I didnt reapply, but screwed the cooler down nice and tight. Will let yall know.

But in youre opinion axe0 does it sound like a loose cable?

It certainly does sound like a loose cable.

 

[bitplayer]

Im starting to think this was just a loose cable. I have opened up my case ALOT in the last week because of this new build and have been moving wires around and swapping out cables (got all white extension cables, did a black and white theme build) so Im thinking that maybe I tugged on something and a cable came loose.

Here is the question though. If my Evo 840 250gb that I keep some games on, came loose, would that actually be able to BSOD my system? My understanding is that data storage drives like this (as long as not being accessed at the moment) can be plugged in at anytime and it wont effect anything. Wouldnt it have to be my system drive that was loosely connected?

Is this the case?

 

[BorisTheAnimal]

Im starting to think this was just a loose cable. I have opened up my case ALOT in the last week because of this new build and have been moving wires around and swapping out cables (got all white extension cables, did a black and white theme build) so Im thinking that maybe I tugged on something and a cable came loose.

Here is the question though. If my Evo 840 250gb that I keep some games on, came loose, would that actually be able to BSOD my system? My understanding is that data storage drives like this (as long as not being accessed at the moment) can be plugged in at anytime and it wont effect anything. Wouldnt it have to be my system drive that was loosely connected?

Is this the case?

Just a thought, Samsung has its Magician software have you checked if there are any firmware updates through there?

Plus about the loose cables, I've noticed that some SATA cables doesn't have the snap technique, that they only plug in easily and if you drag the cable too much they'll drop.

 

[bitplayer]

Im starting to think this was just a loose cable. I have opened up my case ALOT in the last week because of this new build and have been moving wires around and swapping out cables (got all white extension cables, did a black and white theme build) so Im thinking that maybe I tugged on something and a cable came loose.

Here is the question though. If my Evo 840 250gb that I keep some games on, came loose, would that actually be able to BSOD my system? My understanding is that data storage drives like this (as long as not being accessed at the moment) can be plugged in at anytime and it wont effect anything. Wouldnt it have to be my system drive that was loosely connected?

Is this the case?

Just a thought, Samsung has its Magician software have you checked if there are any firmware updates through there?

Plus about the loose cables, I've noticed that some SATA cables doesn't have the snap technique, that they only plug in easily and if you drag the cable too much they'll drop.

I havent installed the software, no. My old system (literally all I did was buy a new case and mobo for this build) ran perfectly fine a week ago without it. With this imparticular ssd the cables (doesnt matter which one I use) dont *snap* into place. I just have to shove them in there, and the cables are hidden behind my mobo and I have been opening the case a lot lately to put new fans in.

Does loose cable or out of date/missing Sata (intel rapid storage) drivers sound more like the culprit?

 

[BorisTheAnimal]

Im starting to think this was just a loose cable. I have opened up my case ALOT in the last week because of this new build and have been moving wires around and swapping out cables (got all white extension cables, did a black and white theme build) so Im thinking that maybe I tugged on something and a cable came loose.

Here is the question though. If my Evo 840 250gb that I keep some games on, came loose, would that actually be able to BSOD my system? My understanding is that data storage drives like this (as long as not being accessed at the moment) can be plugged in at anytime and it wont effect anything. Wouldnt it have to be my system drive that was loosely connected?

Is this the case?

Just a thought, Samsung has its Magician software have you checked if there are any firmware updates through there?

Plus about the loose cables, I've noticed that some SATA cables doesn't have the snap technique, that they only plug in easily and if you drag the cable too much they'll drop.

I havent installed the software, no. My old system (literally all I did was buy a new case and mobo for this build) ran perfectly fine a week ago without it. With this imparticular ssd the cables (doesnt matter which one I use) dont *snap* into place. I just have to shove them in there, and the cables are hidden behind my mobo and I have been opening the case a lot lately to put new fans in.

Does loose cable or out of date/missing Sata (intel rapid storage) drivers sound more like the culprit?

This is what I meant with the snap technique, basically that some doesn't have that clip which holds them in more securely:

But yes I do think that loose cables might cause errors. Though I'm not sure about the drivers but if there are updates there won't be anything wrong with updating them.
​