BSOD Bad Pool Error / Page Fault in non-paged area

deanlove · 02 Jan 2014

Any help on this would be appreciated - the PC crashes on boot (during the 'loading windows' screen) if I try and do a normal boot. Safe mode works, but then I get Bad Pool Error if I try and browse to any complex website (simply stuff works, but this one doesn't, for example - I assume it's Javascript or Flash crashing it).

Plus running many applications (including Notepad) leads directly to a Page-fault in non-paged area result.

Things I've tried: full scans with Avast and Malwarebytes, startup recovery console from the disc and all the options there including Startup Repair multiple times and SFC -scannow, error checking the drive with chkdsk and Partition Magic.

I tried driver verifier, but that was when the computer would still boot, it stopped it booting entirely (the earlier dmp files will be from that, the ones from today in safe mode), and it took some fixing to get as far as safe mode, so reluctant to try it again.

I'm at something of a loss, I can't even look at the dmp files myself as trying to run the Windbg install tool crashes the PC, and I don't have a second Windows machine. And I can't do an in-place re-install as that's not allowed from safe mode...

YoYo155 · 02 Jan 2014

Welcome to SF deanlove :).

I'm currently forming a general idea based on the dump files but I need more information.

Unfortunately files are missing, so I'm not getting the full picture.
Please run the SFDT again and let it run its course it can take 15min at times to collect all the data necessary.
There should be eight files generated not including the dumps.

Please upload the MSINFO32 file:

Start → Run → type MSINFO32 then hit Enter.
In MSINFO32 go to, File → Save → name it your user-name.
Once the file is saved right click it and choose Send to → Compressed (zipped) folder.

Attach the file in your next post.

EDIT:

Your CPU is overclocked.

Code:

!sysinfo machineid
Machine ID Information [From Smbios 2.5, DMIVersion 37, Size=3019]
BiosMajorRelease = 8
BiosMinorRelease = 15
BiosVendor = American Megatrends Inc.
BiosVersion = 1408   
BiosReleaseDate = 09/21/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
SystemFamily = To Be Filled By O.E.M.
SystemVersion = System Version
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = P6T
BaseBoardVersion = Rev 1.xx
7: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 3200

Reset the BIOS back to default:

CLR CMOS

Note

Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.

If any component is overclocked reset it back to stock speeds!

deanlove · 02 Jan 2014

Thanks YoYo - the tool did report successes on all that stuff but I did think there weren't many files. It seems to have worked better this time around.

Good shout on the overclock, entirely forgot about that as it's been stable for years, but have reverted it now (just after running SFDT again). Would be nice if it was that but no such luck!

YoYo155 · 03 Jan 2014

Thanks for the files :) .

We can go around trying to troubleshoot everything but with the system being overclocked
out efforts are futile.
This is from the latest dump.

Code:

CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 3400

Please revert any overclock (CPU / GPU / RAM) back to the default stock settings.

deanlove · 03 Jan 2014

As I mentioned, I reverted the over clock after running the info tool again. I can run it a third time now it's not overclocked if you think it'll give different results.

YoYo155 · 03 Jan 2014

'After running the info tool' doesn't mean anything.
At the time the crash occurred the CPU was still overclocked, I had to reiterate how important it is to eliminate
the possibility of an unstable system at it's core.

deanlove · 03 Jan 2014

Yup, hence why I tested again after reverting the overclock and still crashed in the same places with the same messages, as mentioned. I can provide the dmp files for those crashes if you think they'll be different.

YoYo155 · 03 Jan 2014

Yes, please update with a new instance of the SFDT after each time you've encountered a BSOD :).

deanlove · 03 Jan 2014

Sure, here we go:

YoYo155 · 03 Jan 2014

OK thanks :) .
Did you install any fonts recently?

Your bugchecks have a common denominator with win32k.sys and showing win32k!sfac_GetLongGlyphIDs+0x84 on the call stack.

Please navigate to C:\Windows\System32 and delete FNTCACHE.DAT, then restart the PC.

Afterwards I recommend using the System File Checker.

Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.
OPTION TWO
To Run the SFC /SCANNOW Command in Windows 7