BSODs - 0x0000F4 and 0x00007A errors

[abrahamguo]

Hi guys, I'm having some issues with my laptop. I replaced the hard drive in it about a week ago, and I've been having pretty frequent BSODs since then. The past several days I've been getting 0x0000F4 Kernel Data Inpage Errors. Now this morning I've gotten two 0x0000007A errors. All the files are attached.
Here's a couple more things that could point to an issue - #1: for some time (several months) one of the screws that holds the hard drive has been missing. However, I made sure when I replaced the hard drive that it could not move around.
#2 - occasionally after a BSOD when rebooting, the computer says something like "Exiting PCE ROM. Insert boot media and press a key." It goes away when I reboot again. This is the same message the computer displayed a couple weeks ago when the HD died.
Let me know if you need me to post any other info!

 

[Arc]

A stop 0xF4 is usually a storage related issue. You are saying about stop 0x7A too, but it is not present in the uploaded zip. If those two are combined together, we should check for the HDD at first, on your HGST 320 GB.

Seatool for dos: SeaTools | Seagate download

1. Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results.

_________________________________________________________________________
BSOD ANALYSIS:

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

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800751bb30, fffffa800751be10, fffff80002fe2350}

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

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa800751bb30, Terminating object
Arg3: fffffa800751be10, Process image file name
Arg4: fffff80002fe2350, Explanatory message (ascii)

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

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

PROCESS_OBJECT: fffffa800751bb30

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`077fae38 fffff800`03069d22 : 00000000`000000f4 00000000`00000003 fffffa80`0751bb30 fffffa80`0751be10 : nt!KeBugCheckEx
fffff880`077fae40 fffff800`0301608b : ffffffff`ffffffff fffffa80`07589b50 fffffa80`0751bb30 fffffa80`0751bb30 : nt!PspCatchCriticalBreak+0x92
fffff880`077fae80 fffff800`02f96144 : ffffffff`ffffffff 00000000`00000001 fffffa80`0751bb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`077faed0 fffff800`02cdae93 : fffffa80`0751bb30 fffff800`c0000006 fffffa80`07589b50 00000000`011b0e40 : nt!NtTerminateProcess+0xf4
fffff880`077faf50 fffff800`02cd7450 : fffff800`02d2681f fffff880`077fba38 fffff880`077fb790 fffff880`077fbae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`077fb0e8 fffff800`02d2681f : fffff880`077fba38 fffff880`077fb790 fffff880`077fbae0 00000000`011b1b50 : nt!KiServiceLinkage
fffff880`077fb0f0 fffff800`02cdb282 : fffff880`077fba38 00000000`00012284 fffff880`077fbae0 00000000`011b1628 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`077fb900 fffff800`02cd9dfa : 00000000`00000000 000007fe`fd3dd8c0 fffffa80`04168301 00000000`00012284 : nt!KiExceptionDispatch+0xc2
fffff880`077fbae0 00000000`775e9c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`011b1570 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775e9c12


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
---------