BugCheck C4, {f6, d4, fffffa8005c33060, fffff88002dd1ca2}
Unable to load image \SystemRoot\system32\DRIVERS\[COLOR=#ff0000][U][B]SynTP.sys[/B][/U][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]SynTP.sys[/B][/U][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]SynTP.sys[/B][/U][/COLOR]
Probably caused by : [U][B][COLOR=#ff0000]SynTP.sys[/COLOR][/B][/U] ( SynTP+1aca2 )
Followup: MachineOwner
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: 00000000000000d4, Handle value being referenced.
Arg3: fffffa8005c33060, Address of the current process.
Arg4: fffff88002dd1ca2, Address inside the driver that is performing the incorrect reference.
BUGCHECK_STR: 0xc4_f6
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: [COLOR=#ff0000][U][B]SynTPEnh.exe[/B][/U][/COLOR]
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002d5a3dc to fffff800028d0c40
STACK_TEXT:
fffff880`061a22c8 fffff800`02d5a3dc : 00000000`000000c4 00000000`000000f6 00000000`000000d4 fffffa80`05c33060 : nt!KeBugCheckEx
fffff880`061a22d0 fffff800`02d6fae4 : 00000000`000000d4 fffffa80`05c33060 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`061a2310 fffff800`02b28210 : fffff800`02bc6f90 fffff880`061a2540 fffffa80`02384500 fffff880`02df5700 : nt!VfCheckUserHandle+0x1b4
fffff880`061a23f0 fffff800`02bab375 : 00000000`00000000 fffffa80`10000000 fffffa80`02384570 fffff800`02bab300 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`061a24c0 fffff800`02d6f878 : 00000000`00000003 fffff880`02df57f0 fffff980`1130efc8 fffff880`02dd1e48 : nt!ObReferenceObjectByHandle+0x25
fffff880`061a2510 fffff880`02dd1ca2 : fffff980`1130efc8 00000000`20040000 fffff880`02df57f0 fffff880`02ddadde : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`061a2560 fffff980`1130efc8 : 00000000`20040000 fffff880`02df57f0 fffff880`02ddadde fffff980`1130efd0 : [COLOR=#ff0000][U][B]SynTP[/B][/U][/COLOR]+0x1aca2
fffff880`061a2568 00000000`20040000 : fffff880`02df57f0 fffff880`02ddadde fffff980`1130efd0 00000000`00000000 : 0xfffff980`1130efc8
fffff880`061a2570 fffff880`02df57f0 : fffff880`02ddadde fffff980`1130efd0 00000000`00000000 fffff880`061a2660 : 0x20040000
fffff880`061a2578 fffff880`02ddadde : fffff980`1130efd0 00000000`00000000 fffff880`061a2660 fffff880`02ddb33a : [U][B][COLOR=#ff0000]SynTP[/COLOR][/B][/U]+0x3e7f0
fffff880`061a2580 fffff980`1130efd0 : 00000000`00000000 fffff880`061a2660 fffff880`02ddb33a fffff880`061a2660 : [U][B][COLOR=#ff0000]SynTP[/COLOR][/B][/U]+0x23dde
fffff880`061a2588 00000000`00000000 : fffff880`061a2660 fffff880`02ddb33a fffff880`061a2660 fffff880`02df46b8 : 0xfffff980`1130efd0
STACK_COMMAND: kb
FOLLOWUP_IP:
SynTP+1aca2
fffff880`02dd1ca2 b90b0004e0 mov ecx,0E004000Bh
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: [U][B][COLOR=#ff0000]SynTP[/COLOR][/B][/U]+1aca2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: [U][B][COLOR=#ff0000]SynTP[/COLOR][/B][/U]
IMAGE_NAME: [U][B][COLOR=#ff0000]SynTP.sys[/COLOR][/B][/U]
DEBUG_FLR_IMAGE_TIMESTAMP: 48a4e3e0
FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_[U][B][COLOR=#ff0000]SynTP[/COLOR][/B][/U]+1aca2
BUCKET_ID: X64_0xc4_f6_VRF_[COLOR=#ff0000][U][B]SynTP[/B][/U][/COLOR]+1aca2
Followup: MachineOwner
I'd never run DriverVerifier (that's a lie, I would!) unless instructed. You've got it right. It stresses things out.The verifier is actually the driver verifier that I found mentioned several times on this windows7Forums site.I believe what it does is puts extra stress on components which if there is a faulty driver, will cause them to fail and result in a BSoD. Is this correct?
No two pc's are the same....I ran it on my laptop (not the laptop that is crashing) and haven't had a single issue since last night leading me to believe that if a computer doesn't have a faulty driver, it can run the driver verifier without issue.
No two pc's are the same....
Drew is right about AVG, from my canned BSOD speech:
AVG is known to be a cause of BSOD's on Windows 7 systems. Suggest that you uninstall it. Download the correct AVG Remover for your system (32 or 64 bit).
If you have AVG ID protection installed, download the AVGID Protection Remover from the above link as well (it wouldn't hurt to download and run it anyway). Download BSOD friendly Link Removed due to 404 Error as AVG's replacement.
Uninstall AVG through the Control Panel. Re-boot to Safe Mode and run the AVG Removal tool(s). Re-boot to normal mode and install MSE. Make sure your Windows firewall is enabled! After your blue screens have been resolved, feel free to re-try AVG.
I looked at the website, but isn't this more for HP-type of Windows installs where you get a lot of bloatware? The version I am using is a clean version, no bloatware. I will give it a try though.I'd also run Link Removed - Invalid URL to remove, well, the crap that OEM's insist on installing for your "benefit" (not).