magicandre1981

it is still a duplicate of Run5k's solition and you haven't posted any links to search results nor have you added a picture of WPA.exe with your trace. next time do research and calm down. I sleeped at the time you did your rant here.

analyze system process usage. next time please use search first.

analyzing large ETL files requires extra large amount of RAM otherwise it crashes. consuming ETW is nit the best if it takes hours to see the issue. only run in shortly

docs.microsoft.com/en-us/windows-hardware/test/wpt/…

record heap allocations:

I still have no idea. last file still doesn't show large grow.

StructuredQuery.dll!SemanticsUM::SchemaBinary::Load, StructuredQuery.dll!operator new. And the new operator does the HEap allocations. how large is the search index? try to rebuild it.

the grow is very low in the trace. from what I see the Explorer allocates memory while trying to start programs (shell32.dll!HDXA_LetHandlerProcessCommandEx, windows.storage.dll!CBindAndInvokeStaticVerb::_TryExecuteCom‌​mandHandler, shell32.dll!COpenDefaultLocationCommand::Execute) and querying ContextMenus (shell32.dll!CRegistryVerbsContextMenu::QueryContextMenu) which results in searches to Windows Search (StructuredQuery.dll!StructuredQuery1::CStructuredQueryHelpe‌​r::ParseStructured‌​Qu‌​ery, StructuredQuery.dll!StructuredQuery1::LoadSchemaBinaryFromFi‌​le) and this causes allocations.

it shows high heap usage. without callstacks of allocations from the ETL we can't help you

the link explains everything. Win10 includes wpr.exe, open CMD.exe as admin, run this command wpr.exe -start ReferenceSet -filemode && timeout -1 && wpr.exe -stop C:\HighMemoryUsage.etl, wait 3 minutes to capture the memory usage grow, press a key to stop logging. Zip the large ETL file (+ NGENPDB folder) into 1 zip, upload the zip (OneDrive, dropbox, google drive) and post the share link here.

use Windows Performance Toolkit and measure ReferenceSet and analyze it

"csc" is offline files. do you use them?

StructuredQuery.dll!SemanticsUM::SchemaBinary::Load, StructuredQuery.dll!operator new. And the new operator does the HEap allocations. how large is the search index? try to rebuild it.

the grow is very low in the trace. from what I see the Explorer allocates memory while trying to start programs (shell32.dll!HDXA_LetHandlerProcessCommandEx, windows.storage.dll!CBindAndInvokeStaticVerb::_TryExecuteCom‌​mandHandler, shell32.dll!COpenDefaultLocationCommand::Execute) and querying ContextMenus (shell32.dll!CRegistryVerbsContextMenu::QueryContextMenu) which results in searches to Windows Search (StructuredQuery.dll!StructuredQuery1::CStructuredQueryHelpe‌​r::ParseStructured‌​Qu‌​ery, StructuredQuery.dll!StructuredQuery1::LoadSchemaBinaryFromFi‌​le) and this causes allocations.

it shows high heap usage. without callstacks of allocations from the ETL we can't help you

the link explains everything. Win10 includes wpr.exe, open CMD.exe as admin, run this command wpr.exe -start ReferenceSet -filemode && timeout -1 && wpr.exe -stop C:\HighMemoryUsage.etl, wait 3 minutes to capture the memory usage grow, press a key to stop logging. Zip the large ETL file (+ NGENPDB folder) into 1 zip, upload the zip (OneDrive, dropbox, google drive) and post the share link here.

use Windows Performance Toolkit and measure ReferenceSet and analyze it

disable (not only stop) the RunFullMemoryDiagnosticEntry task to fix it

looking at the picture shows exactly what I told you. I see the ntoskrnl.exe!RtlpGenericRandomPatternWorker call, so the memory test during idle maintenance. so disable this task to fix it

you have no expanded the stack correctly. share the ETL file (compressed as 7z) so that I can take a look at it

you likely have the idle maintenance scheduled task that runs and scans your RAM for error. Check my answer and look for ntoskrnl.exe!RtlpGenericRandomPatternWorker, ntoskrnl.exe!RtlpTestMemoryRandomUp calls in callstack of system process.

share all new dumps

RAM timings are fine. check for a BIOS update

but now I also need the SPD tab again, to compare the data of both to see if the RAM timings are not correct

yes of course you can use different provider

the folder is empty now

you posted the CPU tab, I need the memory tab

post pictures of CPU-Z (memory and SPD tabs) on your onedrive and link them

remove the software that uses EasyAntiCheat.sys and FACEIT.sys and look what happens

upload the file C:\WINDOWS\Minidump\051917-12968-01.dmp (onedrive) ad post a share link here, so that we can debug it

this is still a 100% duplicate. If MS now added the check to security only update use WSUSoffline to update Windows.

they are the same, they ask both how to update Windows on new CPUs like Kaybe Lake (which is your i7-77xx) after applying the latest update rollups. The rules are here, to NOT ask the same over and over again and focus on 1 question!!!!!

remove the latest quality rollup and only install the latest security only updates each patchday.

You did something wrong. I see all data. I posted what I saw from the trace.

share the ETL (zip ot first to reduce the file size to up-&download, so that I can analyze it

use WPR/WPA to capture and analyze the cpu usage: superuser.com/a/1164299/174557. expand the stack of the svchost.exe process in WPA which has most cpu usage (weight %) and loo for the function names to see what the svchost.exe does

@PiotrGrochowski as I said, Intel doesn't support your GPU any longer.

as I already said, Intel doesn't support this old GPUs any longer. if it works, it is ok, but if you have issues, you are out of luck.

Piotr, your HD is also based on the HD4000 like my Ivy Bridge i5, so you're also using a no longer supported GPU. Intel wants to sell new CPUs with newer GPUs so they ignore old users.

@Tetsujin if you read the PDF you see that Intel doesn't support the driver. they release the driver, but don't certificate it for WHQL " The driver is being provided as-is with no Intel support for any graphics issues found. Intel advises upgrading to Intel approved Windows 10 products for the best user experience and support."

@Tetsujin also the HD4000 is not supported officially in win10

the RAM speed may depend on the FSB (Front Side Bus), so try to lower this value in BIOS.

your RAM runs at a bit higher MHz as it is designed. lower it to 800MHz.

make pictures of all CPU-Z tabs and post them

check for the command rate values in CPU-Z

also RAM slots on the motherboard can be damaged and cause corruptions.

@pcworld 0x8024001e = WU_E_SERVICE_STOP (Operation did not complete because the service or system was being shut down).

@enigmaticPhysicist but this is MUCH faster. before the new july update rollup it took several hours until 1 day! so yes it WORKED

@AlexPi this is no miracle, MS fixed the update search logic in an update

@CADbloke firsti install 3020369 and next step the July rollup