Are there issues with latency on a Surface Laptop?
Are there issues with latency on a Surface Laptop?
Surface Pro 7+ Dual-core 11th Gen Intel® Core™ i3 Model, 2.5 years old was bought new (that's the most info I could find regarding adding to this section)
Disk drive(s): make, model, capacity, how full?
Model SAMSUNG MZ9LQ128HBHQ-00000
Size 117.85 GB (126,537,953,280 bytes)
Free Space 10.41 GB (11,176,402,944 bytes)
List of all connected peripherals.
Microphone: RODE NT1-A Condenser Microphone
Interface: UAD Volt II
Headphones: Beyerdynamic 770 Pro 80 OHM Closed-Ear Headphones
XLR Cable: Mogami Gold
XLR Splitter: Roland RCC-YC-XF2XM
Connected to wireless network with router I'd say somewhere around 15-20 feet away
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:33:56 (h:mm
s) on all processors._________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: VOWORKCOMP
OS version: Windows 11, 10.0, version 2009, build: 26200 (x64)
Hardware: Surface Pro 7+, Microsoft Corporation
BIOS: 32.103.143
CPU: GenuineIntel 11th Gen Intel® Core™ i3-1115G4 @ 3.00GHz
Logical processors: 4
Processor groups: 1
Processor group size: 4
RAM: 8033 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 2995 MHz
Reported CPU speed (registry): 2995 MHz
Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.
_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.
Highest measured interrupt to process latency (µs): 1223.40
Average measured interrupt to process latency (µs): 27.952339
Highest measured interrupt to DPC latency (µs): 1210.60
Average measured interrupt to DPC latency (µs): 10.537510
_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
Highest ISR routine execution time (µs): 547.037730
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Highest reported total ISR routine time (%): 0.125363
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%) 0.125363
ISR count (execution time <250 µs): 2345503
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 45
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs): 1205.561937
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation
Highest reported total DPC routine time (%): 1.559435
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 2.228435
DPC count (execution time <250 µs): 5166988
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 4761
DPC count (execution time 1000-2000 µs): 7
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.
NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
Process with highest pagefault count: firefox.exe
Total number of hard pagefaults 108394
Hard pagefault count of hardest hit process: 15314
Number of processes hit: 185
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 242.296827
CPU 0 ISR highest execution time (µs): 547.037730
CPU 0 ISR total execution time (s): 7.253634
CPU 0 ISR count: 2252364
CPU 0 DPC highest execution time (µs): 1205.561937
CPU 0 DPC total execution time (s): 160.516251
CPU 0 DPC count: 3797447
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 56.108664
CPU 1 ISR highest execution time (µs): 306.363940
CPU 1 ISR total execution time (s): 2.954842
CPU 1 ISR count: 93049
CPU 1 DPC highest execution time (µs): 1030.957596
CPU 1 DPC total execution time (s): 15.846565
CPU 1 DPC count: 1026952
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 21.548828
CPU 2 ISR highest execution time (µs): 68.844741
CPU 2 ISR total execution time (s): 0.004494
CPU 2 ISR count: 135
CPU 2 DPC highest execution time (µs): 970.429382
CPU 2 DPC total execution time (s): 2.793429
CPU 2 DPC count: 189915
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 19.590501
CPU 3 ISR highest execution time (µs): 0.0
CPU 3 ISR total execution time (s): 0.0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 952.080801
CPU 3 DPC total execution time (s): 2.387388
CPU 3 DPC count: 157442
_________________________________________________________________________________________________________
Hi! So I do voiceover work on my Surface Pro 7+ laptop, and was recommended to use Latencymon to see if I was potentially having any problems with my computer. I've had the same result pop up a couple times (though the note about network popped up after having done some other steps), and I'm not sure what I can do to improve it at this point. I've affirmed that at least as of right now all drivers and BIOS have been updated as much as they can (there's a preview for a new Windows update available but I have not installed it), I've done as much as I can to better CPU usage without disabling CPU throttling, is there anything else that I can do at this point to help improve my computer's runtime and lower the amount of popping in my recordings?
Surface Pro 7+ Dual-core 11th Gen Intel® Core™ i3 Model, 2.5 years old was bought new (that's the most info I could find regarding adding to this section)
Disk drive(s): make, model, capacity, how full?
Model SAMSUNG MZ9LQ128HBHQ-00000
Size 117.85 GB (126,537,953,280 bytes)
Free Space 10.41 GB (11,176,402,944 bytes)
List of all connected peripherals.
Microphone: RODE NT1-A Condenser Microphone
Interface: UAD Volt II
Headphones: Beyerdynamic 770 Pro 80 OHM Closed-Ear Headphones
XLR Cable: Mogami Gold
XLR Splitter: Roland RCC-YC-XF2XM
Connected to wireless network with router I'd say somewhere around 15-20 feet away
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:33:56 (h:mms) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: VOWORKCOMP
OS version: Windows 11, 10.0, version 2009, build: 26200 (x64)
Hardware: Surface Pro 7+, Microsoft Corporation
BIOS: 32.103.143
CPU: GenuineIntel 11th Gen Intel® Core™ i3-1115G4 @ 3.00GHz
Logical processors: 4
Processor groups: 1
Processor group size: 4
RAM: 8033 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 2995 MHz
Reported CPU speed (registry): 2995 MHz
Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.
_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.
Highest measured interrupt to process latency (µs): 1223.40
Average measured interrupt to process latency (µs): 27.952339
Highest measured interrupt to DPC latency (µs): 1210.60
Average measured interrupt to DPC latency (µs): 10.537510
_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
Highest ISR routine execution time (µs): 547.037730
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Highest reported total ISR routine time (%): 0.125363
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%) 0.125363
ISR count (execution time <250 µs): 2345503
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 45
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs): 1205.561937
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation
Highest reported total DPC routine time (%): 1.559435
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 2.228435
DPC count (execution time <250 µs): 5166988
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 4761
DPC count (execution time 1000-2000 µs): 7
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.
NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
Process with highest pagefault count: firefox.exe
Total number of hard pagefaults 108394
Hard pagefault count of hardest hit process: 15314
Number of processes hit: 185
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 242.296827
CPU 0 ISR highest execution time (µs): 547.037730
CPU 0 ISR total execution time (s): 7.253634
CPU 0 ISR count: 2252364
CPU 0 DPC highest execution time (µs): 1205.561937
CPU 0 DPC total execution time (s): 160.516251
CPU 0 DPC count: 3797447
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 56.108664
CPU 1 ISR highest execution time (µs): 306.363940
CPU 1 ISR total execution time (s): 2.954842
CPU 1 ISR count: 93049
CPU 1 DPC highest execution time (µs): 1030.957596
CPU 1 DPC total execution time (s): 15.846565
CPU 1 DPC count: 1026952
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 21.548828
CPU 2 ISR highest execution time (µs): 68.844741
CPU 2 ISR total execution time (s): 0.004494
CPU 2 ISR count: 135
CPU 2 DPC highest execution time (µs): 970.429382
CPU 2 DPC total execution time (s): 2.793429
CPU 2 DPC count: 189915
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 19.590501
CPU 3 ISR highest execution time (µs): 0.0
CPU 3 ISR total execution time (s): 0.0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 952.080801
CPU 3 DPC total execution time (s): 2.387388
CPU 3 DPC count: 157442
_________________________________________________________________________________________________________
Are there any recorded problems with the computer or your voiceover functionality?
If not, the reported errors might be false negatives or unrelated.
Keep it simple: "If it ain't broken, don't fix it."
However, I did observe your reference to "popping" in recordings. This could result from loose connections, ground loops, static, etc.
Please update your post with full system hardware details and operating system information.
Specify the power supply unit: make, model, wattage, age, condition (original, new, refurbished, used).
List all connected peripherals such as microphones, speakers, headsets, amplifiers, etc.
Mention whether the network is wired or wireless.
More information would be helpful.
It is suggested to use Latencymon to check for any potential issues with the computer.
Are there any recorded problems with the computer or your voiceover functionality?
If not, the reported errors might be false negatives or unrelated.
Keep it simple: "If it ain't broken, don't fix it."
However, I did observe your reference to "popping" in recordings. This could result from loose connections, ground loops, static, etc.
Please update your post with full system hardware details and operating system information.
Specify the power supply unit: make, model, wattage, age, condition (original, new, refurbished, used).
List all connected peripherals such as microphones, speakers, headsets, amplifiers, etc.
Mention whether the network is wired or wireless.
More information would be helpful.
Frizzy_Fizz500
03-26-2021, 07:08 AM #3I've noticed some issues with buzzing and popping lately, though it seems unrelated to my own experience. The buzzing might actually come from outside the building. I'll add all of these updates later! 🫡
Hammerkirby123
03-26-2021, 08:16 AM #4I made the adjustments to include the details you asked for. I managed to capture as much as possible from what was available.
Size is 117.85 GB (126,537,953,280 bytes). Free space is 10.41 GB (11,176,402,944 bytes).
This seems to be the boot drive C: – correct?
There are two clear issues based on the laptop’s specifications:
1) The storage is insufficient for Windows 11, even if it functions; it doesn’t meet modern software needs.
2) It’s nearly full, with only 8.8% free space. I prefer drives to stay between 20-30% free.
As the disk fills up, files become fragmented—split into pieces and scattered across the drive wherever available. This affects performance and could contribute to the problem.
If your voice-over-work is memory-heavy, the software might temporarily move or swap data between RAM and virtual memory on the nearly full disk.
It’s worth noting the laptop has 8 GB of RAM, which is usually enough for most operating systems and applications today.
= = = =
Disk space...
Size is 117.85 GB (126,537,953,280 bytes). Free space is 10.41 GB (11,176,402,944 bytes).
This seems to be the boot drive C: – correct?
There are two clear issues based on the laptop’s specifications:
1) The storage is insufficient for Windows 11, even if it functions; it doesn’t meet modern software needs.
2) It’s nearly full, with only 8.8% free space. I prefer drives to stay between 20-30% free.
As the disk fills up, files become fragmented—split into pieces and scattered across the drive wherever available. This affects performance and could contribute to the problem.
If your voice-over-work is memory-heavy, the software might temporarily move or swap data between RAM and virtual memory on the nearly full disk.
It’s worth noting the laptop has 8 GB of RAM, which is usually enough for most operating systems and applications today.
= = = =
1. LatencyMon ran for just shy of 34 minutes, in that time you had 108,394 hard page faults spread across 185 processes. That's more than 53 hard pages faults per second, and that is huge. Hard page faults occur when a requested page is not in RAM and has to be paged-in from the pagefile. This requires a disk I/O operation, so it's painfully slow. This alone will cause your system to run slow, it may even account for the audio issues if it's an audio process that takes a few page faults.
The basic cause of these hard page faults is because you are running a bigger workload than the installed RAM can handle. If the pagefile setting is not set to automatic then change it to automatic pagefile size, though you may not have the disk space for that. Since it's effectively a tablet I don't think you can install more RAM(?) and that means your only option is to reduce the workload. Run fewer apps at the same time, don't have lots and lots of browser tabs open at the same time...
2. The delay that LatencyMon looks for is primarily in the Interrupt Service Routines (ISR) and Deferred Procedure Calls (DPC) aspects of device interrupt processing. In your case the longest running ISRs (the front-end of interrupt processing) was WDF01000.sys, the Windows Kernel Mode Driver Framework Runtime. This is a set of libraries used by many third-party drivers, so the cause of the long running ISR is going to be in a third-party driver that uses the WDF libraries. Unfortunately LatencyMon can tell you no more than that.
Your longest running DPCs (the back-end of interrupts processing) was ndis.sys, the Windows high-level networking driver. The cause of delays here is almost certainly the lower level wireless adapter driver, so look for an update to this driver. Note that this driver may well use the WDF libraries and so may account for the long running ISR as well.
However, despite the above your main problems are that you're working the tablet way too hard. The SSD is too full for comfort and there isn't enough RAM for the workload you're running. If you can't upgrade the SSD and RAM in there then you either need a more powerful laptop or a significantly smaller workload.
I certainly agree with the above that the free space on your system drive is way too low, but there are other things in there of concern
1. LatencyMon ran for just shy of 34 minutes, in that time you had 108,394 hard page faults spread across 185 processes. That's more than 53 hard pages faults per second, and that is huge. Hard page faults occur when a requested page is not in RAM and has to be paged-in from the pagefile. This requires a disk I/O operation, so it's painfully slow. This alone will cause your system to run slow, it may even account for the audio issues if it's an audio process that takes a few page faults.
The basic cause of these hard page faults is because you are running a bigger workload than the installed RAM can handle. If the pagefile setting is not set to automatic then change it to automatic pagefile size, though you may not have the disk space for that. Since it's effectively a tablet I don't think you can install more RAM(?) and that means your only option is to reduce the workload. Run fewer apps at the same time, don't have lots and lots of browser tabs open at the same time...
2. The delay that LatencyMon looks for is primarily in the Interrupt Service Routines (ISR) and Deferred Procedure Calls (DPC) aspects of device interrupt processing. In your case the longest running ISRs (the front-end of interrupt processing) was WDF01000.sys, the Windows Kernel Mode Driver Framework Runtime. This is a set of libraries used by many third-party drivers, so the cause of the long running ISR is going to be in a third-party driver that uses the WDF libraries. Unfortunately LatencyMon can tell you no more than that.
Your longest running DPCs (the back-end of interrupts processing) was ndis.sys, the Windows high-level networking driver. The cause of delays here is almost certainly the lower level wireless adapter driver, so look for an update to this driver. Note that this driver may well use the WDF libraries and so may account for the long running ISR as well.
However, despite the above your main problems are that you're working the tablet way too hard. The SSD is too full for comfort and there isn't enough RAM for the workload you're running. If you can't upgrade the SSD and RAM in there then you either need a more powerful laptop or a significantly smaller workload.
When I ran Latencymon, I was limited to recording with Audacity and having Firefox open in a browser. I found out that the update prevents me from removing it myself, but under advanced settings in Windows Update it lists a driver update I can download here:
https://www.catalog.update.microsoft.com...27bc01e5a4
It’s unclear where this applies since my device manager and system info don’t show a Realtek USB device. My connection uses a USB-A port, so maybe that could help? Connecting it to an Ethernet cable might also improve stability during live sessions.
I don’t think adding more RAM is feasible due to the device’s slim design and lack of cooling fans—this was intentional to avoid noise in my workspace. I’m not sure how much I can afford a replacement or where to start next. It’s been two and a half years, and it’s really frustrating now.
Thank you for your feedback! I managed to clear a significant amount of files and my storage is now at 71% capacity (34GB free), but I'm still experiencing audio issues—more pronounced than before I began troubleshooting. After installing the latest Windows update on the Surface Pro 7+, I've noticed a noticeable slowdown. Examining my installed applications reveals a large number of new Surface-related software that I don’t fully understand.
When I ran Latencymon, I was limited to recording with Audacity and having Firefox open in a browser. I found out that the update prevents me from removing it myself, but under advanced settings in Windows Update it lists a driver update I can download here:
https://www.catalog.update.microsoft.com...27bc01e5a4
It’s unclear where this applies since my device manager and system info don’t show a Realtek USB device. My connection uses a USB-A port, so maybe that could help? Connecting it to an Ethernet cable might also improve stability during live sessions.
I don’t think adding more RAM is feasible due to the device’s slim design and lack of cooling fans—this was intentional to avoid noise in my workspace. I’m not sure how much I can afford a replacement or where to start next. It’s been two and a half years, and it’s really frustrating now.
You may review the contents of the zip file before uploading, as most files are text documents. Avoid modifying or removing anything. For a detailed explanation of each file, refer to the provided link.
Gravewalker21
04-15-2021, 06:18 PM #9If you wish, download the SysnativeBSODCollectionApp and place it on your Desktop. Execute it and upload the generated zip to a cloud service using the provided link. The app aggregates all available troubleshooting information, enabling us to understand the situation even without BSODs. It does not gather any personal data.
You may review the contents of the zip file before uploading, as most files are text documents. Avoid modifying or removing anything. For a detailed explanation of each file, refer to the provided link.
https://mega.nz/file/qqRwgBoZ#cCIZb5VR-y...00lQ84Uczw
I do want to note that a bit before you sent this reply last night, I had done some troubleshooting on my own. I did update the driver that my computer had suggested, and I cleared up some of the apps that the last Windows update installed that I verified that I would not need. It did install a couple of random updates after I did these things, but nothing that required a restart.
I had some auditions I wanted to try and record for last night, so I started Latencymon up again and kept watch of my Latencymon's activity as well as Task Manager. I think the biggest culprit of my computer running so slow is Windows Defender. It was at the top with an insane amount of pagefaults, and causing at minimum 200MB of memory to be consumed consistently. I followed a guide to turn off its' ability to run at top priority as well as try to make it so it isn't doing a full system check constantly, and I managed to record for 6 minutes with Latencymon not noticing any problems!! Yay!! Unfortunately, Windows Defender started back up afterwards and caused popping in the next batch of recording I did. From what I did last night that seems to be, at the very least, a huge source of my computer running slow, if not the main culprit.
Alright! I did so, here's my zip file!:
https://mega.nz/file/qqRwgBoZ#cCIZb5VR-y...00lQ84Uczw
I do want to note that a bit before you sent this reply last night, I had done some troubleshooting on my own. I did update the driver that my computer had suggested, and I cleared up some of the apps that the last Windows update installed that I verified that I would not need. It did install a couple of random updates after I did these things, but nothing that required a restart.
I had some auditions I wanted to try and record for last night, so I started Latencymon up again and kept watch of my Latencymon's activity as well as Task Manager. I think the biggest culprit of my computer running so slow is Windows Defender. It was at the top with an insane amount of pagefaults, and causing at minimum 200MB of memory to be consumed consistently. I followed a guide to turn off its' ability to run at top priority as well as try to make it so it isn't doing a full system check constantly, and I managed to record for 6 minutes with Latencymon not noticing any problems!! Yay!! Unfortunately, Windows Defender started back up afterwards and caused popping in the next batch of recording I did. From what I did last night that seems to be, at the very least, a huge source of my computer running slow, if not the main culprit.