WinDbg problem!

[RobbyD2]

Hi I've been getting some blue screens as of lately so ran WinDbg and came out with this message, i no its a driver but carnt work out which one! any advice? thanks in advance

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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 80535ef8, address which referenced memory

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

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


FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b08

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

CURRENT_IRQL: 2

FAULTING_IP:
nt!memmove+108
80535ef8 89448fe8 mov [edi+ecx*4-0x18],eax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from f4788fbd to 80535ef8

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
80548da0 f4788fbd 864e34e0 86c2e140 00000018 nt!memmove+0x108
80548dc8 f462e0cb 00000018 86c2e140 862473d8 mouclass+0xfbd
80548e2c 80540d5d 86c60810 01c60600 00000000 i8042prt+0x80cb
ffdff980 00000000 f78a7000 0014d575 00000000 nt!KiDispatchInterrupt+0x35d


FOLLOWUP_IP:
mouclass+fbd
f4788fbd 8b4510 mov eax,[ebp+0x10]

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: mouclass+fbd

MODULE_NAME: mouclass

IMAGE_NAME: mouclass.sys

STACK_COMMAND: kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

 

[linney]

To my untrained eye, things that stand out to me are -

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

mouclass.sys - which is probably a mouse driver.

IRQL: 2.


Running MsInfo32 and looking at Hardware Resources/ IRQ and Conflicts-Sharing, and Components/ Input/ Pointing Devices, might offer a few clues?

Description of Windows XP System Information (Msinfo32.exe) Tool

http://support.microsoft.com/default.aspx?scid=kb;en-us;308549&FR=1&PA=1&SD=HSCH

For some practical help with Debugging have a look at these threads.

Windows Debugger, part of Never-Ending-Problem
thread779-1064535

Getting more friendly logs from Drwatson.
thread779-947690


Search this long thread for the word "Debug"
Third copy attempt on 2GB data files = BSOD!
thread779-1025514

 

[RobbyD2]

thanks 4 the reply linney,ill have a look into MsInfo32 and check out those sites and let u no if i come up with anything useful, thanks again for the reply