BSOD error 0x000000C4

My laptop had a BSOD crash last night and one about 3 days ago. The one three days ago I just ignored because it had happened once about 6 months ago, but never since then. I thought it might be nothing. When it happened again last night, I started looking online to see what might be going on. I looked up "irql not less or equal" because that is what it said on the blue screen. (I will attach the information I copied from when the computer restarted.) I found something that told me to try going to the the Driver Verifier Manager, select "Create Standard Settings", select "automatically select all drivers on this computer", and restart. When I did that I got a BSOD that said "A device driver attempting to corrupt the system has been caught. The faulty driver currently on the kernel stack must be replaced with a working version." Under Technical Information it said "***STOP: 0x000000C4 (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)" I took a picture of the screen with my cell phone.

I looked up the part about the faulty driver on the kernel stack and found this forum. I have attached the requested .zip file. Can someone please translate this stuff for me and help me find out what's causing the problem? If you need more info, let me know. You may also have to tell me where to find it, though!

Attachment 364605

Attachment 364606

Thank you for responding. I updated the ELAN driver, but I have a question about disabling driver verifier. It's my (limited) understanding that driver verifier is what runs in the background making sure all the drivers are working properly. Is that true? If so, does disabling it mean that I won't know if there is a problem with a driver?

Arc said:

The STOP: 0x000000C4 BSODs are I think due to driver verifier. Have you enabled driver verifier? Disable it now.

The ELan pad is causing the BSODs as far as I am seeing. Try to update the driver to it. ELAN Microelectronics Corp.

Let us know the result.
______________________________________________________

Code:

BugCheck D1, {fffffa86061d4260, 2, 0, fffff88005f8a821}

*** WARNING: Unable to verify timestamp for ETD.sys
*** ERROR: Module load completed but symbols could not be loaded for ETD.sys
Probably caused by : ETD.sys ( ETD+f821 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa86061d4260, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88005f8a821, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b1100
GetUlongFromAddress: unable to read from fffff800030b11c0
 fffffa86061d4260 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
ETD+f821
fffff880`05f8a821 8a944bec000000  mov     dl,byte ptr [rbx+rcx*2+0ECh]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFFF88003792FB0

TRAP_FRAME:  fffff8800378b980 -- (.trap 0xfffff8800378b980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=00000002fffffffa
rdx=fffffa800755dc10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005f8a821 rsp=fffff8800378bb10 rbp=fffffa800755dc10
 r8=00000000fffffffe  r9=fffff8800378bcd8 r10=000000000000002c
r11=fffffa8005dd1d44 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
ETD+0xf821:
fffff880`05f8a821 8a944bec000000  mov     dl,byte ptr [rbx+rcx*2+0ECh] ds:00000006`000000e0=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e73e69 to fffff80002e748c0

STACK_TEXT:  
fffff880`0378b838 fffff800`02e73e69 : 00000000`0000000a fffffa86`061d4260 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0378b840 fffff800`02e72ae0 : fffffa80`061c17b0 fffff880`05f69360 00000000`0000001a fffffa80`061d4180 : nt!KiBugCheckDispatch+0x69
fffff880`0378b980 fffff880`05f8a821 : fffffa80`061c17b0 fffff880`05f69468 00000000`00000054 fffff880`05f5e3a4 : nt!KiPageFault+0x260
fffff880`0378bb10 fffffa80`061c17b0 : fffff880`05f69468 00000000`00000054 fffff880`05f5e3a4 00000000`00000053 : ETD+0xf821
fffff880`0378bb18 fffff880`05f69468 : 00000000`00000054 fffff880`05f5e3a4 00000000`00000053 fffff880`05f5e16f : 0xfffffa80`061c17b0
fffff880`0378bb20 00000000`00000054 : fffff880`05f5e3a4 00000000`00000053 fffff880`05f5e16f 00000000`00000008 : i8042prt!ntoskrnl_NULL_THUNK_DATA+0x908
fffff880`0378bb28 fffff880`05f5e3a4 : 00000000`00000053 fffff880`05f5e16f 00000000`00000008 fffff880`0378bba0 : 0x54
fffff880`0378bb30 fffff880`0378bbd0 : fffffa80`0603db40 00000000`00000008 fffff880`03767f40 00000000`00000001 : i8042prt!WPP_RECORDER_SF_+0x94
fffff880`0378bb70 fffffa80`0603db40 : 00000000`00000008 fffff880`03767f40 00000000`00000001 00000000`00000000 : 0xfffff880`0378bbd0
fffff880`0378bb78 00000000`00000008 : fffff880`03767f40 00000000`00000001 00000000`00000000 fffffa80`0755dc28 : 0xfffffa80`0603db40
fffff880`0378bb80 fffff880`03767f40 : 00000000`00000001 00000000`00000000 fffffa80`0755dc28 fffffa80`061d4180 : 0x8
fffff880`0378bb88 00000000`00000001 : 00000000`00000000 fffffa80`0755dc28 fffffa80`061d4180 fffffa80`061d4030 : 0xfffff880`03767f40
fffff880`0378bb90 00000000`00000000 : fffffa80`0755dc28 fffffa80`061d4180 fffffa80`061d4030 fffff880`0378bcd8 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ETD+f821
fffff880`05f8a821 8a944bec000000  mov     dl,byte ptr [rbx+rcx*2+0ECh]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  ETD+f821

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ETD

IMAGE_NAME:  ETD.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdaa06d

FAILURE_BUCKET_ID:  X64_0xD1_ETD+f821

BUCKET_ID:  X64_0xD1_ETD+f821

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_etd+f821

FAILURE_ID_HASH:  {83a88fe7-f814-c652-89af-ce066c4331b3}

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

2: kd> lmvm ETD
start             end                 module name
fffff880`05f7b000 fffff880`05fa0000   ETD      T (no symbols)           
    Loaded symbol image file: ETD.sys
    Image path: ETD.sys
    Image name: ETD.sys
    Timestamp:        Fri Apr 30 14:48:37 2010 (4BDAA06D)
    CheckSum:         0002EACC
    ImageSize:        00025000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Thanks for helping me understand. I have very limited knowledge about all this stuff, but I like to try to learn more when I can.

I followed the instructions from the link you gave to disable driver verifier. A window popped up that said no settings were changed. Does that mean that is wasn't enabled after all? I forgot that the last step in the instructions I had found re: the driver verifier were to search for "verifier /reset" in the Start menu and then click on it. When I did that, was that the same as disabling it?

Arc said:

Driver verifier is a tool, a very sophisticated tool to monitor the drivers. To do it, it puts a high stress on the drivers which causes various sorts of system instability; and that is its pourpose. Even it may cause the system unbootable and beyond repair if adequate proper precaution is not taken before enabling it.

In short, it is not to use abruptly, and even it is used, you need at least a certain level of skill to decipher its message.

Thats all. It is your computer, you will decide whether you will keep verifier enabled or not. I can only suggest you to disable it. Because otherwise you may continue to enjoy stop 0x000000C4 BSOD (and I will not reply back for a further stop 0xC4).