Re: another page fault that i am not able to debug (urgent help required)

Hi
a system thread runs at dispatch or passive level. So i thought
anything executed from within a system thread is bound to be running
at the same irql except ofcours something like acquring a spin lock which
raises its irql or an explicit call to raise ur irql
By any means now i am experiencing the following problem:
PAGED_FAULT_IN_NON_PAGED_AREA. i searched the documentation and found
that it meant ur are accessing(read/write) some prohibited area.
Is there any way that i can know what actually is causing this??
the stack does not show anything meaningfull results. at the time of the
fault
the address written/read is shown as well as the who wrote is shown in the
form
of an address. How can that be used to debug

Pls Help

thanks
mayank

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of James Antognini
Sent: Monday, July 14, 2003 9:42 PM
To: Windows System Software Developers Interest List
Subject: [ntdev] Re: another page fault that i am not able to debug
(urgent help required)

You misunderstand what a system thread guarantees (very little). IRQL
has nothing to do with it.

Did you use to work in a different OS?


If replying by e-mail, please remove “nospam.” from the address.

James Antognini
Windows DDK MVP


You are currently subscribed to ntdev as:
xxxxx@intersolutions.stpn.soft.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

The documentation below, says a little different, basically your hardware or your driver is broken,
fix it.

Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting

The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 Memory address referenced
2 0: Read operation
1: Write operation

3 Address that referenced memory (if known)
4 Reserved

If the driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.

Cause
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Resolving the Problem
Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner’s manual for your computer.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

Comments
Typically, this address is in freed memory or is simply invalid.

This cannot be protected by a try - except handler - it can only be protected by a probe.

----- Original Message -----
From: “Mayank Kumar”
To: “Windows System Software Developers Interest List”
Sent: Monday, July 14, 2003 12:59 PM
Subject: [ntdev] Re: another page fault that i am not able to debug (urgent help required)

> Hi
> a system thread runs at dispatch or passive level. So i thought
> anything executed from within a system thread is bound to be running
> at the same irql except ofcours something like acquring a spin lock which
> raises its irql or an explicit call to raise ur irql
> By any means now i am experiencing the following problem:
> PAGED_FAULT_IN_NON_PAGED_AREA. i searched the documentation and found
> that it meant ur are accessing(read/write) some prohibited area.
> Is there any way that i can know what actually is causing this??
> the stack does not show anything meaningfull results. at the time of the
> fault
> the address written/read is shown as well as the who wrote is shown in the
> form
> of an address. How can that be used to debug
>
>
> Pls Help
>
>
> thanks
> mayank

> By any means now i am experiencing the following problem:

PAGED_FAULT_IN_NON_PAGED_AREA.

Dereferencing a stray pointer.
What is the call stack? what !analyze -v says?

Max

hi maxim,
i am a new user to softice
is this analyze part of softice ?? or something else
does softice have a similar utility to analyze code
for such errors??
mayank

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
Sent: Tuesday, July 15, 2003 1:27 AM
To: Windows System Software Developers Interest List
Subject: [ntdev] Re: another page fault that i am not able to debug
(urgent help required)

By any means now i am experiencing the following problem:
PAGED_FAULT_IN_NON_PAGED_AREA.

Dereferencing a stray pointer.
What is the call stack? what !analyze -v says?

Max


You are currently subscribed to ntdev as:
xxxxx@intersolutions.stpn.soft.net
To unsubscribe send a blank email to xxxxx@lists.osr.com