BSOD 0X000000F4

[MaadDaawg]

BlaakHaat was cruiding along at 4.999 Ghz last night when it re-booted, except, it didn't reboot.

First it stopped due to a fan error looking for me to press F1, which I did, to only to be told it was checking nvram ???. Never came back so I shut it down hit the clear cmos and tried again. This time it gave me the error message that a windows file was corrupt and I should run chkdsk (on win 7 ??)

Each time I booted the raid card bios installed correctly and the raid was alive and well.

Tried a few more times going through the safe start menu trying self repair, sys restore, and even sfc /scannow ... nothing worked. The system could not even find Windows anymore. I was going to do a clean install, but it couldn't find any disk drives either :eek:

WTF - anyone ??

[Witchdoctor]

http://www.pcutilitiespro.com/repair-0x000000f4-stop-errors.aspx?Channel=111200&source=GoogleAdWorudsSearch&campaign=bsod_1&ad_group_name=0x000000f4&creative=10013216722&keyowrd=0x000000f4&matchtype=e&gclid=CNqc9eO15q0CFUSo4Aods1EwtQ

[MaadDaawg]

Can't get into windows :argh:

BIOS recognizes the RAID card and array, but windows does not see any drives at all. Neither my 4 disk array or my storage disk. Tried all the repair solutions ins safe mode but nada.

Booted into system mechanic repair disk but it didn't see the operating system either

Tried to load a fresh install .. didn't see any disks.

[Gunslinger]

I got the same bullshit this weekend on my gaming rig...I was not able to get it to recover or repair.

I saw that link this weekend when googling the problem. Can anyone confirm that app is safe ?

[MaadDaawg]

can you get into your operating system? Mine goes straight to bsod only :(

[GFDuke]

Are the drives and RAID card visible in the bios? I forgot...what motherboard are you on?

[Mr.Scott]

When you say "tried to load a fresh install", what exactly did you do?

[MaadDaawg]

Are the drives and RAID card visible in the bios? I forgot...what motherboard are you on?

Drives and the RAID card are visible in the BIOS. They're on the R3E black edition where they've worked well for a good amount of time. Windows cannot see the RAID ARRAY

When you say "tried to load a fresh install", what exactly did you do?

I put in an install disk and told it to install over the existing OS. It told me it could not install Windows because there were no hard drives in the computer. My other option was to load HDD drivers, but the RAID is controlled by the BIOS of the RAID card

what to do, what to do

:Dizzy::Dizzy:

I can only get into the safe mode text screen. It cannot self repair, it cannot restore because it says there is no operating system on the computer, if I try to go into safe mode it starts but then reboots, and if I run sfc /scannow it tells me there is already a scannow repair scheduled and to restart to complete the repair... in never completes the repair :argh:

[GFDuke]

So when you reset your bios, did you go back in and set it to boot to the RAID card? Grasping at straws here because i have no clue where your setup is at and what your config is. SATA mode set to SATA not RAID right?

Have you gone into the RAID card bios and made sure everything is ok there?

[MaadDaawg]

So when you reset your bios, did you go back in and set it to boot to the RAID card? Grasping at straws here because i have no clue where your setup is at and what your config is. SATA mode set to SATA not RAID right?

Right now I'm on system defaults. I've reset the boot configuration to boot on the raid card. I've tried starting with an OS that controlls plug n play and one that does not - no diff.

I get a cpu fan error (I've got my ram fan plugged in there?) then when I press F1 to continue it says "loading "vnram" (unless I've pressed the del key or the alternate startup keys first)

Very frustrating

Has an AMD 5870 in it, but I've pulled than and tried an nv 560Ti... no diff :Dizzy:

[Mr.Scott]

You're screwed. Bios sees raid card and array and the raid card sees the array, but neither can boot to it because the OS controls the registry for the boot order and required driver for the raid card..............and it's stuck in an endless loop waiting for the first scannow to be started or finished.
There is no repair. Wipe your OS drives and start from scratch.

[MaadDaawg]

That's what I figured, but, how do I wipe my SSDs in the array when I can't reach the operating system and windows setup doesn't see them? Can you do this in the BIOS?

[kikicoco1334]

i think you have to boot it from a flash drive or maybe boot it from a install drive and pull the driver from a flash drive of some kind i can't remember

i HATE raid cards and raid ANYTHING!

[Mr.Scott]

That's what I figured, but, how do I wipe my SSDs in the array when I can't reach the operating system and windows setup doesn't see them? Can you do this in the BIOS?
No. You have to split the drives and wipe them one at a time from another rig. Even a bootable thumbdrive won't see them through the raid card. You might be able to do it on the same rig through a bootable thumb drive if you run the drives one at a time off the mobos SATA ports, but that's only IF the bootable thumb drive can see the drives.
It would be easier to just run the SSD's through the USB on your laptop and wipe them that way.
I'd be more worried about what caused the corruption to start with.

[GFDuke]

If they're sandforce drives you should just use Secure erase. You don't need an OS to use secure erase. If i remember correct yours are the OCZ vertex 2. Correct?
Go here (http://www.ocztechnology.com/ssd_tools/) and get the OCZ Toolbox for your drives then follow the instructions in this thread. You have to burn the iso to a boot disk.

http://www.ocztechnology.com/files/ssd_tools/OCZ_Toolbox_Guide_7_11_2011.pdf

[Gunslinger]

I was able to get into windows, then after about 60 seconds it would lock up for about 3 minutes, then I would get the BSOD.

Then following the restart it would not see the SSD.

[Neuromancer]

When doing the reinstall/repair are you loading the RAID card drivers?

Also if you do get around to secure erasing the SSDs (which is the only way to properly erase an SSD) you might as well go ahead and update the firmware on them too if there are some updates available.

You can do it from the R3E with one of two methods. (I use a partedmagic boot stick) you will either have to connect them to the marvel controller onboard, or run hotswap mode on the intel ports, and detach/reattach them after parted magic loads up.

Pmagic might even work on the RAID (albeit with array broken) I am not certain however what storage controllers linux supports natively.

[MaadDaawg]

If they're sandforce drives you should just use Secure erase. You don't need an OS to use secure erase. If i remember correct yours are the OCZ vertex 2. Correct?
Go here (http://www.ocztechnology.com/ssd_tools/) and get the OCZ Toolbox for your drives then follow the instructions in this thread. You have to burn the iso to a boot disk.

http://www.ocztechnology.com/files/ssd_tools/OCZ_Toolbox_Guide_7_11_2011.pdf

Cool, thanks Bro :) Your memory is precise, vertex 2s. Ordered a vertex 3 to be delivered tomorrow to get the gamer up and running faster :D

[MaadDaawg]

I was able to get into windows, then after about 60 seconds it would lock up for about 3 minutes, then I would get the BSOD.

Then following the restart it would not see the SSD.

yeah, same thing I had :shock::ohcrap:

[MaadDaawg]

No. You have to split the drives and wipe them one at a time from another rig. Even a bootable thumbdrive won't see them through the raid card. You might be able to do it on the same rig through a bootable thumb drive if you run the drives one at a time off the mobos SATA ports, but that's only IF the bootable thumb drive can see the drives.
It would be easier to just run the SSD's through the USB on your laptop and wipe them that way.
I'd be more worried about what caused the corruption to start with.

i booted around 4.8ghz at 1.46 vcore, and upped the bclk until I hit 4.999 then watched the temps until ... it died. Temps were really low with the rads in the window, but the vcore was probably too low. Not sure what caused it :Dizzy:

[Mr.Scott]

i booted around 4.8ghz at 1.46 vcore, and upped the bclk until I hit 4.999 then watched the temps until ... it died. Temps were really low with the rads in the window, but the vcore was probably too low. Not sure what caused it :Dizzy:
What was the ram at? Data corruption is usually a ram issue. Yes, I know you Intel guys don't see this very often, but it does happen. It's quite common on AMD rigs.

[GFDuke]

Data corruption is always a risk. Only crazy people push their gaming rigs beyond desireable specs. :taunt:

This is a better guide on how to Secure Erase using the OCZ toolbox boot disk DAAwg.

http://www.ocztechnologyforum.com/forum/showthread.php?89670-Bootable-Firmware-updater-for-SandForce-Driven-OCZ-SSD-s.&p=645836&viewfull=1#post645836

[Neuromancer]

Good link :)

That is the same tool I use (partedmagic) I just have it on a bootable usb stick. it works for all SSDs :)

http://partedmagic.com/doku.php?id=start

@mrscott. yes Intels controller is VERY forgiving. I was able to boot and run my X58 with a dead stick of RAM!

[Mr.Scott]

@mrscott. yes Intels controller is VERY forgiving. I was able to boot and run my X58 with a dead stick of RAM!
LOL. That's awesome.