Screen flash and "insufficient quota" Windows Search error/X1 Carbon, often resulting in search index corruption

Question

Running Windows 10 21H2 (19044.1645).

I've had a problem now for several years with at least four successive generations of Lenovo X1 Carbon laptops where the screen will randomly flash black for a second and then return. It happens most often when I'm driving external displays through a USB-C dock although I occasionally get it when using the laptop undocked. The following error usually appears corresponding to the display interruption, originating from Microsoft-Windows-Search (Event ID 3079):

Insufficient quota to complete the requested service. (HRESULT : 0x800705ad) (0x800705ad)

My system has no quotas configured and plenty of disk space (currently about 500GB free on the 1TB SSD). C:\programdata\microsoft\search\data typically tops out under 20GB.

I've started from fresh system images and also gone through several new laptops. My latest is the top end X1 Carbon 10th Generation: 12th Generation Intel Core i7-1260P Processor with vPro (E-Core Max 3.40 GHz, P-Core Max 4.70 GHz with Turbo Boost, 12 Cores, 16 Threads, 18 MB Cache).

Occasionally when this happens, I lose the connection to my USB-C dock for a few seconds, but not always. This has happened with four different docks of various models (Targus and Lenovo).

My system has up-to-date ESET and Cortex XDR for antivirus/malware, and I have no ability to disable either one as it is a corporate laptop (I do have admin rights, however).

No dmp file is generated in CrashDumps.

I've also checked all log files for any suspicious events immediately preceding this issue and haven't found anything consistent. (I'm using a PowerShell command like "Get-WinEvent -ListLog * | % {Get-WinEvent -FilterHashTable @{LogName=$_.LogName;StartTime="04-25-2022 10:50";EndTime="04-25-2022 10:52"} -ea 0} | sort timecreated -des >log.txt" to isolate any events immediately before or after the issue).

I've spent many hours with Lenovo attempting to troubleshoot to no avail. I also regularly google this "insufficient quota" error and find nothing relevant or any ideas of how to fix.

I've done all the standard steps of sfc /scannow, DISM.exe /Online /Cleanup-image /Restorehealth, updating drivers (including DisplayLink), running Windows Update, and, as mentioned, buying completely new laptops and installing new OS images.

Does anyone have any idea how I can narrow down the cause of this behavior? I'm hitting a complete wall in getting any more detail than the "insufficient quota" error.

Full error below:

        <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">-<System>  
        <ProviderName="Microsoft-Windows-Search"Guid="{CA4E628D-8567-4896-AB6B-835B221F373F}"EventSourceName="Windows Search Service"/>  
        <EventIDQualifiers="49152">3079</EventID>  
        <Version>0</Version>  
        <Level>2</Level>  
        <Task>3</Task>  
        <Opcode>0</Opcode>  
        <Keywords>0x80000000000000</Keywords>  
        <TimeCreatedSystemTime="2022-04-12T22:06:40.4072733Z"/>  
        <EventRecordID>29603</EventRecordID>  
        <Correlation/>  
        <ExecutionProcessID="0"ThreadID="0"/>  
        <Channel>Application</Channel>  
        <Computer>[redacted]</Computer>  
        <Security/>  
        </System>  
        -<EventData>  
        <DataName="ExtraInfo">Context:WindowsApplicationDetails:Insufficient quota to complete the requested service.(HRESULT :0x800705ad)(0x800705ad)</Data>  
        <DataName="VolumeName">C:\</Data>  
        </EventData>  
        </Event>  

When I occasionally get search index corruption (restarts building from scratch) I see these errors:

SearchIndexer (548,D,0) Windows: An attempt to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 2339864576 (0x000000008b778000) for 32768 (0x00008000) bytes failed after 0.000 seconds with system error 1453 (0x000005ad): "Insufficient quota to complete the requested service. ".  The write operation will fail with error -1011 (0xfffffc0d).  If this error persists then the file may be damaged and may need to be restored from a previous backup.  
SearchIndexer (548,D,0) Windows: An attempt to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 2339897344 (0x000000008b780000) for 32768 (0x00008000) bytes failed after 0.001 seconds with system error 1453 (0x000005ad): "Insufficient quota to complete the requested service. ".  The write operation will fail with error -1011 (0xfffffc0d).  If this error persists then the file may be damaged and may need to be restored from a previous backup.  
SearchIndexer (548,D,0) Windows: An attempt to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.jtx" at offset 36864 (0x0000000000009000) for 8192 (0x00002000) bytes failed after 0.001 seconds with system error 1453 (0x000005ad): "Insufficient quota to complete the requested service. ".  The write operation will fail with error -1011 (0xfffffc0d).  If this error persists then the file may be damaged and may need to be restored from a previous backup.  
SearchIndexer (548,D,0) Windows: Unable to write to section 2 while flushing logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.jtx. Error -1011 (0xfffffc0d).  
SearchIndexer (548,D,0) Windows: The logfile sequence in "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\" has been halted due to a fatal error.  No further updates are possible for the databases that use this logfile sequence.  Please correct the problem and restart or restore from backup.  
The search service has detected corrupted data files in the index {id=4811 - onecoreuap\base\appmodel\search\search\search\gather\server\gathertbl.cxx (862)}. The service will attempt to automatically correct this problem by rebuilding the index.Details: The content index database is corrupt.  (HRESULT : 0xc0041800) (0xc0041800)  
The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.Details: The content index catalog is corrupt.  (HRESULT : 0xc0041801) (0xc0041801)  
The search service has detected corrupted data files in the index {id=4810 - onecoreuap\base\appmodel\search\search\ytrip\common\util\jetutil.cpp (653)}. The service will attempt to automatically correct this problem by rebuilding the index.Details:  0x8e5e01fe (0x8e5e01fe)  
The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.Details: The content index catalog is corrupt.   0xc0041801 (0xc0041801)  
SearchIndexer (548,T,97) Windows: The database engine stopped the instance (0) with error (-510).  Internal Timing Sequence: [1] 0.000002 +J(0)[2] 0.000012 +J(0)[3] 0.000027 +J(0)[4] 0.000001 +J(0)[5] 0.018557 -0.000003 (18) CM -0.017746 (2) WT +J(CM:18, PgRf:0, Rd:0/18, Dy:0/0, Lg:0/0) +M(C:0K, Fs:46, WS:4K # 0K, PF:0K # 0K, P:0K)[6] 0.005000 +J(0) +M(C:0K, Fs:0, WS:-10204K # 0K, PF:-9672K # 0K, P:-9672K)[7] 0.000007 +J(0)[8] 0.028151 -0.000053 (1) WT +J(0) +M(C:0K, Fs:0, WS:-5352K # 0K, PF:-12436K # 0K, P:-12436K)[9] -[10] 0.000008 +J(0) +M(C:0K, Fs:1, WS:4K # 0K, PF:0K # 0K, P:0K)[11] -[12] 0.000021 +J(0) +M(C:0K, Fs:1, WS:0K # 0K, PF:-4K # 0K, P:-4K)[13] 0.000306 +J(0) +M(C:0K, Fs:0, WS:0K # 0K, PF:28K # 0K, P:28K)[14] 0.000009 +J(0) +M(C:0K, Fs:0, WS:-20K # 0K, PF:-20K # 0K, P:-20K)[15] 0.000003 +J(0).  

Answer 1

Still seeing this issue frequently with 21H2 / 19044.1741.

Any ideas?