Hi all
This is my first driver work so feeling loots of problem.
I have created a ndis protocol driver to sniff the network. But when it
starts my system got fail down.
here is the bugcheck detail
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 00000016, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804ea337, address which referenced memory
plese tell me where i am commiting the mistake.
Thanks
Niraj Jha
Software Engineer
Pure Thoughts Technology
You are dereferencing a NULL or illegal pointer. Look at the stack trace
for this, and the first entry with your driver in it is the point of the
problem. You are likely either using a NULL pointer directly or passing it
in to a routine that expects a valid pointer.
While the various groups will answer these, this is one that you should have
been able to find yourself, from either the WinDBG documentation which has a
good description of bugcheck’s or through seaching the groups. The
“experts” on this group, got there by digging and finding how to get
answers, rather than just asking questions.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Niraj Jha” wrote in message news:xxxxx@ntdev…
Hi all
This is my first driver work so feeling loots of problem.
I have created a ndis protocol driver to sniff the network. But when it
starts my system got fail down.
here is the bugcheck detail
kd> !analyze -v
Bugcheck Analysis
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: 00000016, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804ea337, address which referenced memory
plese tell me where i am commiting the mistake.
Thanks
Niraj Jha
Software Engineer
Pure Thoughts Technology