newbee DRIVER_IRQL_NOT_LESS_OR_EQUAL problem

> Hi All,
>
> I am trying to write my first Windows driver, although I have written
> Solaris drivers.
>
> The problem is that when the device interrupts I get a
> DRIVER_IRQL_NOT_LESS_OR_EQUAL error. The address quoted as the fault
> address is in fact the address of the ISR. As far as I am aware all the
> code is locked into memory.
>
> I feel it must be something simple I am missing but I don't know what.
>
> Cheers Paul.
>
> Below is the WinDbg output.
>
> 0: kd> !analyze -v
> ************************************************** *****************************
> * *
> * Bugcheck Analysis *
> * *
> ************************************************** *****************************
>
> 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: f77886b0, memory referenced
> Arg2: 00000007, IRQL
> Arg3: 00000008, value 0 = read operation, 1 = write operation
> Arg4: f77886b0, address which referenced memory
>
> Debugging Details:
> ------------------
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> ************************************************** ***********************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!KPRCB ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!KPRCB ***
> *** ***
> ************************************************** ***********************
> ************************************************** ***********************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> ************************************************** ***********************
>
> FAULTING_MODULE: 804d7000 nt
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 0
>
> WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
> unable to get nt!MmSpecialPoolEnd
> unable to get nt!MmPoolCodeStart
> unable to get nt!MmPoolCodeEnd
> f77886b0
>
> CURRENT_IRQL: 7
>
> FAULTING_IP:
> LaserBus+16b0
> f77886b0 ?? ???
>
> DEFAULT_BUCKET_ID: WRONG_SYMBOLS
>
> BUGCHECK_STR: 0xD1
>
> LAST_CONTROL_TRANSFER: from f77886b0 to 805436d0
>
> STACK_TEXT:
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 8055031c f77886b0 badb0d00 00000002 00000000 nt!Kei386EoiHelper+0x2834
> 00000000 00000000 00000000 00000000 00000000
> <Unloaded_LaserBus.sys>+0x16b0
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_IP:
> LaserBus+16b0
> f77886b0 ?? ???
>
> SYMBOL_STACK_INDEX: 1
>
> SYMBOL_NAME: LaserBus+16b0
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: LaserBus
>
> IMAGE_NAME: LaserBus.sys
>
> BUCKET_ID: WRONG_SYMBOLS
>
> Followup: MachineOwner