DarkerSquirrel

Thanks a lot for quick look into this, Sina. Other things that come to mind related to this: 1. Doing this quick test from a driver (instead of a process)...

Ok , thanks , I will test the dev branch in few hours and let you know. Just speaking out loud some redundant info in case someone is reading this...

Well, as quick dirty fix , what about disabling all cores but one? Would that make the issue go away? As a longer term fix, I think making a robust...

Thanks a lot for explanations, Sina! Let's assume that a process reads KUSER_SHARED_DATA + 0x10; Are you kind enough to write how should I modify this script to print that...

Yes , I am 100% sure I use latest git, I pulled origin last night. OK , tested some more, I realize now the issue, The issues I reported aren't...

I am not using it in debugger mode cause I think that implies to run the debugged program inside a VM, right? That doesn't work for this case, cause I...

I think the docs state that .pagein command is just for debugger mode. I solved it in another way , I opened game in x64dbg, bp at entry point, loaded...

I can't reproduce the issue reliably. In order to trigger this , try something like: start a process with a big dll(my dll is 350 MB large) i x64dbg, bp...

I made sure it's available by reading it often from another process using ReadProcessMemory(). I tried also monitoring just some sections of dlls, much less, let's say a span of...

I think these are heisenbugs, cannot reproduce them anymore. But you are right indeed , !monitor fails for large mem span , it is awfully slow. I managed to trace...