BSOD with error code 0x00000001E

[xironet]

I have a system made it by myself with motherboard GA-945GCM-S2L with BIOS ver. F7.
Recently upgraded to a legal version of Windows 7. I do get intermittent BSOD crash with error code 1E.
Before, I was running XP Pro, and had 2G RAM running @ 667 MHz. When I decided to upgrade my OS, I changed my RAM to 4G which run @ 800MHz. To make sure that the system benefits from a higher frequency for the RAM, I changed the multiplier in the BIOS and hence my CPU clock speed changed from 2.2GHz to 3GHz.

I understand that 1E error refers to a clash between drivers and memory and personally I don't think it has anything to do with over clocking as the system has been designed for over clocking. I need to find out which driver is causing the problem. By the way, I have got SP1 installed as well and have updated Windows fully.
I have attached SF file as well as all the dump files and I am hoping that someone can analyse this files and tell me what to do. Also my IE8 keeps crashing and recovering, and a system like this which should be very fast is indeed extremely slow. I have check the Windows performance and have noticed that CPU and RAM running at full. Any advice will be very much appreciated. (exlorer does not open in order to attach my files. I try to do that from a different system later on)

Thanks

Regards,

Hamid

 

[x BlueRobot]

Please follow - http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[xironet]

Error Code 1E - systems files uploaded

Hi ,

I managed to upload my dump files and the SF files. Please take a look and comment.

Thanks

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000420[/COLOR], fffff80002abc264, fffff8800435eb40, 0}

*** WARNING: Unable to verify timestamp for eamonm.sys
*** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
Probably caused by : [COLOR="Red"]eamonm.sys[/COLOR] ( eamonm+9172 )

Usual causes:  System service, Device driver, graphics driver, memory

0: kd> [COLOR="SeaGreen"]lmvm eamonm[/COLOR]
start             end                 module name
fffff880`084ce000 fffff880`085b0000   eamonm   T (no symbols)           
    Loaded symbol image file: eamonm.sys
    Image path: \SystemRoot\system32\DRIVERS\eamonm.sys
    Image name: eamonm.sys
    Timestamp:        [COLOR="red"]Tue Aug 02 10:33:29 2011[/COLOR] (4E37C469)
    CheckSum:         0003DB0B
    ImageSize:        000E2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The driver which is being blamed as a possible cause belongs to your ESET program, please remove ESET using the ESET Removal Tool, and then install and run full scans with these free alternatives which work the best with Windows 7 due to their lightweight nature on system resources and compatibility with the Windows operating system.

Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

   Information

Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:

• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Remove:

Start Menu\Programs\ESET\ESET Smart Security
Start Menu\Programs\ESET

0: kd> [COLOR="seagreen"]!error c0000420[/COLOR]
Error code: (NTSTATUS) 0xc0000420 (3221226528) - An assertion failure has occurred.

From what I have found, assertions are used in programs written in C++, to enable the program to close with a more obvious cause for the crash. It's basically used by programmers to make debugging much easier.