KernSafe Technology

1) Problems doing install/install on XP SP3. A 50K Driverinstall.exe.mdmp is available, but the forum won't allow me to attach it to this post. Processing it with Visual Studio Debugger reports "Stack overflow in DriverInstall.exe"

The application log contains many entries from both installing and uninstalling TM, all the same:

Faulting application DriverInstall.exe, version 1.2.5.901, faulting module DriverInstall.exe, version 1.2.5.901, fault address 0x000013e5.



2) Drivers appeared to be correctly installed, but they seem to conflict with XP entering suspend mode. A hang occurs with a blank screen or one that says "preparing to ... suspend". I must Power off, then reboot. I've been unable to capture a dump.



3) During startup, the following is in the system log: event 9 for KScsiPrt:

\Device\Scsi\KScsiPrt1

0000: 0f 00 10 00 01 00 6a 00 ......j.
0008: 00 00 00 00 09 00 04 c0 .......À
0010: 01 01 00 50 00 00 00 00 ...P....

Same thing happened to me. The system crashes while going on to sleep mode.

=========================================================
Dump analysis using Windbg
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800772a050, Physical Device Object of the stack
Arg3: fffff80000b9c4d8, Functional Device Object of the stack
Arg4: fffffa8009fd8c10, The blocked IRP

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

Unable to load image \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
*** WARNING: Unable to verify timestamp for KSPrt64.sys
*** ERROR: Module load completed but symbols could not be loaded for KSPrt64.sys

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: KSPrt64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e56d23b

MODULE_NAME: KSPrt64

FAULTING_MODULE: fffff88001046000 KSPrt64

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`00b9c488 fffff800`02b00b52 : 00000000`0000009f 00000000`00000003 fffffa80`0772a050 fffff800`00b9c4d8 : nt!KeBugCheckEx
fffff800`00b9c490 fffff800`02aa0062 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c530 fffff800`02a9ff06 : fffffa80`0a0856a0 fffffa80`0a0856a0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5a0 fffff800`02a9fdee : 00000048`3afbb544 fffff800`00b9cc18 00000000`001e580f fffff800`02c09468 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cbf0 fffff800`02a9fbd7 : 00000009`da2bbbc2 00000009`001e580f 00000009`da2bbbe9 00000000`0000000f : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`02a8c36a : fffff800`02c06e80 fffff800`02c14cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_cdrom_IMAGE_KSPrt64.sys

BUCKET_ID: X64_0x9F_3_cdrom_IMAGE_KSPrt64.sys

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

Thank you for your feedbacks, we can reproduce the problem in some environment, then we will resolve the problem and make an upgraded version recently.