Solved BSOD frequently at random times, STOP: 0x000000F4

[NotThisMind]

Yesterday i got like 30 BSOD's all day all from error above or 'a system thread was forcefully exited and the system was shutdown' to prevent damage or something like that.

Some reboots the disk wasn't detected at BIOS level, some reboots there was the post bios message "a disk read error occurred, press Ctrl Alt Del to reboot", and when it gets to loading, it takes forever always, that is if it doesn't reboot after the loading window.

I'm almost 100% sure it's the disk, but today the computer seems to be running extremely better than normal, although i did get a BSOD early today from the 'system thread exited forecefully' message i said above.

There's no dump files saved from any BSOD because it stucks on "initializing disk for data dump" on the BSOD screen and just gets my fan really loud doing basically nothing.

I just want a confirmation if it's really the disk, it's been getting slower over time...
I attached the posting requirements zip.

 

[Arc]

A stop 0xF4 is HDD related in general, bet there may be some other causes too.

There is no crash dumps in the uploaded zip, so we cannot check; but you should test the HDD. As it is a Seagate one, use Seatools. Take both the shore test and the long test (but not the others). Let us know the results.

http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html
​

Also, uninstall Daemon Tools. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

 

[NotThisMind]

@Arc , tried to run Basic Generic test on SeaTools for Windows, first time got a BSOD right away, 2nd 3rd and 4th got stuck at 6% for a long time on "Outer Scan" and finally gave the error "Short Generic- FAIL".
Is safe to assume disk is long gone right? I'm doomed.

I also did (after i typed sentence above) long generic, got a BSOD, then rebooted (he seemed fine even rebooted somewhat 'fast') did a short generic, same thing as all the generic tests above, 6% then FAIL.

This confirms 100% disk is gone right?

I didn't uninstall Daemon Tools because i don't see the point from here, if you still want me to proceed or try other tools please reply.

Thank you.

 

[Arc]

finally gave the error "Short Generic- FAIL".
Is safe to assume disk is long gone right?

Unfortunate, but true. You need to replace the HDD.

Try to copy the necessary files on the HDD using a bootable linux. If you are lucky you will be able to do it.

http://www.sevenforums.com/tutorials/287439-emergency-kit-save-your-files-dead-os.html

 

[NotThisMind]

Believe it or not, i'm currently backing it up on the main OS, just less than 10GB to go, i've already backed up almost everything in the past days and weeks since i got similar BSOD a month ago but got almost no reply here (it was a different error, i believe 0x7A) .

Let's see if i can still upload to gDrive since i don't have any spare HDD atm, it'll be a long day

Thanks for the assistance, although sometimes the HDD seems to be running fine, like now, it's seems like writting to the disk is 'faster' 'reliable' than reading from it from what i can tell, i just (i know i shouldn't but i really have almost nothing left to back up so) written like 7GB to it on two zip files with 'no problem'.

Anyway, thanks again.

Edit: Just one question, since the BSOD's that caused me to open this thread, google Drive is randomly saying it's offline while on the website itself, even though i'm downloading stuff and upload to it just fine, it just grays out my files in there, and sometimes when he loads folders and files, there are some missing, although if i refresh, they appear right away, it just weird to me that this is happening just now when my HDD is failing, even though afaik browsing gDrive shouldn't have to do in anyway to my HDD, or am i wrong? My heart almost dropped when some files were missing, even though the space used was there... lol.

 

[Arc]

0x7A and 0xF4 is the same thing, depending on the arguments. A typical 0x7A output is ....

KERNEL_DATA_INPAGE_ERROR  (7a)
 The requested page of kernel data could not be read in. [COLOR=Red]  Typically caused by
 a bad block in the paging file or disk controller error[/COLOR]. Also see
 KERNEL_STACK_INPAGE_ERROR.
 [COLOR=Red]If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
 it means the disk subsystem has experienced a failure[/COLOR].

 

[NotThisMind]

Now that i see the title to my thread, it was 7A then right after F4, you're right apparently, it was 0x0000007A (0xFFFFF6FB40000070, 0xFFFFFFFFC000000E, 0x00000000C4214884, 0xFFFFF6800000E000)
http://www.sevenforums.com/bsod-hel...inpage_error-0x0000007a-after-0x000000f4.html

Is there any documentation for those arguments? I remember when i got the first ones i searched but i couldn't find any specifics on the arguments past the STOP error itself, i may or may not have searched enough but...

Thanks again.

 

[Arc]

Now that i see the title to my thread, it was 7A then right after F4, you're right apparently, it was 0x0000007A (0xFFFFF6FB40000070, 0xFFFFFFFFC000000E, 0x00000000C4214884, 0xFFFFF6800000E000)
http://www.sevenforums.com/bsod-hel...inpage_error-0x0000007a-after-0x000000f4.html

Is there any documentation for those arguments? I remember when i got the first ones i searched but i couldn't find any specifics on the arguments past the STOP error itself, i may or may not have searched enough but...

Thanks again.

The second argument is the error status, technically called NTSTATUS.status.
See the second argument in your post that I quoted. It is C000000E which means the disk subsystem has experienced a failure.

The C000000E means, STATUS_NO_SUCH_DEVICE; if elaborated, it means "A device that does not exist was specified".

The summerised reading is, the system is failing to access the HDD. Why? because the HDD is failing, that the disc check utility found, and now you know what was the root cause of the BSOD.

 

[NotThisMind]

Oh ok, i do know what NTStatus errors are, i've had to deal with some while coding, i didn't know what the arguments in a BSOD did mean, glad to know the second is the error status.

Do the other arguments have a useful meaning for diagnosis too? Or where i can find info about them? Or they mean 'nothing'?
Yes, i understand the error, i know HDD is failing, i just want to know to 'diagnose' even slighty BSOD's so in the future i might not need to open a new thread.

Thanks again, gonna see when i can buy a new HDD, i hope 2.5" HDD's are cheaper than 3.5"..

 

[Arc]

The other arguments are not very valuable for a stop 0x7A, but they have their values for other different BSODs.

If you are interested, the legend BSOD analyst John Carrona (usasma) has compiled an exhaustive list of those, see here: BSOD Index

In my place (India), 3.5" discs are much cheaper than the 2.5" ones.

 

[NotThisMind]

Ok, thanks for that link ! Hopefully i don't need it in the future though

I can buy here (Portugal) an external 3.5 with 1TB for like 70€ which is already kind of expensive for me, internals idk, may be more expensive, well, we'll see.

Thanks for all your help, i guess this 'closes' it, appreciated !

 

[Arc]

When you will find that your issue is solved, please consider to mark this thread as solved.

 

[NotThisMind]

Done, sorry, i forgot i can mark this as solved, thanks again.

 

[Arc]

This does not mean that you will not be able to use this thread in any future need. Feel free to give us a shout whenever you need any BSOD help.