[BSOD] WIndows XP SP3

Status
Not open for further replies.

Zarathos

TS Rookie
Hi all! I'm new to this forum and I hope someone will be able to help me!
I have an ASUS Laptop G71V with Windows XP SP3 installed. The programs that I'm usually running on it are: Kaspesky Internet Security 9.0 (always, in background), Windows Live Messenger 8.0 (always), ICQ 6.5 (sometimes), Internet Explorer 8.0 (my default browser) and Visual Studio 2005 SP1.
Drivers are all up to date. PC never crashed before with this hardware/software configuration. Nothing has been added and/or installed.

Ten days ago my computer got a BSOD but I forgot to recover and analyze the minidump. The first time I was using my webcam on WLM. This one I had VS2005 opened and I was browsing a website with IE8. This is the crash analysis:


Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720



************************************
Bugcheck Analysis
************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {80002, 1c, 0, 8050216b}

Probably caused by : ntkrpamp.exe ( nt!KiTimerListExpire+a7 )

Followup: MachineOwner



************************************
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: 00080002, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8050216b, address which referenced memory

READ_ADDRESS: 00080002

CURRENT_IRQL: 1c

FAULTING_IP:
nt!KiTimerListExpire+a7
8050216b 807f0220 cmp byte ptr [edi+2],20h

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 8050232b to 8050216b

STACK_TEXT:
805513fc 8050232b 8055c0c0 ffdff9c0 ffdff000 nt!KiTimerListExpire+0xa7
80551428 80545e7f 8055c4c0 00000000 00206048 nt!KiTimerExpiration+0xb1
80551450 80545d64 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTimerListExpire+a7
8050216b 807f0220 cmp byte ptr [edi+2],20h

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTimerListExpire+a7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3

FAILURE_BUCKET_ID: 0xA_nt!KiTimerListExpire+a7

BUCKET_ID: 0xA_nt!KiTimerListExpire+a7

Followup: MachineOwner
I would be glad to find a solution for a problem that could become really boring. Thank you in advance for your help!
 

Attachments

Route44

TechSpot Ambassador
OxA errors are caused by either hardware or drivers attempting to address a higher IRQ Level than they are desined/inteded to do.

When do your BSODs occur other than what you have reported? From what you have listed both occured while using/connected to the internet.

Are your NIC drivers up-to-date?
 
Status
Not open for further replies.