BSOD updating windows, 0x000000F4

[FigNewman]

Hey guys,

I just installed of win7 on my new comp. Everything went smoothly got my pc up and running. After installing drivers from disk for my wifi card I attemted to update through windows update. After a few minutes my computer started running super slow and then I got a blue screen that stated process or thread crutial to system operation has unexpectedly exited or terminated. Not sure how to fix this.

 

[axe0]

Hi FigNewman,

I suggest you try to get your system as soon as possible up to date.
The updates contain several fixes for several problems, there is a chance those updates will solve your problem.

However, the 0xF4 is usually a crash caused by hard drive problems.
If updating didn't help, I suggest you run a few hard drive tests.

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

   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.

 

[FigNewman]

ok, I ran chkdsk and Seagate, it didn't turn up anything. The error log for Hd tuner showed no errors.
I was able to update after I ran the chkdsk and haven't had a crash since. I'll post the screens to be safe.

 

[FigNewman]

Hey,

I'm still running into errors and every one has had a different code. One was the same as the original post. I also got a 0x000007a and one or two others. I've posted an updated zip.

 

[axe0]

Input/Output errors.

Please check the cable of the hard drive for damage, also check both connections for any damage.
Please check the connection of the hard drive for any broken/bent pins.

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: fffffa800835a610, Terminating object
Arg3: fffffa800835a8f0, Process image file name
Arg4: fffff80002fe36d0, Explanatory message (ascii)

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

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

PROCESS_OBJECT: fffffa800835a610

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.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_[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`0c463e38 fffff800`03072082 : 00000000`000000f4 00000000`00000003 fffffa80`0835a610 fffffa80`0835a8f0 : nt!KeBugCheckEx
fffff880`0c463e40 fffff800`02f97d7b : ffffffff`ffffffff fffffa80`0a7e9060 fffffa80`0835a610 fffffa80`0835a610 : nt!PspCatchCriticalBreak+0x92
fffff880`0c463e80 fffff800`02f94904 : ffffffff`ffffffff 00000000`00000001 fffffa80`0835a610 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29c66
fffff880`0c463ed0 fffff800`02cdaed3 : fffffa80`0835a610 fffff800`c0000006 fffffa80`0a7e9060 00000000`00d60ec0 : nt!NtTerminateProcess+0xf4
fffff880`0c463f50 fffff800`02cd7490 : fffff800`02d5cbf9 fffff880`0c464a38 fffff880`0c464790 fffff880`0c464ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0c4640e8 fffff800`02d5cbf9 : fffff880`0c464a38 fffff880`0c464790 fffff880`0c464ae0 00000000`77bdf9d8 : nt!KiServiceLinkage
fffff880`0c4640f0 fffff800`02cdb2c2 : fffff880`0c464a38 00000000`00de0000 fffff880`0c464ae0 00000000`77bebd40 : nt! ?? ::FNODOBFM::`string'+0x48154
fffff880`0c464900 fffff800`02cd9e3a : 00000000`00000000 00000000`77ba0a34 00000000`00d62901 00000000`00de0000 : nt!KiExceptionDispatch+0xc2
fffff880`0c464ae0 00000000`77c689b5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00d615e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c689b5


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

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

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

ANALYSIS_SOURCE:  KM

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

FAILURE_ID_HASH:  {7e8d25f6-54c6-2456-f4df-269f2fd35200}

Followup: MachineOwner

 

[FigNewman]

Alright, I checked the port on the hard drive and it had all its pins. There was no apparent damage to the cable. I couldn't get a good look at the connection on the motherboard so I'm gonna switch the hard drive over to one of the other ports and see if that fixes it. If that doesn't, can I safely assume that it's the cable?

 

[axe0]

If the cable is properly connected then my thought would be that it is the cable.