Page_fault_in_nonpaged_area?

Status
Not open for further replies.
7

7crystal7

Hi guys,

I'm new to this forum, it sounds good what you talk about here, so maybe you can help me out.

If a windows xp pro SP2 machine, running emule and bittorrent on it. The RAM works perfect, hard disks ok but every 4-5hours I get this blue screen.

Error in tcpip.sys, PAGE_FAULT_IN_NONPAGED_AREA, STOP: 0x00000050

Maybe you can tell me where the problem is and how to fix it?

Thx a lot
Babsi
 
Hi,

Bugcheck 50 may be caused by faulty ram or device driver error. The system event log and the minidump has the most useful diagnostic information. When Windows crashes with blue screen, it writes a system event 1001 or 1003 and a minidump to the folder \windows\minidump. Check system event 1001 and 1003 and it has the content of the blue screen.

Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.The bugcheck was : 0xc000000a (0xe1270188, 0x00000002, 0x00000000, 0x804032100).
Microsoft Windows..... A dump was saved in: .......


Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000

Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001/1003. Copy the content and paste it back here

Zip 5 to 6 minidumps to a zip file and attach it here. Techspot has an upper limit of 100K per attachment. I will study the dump and find out the culprit.

Run memtest to stress test the ram.
 
Thank a lot, ok first two error code of the event 1001:

After a critical error, the computer restarts. The error code was: 0x10000050 (0xff7b7b8f, 0x00000000, 0xf6b3616a, 0x00000000). Dump saved in: C:\WINDOWS\Minidump\Mini120105-02.dmp.

Der Computer ist nach einem schwerwiegenden Fehler neu gestartet. Der Fehlercode war: 0x1000007e (0xc0000005, 0xf6b31230, 0xf751cad4, 0xf751c7d4). Ein volles Abbild wurde gespeichert in: C:\WINDOWS\Minidump\Mini113005-01.dmp.


Attached are 5 dumpfiles.

Thx a lot for your help!!

Greetz
Babsi
 

Attachments

  • dumpfiles.zip
    61.2 KB · Views: 28
Hi,

The culprit is nltdi.sys and the running process is BitSpirit.exe.


Mini120105-02.dmp BugCheck 10000050, {ff7b7b8f, 0, f6b3616a, 0}
Owning Process 82212578 Image: BitSpirit.exe
Probably caused by : nltdi.sys ( nltdi+ba0 )

Mini112905-01.dmp BugCheck 10000050, {ff7b7b8f, 0, f6b3616a, 0}
Owning Process ffaf1c60 Image: BitSpirit.exe
Probably caused by : nltdi.sys ( nltdi+ba0 )
 
opinion

hey guys , sometimes is not as complicated as it looks...i had the same thing happen to me yesterday...as long as you can get to safe mode you are all set....just do a virus scan and a System Restore.... that's the 1st thing i suggest you do....you can also try start,run, shutdown -a (so your pc doesn't restart) or
right-click on my computer , properties ,advanced, by startup and recovery click settings and make uncheck the autom.restart box... hope it helps ..peace :unch:
 
)x00000050 error with Page_fault_in_nonpaged_area

Computer boots up, it goes through post, then the cursor blinks then the screen goes blank. Using the F5 & F8 Keys trying to get to last configuration, nothing. go to Safe mode with Debugging options, nothing. If i select Safemode with newtorking options nothing. If i put in the windows XP SP2 disk, after it goes through it doesn't recognize the hard drive. It did last week when it was working (i have files on there, that i cannot lose). If i select the next option this is what comes up((("A problem has been deteceted and windows has been shut down to prevent damage to your computer. The problems seems to be caused by the following file: setupdd.sys Tech Info. STOP: 0x00000050()xe57AB3F8, 0x00000000, 0xF77F098B, 0x00000002) Setupdd.sys - Address F77F09AB base at F77C9000, Datestamp 41107C8F))) Please help, i am out of ideas. :confused: :confused: :confused: :confused:
 
ditto

Yeah, the same thing happened to me last night. My baby has been acting strange as of late; sometimes upon a cold boot, it'll get to the windows desktop, then reboot - it's been doing that for about a month now. But last night, she did the reboot cycle, then got stuck at the windows login screen, so I rebooted, then got the PAGE_FAULT_IN_NONPAGED_AREA error message, and now, like this last guy, my computer won't boot no matter what I do, safe mode or not. I am using utorrent, and AVG runs a scan every night in the middle of the night, with no viruses found. Am I screwed? I brought the hard drive into work to see if I can dump all my files from it to my work drive, just in case, but I'd like my baby back. Any ideas, folks? I'm desperate.
 
solution? temporary?

Ok, so I spoke with one of my techie friends, and he suggested taking out one of my 2 sticks of 512, then booting to see if it worked. He says that it may be the RAM sticks that are buggered, so switching them in the slots could work as well. I'll try that tonight and report back.
 
Ok guys, i tried the suggestion of taking out the ram.. and seeing if it is the module. This is what i have MEM-MOBL1GBDDR2533LP (2 of their sticks). I tried them by themselves, and i also tried them by themselves but in one of the 4 slots. No luck. I did notice though that cdrom drive clicks ... like it is looking for a file from the windows cd. I only get the page fault error when i have the disk in.. but then it doesn't see the hard drive. If i try to boot it up just as is.. then it goes past post.. shows the logo.. and the cursor in the upper left corner.. then black screen. New ideas please? And wiping/reloading really isn't an option..
:confused: :suspiciou :confused: :suspiciou :confused:
 
success!

Saints be praised! I have switched the RAM on the mobo (I still have the original sticks; they just traded places) and am now speaking to you with my little Frankenstein. Like nothing ever happened. This is not a Microsoft problem, at least in my case, so lamentably I can't start a long-simmering anti-M rant. Oh well. At least my baby's back. Good luck, kids!
 
Hi..I managed to get a fix for it, discovered it by accident. I am not 100% sure it works, but i've been running my pc with this fix for 4 hrs and it didn't crash :)

1. Uninstall Netlimiter 2.07
2. Reboot
3. Reboot again
4. Enter safe mode
5.Install Netlimiter.
6.Reboot :)

Sounds very simple. And it works for me, hopefully for you to :) cya
 
Page_fault_in_nonpaged_area

cpc2004 said:
Hi,

The culprit is nltdi.sys and the running process is BitSpirit.exe.


Mini120105-02.dmp BugCheck 10000050, {ff7b7b8f, 0, f6b3616a, 0}
Owning Process 82212578 Image: BitSpirit.exe
Probably caused by : nltdi.sys ( nltdi+ba0 )

Mini112905-01.dmp BugCheck 10000050, {ff7b7b8f, 0, f6b3616a, 0}
Owning Process ffaf1c60 Image: BitSpirit.exe
Probably caused by : nltdi.sys ( nltdi+ba0 )
Click to expand...

I am facing the same problem when using Windows XP SP2 and using Microsoft Outlook. My system has crashed 5 times in the past 5 hours with the same STOP BLUE SCREEN ERROR with PAGE_FAULT_IN_NONPAGED_AREA message.

I am enclosing the Minidump files duly compressed for analysis. Please would you check the same and confirm the cause of the error?

Thanks in advance.
 
Hello Community,

since yesterday I got the same annoying Error page_fault_in_nonpaged_area!

I read a lot and tried to dumpcheck by myself but I really dont know what to do wíth the information:giddy:

So would please someone tell me what driver is responsible for the crashes?

Thanks so much in Advance

goc

PS: That is what I dumpchecked so far:

Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Dokumente und Einstellungen\Patrick\Desktop\Minidump\Mini040807-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.061219-0316
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Apr 8 10:30:08.062 2007 (GMT+2)
System Uptime: 0 days 0:01:10.755
Loading Kernel Symbols
...........................................................................................................................................................
Loading unloaded module list
........
Loading User Symbols
Unable to load image windev-50dd-2119.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for windev-50dd-2119.sys
*** ERROR: Module load completed but symbols could not be loaded for windev-50dd-2119.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e130d000, 0, 804fb799, 1}


Could not read faulting driver name
Probably caused by : windev-50dd-2119.sys ( windev_50dd_2119+9af )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e130d000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 804fb799, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: e130d000

FAULTING_IP:
nt!wcsncpy+16
804fb799 668b02 mov ax,[edx]

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from af9f99af to 804fb799

STACK_TEXT:
f78e6874 af9f99af f78e6898 e130ce10 000000ff nt!wcsncpy+0x16
WARNING: Stack unwind information not available. Following frames may be wrong.
f78e6a9c 804dd99f 8000059c 00000000 00000000 windev_50dd_2119+0x9af
f78e6a9c 804e381f 8000059c 00000000 00000000 nt!KiFastCallEntry+0xfc
f78e6b2c 80599eff 8000059c 00000000 00000000 nt!ZwEnumerateKey+0x11
f78e6bd4 805b7c0c 000000b0 892ecaac 00000000 nt!IopGetDeviceInterfaces+0x5bb
f78e6c48 805b7ae8 892ecaac e2ac1c60 00000000 nt!IopDisableDeviceInterfaces+0xf1
f78e6c60 805b7d01 00000308 e2ac1c60 00000000 nt!IopSurpriseRemoveLockedDeviceNode+0xb6
f78e6c74 805b7d2c 892eca18 00000003 e2ac1c60 nt!IopDeleteLockedDeviceNode+0x50
f78e6ca8 805b7fb5 892e12f8 02ac1c60 00000003 nt!IopDeleteLockedDeviceNodes+0x3f
f78e6d3c 805b8089 f78e6d78 80700974 e10cf008 nt!PiProcessQueryRemoveAndEject+0x4d2
f78e6d58 8059e83e f78e6d78 89705880 805694fc nt!PiProcessTargetDeviceEvent+0x2a
f78e6d7c 804e23b5 89705880 00000000 8aaffb30 nt!PiWalkDeviceList+0x122
f78e6dac 80574128 89705880 00000000 00000000 nt!ExpWorkerThread+0xef
f78e6ddc 804ec781 804e22f1 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
windev_50dd_2119+9af
af9f99af ?? ???

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: windev_50dd_2119+9af

MODULE_NAME: windev_50dd_2119

IMAGE_NAME: windev-50dd-2119.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46176ede

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x50_windev_50dd_2119+9af

BUCKET_ID: 0x50_windev_50dd_2119+9af

Followup: MachineOwner
---------
Click to expand...
 

Attachments

  • Mini040807-15.zip
    81.5 KB · Views: 6
All your dumps crash at windev-50dd-2119.sys. Do a search on your system to find out what it belongs to (Windev?). Google shows nothing.

BugCheck 10000050, {e190e000, 0, 804fb799, 1}
Probably caused by : windev-50dd-2119.sys ( windev_50dd_2119+9af )
Image name: windev-50dd-2119.sys Timestamp: Sat Apr 07 18:13:50 2007 (46176EDE) <-- Timestamp from Saturday.
 
setupdd.sys page_fault_in_nonpaged

hi guys,
i am new to this forum, i got a problem while installing xp ,already i got 2003
installed,while installing xp i got a problem saying that setupdd.sys page_fault_in_nonpaged.
stop: 0*00000050 (0*e59abaco,0*00000000,0*f74419b1d,0*00000002)
setupdd.sys-address f7419b1d base at f73f3000,datestamp 3b7d8507.
how to overcome this problem ,please help me guys..........
thankyou
krishna prasad
 
hi guys,
I'm new to this forum and i'm not a tech expert:(

Couple of days ago I also got that PAGE_FAULT error.
Here are the attached dump files.

Would you please check them and suggest what is the error please?
I don't have nltdi.sys, so that should be something else

Or at least tell me how to debug the dump files by myself?

Thanks in advance!
 
thanks,
but the only message I got was that "Mini Kernel Dump does not contain driver list", no valuable information at all:(((
 
NTFS.sys stopped

stop: 0x00000050 (0xb9a04645,0x00000001,0xf7b60f8b,0x00000000)

ntfs.sys - address f7b60f9b base at f7b520000, datestamp 41107eea

This is all my computer has been giving me, here are the specs
XP Home SP1, currently upgraded to SP2.
After the reboot, the screen just shows up black, and when i go into safe mode i get this BSOD. any ideas?
 
cpc2004 said:
Hi,

Bugcheck 50 may be caused by faulty ram or device driver error. The system event log and the minidump has the most useful diagnostic information. When Windows crashes with blue screen, it writes a system event 1001 or 1003 and a minidump to the folder \windows\minidump. Check system event 1001 and 1003 and it has the content of the blue screen.

Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.The bugcheck was : 0xc000000a (0xe1270188, 0x00000002, 0x00000000, 0x804032100).
Microsoft Windows..... A dump was saved in: .......


Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000

Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001/1003. Copy the content and paste it back here

Zip 5 to 6 minidumps to a zip file and attach it here. Techspot has an upper limit of 100K per attachment. I will study the dump and find out the culprit.

Run memtest to stress test the ram.
Click to expand...

Hi cpc2004
I've gotten this blue screen error recently.
i mean "page_fault_in _nonpageed_area"
as you said I am going to copy the discription of 1003 from event viewer, and also attach the minidump.zip
i'll be appreciate if you could response me sooner.
because i'm in a hurry a little bit.
------

Error code 10000050, parameter1 fffffffe, parameter2 00000000, parameter3 82344eca, parameter4 00000000.
-
 
Status
Not open for further replies.

Similar threads

M
The fallacy of the cashless monetary system
Replies
0
Views
406
Mark Fuller
M
Senius
What would my FPS be low with 4090?
Replies
1
Views
857
Nelson28
N
Julio Franco
Here's how you can get hired at your dream tech company
Replies
3
Views
149
erickmendes
erickmendes

Latest posts

Back