Random BSODs with Stop code 0x000000F4 in Win 7 Ultimate x64

[spazmaster666]

So, in the past I'm usually someone that can fix most of the issues with my PC builds but my knowledge on SSDs is still somewhat rudimentary so I'm trying to figure if my recent string of BSODs is due to my SSD failing or if due to some other hardware issue.

In the past couple of days I've been getting somewhat random BSODs (once while playing Skyrim, twice while just using Chrome) all with the same stop code of 0x000000F4. So after doing some research I've discovered that this stop code is often attributed to hard drive issues. So I did a scan of both of my system drives (my SSD as well as a 2TB hard drive I use to store most of my applications/page file, etc.) and while the hard drive was fine, the SSD did have some sort of error which the disk check seemed to fix. After clearing the page file and resetting it I again experienced an identical BSOD with the same stop code.

The last two times I received the BSOD were during pretty routine browsing in Chrome with a few background apps running. Before the BSOD occurred, Windows Explorer crashed along with Chrome and a bunch of the background apps with similar error messages. This was an identical situation to the previous BSOD.

So my question is, are these the signs that my SSD (a 128GB Corsair Nova) is dying? Or could it be some other hardware issue or perhaps my Windows install is corrupted? Note that before this I've gone through several months without any issues with my system.

 

[zigzag3143]

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.

If you are overclocking STOP

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.

 

[spazmaster666]

Okay, I've uploaded my minidump folder.

 

[zigzag3143]

Okay, I've uploaded my minidump folder.

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files


Old drivers from as far back as 2004

lirsgt.sys    3/6/2004 2:53:01 PM             
SiWinAcc.sys    11/1/2004 2:23:29 PM         
RTCore64.sys    5/25/2005 1:39:12 AM                           
SiRemFil.sys    10/18/2006 5:20:39 PM                  
pcouffin.sys    12/5/2006 9:39:30 AM           
ezplay.sys    4/30/2007 5:08:55 AM[/B][B] 
Si3132r5.sys    6/1/2007 12:08:28 PM                     
RivaTuner64.sys    7/17/2007 2:13:42 PM                       
ctac32k.sys    7/2/2008 3:38:22 AM         
WinRing0x64.sys    7/26/2008 8:29:37 AM                          
atksgt.sys    10/20/2008 2:50:38 AM        
mv61xx.sys    3/19/2009 10:48:21 PM                         
iaStorV.sys    4/8/2009 11:57:17 AM           
[/B]

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[spazmaster666]

Okay, I've uploaded my minidump folder.

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files


Old drivers from as far back as 2004

lirsgt.sys    3/6/2004 2:53:01 PM             
SiWinAcc.sys    11/1/2004 2:23:29 PM         
RTCore64.sys    5/25/2005 1:39:12 AM                           
SiRemFil.sys    10/18/2006 5:20:39 PM                  
pcouffin.sys    12/5/2006 9:39:30 AM           
ezplay.sys    4/30/2007 5:08:55 AM[/B][B] 
Si3132r5.sys    6/1/2007 12:08:28 PM                     
RivaTuner64.sys    7/17/2007 2:13:42 PM                       
ctac32k.sys    7/2/2008 3:38:22 AM         
WinRing0x64.sys    7/26/2008 8:29:37 AM                          
atksgt.sys    10/20/2008 2:50:38 AM        
mv61xx.sys    3/19/2009 10:48:21 PM                         
iaStorV.sys    4/8/2009 11:57:17 AM           
[/B]

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

So you're saying the BSOD is due to a software issue (i.e. drivers) likely not due to hardware? I uninstalled SPTD as you suggested but it seems strange that I would suddenly run into this problem when I've had that driver installed for months without any problems. I will look into those old drivers as well. Hopefully I won't get any more bugchecks after this.

 

[zigzag3143]

Okay, I've uploaded my minidump folder.

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files


Old drivers from as far back as 2004

lirsgt.sys    3/6/2004 2:53:01 PM             
SiWinAcc.sys    11/1/2004 2:23:29 PM         
RTCore64.sys    5/25/2005 1:39:12 AM                           
SiRemFil.sys    10/18/2006 5:20:39 PM                  
pcouffin.sys    12/5/2006 9:39:30 AM           
ezplay.sys    4/30/2007 5:08:55 AM

[B] 
Si3132r5.sys    6/1/2007 12:08:28 PM                     
RivaTuner64.sys    7/17/2007 2:13:42 PM                       
ctac32k.sys    7/2/2008 3:38:22 AM         
WinRing0x64.sys    7/26/2008 8:29:37 AM                          
atksgt.sys    10/20/2008 2:50:38 AM        
mv61xx.sys    3/19/2009 10:48:21 PM                         
iaStorV.sys    4/8/2009 11:57:17 AM           
[/B]

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

So you're saying the BSOD is due to a software issue (i.e. drivers) likely not due to hardware? I uninstalled SPTD as you suggested but it seems strange that I would suddenly run into this problem when I've had that driver installed for months without any problems. I will look into those old drivers as well. Hopefully I won't get any more bugchecks after this.

BSOD's are almost always a combination of things. Your daemon tools/alcohol may have been working fine until it combined with something like a windows update, or any thing else you may have installed.

 

[spazmaster666]

Okay, so after uninstalling SPTD.sys and a few other drivers, my system ran fine for about 12 hours but then again ran into the F4 BSOD. I've attached the dmp file. I'm beginning to suspect I may have to do a fresh install of Windows (which would probably mean that I will have to purchase a new SSD). I just wish I could figure out what is triggering the BSOD though. I looked through the event viewer and it wasn't much help.

Edit: I just ran a System File Check and it did come up with some errors that could be fixed. Up after opening up the CBS.log it looks like the errors are not core system files. I've also uploaded that in case it helps.

 

[zigzag3143]

Okay, so after uninstalling SPTD.sys and a few other drivers, my system ran fine for about 12 hours but then again ran into the F4 BSOD. I've attached the dmp file. I'm beginning to suspect I may have to do a fresh install of Windows (which would probably mean that I will have to purchase a new SSD). I just wish I could figure out what is triggering the BSOD though. I looked through the event viewer and it wasn't much help.

Edit: I just ran a System File Check and it did come up with some errors that could be fixed. Up after opening up the CBS.log it looks like the errors are not core system files. I've also uploaded that in case it helps.

You obviously have not updated the old drivers.