BSOD page_fault_in_nonpaged_area in windows 7

sam234 · 04 Jan 2014

This started with my laptop freezing. On fixing which now I have started getting BSOD - page_fault and sometimes BAD_POOL_HEADER.

Initially BSOD would appear every 5-10 mins of booting. I did a windows restore from Samsung recovery solution which came pre-installed and was able to fix it but which resulted in text disappearing from icons and windows. On doing sfc /scannow and startup repair the text too got fixed.

Now again after installing Mozilla and chrome, BSOD's have started.Also, on trying to start Mozilla got error - could not load XPCOM

I have already run 360Amigo System speedup and CCleaner to cleanup registry. Did sfc /scannow 3 times. Also did check disk from Disk>properties.

scannow always resulted in same message - some files are corrupted which could not be fixed.

Now BSOD seems to appear a bit late but it has not gone and also Mozilla seems to have start working.

Attaching dump from SF Diagnostic Tool

Antivirus: MSE
Operating system: Windows 7 Home

Note: few months back, my D drive (named as K) suddenly got missing. It could be seen in disk management, but not in windows. I did a repartition when doing windows restore.

sam234 · 06 Jan 2014

Can anyone help here please

Arc · 06 Jan 2014

Hi sam234.

Browse to C:\Windows\Fonts, and delete the fonts those you have lately installed before the BSODs started to occur.

If you have not installed any font, but installed any program or game that installed any font at its own, delete those fonts.

If you cannot access to the fonts folder in normal mode, try in safe mode.

Then rebuild the font cache. Go to C:\Windows\System32\ and delete the "Fntcache.dat" file there. Then restart the computer. On restart, a fresh font cache will be built.

Let us know the result.

sam234 · 06 Jan 2014

I haven't installed any font manually. How do i know which new fonts were installed by softwares. I have noticed that bsod triggers now when i use chrome
But it seems to work fine wen using IE

Arc · 07 Jan 2014

Can you access to the fonts folder manually, without any trouble? If so, do it:

1. Go to C:\Windows\Fonts. Right click. Choose Short By > More.

Attachment 300680

2. In the "Choose Details" dialog, Check "Date Modified" (the Item lower that one indicated in the pic)> OK

Attachment 300681

3. Now Sort fonts by "Date Modified" ...... observe which are contemporary to the BSODs. Delete those.

Attachment 300682

Now delete the "Fntcache.dat" file and observe how it goes.

If there is any further BSOD after doing it, upload the dumps.

sam234 · 07 Jan 2014

Nope. On selecting FONTS folder, BSOD is triggered. But I can access restore font settings through control panel. How do I verify if fonts have been restored?

Arc · 07 Jan 2014

sam234 said:

Nope. On selecting FONTS folder, BSOD is triggered. But I can access restore font settings through control panel. How do I verify if fonts have been restored?

That is the confirmation that the Fonts are behind the BSODs.

Do you have windows installer disc? If so, follow the idea of Copy & Paste - in Windows Recovery Console .... browse to C:\Windows\Fonts. Delete all fonts other than these ones: List of Microsoft Windows fonts

If you dont have the installer disc, you can use any live linux distro (Ubuntu, Puppy, anything) to boot from, and do it.

When done, boot back to windows normally. Go to C:\Windows\System32\ and delete the "Fntcache.dat" file there.

Let us know the results.

sam234 · 17 Jan 2014

Resolved! Thanks a ton :)

Arc · 17 Jan 2014

Let us know for any further issue. :)