Tech Support > Microsoft Windows > Drivers > Re: question for AllocateCommonBuffer and How to send user mode memory data to kernel
Re: question for AllocateCommonBuffer and How to send user mode memory data to kernel
Posted by paullee on March 10th, 2005


I got two bugcheck code when I run the code that I list above,Can
anyone help me??
Thanks a lot

================================================== ===================
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid)
address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0a070007, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f864d60a, address which referenced memory

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


WRITE_ADDRESS: 0a070007

CURRENT_IRQL: 2

FAULTING_IP:
pci2002+660a
f864d60a f3a5 rep movsd

CUSTOMER_CRASH_COUNT: 6

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 805344b1 to 804f6471

STACK_TEXT:
ef83ab28 805344b1 0000000a 0a070007 00000002
nt!MiWaitForInPageComplete+0x275
ef83ab44 ffffffff ffffffff ffffffff ffffffff
nt!MmProtectMdlSystemAddress+0x267
ffffffff 00000000 00000000 00000000 00000000 0xffffffff


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
pci2002+660a
f864d60a f3a5 rep movsd

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: pci2002+660a

MODULE_NAME: pci2002

IMAGE_NAME: pci2002.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3c3238b9

BUCKET_ID: 0xD1_W_pci2002+660a

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

================================================== ==================
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid)
address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0b515b4c, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804fd4aa, address which referenced memory

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


READ_ADDRESS: 0b515b4c

CURRENT_IRQL: 1c

FAULTING_IP:
nt!RtlpStatusTable+242
804fd4aa 3b78fc cmp edi,[eax-0x4]

CUSTOMER_CRASH_COUNT: 9

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 805344b1 to 804f6471

SYMBOL_ON_RAW_STACK: 1

STACK_TEXT:
8053f230 805344b1 0000000a 0b515b4c 0000001c
nt!MiWaitForInPageComplete+0x275
8053f24c 00000001 f01fcec0 f01fce80 f01fce80
nt!MmProtectMdlSystemAddress+0x267


STACK_COMMAND: dds @$csp ; kb

FOLLOWUP_IP:
rdbss!_imp__ExAcquireResourceExclusiveLite+3
f01fcec0 ?? ???

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: rdbss!_imp__ExAcquireResourceExclusiveLite+3

MODULE_NAME: rdbss

IMAGE_NAME: rdbss.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de248

BUCKET_ID: 0xA_rdbss!_imp__ExAcquireResourceExclusiveLite+3

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

================================================== ===================