BSOD 0x50 and 0xF4 on multiple drives

mad0314 · 03 Feb 2013

BSOD 0x50 and 0xF4 started randomly.
I keep getting BSODs about 15 min after starting the computer. The first time it happened I was playing Eve with Teamspeak and a few Chrome tabs open. It kept happening and got to a point where it would crash on the splash screen. Whenever it BSODs, the computer doesn't recognize whatever drive was the boot drive. I noticed after the first few times, it BSOD and it booted into an old boot partition on my secondary drive, and from then on it would not recognize whatever drive was the boot drive at the time until a cold boot. It also happened when trying to run a 7 DVD. This makes me think its a hardware issue (motherboard?) but I want to make sure first. I tried all sorts of different configurations of RAM and slots, so I don't think its that.

Also, most of the time crash dumps fail.

Arc · 03 Feb 2013

Hello mad0314.

You supplied only one crash dump, that is a Stop 0x50, caused by Ntfs,sys.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff98002900000, 0, fffff880016152c4, 0}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!memcpy+b4 )

Followup: MachineOwner
---------

According to Carrona.org, STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

And, a Stop 0XF4 is a Storage device related bugcheck.

Update your SSD's Firmware. It is a OCZ-VERTEX2. Get the update from http://www.ocztechnology.com/ssd_tools/.

Also, have a look. It is very important.

No code has to be inserted here.

You must to free up some more disc space. Follow it: Hard Disk Space - Free Up and Recover . Also, you may use and external data storage for your data. Transfer them from C:, as early as possible.

An antivirus program and it's file system monitoring mechanism may also cause this issue, and AVG is a well known victim in this regard. Uninstall AVG using AVG Remover. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

You have noticed that the BIOS is also listed as a probable cause; and your BIOS version is not the latest.

Code:

BIOS Version/Date    American Megatrends Inc. V1.12, 7/22/2011

But go for it if only the other options failed.

Let us know the situation after applying the suggestions.
If possible, plan to update it.

mad0314 · 06 Feb 2013

I tried to do that but only managed to free up a bit of space. It kept BSOD-ing before I could get anything useful done. Now it's to the point where it crashes before it boots up again. When my hard drive is hooked up, it crashes almost immediately. When only the ssd is hooked up, I could gsometimes get a few minutes out of it, but it's now crashing on the splash screen. I was going to try to create a small partition on the drive, but booting off the Windows disc also crashes! I've rechecked my RAM, I even tried another motherboard I had.

It's it possible the processor or PSU cause this? It doesn't seem logical to me, but it's the only thing I haven't checked

Arc · 06 Feb 2013

It is caused by the Storage devices. The excessive usage of them.

To free it up, follow this method: Copy & Paste - in Windows Recovery Console

Back the data up externally.

mad0314 · 07 Feb 2013

Yes, it was the drives. I booted from a Knoppix USB and was able to apply ntfsfix to the hard drive, but unfortunately it is not recognizing the SSD anymore. When it boots up, it sees it for about a minute, then the entire system hangs for 15 seconds or so, and from that point on it doesn't see the SSD anymore so I haven't been able to attempt the same fix for the SSD. HDD is working fine, no BSOD. Would there be a way to hotplug the SSD once Knoppix is running and attempt it before it crashes?

Why did both drives fail in that way at the same time? Could it have been caused by malware, or did the failure of one drive somehow cause the failure of the other? I've installed MSE and running a full scan now either way.

Arc · 07 Feb 2013

mad0314 said:

Yes, it was the drives. I booted from a Knoppix USB and was able to apply ntfsfix to the hard drive, but unfortunately it is not recognizing the SSD anymore. When it boots up, it sees it for about a minute, then the entire system hangs for 15 seconds or so, and from that point on it doesn't see the SSD anymore so I haven't been able to attempt the same fix for the SSD. HDD is working fine, no BSOD. Would there be a way to hotplug the SSD once Knoppix is running and attempt it before it crashes?

Why did both drives fail in that way at the same time? Could it have been caused by malware, or did the failure of one drive somehow cause the failure of the other? I've installed MSE and running a full scan now either way.

Is there a special reason that you have used that Linux? I haven't seen any reason to apply any ntfsfix at that point of time, rather the ntfs corruption as I have noticed is a combination of multiple other factors. We should have tried to eliminate those, not to apply any Linux based fix.

Have you tried to free the SSD up?

Let us know about your system. Is the SSD and HDD both are bootable? If so, when you boot from the HDD, can you access the SSD in explorer?

Try re-seat the SSD.

mad0314 · 08 Feb 2013

The SSD had gotten to the point where it would not get recognized beyond BIOS. It would only be recognized in BIOS if power had been cut to the SSD. If the SSD started "cold," it would have a green light (I only found out about this LED after my last post). Anything past BIOS, whether any form of Windows including recovery, or Linux, whether hooked up from the start or hot plugged in the OS, it would cause a red/green (2 LED) light and from that point on would not be seen by BIOS or the OS, and would only revert to a green light after disconnecting the power to the SSD. I only managed to remove about 2GB from the SSD before I was no longer able to access it.

I followed the recommended instruction by OCZ to try to reset the drive.

If the drive fails to detect with red/green LED:

1. Switch off System.
2. Turn off the PSU, remove Power cord fm outlet.
3. Disconnect the SSD and all other drives.
4. Remove CMOS Battery.
5. Press PC case power btn for 20 secs to discharge caps.
6. Short the CLR CMOS jumper and leave all to 'drain' for about 30 minutes.
7. Remove jumper/Re-insert the Battery
8. Attach power/turn on PSU and configure CMOS to safe Defaults and set AHCI SATA mode.
9. Save CMOS settings, re-boot and switch off.
10. Connect the SSD back back to SATA port 0/1, switch on and boot to CMOS to check if SSD is detected.
11. If not, set any CMOS Hot Plug/External SATA settings to [DISABLED] on the SSD port and try again.
If yes:
12. Save CMOS and boot into a Bootable Linux Tools (USB or CD/DVD on SATA port 4/5) and Secure Erase/Force Flash latest Firmware.. (http://www.ocztechnologyforum.com/fo...-for-OCZ-SSD-s)..

If still No, follow steps 1-9 above.. then switch system back on and boot into CMOS again..
Then Hot Insert/Plug/Connect the SSD while in CMOS, by placing SATA Power lead on first, then SATA signal Cable.
Then save CMOS and re-boot back into to CMOS to check if SSD is detected. If yes, carry out procedure in step 12 again.

And it just keeps going back to the same thing, so there is no way to try to free up space on it.

mad0314 · 08 Feb 2013

OCZ has a bootable toolbox, I will see if it can update the firmware of the drive.

essenbe · 09 Feb 2013

What ports do you have and is the SSD plugged into an Intel port? If not, plug it into a port controlled by the chipset, especially port 0-1. See if that helps. If not, try going to disk management and if it is there with no drive letter assign it one. I don't know if this will work, but it does on some SSDs.

1. Plug in the drive's SATA power cable *only* (not the data cable)

2. Boot the PC and let it sit for around 30 minutes.

3. With the PC power still on, plug in the SATA data cable. Do not disconnect the power.

4. Press the PC's reset switch.
If it does not show up, go to disk management, see if you see it there, at the bottom section, right click it, select change drive letter or path, on the next screen click add, just use the letter Windows gives it, and click OK. If it wants to format it, don’t do it. It will erase all data on it.

mad0314 · 09 Feb 2013

I've been plugging it in to port 0 of the SATA 3 GB/s port that use the Intel controller shortly after it started messing up. I did get it to recognize the drive in Windows once by hot plugging (mentioned in my post above), tried to assign a drive letter to it and it ended hanging up the entire system. I will try again with those specific instructions.

To clarify, you mean pressing the reset switch on the case, correct?