BSOD crash - efter brug af logitech mus
Periodisk crasher min XP computer lige inde den loader logon menuen - dette er sket efter brug at en logitech nx60 trådløs laptop mus som har en lille usb modtager. Det er næsten sikkert at den vil crashe hvis modtagere sidder i computeren under bootup, men den er også begyndt at gøre selvom modtagere ikke sidder i.Har prøvet at have modtagere tilsluttet andre copmutere med XP som ikke oplever denne fejl, så den må konflikte med nogle af mine drivers - vil jeg mene..
Jeg har debugget et minidump - måske siger det Jer mere, end det siger mig.
Vh. Steffen
Loading Dump File [C:\WINDOWS\Minidump\Mini053007-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed May 30 15:26:22.609 2007 (GMT+2)
System Uptime: 0 days 0:00:20.375
Loading Kernel Symbols
.........................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {f00010d5, 1c, 0, 805029e0}
Unable to load image nv4_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
Probably caused by : nv4_mini.sys ( nv4_mini+5e7cf )
Followup: MachineOwner
---------
0: 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: f00010d5, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 805029e0, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: f00010d5
CURRENT_IRQL: 1c
FAULTING_IP:
nt!KiSetAffinityThread+1a
805029e0 8b4010 mov eax,dword ptr [eax+10h]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0xA
PROCESS_NAME: csrss.exe
LAST_CONTROL_TRANSFER: from 804fd0fc to 805029e0
STACK_TEXT:
baa7753c 804fd0fc 3fffffff 00000000 fffffffe nt!KiSetAffinityThread+0x1a
baa7754c b9f087cf 00000000 00000002 8a041468 nt!KeSetAffinityThread+0x1c
WARNING: Stack unwind information not available. Following frames may be wrong.
baa77558 8a041468 8a051238 8a40d000 8a3c0228 nv4_mini+0x5e7cf
baa7755c 8a051238 8a40d000 8a3c0228 ba10a9fa 0x8a041468
baa77560 8a40d000 8a3c0228 ba10a9fa 8a051238 0x8a051238
baa77564 8a3c0228 ba10a9fa 8a051238 00000001 0x8a40d000
baa77568 ba10a9fa 8a051238 00000001 00000000 0x8a3c0228
baa7756c 8a051238 00000001 00000000 8a40d000 nv4_mini+0x2609fa
baa77570 00000000 00000000 8a40d000 8a3c0228 0x8a051238
STACK_COMMAND: kb
FOLLOWUP_IP:
nv4_mini+5e7cf
b9f087cf ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nv4_mini+5e7cf
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_mini
IMAGE_NAME: nv4_mini.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 458ae7b4
FAILURE_BUCKET_ID: 0xA_nv4_mini+5e7cf
BUCKET_ID: 0xA_nv4_mini+5e7cf
Followup: MachineOwner
---------
