Recent Multiple BSOD's. CI.DLL, Memory Corruption, NTKRNLMP.EXE

Over the course of the last few months, I have been getting random BSOD's and crash's. I leave my PC on 24/7 and most of the time it runs great once it finally gets booted. A few times recently, I'll leave it at the desktop overnight and come back the next day to find a BSOD.

At some points it takes me 5-7 times of powering on and off to finally get it to boot into windows, otherwise it just BSOD's most of the time. Each BSOD shows a different code as well.

I tried memtest86+, i let it run for about 19 hours. It had either 13 or 18 complete pass's and 0 errors.

Im not sure if its a hardware failure, software clashing, or driver issues. Computer was customer built by myself about 5 years ago.

Any help would be great appreciated, as its really frustrating. At times I have to sit for about 20 minutes and hit the power button numerous times to get windows to finally boot. It's also been running much slower than usual.

I have ESET NOD32 AV if that makes a difference. No Wifi on this computer either.

Attached is the .zip of my dump files and other information. I hope I posted this correctly.

koolkat77 said:

Eset can be a cause of BSOD's. Remove and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Microsoft Security Essentials and Malwarebytes, both recommended from a strict BSOD perspective.

Microsoft Security Essentials, Free antivirus for windows

Malwarebytes Anti-Malware Free

   Information

DO NOT start the free trial of MalwareBytes. Deselect the option when prompted.

Hard Drive/Storage

Post a screen shot using Crystal Disk Info: CrystalDiskInfo Standard Edition

How to Upload and Post a Screenshot and File in Seven Forums

Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

Daemon Tools/Alcohol %

Code:

Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public

Uninstall DAEMON Tools and/or Alcohol % software. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO

SFC scannow

Check windows for corruption:

SFC /SCANNOW Command - System File Checker

1. Click on the Start
2. Scroll to Accessories
3. Select Command Prompt > Right click and Run as Administrator
4. Type
   Code:

   SFC /scannow

Start up

Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.

Troubleshoot Application Conflicts by Performing a Clean Startup
Startup Programs - Change

-Blow out all vents with canned air (DO NOT use a vacuum cleaner or an air compressor, they can damage the components).
-Ensure that the fan comes on and is blowing air out of the vent (may not happen at startup, but should happen after using it for a while).

Temperature

For monitoring heat of the system, use Speccy or HWMonitor:
Speccy System Information
HWMonitor

Check for a BIOS update.

Code:

BIOS Version/Date	Award Software International, Inc. F10, 2/5/2010

Stress Test

Hardware - Stress Test With Prime95: Hardware - Stress Test With Prime95

CPU - Stress Test Using IntelBurnTest: CPU - Stress Test Using IntelBurnTest

Video Card - Stress Test with Furmark: Video Card - Stress Test with Furmark

Monitor temperature of the system during the tests: Speccy - System Information - Free Download

Hope this helps for now

Thanks KoolKat, I will try this now and submit my results with what happens.

Well it seems like something I did must have worked. Computer has been pretty stable the past week, and haven't gotten any little blue suprises.

I haven't tried shutting it down, or installing any updates though. Usually when updates would automatically install and had to restart my computer, or I powered off and then tried turning back on, thats when the problem arised.

So far so good though, and the one time I had to power it back on and restart to change some settings and remove programs, I didn't get any BSOD's then either!!

Thanks KoolKat!!!!!