BSOD Win7 Pro 64, IRQL_NOT_LESS... & PAGE_FAULT_IN_NONPAGED...

Paul

Less than half of these crashes appear to be video related so I would start looking at the OS, and the installed driver base.

I would run SFC and driver verifier.


SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7



* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.




Driver Verifier

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

Sfc carried out again with no problems.

Driver verifier executed and several BSODs later, I've attached the new dump files with another Perfmon report.

Thanks for taking an interest.

Gribbly Grobbly said:

Sfc carried out again with no problems.

Driver verifier executed and several BSODs later, I've attached the new dump files with another Perfmon report.

Thanks for taking an interest.

Hum,

Still pointed to win32k.sys and verified. Win32k is a funny file and I still have my doubts.

I also have my eye on this. Related to BS_I2cIo.sys I2C I/O driver fle from BIOSTAR Group. Yours is from 2008 and an I/O driver is just the sort of thing that can cause this. I would update this just in case.

Thanks for your help. I'll do some delving.

Gribbly Grobbly said:

Thanks for your help. I'll do some delving.

Yell if you need help

This would be a yell then.

Sfc reports that all is well.

Attached are the latest dumps. I renamed BS_I2cIo.sys to see how the system would behave without it and the result was more frequent BSODs. I then re-enabled BS_I2cIo.sys and rebooted. The most recent crash after that is reflected in the latest dump. Again it was FSX and PMDG's NGX (flight sim stuff) that was running at the time of the crash.

After page_fault_in_nonpaged_area crashes, windows doesn't want to boot normally and prompts with startup-repair. If I choose 'start windows normally' then I get as far as 'Starting Windows' before it reboots prior to the colours of the logo appearing. If I elect to 'start normally' and make several attempts, Windows will sometimes eventually boot successfully without the start-up repair (which always reports as having failed anyway and after much progress-bar watching). I haven't chosen to return to a system restore point because Windows hasn't been stable yet.

If it is BS_I2cIo.sys with a 2008 date that is the problem then I'm struggling to find a more recent version; unless it installs as part of a bios installation: something that I've been loathe to do on an unstable system. If it's win32k.sys then I'm unsure of how to resolve it.

fsx.exe is Microsoft Flight Simulator and it is my my main reason for attempting the move to 64 bit Windows.

I'll run malwarebytes. The install was as clean as I could make it. The first attempt had snagged up with the multitude of updates and so the second time I used SP1 before updating any further. I can't determine what the odd drivers are. Could it be the BIOS, the overclock, or both? I need the sim software for work and so can't risk losing the (functioning 3.6 GHz 32 bit O/S) system until a current project is finished.

I thought the overclock was removed?

Sorry about the fsx.exe.