BSOD every hour, STOP: 0x000000F4

[bradisdrab]

BSOD randomly, after an hour or so, STOP: 0x000000F4

I built this machine about a year ago and its been a really stable work box up until really recently. Now it seems like every hour or so it gets 'stuck' freezes up and displays a BSOD.

The first couple times it happened it gave a 'KERNAL_DATD_INPAGE_ERROR" 0x0000007A

So I've scanned the disks looking for bad sectors, defragged, updated the intel drivers, rolled back with a system restore, and pulled the memory out, one by one, but I'm still getting these BSODs.; Now it seems to be consistently the F4 error.

I'm posting this quickly since I'm sure it'll freeze soon, please let me know if there is any additional info I could provide to make troubleshooting this any easier. I'd love to avoide completely reformatting and reinstalling, especially if that wouldn't even help.

I'm attempting to upload the zip of my mini dump now...


thanks,
-brad

 

[bradisdrab]

added minidump


System specs;
OS Windows 7 Pro (64-bit OS) CPU Intel core i7 960 @ 3.20GHz 2.00GHz Motherboard AS Rock x58 Extreme Memory 12GB 16000 Graphics Card(s) 2x Nvidia GeForce 8800 GT

 

[bradisdrab]

I was just typing a bit more info when it happened again, twice now since making this thread.

This seems to happen no matter what I'm doing, even if I leave it on without any programs running.

If I'm working when it happens, after approx an hour or so, the cursor starts spinning/loading, and the program hangs. I ctrl+alt+delete, and it goes to blank, black screen with cursor, then BSOD with the STOP error. Then if I've got it set to, it auto-restarts but hangs in BIOS just after memory test. Then I power it down, and startup, back to windows... etc.

Are there any other steps I could be trying? Would newer minidumps help, or perhaps a full or Kernal dump?

any help would be greatly appreciated!
thanks,
-brad

 

[bradisdrab]

I restarted into safe mode to test it, and left it alone; it BSOD'd and restarted itself again.

I zipped up a new copy of the minidump and everything from the forum tool, attached here;

anyone have any pointers?

thanks!

 

[Arc]

The dumps you uploaded, the latest one is of 19/08
View attachment 235423

 

[bradisdrab]

Thank you for looking,

So it isn't making a new minidump? I've set it to do so more than once, (using the first two methods here http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html ) but the last BSOD didn't hold on the blue screen and auto reset even though I had set it not to auto reset. Now I'm really confused. Is it possible its crashing before the dump can be written, or interferring with it?

Here is a photo of my typical BSOD, it never lists anything after initializing...

I'm resetting it for a kernal dump now, (confirmed from the command prompt as setting 2) and I'm restarting to be sure it takes the setting. Then I'm going to wait for it to happen again.

Or would trying for a new minidump be better?

 

[Arc]

According to Carrona.org, STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack.

Start from virus scanning. http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

Let us know the results.

 

[bradisdrab]

My mistake, that was the pre CHKDISK error BSOD. This is the current recurring one;

Windows defender sounds like it'll be worth a shot, trying it now.

 

[Arc]

1. Reseat the sata and power.
2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
3. 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.
4. Update your SSD'd firmware.

 

[bradisdrab]

I downloaded the Windows defender and while I was waiting for it I found a driver for my video cards which was newer than what I had currently installed, so I installed the new driver for my Video cards. Then rebooted.

As I was setting up the USB drive for defender it BSOD'd with a new error x124, picture below;

But this time it looks like it made a new dump! (attaching it now)

I ran windows defender and it didn't turn up anything.

I'm going to confirm that it will dump again when it nexr freezes and I hope something is obivious in the new dump. Please let me know.

thank you!
-b

 

[Arc]

http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696

 

[bradisdrab]

I haven't seen a repeat of that error and I've had three more of the xF4 with no dump. I think it had to be related to the nvidia update, which seems good now.

I'm currently running the seagate DOS disk scan to see if it may be HD related, then I'll see about any firmware updates I can make to the SSD.

Is there any way to check or test the MoBo drivers? Or all of them? Or should I just uninstall/update/reinstall with the best/newest I can find?

 

[bradisdrab]

It took all day but DOS SeaTools finished and passed both drives, looks like they are clear.

 

[bradisdrab]

I downloaded the firmware update for my Crucial m4 SSD, which took a bit of time. Then it crashed with the 0xF4 error and no dump (even though it is set to)

I've restarted and applied the update and am now waiting to see if it happens again.

*fingters crossed*

 

[Arc]

F4 is storage related crash. disc check plus firmware update should solve it.

But as you got stop 124, you should pay attention to it too. As long as there is a hardware related error, the crash will continue to occur.

 

[bradisdrab]

Thanks!

The firmware update seems to have helped a lot. My machine has been up for 24hrs now without any recurrence of the f4.

I'm still keeping my fingers crossed but I'm far more hopeful that it's fixed now.

 

[Arc]

Thanks!

The firmware update seems to have helped a lot. My machine has been up for 24hrs now without any recurrence of the f4.

I'm still keeping my fingers crossed but I'm far more hopeful that it's fixed now.

Me too, as far as there is stop 0x124. If you get another one, dont be late, follow http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696 step by step. You are to point the problem hardware out and replace it, and only then the issue will be solved.