LatencyMon: A top-end system struggles with processing live sound?
LatencyMon: A top-end system struggles with processing live sound?
It would be beneficial to take out one RAM stick for a few days, then swap them back for a few days. Check if latency improves with just one stick. One aspect I’m unsure about is your hard page fault rate – these are pages that triggered a page fault from the pagefile. In a 12-minute 15-second test, you’re experiencing over 28 page faults per second. Even after removing blender.exe, you’re still seeing around 14 hard page faults per second. That seems unusual. The second latency monitor output shows a more typical hard page fault rate. Both the longest ISR and the longest DPC are linked to the Wdf01000.sys driver, which is the root driver for the Windows Driver Foundation. Only this driver is affected; the other drivers aren’t. You may want to submit the complete kernel dump—it’s possible we can identify the driver there. The file is located at C:\Windows\Memory.dmp and is quite large. I can also analyze the long-running DPCs from that dump if needed.
I just considered that maybe the defender would apply if it scanned the drive. I was trying to understand why we think it's related to a page file rather than other files on the disk. I still don’t fully grasp how it’s detecting him with 98GB of RAM—this isn’t a recognized issue in the program. It’s not a known bug. Its RAM... so it shouldn’t be functioning properly. It didn’t create any additional page file. The pattern remains consistent, two scans, same result.
I don't possess a Memory.dmp file; do you have another method available to obtain the data you require? I do have a report in LiveKernelReports, but it reflects my network adapter after initiating fast boot.
That is unusual.
there should be one. Its set up be default
Do you use cccleaner as it can delete it automatically if allowed to.
https://learn.microsoft.com/en-us/window...-live-dump
<< shows how to create one
something has been using page file, unless you set a fixed size, as with your ram amount it should never be used unless you using more ram than you have.
I have 32gb ram, and page file auto set and only 2gb.
Yours is 15.6gb so something uses it.
Do you operate a garbage cleaning tool? Similar to Disk Cleanup or Ccleaner? If you're generating minidumps, a memory.dmp file should exist as well.
Please enter the Run command sysdm.cpl
Select the Advanced tab
Click the bottom Settings button
Share a screenshot of that window.
I performed an advanced system check recently, which likely cleared it.
What storage drives do you have?
Just thinking, take different tack on this... its all drive activity so maybe check drives health and see if its not cause of any of it. It probably isn't, just best not to ignore anything
a page fault is when CPU needs data from Ram
a Hard page fault is when it needs it off Drive.
Defender scanning drive is likely to cause lots of them, by its very actions.
So changing the page file size and limiting it to just 32gb doesn't help when you have 98gb of ram, its meant to be able to grow to the size of your ram IF it needed all of it. Right now, limiting it could lead to Out of Memory Errors.
windows won't use it unless it needs it, hence mine is only 2gb. If I needed it, it could grow.
it appears to be set up right, you just need to create one now.
I have three 2TB M.2 drives:
Western Digital WD_Black SN850X 2 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
I will perform a disk check.
Here is the dump:
https://www.dropbox.com/scl/fi/zsg2...ey...a0hl7ametg&st=zkoyxijx&dl=0