Random BSODs out of nowhere, 0x000000F4 & 0x0000007A

In the past few days, I've been getting a lot of blue screen errors. The first one happened when I was just watching videos on YouTube. The other ones happened either while the computer was idling or while I was playing games. I'm beginning to think that my hard drive is failing. After every blue screen error, the subsequent reboot will fail with another blue screen, but the reboot after that will succeed. I tried to use safe mode, but it also blue screens there as well (everything would slow to a halt first, then everything freezes for a minute or two, then blue screens). Here are the BlueScreenView reports; the full minidumps are in the attached zip file.

Code:

==================================================
Dump File         : 091513-23665-01.dmp
Crash Time        : 2013-09-15 14:30:24
Bug Check String  : KERNEL_DATA_INPAGE_ERROR
Bug Check Code    : 0x0000007a
Parameter 1       : fffff6fc`40010930
Parameter 2       : ffffffff`c000000e
Parameter 3       : 00000001`80214be0
Parameter 4       : fffff880`02126000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75b80
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18229 (win7sp1_gdr.130801-1533)
Processor         : x64
Crash Address     : ntoskrnl.exe+75b80
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : F:\Windows\Minidump\091513-23665-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 285,120
==================================================

==================================================
Dump File         : 091313-74490-01.dmp
Crash Time        : 2013-09-13 23:36:14
Bug Check String  : CRITICAL_OBJECT_TERMINATION
Bug Check Code    : 0x000000f4
Parameter 1       : 00000000`00000003
Parameter 2       : fffffa80`06e39b30
Parameter 3       : fffffa80`06e39e10
Parameter 4       : fffff800`037870d0
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75b80
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18229 (win7sp1_gdr.130801-1533)
Processor         : x64
Crash Address     : ntoskrnl.exe+75b80
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : F:\Windows\Minidump\091313-74490-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 291,600
==================================================

I'm currently running a few disk diagnostics through Hiren's Boot CD, I'll report back all the data once they're finished. But here's something that might relate to the problem I'm having (I'm using a laptop with a 750GB SATA hard disk): You receive various Stop error messages in Windows 7 or in Windows Server 2008 R2 when you try to resume a computer that has a large SATA hard disk

S.M.A.R.T. information:

Code:

ST9750420AS   5WS0K30R
-------------------------------------------------------------------------
  ID      Name                   Value  Worst  Tresh       Raw    Health
-------------------------------------------------------------------------
  1 Raw read error rate           113     79      6     53727488   ••••• 
  3 Spin-up time                   98     98     85            0   ••••  
  4 Number of spin-up times        98     98     20         2160   ••••  
  5 Reallocated sector count      100    100     36           67   ••••• 
  7 Seek error rate                86     60     30    431822237   ••••  
  9 Power-on time                  91     91      0         8531   ••••  
 10 Spin-up retries               100    100     97            0   ••••• 
 12 Start/stop count               99     99     20         1078   ••••  
184 End-to-End error              100    100     99            0   ••••• 
187 Reported UNC error              1      1      0         3396   •     
188 Command timeout               100     96      0   4295098403   ••••• 
189 High Fly writes               100    100      0            0   ••••• 
190 Airflow temperature            60     48     45   40°C/104°F   ••••  
191 G-SENSOR shock counter        100    100      0          139   ••••• 
192 Power-off retract count       100    100      0          170   ••••• 
193 Load/unload cycle count        98     98      0         5434   ••••  
194 HDA Temperature                40     52      0   40°C/104°F   ••••  
194 Minimum temperature            90     52      0    18°C/64°F   -     
195 Hardware ECC recovered        113     99      0     53727488   ••••• 
197 Current pending sectors        99     93      0           24   ••••  
198 Offline scan UNC sectors       99     93      0           24   ••••  
199 Ultra DMA CRC errors          200    200      0            0   ••••• 
240 Head flying hours             100    253      0  141562122084657   ••••• 
241 unknown attribut              100    253      0   1876102870   ••••• 
242 unknown attribut              100    253      0   2077183789   ••••• 
254 G-SENSOR shock counter        100    100      0            0   •••••

See attachments for additional information.

A minidump is not enough to debug a stop 0xF4. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

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

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: fffff6fc40010930, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000180214be0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88002126000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

Do some Disc checks.

1. Run chkdsk /f/r, following the option two of the tutorial Disk Check
2. Seatool for dos: SeaTools | Seagate download
   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.

Now leave the original post. Dont alter it anymore. Continue accordingly.



As Hiren's stuff is not legit, we dont discuss about it.

Same BSOD again. And the same BSOD will continue till action is taken.

Disk 1, Drive 2. Volume name is My Book.
Back the data up and stop using that Disc.

Let us know only if it BSODs without it or not.

dennis96411 said:

It blue screened again with the external drive unplugged. I then tried to copy some files from the internal hard drive to the external hard drive overnight, but I woke up to a blue screen and now the external hard drive is having trouble as well. I'm currently running TestDisk because nothing else recognizes it. Sigh, the problems just keep on coming.

We needed to see that crash dump ... probably some other information may be obtained from that one.