Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

This just started this week, no new hardware, no major updates or software installs either before it started happening. The system will often start slowing down or hang completely before BSOD, and there doesn't seem to be any pattern of when it happens.

Either comes up as KERNEL_DATA_INPAGE_ERROR, or simply says "A process or thread crucial to system operation has unexpectedly exited or been terminated."

Searched around for issues, tried a lot of the common fixes - updated drivers, updated firmware on my harddrive since a lot of topics suggested that may be the problem, ran chkdsk didn't find any problems.

Here are pics of some of the many BSODs I've gotten: bsod

Is this a hardware or software issue? And how can I pinpoint which device or program is causing the problem?

share|improve this question

marked as duplicate by Ƭᴇcʜιᴇ007, terdon, TFM, HackToHell, Julian Knight Mar 23 '13 at 10:11

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

Have you done memtest on your RAM to verify that it's okay and just eliminate that from the possibilities? – nerdwaller Mar 23 '13 at 2:09

Given KERNEL_DATA_INPAGE_ERROR, t his is most likely a hard drive that's on its way towards dying. When it sputters, that will cause fluctuating responses until it completely stops, at which point you get an unresponsive system with the error screen you posted above.

Strongly suggest getting a new drive and copying important files after you've installed the OS.

share|improve this answer


The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

In your case an important Windows Process died.

Check the dumps with WinDbg to see which process died:

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.