Stop 0x000000F4 Error (seemingly random?)

It seems I've been having random BSOD Stop errors ever since I put my new PC together about a month ago. I'm not sure what's causing it, and it's happened when I've been doing different things, but it almost seems to happen more frequently when I'm listening to Pandora Radio on my web browser (chrome).

Things I've attempted to do to fix this:

Switched my BIOS from AHCI to IDE (read on google this fixed some issues). Did not fix the issue.

Googled the problem several times (finding a lot of different error codes and situations not similar to my own.) No fix attempted.

Read the windows website and attempted to get a hotfix for SATA hard drives (something about them not waking up in 10 seconds). Hot fix claimed it could not install on my computer. Gave up on it.

Some system information (copy-pasted from newegg, forgive me if it's a lot of uselessness):

CPU: Intel Core i5-2500K Sandy Bridge 3.3GHz (3.7GHz Turbo Boost) LGA 1155 95W Quad-Core Desktop Processor Intel HD Graphics 3000 BX80623I52500K

Motherboard: ASUS P8P67 PRO (REV 3.1) LGA 1155 Intel P67 SATA 6Gb/s USB 3.0 ATX Intel Motherboard

Video Card: EVGA 012-P3-1571-KR GeForce GTX 570 HD w/Display-Port (Fermi) 1280MB 320-bit GDDR5 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card

Boot Drive: Corsair Force Series 3 CSSD-F120GB3A-BK 2.5" 120GB SATA III Internal Solid State Drive (SSD)

RAM: G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Desktop Memory Model F3-10666CL9D-8GBRL

Storage HD: SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" Internal Hard Drive -Bare Drive

Windows_NT6_BSOD_jcgriff2 attached with PERFMON.html file inside the folder.

FloppyDingo said:

It seems I've been having random BSOD Stop errors ever since I put my new PC together about a month ago. I'm not sure what's causing it, and it's happened when I've been doing different things, but it almost seems to happen more frequently when I'm listening to Pandora Radio on my web browser (chrome).

Things I've attempted to do to fix this:

Switched my BIOS from AHCI to IDE (read on google this fixed some issues). Did not fix the issue.

Googled the problem several times (finding a lot of different error codes and situations not similar to my own.) No fix attempted.

Read the windows website and attempted to get a hotfix for SATA hard drives (something about them not waking up in 10 seconds). Hot fix claimed it could not install on my computer. Gave up on it.

Some system information (copy-pasted from newegg, forgive me if it's a lot of uselessness):

CPU: Intel Core i5-2500K Sandy Bridge 3.3GHz (3.7GHz Turbo Boost) LGA 1155 95W Quad-Core Desktop Processor Intel HD Graphics 3000 BX80623I52500K

Motherboard: ASUS P8P67 PRO (REV 3.1) LGA 1155 Intel P67 SATA 6Gb/s USB 3.0 ATX Intel Motherboard

Video Card: EVGA 012-P3-1571-KR GeForce GTX 570 HD w/Display-Port (Fermi) 1280MB 320-bit GDDR5 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card

Boot Drive: Corsair Force Series 3 CSSD-F120GB3A-BK 2.5" 120GB SATA III Internal Solid State Drive (SSD)

RAM: G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Desktop Memory Model F3-10666CL9D-8GBRL

Storage HD: SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" Internal Hard Drive -Bare Drive

Windows_NT6_BSOD_jcgriff2 attached with PERFMON.html file inside the folder.

No DMP files included in upload please try this method


We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

I apparently didn't have minidump enabled. However I did have kernel memory dump if that helps? I wouldn't know where to find the dmp file for that however.

Whilst awaiting further diagnosis, I can tell you it happens whe a system critical process or thread exits or is terminated unexpectedly. Without it the system cannot function and calls a stop.
MS has a knowledge base series of articles on this which may be of interest.
Connecting a hard disk drive in slave only mode leads to system halt during resume from standby

cyclic said:

Whilst awaiting further diagnosis, I can tell you it happens whe a system critical process or thread exits or is terminated unexpectedly. Without it the system cannot function and calls a stop.
MS has a knowledge base series of articles on this which may be of interest.
Connecting a hard disk drive in slave only mode leads to system halt during resume from standby

I read the page and attempted their "recreate" section (to cause it to happen once more) and manually placing my computer in sleep/standby and resuming did not make it stop error once more.

I'm fairly new to SATA but I don't recall seeing jumpers on my SSD to set it to slave. I might have overlooked it however. Is there any way to tell short of opening the case and looking?

That is only one of several scenarios given by MS.
Perhaps if you post the dump files someone may be able to shed more light on it.

For some reason after it crashed again (finally, it took a while) I went to my Windows/Minidump folder and there was nothing in it.

However to be safe I wrote down the crash info:

KERNEL_DATA_INPAGE_ERROR

STOP: 0x0000007A (0xFFFFF6FC40009A70, 0xFFFFFFFFC000009D, 0x00000001DA590860, 0xFFFFF8800134E788)

Ntfs.sys Address FFFFF8800134E788 base at FFFFF8800125B000 Datestamp 4d79997b

Any idea why it wouldn't have saved a crash file?