Bugcheck 0x10000050, what is it?

NTDEV
1

Hi,

I get bugcheck code 0x10000050 on my PC (not a test machine, not one of
those dev machines). Does anyone know what it means?

The DDK (for 2003 SP1) does not list it.

Thanks,

Oliver

2

Try treating the bugcheck data as if it were a bugcheck 0x50, does it
make sense in that context?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Oliver Schneider
Sent: Thursday, February 09, 2006 4:56 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Bugcheck 0x10000050, what is it?

Hi,

I get bugcheck code 0x10000050 on my PC (not a test machine, not one of
those dev machines). Does anyone know what it means?

The DDK (for 2003 SP1) does not list it.

Thanks,

Oliver

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

3

Check this out it may help.
http://www.sun.com/desktop/products/sunpci/bsod.pdf

Regards.
William Michael Jones “Mike”

“Oliver Schneider” wrote in message
news:xxxxx@ntdev…
> Hi,
>
> I get bugcheck code 0x10000050 on my PC (not a test machine, not one of
> those dev machines). Does anyone know what it means?
>
> The DDK (for 2003 SP1) does not list it.
>
> Thanks,
>
> Oliver
>
>

4

Thanks Doron. Yes it makes sense now and the minidump analysis shows the
reason as 0x50 == PAGE_FAULT_IN_NONPAGED_AREA (below), as you had suggested.
Is this a general rule to take the lower 2 digits and check whether "it
makes sense" (while this can already be a problem without a dump
file).

Cheers,

Oliver

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

Debugging Details:

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 439cec0d

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
e2fa0ffc

FAULTING_IP:
ativvaxx+14867
bfd01867 892c8f mov [edi+ecx*4],ebp

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 00000000 to bfd01867

STACK_TEXT:
00000f64 00000000 00000000 00000000 00000000 ativvaxx+0x14867

FOLLOWUP_IP:
ativvaxx+14867
bfd01867 892c8f mov [edi+ecx*4],ebp

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: ativvaxx+14867

MODULE_NAME: ativvaxx

IMAGE_NAME: ativvaxx.dll

STACK_COMMAND: kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

--

May the source be with you, stranger :wink:

ICQ: #281645
URL: http://assarbad.net