TrueImage Home 2010 build 7060 problems with Windows 7/64 SP1

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Beiträge: 1
Kommentare: 1

HELP. Previous build True Image Home worked fine. Around the time Windows 7 SP1 installed, noticed loading any file took much longer, e.g. project that took <1min to load now took several minutes. Long load time problem went away after True Image uninstalled, reappeared loading latest build 7060.

Build 7060 blue screened when backup job started, analysis summary:

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: 00000000000002a8, Handle value being referenced.
Arg3: fffffa80052e4260, Address of the current process.
Arg4: fffff8800261dc29, Address inside the driver that is performing the incorrect reference.

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

BUGCHECK_STR: 0xc4_f6

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: TrueImageHomeS

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800033163dc to fffff80002e8f640

Mi, 04/13/2011 - 21:08
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Beiträge: 1
Kommentare: 1

Update:

- Part of problem is my doing. I had forgotten I had enabled the Microsoft driver verifier, which is the cause of the BSOD 0xc4. I didn't realize that the driver verifier functionality remains on until the user turns it off. This was the likely cause of my system slow down, very odd.

- BSOD does indicate some snap driver problem, Acronis support sent me a link to latest snapAPI. Combination of 7060 TIH, latest snapAPI, AND disabling the driver verifier feature, things working well so far.

Fr, 04/15/2011 - 15:34
  • Anmelden, um Kommentare verfassen zu können