Thanx in Advance, Crashing BSOD

I'm wondering if someone has time to look at our jcgriff2 and perfmon. Also, bcc ....1a.

And can't figure out why perfmon /report indicates no anti-virus when we had security essentials with the free version of avg, and also now that we have eset, in demo, instead (not in addition to).

Also, we did have to replace four sticks of ram at one point, and discovered a propensity for memtest86 to generate gibberish. After replacing the ram we no longer get errors, but still get gibberish. Replacing the motherboard didn't stop the gibberish either.

Our computer is only a month old. dh67clb3 motherboard, 2 sets of Corsair TW3X4G1333C9 XMS3 4GB 2 X 2 GB PC3-10666 1333Mhz Dual Channel 240-pin DDR3 Desktop Memory, Cooler Master Hyper 212 Plus 120mm Sleeve CPU Cooler, Diablotek 750-Watt ATX Power Supply PHD750, D drive Western Digital WD Caviar Black 1 TB SATA 6 GB/S 7200 RPM 64 MB Cache Internal Bulk/OEM 3.5-Inch Desktop Hard Drive, C drive Lexar Media Crucial 64 GB m4 2.5-Inch Solid State Drive SATA 6Gb/s CT064M4SSD2, and Intel Core i5-2500 Processor 3.3GHz 6 MB Cache Socket LGA1155.

OS is win7x64 home premium full retail installed from bootable installation zipdrive. Thanx in advance.

Ok, I restored a disc image from the day before they tried to install eset.

And because we moved the computer to a new house, I uninstalled the intel network and graphics drivers, updated bios, and then reinstalled the drivers.

Is is possible they tried to download eset for something other than win7x64 svc pack1?

Well actually no, eset removal didn't solve our problem. We didn't remove eset, we flashed an image from the day before we had tried to install eset, an image where we had microsoft security essentials and avg free running side by side.

Unfortunately, the computer kept crashing. And before I could get them to run the diagnostics again, the computer crashed to the point where it wouldn't start.

So we just reflashed our backup image again, and the plan now is to uninstall avg and microsoft security essentials and try to again install eset under a different account name, or what ever we have to do to solve the problem of eset not updating.

If we get more crashing, I'll try to get some more reports to upload. But in the meantime, should we expect that eset will not update during the 30 day trial?

Does the removal tool do something that reformatting and partioning our hard drive doesn't do? Will eset cause a problem with bios or our D:/ drive?

I'll pass the word along that your advice continues to be to run the eset removal tool and then go with microsoft security essentials.

Sent from my ADR6350 using Tapatalk