BSOD Error 0x50 After New Windows Update

Now I'm pretty sure that the 0x50 Error that I got is from a Windows Update. Did you guys try doing a Memory Diagnostic Tool or a memtest86?

I haven't had problems with the new Windows Update at this point... But is it safe to delete FNTCACHE.DAT? Would it make a difference if I delete this file? I don't want to get a Blue Screen again, but I don't want to risk deleting a file that might cause problems for me down the road.

^ exactly why I am not doing the update and waiting for official fix.

After deleting it or renaming it, FNTCACHE.DAT is rebuilt on rebooting. Loads of people are reporting that this fix works and that the update KB2970228 is causing the issue. I decided to rename the file after the updates were installed but before rebooting, as a preventative measure because I am in the middle of doing important work on the PC. I never had a BSOD in the first place. KB2970228 is still installed on the machine. This particular update is to do with displaying the Russian currency symbol so it is hardly an important recommended update as Microsoft called it. Leave it out of your updates until they fix it and you should be fine. Regards, Brian

I've tried to rename the fntcache.dat file and deleting it, but nothing works. I always get the bluescreen on startup..driving me insane!

I think the problem might be something else... For me, everything worked out fine. I didn't need to rename the FNTCACHE.DAT file. I think my problem was updating 12 updates at the same time, which might have caused my computer to Blue Screen.

Have you tried restoring back to a point before all of the Windows Update?

There is an extensive guide to recovering a PC which has been posted by Microsoft. The updates are now acknowledged to have caused a problem on many PCs and it appears to be an Open Type font related issue. For those of you who have found that deleting the fntcache.dat file has not solved the problem then have a look at the known issue 3 method on this page as it deals with temporarily removing the Open Fonts. Then it recommends removing 4 updates which are causing the problem. Perhaps some of the other known issues listed may help also. MS14-045: Description of the security update for kernel-mode drivers: August 12, 2014 Regards and good luck with it.

lvt08 said:

I think the problem might be something else... For me, everything worked out fine. I didn't need to rename the FNTCACHE.DAT file. I think my problem was updating 12 updates at the same time, which might have caused my computer to Blue Screen.

Have you tried restoring back to a point before all of the Windows Update?

After many painful hours i managed to restore it at a point before the update. I didn't work the first time i tried it, but in my desperation I tried it one more time and it worked. Nothing has ever felt so good

I have now updated with every single update and no more bluescreen. might have been to many updates at the same time.

Glad that restore worked for you as I am reading elsewhere that restore is failing for many people. They have no restore points to revert back to for some reason. It appears that this issue manifests itself in many different ways on different systems. Regards