Multiple BSOD crashes. Antivirus programs keep shutting

[appletree]

Hi

i have been experiencing multiple BSOD crashes for the last couple of days.

The first few resulted in a completely black screen with just the mouse pointer. I managed to boot from a recovery disk and deleted Eusing reg cleaner and Rapport End Point.
This helped and i can now start up in safe mode and normal mode.
However still getting error messages in windows and BSOD crashes.

It took me ages to download Malware bytes as the installation kept crashing. Eventually installed it but it then BSOD half way through the scan.
Super Anti spyware shows no infections.
Also have McAfee installed but that keeps crashing too!

The system seems more stable in safe mode & clean boot, but not always.

Not sure if its a virus or software/other problem

Log file is attached.

Any help would be appreciated.

 

[Arc]

Hi appletree.

First of all, you need to uninstall McAfee. It is such a program that no further troubleshooting is possible till it is present there.

Uninstall McAfee Using McAfee Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Another very important thing, you have a 64 bit OS installed on a computer having only 2 GB RAM. That is not desired. You should use 32 bit windows on such a computer.

So install 32 bit windows, dont get McAfee back there, use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Let us know for any further BSOD.
_________________________________________

BugCheck 1A, {41201, fffff683ff7e74b8, d730000062c19867, fffffa80033f7680}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 )

Followup: MachineOwner
---------

BugCheck 1A, {41790, fffffa8000ba31b0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
---------

BugCheck 4E, {99, 3e437, 1, 3daf7}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

BugCheck 18, {0, fffffa8003bc3b30, 2, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48de1 )

Followup: MachineOwner
---------

 

[appletree]

Thanks for your reply.

It wont let me uninstall Mcafee, when i try an error window comes up saying the McAfee UI has stopped working and quits.

This is also happening with other programs when trying to run.

Also i use Chrome as my browser and i am getting constant "aw snap" errors when trying to load a web page, i think this may be related.

The PC is aprox 3 years old and has zero problems until now. McAfee installed from day one. No other recent program installs.

Im lost as to whether its a virus that cant be found/fixed or a memory/hard drive problem?

 

[Arc]

It is a memory related issue. Not necessarily the physical RAM, but anything related to memory.

McAfee passes bad info to the memory almost regularly. So that is a very probable cause. Plus, the computers installed memory is not sufficient for 64 bit OS.

Better you follow the bold lines of post #2.

 

[appletree]

OK i now have a total system failure.
After backing up my info i used the Dell Windows 7 recovery disk to reinstall Windows.

The first installation seemed to install ok. But after about 5 mins got another BSOD.
After reboot windows would not load.

Ran the install disk again. It now gets all the way to the end of installation and comes up with an error message of "cannot install required files. They may be corrupt or missing. error code 0x80070570"
This happens on every attempt.

Now upon switching it on it says unable to find boot device and can only run from the recovery disk.

New HD perhaps?

 

[Arc]

Before replacing the hard disk take some more tests. Both of the tests are bootable.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Also test the HDD using Seatools for DOS.

Let us know the results.