in the logs may this also be related to same issue.
Could anyone help me figuring out the cause of this. whether it is due to any driver or hardware failure. I am also attaching a dump files along with the thread.
Pls help me with the resolution asap. thanks

A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

I am leaning more to a driver issue though due to the following:

The first two minidumps cite the probable cause as savrt.sys which is an Auto Protect driver for Symantec Anti-virus. In the read SYMEVENT.SYS was unable to load which is also a driver for this anit-virus software.

The second two mnidumps point to afd.sys which is an Acillary Function Driver for Winsock which is part of your Windeos OS. In the mix was RTvscan.exe which is the exexcutible for Symantec's Realytime Scanner.

This executible from what I have read is a resource hog but essential. it should not be terminated.

So, here are some suggestions:

1. Run msconfig

2. Run chkdsk

3. Update your anti-virus. There are updates for savrt.sys

4. One piece of hardware I have heard people needed to change out with this issue with savrt.sys was their Nic card.

I have seen people here correct a lot of issues by updating everything they can think of this includes the drivers for the chipset, audio and video as well as firmware; sometimes the BIOS but if has been quite some time I would update this as well but make sure you back everything first.

Here's the thing: You have an updated anti-virus but outdated drivers and firmware for your hardware. Potential conflicts???