ok i have the same problem with TiWorker.exe taking to much cpu power , so what if i do not want it compressing like you say it is doing? how do i kill it? because as it stands i get more and more bsods being caused by TiWorker.exe, i get about 3 or 4 bsods a day and when i look in the dump files it always shows up as TiWorker.exe caused the error. so i ask again, how do i kill it and keep it off?and heres a small example,

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\081513-35069-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
Machine Name:
Kernel base = 0xfffff803`6d86e000 PsLoadedModuleList = 0xfffff803`6db3aa20
Debug session time: Thu Aug 15 11:16:03.385 2013 (UTC - 4:00)
System Uptime: 0 days 0:07:07.129
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8036dcd67d7, fffff8801183e910, 0}

Probably caused by : ntkrnlmp.exe ( nt!CmpGetNameControlBlock+13f )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8036dcd67d7, Address of the instruction which caused the bugcheck
Arg3: fffff8801183e910, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!CmpGetNameControlBlock+13f
fffff803`6dcd67d7 3b3e            cmp     edi,dword ptr [rsi]

CONTEXT:  fffff8801183e910 -- (.cxr 0xfffff8801183e910)
rax=0000000000004260 rbx=0000000000000000 rcx=fffff8a00001b260
rdx=000000000000004a rsi=0000000000000003 rdi=0000000092892b5d
rip=fffff8036dcd67d7 rsp=fffff8801183f310 rbp=fffff8801183f3b8
 r8=0000000000000488  r9=fffff8a00cfb3de4 r10=fffff8a00cfb3de4
r11=0000000000000000 r12=000000009c90fc58 r13=fffffffffffffffb
r14=fffff8a000017000 r15=fffff98000020601
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!CmpGetNameControlBlock+0x13f:
fffff803`6dcd67d7 3b3e            cmp     edi,dword ptr [rsi] ds:002b:00000000`00000003=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  TiWorker.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8036dcd67d7

STACK_TEXT:  
fffff880`1183f310 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpGetNameControlBlock+0x13f


FOLLOWUP_IP:
nt!CmpGetNameControlBlock+13f
fffff803`6dcd67d7 3b3e            cmp     edi,dword ptr [rsi]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpGetNameControlBlock+13f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5165e551

STACK_COMMAND:  .cxr 0xfffff8801183e910 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpGetNameControlBlock+13f

BUCKET_ID:  X64_0x3B_nt!CmpGetNameControlBlock+13f

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

this is the 3rd install of windows 8 pro that has had the same issues with it.