Solved BSOD at Startup. Memory or Drive failure? Page_Fault_In_Nonpaged_Area

[cleareyes]

Hi,
I'm trying to troubleshoot what's gone wrong with my computer, and I was hoping someone could help. I self built this ~2 years ago, and haven't had a problem until now.
Build Here (Intel Core i5-3570K, Asus GeForce GTX 780, Fractal Design Define R4 (Black Pearl) - System Build - PCPartPicker)
I turned my computer on this afternoon and Windows failed to start. I tried repairing with no luck, and there are no restore points available. I stored my OS on my SSD which makes me think my SSD has failed. I've tried using working power cables / SATA cables to try and rule out the connection being the issue. I've changed the RAM slots to rule out bad slots too.

Here is the error image from the BSoD I get when I try to start Windows normally.
http://i.imgur.com/fGKLEPK.jpg

Also, these are the two errors that appeared after trying to run Startup Repair/Diagnose:
http://i.imgur.com/DM9sTAL.jpg

Any help on trying to diagnose this would be greatly appreciated. I've seen other threads posted here before about this error, but they seemed to be able to start Windows, however.

 

[Arc]

Sometimes a BSOD may make the system unbootable. Follow it:
Troubleshooting Windows 7 Failure to Start

Let us see if the steps can make the system bootable.

Also try to boot the computer in http://www.sevenforums.com/tutorials/69585-safe-mode.html .... if it boots, post the data following the Blue Screen of Death (BSOD) Posting Instructions.

Actually a stop 0x50 may be caused by both the physical RAM and the drivers. It is impossible to point one of them out without checking the crash dump.

 

[cleareyes]

Hi thanks for the response. I tried booting into Safe Mode following the instructions you provided but I got the BSoD every time. I also tried booting from "Last Known Good Configuration" which let me see the cursor for a few moments before blue screening.

Would you recommend anything else?

 

[Arc]

Yes, gregrocker

I am requesting him to have a look at your thread. Follow his guidance. He is the best person to deal with these issues.

 

[gregrocker]

Have you started the steps for http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html yet?

Please proceed and report back results as you go as other steps may be indicated. Feel free to ask back any questions. I would do run at least two of the bootable AV's if you can't get into Safe Mode to run Malwarebytes. Repairs may not work if the PC isn't cleared of any infection first.

 

[Arc]

Lately I came to know about it: http://www.sevenforums.com/news/341...hes-bring-blue-screens-death.html#post2855054

KB2982791

If you have got this windows update installed lately? Then do what they have done.

I solved the problem by deleting c:\Windows\System32\FNTCACHE.DAT using command prompt within F8 menu.

It appears that the problem is down to a corruption in the File c:\Windows\System32\FNTCACHE.DAT caused by the Update though there is some speculation as to wether one or several of the KB's cause the corruption.

 

[cleareyes]

Hi guys! Thanks for all the suggestions. Apologies for the delayed responses. Work has been rough lately. So I am able to boot using a Linux USB boot drive and access all of my files which leads me to believe this isn't a Hardware error. I did recently install a boatload of Windows Updates that day before it died (I update regularly, though). If that doesn't work, I will try following the guide provided by gregrocker and report back.

 

[cleareyes]

Lately I came to know about it: http://www.sevenforums.com/news/341...hes-bring-blue-screens-death.html#post2855054

KB2982791

If you have got this windows update installed lately? Then do what they have done.

I solved the problem by deleting c:\Windows\System32\FNTCACHE.DAT using command prompt within F8 menu.

It appears that the problem is down to a corruption in the File c:\Windows\System32\FNTCACHE.DAT caused by the Update though there is some speculation as to wether one or several of the KB's cause the corruption.

I'm happy to say this was the exact problem. I deleted it while running the Linux USB boot drive, and it booted right up. Thank you SO much for your help. This saved me a lot of headaches and potentially $$$

 

[Arc]

You are welcome.

A bad update caused this exact issue worldwide, in a great rate.