I've recently started having an issue with a BSOD occurring sporadically with a stop code of 0x000000F4. From doing some reading, it is a hardware issue and many people are getting it with SSD's installed.
These are my current specs:
[img_thumb]http://i.imgur.com/zjBvs.png[/img_thumb]
[img_thumb]http://i.imgur.com/2JTF5.png[/img_thumb]
[img_thumb]http://i.imgur.com/j5KwJ.png[/img_thumb]
People say that it has something to do with outdated SSD firmware.
Things I've tried:
Clean windows install
Changing minidump directories (untested)
Creating the minidump folder in C:\Windows\Minidump manually (untested)
I originally thought it had something to do with running low on RAM while playing Tekkit (a RAM shitting minecraft mod), but then I realized it was occurring before I had even installed the mod. The BSOD occurs at random times and is usually led on by the program I am using locking up. It does not stop responding and gray out like a normal app crash, it simply just freezes in place. My mouse can still move but it essentially becomes useless as each open program locks up one by one. Eventually, the taskbar disappears. Winamp will continue playing music until the BSOD comes. This entire ordeal can last up to 3-4 minutes.
If I remember correctly this started about two weeks ago, where I would come back to my computer and see it at the OS selection screen. At the time I had Windows 7 as well as Windows Server 2008 R2 running on two separate drives. My drive heirarchy is as follows: On C:\ is Windows (it's MBR) and all Applications. On D:\ is Steam, and various games. On E:\ was all Server files as well as the installation itself, after I did a clean install, I left it empty. Note: C:\ and D:\ are SSD while E:\ is an HDD.
[editline]15th August 2012[/editline]
Just tried to install some updates, went to do some laundry, I come back and I'm left with a 0x07A BSOD. Apparently that's a KERNAL_INPAGE_ERROR or something. It has to do with virtual memory which does make sense because just before I restarted to install the updates, I changed the page file to include all three drives. I guess I'll change it back now.
[editline]15th August 2012[/editline]
Left my computer alone, playing music, to go finish cleaning my room. Took about 45 minutes to hit BSOD again. Still no kernel dump.
Ran every test in HDTune and Memtest 86+ both came up entirely clean. I'm running out of ideas here, and it seems nobody on facepunch knows what a blue screen is.
[editline]15th August 2012[/editline]
I guess I'll continue talking to myself, but anyway, I attempted to use a user-initiated bugcheck when the lockup began. It worked, but still would not write a memory dump.
What are the parameters followed by the F4 error? Ex. (0x00000003, 0x8A572020,0x8A572194,0x805D11F8)
Try updating your SSD firmware. There is probably a download and a tool to do it at the manufacturers website. I think you have Crucial drives, so go on from here: [url]http://www.crucial.com/eu/support/firmware.aspx[/url]
[QUOTE=U.S.S.R;37266629]What are the parameters followed by the F4 error? Ex. (0x00000003, 0x8A572020,0x8A572194,0x805D11F8)[/QUOTE]
I know for a fact, the first parameter is 0x03, like you wrote. I'm pretty sure that the termination that caused the crash was a process as opposed to a system thread.
Next time it happens, I'll write 'em down.
[editline]16th August 2012[/editline]
[QUOTE=Drumdevil;37266695]Try updating your SSD firmware. There is probably a download and a tool to do it at the manufacturers website. I think you have Crucial drives, so go on from here: [url]http://www.crucial.com/eu/support/firmware.aspx[/url][/QUOTE]
I'm going to make this my last resort, since it may or may not wipe my drive. Also because there is a small chance I can brick it.
Also, if I do have to wipe it; do either of you know of any software that I can use to make an exact copy of both drives and put them on a third drive to transfer back later?
[editline]16th August 2012[/editline]
Just got another one. Here's the info:
STOP code: 0x000000F4 (0x0000003, 0xFFFFFA800692CB30, 0XFFFFFA800692CE10, 0XFFFFF80002F8A720)
[editline]16th August 2012[/editline]
how the fuck do you read a specific stack address? The parameters point to extremely useful information that I can't even read. It's like my computer doesn't want to me to know anything.
Just to let you guys know, I'm doing everything I possibly can to avoid purchasing anything new.
[QUOTE=Adelle Zhu;37272746]
[editline]16th August 2012[/editline]
how the fuck do you read a specific stack address? The parameters point to extremely useful information that I can't even read. It's like my computer doesn't want to me to know anything.[/QUOTE]
You can't really read a stack address unless you're a seasoned software/hardware developer (Unless I'm wrong and there is an exception), the Hexadecimal code here is meant to be translated to an individual error code/process allocation/parameter; it can, however be compared to a generic list for BSOD errors.
It seems like you do have an SSD problem (from what I can tell), you should use something like Norton Ghost as cloning software to back up everything. You can get 1TB external drives for like, $89/£56 in some places. You might have to do as Drumdevil instructed.
[editline]17th August 2012[/editline]
If you are still reluctant, I recommend you contact Microsoft, if they do say that your SSD is definitely the cause of the problem, follow their instructions. A warranty might be something to have at hand, too, if you have one.
[editline]18th August 2012[/editline]
[url]http://www.carrona.org/bsodindx.html#0x000000F4[/url]
Here is a comprehensive little 'guide' about the certain error you are having. It also contains a lot more information about Hexadecimal values and STOP error parameters and such. It seems doubtful though, that you have an issue regarding to your disk drive hierarchy as your C:/ drive is connected to the master channel SATA connector, correct?
[QUOTE=U.S.S.R;37292009]You can't really read a stack address unless you're a seasoned software/hardware developer (Unless I'm wrong and there is an exception), the Hexadecimal code here is meant to be translated to an individual error code/process allocation/parameter; it can, however be compared to a generic list for BSOD errors.
It seems like you do have an SSD problem (from what I can tell), you should use something like Norton Ghost as cloning software to back up everything. You can get 1TB external drives for like, $89/£56 in some places. You might have to do as Drumdevil instructed.
[editline]17th August 2012[/editline]
If you are still reluctant, I recommend you contact Microsoft, if they do say that your SSD is definitely the cause of the problem, follow their instructions. A warranty might be something to have at hand, too, if you have one.
[editline]18th August 2012[/editline]
[url]http://www.carrona.org/bsodindx.html#0x000000F4[/url]
Here is a comprehensive little 'guide' about the certain error you are having. It also contains a lot more information about Hexadecimal values and STOP error parameters and such. It seems doubtful though, that you have an issue regarding to your disk drive hierarchy as your C:/ drive is connected to the master channel SATA connector, correct?[/QUOTE]
Define, master sata channel
[editline]18th August 2012[/editline]
None of his suggested KB articles match my issue. It happens at random, but they are few and far between.
[QUOTE=Wikipedia]Master/slave is a model of communication where one device or process has unidirectional control over one or more other devices. In some systems a master is elected from a group of eligible devices, with the other devices acting in the role of slaves.[/QUOTE]
[url]http://en.wikipedia.org/wiki/Master/slave_(technology)[/url]
If your C:/ drive (or wherever the windows installation is, but you said C:/) isn't set as a master manually, it can cause issues, though that may not be the problem here as you are getting random crashes and not immediate ones. It's your best bet besides the firmware update.
[editline]18th August 2012[/editline]
Actually, scratch that, I'm an idiot. SATA devices don't use a master/slave system.
[editline]18th August 2012[/editline]
I can only really put it down as Drum did, a firmware issue. I'd gone on a stupid tangent without realizing something simple, sorry.
I think you could still take a look at the boot order, though.
On my Adata drive updating the firmware was as easy as 1 2 3. Didn't need to format etc. Download the manufacturers flash application, perhaps a separate firmware file, open application and done.
It seems easy, but I'm just following Crucial's warnings of a possible wipe or brick.
I'm going to check the boot order now, but do either of you know why my motherboard only let's me select three items in the order menu? It's always my Games SSD, the CD Drive, and "Disabled". The Primary SSD is never on that list.
[editline]18th August 2012[/editline]
I just checked the boot order and M4SSD2 is first, M4SSD1 isn't even listed even though they are in SATA 1 and 2, respectively. They are the same type of SSD but one is newer than the other and is running a different firmware (M4SSD2). I bought them a few months apart.
[editline]18th August 2012[/editline]
Also, just for good measure I changed the SATA cable on SSD1 (Games and Stuff). I have to find another SATA cable to change SSD2 with.
[editline]18th August 2012[/editline]
I got bored and ran Startup repair. It destroyed my theme by unpatching all the custom system files. I'll stick with the default theme. Maybe it'll do something.
Your drives should all be running the same firmware. The issue with the boot order is a bit strange, I'll have to wake up a bit before I can think with logic that is above the level of a spongiform Encephalopathy ridden cow.
After updating the firmware almost 4 hours ago, I think I can safely say that it was the solution. Though I'm not holding my breath. I'll wait another few hours before I call it.
[editline]18th August 2012[/editline]
It's been almost 6 hours since I updated my firmware. No crashes whatsoever. Thanks for all your help gentlemen.
You can thank Drumdevil alone, all I did was babble about. Anyway, have a nice time.
Sorry, you need to Log In to post a reply to this thread.
