MZ@ !L!This program cannot be run in DOS mode. $T>Cw_-$_-$_-$}.%_-$},%_-$_,$_-$})%_-$}-%_-$}%%3_-$}$_-$}/%_-$Rich_-$PELW! `  I@ABX(6-\*Z8 P.text2 `.dataX@.idata@@.rsrc@@.reloc\*, @BThreadD@) 0U@UQQQQQR0RLR`R|RRRRRRS,SHS`S|SSSSSTT0THT`TtTTTTTUUU X XXXX XX@ZPi5f g0hiim`op @@ `p`PP PP@@0`P,p67Zosu xypz0PpP` 0P@@PйP`@P`p@`@Pppp0pP@ `  `0@P @    PP0p`0P   !!0""#`## $$$@%%&`&P'' (p(( )))P**+p++0,, -- ...P//0`001122`34`440555P66 777@8`999;0; <`<P==p>>>?@??0@@A@BBCPDDE FF@GG`HHI`IIPJJKPKKL MpMNO QQR0RUVpVVPWWXpYYZ0[[]^`b`ccpde0eef`ffgphiijPkkPllPmmPnn@oo@pqqrs@tt@uu wpxxy{{`||}}}`~~p ``@*FaultInjectionIncludeDllsFaultInjectionExcludeDllsFaultInjectionTimeOutFaultInjectionProbabilityAVRF: fault injecting call made from %p AVRF:FINJ: invalid fault injection class %X Not used.Current thread using the heapLast thread that used the heapHeap handlemultithreaded access in HEAP_NO_SERIALIZE heapheap handle with incorrect signature\KernelObjects\HighCommitConditionPage heap: pid 0x%X: page heap enabled with flags 0x%X. Process heap handleattempt to destroy process heapSize requestedextreme size requestAddressHeapRootPage heap: freeing a null pointerPage heap countActual countprocess heap list count is wrongCorruption AddressBlock sizeHeap blockcorrupted headerblock already freedcorruption addresscorrupted infix pattern for freed blockHeap owning the blockHeap used in the callcorrupted heap pointer or using wrong heapcorrupted suffix patterncorrupted prefix patternCorrupted stampcorrupted start stampcorrupted end stampException codeexception raised while verifying blockcorrupted heap blockheap signatureheap blockvirtual storage list entrylist headlist countAVRF: Reached the end of heap list without finding heap index %x. Total number of heaps %x heap list entryAVRF: EntryContents.Blink = %p, expected %p VerifierRegisterLayerAVRF: Spy [%s, %u]: %X VerifierRegisterBasicsLayersVerifierUnregisterLayerVerifierUnregisterBasicsLayersThis verifier stop is continuable. After debugging it use `go' to continue.This verifier stop is not continuable. Process will be terminated when you use the `go' debugger command. =========================================================== VERIFIER STOP %p: pid 0x%X: %s %p : %s %p : %s %p : %s %p : %s =========================================================== %s =========================================================== AVRF: Noncontinuable verifier stop %Ix encountered. Terminating process ... AVRF: Terminate process after verifier stop failed with %X AVRF: Invalid LayerDescriptor or BreakDecriptor passed for Stop code 0x%XAVRF: Invalid Stop code 0x%X passed to VerifierStopMessageExAVRF: Failed to initialize logging and stop support%s AVRF:bogus string length, overflow AVRF:Failed to save message into stop list StopProcessingstop codeadvapi32.dllRegCreateKeyExWRegCloseKeyRegQueryValueExWRegSetValueExWRegDeleteValueWSOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\GlobalFlagAVRF: settings: result %u %x0x%08XVerifierFlags{9760941A-8DA5-4dbe-843B-0EBD376CAB02}HandlesBasics{159D60EC-F459-456b-A27B-1076AD59F8F4}Locks{EDDA96DB-D216-467d-BE3C-8603745EDA43}TLS{8A70B8A4-4FA6-41c3-85EE-595FCB3E1051}Memory{F86B022F-E589-4e8f-B0DD-6B7AF9D71A59}Exceptions{970bd287-2e5a-4a06-9084-9e394d4c2697}DirtyStacksMiscellaneous{02A5B40C-2F22-4409-BB37-7EF0D3F34A88}DangerousAPIs{de35a0c0-d3b8-11d9-8cd5-0800200c9a66}TimeRollOver{F15FC24E-53A0-444D-8D28-F7697EDD9C83}Threadpool{5FE32372-CE71-43f9-B75D-6AD4B1B08D6A}InputOutput{81EEC8DA-0E61-4942-8037-9A6C4A86510D}Leak{6335D1CF-7955-414e-8C6A-1A40AC9357AC}SRWLockntdll.dllLdrGetProcedureAddressForCallerAVRF: AVrfpLdrGetProcedureAddress (%p, %s) -> new address %p PageHeapSizeRangeStartPageHeapSizeRangeEndPageHeapRandomProbabilityPageHeapDllRangeStartPageHeapDllRangeEndPageHeapTargetDllsPageHeapVirtualMemoryPercentPageHeapCommitMemoryPercentThreadTrackerSizeHeapTrackerSizeVspaceTrackerSizeDllLoadUnloadTrackerSizeCritsectDeleteTrackerSizeOutbuffTrackerSizeThreadpoolTrackerSizeForcePendingIOTrackerSizeEventTrackerSizeDelayFreeSizeMBAVRF: failed to initialize call trackers (%X). AVRF: failed to initialize FreeMemoryCallBacks (%X). AVRF: VerifierRegisterBasicsLayers failed. AVRF: VerifierLoadEssentialStrings failed, status %#x AVRF: NtQuerySystemInformation (SystemBasicInformation) failed, status %#x OANOCACHE1AVRF: failed to define OANOCACHE variable (%X). AVRF: Failed to initialize verifier.dll provider for %ws with flags 0x%X. AVRF: verifier.dll provider initialized for %ws with flags 0x%X AVRF: Exception during verifier.dll init for %ws with flags 0x%X. ntdll.dllNtSuspendProcessNtResumeProcessAVRF: failed to create verifier heap. AVRF: failed to initialize verifier stop logic (%X). RtlReportExceptionAVRF: Exception %x from address %p Dirtying stack range %p - %p for thread %p AVRF: failed to allocated a verifier TLS slot. Context record. Use .cxr to display it.Exception record. Use .exr to display it.Code performing invalid accessInvalid address being accessedfirst chance access violation for current stack traceAVRF: failed to add free memory callback @ %p AVRF: attempt to delete invalid free memory callback @ %p Stack low limit addressDLL name address. Use du to dump it.DLL memory range sizeDLL memory base addressUnloading DLL inside current thread's stack address rangeAVRF: Couldn't read %s @ %p AVRF: Read just %Ix out of %Ix bytes of %s @ %p RtlInitializeSRWLockRtlReleaseSRWLockExclusiveRtlReleaseSRWLockSharedRtlAcquireSRWLockExclusiveRtlAcquireSRWLockSharedRtlCreateMemoryBlockLookasideRtlExtendMemoryBlockLookasideRtlAllocateMemoryBlockLookasideRtlFreeMemoryBlockLookasideNtAllocateVirtualMemoryNtFreeVirtualMemoryNtMapViewOfSectionNtUnmapViewOfSectionNtUnmapViewOfSectionExNtCreateSectionNtOpenSectionNtCreateFileNtOpenFileNtCreateKeyNtOpenKeyRtlTryEnterCriticalSectionRtlEnterCriticalSectionRtlLeaveCriticalSectionRtlInitializeCriticalSectionRtlInitializeCriticalSectionAndSpinCountRtlDeleteCriticalSectionRtlInitializeResourceRtlDeleteResourceRtlAcquireResourceSharedRtlAcquireResourceExclusiveRtlReleaseResourceRtlConvertSharedToExclusiveRtlConvertExclusiveToSharedNtCreateEventNtOpenEventNtCloseRtlAllocateHeapRtlReAllocateHeapRtlFreeHeapNtReadFileNtReadFileScatterNtWriteFileNtWriteFileGatherNtWaitForSingleObjectNtWaitForMultipleObjectsRtlSetThreadPoolStartFuncNtSetEventNtClearEventNtPulseEventNtQueryEventNtResetEventNtSetEventBoostPriorityNtAlertResumeThreadNtAlertThreadNtGetContextThreadNtImpersonateThreadNtQueryInformationThreadNtQueueApcThreadNtResumeThreadNtSetContextThreadNtSetInformationThreadNtSuspendThreadNtTerminateThreadNtGetNextThreadNtQueryInformationProcessNtSetInformationProcessNtTerminateProcessNtGetNextProcessNtAllocateUserPhysicalPagesNtExtendSectionNtReadVirtualMemoryNtWriteVirtualMemoryNtFlushVirtualMemoryNtLockVirtualMemoryNtUnlockVirtualMemoryNtProtectVirtualMemoryNtQuerySectionNtFreeUserPhysicalPagesNtGetWriteWatchNtResetWriteWatchNtFlushInstructionCacheNtDeleteKeyNtDeleteValueKeyNtEnumerateKeyNtEnumerateValueKeyNtFlushKeyNtNotifyChangeKeyNtNotifyChangeMultipleKeysNtQueryKeyNtQueryValueKeyNtQueryMultipleValueKeyNtReplaceKeyNtRenameKeyNtCompactKeysNtCompressKeyNtRestoreKeyNtSaveKeyNtSaveKeyExNtSaveMergedKeysNtSetValueKeyNtUnloadKeyExNtSetInformationKeyNtLockRegistryKey_vsnprintf_vsnwprintf_snprintf_snwprintfLdrLoadDllLdrUnloadDllRtlInitializeCriticalSectionExTpAllocWorkTpAllocTimerTpAllocWaitTpAllocIoCompletionTpReleaseIoCompletionTpAllocAlpcCompletionTpSimpleTryPostTpCallbackLeaveCriticalSectionOnCompletionTpCallbackDetectedUnrecoverableErrorRtlQueueWorkItemRtlCreateHeapRtlRegisterWaitRtlDeregisterWaitExRtlDeregisterWaitRtlCreateTimerQueueRtlDeleteTimerQueueExRtlDeleteTimerQueueRtlCreateTimerRtlDeleteTimerRtlUpdateTimerRtlCancelTimerRtlSetTimerNtDeviceIoControlFileNtFsControlFileNtRemoveIoCompletionNtRemoveIoCompletionExRtlExitUserThreadRtlSetIoCompletionCallbackNtSetInformationFileNtCancelIoFileNtCancelIoFileExRtlDeleteSecurityObjectRtlDestroyHeapNtNotifyChangeDirectoryFileNtDuplicateObjectRtlTryAcquireSRWLockExclusiveRtlAcquireReleaseSRWLockExclusiveRtlTryAcquireSRWLockSharedRtlSleepConditionVariableSRWRtlFreeUnicodeStringRtlFreeSidRtlExitUserProcessRtlSetSecurityObjectRtlSetSecurityObjectExLdrGetProcedureAddressHeapCreateHeapDestroyCloseHandleExitThreadTerminateThreadSuspendThreadTlsAllocTlsFreeTlsGetValueTlsSetValueCreateThreadWaitForSingleObjectWaitForMultipleObjectsWaitForSingleObjectExWaitForMultipleObjectsExGlobalAllocGlobalReAllocLocalAllocLocalReAllocCreateFileACreateFileWFreeLibraryAndExitThreadGetTickCountIsBadReadPtrIsBadHugeReadPtrIsBadWritePtrIsBadHugeWritePtrIsBadCodePtrIsBadStringPtrAIsBadStringPtrWVirtualFreeVirtualFreeExCreateEventACreateEventWOpenEventAOpenEventWMultiByteToWideCharWideCharToMultiByteUnmapViewOfFileUnmapViewOfFileExSetThreadAffinityMaskSetThreadPriorityGlobalFreeLocalFreeVirtualAllocHeapAllocHeapReAllocHeapFreeSetProcessWorkingSetSizeExSetProcessWorkingSetSizeRegCreateKeyARegCreateKeyWRegCreateKeyExARegOpenKeyARegOpenKeyWRegOpenKeyExARegOpenKeyExWRegNotifyChangeKeyValueRegSetValueARegSetValueWRegSetValueExAmalloccallocreallocfree??2@YAPAXI@Z??3@YAXPAX@Z??_U@YAPAXI@Z??_V@YAXPAX@Z_strdup_wcsdup_mbsdupCoInitializeCoInitializeExCoUninitializeRoInitializeRoUninitializeCoTaskMemAllocCoTaskMemReallocCoTaskMemFreePostThreadMessageWPostThreadMessageAPostMessageWPostMessageAPostQuitMessageRegisterPowerSettingNotificationUnregisterPowerSettingNotificationSetClipboardDataSysAllocStringSysReAllocStringSysAllocStringLenSysReAllocStringLenSysAllocStringByteLenSysFreeStringVariantClearSetupDiCreateDevRegKeyASetupDiCreateDevRegKeyWSetupDiOpenDevRegKeykernel32.dllmsvcrt.dllole32.dlluser32.dllsetupapi.dlloleaut32.dllkernelbase.dllcombase.dllAVRF: internal error: we do not have a replacement for %s !!! vfbasics.dllAVRF: %ws: null entry point. AVRF: %ws @ %p: entry point @ %p . mfplat.dllnsi.dllthreadpoolwinrt.dllrtworkq.dllAVRF: low memory: will not verify entry point for %ws . AVRF: hooked dll entry point for dll %ws AVRF: dll entry @ %p (%ws, %x) AVRF: failed to get dll base of user32.dll. AVRF: TLS slot %x allocated by code at %p. AVRF: AVrfpLdrLoadDll (%p, %ws) AVRF: AVrfpLdrUnLoadDll (%p) winlogon.exesppsvc.exeOESpamFilter.dllMSWSOCK.DLLgdiplus.dllTTTraceWriter.dlllicwmi.dlldpcdll.dlllicdll.dllSbscrdll.dllUSER32.DLLDNSAPI.DLLmswsock.dllSPOOLSS.DLLlocalspl.dllNETAPI32.DLLnetlogon.dllasfsipc.dllframedyn.dlliac25_32.axrpcss.dllODBC32.dllcatsrv.dllGDI32.DLLiuengine.dllUxTheme.dllWINHTTP.DLLCritical section debug info addressLock countCritical section addresscritical section over-released or corruptedNumber of critical sections owned by current thread. %p (CS = %p, DebugInfo = %p), left %p, right %p, parent %p ================================================ Critical section tree root = %p ================================================ AVrfpInsertCritSectInSplayTree( %p ) AVrfpFindCritSectInSplayTree( %p ) AVrfpDeleteCritSectFromSplayTree( %p ) AVrfpInitializeCriticalSectionCommon (%p, %x, %x)) AVRF: InitializeCriticalSection (%p) - no tree node. AVRF: InitializeCriticalSection (%p) - out of memory - DebugInfo is not valid. AVrfpRtlDeleteCriticalSection (%p) AVrfpRtlInitializeResource (%p), CS = %p AVrfpRtlDeleteResource (%p), CS = %p Number of critical sections owned by curent thread.current thread doesn't own locksAVRF: AVrfpCheckStaticInitializedCriticalSection (%p) - no tree node. AVRF: checking CS @ %p (debug info @ %p) **************************************************************************** ** ** ** Potential deadlock detected! ** ** Type !avrf -dlck in the debugger for more information. ** Deadlock detection: Must release resources in reverse-order Resource %p acquired before resource %p -- Current thread (%p) is trying to release it first AVRF: Overflow for BytesAllocated (%p) + Size(%p) AVRF: deadlock: stop: %p %p %p %p Application verifier deadlock/resource issueEnumThreadWindowsRealGetWindowClassWPeekMessageWwudfhost.exeUNKNOWNadsldp.dlladsldpc.dlldetours.dlldeviceaccess.dlldhcpcore.dlldhcpcore6.dlldiagperf.dllesent.dllfirewall.cplfirewallapi.dllfxsst.dllieframe.dlliessetup.dlljscript.dlllogger.ocxmpssvc.dllmscories.dllmsfeeds.dllPerftrack.dllpwrshsip.dllradardt.dllrometadata.dllShimEng.dlltaskschd.dlltrkwks.dllUNTFS.dllUrlmon.dllVSSAPI.DLLwab32.dllwbemcons.dllwebclnt.dllwercplsupport.dllwinspool.drvwintypes.dllWLDAP32.dllwmp.dll,(null)\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\\REGISTRY\USER\\Registry\Machine\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\VerifierAppLaunchCountPageHeapFlagsAVRF: %ws Failed to close event 0x%p with Status 0x%X AVRF: %ws Failed to close handle 0x%p with Status 0x%X AVRF: %ws Failed to close event 0x%p with Status 0x%X in event completion callback AVRF: %ws Failed to clear event 0x%p with Status 0x%X AVRF: %ws Failed to create event with Status 0x%X AVRF: %ws Failed to register wait callback with Status 0x%X AVRF: conditional breakpoint %X hit. EventThreadProcessSectionKeyFileEventOrProcessAVrfpFreeVirtualMemNotify: NtQueryVirtualMemory( %p ) failed %x Buffer sizeBuffer start addressUnexpected exception raised while initializing output buffer.AVRF: (%x, %x) AVrfpInitOutputBuffer filling Buffer 0x%p, size 0x%x W%LZLNW ttZtN`@RSDS{GGJoSverifier.pdbGCTL.rdata$brc.cfguardA.rdata@Z .rdata$sxdataLZ.rdata$zzzdbg[1.text$mn.xdata$xB.edata6.data$brc .datad.bssP.idata$5P.00cfgX.idata$2l.idata$3P.idata$4 .idata$6.rsrc$01.rsrc$02UEEE}t} t E xu M QU ELEM9EUE BHM;UsEMU;EvMUEPMQUBPMQE}}UELMUREPMQREP迕E}}TMUD EMQU REH$QUR艕E}}EMTUEPM(QUB,PMQSE}}UELMURE0PMQ4REPE}}MUD EMQU@REHDQURE}}EMTUEPM8QUBMA8UELMU EBDM UQH3Ext MIUzt EHMy t UJ Ex(t MI(Uz0t EH0My@t UJ@Ex8t MI8E]̋UQ}t} t E xu ȅU BE MLMU:Ext MIUzt EHMy t UJ Ex(t MI(Uz0t EH0My8t UJ8Ex@t MI@ZU B3]̋UEE}s?E MAUEEM;Ms;Ut1M;MsUt MMUUEE뽋M;Mv9URjd0HQUE8uMMUEMUEEM;MsfUt\MQUMRE;Ev< MMU;UsEt UUEEMM뒋U3ɋUf ЋE3ҋEfTMED]̋U$3ʼnEEh E}}ErjEPM܉ |YhȦhjhB' `hjhZ' hjh\' hjh^' fhjh`v' hjhbb' hjhdN' xYjjhhjhUR`EMPUE}h jhhh?E MMU |jM Phuek3 fk3ɋ fLk D kǁZkǀ\\jjhhjhMQ`UMPUE}|hjhhh@jjjhЦjh EP `MMPUjjj@hYjhLUR`EMPU3M3"]̋UE}rURh #h(EM Yh,]̋Ud0Hhu3Eh(kZuNk\u=kUZkU \kǁ^E_E UUE;`sBM<\u3UEZMU \E^MMh,E]̋UEd0Hhu3h(E UUE;`s_MU;ZuNEM ; \u?kǀZkǂ\kǁ^Eh,}t E3]̋Ud0Hhu3Eh(E UUE;fsBMU„RHEEEMQEPMEEE]̋UE HU JEUE PMQG]̋Ujh(h`dPSVW1E3PEde} u3^E PMQ9U u'EEE E̍MQU RjEP0ME E܋M (MEEU܁:ͫu0E܁xu$M9uUBH;M u UBEEEoMEЁ}u@EMă MċUTU̍EPM QjUR/EEEËeEE,E PM QhEԃ}t UԃUEEMd Y_^[]̋UE PMQ+E}UBu'EEM MURE PjMQ/UREPEEEMUA ;BtMMURE PjMQ.UEJ0;HtUUEPM QjUR.jjEPMQ1E]̋UE HU JEHUJE PMQD]̋UE HU JEHUJE PD]̋U3ʼnEE H U JEM P$Q,EtjCUMPUM A0jURE PMQEUEM HUE BXMQjU RE PlEMQ\EP\MQ`E PMQ`U B PMQ2UMUR7M3 ]̋U jEPM QUR`E}EPMQEUMUBߋMAURE PpEMQ\EP\MUA`+BMA`UB PMQ_U+ȋUEPbE]̋U E H MU BM AUM}@wAUEMUE9MtUUE PMUP3AYMUE9Et-MMU EJ;HwU REP@MUƋE PMQ@]̋U EE E}@w5MUEMU9EtMMIUUŋEMU”9UtEEMQ;U rEME}t-UR@EHUJEUE]̋UE HMUJE H+MUJE MHU$RE $Pq@MQUR]̋UEM HUEBM$Q=?UE BMUQE$PM$Q@UBEMAUB+EMAUREPMQURP]̋U E H($MUBtxMQEPM 9QudUR?EHUJEUE MQPE HUJE HM$Q>UREPFM Q$$UEHtlU BM AU9BuXEP>MQEPMEM QEPM QU$R=>EPMQU B($EM UA;BuOM UA;BuAMQURhEHQUBPcMQURfE PMQY U REP]̋UEEEjEPxMylt>UBlEMUAl;Bpu MApUEHJlUBtMAtE}t[Ut?MQdE HdUzdu E@hMMUB PMQEUUEH MU+EMUREPMQEE]̋U3ʼnEEE} u2aE U UEHUJEHQjUBPMQTP=Ut/My0t&UB0P CMMPUUB0jEPM t.E U EHUJEPMxQ; UREP.MQU Ujj E Pj+Mt$ExtMQRCEMPUMEMQEPMQjUPtM3]̋U EEsyjM QURvE}| EE}tKjEP|Ms(UMU BM AEUR|E]̋U 3ʼnEEEE U U;MP$Q,EtAUz0tEH0QCUMPUjCEMPUMA0UREPOEMͫUB܋EMQ0PEH QURmE}uEPMQdЅujEPMQUBMAUBPMQ?UJbU UEH MUtBMytUBP CMMPUjCUMPUMAU;@XvE PMQjURkE @MyluUE BlMU QpEHpU QEM HpUBtMAtUEMU t:MUzduEMHdUEBhMQhEMUQhEPM;@Xv EPM3]̋UEHlM}t.UtMMUB;E uE MQU3]̋UjEP MxQq8Ѕu;EUExP5EMMUBMAEURE]̋U E PMQkE}UEPEMQE}t}uU REPE}ttEM MUREPWE}| EE}u9MQURjEPMQURE PMQEEE}t UREP:}t MQUR'}tHEH;M v=UtEPE MQE}tURE PMQUR E] ̋UEMUU UE4;Ew'MQUREH UJ E4E΋MU E]̋U4EPE}EEMUEHMUE;Hjh@URE}tEHMU@UPEEEPMQ_E}| EE}uoUUE@EEMQt E@EEPMQURdE}| EE}u9}tEPMQ2}thUREPEMU;BuMUEMHUREP}u>}t6MQTE̋URHEЋEPMQh@UREPMQMUz@v(EPEԃ}tMQh@UREPqM$Q2UREP(MQEE]̋U3ʼnEE၇U%t ƅ{Mu ƅ{lEt Pu ƅ{?U%t"M ; Tr U ;Tv ƅ{ EhR|Pj j$ȉpDžtttt;ps.t|;Trt|; Tw뵋t;pu ƅ{iEt6U°Rll3ҹd;Ur ƅ{"=t =u ƅ{ƅ{{M3]̋UE MUEM;Ms3U;Uv] ̋UE EMQXUE@XE]̋U]̋U\3ʼnEhEPEEEMMEEURhhDXxẼ}| EE}uEjj,EPjPẼ}| EE}uEhM +UhT.Th UhdXh`X|XP0H Qhjj]E̋M3]̋U 3EEEEEEEEjMQhUREE]̋UT3ʼnEE}u3=}uETu+-E}| EE}u3} u}t3EEjh MQUR"E}| EE}uEt h3E Mt E@EURhEPMQE}| EE}u)hjUREt hq3 hhMQ UEP@MUJDjhEPE}| EE}u)hjMQUt h3EEMUEBMUJE X}tU MU%tMQEPM tEHUJjEPMUhjEHQE}| EE}u)hjUREt h3sjMQUREPM QURMUu6EHQhjUREt hm3 MEjEPjMREEQE}| EE}uFUPMQRhjEPMt h3^UR)ExP)MQ)U„R)E}@sEMRu)EE܋MQ[)U@EPMUh EP|MQEUREEPMQhPUREPMQjCUċMPUċMjhhhpU RE@Xh (MQhT(TTh ,E-M3]̋U43ʼnEEd0M;Hu1hjhjhjhURh(j 33aEP?E}u3HjMQTUEjM QEjU RE}EEMujjEPMQUB PMQRCEMPUMt.Ex0t%MQ0RCE܋MPU܋MA0YUEMUE9EtxMMjj U REP=MQRE P CM؋MPU؋Ut%MytUBP CMԋMPUsURIth (EP& T Th ,UREHQUtEQCUЋMPUЋEHMUUEMU9UuhjEHQhjUBP뽋MQ3M3@]̋UVEEE}vOT@t,hjhjhHMQh(URhXj0E t h3 MMU#UUEP?E}u3MU QU E$ȅu U REPMt<%t}sMQUR=uEPE}tE}s&MхuEPMQHЅuX}u7E PMQjUREPPMQEUR}EMH UtMQEP*MQURMMqUREP+MqUREPMQE}| EE}t UBE}t}MQURE$ȅuCU uEH QhUBP6 }tMQ RjEHQ U REH QUBPMQUR}}t8}tjEPMQU REP"MQUREPLMхu8EPM QUPM MQE}tkpYpYU…u!MQ|}uU t hE^] ̋U E}u?T%t,hjhjhpMQhxURhj&-EPE}u2MU QU E PMQ]UREPE}t/MAUBMAUREPEMQU REQUREEPaMuU t hE] ̋U43ʼnEEEEEEE}vP T@t,hjhjhHURh(EPhXj+M t h:3UUE#EEMQxE}u3UE BE M QUREPMQE}ujjUREPHM }uUE;B v EMQ +URhEHMQ UEB MuEMHUB PMQUBEE,}t MQ U EHMUUE EEMQU REPE}uM QURoEPMQBE܋URU;UrEPMQUR EPMQUR E;Ev`M tU+URjEEP >}tM+MQhUUR| E+EPhMMQ_ }t$UREPyEMQUԋEHM#UREPM QU REQU t E %E؃}t$MQUREЋEЋMԉHUЋE؉B@MQU RE PMREPjM QU REQ}t2UBEHUJEPMQEURE PMREP}teMt.Ex0t%MQ0RCE̋MPŰMA0UREP]MQUREEMQ0P}u4}u.E$ȅu"UREPM QUPMQEUR}uE t hFEM3]̋U EEPhE}uEMU QU E PMQU REPaMQUR4E}t EH MURy}uEPM QUPMQXEUR}uE t hdE] ̋U Tu3h ( T;MTUE}Tt4E-EMUE-M U U EEËM; Tt/hjhjhTRhEPhj%& TMh ,E]̋UQEPE}u3$MU QU E PMQ;UR3]̋U EPoE}u2EMU QU E PMQ}t0U REP_MQUR2E}tEEP|MuURE PMREPEMQE] ̋U]̋UQEPE}u2MR]̋UQEPQE}u2MR]̋UEPE}u2MU QU E PMQU REP MQURE}tEPMQEUEBEEMQ}u"UREPM QUPMQEURvE]̋UEP?E}u2MU QU E PMQU REP9MQURE}t8EPMQE}t UEH }t UEH EEUR}u&EPMQURE PMREPEMQE]̋UEPOE}u2MU QU E PMQU REPIMQURE}t6EPMQEUҋE#PMQUB EMAEEUR0}u&EPMQURE PMREPwEMQE]̋UQEPaE}u2%jMQyUBMAUR]̋U3]̋U3]̋UQEPE}u2Mu2]̋U4EPj MQU RjE}|} u}u E5EMԉMIUUEPMQE}t U MUUEH MEU%t3hMQRhEPh MQh(URhj  Et.hjhURh EPh(MQh,jU%t3h@MQRhEPh MQh(URhTjEt0h|URhEPh MQhURhjkEt3h@UBPhMQh URh(EPhj.Mt3h@EHQhURh EPh(MQhjUt0hMQhURh EPh(MQh jUt0hMQhURh EPh(MQh8j}U t3hLMQRhEPh MQh(URh\j @hjhEPh MQh(URhj]̋UjhHh`dPSVW1E3PEdeE HMEEEEU REPiEM9ͫt%UUE8ͫu MMUztEEMQ;Ut EE|MQREPFM9A tUUE EMMtEUEBEMMhU+UREPE؃}tMMU؉Uȃ}tEPMQUREPEjMÉ}uBEM MUTUȍEPMQUREPZEEEËeEMd Y_^[]̋Ujhhh`dPSVW1E3PEdeEEEE EEM9ͫt!U:ͫu E E̋M̃MyUzt ẼEbMQ;Ut ẼEFMt>U%u.hjMU QR E}tẼE̋MMԃ}tURE PMQUREjEU؁}uBEẼ E̋MLMԍURE PMQUREEEËeEMd Y_^[]̋Ujhh`dPSVW1E3PEdeEEEE EEM9ͫtŨUExtM̃MUtxEMP +Q u.hjEM HQq E}tŨŰEEԃ}u0hMQRE P> E}tḾɀM̋UUԃ}tEPM QUREPHEjME؁}uBEM̃ M̋UTUԍEPM QUREPEEEËeEMd Y_^[]̋U E PMQ[EUEBMUQEPMQ艾UB EͫMA܋UE H0JUBE%MAUUUEEM+MQhUR ]̋U3ʼnEE EMUJEMHUEB MͫUB܋Eu*U UUEEM+MQhUR  EtjCUMPUMA UBM3V]̋UEEM#MMUUEPj MQ }3U%uMQjUR }3E%EMMUUEPMQU RE}u3xEPMQU REPfMQURIEPMQ URjE$ȅu UuEPhM Q E ]̋UE EjjMQUREPMQ豹UR EPܹͫUͫ E}ͫt뮋EHUJEHQhU R E@MQEPMQUR ]̋U 3ʼnEEE EM MjjUREPMUE;BMEPj MQi}3URjEPO}3Mt$ExtMQRCEMPUMQUREPMQ=EC3<UUEPMQU RE EPE}u3 MQURE PMQUPȅtNURjE PMQUPȅt&URE PMQUPȅuUREPM QUR3yEM;HwUREPMQ @UBPMQUR Eu!MU+QRhEMHQ UREPM QUREM3 ]̋UE EMQURE PE}uE'%M MU%u MME]̋UQjjEPMQ)UREPM QURE PEE]̋UQjjEPMQURE PMQU REE]̋UQEPMQU REPM QEE]̋UQ}uEPMQU REE PMQU REE]̋UH3ʼnEEhhQU MA| Dž Džt tDžA]$ ,M 9 3uDžA hj4PM莫| Dž DžuDžAM;r?;w DžAM;sUlhjQ Mܪ| Dž Džu M3f]̋U(ET+ M MhjURUMCE}}T+ E EhjMQUME}}UUEEEMMU;UE؉EM;Mu&UREPhjj]EAhLjMQUM茩E}}gU;Ut#EPMQh\jj]EAhT EE]̋U Eu_hT(hȅu-hnEUUhEPMQj\hT,hT]̋UEEM9T+ U Uh"jEPUME}}}uk€D+ U Uh"jEPUMыE}}FMU< + E M9A v& + U E9P s ME]̋UE8u EMBEEEjhMQjURjLE}|CEMUQEPhM UUE]̋UQE}u3RE E MQU E;Pv MQUBE M;AwUBEMQU EPE]̋UE E MQ+U EP]̋UEE} tK}tEEt;UEff UUEEM M UUEE믃} uMMUUEz3Mf}tUEE]̋UE EhMQUR>E}|hEPjMQUR E}v3MfE] ̋UEE E} tMtEEM M ܃} uEW}t}| U+U E ME] ̋U E EE}t }v EWMQUREPBE}t}| MU EE] ̋UQE} tE ;EvEWE] ̋UEEE EMQUREPMQE}|U;UvEEEMUUEz%E;EuMMMUEEMM}tUEE]̋U E EhMQURE}|)EEMQURjEPMQ EE }vUE]̋UEE E} tMtEEM M ܃} uEW}t}| U+U E ME] ̋U E EE}t }v EWMQUREP@E}t}| MU EE] ̋UEEE EMQUREPMQE}|U;Uv#EMAU3MfUUEz*E;EuMUJE3ɋUf EEMM}tUEE]̋UQhE PMQE}|UREPjM QURE} v3MfE]̋U}t Exu h"MQUREPjjE}}EMQE}}UBP*E}u E } uDEMQURKE%Eu MQ% UREPFMQ@EUREPMMUREPM MUREP;MQURE] ̋Uh"EPMQjUREPE}}EMQHDh"UREPjMQURE}}EEPLDh"MQURjEPMQE}}EURPDh"EPMQjUREPE}}ERMQTDh#UREPjMQURE}}EEPXDE]̋U 3ʼnEh#hP MQhR@ is舟3ҋf HDQjRjh?jjjPhPt3M3ם]̋U 3ʼnELDPEMQUUMPUM3肝]̋Ud3ʼnEE PDPEMQUREPjh#MQUUMPUE}u}tEPh# 3E MMU sELE܅tUELE܈LыUU} sӝEDEMQh#UR  u} tE MM3c]̋UH3ʼnETDPEM Qh#jUR E܉E؋M؃MȋUffEփEf}uM+MMċUčDEMQURjjh#EPMMЋMPUЉE}u EEE̋M3蕛]̋U3ʼnEXDPEh#MQUUMPUE}u EEEM3!]̋U3ʼnETDPEjM Qjjh#UREEMPUE}u EEEM3觚]̋U3ʼnETDPEh#MQUUMPUE}u EEEM31]̋U4VWEE}t EEԃ} u x}uLEMMUUEEMMkTUUE M&U Eԋ ;t U E}w kEԍLMUE@MAUB EEMM}s UUEEM+MUJEM<QE @H}s KUUEEM+MUJ E xYHUBh(M}Y}HYU`}njZ}nj\Mf}ǐ`}ǐbh,Th (Ek TMMU;Us EE+EEMMU+UEPMUE THkMTUTEM܋U܋EE}TtSM܁M؋U؁ŰEMŰB@AMU؋BAMU؋A MU؉Qh ,KEE;Es E3M+MMUUE+EMAUEMAE_^] ̋U4VWEEEEE}t EE} t}u M U;t M U}w Exr MMUzu6kUD EMUQUEMH MUEBEMyukMTUExukELMUzukUD E}?}s MMUE M;v U:t Ev Mv rxYh(uYuHYE `uƌZuƌ\UfuƐ`uƐbh,}}s MMUE M;v yU:t g<%E̋MQEPMQ ŰEPMQ<EH @}EU;Us EkHMMUE;t M;Ms U+UUE E܃E܋MU;QkEMTUԋEԃ8t E h ( TMU؋E؁}TtHM؁MUԋE;Bu/jMQ%~UEԋHJUEԋH UR!~h ,JE_^] ̋UhE PMQE}|)UUEPMQjU REP@EE} v3ɋUf E]̋UQEPM QURE}|EPM QURE EE]̋UhEPM QURE}|$hEPjM +MQUE PQEE] ̋UQhE PMQE}|hURjE PMQE} v3ҋEfE] ̋U83ʼnEEEE EЋE 3ҹUEkDUЉT DMQjUREPE܃}jMQUREPE܃}}M؉ME UU}EMUUE;EM;M} <UDEȋMȃU EgqE}tMRjEP裕 L}tMQUREPMQ 3ҋEMfAUE3MUJE+M3Ԏ]̋UEPhCjURhE}|;,DPMQjURhDE}}DyrEPhDjAMQ E}|<DREPjMQh0DE}}4DURhCj?EPE}|< CQURjEPh DE}}$DMQhCj@UROE}|8CPMQjURh8DE}} =t=t Q3]̋U Et  U%t  M t  E t  U%t  M@t  Et  U%@t  M@t  E k tdEE UUE;EsMM R0MfM ЋUU}sv3Mf  U%t  MtEU EtU%M]̋U=h.u [EPMQURU M]̋UQd0Hht7Ut< < < <EE E]̋UQd0Hht2}t#} tUE <EE .}t!} tUE EE E]̋Ud0Hhu3.<u3jEPMQURE PMQ]̋Ud0Hhu3<u3 EP]̋UQd0Hhu3"ME}tUz t 3]̋UQd0Hhu3!ME}tU:~ 3]̋UQd0Hhu E MTQEE]̋UQd0Hhu E M`QEE]̋UEPMQU REP親]̋U EEMTE}u E[MQURE PMQ\E}};}uU:u EE}tE}tMUE]̋U EMTE}u EE8uME#iE UUEM;s8}s2U + E MUʋEMU$T뵃}sE EME]̋U EM[SE}u E+EjjEP+ M QUREE]̋UE PMQ]̋U츠t 3]̋U}u VE|EM;vUEMMCUCE dBMEmUREPMQu 3]̋U%]̋UQ3ʼnEVU u 4uEttuuB uR?5l.PP֋M3^n] ̋U3V;wrwE0 E^]̋UM9uE I  3]̋UT3ĉ$PS]D$Vu Wj@3t$WPxthD$`WPhtD$hD$HHC $ <Vv CKt$t$Dt$ D$CL$ ^D$0Sv6D$PΉ|$(|$0T$|$4|$8|$@D$H T$LD$DPօuE;JCF~ C^Sv6ΉD$D$HD$P|$ D$H|$PPօt ;v Nj$\_^[3l]̋U\3ʼnESVWS3VP's DžjXjPVV4j3CSRP4RPjP(tej,VPr DžVj,PjVDž8x ;ދM_^3[k]̋ULVWj}Y3E3j,EEWP}U0r uE}EȍEEWj,PjWE8_^]̋UEVWth.uMu%f} u..ugf} u .Po.cuCwf} u .F.:f} u .P'.f} .t .P_^]̋UQ3ʼnEd0V5.QjpP֋M3^oj]̋UQ3ʼnEd0Vu5.jpP֋M3^,j]̋UQ3ʼnEEV0d05.jpP֋M3^i]̋U3ʼnESVWn,EPV5.WP=uBW5u}uĸ؍EPQM_^3[ci]Åx3ۋÉE9vNw ӋΉUt0\uщUAuMtAPh.0YYtE@E;r4{~t5|.Eh.PPhSEPWB5|.Eh.PPhSEPW ̋US]MVu9] u 33.UeeQ3jE PQMD<xɋE;Ew.UV3ˋ]E PQr=xM3ҋEVuUU+UPQK=pEU^[] ̋U43ʼnES] VW}3UE;u;uhVum RSWUЉuЉu<}ЪͫQύUjPQMR;Rh Vuމ}]m} vj _}M9q9ut}kQMWSuE:}MUރu EUM‹DME‰UUFDED ;r]}EAY r.Uj3PQML:L.UQj3PQM#:#hVuVjlfM fufM3fMfUfUj Xf;vfM‰Ff}EEbj.QuU䋈3PQM9M3Mf;s]UFEڋuEEuEE}UUJ:M>Ћ}~mUuƋM܋] }u3f;t9Eu.3ɋljFˉN 3e_^[M3d]̋U3ʼnESVWڋM]}u Su Uu9xs]3};]u;} t]+]QuMWSj8xH}tuMVWSPUx,}Eu ؋|;]u;} t33VNjM_^3[c]̀yu2At 38A AtA ? .A,̋UE S.W3ɉMO;C,sfC,fGfVu9Mugs4Ws0j7sDWs@j7sAt tKVBt83fEE .3QjA8ME URPU4xE?3^]̋UQQVWFt\>tW.t[U 3+Mω}jQMRU}N5xFM9Uwr;w(_^]NH,}EPQuu uxFtF++ME3̋U(3ʼnES]VW} h3VW3f Su u" uQRP}fu3F_GG #΃d DDDPu uv ‹J(jBYE EtuWuux3M_^3[^]̋U`3ʼnESVW3ۋ.]Љ]ԋGwЉ]N8EGE3EfEEGF83Y@YY MMAtF(^(G ] G$FEF^AB,f$^4F,F EF0Z,3AU HU.B,EEUtM؃+ȉMMMUAy ~EPEPQu u7.MMB,;=UjuS29}}.UȋjuS1.Ujuu1U9]9U.UjuuV1|f}K.3ɋB,FFNF$N N +J,NF(N,FwLwHVwDPօt G@EfEfG@.uUjVS0.U܋ jVSo0M3B .q,iu;vЋE+ЃuMM3 .%ffNff#EU.]@,E_E3EUM EEMʉE3e;EQRUSV.fEMP.wPp,u<t}EMEPSVjGL8w0.P,E΃ȋÃ;Esw ;MhEfG@$UM<<<A$t y ;_(u ;W,uJ0tDAf;s6k 3G0XM;MuM ;HMB;rߋEA?7EF(PEPQu u7_Ef$MF .jZ@,]EU U .F(X,3]E N,EfF E^F_DtwLwHVP3e_^[M3V] ̋U.L$ VujvPp,uxD$Pu u^]̋U$3ʼnE.SVW@,ډME[u3̉MfF@t!!CU}3U} QuWRыM6*ȅ.MjvPp,uaȅxx3f;F@ufEfF@}tMVuWuPUȅxBFL8w>fE.fF@B,UЉUEu;}wr;UsMV_3ɋUt{(uN3ۉY(F F$AQyY Y$A,Q0y4~DtvLvHQP׸(e_^[M3U]̋U83ʼnESV5.WU؉M苾YFl܉EYeӉeQMWu u(5.U܋j_W.)9u EU DME싆9u EU DME􋆸9u EU DME}j@jwV{ZG ]G$FEhF,^0F4jwKZG F8wLwHVwDPօt GLt)Wu33ufG@uuS]yd]e}QűQuЋuub'5 .ytApu 0EU DUEy|Axu 0EU DUE􃹄u 0؋D]E3ɉE9Mu9Mu;]u ;Ewj@QVYG G$FEhF,^0F4jwXG F8wLwHVwDPօGL8w@t*M3Wu3fG@uuuSxGL8w]C];]s]3e_^[M3R] ̋U03ʼnESV5.WUM苾V܉EzVeӃeeQMWu u%`5.Uj&u EU DMEu EU DME}j@jwVWG ]G$FEhF,^0F4jwWWG F8wLwHVwDPօt GLwt'MUWu3ufG@uuSP.]؋u܋P,3;(r;QuԋMӋ]jXPRM$ .$ u U 4DE,(u ȋ \ΉM];Mu ;]wj@jV6VG G$FEhF,F0^4jw VG F8wLwHVwDPօGL8w5MUWu3ufG@uSuxGL83e_^[M3(O] ̋U@3ʼnE.SىU]ȋVW-}u QVu ׋u".ϋ}33ҋuA;r Br܍ }؅u c5.EEN,M܉EReˉe׉M؉EUԃ}Eċ Du}%JB 3҉E33f;}}E ty+N,EQũRPUQMȉE!}Eu M U TE@Ef;Esf;Ew t5.뒋E5.EM؋UA E@M؉UԉE=sEEtE3uSWe_^[M3L] ̋U3ʼnE.3SVW]}E MEGjMpPr,QMx 7twuuSPօx3M_^3[7L]̋UQ3ĉ$SVW}j@j_sVgRC C$FEF0E hF,F4js7RC F8sLsHVsDPօt5CL8s+.t1t-wWu uxx3L$ _^[3_K]wWu u7̋UX3ʼnESVW}fUΉMЋGEԡ.OQMЋVuu L5.gPelt5t1PhUjWvdpUv`j?EGP (;,uʉULM܉E Mwj@jVPG G$FE؉F0EhF,F4jwPG F8wLwHVwDPօ$UEPj,(u E؉U DM؉E܋wj@jVPG MG$Fu F,3F,E؉F0EhF4jwOG F8wLwHVwDPօZ}uUԍEȋMPuu r5.EعfU΃g4g8G(E܉G,EȉG0( f;uf9Mvf;u f9MsG<GLX403ۉEċȉẼ}u3IE Mwj@jVNG G$FE؉F0EhF,F4jwNG F8wLwHVwDPօ,GL8t&MкP,Wuu=GL8weMCMԉM̃@sVE3x3M ]EQfUURUh7]EP,PQˉ}GL5.EP,3}8] wEj@jVEMG G$FEhF, ^0F4jwvMG F8wLwHVwDPօt6UԍEQMP.hp6PuSx3EPƍe_^[M3F]̋U<3ʼnES‰EVWf!v (2F,39#NF] }QЉMSUЉUԉUUUUUWEEUP3PQ_EUP 3PQ>E EtuU܋uB-9}u 9]`F +~ j@jPEK.UYY3PQu7.UQR 3PQF.UQ$ R3PQ.UQ,(R3PQ.Uȃeeu03PQx~MuċFvUFA(AA, @y0Y4űuM~$FA8tv,v(QP׋F,8wE EtU܋uuR3M_^3[D]̋Ud3ʼnESeVWQjUuGEG_ЃEԡ.3ME PQ.Ueeu싈3ME PQwj@jVIG G$FF, EF0EhF4jwIG F8wLwHVwDPօt ~E EuS.#Q3MEPQ>.S Q3MEPQ.SQ$ 3MEPQ.SQ,(3MEPQb.U؃eeu싈03MEPQuԋUC(G G$CC, `EC0EC4wuuGC8GDEtwLwHSPUGL8,.Uu싈3MEPQES Etwj@jVGG 3ɋG$F.F, hjEF0M N4wGG F8GDEtwLwHVPUE .EGEGEEG EG$EEEGEGDEċGHEȋGLE3M]E 3PQBMM_^3[@]3̋U43ʼnESeVWQjUЉuGEG_ЃEԡ.3ME PQ2r.Ueeu䋈3ME PQ\@wj@jVIFG G$FF, EF0EhF4jwFG F8wLwHVwDPօt uE Ej@jSE.SYY3MEPQP.S Q3MEPQ"b.SQ$ 3MEPQ4.SQ,(3MEPQ.U؃eeu䋈03MEPQuԋUC(G G$CC, `EC0EC4wuu}GC8GDEtwLwHSPUGL8i.Uu䋈3MEPQ]Ag.Ueeu䋈3ME PQ& Oj@jQMDM G G$AA, EA0EhA4jwCM GA8GDEwLwHQPUj@jSC.SYY3MEPQU.S Q3MEPQ'.SQ$ 3MEPQ.SQ,(3MEPQ.U؃eeu䋈03MEPQuԋUC(G G$CC, @EC0EC4wuuBGC8GDEtwLwHSPUGL8w2.Uu䋈3MEPQ&xE Et3M_^3[;]̋U,3ʼnESVWE3PjEԋPSS}uz}ut5.ESjP.Ή]EPWPօxsM9MuA5.ESjP.]􋀰PWPօx>EM;Eu/MԋEMQjMQSP5.WPօP3M_^3[:]̋U3ʼnES]$Vu(WtVӋg&.3ۋ5x.Sj@PSWPօ u .p ppjS;v؉.pppjj|hPLu -QЋO jY؅nu 33ɉ;u 3 LV.QNj@3FPQ =Cu@ʉ;hE 3ۉPT dh3fL\`lptx|9Cu\`.p$p pjS4 .pppjS =Clpu2QjSR bPh.3QjQP j@ jP<p l@hjP Dž8<< DP PPօwmt}.t+t'8wALV#%8wLVhv3.3PQ xj@ jPs;l p_Vbuj Yue΋@$F 3_^̋SVW3j=Y@GS(W>P}cS,_^[̋SVWh@(jY@Sbh@,_^[̋SVW3j=3Yh@( >9Xt;uh@,_^[̋SVWh@ad50d3\Wjv@uh/Wj] /hK$h@5$ obDŽ_^[̃=$u3cȡ$̋VjV :jXu}~vw~S^PvwVv ShPh@lOjEPjSjDx:}u }t+h/wh$0VhP0v hp0Sh0hZi[^_]j hr%3uh@hAEE3@ËeuEy%̃=At h@P̋SVWٿ A3jSW_t&@rSh0jj]̸3_^[̋UQQVW3uiSjh@lEt< AuWVS9_;tEEE@rWh0Vj],E[t h@`_^]ËEjh($ډMuYjh@TtEe3u܃s+jj AP^tuSuPFEe$h@`̋UQVW3A< M+BS];+;]; r ];pr%]; ] ; 3E+tct)P]p] SVhh41v] hL1u ht1Sh1Vh1hf^PE]p=] SVh 4P(]p ] SVh3OEuPPu SVhhpi[E_^]̋UQVWu }WEt.u MW!=t ׋ǚu MW+u ׋_^]̋Qj5̋Qj5t̋U} t+} !t"jq1Ruhhh3@3]̋U VW3u#EPjEPWWjDx/Eu&B;v+;sWWWWVuh.h_^]̋UQQVjjE3PjQFXx E Eu3^]̋UQVWEPu uWQy}tEWuh1jj]-E;E t%}tWuu Ph2jj]A_^] ̋U|VWj|_WEjP" }El@PjyWEjP" E@Ep@EdBEh@_^]̋UVh)E3PuEPEPVVLȅh42EPEPVEPuȅEDEhL2PEPVEPuȅE8Ehh2PEPVEPuȅxfE<Eh2PEPVEPuȅx7EEh2PEPVEPuȅxE^]̋UVh)E3PuEPEPVVLh2EPhVEPuxnh2EPhVEPuxHh2EPh@VEPux"h3EPhVEPu^]̋U03ʼnEVWjj,EЋPjP |d0.D.|.x.Xx.P.<.H l. . . tQt.dp.EPW .Qd 0h.vM_3^]̋V5`WtIt t t tt tu =\uk d;;rL;s`;k _^̋UQQ=CPSVWw5\0T5``;Lt!B2Ek D8E;r 39EsUk _^[]̋V0u `u q6u)5Xtk W:;rP;s:_k ~u6hEjj]̋^̋VWj*Y`300j3`;`>;9;0;<=;`<<>L<X<Y3:@;_^̋ T3t X3| \3h ` xxtq d3tt[ h3^tE l3Hdt/ p32lt t3pt3n̋SWڃw3JGiVPd0jpt">^tF P y 3^_[̋ t | hw xl a V dK l@ p53t|hxdlp̋Vt"~t F Pd0Vjpt^̋U3ʼnEWfU}MS3V39wÉ]t G P(3@G@37ʉMt!i(f90twPP֋M3i@@D>,G0PfMEfL>(D>8E D>@ED>D3fD>*@jZf;tf;uVtJP4tC.effD>*3f;s#WH}֍YG[R;r}]jZ3f9L>*u.QGHPj R$fu3@fD>*ED>HfD>*^[t G P,M3_e]h:Oh: ̋U@ESVuWh FPj~,WEPu M~]u@"Sh@$F$3u#658sHup(Ht';X u :S,S(3_^[Ép̋SV3@Wt#3ҹ :9WhhLVj]j s@@t H ;utt V_^[̋SV3ۋ@Wt#3ҹ :VhLSj]3ҋHt(W :V, V(6<t*u 9uSSS6Vhhx I_^[̋SV3Wڋ>t9u9u PPP6Vh,d0;trjֹ`:t3PPPPVhhxHEh :(Ӌau 9uPPP6VhhxaHh :,_^[<VWt(uS :S(֋S,[_^̋V|;~tEV ;P$u ~|jЃ t"p^jv jvVhhxG^̋UQSW3M<Vh :(5;^ U9F Ntt U3ɋEt=t)tuHPRSQv h-jSu Qv hjRSQv h jRSQv hhxF~v_^;^ svw uh :,_[]̋UQQSVW:<؉][$3G΋PEtSHQ9E@(V3Ƀ uwN t,d0;u;tj6jQVhhxENt(d0;tj6jQVhhxEUW^ ~ 29^ uF3QV؅tD3G9~ Uj <tuW8p$><t~_^[]̋USVW8<؉]zC$3ۉECtuOQE8G(FeUE9V u5FF}RF98tMM8uV3 Uu39~ t0d0;uE9F tW6Wv VhhxJD9~t(d0;tW6WvVhhxDEˋUF S^"AN@s~>9V !tRGP67G,VEE PGP71j6j1Vh hxCV(xMN33C;…u RU<tuj6p$'<tg_^[]̋UQSVW3G6uhjZΉ]t<tQf6p$d<t/u%3ҋtVs$ P 63ҋB 3ۅFV,xut US_^[]=u3̋U 3ʼnE@S]VWutSVWhLjj]t5u VWjfZxSupWPh :(3ҋEtC<t7Htt ȋE3jjQpp hhxwAh :,u VWjfZx/SupWPh :(}u]yP=Cs :S,WS(&@tWhLjj]x<t2Kt t3jjPss hhx:>W,EVhe=؉]yEW,EVPeS :uW(ÿ :]W(E :W,VhjhȎthj8Zu@tVVhMjj]uTh :(e<t&u3ҋu9tTEVPuh :,̋UMhj8Z7M3Bh]%T̋UMhj8ZM3B8]%l̋UMhj8ZM3 ]%`̋UMhj8ZM3B]%̋UMhj8ZwM3B]%̋USV3W9t9]tz8z8u Z8tI>yE<t9u/PSPSPShM6h$Nh28>u _^[]́r; s Qh:W̋UQSVW.<t7u-C$ΉE~3ҋBtuOQ@.G(VtC~ 3ɋjA<tuj'.p$~ <t_^[]̋VFt`>t[xuSW :W(3ҋ)u1'y&@tVhHNjj]W,_^̋UQSVWx-<t7u-C$ΉEU3ҋBtuOQ-G(V(xKV3u 3ɋPA<tuj,p$M <t_^[]̋UMhjZ\Mt]̋UMhjZgMt]̋ C3@;u 9Cs;w3̋Ut39Ev 9 t @;Er3]3@̋UVu[=tRtd 0uuQd 03ҋW :W(uVW,_^]̋U3ʼnES3ۅtzV3FWNC@BwV}O tu U u WQSt7GtF@sGtF9u8:_^M3[O]jlh5ډ]܋щU3fEjY}f3u3}īu@tSRhNVj]VjEPVjt3@E!ujYu}jZU3@ËeejZU3@]܃}u4t t 3jjPSuhhx}6tbu;t[EjY}U3@Ëe3E]juPSuuh뤍MiPaPSuh눋M9Mu8}t2t <M3jPSuQhhx53@E؃}t3̋UQ3ʼnE3=CpVr 5dBtAPAPP5`BtAPP֋M3^J]h9(h9,̋VX'9WV3VPe 9A 9A t}P&9P%9P%9@P%9@ P%;rh9 9@<@@7At g 9A t S 9t D59_^t2á9t=t3;H$̋U S}3V59WщUt"F8~8?F0u 9G$N8;u2iF0G$ ȋE O$;F O?Q ;u_9Xt ;u3^[Ã̋UQQSVWutjPֹ } c3ۋ9] tjhS] S CsP!EPs Vj j$E3҉CPEjY9@Po"t 3ҋB_^[]̋U$S3ۉM]]zVWAjYYjY}L3uH=E}uMuuLuu33ҍNQjYE9@ P!u}3@EM"uD}SS5MQuh]u8]fQZNM9_ t 9w t3fGfGf@w fG3Bf;AM;t*^6C;HuC$8E E;u3Gt} uU3S@P3Eh(VPuEӃ b$J$9z@8 B$BPvE 3A$1A$}uA PEP? ˍAPGP0 fGfv 9 Ët Fus 9Dx3@ C$EC @HX9DT};t3JAU;Cu!A$3C$uu3p ы U;u뉍O3;t,MGZS93uC;Hu C$8E tG;u3@E_;@t3tj (YEPs(Vj j$t @(E{j ǠY}Et jZpEt 3ɍQ]t jZOI_^[] ̋U VuPAeS؅ CfuM!PSֹW{ wHfCf 9c 9^t|APF<uEhPjj]FWpuh@Pjj]F$UWp 99^t 6uUf$F$uATN$f$փtG@$t9x t Gutb ouj_EP Pj j$[^]̋VW3jY9@ 4V u9xt ;u3_^Ã̋V39Fu9FtPVFPfjZ^_̋SVW3:ǃtjt6 93j[ttHRp\ 93(tEHRp- 93tHRp 9u) 9u 9A$;t(tu,AA;Av!A;AvAAA;A vA t,APS0y9SphPjj] _^[̋V3tGt#ua 9j^IP= 9( P 9IPP9)p^̋V3^93A9Tu^Y@w9w9vT(^̋UD$VP3~D$PtD$Pj9 v+FPPD$ P`9 wփ@v-3FPPD$P*9@wփ@v-3FPoPD$P9@wօtW:t$ N6舾D$;ut$ N6pD$;ut$ N6XD$;u9T^]̋U=9EVu 99959tVPRQhPjj]WWVWPWRWQhPjp#_^]̡9 r 9É̋SVW39_ twQp$f9_w_3 N6;uGP3_^B[̋U SV3]9s f{ 9W{A8E;tJ]HQ$E;v += v +Ӂ s ^FE;uʋ 9]u3UQ(f{r,?C;t f{rO?CF;u 9q,_^[]̋U SVW];KuuM;t!؍{w V3G;]u]CfHCPjZ_^[]Íxw EVVP+EK;uՍC Px̋UQSVW3ɉM_30V6:u&B;GuB$3G$uuAM M;u_^[]̋U SڋVW]C tj YB s(z(j YK$t B$ B$KM;t*ڍxw EVVCPAE;Euۋ];t C PCfHCPsjZm_^[]̋UQQS3CV9W39=9h(QEPh9WEP59x9=9uh_^̋USWڋtcVuFE jjuGGS7vP؅y'g MtF^_[] ̋U 3ʼnEEVu W=`9NShQPPׅu|Qy$u:Ps p$jp$C Pss hh4,9N[M3_3@^]̋UQ3ʼnE=Wu Kt*Gu$V59tWhPHp$P^M3_]̋U$3ʼnE=SWu GV59t~jjjEj]{$uE}tFuEup p$jMp$A Pqq hh,9O3jPPPE܋PPօu^M_3[]̋USVW}j Y3}7/@$G_~tF$uj Y薳t F$Ox_^[]́=Cpr>t t3@39u9u9u⁸u3H$d0@ +@́=CpVr/~$uaFt3@^JF;3^́=Cpr#t3@3̋UVt/u9Q r 29A s3@yuAt ;r2;r3^]̋U,SV]<u3W}WJ؅rs$g5Mg$Y5MEB5ME+5MEEtN@}֋Fu3jjEPjjtygGN EGEG;~j39NtN9tN9BtN9tN9UMu9Uu 9UutNutN39F3_^[]̋U8SVWڋQEap$VC$ 39t(F@u"QQG Pww hh'N@֋jFjjEPjjtE9Ct4Psw X p$G juPww hh,NC;EtRjjEPjjXx@$t7@39t(9Et#9EtPPA Pqq hhuuuu uP֋M3^辷]̋U 3ʼnEVWj(Z0耟u upP3WjEPWutEyu dWWu PjZiM_3^<]̋U 3ʼnEVWj)Z0u upP3WjEPWutEyu dWWu PjZ١M_3^謶]̋UQ3ʼnEV3ҹduupu uPu duuu ujZ]M3^1]̋UQ3ʼnE3ҹVBuupu uPu duuu ujZM3^]̋UQ3ʼnEVjZ胝uupu uPփ}u"uuuu dp$jZqM3^E]̋UQ3ʼnEVjZuupu uPփ}u"uuuu p dp$jZM3^Ŵ]̋UQ3ʼnEVjZ胜upPujuj dp$jZ脟M3^Z]̋UEH4E uE;v3#EV0;w3;^] ̋UE MV@1;w3 I3;@^] ̋UQQ3ʼnEV5h5Pօx55@EPu 5PօxEM3^Q]3̋UQ3ʼnEVW} Gtu5p@PP֋5W5P֋M_3^߲]̋UQ3ʼnESVW} Gtu5p@PP֋5lSP֍GPO58SP֋5W5P֋M_^3[M]̋UQ3M@f9w2GSWj#[3V+P4Pq ~~y^M;~2^_[]̋UQQSf= VM ]u23Wf9t$]CxP0f9u 3Gf9u];u,t[ftVPYuJh,UV,YYt-ft"PYt fu3f9w2_^[]ð̋U3ʼnESVW3}eMkVEPx/EEE3ɍEMPhWE@MM_^]̋UL3ʼnESVWhPDž3Dž1PDžPhSDž@h#PPhPjP3xTu*u!jPP$ u 3dy`%uM_^3[0]̋U@3ʼnEVhVE܋PEPjEPjEPV3A} u~EE;vHjEEPjjEPVYh#EPh#EPhVEPEPVEPVEPVEPVM3^L]̋U =Wtkd0@@H8P]w3]t$nGPtS]3PGGP w\wXQ׉whmD_^[]̋UQS]VU#=MEp1p1;t ;u*;u~dFh #W;9VEap̋UQ3ʼnESVW(j YMu8uE 50ΉGEWG C$hGP֋y zM M_^3[7k] ̋UQ3ʼnEVx蕩H$EtDMu50P֋M3^j]̋UEh0E hp0]zEt 8~j̋UQ3ʼnESVWx3=RXϨH$BDtCTL EtH@$tA@t 0tN3ɅtV 3ҍF jj#VQRhh]H$ PH$5uPӋM_^3[i]̋U3ʼnESWكu utvxPh|PjSxVju_h|PDu9jh|PDu!jj4uShhM_3[h]ÍP<tu3PPPPPhh踳 ̋UxAuPcIt'|A=BtjhpX YY̸OVWu}uuu Wx-jujZcu裦 pp$Vj7jZS_^]̋UxAuPHt'|A=BtjhpX YY̸IVWu}u Wxx-jujZɹu pp$Vj7jZR_^] ̋UQ3ʼnEVj Z0#OupPHt0|A=BtjhpX YY腥@43A33A袸uuu uP33A跸tjujZƋM3^f]̋UQ3ʼnEVj!Z0cNupPNGt0|A=BtjhpX YYŤ@43A33Auuu uP33AtjujZ3ƋM3^e]̋UQ3ʼnEVj"Z0MupPFt0|A=BtjhpX YY@43>33A"uu uP33A:tjujZvƋM3^$e] ̋UQ3ʼnEVj#Z0LupPEt0|A=BtjhpX YYE@43>33Abuu uP33AztjujZ趶ƋM3^dd] ̋UQ3ʼnEVWjZx"Luxt!tt=tVP׋xjujZ<@t3@C@%yH@u pp$VjujZKM3^`]̋UQ3ʼnEVj+ZxCHM3Bpyu uP֋M3^,`]̋UQ3ʼnEVj,ZxGM3BpuP֋M3^_]̋UQ3ʼnEVj-ZxGM3Bpu uP֋M3^|_]̋UQ3ʼnEVj.Zx3GM3BpiM 3B^uu uP֋M3^_] ̋UQ3ʼnEVj/ZxFM3Bp uuuu uP֋M3^^]̋UQ3ʼnEVj0ZxsFM3Bpuuuu uP֋M3^S^]̋UQ3ʼnEVj1ZxFM3BpIu uP֋M3^]]̋UQ3ʼnEVj2ZxEM3Bpu uP֋M3^]]̋UQ3ʼnEVj3ZxSEM3Bpuuu uP֋M3^6]]̋UQ3ʼnEVj4ZxDM3Bp)u uP֋M3^\]̋U$3ʼnESVWjY3}3uj5Zx{D}@Et53ҋBu tVVVWj ZGtVjEPVWt95txh1(3Fu W}P׋x xMft h1,x xMiM_^3[[]̋UQ3ʼnEWj6ZxC} xt M 3BMjZuuuuu uP׋M3_o[]̋UQ3ʼnEVj7Zx3CMjZpiuuuu uP֋M3^[]̋UQ3ʼnEVj8ZxBMjZp uP֋M3^Z]̋UQ3ʼnEVj9ZxBMjZpuuu uP֋M3^fZ]̋UQ3ʼnEVj:Zx#BMjZpYuP֋M3^Z]̋UQ3ʼnEWj;ZxA}xt MjZu uP׋M3_Y]̋UQ3ʼnEWjZx@MjZpu uP֋M3^X]̋UQ3ʼnEVj?ZxC@MjZpyuuuu uP֋M3^#X]̋UQ3ʼnEVj@Zx?MjZpuuuu uP֋M3^W]̋UQ3ʼnEVjAZx?MjZpuuu uP֋M3^fW]̋UQ3ʼnEVjBZx#?MjZpYuuu uP֋M3^W]̋UQ3ʼnEVjCZx>MjZpuuu uP֋M3^V]̋UQ3ʼnEWjDZxc>MjZx=t*}@t }u3PPPPuhhDuuuu uP׋M3_V]̋UQQ3ʼnEVWjEZx=MjZxutEEPuuu uP׋Etx$;Es<tuUMjuCLM_3^nU]̋UQ3ʼnEVjFZx3=MjZpiuu uP֋M3^U] ̋UQ3ʼnEVjGZxWu(}$Wu uuuuu uP֋uPujZI_M3^@]$̋UQ3ʼnEVjZ`(upP!t=BtjhpX YYjX>Wu(}$Wu uuuuu uP֋uPujZ虒_M3^F@]$̋UQ3ʼnEVjZ`(upP t=BtjhpX YYjX@33WA蓑}Wu uP33A誑uVujZ_M3^?] ̋UQ3ʼnEVjZ`S'upP> t=BtjhpX YYjX@33WA}Wu uP33AuVujZ7_M3^>] ̋UQ3ʼnEVjZ`&upPt=BtjhpX YYjX2W}Wuuu uP֋uPujZ蕐_M3^B>]̋UQ3ʼnEVjZ`&upPt=BtjhpX YYjX2W}Wuuu uP֋uPujZ_M3^=]jh0Aej Z`d%p33A(e}WP֋uE%uVujZGuA}u33A ̋UQ3ʼnEVj Z`$upPt=BtjhpX YYjXuuuu uP֋M3^<]̋UQ3ʼnEVj Z`C$upP.t=BtjhpX YYjXuuuu uP֋M3^;]̋UQ3ʼnEVj Z`#upPt=BtjhpX YYjXuuuuu uP֋M3^h;]̋UQ3ʼnEVj Z`##upPt=BtjhpX YYjXuuuuu uP֋M3^:]̋UQ3ʼnEVjZ0"pPփ=^t i +HM3w:]̋UQ3ʼnEVj1Z03"uu puP֋M3^$:] ̋UQ3ʼnEVj0Z0!uupu uP֋M3^9]̋UQ3ʼnEVWx!}WpP֋xju3B菏M_3^n9]jhP=ejZ4!p33Aeuu uP֋uE#tjujZu@= u33Aڊ̋UQ3ʼnEVjZ upP֋tMjujZ袎M3^8]̋UQ3ʼnE} tM 3juB`VjZ- u upP֋M3^!8]̋UVW}Wuu uxj7uuA_^]jhp$<e3ҹдp33Aieu uuuuu uP֋uE$tjujZu褉;u33A>jh;e3Bдp33AȈeu uuuuu uP֋uE$tjujZu\;u33A蝈jh:ejZдdp33A(euuuuu uP֋uE$tjujZuf:u33A̋UQ3ʼnEVxupP֋M3^5]̋UQQVWAMjZ}39t @tuPPPPWhVvuPBt*A=BtjhpX YY̸ES] t t3ҋ3A3< Mtt[RRRPShVuWVuuSuLEx#}uuE hWV03jZE[_^]uu9uRRRRRhh9u=t=Bvk̋UQQMSVWjZ`]3u} tEtA@E;t!;t< tJPPRQVh 1uM3VS7B*< EtPPPSWhh~VSWu\Ex!}uu hjV37jZE_^[]̋UQQVWAMjZzM jZo},395t$@tuVVVVWhh~uPt)A95BtjhpX YY̸E S]t tΉu3AM< ttkVVVPShh}u(WVu$u uuuSu u4Ex#}uuE hWV03jZbE[_^](93u95t=Bvu(̋UMVWjZ#M3WWWu jZu u,xu hWWWu jZ_^]̋UQ3ʼnEMVWjZM3WWWu jZjZxTuu puP֋xu hWWWu jZRM_3^%1] ̋U]%(̋U]%0̋Uujhe];}jZ@L@EAuP-t$A=Btj hpX YY3ejujZfMGeuu SMPU܉EEj}ujZt ]}ËaES jhejZ@tpAuPXt$A=Btj hpX YY3EMeu uP֋uE#tjujZuEaűUQ3ʼnEVjZ@MjupjZduP֋M3^]̋UQQ3ʼnESVWjZ@33LujY@Et>f;u^jujZGdEVPUtjXf;ujujZM`M_^3[ ]jh4ej-Z0pMeuu }WP֋uE$tWu3ҋu_ }uj,h ej.Z04@EЋuu3e=l@tE8u VPPVu u}jW3_EEEE؋E̋E̋E܁}ܔtuuUMEEEËe3G}jWu3EWu3ҋbMEuVu uMPUЋ}Eu3utus^u}7Ë^^uj,hHTej/Z0@EЋuu3e=l@tE8u VPPVu u}jW3@_EEEE؋E̋E̋E܁}ܔtuuUMEEEËe3G}jWu3EWu3ҋ-aMXEVu uMPUЋ}E&uuu3ҋ]}o u}jhpejZpMeuP֋uE#tjujZu\uWjhejZxutjujZ`M;eu VP׋uE#tjujZu\Zuj h jZxx}tjujZM_MeuPE UjhЕ* uM<E<+} t?u Gt?uNG@@t$VWaGp$YGp hYjj]eVhW @EEh/Eph$0E0hLYuhXYuhpYh5P3ËeEujuuFp$jZ Yw ̋UQ3ʼnEVWj$Z0}Wupuuu uP<t=}t7~3U@:ju <tuM6jP?`M_3^]̋UQ3ʼnEVj%Z0Cu$u puuuuu uP<t<}t6}~0U@:jRu<tuUMjVM3^] ̋UQ3ʼnEVjZuupu uP֋~#}t<tuU MjV'M3^S]̋UQ3ʼnESVj Zu] upSuPփ<t=~9}t3U@:j+u <tuM6jPM^3[]̋UEPuu u]̋UEPuu u]̋UQ3ʼnEVj`Zxuupu uP֋~#}t<tuU MjVM3^]̋UQ3ʼnESVjaZxu] upSuP֋~&}t <tuM6jP"M^3[M]̋UEPuu u]̋UEPuu u9]̋V3;tVVVRQhhN??W<.9Ht*;u95<tVVVVQhRhN_^Íp̋UQ3ʼnEVjZ0C33ApUP33A(Uvy< tnκu[WjYtAMSj0wSOlGPG?.P@S`[ <_ƋM3^]̋UQ3ʼnESVWjZ0a< Xuutjh0lPu#h0`9=<tG@@4W3JGP>h0`h:(W>h:,uVPӋM_^3[]̋UQ3ʼnESWjZ0< XtR}u@Vjh0Tth0`^u=<t?@4W3}WPӋM_3[]̋UQ3ʼnESVWj Z0< XtO}u=jh0Th0`u95<t%?@4W3.}33A:Ru WP33AWRƋM_^3[R]̋UEс8t%h.MHt졨.+<E B3]; u%̋Uuh j]̋UQQ 5=ff fff%f-EEE jXkǀjXk LjX Lhh j]̋Uj]̋UhEE jXkMhv]̋U=t =N@u hYУ]̋U0VjXE}r)E EEEEЋEeEjhE$EEEEE EEEEE(E܋E؋E;Eu빋EeȋEeME3EME8t E8N@u EO@^]̋U} u3@] %%% ̀@s sË3Ҁ33̋D$L$ ȋL$ u D$S؋D$d$؋D$[SVD$ uL$D$3؋D$ Aȋ\$T$D$ ud$ȋD$r;T$wr;D$ vN3ҋ^[h`d5D$l$l$+SVW1E3PeuEEEEdËMd Y__^[]Qh`d5D$l$l$+SVW1E3ʼnEPeuEEEEdËM3QQL$+ȃ YQL$+ȃ Y̋UVuW} t N3 8FN 3 8_^]̋US] VWE{C3=PWEE}uVyE @futEEus CFFL8Et!SMx~9s tiUMt}뺋}E$t,}{ t!hCPuWE_^[]hCP{ ]SuMӋIH%<%@%DSVWT$D$L$URPQQh@d53ĉD$d%D$0XL$,3p t;T$4t;v.4v\ H {uhCCd_^[ËL$At3D$H3Uhp pp> ]D$T$Ut$L$)qqq( ]UVWS33333[_^]Ëj33333USVWjjhQ _^[]Ul$RQt$ ]̋UP=`td E;Ar;Avj Y)]̋UQ3ʼnEP=`t6? 6`<6H6 X6 h6 !x6!60"6"6#6`#6#6 $7$7$,7@%@7%X7&h7`&|7P'7'. (7p(.(7 )7)7)8P*8*(8+@8p+X8+l80,8,8 -8-8 .8.8.9P/ 9/ 9009`0D90P91d9192929`3949`49490595:5 :P6:6,: 7<:7L:7`:@8t:}:`~:~::y:pz:P:::@;;4;PL;`\;;`;;e;p;;@ <` <8<L<\<l<|<<<@ < < <P<= =8=PH=\=`It=f= =9422= =`2=L2 h2> 4>bL>`cX> Ml>c>pd>K)xE0"`,EDEXEpEдE@E`;E:A0@A@BA"@BBB BC,BPD0e>`f>`9>>>???p$? 0?0@?;T? <l?P=?p>?f?g?i?i??P? @`H@U,@V@@pVP@Vd@PWt@W@X@Y@Z@@@P@@{@{A0[ A[4ApLA`AphlAjxApYA@uAuA wAIAHDD@pTDqhDq|DrDsD@tDtCCCpCCpCI DPJ0DJBPkBkBPlBlBPnBnB@oBot:`|:|:}:}BPmBmCPmDPKDKDL CC,C@%?%@% D%E%F%G%H%I%J%? (#)#*#+#,#-#.#? 2#3#4#5#6#7#8#? <#=#>#?#@#A#B#? F#G#H#I#J#K#L#? P#Q#R#S#T#U#V#? Z#[#\#]#^#_#`#? d#e#f#g#h#i#j#? n#o#p#q#r#s#t#? x#y#z#{#|#}#~# ? ####### ? ####### ? ####### ? ####### ? #######? ?" ? ? ? ? ? ?     ?   P?"@ABCDEF? XYZ[\]^? bcdefgh? lmnopqr? vwxyz{|? ? ? ? ?" ?  ?  ?  ?  ? ? ? ? ? ?  ? ? !"#$%&? *+,-./0? 456789:? >?@ABCD? HIJKLMN? RSTUVWX?"\]^_`ab?"fghijkl? pqrstuv? z{|}~P? pqrstuvQ?"z{|}~R? ? ? ? ? ?"?"?"? ?  ? ?   ? ? ? "#$%&'(? ,-./012? 6789:;<? ? ? ? ? ? Expected least significant bitDN@0   pT@H8P@@0 x8p|(((x8PH8h(0 @`@0<  d( 0 0 ( 0   pT@H8P@@0 zp0p| (( 8PH8hh(0 @`@0<   0$80 ( Ph@0$( ,0  H@`t|LPHLd`d 8@ 0         h0   pT@H8P@@0 x8p|(((h8PH8h(0 @`@ 0< d( 0 0 ( X0    hLP8@0H@@0   @P((h8PH8h(0 @`@ 0< @b( 0 0h<,0 $(0  XPj (0pHLd`d 8@ 0    5   8h@0$( ,0  0@dxLPHLd`d 8@ 0    7    h<,0 $(0  XPj (0pHLd` 0p($    5   X0    hLP8@0H@@0   @P((h8PH8h(0 @`@ 0< @b( 0 Hh@0$( ,0  8@dxLPHLd`d 8@ 0    (7     6Rf<Vp0Jl ,<Xj,>Rh~:Nr,:FR\t~(<Xl:Rl|,Xv*<Hv2BTj(:Rbx` 6Rf<Vp0Jl ,<Xj,>Rh~:Nr,:FR\t~(<Xl:Rl|,Xv*<Hv2BTj(:RbxZRtlDllShutdownInProgressRtlAllocateHeapRtlInitUnicodeString RtlInitializeCriticalSectionNtQueryPerformanceCounterNtQuerySystemTimeRtlCompareUnicodeStringRtlRandom!DbgPrintRtlCaptureStackBackTracesRtlEnterCriticalSectiontRtlLeaveCriticalSectionRtlUpcaseUnicodeCharRtlAcquireSRWLockExclusiveRtlReleaseSRWLockExclusiveRtlAcquireSRWLockSharedRtlReleaseSRWLockSharedNtQueryVirtualMemoryRtlRaiseExceptionNtAllocateVirtualMemoryNtQuerySystemInformationNtQueryEventNtQueryInformationProcessQNtFreeVirtualMemoryRtlFlushSecureMemoryCacheNtProtectVirtualMemoryRtlLookupElementGenericTableAvl0RtlInsertElementGenericTableAvlARtlDeleteElementGenericTableAvlRtlFreeHeapNtOpenEvent,RtlInitializeSRWLock"DbgPrintEx$RtlSetHeapInformation"RtlInitializeCriticalSectionExRtlCreateHeap?RtlDeleteCriticalSectionRRtlDestroyHeap&RtlInitializeGenericTableAvlwRtlEnumerateGenericTableAvlRtlGetUserInfoHeap?RtlSetUserValueHeap>RtlSetUserFlagsHeapRtlLockHeapRtlUnlockHeapNtReadVirtualMemoryFRtlSizeHeapRtlValidateHeapLdrLockLoaderLockLdrUnlockLoaderLockUNtTerminateProcessLdrLoadDllLdrUnloadDllRtlInitAnsiString{LdrGetProcedureAddresskRtlEncodePointer3RtlDecodePointerpLdrFindResource_UdLdrAccessResourceRtlUnicodeStringToAnsiStringRtlFreeAnsiStringLdrQueryImageFileExecutionOptionsLdrQueryImageFileKeyOptionRtlImageNtHeader!RtlSetEnvironmentVariablevNtWriteVirtualMemoryRtlCaptureContextRtlUnhandledExceptionFilterntdll.dllmemmoveg_vsnwprintfe_vsnprintfj_wcsicmpsscanf_swcstoulRtlVerifyVersionInfowcsstrS_stricmp9VerSetConditionMaskRtlQueryHeapInformationNtOpenThreadRtlAddVectoredExceptionHandlerRtlEqualUnicodeStringRNtSuspendThreadtLdrGetDllHandleFRtlDeleteResourceRtlAcquireResourceShared+NtDelayExecutionRtlAcquirePebLockRtlReleaseResourceNtClose*RtlInitializeResourceRtlAcquireResourceExclusiveRtlRemoveVectoredExceptionHandlerNtQueryInformationThreadLdrQueryProcessModuleInformationRtlNtStatusToDosErrorRtlFindClearBitsAndSetNtQueryObjectRtlReleasePebLock NtResumeThreadmLdrFindEntryForAddress;RtlInterlockedPushEntrySList[RtlSplay:RtlDelete+RtlInitializeSListHeadRtlpWaitForCriticalSection!RtlInitializeCriticalSectionAndSpinCount|RtlTryEnterCriticalSectionRtlConvertExclusiveToSharedRtlRaiseStatusRtlConvertSharedToExclusive:RtlInterlockedPopEntrySListRtlQueryDepthSListNtCreateEventLRtlDeregisterWait NtSetEventRtlRegisterWaitiswspacezRtlEnumerateGenericTableWithoutSplayingAvlm_wcsnicmpNtOpenProcessTokenExRtlAppendUnicodeStringToStringRtlAppendUnicodeToStringNtOpenKeyRtlConvertSidToUnicodeStringNtQueryInformationToken3NtDeleteValueKeyGNtSetValueKeyNtQueryValueKeyWNtGetContextThreadMRtlDeregisterWaitExRtlWalkFrameChainNtClearEvent7RtlSetThreadPoolStartFuncRtlCheckForOrphanedCriticalSectionslNtWaitForMultipleObjectsNtCreateKeynNtWaitForSingleObjectNtCreateSectiondNtUnmapViewOfSectionNtOpenSection|NtMapViewOfSectionRtlFreeUnicodeStringmemcpymemset'_alloca_probeRtlUnwind S( @Xp0H`x 8Ph(9@:X;p<=xy0H`x 8Ph345 6( 7@ 8X 9p : ; < R S T U 0 H ` x                  0  @  P  `  p                        0  @  P  `  p                        0  @  P  `  p                      0 @ P ` p             0 @ P ` p        xP(`d2,H :P(@#%f`(X* 6 8CnT( `h"nXvf h0v   0P.`>@*"6  %^ 28"@F R[r(aglu>}T  ȌdH>rlp FhRX(8`4VS_VERSION_INFO 98 98?"StringFileInfo040904B0LCompanyNameMicrosoft Corporation~+FileDescriptionStandard application verifier provider dlln'FileVersion10.0.14393.0 (rs1_release.160715-1616): InternalNameverifier.dll.LegalCopyright Microsoft Corporation. All rights reserved.B OriginalFilenameverifier.dllj%ProductNameMicrosoft Windows Operating System> ProductVersion10.0.14393.0DVarFileInfo$Translation <AVRF: Terminate process after verifier stop failed with %X kThis verifier stop is not continuable. Process will be terminated when you use the `go' debugger command. LThis verifier stop is continuable. After debugging it use `go' to continue. 9AVRF: Formatting message failed in VerifierStopMessageEx LAVRF: Noncontinuable verifier stop %p encountered. Terminating process ... ======================================= VERIFIER STOP %p: pid 0x%X: %S %p : %S %p : %S %p : %S %p : %S %S ======================================= %S ======================================= ======================================= VERIFIER STOP %p: pid 0x%X: %s %p : %s %p : %s %p : %s %p : %s %s ======================================= %s ======================================= FullDllsSize SizeStartSizeEndRandRateBackwardUnalignTracesProtectNoSyncNoLockFaults FaultRateTimeOutAddr AddrStartAddrEndRandom4TRUE for full page heap. FALSE for normal page heap.iPage heap allocations for target dlls only. Name of the binaries with extension (.dll or something else).%Page heap allocations for size range.Beginning of the size range.Ending of the size range.uDecimal integer in range [0..100] representing probability to make page heap allocation vs. a normal heap allocation.Catch backwards overruns.No alignment for allocations.Collect stack tracescProtect heap internal structures. Can be used to detect random corruptions but execution is slower.LCheck for unsynchronized access. Do not use this flag for an MPheap process."Disable critical section verifier.Fault injection.Probability (1..10000) for heap calls failuresQTime during process initialization (in milliseconds) when faults are not allowed.'Page heap allocations for address rangeBeginning of the address rangeEnding of the address range'Page heap allocations with probability.DFailed within the address range where the specified dlls are loaded.Doesn't fail within those dlls.Grace period as Milliseconds. Wait API.Heap allocation.Virtual memory allocation. Registry API. File API.Event Manipulation. Map View.Ole API."Disable automatic stack expansion.Traces6Maximum number of traces in the handle history buffer.Delay"Delay until rollover in (seconds). AsyncCheck9Check asynchronous calls that require a persistent thread DllMainCheck<Check LoadLibrary/FreeLibrary calling when DllMain is active ExecWritePage4Checking the usage of executable and writable memoryFillReadBuffereFills I/O buffer with a pattern before initiating the I/O, to catch bugs around uninitialized buffersForcePendingIOVProbability in parts per million for forcing STATUS_PENDING in place of STATUS_SUCCESS ExcludeDllsUExcludes these dlls (comma separated) from leak detection. Max size is 255 charactersChecks for errors in lock usage. This might cause access violations when errors are located. A debugger is required to see the test results.Checks that applications and components use RPC correctly. Common mistakes and problems while using RPC are flagged. A debugger is required to see the test results.Checks that applications and components use COM correctly. Common mistakes and problems while using COM are flagged. A debugger is required to see the test results.Checks that applications and components use TLS (Thread Local Storage) APIs correctly. Common mistakes and problems while using TLS APIs are flagged. A debugger is required to see the test results.#Helps catch uninitialized variablesaDetects first chance access violation exceptions. A debugger is required to see the test results.Checks for handle errors. This might cause access violations when errors are located. A debugger is required to see the test results.GChecks the heap errors. A debugger is required to see the test results.Checks for adequate stack size by stopping stack growth. This causes a stack overflow error if the original stack size is too small. You can prevent this from happening by increasing the stack commit size.TChecks usage of virtual memory APIs. A debugger is required to see the test results.$Checks usage of dangerous API usage.Forces the GetTickCount API to roll over faster than they normally would. This allows applications to test their handling of timer rollover more easily.GChecks for dirty threadpool thread and other threadpool related issues.Low Resource Simulation also known as Fault Injection, tries to simulate an environment under low resources, such as out of memory.'Checks issues related to I/O transfers.VChecks that when a dll is unloaded there are no outstanding resources allocated by it.Checks for errors in SRW locks usage. Invalid SRW lock usage can result in application crashes or hangs. A debugger is required to see the test results."Dangerous call to TerminateThread.,Thread ID for the caller of Terminatethread. Not used. Not used. Not used.This stop is generated if a thread (thread ID is parameter1) is terminated explicitly using TerminateThread.This function is very dangerous because it introduces data corruption and deadlocks (as per MSDN).2Potential stack overflow in low memory conditions. Not used. Not used. Not used. Not used.This stop is generated if the initial stack commit size of a thread is such that a stack overflow can be raised in low memory conditions if stack cannot be extended.8ExitProcess called while multiple threads still running.Number of threads running. Not used. Not used. Not used.This stop is generated if a thread calls ExitProcess while there are several threads running. In such a case, internally TerminateThread will be called for each thread and this can create deadlocks or data corruptions.%LoadLibrary is called during DllMain.Dll Name (use du to dump).Dll base address. Not used. Not used.xThis stop is generated if the code inside DllMain calls LoadLibrary or FreeLibary. It's the behavior forbidden by MSDN.%FreeLibrary is called during DllMain.Dll Name (use du to dump).Dll base address. Not used. Not used.xThis stop is generated if the code inside DllMain calls LoadLibrary or FreeLibary. It's the behavior forbidden by MSDN.KSetProcessWorkingSetSize is called with MinimumWorkingSetSize = 0xFFFFFFFF. Not used. Not used. Not used. Not used./Please use MinimumWorkingSetSize = (SIZE_T) -1.KSetProcessWorkingSetSize is called with MaximumWorkingSetSize = 0xFFFFFFFF. Not used. Not used. Not used. Not used./Please use MaximumWorkingSetSize = (SIZE_T) -1.MSetProcessWorkingSetSizeEx is called with MinimumWorkingSetSize = 0xFFFFFFFF. Not used. Not used. Not used. Not used./Please use MinimumWorkingSetSize = (SIZE_T) -1.MSetProcessWorkingSetSizeEx is called with MaximumWorkingSetSize = 0xFFFFFFFF. Not used. Not used. Not used. Not used./Please use MaximumWorkingSetSize = (SIZE_T) -1./Thread that is exiting owns a critical section.HThread ID of the thread that is exiting while owning a critical section.GCritical section address. Run !cs -s <address> to get more information.+Critical section debug information address.WCritical section initialization stack trace. Run dps <address> to dump the stack trace.This stop is generated if a thread (thread ID is parameter1) is terminated, suspended or is in a state (worker thread finished a work item) in which it cannot hold a critical section. The current thread is the culprit. To debug this stop use the following debugger commands: $ kb - to get the current stack trace. If the current thread is the owner of the critical section it is probably calling ExitThread. The current thread should have released the critical section before exiting. If the current thread is calling TerminateThread or SuspendThread then it should not do this for a thread holding a critical section. $ !cs -s parameter2 - dump information about this critical section. $ ln parameter2 - to show symbols near the address of the critical section. This should help identify the leaked critical section. $ dps parameter4 - to dump the stack trace for this critical section initialization.4Unloading DLL containing an active critical section.GCritical section address. Run !cs -s <address> to get more information.WCritical section initialization stack trace. Run dps <address> to dump the stack trace.DLL name address.DLL base address.This stop is generated if a DLL has a global variable containing a critical section and the DLL is unloaded but the critical section has not been deleted. To debug this stop use the following debugger commands: $ du parameter3 - to dump the name of the culprit DLL. $ .reload dllname or .reload dllname = parameter4 - to reload the symbols for that DLL. $ !cs -s parameter1 - dump information about this critical section. $ ln parameter1 - to show symbols near the address of the critical section. This should help identify the leaked critical section. $ dps parameter2 - to dump the stack trace for this critical section initialization.9Freeing heap block containing an active critical section.GCritical section address. Run !cs -s <address> to get more information.WCritical section initialization stack trace. Run dps <address> to dump the stack trace.Heap block address.Heap block size.This stop is generated if a heap allocation contains a critical section, the allocation is freed and the critical section has not been deleted. To debug this stop use the following debugger commands: $ !cs -s parameter1 - dump information about this critical section. $ ln parameter1 - to show symbols near the address of the critical section. This should help identify the leaked critical section. $ dps parameter2 - to dump the stack trace for this critical section initialization. $ parameter3 and parameter4 might help understand where this heap block was allocated (the size of the allocation is probably significant).1Double initialized or corrupted critical section.GCritical section address. Run !cs -s <address> to get more information.DAddress of the debug information structure found in the active list.LFirst initialization stack trace. Run dps <address> to dump the stack trace.MSecond initialization stack trace. Run dps <address> to dump the stack trace.Usually this stop is generated if a critical section has been initialized more than one time. In this case parameter3 and parameter4 are the stack trace addresses for two of these initializations. Some other times it is possible to get this stop if the critical section or its debug information structure has been corrupted. In this second case it is possible that parameter3 and parameter4 are invalid and useless. To debug this stop: $ !cs -s -d parameter2 - dump information about this critical section. $ ln parameter1 - to show symbols near the address of the critical section. This might help identify the critical section if this is a global variable. $ dps parameter3 and dps parameter4 - to identify the two code paths for initializing this critical section.2Free memory containing an active critical section.GCritical section address. Run !cs -s <address> to get more information.+Critical section debug information address.WCritical section initialization stack trace. Run dps <address> to dump the stack trace. Not used.This stop is generated if the memory containing a critical section was freed but the critical section has not been deleted using DeleteCriticalSection. To debug this stop use the following debugger commands: $ !cs -s -d parameter2 - dump information about this critical section. $ dps parameter3 - to identify the code path for initializing this critical section. In most cases the lock verifier detects immediately leaked critical sections contained in a heap allocation, a DLL range, a virtual memory allocation or a MapViewOfFile mapped memory range and issues different stops in these cases. So there are very few cases left for this verifier stop. The lock must be in a memory range freed by kernel-mode code or freed cross-process by APIs like VirtualFreeEx. Most typically this stop will be encountered if a previous stop (e.g. LOCK_IN_FREED_HEAP or LOCK_IN_UNLOADED_DLL) was continued by hitting `g' in the debugger console.Corrupted critical section.GCritical section address. Run !cs -s <address> to get more information.;Invalid debug information address of this critical section.:Address of the debug information found in the active list.FInitialization stack trace. Run dps <address> to dump the stack trace.UThis stop is generated if the DebugInfo field of the critical section is pointing freed memory. Usually another valid DebugInfo structure is found in the active critical section list. Without corruption the two pointers should be identical. To debug this stop use the following debugger commands: $ !cs -s -d parameter3 - dump information about this critical section based on the current contents of the debug info structure found in the active list (this structure is rarely corrupted so usually this information is trustworthy). $ !cs -s parameter1 - dump information about this critical section based on the current contents of the critical section structure (the structure is corrupted already so sometimes this information is NOT trustworthy). $ dps parameter4 - to identify the code path for initializing this critical section. Dump the critical section at address parameter1 and look for the corruption pattern. With good symbols for ntdll.dl you can use the following commands: $ dt ntdll!_RTL_CRITICAL_SECTION LOCK_ADDRESS $ dt ntdll!_RTL_CRITICAL_SECTION_DEBUG DEBUG_ADDRESS&Invalid critical section owner thread.GCritical section address. Run !cs -s <address> to get more information.Owning thread.Expected owning thread.$Critical section debug info address.This stop is generated if the owner thread ID is invalid in the current context. For example, the critical section is being released by a thread other than the one that acquired it. To debug this stop: $ !cs -s parameter1 - dump information about this critical section. $ ln parameter1 - to show symbols near the address of the critical section. This should help identify the critical section.)Invalid critical section recursion count.GCritical section address. Run !cs -s <address> to get more information.Recursion count.Expected recursion count.$Critical section debug info address.TThis stop is generated if the recursion count field of the critical section structure is invalid in the current context. To debug this stop: $ !cs -s parameter1 - dump information about this critical section. $ ln parameter1 - to show symbols near the address of the critical section. This should help identify the critical section.2Deleting critical section with invalid lock count.GCritical section address. Run !cs -s <address> to get more information. Lock count.Expected lock count.Owning thread.This stop is generated if a critical section is owned by a thread if it is deleted or if the critical section is uninitialized. To debug this stop: $ !cs -s parameter1 - dump information about this critical section. If the owning thread is 0 the critical section has not been initialized. $ ln parameter1 - to show symbols near the address of the critical section. This should help identify the critical section.,Critical section over-released or corrupted.GCritical section address. Run !cs -s <address> to get more information. Lock count.Expected lock count.$Critical section debug info address.This stop is generated if a critical section is released more times than the current thread acquired it. To debug this stop: $ !cs -s parameter1 - dump information about this critical section. $ !cs -s -d parameter4 - dump information about this critical section. $ ln parameter1 - to show symbols near the address of the critical section. This should help identify the critical section.!Critical section not initialized.GCritical section address. Run !cs -s <address> to get more information.$Critical section debug info address. Not used. Not used.This stop is generated if a critical section is used without being initialized or after it has been deleted. To debug this stop: $ ln parameter1 - to show symbols near the address of the critical section. This should help identify the critical section.(Critical section is already initialized.GCritical section address. Run !cs -s <address> to get more information.$Critical section debug info address.AFirst initialization stack trace. Use dps to dump it if non-NULL. Not used.(This stop is generated if a critical section is reinitialized by the current thread. To debug this stop: $ !cs -s parameter1 or !cs -s -d parameter2 - dump information about this critical section. $ ln parameter1 - to show symbols near the address of the critical section. This might help identify the critical section if this is a global variable. $ dps parameter3 - to identify the code path for the first initialization of this critical section. $ kb - to display the current stack trace, that is reinitializing this critical section.=Freeing virtual memory containing an active critical section.GCritical section address. Run !cs -s <address> to get more information.LCritical section initialization stack trace. Use dps to dump it if non-NULL.Memory block address.Memory block size.This stop is generated if the current thread is calling VirtualFree on a memory block that contains an active critical section. The application should call DeleteCriticalSection on this critical section before if frees this memory. $ kb - to display the current stack trace, that is calling VirtualFree. The probable culprit is the DLL that calls VirtualFree. $ !cs -s parameter1 - dump information about this critical section. $ dps parameter2 - to identify the code path for the initialization of this critical section.>Unmapping memory region containing an active critical section.GCritical section address. Run !cs -s <address> to get more information.LCritical section initialization stack trace. Use dps to dump it if non-NULL.Memory block address.Memory block size.$This stop is generated if the current thread is calling UnmapViewOfFile on a memory block that contains an active critical section. The application should call DeleteCriticalSection on this critical section before if unmaps this memory. $ kb - to display the current stack trace, that is calling UnmapViewOfFile . The probable culprit is the DLL that calls UnmapViewOfFile. $ !cs -s parameter1 - dump information about this critical section. $ dps parameter2 - to identify the code path for the initialization of this critical section.2Current thread does not own any critical sections.GCritical section address. Run !cs -s <address> to get more information.4Number of critical sections owned by current thread.Not usedNot used,This stop is generated if the current thread is calling LeaveCriticalSection but, according to the internal verifier bookkeeping, it doesn't own any critical section. If parameter2 is zero, probably this is a bug in the current thread. It either tries to leave a critical section that it didn't enter, or maybe it is calling LeaveCriticalSection more times than it called EnterCriticalSection for the same critical section. If parameter2 is not zero (it is a negative integer number) the internal verifier data structures are probably corrupted.6Using critical section that is private to another DLL.GCritical section address. Run !cs -s <address> to get more information. Not used.Not usedNot usedThis stop is generated if the current thread tries to use a private lock that lives inside another DLL. For example a.dll tries to enter a critical section defined inside ntdll.dll. Private locks cannot be used across DLLs. The SRW Lock is not initialized.SRW LockNot usedNot usedNot used This stop is generated if a thread is trying to use the SRW lock (Param1) that is not initialized. $ kb - to get the current stack trace. This is where the SRW lock is being used. The SRW lock should be initialized using InitializeSRWLock before it can be used.$The SRW Lock is already initialized.SRW Lock5ThreadId of the thread that initialized the SRW lock.gAddress of the initialization stack trace. Use dps <address> to see where the SRW lock was initialized.Not usedDThis stop is generated if the SRW lock (Param1) is being re-initialized. If the SRW lock is being actively used by other threads, re-initializing the lock will result in unpredictable behavior by the application including hangs and crashes. The initialization stack trace may show an acquire if the SRW lock was statically initialized. $ kb - to get the current stack trace. This is where the SRW lock is being re-initialized. $ dps Param3 - to get the SRW lock initialization stack trace. This stack trace may show an acquire if the lock was statically initialized.+Mismatched Acquire-Release on the SRW lock.SRW Lock2ThreadId of the thread that acquired the SRW lock.]Address of the acquire stack trace. Use dps <address> to see where the SRW lock was acquired.Not used.This stop is generated if the SRW lock (Param1) is being released with a wrong release API. If the SRW lock was acquired for shared access and is being released using the exclusive release API or the SRW lock was acquired for exclusive access and is being release using the shared release API. This can result in unpredictable behavior by the application including hangs and crashes. $ kb - to get the current stack trace. This is where the SRW lock is being released using the wrong API. $ dps Param3 - to get the SRW lock acquire stack trace.>The SRW lock is being acquired recursively by the same thread.SRW LockcAddress of the first acquire stack trace. Use dps <address> to see where the SRW lock was acquired.Not usedNot used This stop is generated if the SRW lock (Param1) is being acquired recursively by the same thread. This will result in a deadlock and the thread would block indefinitely. Recursive acquisition of an SRW lock in exclusive mode will cause a deadlock. Recursive acquisition of an SRW lock in shared mode will cause a deadlock when there is a thread waiting for exclusive access. Consider the example below: - Thread A acquires the SRW lock in shared mode - Thread B tries to acquire the SRW lock in exclusive mode and waits - Thread A tries to acquire the SRW lock in shared mode recursively. This will be successful as long as there is no exclusive waiter (in this case B). Since SRW locks do not have writer starvation, thread A waits behind thread B. Now, Thread B is waiting for Thread A which is inturn waiting for Thread B causing a circular wait and hence a deadlock. $ kb - to get the current stack trace. This is where the SRW lock is being acquired recursively. $ dps Param2 - to get the stack trace for the first acquire.@The thread that is exiting or being terminated owns an SRW lock.SRW Lock;ThreadId of the thread that is exiting or being terminated.]Address of the acquire stack trace. Use dps <address> to see where the SRW lock was acquired.Not usedThis stop is generated if the thread (Param2) that owns the SRW lock (Param1) is exiting or being terminated. This will result in an orphaned SRW lock and the threads trying to acquire this lock would block indefinitely. $ kb - to get the current stack trace. This is where the thread is exiting or is being terminated. $ dps Param3 - to get the SRW lock acquire stack trace.<The SRW lock being released was not acquired by this thread.SRW LockCurrent ThreadId.2ThreadId of the thread that acquired the SRW lock.]Address of the acquire stack trace. Use dps <address> to see where the SRW lock was acquired.This stop is generated if the SRW lock (Param1) is being released by the thread (Param2) that didn't acquire the lock. This represents bad programming practice that is hard to get right and can lead to unpredictable behavior by the application. $ kb - to get the current stack trace. This is where the thread is releasing the SRW lock that it didn't acquire. $ dps Param4 - to get the SRW lock acquire stack trace.3The memory being freed contains an active SRW lock.SRW Lock"Address of the memory being freed.2ThreadId of the thread that acquired the SRW lock.]Address of the acquire stack trace. Use dps <address> to see where the SRW lock was acquired.This stop is generated if the memory address (Param1) being freed contains an active SRW lock that is still in use. This can result in unpredictable behavior by the application including crashes and hangs. $ kb - to get the current stack trace. This is where the memory is being freed that contains an active SRW lock. $ dps Param4 - to get the SRW lock acquire stack trace.3The DLL being unloaded contains an active SRW lock.SRW LockPAddress of the name of the DLL being unloaded. Use du <address> to see the name.2ThreadId of the thread that acquired the SRW lock.]Address of the acquire stack trace. Use dps <address> to see where the SRW lock was acquired.This stop is generated if the DLL being unloaded (Param2) contains an active SRW lock (Param1) that is still in use. This can result in unpredictable behavior by the application including crashes and hangs. $ kb - to get the current stack trace. This is where the DLL is being unloaded that contains an active SRW lock. $ du Param2 - to find the name of the DLL that is being unloaded. $ dps Param4 - to get the SRW lock acquire stack trace.1Invalid handle exception for current stack trace.Exception code.)Exception record. Use .exr to display it.'Context record. Use .cxr to display it. Not used.This stop is generated if the function on the top of the stack passed an invalid handle to system routines. Usually a simple kb command will reveal what is the value of the handle passed (must be one of the parameters - usually the first one). If the value is null then this is clearly wrong. If the value looks ok you need to use !htrace debugger extension to get a history of operations pertaining to this handle value. In most cases it must be that the handle value is used after being closed./Invalid TLS index used for current stack trace.Invalid TLS index.!Expected lower part of the index. Not used. Not used.This stop is generated if the function on the top of the stack passed an invalid TLS index to TLS system routines. Usually a simple kb command will reveal what is wrong. The typical bug here is to assume a certain value for a TLS index instead of calling TlsAlloc. This can happen either by thinking that you always get value N therefore there is no need to call TlsAlloc or more frequently due to an uninitialized variable.3Invalid parameters for WaitForMultipleObjects call.!Address of object handles vector.Number of handles. Not used. Not used.This stop is generated if the function on the top of the stack called WaitForMultipleObjects with NULL as the address of the array of handles to wait for or with zero as the number of handles. A simple kb command will reveal the function calling this API incorrectly.=NULL handle passed as parameter. A valid handle must be used. Not used. Not used. Not used. Not used.hThis stop is generated if the function on the top of the stack passed a NULL handle to system routines.&Waiting on a thread handle in DllMain.Thread handle. Not used. Not used. Not used.This stop is generated if the current thread is currently running code inside the DllMain function of one of the DLLs loaded in the current process and it calls WaitForSingleObject or WaitForMultipleObjects to wait on a thread handle in the same process. This would most likely lead to a deadlock because the thread handle will not get signaled unless that second thread is exiting. When the second thread will call ExitThread it will try to acquire the DLL loader lock then call DllMain (DLL_THREAD_DETACH) for all DLLs in the current process. But the loader lock is owned by the first thread (the one that is waiting on the thread handle) so the two threads will deadlock.!Incorrect object type for handle. Handle value.&Object type name. Use du to display it/Expected object type name. Use du to display it Not used.This stop is generated if the current thread is calling an API with a handle to an object with an incorrect object type. E.g. calling SetEvent with a semaphore handle as parameter will generate this stop. To debug this stop: $ kb - to display the current stack trace. The culprit is probably the DLL that is calling into verifier.dll; $ du parameter2 - to display the actual type of the handle. The handle value is parameter1. In the example above, this will display: Semaphore. $ du parameter3 - to display the object type expected by the API. In the example above, this name will be: Event. $ !htrace parameter1 might be helpful because it will display the stack trace for the recent open/close operations on this handle.:Unloading DLL that allocated TLS index that was not freed. TLS index2Address of the code that allocated this TLS index.$DLL name address. Use du to dump it.DLL base address.This stop is generated if a DLL that allocated a TLS index is being unloaded before freeing that TLS index. To debug this stop: $ du parameter3 - display the name of the culprit DLL; $ .reload xxx.dll=parameter4 - reload symbols for the culprit DLL (if needed). xxx.dll is the name of the DLL displayed in the above step; $ u parameter2 - disassemble the code that allocated the TLS. This should point to the function that allocated the TLS but forgot to free it before the DLL was unloaded.!Corrupted verifier TLS structure. TEB address.Expected TEB address. Thread ID.Expected thread ID.This stop is generated if the internal verifier structures used to store the state of TLS slots for thread are corrupted. Very likely this is due to some random corruption in the process.Using an invalid TLS index. TLS index Not Used. Not Used. Not Used.\This stop is generated if an invalid TLS index is used. In most cases, it's because code is still using this index when TlsFree is called. Here is an example for the threadpool thread. T1: Dll loads and TlsAlloc T1: Queue callback T1: Skipped waited/cancelled callback T1: TlsFree T2: Callback runs and calls TlsSetValue T1: Dll unloads@Freeing virtual memory block with invalid size or start address.Allocation base address.Memory region size. Not used. Not used.This stop is generated if the app verifier detects a VirtualFree or a DLL unload with an invalid start address or size of the memory allocation. In the case of DLL unload this probably means a memory corruption inside the loaded DLL list. To debug this stop look at the current stack trace and the memory address and size that is about to be freed and try to determine why they are invalid.Incorrect virtual alloc call.#Pointer to allocation base address.Pointer to memory region size.Not usedNot used*This stop is generated if the app verifier detects a VirtualAlloc call with an invalid start address or size of the memory allocation. To debug this stop look at the current stack trace (kb) and the memory address and size that is about to be allocated and try to determine why they are invalid.Incorrect map view call. Pointer to mapping base address.Pointer to view size. Not used. Not used.This stop is generated if the app verifier detects a MapViewOfFile call with an invalid base address or size of the mapping. To debug this stop look at the current stack trace (kb) and the memory address and size that is about to be mapped and try to determine why they are invalid.Probing invalid address.Start address.Memory block size.Invalid address. Not used.This stop is generated if the app verifier detects an IsBadXXXPtr call with an invalid address (e.g. a kernel-mode address, instead of a normal user-mode address) for the memory buffer to be probed. To debug this stop look at the current stack trace (kb) and try to determine why the caller of the IsBadXXXPtr function ended up with an invalid address. Many times, the address is plain bogus, e.g. an uninitialized pointer. MSDN library lists a few reasons why applications should not use the IsBadXXXPtr APIs: In a preemptive multitasking environment, it is possible for some other thread to change the process's access to the memory being tested. Dereferencing potentially invalid pointers can disable stack expansion in other threads. A thread exhausting its stack, when stack expansion has been disabled, results in the immediate termination of the parent process, with no pop-up error window or diagnostic information. Threads in a process are expected to cooperate in such a way that one will not free memory that the other needs. Use of this function does not negate the need to do this. If this is not done, the application may fail in an unpredictable manner. Because of all these reasons, we recommend to never use these APIs.Probing free memory.Start address.Memory block size.Address of free memory page. Not used.This stop is generated if the app verifier detects an IsBadXXXPtr call for a memory allocation that is free. This is very bad because it is possible that, in some other cases, this memory was already reused for some other allocation. Since the current code path (kb) doesn't own that memory, it could end up corrupting someone else's memory, with disastrous effects. To debug this stop look at the current stack trace (kb) and try to determine why the caller of the IsBadXXXPtr function ended up probing free memory. The address could be plain bogus (e.g. uninitialized pointer) or maybe already freed memory. If the memory was already freed by one of the VirtualFree or UnmapViewOfFile APIs, `!avrf -vs -a parameter3' will search for a log of stack traces of the code paths that allocated/freed that address and display these stack traces if they are available. This might show the stack trace that freed up this memory. More often, the memory is an already freed heap allocation. To check for that possibility, `!avrf -hp -a parameter3' will search for a log of stack traces of the code paths that allocated/freed that address from/to the heap and display these stack traces if they are available. MSDN library lists a few reasons why applications should not use the IsBadXXXPtr APIs: In a preemptive multitasking environment, it is possible for some other thread to change the process's access to the memory being tested. Dereferencing potentially invalid pointers can disable stack expansion in other threads. A thread exhausting its stack, when stack expansion has been disabled, results in the immediate termination of the parent process, with no pop-up error window or diagnostic information. Threads in a process are expected to cooperate in such a way that one will not free memory that the other needs. Use of this function does not negate the need to do this. If this is not done, the application may fail in an unpredictable manner. Because of all these reasons, we recommend to never use these APIs.Probing a guard page.Start address.Memory block size.Address of guard page. Not used. This stop is generated if the app verifier detects an IsBadXXXPtr call for a memory allocation that contains at least one GUARD_PAGE. This is very bad because it is very possible that this GUARD_PAGE is the end of the current stack of a thread. As documented in the MSDN library: Dereferencing potentially invalid pointers can disable stack expansion in other threads. A thread exhausting its stack, when stack expansion has been disabled, results in the immediate termination of the parent process, with no pop-up error window or diagnostic information. To debug this stop look at the current stack trace (kb) and try to determine why the caller of the IsBadXXXPtr function ended up probing a GUARD_PAGE. MSDN library lists a few reasons why applications should not use the IsBadXXXPtr APIs: In a preemptive multitasking environment, it is possible for some other thread to change the process's access to the memory being tested. Dereferencing potentially invalid pointers can disable stack expansion in other threads. A thread exhausting its stack, when stack expansion has been disabled, results in the immediate termination of the parent process, with no pop-up error window or diagnostic information. Threads in a process are expected to cooperate in such a way that one will not free memory that the other needs. Use of this function does not negate the need to do this. If this is not done, the application may fail in an unpredictable manner. Because of all these reasons, we recommend to never use these APIs.Probing NULL address. Not used. Not used. Not used. Not used.oThis stop is generated if the app verifier detects an IsBadXXXPtr call with a NULL address. To debug this stop look at the current stack trace (kb) and try to determine why the caller of the IsBadXXXPtr function ended up with the NULL address. This is typically the sign of someone not checking the return value of one of the memory allocation functions. For example the code below is incorrect: int main (void) { PVOID p; p = malloc (1024); Use (p); return 0; } void Use (PVOID p) { if (IsBadReadPtr (p)) { return; } // // p is safe to be used here. // } This code should be re-written as this: int main (void) { PVOID p; p = malloc (1024); if (NULL == p)) { return -1; } Use (p); return 0; } void Use (PVOID p) { // // p is safe to be used here. // } MSDN library lists a few reasons why applications should not use the IsBadXXXPtr APIs: In a preemptive multitasking environment, it is possible for some other thread to change the process's access to the memory being tested. Dereferencing potentially invalid pointers can disable stack expansion in other threads. A thread exhausting its stack, when stack expansion has been disabled, results in the immediate termination of the parent process, with no pop-up error window or diagnostic information. Threads in a process are expected to cooperate in such a way that one will not free memory that the other needs. Use of this function does not negate the need to do this. If this is not done, the application may fail in an unpredictable manner. Because of all these reasons, we recommend to never use these APIs.8Probing memory block with invalid start address or size.Start address.Memory block size. Not used. Not used.This stop is generated if the app verifier detects an IsBadXXXPtr call with an invalid start address (e.g. a kernel-mode address, instead of a normal user-mode address) or invalid size for the memory buffer to be probed. To debug this stop look at the current stack trace (kb) and try to determine why the caller of the IsBadXXXPtr function ended up with an invalid address or size. Many times, the address or size are plain bogus, e.g. an uninitialized variables. MSDN library lists a few reasons why applications should not use the IsBadXXXPtr APIs: In a preemptive multitasking environment, it is possible for some other thread to change the process's access to the memory being tested. Dereferencing potentially invalid pointers can disable stack expansion in other threads. A thread exhausting its stack, when stack expansion has been disabled, results in the immediate termination of the parent process, with no pop-up error window or diagnostic information. Threads in a process are expected to cooperate in such a way that one will not free memory that the other needs. Use of this function does not negate the need to do this. If this is not done, the application may fail in an unpredictable manner. Because of all these reasons, we recommend to never use these APIs.1Unloading DLL with invalid size or start address.DLL memory base address.DLL memory range size.$DLL name address. Use du to dump it. Not used.This stop is generated if the app verifier detects a DLL unload with an invalid start address or size of the DLL memory range. This probably means a memory corruption inside the internal ntdll.dll loaded DLL list.AFreeing memory block inside current thread's stack address range.Allocation base address.Memory region size.Stack low limit address.Stack high limit address.This stop is generated if the app verifier detects a VirtualFree for a block of memory that is actually part of the current thread's stack (!). To debug this stop look at the current stack trace (kb) and try to understand why the function that called VirtualFree thought that the memory block was dynamically allocated or mapped but that was actually memory allocated from the stack.7Incorrect FreeType parameter for VirtualFree operation.(Incorrect value used by the application.Expected correct value 1.Expected correct value 2. Not used.This stop is generated if the app verifier detects a VirtualFree with an incorrect value for the FreeType parameter. The only two acceptable values for this parameter are MEM_DECOMMIT and MEM_RELEASE. If VirtualFree is called with any other value except these two, VirtualFree will fail to free the memory. To debug this stop look at the current stack trace (kb): the caller of VirtualFree is probably the culprit.9Trying to free virtual memory block that is already free.Memory block address. Not used. Not used. Not used.This stop is generated if the app verifier detects a VirtualFree for an address that is already free. To debug this stop look at the current stack trace (kb) and try to determine why the memory is already free but the application is trying to free it again. `!avrf -vs -a parameter1' will search for a log of stack traces of the code paths that allocated/freed that address and display these stack traces if they are available. This might show the stack trace that freed up this memory.AIncorrect Size parameter for VirtualFree (MEM_RELEASE) operation.'Incorrect size used by the application.Expected correct size (0). Not used. Not used.This stop is generated if the app verifier detects a VirtualFree (MEM_RELEASE) with a non-zero value for the dwSize parameter. When using MEM_RELEASE , the only acceptable value for this parameter is 0. If VirtualFree is called with any other value except 0, VirtualFree will fail to free the memory. To debug this stop look at the current stack trace (kb): the caller of VirtualFree is probably the culprit.7Unexpected exception raised in DLL entry point routine.DLL name (use du to dump it).)Exception record. Use .exr to display it.'Context record. Use .cxr to display it.Verifier dll descriptorThis stop is generated if a DLL's entry point (DllMain) function is raising an exception. One example why this is bad is: if DllMain(DLL_PROCESS_ATTACH) is raising an exception, the Windows DLL loader will: - Catch and hide the exception; - Unload the DLL without calling its DllMain(DLL_PROCESS_DETACH). So in many cases the DLL allocated some resources already, then it raised the exception, and it will not have a chance to release these resources on DllMain (DLL_PROCESS_DETACH). To debug this stop: $ du parameter1 - to display the DLL name; $ .exr parameter2 - to display the exception information; $ .cxr parameter3 followed by kb - to display the exception context information and the stack trace for the time when the exception was raised; $ parameter4 is the address of an internal verifier structure and doesn't have any significance for most of the verifier users./Unexpected exception raised in thread function.Exception code.)Exception record. Use .exr to display it.'Context record. Use .cxr to display it. Not used.This stop is generated if a thread function is raising an exception. This is bad because the whole process will be killed. To debug this stop: $ parameter1 might be significant for the type of exception. E.g. an exception code C0000005 means Access Violation; $ .exr parameter2 - to display the exception information; $ .cxr parameter3 followed by kb - to display the exception context information;1Unexpected exception raised while probing memory.Exception code.)Exception record. Use .exr to display it.'Context record. Use .cxr to display it.Not usedThis stop is generated if we get an exception during an IsBadXXXPtr call. This means that the memory buffer we are probing doesn't actually have the protection assumed by the caller, or that the memory was freed already, etc. See the discussion above about other stop code (PROBE_INVALID_ADDRESS, PROBE_FREE_MEM, PROBE_GUARD_PAGE, PROBE_NULL, PROBE_INVALID_START_OR_SIZE) for more examples of why using the IsBadXXXPtr APIs is not recommended. To debug this stop: $ parameter1 will typically be C0000005 and that means Access Violation; $ .exr parameter2 - to display the exception information; $ .cxr parameter3 followed by kb - to display the exception context information and stack trace at the time when the exception was raised;Trying to reset NULL address. Not used. Not used. Not used. Not used.This stop is generated if the app verifier detects a VirtualFree (MEM_RESET) call with a NULL first parameter. MEM_RESET should be used only for already allocated memory, so NULL is not a valid first parameter in this case.FFreeing heap memory block inside current thread's stack address range.Allocation base address.Memory region size.Stack low limit address.Stack high limit address.This stop is generated if the app verifier detects a HeapFree, for a block of memory that is actually part of the current thread's stack (!). To debug this stop look at the current stack trace (kb) and try to understand why the function that called HeapFree thought that the memory block was dynamically allocated or mapped but that was actually memory allocated from the stack.DUnmapping memory region inside current thread's stack address range.Allocation base address.Memory region size.Stack low limit address.Stack high limit address.This stop is generated if the app verifier detects an UnmapViewOfFile, for a block of memory that is actually part of the current thread's stack (!). To debug this stop look at the current stack trace (kb) and try to understand why the function that called UnmapViewOfFile thought that the memory block was dynamically allocated or mapped but that was actually memory allocated from the stack.Incorrect RTL_RESOURCE address.Address. Not used. Not used. Not used.jThis stop is generated if the application is trying to use NULL or some other incorrect address (e.g. a kernel-mode address) as the address of a valid object. RtlInitializeResource (NULL) is an incorrect API call that will trigger this kind of verifier stop. param1 is the incorrect address used and the culprit is on the stack trace (display it with kb).!Invalid critical section address.Address. Not used. Not used. Not used.hThis stop is generated if the application is trying to use NULL or some other incorrect address (e.g. a kernel-mode address) as the address of a valid object. EnterCriticalSection(NULL) is an incorrect API call that will trigger this kind of verifier stop. param1 is the incorrect address used and the culprit is on the stack trace (display it with kb).1Attempt to execute code in non-executable memory.Address being accessed.Code performing invalid access.)Exception record. Use .exr to display it.'Context record. Use .cxr to display it.This stop is generated if the application is trying to run code from an address that is non-executable or free. To debug this stop: $ u parameter2 - to unassemble the culprit code $ .exr parameter3 - to display the exception information; $ .cxr parameter4 followed by kb - to display the exception context information and the stack trace for the time when the exception was raised.=Unexpected exception raised while initializing output buffer.Buffer start address. Buffer size.)Exception record. Use .exr to display it.'Context record. Use .cxr to display it.This stop is generated if we get an exception while initializing a buffer specified as output parameter for a Win32 or CRT API. This typically means that the specified output buffer size is incorrect. To debug this stop: $ .exr parameter3 - to display the exception information; $ .cxr parameter4 followed by kb - to display the exception context information and stack trace at the time when the exception was raised.9Unexpected exception when trying to find heap block size.&Address of the heap block being freed. Heap handle.)Exception record. Use .exr to display it.'Context record. Use .cxr to display it.This stop is generated if we get an exception while calling HeapSize for a heap block that is being freed. This typically means that the specified heap block address is incorrect or the heap is corrupted. To debug this stop: $ .exr parameter3 - to display the exception record; $ .cxr parameter4 followed by kb - to display the exception context information and stack trace at the time when the exception was raised.0Freeing memory block with invalid start address.$Address of memory block being freed.&Expected correct memory block address. Not used. Not used.{This stop is generated if the program calls VirtualFree (MEM_RELEASE) with an lpAddress parameter that is not the base address returned by the VirtualAlloc or VirtualAllocEx function when the region of pages was reserved; To debug this stop: $ kb - to display the current stack trace, that is calling VirtualFree. The probable culprit is the DLL that calls VirtualFree.2Unmapping memory block with invalid start address.'Address of memory block being unmapped.&Expected correct memory block address. Not used. Not used.qThis stop is generated if the program calls UnmapViewOfFile with an lpBaseAddress parameter that is not identical to the value returned by a previous call to the MapViewOfFile or MapViewOfFileEx function. To debug this stop: $ kb - to display the current stack trace, that is calling UnmapViewOfFile. The probable culprit is the DLL that calls UnmapViewOfFile.<unexpected exception raised in threadpool callback function.Exception code(Exception record. Use .exr to display it&Context record. Use .cxr to display itNot usedThis stop is generated if a callback function in the threadpool thread is raising an exception. To debug this stop: $ parameter1 might be significant for the type of exception. E.g. an exception code C0000005 means Access Violation. $ .exr parameter2 - to display the exception information. $ .cxr parameter3 followed by kb - to display the exception context information.code in non-executable memoryAddress being accessedCode performing invalid access)Exception record. Use .exr to display it.'Context record. Use .cxr to display it.This stop is generated if the application is trying to run code from an address that is non-executable or free. To debug this stop: $ u parameter2 - to unassemble the culprit code $ .exr parameter3 - to display the exception information $ .cxr parameter4 followed by kb - to display the exception context information and the stack trace for the time when the exception was raised.Creating executable heap. Not used. Not used. Not used. Not used.gThis stop is generated if the application is creating an executable heap. This can be a security risk.Allocating executable memory.$Page protection specified by caller. Not used. Not used. Not used.hThis stop is generated if the application is allocating executable memory. This can be a security risk.@Attempt to execute code in non-executable memory (first chance).Address being accessed.Code performing invalid access.)Exception record. Use .exr to display it.'Context record. Use .cxr to display it.This stop is generated if the application is trying to run code from an address that is non-executable or free. To debug this stop: $ u parameter2 - to unassemble the culprit code $ .exr parameter3 - to display the exception information; $ .cxr parameter4 followed by kb - to display the exception context information and the stack trace for the time when the exception was raised.8The priority of this threadpool thread has been changed.6Callback function where the priority has been changed.Context.=Threadpool Object allocation stack trace, use dps to dump it.Current Priority.^threadpool thread (%x) having executed Callback (%p) has an altered thread priority (%i -> %i)ZThis stop is generated if the thread priority is changed when it's returned to threadpool.8The affinity of this threadpool thread has been changed.6Callback function where the affinity has been changed.Context.=Threadpool Object allocation stack trace, use dps to dump it.Current affinity.cthreadpool thread (%x) having executed Callback (%p) has an altered thread affinity mask (%p -> %p)ZThis stop is generated if the thread affinity is changed when it's returned to threadpool.2Unprocessed msg in the msg pool of current thread.*Callback function that posted the message.Context.=Threadpool Object allocation stack trace, use dps to dump it.`Threadpool thread id. Please use !avrf -tp <threadid> to see the messages posted to this thread.\threadpool thread (%x) having executed Callback (%p) has outstanding window message (%x: %x)This stop is generated if any message left as unprocessed when this threadpool thread is returned to the pool. It's dangerous since it will be processed in a totally different context. Please use Please use !avrf -tp <Param4> to see the messages posted to this thread./Unclosed window belonged to the current thread.Callback function.Context.=Threadpool Object allocation stack trace, use dps to dump it.Threadpool thread id.ithreadpool thread (%x) having executed Callback (%p) has valid hwnd (%x: %s) which could receive messageshThis stop is generated if any window is kept alive when this threadpool thread is returned to the pool.+ExitThread() called on a threadpool thread.Callback function.Context.=Threadpool Object allocation stack trace, use dps to dump it. Not Used.This stop is generated if ExitThread is called on a threadpool thread.It's forbidden since it will make system unstable. It will cause resource leak, hang or AV.KThread is in impersonation state when it's returned to a threadpool thread.4Callback function where the thread was impersonated.Context.=Threadpool Object allocation stack trace, use dps to dump it. Not Used.This stop is generated if call back function change the thread token to impersonate another user and forgot to reset it before returning it back to the threadpool.JA function which requires persistent thread is called within the callback.Callback function.Context.=Threadpool Object allocation stack trace, use dps to dump it. Not Used.Some Microsoft Windows APIs need to be called inside a dedicated or persistent thread. In the threadpool you should generally avoid using thread local storage and queuing asynchronous calls that require a persistent thread, such as the RegNotifyChangeKeyValue function. However, such functions can be queued to a persistent worker thread using QueueUserWorkItem with the WT_EXECUTEINPERSISTENTTHREAD option. A kb in debugger will reveal the caller.%Thread is in dirty transaction state.<Callback function where the transaction context was changed.Context.=Threadpool Object allocation stack trace, use dps to dump it.Transaction Handle.eThis stop is generated if call back function forgot to close or reset the current transaction handle.?This threadpool state has unbalanced CoInit and CoUnInit calls.<Callback function that left the thread in a dirty com state.Context.=Threadpool Object allocation stack trace, use dps to dump it.Balanced Call counts.RThis stop is generated if call back function calls CoInit and CoUnInit unbalanced.The parameters for the timer object are inconsistent. Period should be 0 when WT_EXECUTEONLYONCE is specified when creating the timerPeriod specified.Flags specified. Not Used. Not Used.This stop is generated if the period to signal the timer is not zero when the timer is set to signal only once with the WT_EXECUTEONLYONCE flagKThe loader lock has been held by the threadpool thread within the callback.Callback function.Context.=Threadpool Object allocation stack trace, use dps to dump it. Not Used.This stop is generated if the loader lock is held within the callback and is not released when the thread is returned to the threadpool.KThe preferred language is set by the threadpool thread within the callback.Callback function.Context.=Threadpool Object allocation stack trace, use dps to dump it. Not Used.This stop is generated if the preferred language is set within the callback and is not cleared when the thread is returned to the threadpool.LThe background priority is set by the threadpool thread within the callback.Callback function.Context.=Threadpool Object allocation stack trace, use dps to dump it. Not Used.This stop is generated if the background priority is set within the callback and is not disabled when the thread is returned to the threadpool.0TerminateThread() called on a threadpool thread. Not Used. Not Used. Not Used. Not Used.This stop is generated if TerminateThread is called on a threadpool thread. It's forbidden since it will make system unstable. It will cause resource leak, hang or AV.BThe stack was unwinded when asynchronous I/O operation is pending.*Address of stack variable used in the I/O.Current stack pointer.$Original thread that issued the I/O.$Stack Trace when the I/O was issued.iThis stop is generated if the application issued an I/O operation that uses a stack variable and has not waited for the I/O to complete, thus leading to stack corruption. To debug this stop: $ dps parameter4 to display the stack trace when the I/O was issued. Parameter1 indicates the stack based address and parameter3 the thread that issued the I/O.CThe stack was corrupted when asynchronous I/O operation is pending..Address of the stack variable used in the I/O.Current stack pointer.$Original thread that issued the I/O.$Stack Trace when the I/O was issued.iThis stop is generated if the application issued an I/O operation that uses a stack variable and has not waited for the I/O to complete, thus leading to stack corruption. To debug this stop: $ dps parameter4 to display the stack trace when the I/O was issued. Parameter1 indicates the stack based address and parameter3 the thread that issued the I/O.1Using a freed address in a pending I/O operation.Address used in the I/O.Address being freed.$Original thread that issued the I/O.$Stack Trace when the I/O was issued.This stop is generated if the application issued an I/O operation and freed the memory used in the I/O before the I/O completed thus leading to memory corruption etc. To debug this stop: $ dps parameter4 to display the stack trace when the I/O was issued. Parameter1 indicates the address used in the I/O. Parameter2 indicates the address being freed and parameter3 the thread that issued the I/O.YAn I/O status block (OVERLAPPED) is reused while associated I/O request is still pending.-Address of the I/O status block (OVERLAPPED).$Original thread that issued the I/O.$Stack Trace when the I/O was issued. Not Used.kThis stop is generated if the application reused an I/O status block (OVERLAPPED) while an I/O request using that I/O status block (OVERLAPPED) is still pending. To debug this stop: $ dps parameter3 to display the stack trace when the original I/O was issued. Parameter1 indicates the address used in the I/O and parameter2 the thread that issued the I/O.KUsing an unsupported flag, FILE_ATTRIBUTE_NOT_CONTENT_INDEXED on CreateFileReturn Address. Not used. Not used. Not used.9CreateFile while writing %hs%ws with flags %08x %08x %08xOld version of the MSDN erroneously documented CreateFile as supporting FILE_ATTRIBUTE_NOT_CONTENT_INDEXED. If this flag is intended it should be set using other API functions such as SetFileAttributes. $ ln Parameter1 to find the caller of CreateFile.A heap allocation was leaked.oAddress of the leaked allocation. Run !heap -p -a <address> to get additional information about the allocation.VAddress to the allocation stack trace. Run dps <address> to view the allocation stack.EAddress of the owner dll name. Run du <address> to read the dll name.Base of the owner dll. Run .reload <dll_name> = <address> to reload the owner dll. Use 'lm' to get more information about the loaded and unloaded modules.jThis stop is generated if the owner dll of the allocation was dynamically unloaded while owning resources.A HANDLE was leaked.}Value of the leaked handle. Run !htrace <handle> to get additional information about the handle if handle tracing is enabled.VAddress to the allocation stack trace. Run dps <address> to view the allocation stack.EAddress of the owner dll name. Run du <address> to read the dll name.Base of the owner dll. Run .reload <dll_name> = <address> to reload the owner dll. Use 'lm' to get more information about the loaded and unloaded modules.This stop is generated if the owner dll of the handle was dynamically unloaded while owning resources. To debug this stop: Run !htrace parameter1 to get additional information about the handle.An HKEY was leaked.Value of the leaked HKEY.VAddress to the allocation stack trace. Run dps <address> to view the allocation stack.EAddress of the owner dll name. Run du <address> to read the dll name.Base of the owner dll. Run .reload <dll_name> = <address> to reload the owner dll. Use 'lm' to get more information about the loaded and unloaded modules.mThis stop is generated if the owner dll of the registry key was dynamically unloaded while owning resources.!A virtual reservation was leaked.Leaked reservation address.VAddress to the allocation stack trace. Run dps <address> to view the allocation stack.EAddress of the owner dll name. Run du <address> to read the dll name.Base of the owner dll. Run .reload <dll_name> = <address> to reload the owner dll. Use 'lm' to get more information about the loaded and unloaded modules.tThis stop is generated if the owner dll of the virtual reservation was dynamically unloaded while owning resources.A BSTR was leaked.iAddress of the leaked BSTR. Run !heap -p -a <address> to get additional information about the allocation.VAddress to the allocation stack trace. Run dps <address> to view the allocation stack.EAddress of the owner dll name. Run du <address> to read the dll name.Base of the owner dll. Run .reload <dll_name> = <address> to reload the owner dll. Use 'lm' to get more information about the loaded and unloaded modules.jThis stop is generated if the owner dll of the SysString was dynamically unloaded while owning resources.*A power notification was not unregistered./Address of the power notification registration.XAddress to the registration stack trace. Run dps <address> to view the allocation stack.EAddress of the owner dll name. Run du <address> to read the dll name.Base of the owner dll. Run .reload <dll_name> = <address> to reload the owner dll. Use 'lm' to get more information about the loaded and unloaded modules.xThis stop is generated if the dll registered for power notification and was dynamically unloaded without unregistering.A COM allocation was leaked.sAddress of the leaked COM allocation. Run !heap -p -a <address> to get additional information about the allocation.VAddress to the allocation stack trace. Run dps <address> to view the allocation stack.EAddress of the owner dll name. Run du <address> to read the dll name.Base of the owner dll. Run .reload <dll_name> = <address> to reload the owner dll. Use 'lm' to get more information about the loaded and unloaded modules.oThis stop is generated if the owner dll of the COM allocation was dynamically unloaded while owning resources.t00 000D0L0P0T0X0\0`0d0h0l0p0t0x0|000000000000000000000000000001 111\1`1h1p1P >?`|s00Y1j1p111111111122%292G2V2]2f2r22222222233-3?3X3_3i3u3333333333334.4;4@4a4j44444445 5&5g5s555555666.6;6o6~666666667 77H7N7\7m77777777788X8^8y8888888859;9V9b9r9999999 ::':7:I:[:o:u:::: ;X;;;;;;;;;;;; <>>>>>?F?i??????p\S0Z0a0h0q000000|1111%2c2y2293D3Y3333334445,5K5888N: ->h>>>??,?5?0#0-0d0j00000000001 111'11113$4D444*5k5x5~6666666666666)7H7O7V7]7f77788A8M8888899(91969<9R9n9z99:":):0:9:B::"=5=======>>>>>? ?}111y224+41474F4W44444444444H66::::::::::;;%;.;7;@;V;_;h;q;z;;;;;;;;;;; <<<%<.>>L000 333q4566#7K7q7O889_99999:Q;;;;<<%<<<<<<112t2233&3X3]3g3333333474<4F4U4u4z44444444455/545>5M5m5r5|55555555566%646T6Y6c6r6666666667 77Z7_7i77777778858:8D8S8s8x8888888888 9-929<9K9k9p9z999999999:%:*:4:@:`:e:o:{:::::: ;Q;];k;t;;;;;;;;; <<<< <%<+<1<7<=>8>=>O>>>>>>`?j?????????? 00'0-03090>0C0I0O0U0[0`0e0t00000051;1E11 2#2222A3x33333334 4R55555666)6E6P666666/797N7U7^7f7o7{7777777/8T8d8u888889 99 9)93999a9m9s9x9999999:::Q:W:b::::::*;Q;_;k;v;>01112 33'3B3G3L3V3j333333333334 44404H4M4l4v4445i5s5z555555566666666N7a7777778#8*8<8O888888s9E:Q::::::::;;5;J;Q;W;^;k;q;~;;;<\>>>>>>??&?;?B?H????0000002 3A3m444444444455)5B5M5X5^5m555555555 666)6B6[6f6q6w6666666666 777!7'717:7E7O7W7]7c7m7v77777777777777778 888!8*858?8G8M8S8]8f8q8{888899o0001(121111111222$292?2U2[2q2w2222222222223 33 3'313=3D3N3W3^3h3w333333333333333444 4*434:4D4M4T4^4g4n4x4444444445D5z555566"666@6\6r6666667!7.7a7m7w77777777777 88848O8X8]8c8h8r8w888888888 9?9\9j999999999::::<:F:P:V:\:f:o::::::::L;Y;_;n;|;;;;;;;;<<"<9s>}>>>>l????N2T2p222233333J4S4456F666667u77777777788!8%8-818@8D8L8P8]8a8i8m8888888 9 9-9R9l9u9::4:<:E:L:X:f:n:w:~::::g;<<=">^>>q?? \02u2)344G55 6<6667&7m7778889h:::=;l;;;&*>r>\??0d011>11P222344~4455y666 7p777 89899:;!;x;;;;1S>>?Q?u??@!0O0}000`1t112(222 33334G4u445?555&6T66677G7777788$8U8^888889`9x::;;;(> ?Z?d?r?Pd01"1^11111'2:2d2222223*3Y3333333R4 5`56G6T6z666;7H7i7778%8-8<8M8S8q888888999 9&9.9O9Z9d9n9}9999999999::::,:9:K:Z::::: ;;?;;;;;< <)<\!>c>n>|>>>>> ?+??????`0>0o0|0000000000 191T1l1t1z1111111112242>2g2s2y2222222233.3I3g3m33314A4I4O4U445A5G5X5^55555*6`6u666666777'7B7Q7a7p7z7777777777888!8/878>8P8^8x88888888888888 99 9%939J9c9r9x999999999999999999999999::@:p:|::::::::::;%;6;>;L;U;`;s;};;;;;;;;;;;;;;;;;;;<< <<>%>7>K>>>>>'??????p0 0060F0Q0c0m0u00000000000000000 11 121>1F1X1d1l1{111111111112'2-232=2C2I2U2_2g2{2222222223&3A3_3r3{3344-434K4W4u44444445P5W55555566.6`6g6t666666"7l7777>8G8c8t8z8888888999=9|99999 ::':x:::::: ;;,;>;H;Z;o;|;;;;;;;;;<<<-<4+>B>Y>a>s>z>>>>>>>>>>?=I=O=[=e=|========>>>>>>>>>>>? ?S?a?n?x??????? 0*080H0M0W0]0g0{0000000000011?1O1U11112C2Z2q2222222222233W3t333333444:4H4444h5z555666:6D66667&7/7B77O8}88888888889<9T9l9|99999999:::):3:Z::7;b;;;;;;;;;;;;<<====>?>0X0~0J112O2W2a2p2z22 303334H4e4o4444 5*5I5l55 616g667(767<7A7G7R7\7h7u7779888::::::::::: ;;;#;-;2;=;C;M;[;;;q<<<<<<<<<==3===M=Y=a=f=|=============(>G>P>_>p>>>>> ??\?o????0.090U0_0o00001*1A1172~2233@3K3T3b3k3y3333414H4_4585p555"6^666 7C7r7z7777C8x88889S9~999: ::::;@;h;x;;;;<<1<>P>h>>>>??X?h?????0<0g0u000011<1x11112V2222223g3w333334'4:4U4u444 55A555556*6[6666667737F7V7|778%8U8y88889G9U9e99999:W:e:u:::::5;T;y;;;;; <<.!>B>w>>>>x????????00#0,020W0s0|00000000011V1`111111!2J2d222323A3^3h3p3333333333333333 4:4O4U4c4l4q4w44444444445^5t55>6H6]6d6j6x6~66667777#7N7T77777777777"898I8a8n8v888888888 999>90:9:S:^::::::::::::;; ;;=;H;y;;;;;;;;;;<* >&>,>:>A>G>O>T>Y>^>d>j>v>>>>>>>??&?-?9?J?P?^?m?v?{???????0000$0*030?0M0s000000000001?1P1_1e1w111111111111222$2/252J2]2e2x2222222222 33%3K3T3l3333333+4=4H4m4|44444 5555g5w5555555556-6?6O6g666666666'777B7h7q7~7777777'878B8m8888888889 9969D9M9X9^9k9r9x99999 :::&:.:X:d:::::::::::::0;O;i;t;;;< <"<,<;>>3>H>m>t>~>>>>>>>>>>T?s?~???????????|0000J0Y0g0l0v0000000000 1%1=1C1I1O1n111111111111112 2)222222<3B3`3k3w3|3334%4*4/444=5h5w5|5555555555{667[77778 88"848G88889/9g9t9}999999999:7:F:N:S:X:r:~:::::::::::::;;;K;r;;;;;;;;;;;;;;<&<4<:E>> ?k???????????8%0Q0a0h0n0}0000000000"111G1U1e1x111122%282B2H2n22223!343>3D3{3334:4e4444444 5Y5l55556!6y6666666'757`7r777%888?8T8q8888899I9V999999999: :S:c:j:::::;;;;; <<<<<<<====G=q=y=~============Y>o>>>>>>>?+?1?;?A?F?K?n?}???00$090L0T00000W1h1~11111111122$22282>2C2i2o2222@3S33333 44$4P4h4v444444575F5556Q6i66667w77778<8D8i8n8v8{88888B9o99999: ::*:I:W:o::::::::;8;@;T;Z;d;j;;;;;; <<<%>5>I>O>Y>_>>>>??5>e>>>>>?)?W?e?????0 00B0g0u000001%1n11112'2^2z22233h3w3334494g4u4444 575E5c55555616W6e66666'757b7777778G8U8s88888888 9i9u99999?:f:v:::::::: ;;?;Z;;;;;;;;;;)<9>>>6>F>y>>>>,?I?\?f?l??????@,070D0T0g0q0w000011"1(1M11111112G2U2e2x2222233(32383]3333333 4W4e4u44444455(52585Y5555'656E6X6b6h666666667G7U7e7x7777777888:8g8u88888889%9A9g9x99999W:e:x::::&;S;c;;;<7<<<<'=7=J=|========>M>f>>>>?K?g?{????P 00/050>0D0s000000M1\11111282n2x22222;3p33333+4L4n4444)555556626H6w6666667(7W7b7|7777M8_888$969Z9w99999:K:d::::;3;J;{;;;;<11>{>>>>>?)?6??`60A0L000000000&1>1T1`1>22222343c3v333334s44475D5S5d55555566A6g6s6666666666707777777778s88899#9+9=9C9M9S999999 :::#:c:::;S;c;;;;S>d>>>>?C?T?s???p0C0S0b0j0~0000011.161J1P1Z1`11112 22%2/252V22222222323333333333G4U4x4444C5T5z5555666#747W7p77$8s88889:99999:>:[:e:::::::;;9;A;[;l;;;;;<"(>g>v>>>M?g?|?????<0000=0O0\0l0000000000111%10161N1w1111111111'272B2N2\2b2n2v22223%3`3f3l3r3x3~3333333333333333344%4.4e4r4}44444444444446 66!7>777z8"9M999999:;;R;\;a;;;;;1<=<<<<<= =<=@=\=`=|======>> >@>`>h>l>>>>>>>?? ?$?(?H?h?????00(0H0h00000011(1H1h111111111282X2x22222383X3x33333484X4x4444454585D5\5`5l55555500 0 0<0`0h0l0p0x0000000081<1@1H1L1P11111112 222 2p2t2x22222222@3D3H3P3X333333444 4$4(4x4|4444444444L5P5T5X5\5`5d5h5l5p5t5x5|5555555555555646d6666,70747P7x7777777777777777777777788888 8(8,84888@8D8L8P8X8\8d8h8p8t8|888888888888888888888899 9999$9(90949<9@9H9L9T9X9`9d9l9p9x9|9999999999999999999999:: ::: :$:,:0:8:<:D:H:P:T:\:`:h:l:t:x:::::::::::::::::::::::;;;;; ;(;,;4;8;@;D;L;P;X;\;d;h;p;t;|;;;;;;;;;;;;;;;;;;;;;;<< <<<<$<(<0<4<<<@>>>> >(>,>4>8>@>D>L>P>X>\>d>h>p>t>|>>>>>>>>>>>>>>>>>? ??? ?,?0?ȃO#z;FilF94Aͫ58lfCDW5HUw5(^oT2x憲SWF- dDWuS$e)P\"&Єtx8ra/>)d /@Jh(gAӮ@fbTrfQUQ 0͗3WC`B gwmzZ"V.˽unl`ulM=#?uI$#"iΡ܇Boh,"i`gK +6PѽQi@igEԜP? ҍNyz$z3LĪ!  ܺ.mCy4Zɶ nH҆wG]_7=J$ U'}>Clk,gDvړRn 427!#L>5%r#DsIpH'-L ԹňZCT(]|wjgaAT/JdzO"C^-8J~{a,KnCt XʭT,r+T0ynzL6fNK`||:t+̐^ko.Ep֠x? zO(D QOY- uV^mt8lVb\={:))'X[ڕokܞ)? OB0%MAOTZ ώyUq[ighc5:mM/$fqH 벵kKfA^l_bu0d.|m\Զ$Í~]ʊ ?\ =n d̻ꑜ\H 6k7 9RD^y31r<] $yLh/aGںk?m +*U{+@A+s&1i',V̑GN:dfm+|Wy ̕r%fԅ3 ` l}ea%٘H^ѭ=kbhj@C+׾߰UY*Xhv$7*$0F'^״"PA5kpO6010  `He PlF_;>.],Sp) 003 |0  *H  01 0 UUS10U Washington10URedmond10U Microsoft Corporation1.0,U%Microsoft Windows Production PCA 20110 150818171528Z 161118171528Z0p1 0 UUS10U Washington10URedmond10U Microsoft Corporation10UMicrosoft Windows0"0  *H 0 >_h~ELj\\A@ŽyBOm $7_6 {FF񪻫n}$WD=OclGQ0{n̡t+1ޘB"v9{4.ZY,“mQkTS!AS1i1) 9w|CҭE‹e wIǺQQ9g( $ TϩKt*|eqX7Wn298a?7ѲGVwI0{0U%0+ +7 0UI DP/oMT0QUJ0HF0D1 0 U MOPR1301U*31612+85cef474-af76-4076-90ff-a35e1e23d7de0U#0)9ėx͐O|US0TUM0K0IGEChttp://www.microsoft.com/pkiops/crl/MicWinProPCA2011_2011-10-19.crl0a+U0S0Q+0Ehttp://www.microsoft.com/pkiops/certs/MicWinProPCA2011_2011-10-19.crt0 U00  *H  `t:, u'G+?4ϝPheSFޭl&!Oe;0%̀T܍ cTYy#5~-OdI)Y \vjL5'߽PnӐ} _2#s{BP$-@B{p|/gc[ډuVmnaƛR'V65n7+arQoe`iܽ4TP(3&,9҄ "QܝDu׷00 avV0  *H  01 0 UUS10U Washington10URedmond10U Microsoft Corporation1200U)Microsoft Root Certificate Authority 20100 111019184142Z 261019185142Z01 0 UUS10U Washington10URedmond10U Microsoft Corporation1.0,U%Microsoft Windows Production PCA 20110"0  *H 0  . i!i33T ҋ8-|byJ?5 pk6u1ݍp7tF([`#,GgQ'rɹ;S5|'# oFnhttp://www.microsoft.com/pki/certs/MicRooCerAut_2010-06-23.crt0  *H  |qQyn9>\` QfG=*hwLb{Ǻz4KbzJ7-W|=ܸZij:ni!7ށugӓW^)9-Es[zFX^gl5?$5 uVx,Јߺ~,c#!xlX6+̤-@EΊ\k>p* j_Gc 26*pZBYqKW~!<ŹE ŕ]b֠c uw}=EWo3wbY~10001 0 UUS10U Washington10URedmond10U Microsoft Corporation1.0,U%Microsoft Windows Production PCA 20113 |0  `He0 *H  1  +70 +7 10  +70/ *H  1" J)Ik\M(,9OR)0Z +7 1L0J$"Microsoft Windows" http://www.microsoft.com/windows0  *H [eMg9rۈ5v[_m||a5"&`91Uf hLuͱǧ!)}MP+"[`72FMfi_RQf+[S'1A |a0Y0D`TC M8Bݓs0W&E GͿ$`2X`FXG2tag_TϓLĦ]an(aF'$gr!KdPb]w=WuBM@Q>gfD~Knʱz* 1N5xhttp://www.microsoft.com/pki/certs/MicRooCerAut_2010-06-23.crt0U 00 +7.00=+1http://www.microsoft.com/PKI/docs/CPS/default.htm0@+042 Legal_Policy_Statement. 0  *H  Q ?q=!o1Wm0fjxǨ%kTW+QDS`v@@A\\^5$VKtBȯ7}Z?yJR8/ye٩kzoK0D$"<Y)p2J'U/3b_W@ΙfjbJ &9Jqc{!mÜ<}jxm8ؔƥ B"8 %d~cY%z.9Wvqa˚Gͧ};q ]t"aڰPo1:eGxHr~akow˧ 9؂r*T9[ Uzs;-3.)/T'!ȬN(ۖBAM*f0ӻt2Kc{/!YD8 ##wN™" 7/.p]葈DȈH`-b+֜` s@dDXBAr947R)G#: h1(?00UP |4Dgzkmub0U#0c:\1C{|F3hZmU0VUO0M0KIGEhttp://crl.microsoft.com/pki/crl/products/MicTimStaPCA_2010-07-01.crl0Z+N0L0J+0>http://www.microsoft.com/pki/certs/MicTimStaPCA_2010-07-01.crt0 U00U% 0 +0  *H  k3JƚEC;I0Y2)R7^+>[ Romn=t[,!:lP=d*ݲ~I/novGBT}3bC UrYhɹJBdyf S:y0a0㡁01 0 UUS10U Washington10URedmond10U Microsoft Corporation1 0 U MOPR1'0%U nCipher DSE ESN:7D2E-3782-B0F71%0#UMicrosoft Time-Stamp Service% 0 +5_iX׵적001 0 UUS10U Washington10URedmond10U Microsoft Corporation1 0 U MOPR1'0%U nCipher NTS ESN:57F6-C1E0-554C1+0)U"Microsoft Time Source Master Clock0  *H 30"20160716002813Z20160717002813Z0w0= +Y 1/0-0 30 0 0 5O06 +Y 1(0&0  +Y  0` 0 0  *H y-, &PT؜ m[w& HL^^Cn+^t ȈTҗ{ITC1l6@b ]UjS*6E=+(Pբ%ƽ'xƱ=;7 p+:|~x*j^vlh"Ɯ~_)!}LiТV, P,mb5r͖`'VReJP[;ps.bp#yl-a'"],<1000|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20103!זW0  `He20 *H  1  *H  0/ *H  1" Eٍ9oK:vt΢6VAax0 *H   10005_iX׵00~0|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20103!זW0]S`zxx S0  *H  bA9`z=/\o7(ryQtjpY6!:h5.k\!ao |bhjn\~#Cd6WX k[y+cX/ZUܢ4wnݴN3]5vl(J ;HM]$ #ÃXTaGxTGEcZ >'owQ:9jC]|%=$Ac$ّ@F