Random BSODs PAGE_FAULT_NONPAGED_AREA and MEMORY_MANAGEMENT tonight.

Hi all, been lurking here a while since regedit stuff for memory card readers (Brink?)during the W7 Beta. It seems you guys come top of the pops regarding STOP errors on Google so I'm all registered and hoping to work it out.

Now my recently running well computer has started with random BSODs...

Recently installed software for Logitech G700 and had a replacement Nokia E7-00 with the Nokia suite of pain installed- I'm thinking there could be an issue or two there...

Not sure how to add my edited system specs, are they visible?


Regards from Down under,
G'David

Several Problems


First. These were all caused by memory management Usually a driver



These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

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

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



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.

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/Win7 Startup Repair feature).

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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- 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.

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.

Second really, really old drivers

These need updating.

Code:

SiWinAcc.sys    11/1/2004 2:23:29 PM    fffff880`01326000    fffff880`01330000    0x0000a000    0x41868d31                            
SiRemFil.sys    10/18/2006 5:20:39 PM    fffff880`01b0c000    fffff880`01b14000    0x00008000    0x4536a8b7                            
LVUSBS64.sys    2/3/2007 1:05:16 PM    fffff880`07bd4000    fffff880`07be0980    0x0000c980    0x45c4cedc                            
CamDrL64.sys    2/3/2007 1:17:27 PM    fffff880`0566f000    fffff880`05756a00    0x000e7a00    0x45c4d1b7                            
WinRing0x64.sys    7/26/2008 8:29:37 AM    fffff880`09d08000    fffff880`09d0f000    0x00007000    0x488b26c1

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Repeated App crashes in IE9 and Media player and VLC all related to nvd3dum.dll

Haven't seen a crash in 24hrs +...

I am starting to think it might be an nVidia drivers issue also...

All seemed good, plugged Nokia E7 into USB and completed backup. After opening around 8 tabs in IE9 IE had an appcrash an failed to render tab...

Any ideas?

Please? Have a day off tomorrow...

GDavidF said:

All seemed good, plugged Nokia E7 into USB and completed backup. After opening around 8 tabs in IE9 IE had an appcrash an failed to render tab...

Any ideas?

Please? Have a day off tomorrow...

Still old drivers

Code:

SiWinAcc.sys    11/1/2004 3:23:29 PM                               
SiRemFil.sys    10/18/2006 6:20:39 PM                             
LVUSBS64.sys    2/3/2007 2:05:16 PM                           
CamDrL64.sys    2/3/2007 2:17:27 PM       
WinRing0x64.sys    7/26/2008 9:29:37 AM                             
pccsmcfdx64.sys    8/28/2008 5:44:41 AM

Still memory corruption.



Did you run verifier or memtest?

Memtested recently, I ran verifier a few weeks ago and it prevented windows from opening (way out of my depth).

Is there any way I could chase down the drivers that you know of?

GDavidF said:

Memtested recently, I ran verifier a few weeks ago and it prevented windows from opening (way out of my depth).

Is there any way I could chase down the drivers that you know of?

your system crash.

Re: drivers. google their name and if the date for the driver is before 7/13/2009 install them using compatibility mode.

Compatibility Mode



Not really. Verifier is supposed to make