body { -ms-overflow-style: scrollbar; overflow-y: scroll; overscroll-behavior-y: none; } .errorContainer { background-color: #FFF; color: #0F1419; max-width: 600px; margin: 0 auto; padding: 10%; font-family: Helvetica, sans-serif; font-size: 16px; } .errorButton { margin: 3em 0; } .errorButton a { background: #1DA1F2; border-radius: 2.5em; color: white; padding: 1em 2em; text-decoration: none; } .errorButton a:hover, .errorButton a:focus { background: rgb(26, 145, 218); } .errorFooter { color: #657786; font-size: 80%; line-height: 1.5; padding: 1em 0; } .errorFooter a, .errorFooter a:visited { color: #657786; text-decoration: none; padding-right: 1em; } .errorFooter a:hover, .errorFooter a:active { text-decoration: underline; } #placeholder, #react-root { display: none !important; } body { background-color: #FFF !important; }

JavaScript is not available.

We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using twitter.com. You can see a list of supported browsers in our Help Center.

Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2023 X Corp.

Conversation

This is a long shot... but is there any way how to allocate such non-paged kernel memory, that MiScrubMemoryWorker (called by NtSetSystemInformation(SystemScrubPhysicalMemoryInformation, ...) won't touch it?

5

3

8

Why?

1

In short: when MiScrubMemoryWorker is triggered, it (roughly) unmaps some PTE, calls RDTSC and then maps the PTE again. Now when you have "blue pill"-like hypervisor and enable RDTSC trapping, it might crash, because some of the HV page is unmapped.

1

2

...so I was wondering whether there's simple hacky workaround this

1

going semi-type-1 when runtime is neither hacky nor simple but does work. I'm not sure how I should call this though, type 1.5? On the other hand, have you tried MmAllocateIndependentPages yet?

10:56 PM · Sep 6, 2019