Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Page_Fault_In_Nonpaged_Area (Kernal Fault Check)


  • Please log in to reply
4 replies to this topic

#1 rwhjr

rwhjr

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:05:44 AM

Posted 07 January 2009 - 02:25 PM

I have recently began to get Blue Screen - Page_Fault_In_Nonpaged_Area crashes on my HP DV1000 laptop/XPHome/SP3. I have tried to reboot and sometimes it boots up just fine. I have followed the steps described in this column and am posting the following Dump File Analysis Report. It seems that the issue is with the NTOSKRNL.EXE file. I have analyzed several of the dump file reports and they all indicate this as the probable issue.

Does anyone have any suggestions how to resolve this?


Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini010709-10.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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Wed Jan 7 10:54:09.296 2009 (GMT-6)
System Uptime: 0 days 0:00:55.875
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e1103000, 0, 804d92c2, 1}


Could not read faulting driver name
Probably caused by : ntoskrnl.exe ( nt!KiFastCallEntry+f8 )

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

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: e1103000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 804d92c2, 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: e1103000

FAULTING_IP:
nt!RtlInitUnicodeString+1b
804d92c2 66f2af repne scas word ptr es:[edi]

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 10

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: svchost.exe

LAST_CONTROL_TRANSFER: from 804de7ec to 804d92c2

STACK_TEXT:
a99d0d44 804de7ec 0256e688 00100080 0256e654 nt!RtlInitUnicodeString+0x1b
a99d0d44 00000001 0256e688 00100080 0256e654 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000810 00000000 00000000 00000000 00000000 0x1


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiFastCallEntry+f8
804de7ec 8be5 mov esp,ebp

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiFastCallEntry+f8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48a404ab

FAILURE_BUCKET_ID: 0x50_nt!KiFastCallEntry+f8

BUCKET_ID: 0x50_nt!KiFastCallEntry+f8

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

BC AdBot (Login to Remove)

 


#2 quietman7

quietman7

    Bleepin' Janitor


  • Global Moderator
  • 50,926 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Virginia, USA
  • Local time:06:44 AM

Posted 07 January 2009 - 03:15 PM

ntoskrnl.exe is a critical process involved in the boot-up cycle.

PAGE_FAULT_IN_NONPAGED_AREA
Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA

I will move this to the XP Forum where one of our Advisors can you assist your further.
.
.
Windows Insider MVP 2017-2018
Microsoft MVP Reconnect 2016
Microsoft MVP Consumer Security 2007-2015 kO7xOZh.gif
Member of UNITE, Unified Network of Instructors and Trusted Eliminators

If I have been helpful & you'd like to consider a donation, click 38WxTfO.gif

#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:06:44 AM

Posted 07 January 2009 - 03:36 PM

This is an error with a program accessing memory. The memory address that it tried to access was either empty, or didn't have the contents that it expected to find.

This can happen (most commonly) due to corrupted memory (RAM, VRAM, mobo, cpu, virtual memory) or it can be due to a corruption in a software driver (or even malware).

Unfortunately, the dump file doesn't contain much information about the program that caused this. It mostly points to Windows system files - and if they were corrupt there'd be more problems with your system than just the BSOD's.

So, we'll start with having you conduct a memory diagnostic. Here's a link to a free, bootable one: http://www.memtest86.com/
Please read the directions carefully so you can make a boot disk. Then boot with it in the drive. You'll have to press "Esc" as the HP screen first shows up - this will let you access the boot menu and will let you tell the system to boot from the CD/DVD drive.

Let the test run for at least 3 passes - but overnight is better. If it starts spitting errors out, you can stop the test and post back here.
Let us know how it works out and we'll move on from there.

While waiting for a reply, you may want to try the advice here: http://www.bleepingcomputer.com/blogs/usas...?showentry=1252 This will let you know if an infection is present.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#4 rwhjr

rwhjr
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:05:44 AM

Posted 16 January 2009 - 04:18 PM

I ran the memory test... everything OK. Also ran virus scans.. also all OK.

#5 lowtek_otc

lowtek_otc

  • Members
  • 280 posts
  • OFFLINE
  •  
  • Local time:05:44 AM

Posted 16 January 2009 - 07:30 PM

I ran the memory test... everything OK. Also ran virus scans.. also all OK.



If you allowed memtest to complete its full scan with no errors then continue to a hard drive diagnostic test:

http://www.bleepingcomputer.com/forums/t/28744/hard-drive-installation-and-diagnostic-tools/




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users