How to debug a Stop 0x50?

[Dave Parker]

I'd like to find out if there is a way to debug a STOP 0x50
given that I have the STOP message and a memory dump.

I can reproduce the STOP message reliably by running
certain applications. For instance, attempting to install
AOL 9.0 gets it 85% of the way through installation and MS
Publisher gets it when I select insert->picture.

The Stop message is:

STOP 0x00000050(0xFFFFFEF8,0x00000000,0x8053434E,0x00000000)

PAGE_FAULT_IN_NONPAGED_AREA

The computer runs reliably as long as I stay away from the
handful of applications/operations.

What I've done so far:

On my Compaq Presario 7PL290, I have 3 memory DIMMs
installed. I configured the system so that each DIMM was
the only one installed (in slot 1) and verified the problem
persisted. After this, I installed 1 of the DIMMs in slot
2 (alone) and the problem persisted. I'd like to believe
that I've ruled out a memory problem (the STOP message was
identical in each case).

I then installed the latest BIOS, Nvidia driver, and any
updated drivers from Windows update. Problem persists.

I tried starting my system in Safe Mode and was able to
reproduce the problem.

I ran the application with Norton Antivirus enabled and
disabled. Problem persists.

It's not obvious to me that any software or hardware
install coincided with the start of the problem.

So, back to my original question. Is there a way to get
valuable information from the stop message and the memory dump?

Thanks!

 

[Dave Parker]

Just to add a little more...

I've tried running verifier.exe. I set it to check all
installed drivers and reboot.

During XP startup, I get a BSOD that is so brief that I
cannot read it. I have no idea if it is the same error or
not. Unfortunately, since there is no way to get the
system run with verifier enabled, I cannot figure out how
to get any useful data from it.

Dave

 

[Rick \Nutcase\ Rogers]

Hi Dave,

A 0x50 stop error can have several causes, some "light" reading for you:

STOP: 0x00000050 Page_Fault_In_Non-Paged_Area Error After Installing Service
Pack 1 (SP1)
http://support.microsoft.com/?kbid=329293

Error Message: STOP 0x00000050 (0xffffffe0, 0x00000001, 0xf30da010,
0x00000000) PAGE_FAULT_IN_NONPAGED_AREA
http://support.microsoft.com/?kbid=817197

"STOP 0x00000050" Error Message in Stac97.sys After You Upgrade Your
Panasonic Toughbook to Windows XP Service Pack 1
http://support.microsoft.com/?kbid=329832

"STOP 0x0000008e" Error Message During Windows XP Setup
http://support.microsoft.com/?kbid=315335

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

 

[Dave Parker]

Hi Rick,

Thanks a bunch for taking the time to reply. I looked
through the 4 pointers you provided with no luck. I even
followed the instructions on the first although this
problem did not occur during XP setup.

Do you have any ideas on how I can get info out of
"verifier" given what I wrote in my second post? Turning
on verifier does result in a BSOD but the BSOD isn't
visibile for even a second.

Dave

 

[Guest]

More info....

I got adventurous and installed the MS Debugging Tools.
Unfortunately, it didn't show me anything definitive. The
summary info I could get is:

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: fffffef8, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8053434e, If non-zero, the instruction address which
referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


READ_ADDRESS: fffffef8 Nonpaged pool expansion

FAULTING_IP:
nt!ExFreePoolWithTag+1f6
8053434e 668b4efa mov cx,[esi-0x6]

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 00000000 to 804f4103

STACK_TEXT:
f484788c 00000000 00000000 00000000 00000000
nt!KeBugCheckEx+0x19


FOLLOWUP_IP:
nt!ExFreePoolWithTag+1f6
8053434e 668b4efa mov cx,[esi-0x6]

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!ExFreePoolWithTag+1f6

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

BUCKET_ID: ZEROED_STACK

MODULE_NAME: Unknown_Module

Followup: MachineOwner

 

[Rick \Nutcase\ Rogers]

Hi Dave,

It does look like a driver or misbehaing software issue, but it might be
tough to find. Start by booting clean:

HOW TO: Perform Advanced Clean-Boot Troubleshooting in Windows XP
http://support.microsoft.com/?kbid=316434

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone



More info....

I got adventurous and installed the MS Debugging Tools.
Unfortunately, it didn't show me anything definitive. The
summary info I could get is:

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: fffffef8, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8053434e, If non-zero, the instruction address which
referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


READ_ADDRESS: fffffef8 Nonpaged pool expansion

FAULTING_IP:
nt!ExFreePoolWithTag+1f6
8053434e 668b4efa mov cx,[esi-0x6]

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 00000000 to 804f4103

STACK_TEXT:
f484788c 00000000 00000000 00000000 00000000
nt!KeBugCheckEx+0x19


FOLLOWUP_IP:
nt!ExFreePoolWithTag+1f6
8053434e 668b4efa mov cx,[esi-0x6]

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!ExFreePoolWithTag+1f6

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

BUCKET_ID: ZEROED_STACK

MODULE_NAME: Unknown_Module

Followup: MachineOwner