Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: BSOD: irql_not_less_or_equal AND page_fault_in_nonpaged_area

26 Aug 2012   #1

MS Windows 7 Home Premium 64-bit SP1
 
 
BSOD: irql_not_less_or_equal AND page_fault_in_nonpaged_area

Working on my brother's machine which keeps getting BSOD.
It was infrequent at first, and he ignored it for a few months. Now it's usually within a minute of booting up the machine, making it completely unusable.
Windows 7 Home Premium x64

Attached is the information from the SF Diag Tool.

Help would be very much appreciated.
Thanks

(more info below)


The error message is either "irql_not_less_or_equal" or "page_fault_in_nonpaged_area", which one appears seems random.

System restore does nothing, Startup repair doesn't help, and I've scanned for malware using MalwareBytes even though the symptoms started immediately upon setting up the machine (not much time there to get infected).

I tried removing hardware (along with drivers) individually to narrow down the problem, to no avail. I tried the mouse, keyboard, video card, and network adapter.

I would have already reinstalled the OS, but he upgraded from XP to Windows 7 Home Premium and I was told he was not eligible for a full install, only an upgrade.

My System SpecsSystem Spec
.

28 Aug 2012   #2

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

Hello Dan and welcome to Sevenforums.

Updating System Specs will give us a better sight of
how your system is put together. It's simply done.
§ Download Speccy
§ |User CP (top of the page)| |Edit System Spec|
§ COPY & PASTE section to section
§ Include Laptop, Desktop information
§ End with |Save Changes|
´´´´´´´´

BSOD Analyse
1) Combining your crash dumps and the general view of BSODs culprits, I'd suggest you to have a look at your memory, the sticks. Through decades people have been using the bootable tool called Memtest86+ and it's basically very unique in these manners.
Be sure to check your warranty rules and regulations before opening your case.
* Memtest86+ is USB-ready, and can be booted directly from it. Download the flashdrive wizard.
* To ensure that either your sticks OR your motherboard slots are broken, it's necessary to do the below procedure-
* Pull out all sticks except ONE, scan it.
* If no errors, pull the scanned stick into another slot.
* Proceed like this until you've scanned all sticks individually, and all the slots.
Problem Devices

Problem devices can be found in your Device Manager. Search Device Manager in Start, and look for . Note that if the warning sign isn't there, select View on the top of the window, and end with Show hidden devices.

Code:
Security Processor Loader Driver	ROOT\LEGACY_SPLDR\0000	This device is not present, is not working properly, or does not have all its drivers installed.
Make sure their drivers are installed.

* What's the temperatures in general?
* Are the CPU pins all the way in?
* When was the last time the thermal paste was changed?


Best Regards,
Frederik.
My System SpecsSystem Spec
05 Sep 2012   #3

MS Windows 7 Home Premium 64-bit SP1
 
 

I really appreciate the help!
Let me know if you need any more info.


System Specs --- I have used Speccy to update the System Specs for my profile.

Memtest86+ --- I have checked each Memory Stick and Slot individually for 2 hours each (9 -10 passes) - ZERO Errors

Problem Devices --- The "Security Processor Loader Driver" error only shows up in safe mode, which is the only way I was able to get the SF Diag Tool to finish. I'm not sure if that's worth pursuing (did some reading in this thread). No other drivers show errors.

Quote:
* What's the temperatures in general?
* Are the CPU pins all the way in?
* When was the last time the thermal paste was changed?
Temperatures --- Speccy shows the CPU at 34 C, Motherboard at 30 C, Graphics card at 36 C, and Hard Drive at 31 C. These readings were taken immediately before a BSOD.

CPU Pins and Thermal Paste --- The computer was put together back in March of this year. The thermal paste has not been changed since. I'm pretty sure the CPU Pins are all the way in (would it work at all otherwise?) Though I didn't install the CPU for this build, I only supervised it.
My System SpecsSystem Spec
.


05 Sep 2012   #4

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

Alright thanks, let's go and enable verifier.

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

So, 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/Windows 7 Startup Repair feature) - and create a System Repair Disc (Windows 7) if you don't have a full installation DVD.
You can do this by going to Start...All Programs...Maintenance...Create a System Repair Disc (don't forget to test the disc to make sure it works).

For Vista, you can download the repair discs from different websites. If unable to locate them, shoot me a PM and I'll point you to them.
For Win8, BSOD's are different - and we'll have to adjust how we do this with them.

Also, to ensure that you can recover, here's another couple of additional steps:
- Get to the Safe Mode menu (rapidly tap F8 just before the Windows splash screen comes up). Scroll down to and select "Disable automatic restart on System Failure"
- Get the RED information from this picture (in particular we will need the name of the file that the error occurred in):
Picture of a BSOD

Then, here's the procedure to run Driver Verifier:
- 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 "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- 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.

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 (an estimate on my part).

Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Windows 7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
Best Regards,
Frederik.
My System SpecsSystem Spec
05 Sep 2012   #5

MS Windows 7 Home Premium 64-bit SP1
 
 

The verifier is running and I got the BSOD to happen again...

Quote:
Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.
Not sure where to locate the memory dump file(s).
Should I run the SF Diag Tool again?
Is a file created somewhere that I'm not seeing? (I looked at root of C drive, and nothing was there).
My System SpecsSystem Spec
06 Sep 2012   #6

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

C:\Minidump. That should be the path. If you're wondering check your setup:

To ensure minidumps are enabled:

* Press Start, in the Search Box type: "sysdm.cpl" (without the quotes), press Enter.
* Select the Advanced tab, click on Startup and Recovery Settings.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information headline select Small memory dump (256 kB) in the dropdown box.
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK till you're out of the dialogue.
* Reboot if changes have been made.

Best Regards,
Frederik.
My System SpecsSystem Spec
06 Sep 2012   #7

MS Windows 7 Home Premium 64-bit SP1
 
 

The Minidump was disabled by default.
Also, the systemroot was the C:/Windows directory... just FYI.

Attached is a .zip file of the Minidump folder.
Let me know if I can provide any more info.
My System SpecsSystem Spec
06 Sep 2012   #8

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

Quote:
Also, the systemroot was the C:/Windows directory... just FYI.
Yeap, I knew.

Let's take a look.

Code:
STACK_TEXT:  
fffff880`02ffd228 fffff800`03082769 : 00000000`0000000a fffff880`0321f070 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02ffd230 fffff800`030813e0 : fffff880`02ffd0a0 fffffa80`054171a0 fffff880`00c161a0 fffff980`01372c02 : nt!KiBugCheckDispatch+0x69
fffff880`02ffd370 fffff800`035103b6 : 00000000`00000003 00000000`00000010 00000000`00000001 00000000`00000002 : nt!KiPageFault+0x260
fffff880`02ffd500 fffff800`03511276 : 00000000`00000000 fffff980`01372cf0 00000000`ffffffff fffff880`02ffd610 : nt!ViIrpDatabaseReleaseLock+0x6
fffff880`02ffd530 fffff800`0351768e : fffff980`01372cf0 fffff800`03516002 fffffa80`03a21480 00000000`ffffffff : nt!VfIrpDatabaseEntryFindAndLock+0xa6
fffff880`02ffd570 fffff800`0351f0ef : fffff980`01372cf0 00000000`ffffffff fffffa80`056b4001 00000000`00000000 : nt!IovpCompleteRequest1+0x2e
fffff880`02ffd5e0 fffff880`01954bce : fffffa80`05f81000 fffff980`01698e02 00000000`00000003 fffffa80`056b4010 : nt!IovCompleteRequest+0xef
fffff880`02ffd6b0 fffff800`035275d6 : fffffa80`06c088e0 fffffa80`06c088e0 fffff880`02ffd8d0 fffff980`01698e50 : CLASSPNP!TransferPktComplete+0x1ce
fffff880`02ffd730 fffff800`03086bc1 : fffff980`01698fb3 00000000`00000001 00000000`00000000 fffff800`0313cdf3 : nt!IovpLocalCompletionRoutine+0x166
fffff880`02ffd790 fffff800`0351f19f : fffff980`01698e50 fffffa80`0542e701 fffffa80`0542e701 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`02ffd880 fffff880`00c0941a : 00000000`00001000 00000000`00000000 00000000`00000000 fffffa80`0542e7d0 : nt!IovCompleteRequest+0x19f
fffff880`02ffd950 fffff880`00c09242 : fffffa80`06002b80 fffff880`00c0bb53 fffffa80`06001260 fffffa80`0542e7d0 : ataport!IdeCompleteScsiIrp+0x62
fffff880`02ffd980 fffff880`00c03e32 : 00000000`00000000 00000000`00000000 fffffa80`05418500 fffffa80`0542e7d0 : ataport!IdeCommonCrbCompletion+0x5a
fffff880`02ffd9b0 fffff880`00c0c805 : fffffa80`054171a0 fffffa80`06002b80 00000000`00000000 fffffa80`06002b80 : ataport!IdeTranslateCompletedRequest+0x236
fffff880`02ffdae0 fffff880`00c0c104 : fffffa80`054171a0 00000000`00000000 fffffa80`054171a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
fffff880`02ffdc10 fffff800`0308d8ec : fffff880`02fd5180 fffff800`03184ede fffffa80`05417050 fffffa80`05417118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02ffdcd0 fffff800`0307aeca : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`00c0bf5c : nt!KiRetireDpcList+0x1bc
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a
Do you have controllers, adapters and ports fully updated? You can find these on your motherboard manufacturer, likely.

Best Regards,
Frederik.
My System SpecsSystem Spec
17 Sep 2012   #9

MS Windows 7 Home Premium 64-bit SP1
 
 

I went into Device Manager and enabled "Show Hidden Devices".

Then, I did a right-click > "Update Driver Software" > "Search Automatically..."
I did this for each item in the list, and all were already up-to-date, except for the "WAN Miniport..." items (under Network Adapters).
Windows reported that it could not find the file(s) associated with the WAN Miniport drivers, so it was unclear whether they were updated or not.
I dug a bit, trying to find the drivers for these items, but I'm feeling now like it is a wild goose chase.

Other than that, all items have been updated.

How would you recommend I proceed?
Please keep in mind that when I boot up the machine I have about 1 minute (on average) before it crashes, or up to 5 minutes if in Safe mode.



EDIT:
Update... I downloaded all the drivers from the Motherboard manufacturer's website and installed them, just in case windows was lying to me when it said the drivers were up to date.

My brother is frustrated and wants to just take it to some computer repair place, so I'm holding him off the best I can.
What are the next few steps you would recommend?
Does it seem like a hardware problem or a software problem to you?
I ask because it will be out of my hands soon so I would like to have a plan of action for him to follow.

Thanks,
Daniel
My System SpecsSystem Spec
21 Feb 2013   #10

MS Windows 7 Home Premium 64-bit SP1
 
 

I still need help with this issue, if anyone can provide it.
I never got a response to my last post.
My System SpecsSystem Spec
Reply

 BSOD: irql_not_less_or_equal AND page_fault_in_nonpaged_area





Thread Tools



Similar help and support threads for2: BSOD: irql_not_less_or_equal AND page_fault_in_nonpaged_area
Thread Forum
Solved Bsod- page_fault_in_nonpaged_area (help!) BSOD Help and Support
bsod PAGE_FAULT_IN_NONPAGED_AREA BSOD Help and Support
Solved Bsod page_fault_in_nonpaged_area BSOD Help and Support
BSOD Page_fault_in_nonpaged_area? BSOD Help and Support
Solved Bsod page_fault_in_nonpaged_area BSOD Help and Support
Bsod page_fault_in_nonpaged_area BSOD Help and Support
Bsod page_fault_in_nonpaged_area BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 10:21 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33