asked on Page_Fault_In_Nonpaged_Area STOP: 0x00000050
Issue on XP Pro computer.
Computer is an ASUS with a Celeron D CPU 3.20 GHZ and 512 MB of Ram.
Unit is blue screening right after the logon screen appears.
When it blue screens, the error message is page_fault_in_nonpaged_are
Stop 0x00000050
I can access the computer in safe mode as the user or as admin. User has admin rights.
I have turned off all non microsoft services
Looking at the event log when trying to start in normal mode, the sequence is
Microsoft (R) Windows (R) 5.01. 2600 Service Pack 3 Multiprocessor Free.
The Event log service was started.
To see if I could get more log info, I started and restarted the computer 3 times. All that appears in the event log (during this start/restart process are those two events repeated for each restart.)
When I start it again in safemode, I get additional information:
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xed77af35, 0x00000000, 0x8053ce32, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini03
(I don't know what to use to open and view the minidump file.)
I have done a full memory scan without errors.
I did a diagnostic surface scan of the hard drive for errors without a problem.
Linux boot disk (Slax 6.07) runs on the system fine.
I have done a system restore to beyond the point where the problem appeared to have begun. (This is a clients computer and the problem started while they were away on vacation. The computer was starting / restarting about every minute since 2/25/09!)
I looked for exploded capacitors and the motherboard seems to be physically fine.
I'm not sure what to try next and would appreciate any suggestions. My next attempt will probably be to toss in another hard drive, set it up for XP Pro and see if this is stable. If it is, I think I'd assume the operating system got hosed in someway but I'd rather not do this if 1) I don't have to, and 2) it still might not be the solution.
Any ideas?
Thanks in advance for the assistance.
Regards,
Bill Marquardt
Computer is an ASUS with a Celeron D CPU 3.20 GHZ and 512 MB of Ram.
Unit is blue screening right after the logon screen appears.
When it blue screens, the error message is page_fault_in_nonpaged_are
Stop 0x00000050
I can access the computer in safe mode as the user or as admin. User has admin rights.
I have turned off all non microsoft services
Looking at the event log when trying to start in normal mode, the sequence is
Microsoft (R) Windows (R) 5.01. 2600 Service Pack 3 Multiprocessor Free.
The Event log service was started.
To see if I could get more log info, I started and restarted the computer 3 times. All that appears in the event log (during this start/restart process are those two events repeated for each restart.)
When I start it again in safemode, I get additional information:
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xed77af35, 0x00000000, 0x8053ce32, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini03
(I don't know what to use to open and view the minidump file.)
I have done a full memory scan without errors.
I did a diagnostic surface scan of the hard drive for errors without a problem.
Linux boot disk (Slax 6.07) runs on the system fine.
I have done a system restore to beyond the point where the problem appeared to have begun. (This is a clients computer and the problem started while they were away on vacation. The computer was starting / restarting about every minute since 2/25/09!)
I looked for exploded capacitors and the motherboard seems to be physically fine.
I'm not sure what to try next and would appreciate any suggestions. My next attempt will probably be to toss in another hard drive, set it up for XP Pro and see if this is stable. If it is, I think I'd assume the operating system got hosed in someway but I'd rather not do this if 1) I don't have to, and 2) it still might not be the solution.
Any ideas?
Thanks in advance for the assistance.
Regards,
Bill Marquardt
Windows XP
Last Comment
willcomp
A page fault is usually caused by a driver and should be correctable once the driver is identified. That you can boot into safe mode reinforces probability of a faulty driver.
Attach the last two minidump files to a comment after renaming with a .txt extension. They are located in c:\windows\minidump folder. I'll be calling it a day shortly, but will check back later today. Someone else may analyze the files for you in the interim
If you want to try your hand at crash dump analysis, here's a good reference: http://support.microsoft.com/kb/315263
Attach the last two minidump files to a comment after renaming with a .txt extension. They are located in c:\windows\minidump folder. I'll be calling it a day shortly, but will check back later today. Someone else may analyze the files for you in the interim
If you want to try your hand at crash dump analysis, here's a good reference: http://support.microsoft.com/kb/315263
ASKER
Here are a couple of the dumps. They are representative of the first that occurred and one of the last.
I have changed the extension from tmp to txt.
Thanks for taking a look at these.
Bill
DUMP4f39.txt
DUMP4c2c.txt
I have changed the extension from tmp to txt.
Thanks for taking a look at these.
Bill
DUMP4f39.txt
DUMP4c2c.txt
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thank you everyone. Once I had the info from nobus, I ripped it completely out of the registry so it never loaded (it wasn't used by the client.) Interesting about it's issue with AVG.
Since there were multiple contributors to the solution, can someone suggest a fair way to divvy up the points? BTW: I did have it resolved prior to the message from willcomp though it certainly was an interesting knowledge addition.
Bill
Since there were multiple contributors to the solution, can someone suggest a fair way to divvy up the points? BTW: I did have it resolved prior to the message from willcomp though it certainly was an interesting knowledge addition.
Bill
I'd suggest a split between nobus and myself. I did the heavy lifting and provided basic solution, nobus beat me to identifying the specific driver.
ASKER
I hope a 50/50 split is fair for both of you. I do appreciate all the help.
Regards,
Bill
Regards,
Bill
OK by me. Glad to help.
Bill