i found a way to get into this log … it does not look like an issue with avast but is there anyone that can read this thing a little better then me? …
Opened log file ‘c:\debuglog.txt’
Microsoft ® Windows Debugger Version 6.7.0005.1
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini092807-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRVc:\symbolshttp://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) MP (4 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: Fri Sep 28 19:41:29.093 2007 (GMT-4)
System Uptime: 0 days 0:24:52.714
Loading Kernel Symbols
…
Loading User Symbols
Loading unloaded module list
…
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {0, 2, 1, f63832b5}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_RemoveBadReqIrp+6b )
Followup: MachineOwner
0: kd> !analyze -v;r;kv;lmtn;.logclose;q
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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f63832b5, address which referenced memory
Debugging Details:
WRITE_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_RemoveBadReqIrp+6b
f63832b5 8907 mov dword ptr [edi],eax
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from 804f1ad5 to f63832b5
STACK_TEXT:
80550284 804f1ad5 41426d72 86050458 8611f0e0 USBPORT!USBPORT_RemoveBadReqIrp+0x6b
8055029c f6383085 8611f102 00000000 8611f0e0 nt!IoCsqRemoveNextIrp+0x3d
805502bc f6383650 8611f028 00000000 f63834ec USBPORT!USBPORT_BadRequestFlush+0x3b
805502e0 805016f7 8611f70c 8611f028 177b689c USBPORT!USBPORT_DM_TimerDpc+0x164
805503fc 80501813 8055b0a0 ffdff9c0 ffdff000 nt!KiTimerListExpire+0x14b
80550428 805450bf 8055b4a0 00000000 0001752d nt!KiTimerExpiration+0xb1
80550440 8055ae40 ffdffc50 00000000 8055ae40 nt!KiRetireDpcList+0x61
80550450 80544fa4 00000000 0000000e 00000000 nt!KiIdleThread0
80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_RemoveBadReqIrp+6b
f63832b5 8907 mov dword ptr [edi],eax
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62
SYMBOL_NAME: USBPORT!USBPORT_RemoveBadReqIrp+6b
FAILURE_BUCKET_ID: 0xD1_W_USBPORT!USBPORT_RemoveBadReqIrp+6b
BUCKET_ID: 0xD1_W_USBPORT!USBPORT_RemoveBadReqIrp+6b
Followup: MachineOwner
… there is more but ive exceeded the allowed message length