View Single Post
05 Jun 2010  
CarlTR6

Windows 7 Ultimate 32 bit
 
 

I looked at your five most recent dumps. All of them point to hardware errors specifically device drivers and memory.

Quote:
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

BSOD Index


STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

BSOD Index


STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel

BSOD Index


STOP 0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH

Usual causes: Device driver, System DLL corruption, Faulty hardware in I/O path (a disk error, faulty RAM, or a corrupted page file), BIOS

BSOD Index
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BugCheck 1E, {ffffffffc0000005, fffff80002afd13c, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiAllocatePagedPoolPages+4fc )

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  CCC.exe


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BugCheck A, {2000000, 2, 1, fffff80002a7f14c}

Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+13c )

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BugCheck 1A, {41284, fffff9800175a001, 29d, fffff780c0000000}

Probably caused by : CI.dll ( CI!I_ReloadCatalogs+14a )

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C0000221, {fffff8a0001e3010, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5ff )

Followup: MachineOwner
I looked at one of the files listed in your dumps as a possible cause. It is CI.dll.
Quote:
The process Alcohol 120% or ci.dll belongs to the software ci.dll or Alcohol 120% by Alcohol Soft Development Team.

Description: ci.dll is located in the folder C:\Windows\System32. This .dll file is a Browser Helper Object (BHO) that runs automatically every time you start your Internet browser
Alcohol is a known cause of BDOD's in Win 7. I also found that CI.dll can be a legitimate Windows dll as well as a malware BHO.

Start by uninstalling Alcohol if you have it installed.

Next download and install Malwarebytes and do a thorough scan of your system.

After you have done this, post back and we will take things from there.
My System SpecsSystem Spec