Its bad and annoying. You said you will reply back in your thread, but you did not do that, and started another thread.
It not only gives a bad impression but also a contravention to the basic guideline of the BSOD forum.
Before posting a BSOD thread, please read the instructions here:
Blue Screen of Death (BSOD) Posting Instructions
If you need to add new information like the dump files, please make a new post in your initial BSOD thread.
Please do not make an extra new thread.
Please do not post anything other than Windows 7 Blue Screen Of Death problems in this section.
This time we are merging this post with your earlier thread, but if this attitude continues then you will not get a reply.
Anyway, for your issue, update the touchpad driver (Synaptics). The one that you have installed there is not compatible with windows 7. I wonder how you got it installed. Here is the easiest way to get the driver.
___________________________________________________________
Code:
BugCheck C4, {f6, d0, fffffa800755eb30, fffff88003d213b9}
*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
Probably caused by : SynTP.sys ( SynTP+123b9 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000d0, Handle value being referenced.
Arg3: fffffa800755eb30, Address of the current process.
Arg4: fffff88003d213b9, Address inside the driver that is performing the incorrect reference.
Debugging Details:
------------------
BUGCHECK_STR: 0xc4_f6
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: SynTPEnh.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff80002f1c4ec to fffff80002a89a40
STACK_TEXT:
fffff880`028ed1b8 fffff800`02f1c4ec : 00000000`000000c4 00000000`000000f6 00000000`000000d0 fffffa80`0755eb30 : nt!KeBugCheckEx
fffff880`028ed1c0 fffff800`02f31aa4 : 00000000`000000d0 fffffa80`0755eb30 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`028ed200 fffff800`02ce4950 : fffff800`02d7ecf0 fffff880`028ed430 fffffa80`03d03a00 00000000`20040000 : nt!VfCheckUserHandle+0x1b4
fffff880`028ed2e0 fffff800`02d629f5 : 00000000`00000000 fffffa80`10000000 fffffa80`03d03a40 fffff800`02d62900 : nt! ?? ::NNGAKEGL::`string'+0x1a10e
fffff880`028ed3b0 fffff800`02f31838 : 00000000`00000000 fffff800`02f2a6bb fffff880`03d5a7c0 fffff800`02f2937c : nt!ObReferenceObjectByHandle+0x25
fffff880`028ed400 fffff880`03d213b9 : fffff980`0cab2fc8 00000000`20040000 00000000`20040000 00000000`00000003 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`028ed450 fffff980`0cab2fc8 : 00000000`20040000 00000000`20040000 00000000`00000003 fffff980`0cab2fd0 : SynTP+0x123b9
fffff880`028ed458 00000000`20040000 : 00000000`20040000 00000000`00000003 fffff980`0cab2fd0 00000000`00000000 : 0xfffff980`0cab2fc8
fffff880`028ed460 00000000`20040000 : 00000000`00000003 fffff980`0cab2fd0 00000000`00000000 fffff880`028ed580 : 0x20040000
fffff880`028ed468 00000000`00000003 : fffff980`0cab2fd0 00000000`00000000 fffff880`028ed580 fffff880`03d39899 : 0x20040000
fffff880`028ed470 fffff980`0cab2fd0 : 00000000`00000000 fffff880`028ed580 fffff880`03d39899 fffff880`028ed580 : 0x3
fffff880`028ed478 00000000`00000000 : fffff880`028ed580 fffff880`03d39899 fffff880`028ed580 00000000`20040000 : 0xfffff980`0cab2fd0
STACK_COMMAND: kb
FOLLOWUP_IP:
SynTP+123b9
fffff880`03d213b9 b90b0004e0 mov ecx,0E004000Bh
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: SynTP+123b9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SynTP
IMAGE_NAME: SynTP.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47ec46b4
FAILURE_BUCKET_ID: X64_0xc4_f6_SynTP+123b9
BUCKET_ID: X64_0xc4_f6_SynTP+123b9
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xc4_f6_syntp+123b9
FAILURE_ID_HASH: {a1c75ec5-9c55-6a89-f49f-f12d7ae47561}
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000d0, Handle value being referenced.
Arg3: fffffa800755eb30, Address of the current process.
Arg4: fffff88003d213b9, Address inside the driver that is performing the incorrect reference.
Debugging Details:
------------------
BUGCHECK_STR: 0xc4_f6
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: SynTPEnh.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff80002f1c4ec to fffff80002a89a40
STACK_TEXT:
fffff880`028ed1b8 fffff800`02f1c4ec : 00000000`000000c4 00000000`000000f6 00000000`000000d0 fffffa80`0755eb30 : nt!KeBugCheckEx
fffff880`028ed1c0 fffff800`02f31aa4 : 00000000`000000d0 fffffa80`0755eb30 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`028ed200 fffff800`02ce4950 : fffff800`02d7ecf0 fffff880`028ed430 fffffa80`03d03a00 00000000`20040000 : nt!VfCheckUserHandle+0x1b4
fffff880`028ed2e0 fffff800`02d629f5 : 00000000`00000000 fffffa80`10000000 fffffa80`03d03a40 fffff800`02d62900 : nt! ?? ::NNGAKEGL::`string'+0x1a10e
fffff880`028ed3b0 fffff800`02f31838 : 00000000`00000000 fffff800`02f2a6bb fffff880`03d5a7c0 fffff800`02f2937c : nt!ObReferenceObjectByHandle+0x25
fffff880`028ed400 fffff880`03d213b9 : fffff980`0cab2fc8 00000000`20040000 00000000`20040000 00000000`00000003 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`028ed450 fffff980`0cab2fc8 : 00000000`20040000 00000000`20040000 00000000`00000003 fffff980`0cab2fd0 : SynTP+0x123b9
fffff880`028ed458 00000000`20040000 : 00000000`20040000 00000000`00000003 fffff980`0cab2fd0 00000000`00000000 : 0xfffff980`0cab2fc8
fffff880`028ed460 00000000`20040000 : 00000000`00000003 fffff980`0cab2fd0 00000000`00000000 fffff880`028ed580 : 0x20040000
fffff880`028ed468 00000000`00000003 : fffff980`0cab2fd0 00000000`00000000 fffff880`028ed580 fffff880`03d39899 : 0x20040000
fffff880`028ed470 fffff980`0cab2fd0 : 00000000`00000000 fffff880`028ed580 fffff880`03d39899 fffff880`028ed580 : 0x3
fffff880`028ed478 00000000`00000000 : fffff880`028ed580 fffff880`03d39899 fffff880`028ed580 00000000`20040000 : 0xfffff980`0cab2fd0
STACK_COMMAND: kb
FOLLOWUP_IP:
SynTP+123b9
fffff880`03d213b9 b90b0004e0 mov ecx,0E004000Bh
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: SynTP+123b9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SynTP
IMAGE_NAME: SynTP.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47ec46b4
FAILURE_BUCKET_ID: X64_0xc4_f6_SynTP+123b9
BUCKET_ID: X64_0xc4_f6_SynTP+123b9
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xc4_f6_syntp+123b9
FAILURE_ID_HASH: {a1c75ec5-9c55-6a89-f49f-f12d7ae47561}
Followup: MachineOwner
---------
1: kd> lmvm SynTP
start end module name
fffff880`03d0f000 fffff880`03d65000 SynTP T (no symbols)
Loaded symbol image file: SynTP.sys
Image path: SynTP.sys
Image name: SynTP.sys
Timestamp: Fri Mar 28 06:45:32 2008 (47EC46B4)
CheckSum: 00058FCC
ImageSize: 00056000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4