SafeSpace Issue Question

I just installed Safespace to give it a try and it has the same problem that turned me off to Geswall, when you open my computer or windows explorer, it hangs for 7-8 seconds. Every folder page you go deeper in it's fine and backwards it's also fine. However, if you go down the folder tree than back out to the start, it hangs for the 7-8 seconds on the first page. Is there a way to fix this? I know it's Safespace that is causing it and I know Geswall did the same thing. Do you notice this behavior? It's annoying for someone who goes through their folders a lot. I would like to continue using this program but I can't if it hangs explorer like this.

 

I tried GeSWall before, and SafeSpace after, and I had the same problem with both (& I ended removing both)

SafeSpace gave me too BSOD with ProcessGuard's driver (or if one's prefers, PG's driver gave me BSOD with SafeSpace ):

Code:

Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Sun Apr 13 16:16:28.906 2008 (GMT+2)
System Uptime: 0 days 5:38:51.476
Loading Kernel Symbols
...........................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 8561f000, 8561f260, a4c0000}

Unable to load image procguard.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for procguard.sys
*** ERROR: Module load completed but symbols could not be loaded for procguard.sys
*** WARNING: Unable to verify timestamp for ASWave.sys
*** ERROR: Module load completed but symbols could not be loaded for ASWave.sys


Probably caused by : procguard.sys ( procguard+509 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 8561f000, The pool entry we were looking for within the page.
Arg3: 8561f260, The next pool entry.
Arg4: 0a4c0000, (reserved)

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




BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  8561f000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  SafeSpace_Agent

LAST_CONTROL_TRANSFER:  from 8054b941 to 8053354e

STACK_TEXT:  
b298a3cc 8054b941 00000019 00000020 8561f000 nt!KeBugCheckEx+0x1b
b298a41c 8054b2b9 8561f008 00000000 b298a460 nt!ExFreePoolWithTag+0x2be
b298a42c f7bce509 8561f008 02520046 024e010e nt!ExFreePool+0xf
WARNING: Stack unwind information not available. Following frames may be wrong.
b298a460 f7bce557 b298a484 b298a498 b298a49c procguard+0x509
b298a478 b2d4eef4 02500008 00110000 02510008 procguard+0x557
b298a4e0 b2d54d33 0000032c 024e00d8 00000036 ASWave+0x2def4
b298a540 b2d54d0a 0000032c 00000001 00000001 ASWave+0x33d33
b298a5a0 b2d54d0a 00000328 00000001 00000001 ASWave+0x33d0a
b298a600 b2d54d0a 00000324 00000001 00000001 ASWave+0x33d0a
b298a660 b2d54d0a 000002e4 00000001 00000001 ASWave+0x33d0a
b298a6c0 b2d54d0a 00000130 00000001 00000001 ASWave+0x33d0a
b298a720 b2d54d0a 000002d4 00000001 00000001 ASWave+0x33d0a
b298a780 b2d54d0a 00000308 00000001 00000001 ASWave+0x33d0a
b298a7e0 b2d54d0a 00000320 00000001 00000001 ASWave+0x33d0a
b298a840 b2d54d0a 00000148 00000001 00000001 ASWave+0x33d0a
b298a8a0 b2d54d0a 00000144 00000001 00000001 ASWave+0x33d0a
b298a900 b2d54d0a 000002fc 00000001 00000001 ASWave+0x33d0a
b298a960 b2d54d0a 000002a8 00000001 00000001 ASWave+0x33d0a
b298a9c0 b2d54d0a 00000268 00000001 00000001 ASWave+0x33d0a
b298aa20 b2d54d0a 000002a4 00000001 00000001 ASWave+0x33d0a
b298aa80 b2d36ad0 0000028c 00000001 00000001 ASWave+0x33d0a
b298aab8 b2d365a0 e1a66458 e23ae898 804dc2b2 ASWave+0x15ad0
b298ab08 b2d34a10 e23ae898 86eaf808 00000000 ASWave+0x155a0
b298ab24 b2d22683 872d1960 86f28a90 86c5c498 ASWave+0x13a10
b298ab4c b2d28a15 86dad3e0 872d1960 00000018 ASWave+0x1683
b298ab80 b2d22228 86dad3e0 872d1960 00000018 ASWave+0x7a15
b298abd4 804e37f7 86eb1170 86f28a50 806ef2d0 ASWave+0x1228
b298abe4 8056a148 86f28ac0 86dad3e0 86f28a50 nt!IopfCallDriver+0x31
b298abf8 8057ad03 86eb1170 86f28a50 86dad3e0 nt!IopSynchronousServiceTail+0x60
b298aca0 8057d281 000001d4 00000000 00000000 nt!IopXxxControlFile+0x611
b298acd4 b2d46e6e 000001d4 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
b298ad34 804de7ec 000001d4 00000000 00000000 ASWave+0x25e6e
b298ad34 7c91eb94 000001d4 00000000 00000000 nt!KiFastCallEntry+0xf8
0012f3b8 00000000 00000000 00000000 00000000 0x7c91eb94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
procguard+509
f7bce509 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  procguard+509

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: procguard

IMAGE_NAME:  procguard.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  44d98742

FAILURE_BUCKET_ID:  0x19_20_procguard+509

BUCKET_ID:  0x19_20_procguard+509

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

Probably caused by : procguard.sys ( procguard+509 )

PROCESS_NAME: SafeSpace_Agent

 

Any way to stop this?