Windows 10: Windows 10 Blows Up Random Process Virtual Memory

Discus and support Windows 10 Blows Up Random Process Virtual Memory in Windows 10 BSOD Crashes and Debugging to solve the problem; So I'm having problems with Windows 10 randomly blowing up after all of a sudden several processes start consuming virtual memory off the charts. With... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by FortChagos, Nov 28, 2018.

  1. FORTCHAGOS
    FortChagos Win User

    Windows 10 Blows Up Random Process Virtual Memory


    So I'm having problems with Windows 10 randomly blowing up after all of a sudden several processes start consuming virtual memory off the charts. With 32 GBytes of RAM, I shouldn't have any virtual memory issues. Here are several Resource-Exhaustion-Detection event logs. Amoung the offending processes are several Microsoft processes such as LogonUI.exe and Outlook.exe. I don't think this is a memory leak in processes but something in Windows 10 itself. I shouldn't have to sit with the Resource Monitor open viering Commit Charge in hopes of noticing it suddenly go from 20-30% to rapidly climbing to 100% in hopes of killing off whatever process is at the top of the PID list sorted on Commit (KB) in desending order to prevent Windows from going into la la land.


    I see there have been several similar complaints going back several years. Can Microsoft invest some time into finding and fixing the issue. Just let me know what data you want to collect for troubleshooting.


    Log Name: System

    Source: Microsoft-Windows-Resource-Exhaustion-Detector

    Date: 11/20/2018 10:51:14 AM

    Event ID: 2004

    Task Category: Resource Exhaustion Diagnosis Events

    Level: Warning

    Keywords: Events related to exhaustion of system commit limit (virtual memory).

    User: SYSTEM

    Computer: bigface

    Description:

    Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: LogonUI.exe (14740) consumed 31767203840 bytes, NortonSecurity.exe (5004) consumed 737849344 bytes, and chrome.exe (988) consumed 551976960 bytes.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Microsoft-Windows-Resource-Exhaustion-Detector" Guid="{9988748E-C2E8-4054-85F6-0C3E1CAD2470}" />

    <EventID>2004</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>3</Task>

    <Opcode>33</Opcode>

    <Keywords>0x8000000020000000</Keywords>

    <TimeCreated SystemTime="2018-11-20T15:51:14.350822700Z" />

    <EventRecordID>3447</EventRecordID>

    <Correlation ActivityID="{89C9CCE5-49D1-4EB3-AE66-13FDE86C0501}" />

    <Execution ProcessID="9544" ThreadID="18364" />

    <Channel>System</Channel>

    <Computer>bigface</Computer>

    <Security UserID="S-1-5-18" />

    </System>

    <UserData>

    <MemoryExhaustionInfo xmlns="http://www.microsoft.com/Windows/Resource/Exhaustion/Detector/Events">

    <SystemInfo>

    <SystemCommitLimit>42897035264</SystemCommitLimit>

    <SystemCommitCharge>42828402688</SystemCommitCharge>

    <ProcessCommitCharge>39176499200</ProcessCommitCharge>

    <PagedPoolUsage>817098752</PagedPoolUsage>

    <PhysicalMemorySize>34307100672</PhysicalMemorySize>

    <PhysicalMemoryUsage>31976775680</PhysicalMemoryUsage>

    <NonPagedPoolUsage>488148992</NonPagedPoolUsage>

    <Processes>219</Processes>

    </SystemInfo>

    <PagedPoolInfo>

    <Tag_1>

    <Name>MmSt</Name>

    <PoolUsed>34334720</PoolUsed>

    </Tag_1>

    <Tag_2>

    <Name>SaFA</Name>

    <PoolUsed>32237392</PoolUsed>

    </Tag_2>

    <Tag_3>

    <Name>MmRe</Name>

    <PoolUsed>18832464</PoolUsed>

    </Tag_3>

    </PagedPoolInfo>

    <NonPagedPoolInfo>

    <Tag_1>

    <Name>smNp</Name>

    <PoolUsed>42131456</PoolUsed>

    </Tag_1>

    <Tag_2>

    <Name>ismc</Name>

    <PoolUsed>34910208</PoolUsed>

    </Tag_2>

    <Tag_3>

    <Name>smCB</Name>

    <PoolUsed>27377664</PoolUsed>

    </Tag_3>

    </NonPagedPoolInfo>

    <ProcessInfo>

    <Process_1>

    <Name>LogonUI.exe</Name>

    <ID>14740</ID>

    <CreationTime>2018-11-20T03:53:26.272031600Z</CreationTime>

    <CommitCharge>31767203840</CommitCharge>

    <HandleCount>752</HandleCount>

    <Version>10.0.17134.1</Version>

    <TypeInfo>201</TypeInfo>

    </Process_1>

    <Process_2>

    <Name>NortonSecurity.exe</Name>

    <ID>5004</ID>

    <CreationTime>2018-11-19T02:40:56.837702700Z</CreationTime>

    <CommitCharge>737849344</CommitCharge>

    <HandleCount>3423</HandleCount>

    <Version>16.2.1.16</Version>

    <TypeInfo>66</TypeInfo>

    </Process_2>

    <Process_3>

    <Name>chrome.exe</Name>

    <ID>988</ID>

    <CreationTime>2018-11-19T04:25:39.111368000Z</CreationTime>

    <CommitCharge>551976960</CommitCharge>

    <HandleCount>774</HandleCount>

    <Version>70.0.3538.102</Version>

    <TypeInfo>211</TypeInfo>

    </Process_3>

    <Process_4>

    <Name>chrome.exe</Name>

    <ID>7316</ID>

    <CreationTime>2018-11-20T00:52:05.248943000Z</CreationTime>

    <CommitCharge>500183040</CommitCharge>

    <HandleCount>373</HandleCount>

    <Version>70.0.3538.102</Version>

    <TypeInfo>152</TypeInfo>

    </Process_4>

    <Process_5>

    <Name>

    </Name>

    <ID>0</ID>

    <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

    <CommitCharge>0</CommitCharge>

    <HandleCount>0</HandleCount>

    <Version>0.0.0.0</Version>

    <TypeInfo>0</TypeInfo>

    </Process_5>

    <Process_6>

    <Name>

    </Name>

    <ID>0</ID>

    <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

    <CommitCharge>0</CommitCharge>

    <HandleCount>0</HandleCount>

    <Version>0.0.0.0</Version>

    <TypeInfo>0</TypeInfo>

    </Process_6>

    </ProcessInfo>

    <ExhaustionEventInfo>

    <Time>2018-11-20T15:51:10.111621000Z</Time>

    </ExhaustionEventInfo>

    </MemoryExhaustionInfo>

    </UserData>

    </Event>



    Log Name: System

    Source: Microsoft-Windows-Resource-Exhaustion-Detector

    Date: 11/17/2018 11:16:58 AM

    Event ID: 2004

    Task Category: Resource Exhaustion Diagnosis Events

    Level: Warning

    Keywords: Events related to exhaustion of system commit limit (virtual memory).

    User: SYSTEM

    Computer: bigface

    Description:

    Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: LogonUI.exe (20400) consumed 31508566016 bytes, OUTLOOK.EXE (17196) consumed 283516928 bytes, and NortonSecurity.exe (4752) consumed 279199744 bytes.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Microsoft-Windows-Resource-Exhaustion-Detector" Guid="{9988748E-C2E8-4054-85F6-0C3E1CAD2470}" />

    <EventID>2004</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>3</Task>

    <Opcode>33</Opcode>

    <Keywords>0x8000000020000000</Keywords>

    <TimeCreated SystemTime="2018-11-17T16:16:58.089002800Z" />

    <EventRecordID>3073</EventRecordID>

    <Correlation ActivityID="{BC79D599-25D5-43FB-8F6A-1E68B78D9873}" />

    <Execution ProcessID="11908" ThreadID="6964" />

    <Channel>System</Channel>

    <Computer>bigface</Computer>

    <Security UserID="S-1-5-18" />

    </System>

    <UserData>

    <MemoryExhaustionInfo xmlns="http://www.microsoft.com/Windows/Resource/Exhaustion/Detector/Events">

    <SystemInfo>

    <SystemCommitLimit>38602067968</SystemCommitLimit>

    <SystemCommitCharge>38503141376</SystemCommitCharge>

    <ProcessCommitCharge>35569905664</ProcessCommitCharge>

    <PagedPoolUsage>539947008</PagedPoolUsage>

    <PhysicalMemorySize>34307100672</PhysicalMemorySize>

    <PhysicalMemoryUsage>33765572608</PhysicalMemoryUsage>

    <NonPagedPoolUsage>359956480</NonPagedPoolUsage>

    <Processes>203</Processes>

    </SystemInfo>

    <PagedPoolInfo>

    <Tag_1>

    <Name>MmSt</Name>

    <PoolUsed>49002192</PoolUsed>

    </Tag_1>

    <Tag_2>

    <Name>FMfn</Name>

    <PoolUsed>42283840</PoolUsed>

    </Tag_2>

    <Tag_3>

    <Name>Ntff</Name>

    <PoolUsed>23310816</PoolUsed>

    </Tag_3>

    </PagedPoolInfo>

    <NonPagedPoolInfo>

    <Tag_1>

    <Name>ismc</Name>

    <PoolUsed>34910208</PoolUsed>

    </Tag_1>

    <Tag_2>

    <Name>Devi</Name>

    <PoolUsed>17929120</PoolUsed>

    </Tag_2>

    <Tag_3>

    <Name>smNp</Name>

    <PoolUsed>13516800</PoolUsed>

    </Tag_3>

    </NonPagedPoolInfo>

    <ProcessInfo>

    <Process_1>

    <Name>LogonUI.exe</Name>

    <ID>20400</ID>

    <CreationTime>2018-11-17T02:41:23.256238700Z</CreationTime>

    <CommitCharge>31508566016</CommitCharge>

    <HandleCount>752</HandleCount>

    <Version>10.0.17134.1</Version>

    <TypeInfo>201</TypeInfo>

    </Process_1>

    <Process_2>

    <Name>OUTLOOK.EXE</Name>

    <ID>17196</ID>

    <CreationTime>2018-11-15T01:26:42.661928300Z</CreationTime>

    <CommitCharge>283516928</CommitCharge>

    <HandleCount>3892</HandleCount>

    <Version>16.0.11001.20074</Version>

    <TypeInfo>210</TypeInfo>

    </Process_2>

    <Process_3>

    <Name>NortonSecurity.exe</Name>

    <ID>4752</ID>

    <CreationTime>2018-11-15T00:50:03.775148000Z</CreationTime>

    <CommitCharge>279199744</CommitCharge>

    <HandleCount>3079</HandleCount>

    <Version>16.2.1.16</Version>

    <TypeInfo>67</TypeInfo>

    </Process_3>

    <Process_4>

    <Name>chrome.exe</Name>

    <ID>17352</ID>

    <CreationTime>2018-11-15T23:00:43.278932200Z</CreationTime>

    <CommitCharge>222027776</CommitCharge>

    <HandleCount>476</HandleCount>

    <Version>70.0.3538.102</Version>

    <TypeInfo>152</TypeInfo>

    </Process_4>

    <Process_5>

    <Name>

    </Name>

    <ID>0</ID>

    <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

    <CommitCharge>0</CommitCharge>

    <HandleCount>0</HandleCount>

    <Version>0.0.0.0</Version>

    <TypeInfo>0</TypeInfo>

    </Process_5>

    <Process_6>

    <Name>

    </Name>

    <ID>0</ID>

    <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

    <CommitCharge>0</CommitCharge>

    <HandleCount>0</HandleCount>

    <Version>0.0.0.0</Version>

    <TypeInfo>0</TypeInfo>

    </Process_6>

    </ProcessInfo>

    <ExhaustionEventInfo>

    <Time>2018-11-17T16:16:59.639281200Z</Time>

    </ExhaustionEventInfo>

    </MemoryExhaustionInfo>

    </UserData>

    </Event>





    Log Name: System

    Source: Microsoft-Windows-Resource-Exhaustion-Detector

    Date: 11/14/2018 7:39:04 PM

    Event ID: 2004

    Task Category: Resource Exhaustion Diagnosis Events

    Level: Warning

    Keywords: Events related to exhaustion of system commit limit (virtual memory).

    User: SYSTEM

    Computer: bigface

    Description:

    Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Wacom_TouchUser.exe (11564) consumed 29938606080 bytes, OUTLOOK.EXE (17264) consumed 419147776 bytes, and chrome.exe (8224) consumed 393830400 bytes.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Microsoft-Windows-Resource-Exhaustion-Detector" Guid="{9988748E-C2E8-4054-85F6-0C3E1CAD2470}" />

    <EventID>2004</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>3</Task>

    <Opcode>33</Opcode>

    <Keywords>0x8000000020000000</Keywords>

    <TimeCreated SystemTime="2018-11-15T00:39:04.014166800Z" />

    <EventRecordID>2819</EventRecordID>

    <Correlation ActivityID="{D770D54E-7653-4135-AF52-9FE4620B0CA8}" />

    <Execution ProcessID="14088" ThreadID="16464" />

    <Channel>System</Channel>

    <Computer>bigface</Computer>

    <Security UserID="S-1-5-18" />

    </System>

    <UserData>

    <MemoryExhaustionInfo xmlns="http://www.microsoft.com/Windows/Resource/Exhaustion/Detector/Events">

    <SystemInfo>

    <SystemCommitLimit>38602067968</SystemCommitLimit>

    <SystemCommitCharge>38504808448</SystemCommitCharge>

    <ProcessCommitCharge>34900652032</ProcessCommitCharge>

    <PagedPoolUsage>326729728</PagedPoolUsage>

    <PhysicalMemorySize>34307100672</PhysicalMemorySize>

    <PhysicalMemoryUsage>32588873728</PhysicalMemoryUsage>

    <NonPagedPoolUsage>292925440</NonPagedPoolUsage>

    <Processes>209</Processes>

    </SystemInfo>

    <PagedPoolInfo>

    <Tag_1>

    <Name>MmSt</Name>

    <PoolUsed>37591248</PoolUsed>

    </Tag_1>

    <Tag_2>

    <Name>SaFA</Name>

    <PoolUsed>35402160</PoolUsed>

    </Tag_2>

    <Tag_3>

    <Name>MmRe</Name>

    <PoolUsed>20914528</PoolUsed>

    </Tag_3>

    </PagedPoolInfo>

    <NonPagedPoolInfo>

    <Tag_1>

    <Name>ismc</Name>

    <PoolUsed>34910208</PoolUsed>

    </Tag_1>

    <Tag_2>

    <Name>Devi</Name>

    <PoolUsed>17864704</PoolUsed>

    </Tag_2>

    <Tag_3>

    <Name>smNp</Name>

    <PoolUsed>14200832</PoolUsed>

    </Tag_3>

    </NonPagedPoolInfo>

    <ProcessInfo>

    <Process_1>

    <Name>Wacom_TouchUser.exe</Name>

    <ID>11564</ID>

    <CreationTime>2018-11-14T04:16:29.615232400Z</CreationTime>

    <CommitCharge>29938606080</CommitCharge>

    <HandleCount>270</HandleCount>

    <Version>6.3.31.4</Version>

    <TypeInfo>201</TypeInfo>

    </Process_1>

    <Process_2>

    <Name>OUTLOOK.EXE</Name>

    <ID>17264</ID>

    <CreationTime>2018-11-14T23:57:37.896249400Z</CreationTime>

    <CommitCharge>419147776</CommitCharge>

    <HandleCount>3476</HandleCount>

    <Version>16.0.11001.20074</Version>

    <TypeInfo>210</TypeInfo>

    </Process_2>

    <Process_3>

    <Name>chrome.exe</Name>

    <ID>8224</ID>

    <CreationTime>2018-11-14T04:16:43.428407900Z</CreationTime>

    <CommitCharge>393830400</CommitCharge>

    <HandleCount>671</HandleCount>

    <Version>70.0.3538.102</Version>

    <TypeInfo>219</TypeInfo>

    </Process_3>

    <Process_4>

    <Name>

    </Name>

    <ID>0</ID>

    <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

    <CommitCharge>0</CommitCharge>

    <HandleCount>0</HandleCount>

    <Version>0.0.0.0</Version>

    <TypeInfo>0</TypeInfo>

    </Process_4>

    <Process_5>

    <Name>

    </Name>

    <ID>0</ID>

    <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

    <CommitCharge>0</CommitCharge>

    <HandleCount>0</HandleCount>

    <Version>0.0.0.0</Version>

    <TypeInfo>0</TypeInfo>

    </Process_5>

    <Process_6>

    <Name>

    </Name>

    <ID>0</ID>

    <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

    <CommitCharge>0</CommitCharge>

    <HandleCount>0</HandleCount>

    <Version>0.0.0.0</Version>

    <TypeInfo>0</TypeInfo>

    </Process_6>

    </ProcessInfo>

    <ExhaustionEventInfo>

    <Time>2018-11-15T00:39:03.241502000Z</Time>

    </ExhaustionEventInfo>

    </MemoryExhaustionInfo>

    </UserData>

    </Event>





    Log Name: System

    Source: Microsoft-Windows-Resource-Exhaustion-Detector

    Date: 11/12/2018 7:53:57 AM

    Event ID: 2004

    Task Category: Resource Exhaustion Diagnosis Events

    Level: Warning

    Keywords: Events related to exhaustion of system commit limit (virtual memory).

    User: SYSTEM

    Computer: bigface

    Description:

    Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: LogonUI.exe (8352) consumed 31292297216 bytes, SearchIndexer.exe (4472) consumed 460734464 bytes, and OUTLOOK.EXE (12812) consumed 389242880 bytes.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Microsoft-Windows-Resource-Exhaustion-Detector" Guid="{9988748E-C2E8-4054-85F6-0C3E1CAD2470}" />

    <EventID>2004</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>3</Task>

    <Opcode>33</Opcode>

    <Keywords>0x8000000020000000</Keywords>

    <TimeCreated SystemTime="2018-11-12T12:53:57.617125500Z" />

    <EventRecordID>2188</EventRecordID>

    <Correlation ActivityID="{EAD010B5-B0FD-4E2C-9C04-D11E4526E2AB}" />

    <Execution ProcessID="3076" ThreadID="20072" />

    <Channel>System</Channel>

    <Computer>bigface</Computer>

    <Security UserID="S-1-5-18" />

    </System>

    <UserData>

    <MemoryExhaustionInfo xmlns="http://www.microsoft.com/Windows/Resource/Exhaustion/Detector/Events">

    <SystemInfo>

    <SystemCommitLimit>38602067968</SystemCommitLimit>

    <SystemCommitCharge>38542544896</SystemCommitCharge>

    <ProcessCommitCharge>35683082240</ProcessCommitCharge>

    <PagedPoolUsage>550940672</PagedPoolUsage>

    <PhysicalMemorySize>34307100672</PhysicalMemorySize>

    <PhysicalMemoryUsage>33794232320</PhysicalMemoryUsage>

    <NonPagedPoolUsage>382840832</NonPagedPoolUsage>

    <Processes>190</Processes>

    </SystemInfo>

    <PagedPoolInfo>

    <Tag_1>

    <Name>MmSt</Name>

    <PoolUsed>37665696</PoolUsed>

    </Tag_1>

    <Tag_2>

    <Name>SaFA</Name>

    <PoolUsed>32662800</PoolUsed>

    </Tag_2>

    <Tag_3>

    <Name>MmRe</Name>

    <PoolUsed>19093584</PoolUsed>

    </Tag_3>

    </PagedPoolInfo>

    <NonPagedPoolInfo>

    <Tag_1>

    <Name>ismc</Name>

    <PoolUsed>34910208</PoolUsed>

    </Tag_1>

    <Tag_2>

    <Name>Devi</Name>

    <PoolUsed>17897728</PoolUsed>

    </Tag_2>

    <Tag_3>

    <Name>smNp</Name>

    <PoolUsed>13971456</PoolUsed>

    </Tag_3>

    </NonPagedPoolInfo>

    <ProcessInfo>

    <Process_1>

    <Name>LogonUI.exe</Name>

    <ID>8352</ID>

    <CreationTime>2018-11-12T04:53:38.563036600Z</CreationTime>

    <CommitCharge>31292297216</CommitCharge>

    <HandleCount>750</HandleCount>

    <Version>10.0.17134.1</Version>

    <TypeInfo>201</TypeInfo>

    </Process_1>

    <Process_2>

    <Name>SearchIndexer.exe</Name>

    <ID>4472</ID>

    <CreationTime>2018-11-11T04:09:07.203803900Z</CreationTime>

    <CommitCharge>460734464</CommitCharge>

    <HandleCount>1863</HandleCount>

    <Version>7.0.17134.285</Version>

    <TypeInfo>66</TypeInfo>

    </Process_2>

    <Process_3>

    <Name>OUTLOOK.EXE</Name>

    <ID>12812</ID>

    <CreationTime>2018-11-11T04:10:06.636181500Z</CreationTime>

    <CommitCharge>389242880</CommitCharge>

    <HandleCount>3418</HandleCount>

    <Version>16.0.11001.20074</Version>

    <TypeInfo>211</TypeInfo>

    </Process_3>

    <Process_4>

    <Name>chrome.exe</Name>

    <ID>11684</ID>

    <CreationTime>2018-11-11T04:10:02.600705500Z</CreationTime>

    <CommitCharge>306413568</CommitCharge>

    <HandleCount>506</HandleCount>

    <Version>70.0.3538.77</Version>

    <TypeInfo>152</TypeInfo>

    </Process_4>

    <Process_5>

    <Name>

    </Name>

    <ID>0</ID>

    <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

    <CommitCharge>0</CommitCharge>

    <HandleCount>0</HandleCount>

    <Version>0.0.0.0</Version>

    <TypeInfo>0</TypeInfo>

    </Process_5>

    <Process_6>

    <Name>

    </Name>

    <ID>0</ID>

    <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

    <CommitCharge>0</CommitCharge>

    <HandleCount>0</HandleCount>

    <Version>0.0.0.0</Version>

    <TypeInfo>0</TypeInfo>

    </Process_6>

    </ProcessInfo>

    <ExhaustionEventInfo>

    <Time>2018-11-12T12:53:54.709494000Z</Time>

    </ExhaustionEventInfo>

    </MemoryExhaustionInfo>

    </UserData>

    </Event>





    Log Name: System

    Source: Microsoft-Windows-Resource-Exhaustion-Detector

    Date: 11/5/2018 2:18:34 PM

    Event ID: 2004

    Task Category: Resource Exhaustion Diagnosis Events

    Level: Warning

    Keywords: Events related to exhaustion of system commit limit (virtual memory).

    User: SYSTEM

    Computer: bigface

    Description:

    Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: LogonUI.exe (7648) consumed 33818791936 bytes, NortonSecurity.exe (5176) consumed 248037376 bytes, and Adobe Desktop Service.exe (588) consumed 161103872 bytes.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Microsoft-Windows-Resource-Exhaustion-Detector" Guid="{9988748E-C2E8-4054-85F6-0C3E1CAD2470}" />

    <EventID>2004</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>3</Task>

    <Opcode>33</Opcode>

    <Keywords>0x8000000020000000</Keywords>

    <TimeCreated SystemTime="2018-11-05T19:18:34.719485500Z" />

    <EventRecordID>1495</EventRecordID>

    <Correlation ActivityID="{787B2A4E-C7E5-455B-93AE-91179DEA1BAB}" />

    <Execution ProcessID="15192" ThreadID="17248" />

    <Channel>System</Channel>

    <Computer>bigface</Computer>

    <Security UserID="S-1-5-18" />

    </System>

    <UserData>Jus

    <MemoryExhaustionInfo xmlns="http://www.microsoft.com/Windows/Resource/Exhaustion/Detector/Events">

    <SystemInfo>

    <SystemCommitLimit>38602067968</SystemCommitLimit>

    <SystemCommitCharge>38507552768</SystemCommitCharge>

    <ProcessCommitCharge>36140277760</ProcessCommitCharge>

    <PagedPoolUsage>401985536</PagedPoolUsage>

    <PhysicalMemorySize>34307100672</PhysicalMemorySize>

    <PhysicalMemoryUsage>33711984640</PhysicalMemoryUsage>

    <NonPagedPoolUsage>323493888</NonPagedPoolUsage>

    <Processes>180</Processes>

    </SystemInfo>

    <PagedPoolInfo>

    <Tag_1>

    <Name>MmSt</Name>

    <PoolUsed>29061600</PoolUsed>

    </Tag_1>

    <Tag_2>

    <Name>MmRe</Name>

    <PoolUsed>16804768</PoolUsed>

    </Tag_2>

    <Tag_3>

    <Name>CM25</Name>

    <PoolUsed>16429056</PoolUsed>

    </Tag_3>

    </PagedPoolInfo>

    <NonPagedPoolInfo>

    <Tag_1>

    <Name>ismc</Name>

    <PoolUsed>34910208</PoolUsed>

    </Tag_1>

    <Tag_2>

    <Name>Devi</Name>

    <PoolUsed>17941408</PoolUsed>

    </Tag_2>

    <Tag_3>

    <Name>smNp</Name>

    <PoolUsed>16715776</PoolUsed>

    </Tag_3>

    </NonPagedPoolInfo>

    <ProcessInfo>

    <Process_1>

    <Name>LogonUI.exe</Name>

    <ID>7648</ID>

    <CreationTime>2018-11-05T04:17:26.633904000Z</CreationTime>

    <CommitCharge>33818791936</CommitCharge>

    <HandleCount>698</HandleCount>

    <Version>10.0.17134.1</Version>

    <TypeInfo>201</TypeInfo>

    </Process_1>

    <Process_2>

    <Name>NortonSecurity.exe</Name>

    <ID>5176</ID>

    <CreationTime>2018-11-04T14:19:33.969948500Z</CreationTime>

    <CommitCharge>248037376</CommitCharge>

    <HandleCount>3101</HandleCount>

    <Version>16.2.1.16</Version>

    <TypeInfo>66</TypeInfo>

    </Process_2>

    <Process_3>

    <Name>Adobe Desktop Service.exe</Name>

    <ID>588</ID>

    <CreationTime>2018-11-04T18:57:37.686553400Z</CreationTime>

    <CommitCharge>161103872</CommitCharge>

    <HandleCount>1210</HandleCount>

    <Version>4.7.0.400</Version>

    <TypeInfo>211</TypeInfo>

    </Process_3>

    <Process_4>

    <Name>dwm.exe</Name>

    <ID>7900</ID>

    <CreationTime>2018-11-04T17:40:43.913446900Z</CreationTime>

    <CommitCharge>113270784</CommitCharge>

    <HandleCount>1016</HandleCount>

    <Version>10.0.17134.1</Version>

    <TypeInfo>152</TypeInfo>

    </Process_4>

    <Process_5>

    <Name>

    </Name>

    <ID>0</ID>

    <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

    <CommitCharge>0</CommitCharge>

    <HandleCount>0</HandleCount>

    <Version>0.0.0.0</Version>

    <TypeInfo>0</TypeInfo>

    </Process_5>

    <Process_6>

    <Name>

    </Name>

    <ID>0</ID>

    <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

    <CommitCharge>0</CommitCharge>

    <HandleCount>0</HandleCount>

    <Version>0.0.0.0</Version>

    <TypeInfo>0</TypeInfo>

    </Process_6>

    </ProcessInfo>

    <ExhaustionEventInfo>

    <Time>2018-11-05T19:18:33.747250000Z</Time>

    </ExhaustionEventInfo>

    </MemoryExhaustionInfo>

    </UserData>

    </Event>

    :)
     
    FortChagos, Nov 28, 2018
    #1
  2. GNJHA
    GNJha Win User

    Boot Process

    Hi,

    Please suggest me a link that can explain the boot process step by step of ...

    • Windows 7,
    • Windows 8.1,
    • Windows 10,
    • Windows Server 2008 R2 and
    • Windows Server 2012 R2

    With Regards

    InTech
     
    GNJha, Nov 28, 2018
    #2
  3. SACHIN VENKATESH
    Sachin Venkatesh Win User
    increasing virtual memory/Windows not activated

    Hello,

    Thank you for posting in Microsoft Community.

    I understand the inconvenience you are facing in Windows. We will help you.

    To assist you better, I suggest you to answer the below questions.

    • Are you getting that your Windows is not activated and is your Windows activated?
    • Are you not able to get into Settings in Windows?
    • Are you trying to increase the virtual memory?
    • Are you getting any error message or code regarding the memory issues?
    Please post to us with more information to help you better.
     
    Sachin Venkatesh, Nov 28, 2018
    #3
  4. SACHIN VENKATESH
    Sachin Venkatesh Win User

    Windows 10 Blows Up Random Process Virtual Memory

    increasing virtual memory/Windows not activated

    Hello,

    Thank you for your response.

    For Windows activation issues,

    Refer: Get Help Activating Microsoft Windows

    To increase the virtual memory in Windows 10 please follow the below steps.

    • Press Windows + E keys, opens File explorer.
    • Left side Navigation Pane right click on
      This PC.
    • Select Properties, select Advance system settings.
    • Select Settings next to performance.
    • Under Advance Tab select change in
      Virtual memory.
    • Uncheck Automatically manage paging file size for all drives.
    • Select the Range of virtual memory that you want to change.
    Restart and check if the issue is resolved.

    Keep us posted to help you better.
     
    Sachin Venkatesh, Nov 28, 2018
    #4
Thema:

Windows 10 Blows Up Random Process Virtual Memory

Loading...

  1. Windows 10 Blows Up Random Process Virtual Memory - Similar Threads - Blows Random Process

  2. Virtual Memory

    in Windows 10 Gaming
    Virtual Memory: Can I increase the size of virtual Memory after manually setting it onceActually I had set my virtual Memory for 12 GB and now when I try to increase it,it doesn't increases https://answers.microsoft.com/en-us/windows/forum/all/virtual-memory/2282dafe-cf9d-4a27-a932-6f8ccec5cc90

  3. Virtual memory

    in Windows 10 Software and Apps
    Virtual memory: Hello all hope every one is having a good Day/Night I have a Asus IntelR CoreTM i7-2600K CPU @ 3.40GHz with 24 gig of ram With a NVIDIA GeForce GTX 1050 TiI Play Games mostly on my pc like The Witcher series, Fallout series, Borderlands Series & Red Dead Redemption 2 ....

  4. Virtual memory

    in Windows 10 Gaming
    Virtual memory: Hello all hope every one is having a good Day/Night I have a Asus IntelR CoreTM i7-2600K CPU @ 3.40GHz with 24 gig of ram With a NVIDIA GeForce GTX 1050 TiI Play Games mostly on my pc like The Witcher series, Fallout series, Borderlands Series & Red Dead Redemption 2 ....

  5. Virtual Memory

    in Windows 10 BSOD Crashes and Debugging
    Virtual Memory: I have a SSD 128gb and 1TB HDD.Should i set more VM on HDD does it make the pc run better or should i check the AUTOMATICALLY MANAGE PAGING FILE FOR ALL DRIVES Currently, i set Virtual memory like this :...

  6. Windows 10 virtual memory

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 virtual memory: So I've got 32GB of RAM, 38% of it is used, still Windows thinks it necessary to wreak havoc on my poor HDD instead? That poor baby's moaning and groaning away at 100% while running some memory intensive programs, meanwhile my RAM which is specifically designed for that task...

  7. Virtual memory

    in Windows 10 Ask Insider
    Virtual memory: Hi guys, I'm trying to clear up some space on my SSD to install some games and I've noticed that my virtual memory is taking up 244GB !! I feel like this is highly irregular as all I can find online is about upping the virtual memory size. I'd like to reduce this, but I'm not...

  8. Virtual Memory

    in Windows 10 BSOD Crashes and Debugging
    Virtual Memory: What is the recommended Virtual Memory for my laptop? https://1drv.ms/t/s!ApFhXMFCkw0wiARdOisNu01fep5C?e=Tg8mgY https://prnt.sc/qj9xpb Please tell..... Thanks & Regards, Regal76...

  9. Virtual Memory

    in Windows 10 BSOD Crashes and Debugging
    Virtual Memory: What is the advantage and disadvantage of using virtual machine? https://answers.microsoft.com/en-us/windows/forum/all/virtual-memory/2e730df6-0913-4ad6-b629-d84de6c8b414

  10. Process taking up alot of memory.

    in Windows 10 Performance & Maintenance
    Process taking up alot of memory.: Hey guys, so I have this process it's taking up alot of memory. [img] My computer Stats: [img] 28198