Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

page fault in non paged area 2

Status
Not open for further replies.

pawz

Technical User
Dec 24, 2002
258
GB
this is the stop message on a Dell laptop running XP Pro.

It seems to have been an intermittent fault at first, as the owner found she could make it go away ( don't know how), but then it happened again immediately after she had loaded a digital camera, then it was ok ( she says) and then happened again after she loaded software for a scanner.
She called a friend in who got in by safe mode and downloaded a graphics driver upgrade and they thought they had fixed it, but no...

when I got it I ran sigver and found three files belonging to AVG 7.0 were unsigned - but I didn't know what to do about it.
I was able to get in and out and on the net with no problems at all, and everything seemed fine, including the antivirus software.

Then I loaded a twain driver from a cd, and the stop message was there again after I shut down and rebooted. Hmph

So I uninstalled AVG, and all in the garden was rosy again.

I downloaded and installed Avast AV, and told it not to do a bootscan on startup

but I got the message again.

Took the AV off again and back to roses again - no message.

What is wrong do you think?

It seems every new install brings up this stop message.

Where do I go from here?

All help appreciated :)
 
To get further information about the error look in your Event viewer.

Look in the System or Application folder. You can get to the Event Viewer via right click My Computer icon and select Manage.

Any errors logged in the Event Viewer can be expanded by double clicking on the error line.

Take any event error I.D. number and search for it on these sites.


Also check any "Information" line that mentions "savedump" and you should find reference to "recovered from a bug check". This is the Stop Error that caused your problem.

You can also turn off "automatically restart after an error" so it will just halt at the fault and display the full Stop Error and blue screen.

Right-click My Computer, and then click Properties .
On the Advanced tab, click Settings under Startup and Recovery .
Click to clear the Automatically restart check box under System failure , and then click OK . The error message on a blue screen should remain on the screen so you can record the error information.



If the error occurred after installing a device driver or application, try using Safe Mode and removing the driver or program.

To check your RAM.


To check your Hard Drive.

The drive manufacturer will have free diagnostic software to check your drive for problems.

You can also load the Recovery Console and run ChkDsk /r to check for problems.

HOW TO: Install and Use the Recovery Console for Windows XP (Q307654)

To check your drivers.

HOW TO: Verify Unsigned Device Drivers in Windows XP


To check conflicting software.

310353 - How to Perform a Clean Boot in Windows XP

316434 - HOW TO: Perform Advanced Clean-Boot Troubleshooting in Windows XP

310560 - How to Troubleshoot By Using the Msconfig Utility in Windows XP




Removing adware & spyware
faq608-4650

Will check your computer for spyware and adware.



To checkout unnecessary services you are running.

See if you have any services that are flagging as "Starting" but not actually running.


Some general things to try.

See if System Restore will get you back to a restore point before your problem with Windows.

Try Safe Mode (Do you have this problem in Safe Mode?).

Try running ChkDsk to check your drive for errors. Right click your Drive icon/ Properties/ Tools/ Error Checking.

Run the System File Checker program from the Run Box by typing.....Sfc /Scannow in it and have your XP CD handy.

If they don't work you could try repairing windows itself by running it over itself. You will lose all your windows updates but your files will be untouched.

How to Perform an In-Place Upgrade (Reinstallation) of Windows XP (Q315341)



Plenty of reading and suggestions here.


 
well Bill thank you for all of that (gulp)

some of that I have already tried, some I haven't, some I can't because the OS is now SP2. It wanted to download that the minute I got in, and I allowed it to continue, so now, if I wanted to put recovery console on or change system files I would have to slipstream I guess, but you have added to my list of things to do.
The only error message in the events when I looked yesterday was a Userenv ID 1517. I get that on my own computer occasionally so did not think that too significant.

Anyway, thank you. If I identify the problem in a clear way I shall post my discovery, if I don't I shall probably be back for more ( wot-MORE?) help... Gracie :)
 
oh dear, Linney, I do apologise, I saw Bill's entry and sorta joined yours with his. Thank you again - you too have helped me before, what a great bunch you are.

Now to work.. ho hum.

Gracie :)
 
linney, I am going to put a new post on to see if anyone can help me with creating a bootable cd and then putting the windiag iso on it. My attempt seems not to have worked :(
 
there is no floppy drive linney. I did get a memtest working via the Ultimate Boot disk you pointed me to, but then I discovered that there is a very good diagnostic program already on the machine which you access by the menu on bootup.

There was too much to go through, but I did 86% of the blue screen tests and all the memory tests were fine.

I am down in the dumps tho because I have now taken all the recently installed software off, and the antivirus software, but the message is still coming. It isn't every time. I remove something and that is ok, I reboot and that is ok, I indicate to turn off the computer without going into any account, just from the welcome screen, and then, when I start up again, the message comes back. Then I have to go for last known config and can get in, and it might be fine until I want to install something else, and then it all starts over again
 
I often see posts about strange errors and happenings on Laptops that may be a cause of blocked vents and overheating problems.

When running your memory tests you perhaps should allow them to run for a couple of hours before stopping them.

It is a hard job to track down such an intermittent fault as you are experiencing, especially if it is being caused by faulty hardware.

There is this snippet of information which may or may not confirm or not confirm that it is the same exact fault occurring every time.

If you want the highly technical cause of a crash look in the Documents and Settings/ All Users/ Application Data/ Microsoft/ Dr Watson/ Drwtsn32.log

Find the entry that is relevant by date and time to the crash you are investigating. The exact cause of the crash is indicated by "FAULT ->" on the left of page next to line of code causing crash. This, if your as cluey as me, wont tell you much but you can use it to see if it is the same fault all the time, and further up the log you can find what processes and modules are running.
 
ok Linney, I will give it a go - thank you for that Userenv tip, I have just downloaded it.
 
well did the dr watson thing. Assume the bottom of the page is the latest. There was FAULT there... to do with MFC42 perhaps as that was next door in the line. I think that is a .dll as Grisofts AVG 6.0 is mentioned above it and a Mfc42.dll

That could be significant because the lady had also just downloaded and installed AVG 7.0 when things went pearshaped.

However, it doesn't leave me much closer to a solution...

do you suppose a reformat would fix it? Even that is nightmarish as I expect it was all pre-installed. Don't know if she has got the software disks, but loads of posh software on there.
 
there are 8 mfc42.dlls on the laptop; 5 of one size and version, 3 of another.

They wouldn't cause this fault though would they?

another consistent complaint in Dr Watson, from top to bottom of the page was

stack unwind information not available. Following frames may be wrong.

It didn't have 'Fault' next to it

I have no idea what I can do with that...

feeling very glum we are
 
mfc43.dll is a true windows DLL, unfortunately if often is packaged in different versions with some software. Once you have version issues, you need to track them all down.

Do a search for mfc42.dll, and remove it from all directories other than C;\windows\system32

Then do a start, run, sfc /Scannow
 
Bill, I haven't done the sfc scannow yet, but I renamed all but the system32 mfc42.dll as 'oldmfc42.dll', and things started looking up from that point on.

Bit by bit I reloaded all the recent software I had taken off, including antivirus, and checked between each application to change any new mfc42's to 'old' ( so they can be reverted if its found they are needed), and it all went smoothly with NO Stop Message!

And I turned it off, and rebooted, and warm booted and cold booted, hardly daring to look at the screen in case... but NO message!

So, I am scared to say its fixed just in case I get up tomorrow and boot up and find it is back, but oh, how wonderful if it isn't!

So, big hugs to you for telling me to do that- I didn't think little ol mfc42.dll's could do such a thing, and also for Linney for pointing me to Dr watson, where I noticed the dll mentioned as a FAULT.

you are stars

exhausterpated Gracie
 
Fingers crossed.

"stack unwind information not available. Following frames may be wrong".

No real idea what the above means, but as I see it in every log I look at I feel it is not worth bothering too much about.
 
linney, there is one more question I need to ask - it booted up fine this a.m. by the way :) - these older version dll's that I have renamed, can I replace them with a copy of the one in system32, and do I need to, I mean, why has the software for the camera and scanner etc got this dll if it doesn't need it, why can't it call up from the system32 library? And, can I re-enable the other two that are of the right version but are parked in i386 and somewhere else, or do I not need to do that either?

huge thank you's again - this was a toughie for me and if you hadn't pointed me to Dr W I would not have found it. I shall go there more often in future!

I might put this question on a new thread in case its not seen here as I want to give the laptop back later today

Gracie:)
 
Versions in folders such as the i386 you mention are probably older Service Pack files retained for backup purposes in case you have to remove a later Service Pack, or versions in DllCache folders are current System File Checking backups.

Over time as updates to Windows occur various in-use Dll's will become updated by Microsoft. This will leave older versions in other third party programs at their original versions, which in turn may make these older versions incompatible with other pieces of Microsoft's updated software.

I'm guessing here that third party programs look to their own program files folder for the Dll's before they check the System32 folder.

Guessing again, they probably include these Dll's in the first place because it is uncertain which actual version of Windows (and update state) they may end up running on.


Are you a victim of Dll Hell ???????????




Either delete the old ones you have renamed or leave them in their currently renamed state (third party program ones). Old Service Pack Files should be left at the old Service Pack version. Do give clear instructions to the owner of what is what in case they ever reinstall the various programs and begin the whole sorry mess again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top