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

[deanlove]

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]

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:

rb: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.

!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
[COLOR=Red][U][B]CurrentSpeed: 3200[/B][/U][/COLOR]

:ar: 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]

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]

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.

CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: [COLOR=Red][U][B]3400[/B][/U][/COLOR]

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

 

[deanlove]

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]

'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]

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]

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

 

[deanlove]

Sure, here we go:

 

[YoYo155]

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

 

[deanlove]

Not installed any fonts, though weirdly nearly every font (all but five of all 243 of them) is showing a modified date of 01/01/2014 either at 00:33 or 00:46, which I think is when things started going wrong.

SFC -scannow finds nothing - Windows Resource Protection did not find any integrity violations.

But - the good news is, this fixes the BSODs in safe mode, hurrah and thank you! But... the machine still won't boot normally. And because it's not blue-screening (it just gets to "loading windows", takes about 5 seconds, then restarts) I'm not even getting any dump files for that.

Going to try start-up repair from CD again and see if it finds anything now.

 

[YoYo155]

Good news !
That's progress ,

Follow this tutorial and select Disable Automatic Restart on System Failure that way it won't restart
right away and you can snap a picture of the error (BSOD).

• http://www.sevenforums.com/tutorials/666-advanced-boot-options.html

Attach it to your next post.

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[deanlove]

Okay, got the screenshot, it doesn't look hugely helpful though!

 

[YoYo155]

Thanks .

:ar: Please cleanup your start up procedure it is a must!:

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

:ar: Please Remove Daemon Tools:

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Alcohol 120% at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Does it normally boot now?

 

[deanlove]

Removed Daemon Tools and tried a clean boot but still no joy - crashes in the same way as before.

 

[YoYo155]

Hmm, can you please upload a new instance of the MSINFO32 file?

rb: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.

Also,
View attachment 300218

*Each time you try to boot normally into Windows that is.

 

[deanlove]

1 is remaining the same, 2 is varying slightly. Just did two more crashes and got 812D6 and 7A2D6 as the last five digits, the rest have stayed the same. MSINFO attached.

 

[YoYo155]

OK thanks .
Let's shoot for the most obvious driver not being loaded while in Safe-Mode that being
the GPU driver.

Please navigate and change the extension of atikmpag.sys to .bak and try to reboot into Windows.
ie.

-- Before:

c:\windows\system32\drivers\atikmpag.[B]sys[/B]

-- After:

c:\windows\system32\drivers\atikmpag.[B]bak[/B]

 

[deanlove]

Thanks, but no luck with that.

 

[YoYo155]

OK you can undo the change.
Can you think of something that changed prior to when the issue started?
New hardware / software, a power outage, you downloaded something?

You can try a restore point to before it had started.

• http://www.sevenforums.com/tutorials/700-system-restore.html
• If you do, don't forget to delete FNTCACHE.DAT (post #10) once more.