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

Hello,

sometimes when I start my computer and login, XP crashes.
I run WinDbg and analyzed the MEMORY.DMP:

I thought may be Eset wants my Crash-Dump?

 

@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

 

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. )

 

Thank you guys for your response!

I didn't mention, but I don't use my Parallel port and it is still deactivated in the BIOS!

Yes, I am running an "AMD Athlon64 X2" processor (but a 32bit Win).

Well, everything is possible

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

 

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?

 

No, there no other types of errors.

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