BSOD: OVERLAPPED_MODULE: Address regions for 'amon' and 'Parport.SYS' overlap

[Whissi]

Hello,

sometimes when I start my computer and login, XP crashes.
I run WinDbg and analyzed the MEMORY.DMP:
{QUOTE->
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details
Loading unloaded module list
......
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: 00000081, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 89dbbec0, address which referenced memory
Debugging Details:
------------------

OVERLAPPED_MODULE: Address regions for 'amon' and 'Parport.SYS' overlap
READ_ADDRESS: 00000081
CURRENT_IRQL: 2
FAULTING_IP:
+ffffffff89dbbec0
89dbbec0 0000 add byte ptr [eax],al
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: explorer.exe
TRAP_FRAME: bacc7f58 -- (.trap ffffffffbacc7f58)
ErrCode = 00000000
eax=00000081 ebx=ffdff000 ecx=89dbbeb4 edx=89dcee48 esi=ffdff9c0 edi=49492872
eip=89dbbec0 esp=bacc7fcc ebp=bacc7fcc iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
89dbbec0 0000 add byte ptr [eax],al ds:0023:00000081=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 89dbbec0 to 805436d0
STACK_TEXT:
bacc7f58 89dbbec0 badb0d00 89dcee48 89d2c918 nt!KiTrap0E+0x238
WARNING: Frame IP not in any known module. Following frames may be wrong.
bacc7fcc 80544e5f 89dcee48 89dbc000 00000000 0x89dbbec0
bacc7ff4 805449cb b565dd44 00000000 00000000 nt!KiRetireDpcList+0x61
bacc7ff8 b565dd44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
805449cb 00000000 00000009 0081850f bb830000 0xb565dd44

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+238
805436d0 f7457000000200 test dword ptr [ebp+70h],20000h
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiTrap0E+238
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1e
FAILURE_BUCKET_ID: 0xD1_nt!KiTrap0E+238
BUCKET_ID: 0xD1_nt!KiTrap0E+238
Followup: MachineOwner
<-QUOTE}
I thought may be Eset wants my Crash-Dump?

[covaro]

@Whissi

Parport.sys is your Parallel port driver. Easiest thing to do if you don't use your parrallel port would be to Disable it in the BIOS and that should alleviate the problem. As far as why that's happening, might need to wait for one of the Eset gang to poke their head in.

-Cov

[alglove]

It is possible that a hardware problem (probably related to RAM) is causing the error. For example, it could be a bad stick of RAM, or more likely, a BIOS setting that is running the RAM too fast (memory timing too tight), or not enough voltage going to the RAM (often a BIOS setting).

I am guessing from the "ntkrpamp.exe" image name that you are running some sort dual-core processor that supports DEP in hardware? (No, I do not think the CPU is the problem. I am just being nosy. ;))

[Whissi]

Thank you guys for your response!
{QUOTE-> Parport.sys is your Parallel port driver. Easiest thing to do if you don't use your parrallel port would be to Disable it in the BIOS and that should alleviate the problem. <-QUOTE}I didn't mention, but I don't use my Parallel port and it is still deactivated in the BIOS!


{QUOTE-> I am guessing from the "ntkrpamp.exe" image name that you are running some sort dual-core processor that supports DEP in hardware? <-QUOTE}Yes, I am running an "AMD Athlon64 X2" processor (but a 32bit Win).

{QUOTE-> It is possible that a hardware problem (probably related to RAM) is causing the error. <-QUOTE}Well, everything is possible :-)

But I am very sure, that my RAM don't cause this problem.

[alglove]

Strange. Very strange. Komisch, even.... ???

Do all of your crash dumps show STOP 0x000000d1 conflicts between AMON.sys and Parport.sys, or are there other types of errors?

[Whissi]

{QUOTE-> Do all of your crash dumps show STOP 0x000000d1 conflicts between AMON.sys and Parport.sys, or are there other types of errors? <-QUOTE}No, there no other types of errors.

This happens only once in ~50 systemboots... it is very rare - but it happens :'(