0xF4 0x3 BSOD and no more startup

mrmaia

Distinguished
Aug 9, 2011
598
0
19,010
Good afternoon guys.

Yesterday I was just surfing the Web when my systrem crashed all of a sudden displaying the following code on a BSOD:

STOP: 0X000000F4 (0x0000000000000003, 0xFFFFFA800ED6FB30, 0xFFFFFA800ED6FE10, 0xFFFFF80003DCCCB0)

From this on, my computer won't recognize my system and ask for a boot disk.

I use a SSD for booting and a HD for data.

When I try using the System Recovery thru my Win7 DVD, it not only does not recognize my Win7 but also asks me to find drivers for my disk, and I have no idea of what it means.

Calling the command prompt from the DVD prompts initially for the X:\Sources path, and I cannot run chkdsk right away - it says X: is write protected. Switching to C: and allowing it to dismount works though, but chkdsk /r says no problem was found. The computer worked for a while afterwards, but I got the same BSOD again after a few hours and had to start over. I'm currently running chkdsk again.

Of all the possible fixes, I'd like to avoid clean formatting as I have a truckload of data I wouldn't like to lose.

Thank you!
 


Thank you for your reply, but I'd like to check the source of this info. If you can post it I'll be thankful.
 


650W - It's a Corsair HX650. Now I'm curious, what could the PSU do to cause a process-related BSOD?

I'll unplug and switch ports as soon as my chkdsk finishes, which will happen in a couple hours.

Thanks for your help!
 

OK, if the PSU is weak, lets say 450Watts would be weak for your set up and do just that, BSOD sometimes.

Or it could be the RAM and other 1000 things.
Faulty PSU can corupt HDD's.

 

its not likely to be the psu. I suggest getting your hard drive manufacturers diagnostic util to check for issues after you use chkdsk, also run memtest86+ to check for memory errors. You may just need to reinstall windows. If you have a spare drive, install windows on that and see if it boots.
 


Nothing, last time I instaled something was 2 weeks ago. And no device also.



Memtest ran earlier because of another issue and detected no errors, but I will try scanning my disks later.


Switching my boot drive to the Marvell SATA controller made it work, but I didn't give it enough time to say it's fixed. If it does, can I say it's a MB problem?