Keep Getting Stop Error Codes 0x0000007a and 0x000000f4

Crysis01 · 01 Mar 2014

Hi guys,

I was wondering if anyone can help me with these BSOD's I've been getting. They've been happening about 4 or 5 times a day and they're almost always these 2 error codes but mostly the 7a one.

I've tried uninstalling and updating pretty much every single driver and changed ram sticks and the slots they're in. I'm still fairly confident it's a driver issue though because it will run fine for hours in safe mode and safe mode with networking. Some of the drivers the BSOD's tell me are responsible are ntoskrnl.exe, ataport.sys and more recently asyncmac.sys, HTTP.sys and nusb3xhc.sys. Also, sometimes the computer will kind of freeze up where nothing responds except the mouse and I have to hold the power button to turn off the computer.

This problem has been going on for a couple of months where it will have its good days where it won't BSOD at all and then a really bad couple of days where it's virtually unusable because it keeps crashing.

I would really appreciate if you guys could help me solve this problem or give me some suggestions as to what the problem is. :)

derekimo · 01 Mar 2014

Welcome to the forum,

Additional information is required.

1. Download this .BAT file to your desktop

Download

2. Right-click the .BAT file and 'Run as Administrator'
3. Locate the .ZIP file created on your desktop, and upload it here in your next reply.

Crysis01 · 01 Mar 2014

Hi derekimo,

I've attached the ZIP file your after.

Crysis01 · 02 Mar 2014

I just got another BSOD with the f4 error code. This time it's saying srv.sys caused it.

Can someone please help. I'm ready to throw the computer out the window.

Arc · 02 Mar 2014

Code:

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc40008920, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 000000010e894860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8800112493c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

Code:

BugCheck 7A, {fffff6fc40008920, ffffffffc0000185, 10e894860, fffff8800112493c}

Probably caused by : ataport.SYS ( ataport!IdePortDispatchPnp+22 )

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

ataport.sys is the system native IDE ATA/ATAPI controller (alongwith atapi.sys). It should not fail at its own. But it is highly vulnerable to a special type of malware, called rootkit. So scan the system for possible virus infection with the following programs.

If anything found, delete those all. If nothing is found, it may be that the physical port is failing itself.
Re-seat the sata and power.

Change the SATA cable to a new one. Apply the cable to another unused port on the motherboard.

Also test your HDD using Seatools for DOS.

Let us know the results.

Crysis01 · 02 Mar 2014

Thanks for the assistance Arc. I've just done a scan with TDSSKiller and it didn't find anything although when I tick verify file digital signatures and detect TDLFS file system in the settings it picks up a medium risk threat Device/HardDisk0/DRO. I'm not sure if that's a real threat or not seeing as it doesn't get picked up in the scan with default settings.

I'll test my Hard Drive with Seatools and change my SATA cable and the port it's in and I'll let you know how it goes.

Arc · 02 Mar 2014

Crysis01 said:

a medium risk threat Device/HardDisk0/DRO.

That is a bootkit (boot malware), situated at the root of Hard Disc 0. It may be enough reason for the stop 0xF4 and 0x7A BSODs.

I suggest you to run Windows Defender Offline, linked in my earlier post. When the scan is finished, run Startup Repair, for three times, with restarts after every run.

Do the other two things as you planned, too.

Let us know.

Crysis01 · 02 Mar 2014

This doesn't sound good. I just ran a Short Drive Self Test on Seatools and it says it failed. The test code is 6C9AC2A4. It passed the S.M.A.R.T Check and the Short Generic test though and I haven't had a chance to run the Long Generic test yet.

Does this mean that there's something wrong with my Hard Drive?

Arc · 02 Mar 2014

Overall, the situation is not good.

Take the two bootable scans ... WDO and Long Generic test.
Dont back up the data off the HDD before completing the WDO scan.

Crysis01 · 02 Mar 2014

I just realised you wanted me to use the bootable version of Seatools. I accidently scanned with the Windows version.

Anyway I followed the instructions on how to get Seatools to boot from a USB and I had no trouble doing that. The problem I'm having now though is when I boot from the USB I get this message: InitDiskBad or missing command interpreter: command.com/P /E:256 Enter the full shell Command Line.

Do you know what this means?