Guide: DPC Latency

Hellbovine

Well-Known Member
Does your computer have frame rate stuttering, audio drop-outs, or other noticeable problems while playing a game or working on audio production? If so, it may be due to high DPC latency, which is an extremely important topic that often gets overlooked in gaming websites, forums, and benchmarks.

DPC stands for Deferred Procedure Call, and is a very technical subject, but this guide is going to make it as simple as possible. If a computer has DPC issues, it is because a driver is having difficulty processing data in a timely manner. Basically, a driver is saying "Hit the pause button, I cannot handle all of this!" Communication between devices then becomes congested, causing performance to suffer.

Depending on how big the "pause" was, the consequences could be as minor as a quick audio drop-out or "crackle/pop" noise, a more moderate effect of frame rate stuttering, or it could be so bad that a driver freezes and you get a blue screen of death. These are just some examples, and other similar effects can occur, as well as multiple effects together.

Because there are numerous causes of DPC latency, it is not practical to list them all individually, and this guide must teach readers how to troubleshoot them instead. Google is your friend while working through this guide, so do not be afraid to lookup things you are unsure of to learn more.

DISCLAIMER
Before you get started with this guide, make sure to backup all of your important files so that in the event you make a mistake it does not cause you to lose anything. Troubleshooting can be volatile, you may end up needing to install Windows again, and some major DPC problems actually require this as a mandatory step, so it is also best to prepare a Windows install USB in advance too.

Create a list of every part in your computer because you will need to know what hardware you have in order to optimize everything properly. If you are not sure how to do this, you can download a program like Speccy from Piriform to assist.

It is important to know that there are differences between a desktop and a laptop regarding DPC latency. A laptop's purpose is convenience, to carry around for basic tasks like word processing and web browsing, they are not for gaming or audio production, and "gaming" laptops are just marketing hype. There are many reasons for these disparities, but all that matters is laptops usually have much higher DPC than their equal desktop counterparts.

STEP 1: RECORD DPC DATA
In the following steps we will discuss how to check the DPC levels in a computer.

1A) Download the latest version of LatencyMon from the official source (https://www.resplendence.com/downloads).

1B) Find the downloaded file, right-click on LatencyMon and select "Run as administrator" to install it, and follow the prompts. Uncheck the option to launch LatencyMon at the end because we are not ready yet. You can delete the downloaded file after the install is finished.

1C) Before running LatencyMon, reboot the computer. Wait about 2 minutes for Windows to finish initial background activities at the desktop, then right-click the LatencyMon shortcut and select "Run as administrator" to load it. Maximize the window so that it is full-screen. All of the default settings in LatencyMon are good and do not need editing.

1D) Click the green "Start monitor" button at the top left and then take your hand off the mouse and keyboard. Once the timer has reached 5 minutes press the red "Stop monitor" button at the top left. Now we have DPC data we can evaluate.

Note: all recordings should be ran for 5 minutes, performed only after a reboot, and while the computer is idle, without other programs running.

STEP 2: DIAGNOSE DPC ISSUES
Identifying a problem is fairly easy, using some guidelines. Anything spiking over 100 microseconds (or 0.1 milliseconds) can be problematic. If something is reaching into the hundreds or thousands of microseconds it will almost assuredly manifest as a problem somewhere, even if you do not overtly notice it, and the performance of the system will be hindered. To get started, we need to identify the most troublesome driver first.

2A) The "Main" tab is a quick summary of the latency spikes that are occurring in the system. Look at the text labeled "Highest reported DPC routine execution time" and you will see a number, such as 1098.145234 which indicates how long the "pause" was for. In the parenthesis to the right of it there will be a driver file name, such as ndis.sys and that is the driver responsible for the spike.

2B) The "Drivers" tab gives us a detailed look at every driver installed and how high each of them is spiking, as seen in the "Highest execution" column. This number can be slightly confusing because it is now in milliseconds, and so a value of 1.098145 in this column for ndis.sys is exactly the same spike we saw on the first tab.

STEP 3: UNDERSTANDING DPC ISSUES
To fix these problems we have to understand why they are happening. Underneath all of the user interfaces are countless lines of code that have an infinite number of ways a developer can make a mistake, and even if all the code is working as intended users can create problems through operator error by doing something that developers cannot reasonably plan for. The three major sources of DPC issues are listed below.

3A) BIOS: this is where a lot of mistakes are made, for two main reasons. One is that people will overlook it and use the defaults, which are not optimized for gaming or audio production, thus not optimized for DPC latency. The other problem is that people will haphazardly change settings, which can make things worse than the defaults.

3B) Drivers: these are often the cause of problems, and also where a lot of operator error occurs, because too many people are using 3rd party driver installers or Windows update. The way Windows update matches your hardware to a driver is not always accurate. For example, if I let Windows update run on my desktop computer it will download a 2 year old graphics driver instead of the latest, as well as attempting to install incorrect chipset drivers. On my laptop, Windows update tries to install half a dozen incorrect drivers, including an optional monitoring app that causes an error every reboot.

3C) Windows: as the operating systems have grown over the years they have more code running than ever before, naturally increasing the chances of a conflict occurring, leading to DPC issues. This increased background activity also consumes more resources, which decreases overall performance too. All of the new power saving and virtualization features being added in each update also greatly contributes to decreased performance.

STEP 4: BIOS OPTIMIZATION
Enter the BIOS during a reboot to configure it, which usually requires a function key to be pressed, such as F2. If a mistake is made and it is preventing the computer from booting, a few methods for resetting the BIOS exist. There is a reset to defaults option in the BIOS menu, it can also be reset by removing the CMOS battery from the motherboard (turn off power first), or reset by putting a jumper over the appropriate pins.

4A) Reset the BIOS to defaults. Be sure that any boot configuration options you manually changed before, such as IDE/AHCI mode or UEFI/CSM do not get altered in this process or you will be forced to install Windows again. If you have serious DPC issues though, this may be part of the problem and perhaps using the default boot options and installing Windows again will be how you fix things. Lastly, take note of the BIOS version for the next step, then save these changes and exit, allowing the computer to boot back into Windows.

4B) After the step above, go online and check the manufacturer website for your motherboard and download the latest BIOS update. Follow the instructions and install the new BIOS. After the update is done, you need to reset the BIOS to defaults one more time, then save and exit, before going back into the BIOS and manually configuring any settings.

4C) BIOS settings have little documentation, and the fastest way to figure out what something does is to write down literally every setting and Google them to learn more. You can also download the PDF manual for your motherboard and it may explain the settings in more detail. There are too many settings over the years to list them all, so it requires some experimentation to figure out the best combination for your computer. Below are some commonly tweaked settings related to performance:

- Disable Enhanced Halt State (C1E)
- Disable OS ACPI C3 Report
- Disable OS ACPI C2 Report
- Disable Intel SpeedStep Technology or AMD equivalent
- Disable integrated graphics (if a GPU is installed)
- Disable unused devices (e-sata, serial ports, etcetera)
- Disable Intel Turbo Boost Technology or AMD equivalent
- Toggle Intel Hyper-Threading or AMD equivalent
- Toggle XMP Memory Profile or AMD equivalent
- Disable Virtualization Technology and VT-d
- Disable Intel Dynamic Power Technology or AMD equivalent
- Set Processor Power Efficiency Policy to High Performance
- Disable Intel Smart Connect Technology or AMD equivalent
- Disable Intel Rapid Start Technology or AMD equivalent
- Disable Deep S4/S5
- Disable PCIe ASPM Support
- Disable Native ACPI OS PCIe Support

Note: the basic premise is to disable unused features, power savings, and settings that cause the processor clock speed to fluctuate, as these are things that create DPC issues. Also, it is recommended to enable Execute Disable Bit (NX) since it is required for DEP (Data Execution Prevention) and some anti-cheat software, and could get you banned if it is disabled. Lastly, enabling HPET does not force the timer, it only allows the timer to be available to Windows if it is needed, and some benchmarking software requires it.

STEP 5: DRIVER OPTIMIZATION
The main remedy to fix a bad driver is to uninstall the culprit then replace it with a better one. There is one big problem though that causes interference in modern operating systems, and that is forced Windows updates, as previously explained in the "Understanding DPC Issues" section. To combat this, there are a few options that should be pursued, such as integrating registry keys to prevent Windows update from forcibly installing drivers, unplugging from the internet, or booting into safe mode without networking.

5A) Update all hardware firmware. Similar to BIOS, firmware is the code that is built onto the actual hardware. Many devices have firmware updates available, such as optical drives, graphics cards, solid state drives, internet routers, etcetera. The easiest way to find these is to type in the model number at the manufacturer website and specifically look for "firmware" downloads. Take the time to check every single piece of hardware connected to the computer, both internally and externally.

5B) Check that all of the required drivers for the computer are actually installed. To do this, access the "Device Manager" which can be found in the Control Panel, then check for any yellow exclamation marks which indicate that a driver has not yet been installed and the device is running in limited capacity. Some of the device names are easy to recognize, but others will require a Google search to figure out what they are. Install any missing drivers and see if that fixes the issues.

5C) After all missing drivers are installed, go uninstall any problematic drivers indicated in LatencyMon, reboot and then replace the bad driver and see if that fixes the issues.

Note: only download the latest, official drivers from the hardware manufacturer, you should not be using 3rd party driver packs, modded drivers, or Windows update for drivers. Also, be sure to always right-click and "Run as administrator" when installing a driver. For some drivers you have the option of using the manufacturer version or the one that comes from the designer. For example, Realtek Audio supplies a generic sound driver, but some hardware manufacturers will provide a customized version. In situations like these, try both and see which one works better.

STEP 6: WINDOWS OPTIMIZATION
The goal here is to disable as much power savings as possible, reduce the background activity, and stop things like Windows update from taking control of the computer. This step is where the NTLite program shines, because all of these settings can be integrated into a custom Windows so that it is optimized right out of the box after a clean install, rather than doing all of this manually or with scripts. I also have a guide on how to create an optimized Windows image that you can use, which has all of these tweaks included already.

6A) The general guidelines for improving performance are listed below, though the individual steps are not shown because they vary between operating systems. Below are some of the commonly tweaked settings, and you do not have to do all of them, but each one will either improve DPC or reduce the overhead of Windows, thus improving performance:

- Disable troubleshooters/diagnostics
- Disable telemetry everywhere (Windows, apps, drivers, etcetera)
- Enable the "High performance" power plan
- Adjust advanced power settings to disable power savings features
- Disable/pause Windows update
- Disable automatic updating everywhere (apps, drivers, etcetera)
- Disable antivirus (Defender)
- Disable firewall
- Disable advanced security features
- Disable virtualization
- Disable indexer
- Disable sysmain (superfetch)
- Disable internet novelty features (dynamic wallpaper, suggestions, ads, etcetera)
- Reduce visual effects (DWM settings)
- Disable all syncing (OneDrive, Microsoft Account, etcetera)
- Disable all startup apps (do not automatically start programs after reboot)
- Remove all forms of file compression and encryption
- Disable pagefile or set it to a static amount

6B) All standard versions of Windows operating systems have now reached end of life, except for W10 and W11. As time goes on, more programs (games, browsers, etcetera) will stop working on older operating systems, so keep that in mind when choosing one. If you are building a computer, it is also important to know that older operating systems may not support the latest technology or have drivers available for new hardware.

6C) When it comes to W10 versus W11, the benchmarks I use show W10 being equal or pulling slightly ahead of W11 in some cases, and I highly recommend testing both operating systems to see which one has lower DPC latency on your machine, as I found W10 to have lower average latency and fewer spikes than W11. This may be hardware dependent though, and since license keys are interchangeable between them, it is worth taking the time to test this and see which is best for you. Also, W11 is new, it takes several years for operating systems to mature and stabilize, and Microsoft is actively evolving W11 which can make tweaking it more difficult as they change or add new features.

6D) The final bit of Windows advice is to upgrade hardware, but be sure to allocate money where it matters the most. The single biggest improvements that can be made to speed up Windows is ensuring that you are at least using a solid state drive or better, as well as 8 GB memory at a minimum, along with a good processor that has a high single-threaded performance rating. These three pieces of hardware are important because it is where the bulk of all communication happens, and bottlenecks here can severely affect everything else in the computer.

STEP 7: OPTIMIZATION SUMMARY
The goal here is to take everything learned up to this point and combine it into a final solution. The following is a summary of how I optimize computers for gaming, and is also what I do after building a new computer:

7A) Cleanly install a default Windows or an optimized image, and be sure to delete the previous partitions during Windows Setup. This is only going to be a temporary operating system so that we can do the next steps. Even if an installation of Windows already exists on the drive it is best to start fresh, as this eliminates a ton of problems right away since broken and bloated Windows installs are very common.

7B) Update motherboard BIOS and optimize settings, as discussed in the "Bios Optimization" section.

7C) Update all hardware firmware, as discussed in the "Driver Optimization" section.

7D) Download all of the latest, official drivers that are required for the computer, as discussed in the "Driver Optimization" section. Copy these to a USB and set it aside for now.

7E) Install an optimized Windows image with your chosen tweaks, as discussed in the "Windows Optimization" section. At a minimum, Windows update should be paused, with automatic driver downloads disabled, and the power plan set to High performance. Unplug the internet before install to create a local account (do not tie the computer to a Microsoft Account) on Windows 10, or integrate the bypassNRO tweak to do this on Windows 11.

7F) Once you reach the desktop after the last step, check LatencyMon and diagnose the DPC levels. There should not be any issues at this point, but if there are they need to be fixed now. After any problems are fixed, proceed by installing only 1 driver, then reboot and run LatencyMon to check for conflicts, stopping to address any problems before repeating this process with the next driver.

PREVENT FUTURE ISSUES
Once you have a freshly installed Windows, with all of the required drivers, and no DPC issues, the next thing to think about is how to prevent problems as you move forward, since this is also where a lot of operator error comes from. At this point, everyone starts to install all of their games and other software they use on a daily basis. A minimalist approach here is the best way to ensure that the performance of your computer does not degrade over time. The biggest mistake I see on gaming machines is all of the unnecessary bloatware. Examples of this include the following:

- MSI Afterburner
- Nvidia GeForce Experience
- Razer Cortex Game Booster
- Bitsum Process Lasso
- Driver and software assistants (Dell, HP, etcetera)
- Unused/optionally downloaded .NET Frameworks
- Too many others to list

The other important thing to do, is take the time to customize all of the software being installed. An example of this would be the Steam, for playing games. There are numerous settings to configure in apps like these and all of the unused features should be disabled, along with automatic updates, startup on reboot, and anything else that consumes resources or bandwidth.

For more guides like this one, visit the following link:
https://www.ntlite.com/community/index.php?threads/gaming-lounge.2999/
 
Last edited:

Hellbovine

Well-Known Member
Before replying to this guide, please keep the following in mind.

Tech Support:
This is not a DPC support forum. Members are not paid to help others, so please respect that by following directions and putting in real effort into trying to figure things out on your own first, using Google and the information from this guide.

The guide will fix the vast majority of DPC issues if it gets followed properly. It is obvious when someone does not read through everything or chooses to skip steps, so do not be lazy and ask us to troubleshoot your problems if you have not gone through the entire guide yet. Please let me know if there are any mistakes in the guide though, or if something needs to be clarified or added.

Computers are complicated and require effort, especially gaming computers. Guides like these are designed to teach people the skills they need to be successful on their own, so in the future they can troubleshoot problems without a guide. This thread is not intended to be a place for the internet to come and dump their DPC issues for us to fix--if that happens, it will be met with annoyed responses and the thread will eventually be locked.

Nvidia Display Driver:
If you are coming here because of DPC issues with your Nvidia driver, see this thread (link) and this one (link) for more information. Both threads had to be locked because they grew rapidly and too many of the participants were not following directions. At this point in time, Nvidia has finally paid attention to this bug that has been around for years, and put it on their known issues list. This is clearly a bug that Nvidia and/or Microsoft have to address, since there are no universal tweaks a consumer can do to workaround it, so all we can do is wait for it to be fixed. There is nothing to be gained by continuing to discuss the topic, so do not post about Nvidia in this guide's thread or the posts will be deleted.
 
Last edited:

Clanger

Polisher Extraordinaire
Staff member
Nvidia Display Driver:
If you are coming here because of DPC issues with your Nvidia driver, we have a separate thread dedicated to that (link). Please don't post in that thread until you've read through all the links on the first post of page 1. Right now there is no known, universal solution, for fixing that driver.
That thread is now locked because users continue to ignore your requests and garlin's requests/warnings.
 

Hellbovine

Well-Known Member
Re: Nvidia Display Driver (nvlddmkm.sys)

For anyone that was following the Nvidia thread, or now this one, I wanted to make a note about what to expect in the future for all of the people that were patiently waiting for a solution. I'm still going to be working on trying to solve the Nvidia bug on my own, and will keep people updated on that.

If you have non-Nvidia DPC issues, follow this guide as written and it should solve everything. If not, post here and we'll work through a solution and then I'll update this guide with that information. If your only issue is the Nvidia driver, then keep checking back about once a week, and if a solution is found I'll update the original post on page 1 of the locked Nvidia thread by changing the text at the very top to say "Resolved" with a link to the solution, as well as adding a note to this guide.

I think we're actually narrowing in on an Nvidia solution, and I'm hopeful, because a small handful of people have solved it, they just cannot reproduce it. Last night, I too managed to get a 5 minute LatencyMon run where nothing spiked above 80, even the Nvidia driver, but I also could not reproduce it. I think this is because these are partial fixes, and the bug requires a multipronged solution. With this in mind, I have a number of ideas I want to try, but it's all a very time consuming process, and a refined solution could still be days, weeks, or months away.
 
Last edited:

aurox87

New Member
Dropping this here as I think you are interested in this (and because the other thread got nuked):

From the changelog of the most recent NVIDIA driver (528.49)

Open Issues in Version 528.49 WHQL
...
1676071700025.png
...

Let's hope for the best! Also the gist of my continued testing:
  1. Win11 22H2 got worse DPC latency than Win10 / Win 11 21H2 (we knew that already)
  2. Disabling C-States (and maybe more of the stuff you suggested in STEP 4: BIOS OPTIMIZATION) lowers the IDLE latency a good amount (but does not fix the nvlddmkm.sys spikes)
  3. Enabling "Prefer maximum performance" in the general tab of the NVIDIA 3D settings dialog fixes the latency spikes from nvlddmkm.sys, at the expense of more power draw due to the GPU not downclocking when IDLE
 

Hellbovine

Well-Known Member
Win11 22H2 got worse DPC latency than Win10 / Win 11 21H2
This is my finding too, which is why I recommend W10 over W11. This could be hardware dependent though, so I encourage people to try both and see which one works best for their machine.

Enabling "Prefer maximum performance" in the general tab of the NVIDIA 3D settings dialog fixes the latency spikes from nvlddmkm.sys
I don't think this is entirely accurate, as everyone that tried it in the DPC thread would say it either made no difference, or it helped, but didn't solve it (still spikes anywhere from 200-600). You are right though that it substantially increases the heat output of the cards. My card's temps increase by over 30 degrees fahrenheit when it's set to prefer maximum performance globally.
 
Last edited:

aurox87

New Member
I made a thread the other day about that. I meant to include a reply here with a link to it, but forgot. My apologies.
https://www.ntlite.com/community/index.php?threads/nvidia-dpc-bug-news.3348/

Ah, my apologies in that case for duplicating that information here :-/

Let's hope they fix that problem in time, it has been a thing for way too long. Funny that it has to do with the power states of their (newer?) GPUs.

This is my finding too, which is why I keep recommending W10 over W11.

Unfortunately (or fortunately I should say) I bought a HDR OLED gaming monitor recently and the HDR support in Win10 is just... bad. They made big improvements in Win11, so I'm sticking with 21H2 for the time being. While NVIDIA is trying to figure out how to fix their power state problem I'm learning how to create custom images with NTLite so I'm prepared to switch to 22H2 once they fix it! ;)
 

Clanger

Polisher Extraordinaire
Staff member
Problem also happens with older gpus like my GT710. there has been no new drivers since december and it looks like older gpus are being/going to be ignored.
 

aurox87

New Member
I don't think this is entirely accurate, as everyone that tried it in the DPC thread would say it either made no difference, or it helped, but didn't solve it (still spikes anywhere from 200-600). You are right though that it substantially increases the heat output of the cards. My card's temps increase by over 30 degrees fahrenheit when it's set to prefer maximum performance globally.

Oh it absolutely did for me, just make sure you restart your computer after setting "prefer maximum performance" in the *global* 3D settings. I still got spikes to 300us max (less frequently), but not the 2000-3000us ones. If you would try it again (do a restart), I'd love to hear the result.
 

Hellbovine

Well-Known Member
Oh it absolutely did for me, just make sure you restart your computer after setting "prefer maximum performance" in the *global* 3D settings. I still got spikes to 300us max (less frequently), but not the 2000-3000us ones. If you would try it again (do a restart), I'd love to hear the result.
I do believe you, what I mean though is 300 is not actually "fixed", and this is where a lot of people were getting hung up in the Nvidia thread too. I made a post about it here (link) that explains it in more detail, though that post could still use more clean up too.

Sorry if I sounded like I was just naysaying you, I only meant to clarify the "fixed" wording, because it was a constant issue in that thread, which was a huge part of why I created this DPC guide and why the Nvidia thread got locked, because this information wasn't getting across to the masses very well. The baseline for the Nvidia driver is actually in the hundreds, people with spikes from any driver into the thousands almost assuredly have general DPC issues that need to be addressed. Drivers interfere with each other, so the extremely sensitive Nvidia driver spikes into the thousands when something else isn't configured optimally in the machine.

Now with that being said, there are tons of ways to remedy DPC issues, so one person may find great success in using the "prefer maximum performance" in the Nvidia control panel, while others can find the same success by optimizing their BIOS or using a better power plan. I don't see major differences on my machine when changing the Nvidia control panel setting because the rest of my system is optimized which achieves the same effect. The goal of the Nvidia thread was to figure out how do we get an optimized machine down into the double digits, instead of the hundreds. Only about 4 people claimed to be able to do this, but none of the solutions could be replicated by those claimants, or by other people.
 

aurox87

New Member
I get your point. For me the 300us spikes seemed "normal" and "fixed", but of course one can (and should) ask the question what "normal" actually is. Unfortunately I went with a 13900KF, so I can't boot my PC without the 4090. Would be interesting to see what the baseline of 21H2 / 22H2 is with C-states disabled and no NVIDIA card installed.

I have to disagree though with your statement, that something else is wrong on your system if you get spikes into the thousands with the NVIDIA driver. I've swapped out the motherboard, RAM and hard drives by now. New displays, new display cables, multiple fresh installs of Windows in different versions with and without tweaks and different drivers. It's always spiking into throusands with my 4090 on 22H2 until I disable downclocking via the prefer maximum performance setting. I've also seen numerous reports in the NVIDIA forums and on reddit from people with a 4090 with exactly the same Latency Mon graph. I am certain at this point that different generations of NVIDIA cards behave differently in regards of P-states and DPC latency.

I'd love to get my hands on say a GTX 2070 to verify my theory, but I can't justify the effort / money just to test.
 

Clanger

Polisher Extraordinaire
Staff member
I got a LaMon screen grab for a clean w7(updated to end of extended support), no added drivers, it reports 3 video drivers, all at 0, zero, us(i cant do that funny symbol). only tweak was a bcd - enable msi mode, nothing else.

Capture.PNG
 
Last edited:

AI_vs_M$

New Member
Informative, there're a few things not being dicussed, but we can start with this:

In computing, an Interrupt Request (IRQ) is a signal sent to the processor by a device, indicating that the device needs attention. When two or more devices share the same IRQ, they must take turns using it. This is called a shared IRQ. Shared IRQs can cause conflicts and affect the system's performance.

One area where shared IRQs can have a significant impact is in the area of Deferred Procedure Calls (DPCs) in Windows. DPCs are software routines that the operating system uses to handle time-critical tasks, such as disk I/O and audio processing. When a DPC is executed, it takes control of the CPU and prevents other DPCs from running until it has finished. This is where the problem arises: if two devices that share the same IRQ generate DPCs at the same time, they can conflict with each other, causing a delay in processing and an increase in DPC latency.
Managing your shared IRQ devices is important to avoid these conflicts and keep your system running smoothly. One way to do this is to assign different IRQs to each device. This can be done through the device manager in Windows. Another way is to disable devices that are not being used. This frees up IRQs and reduces the chances of conflicts.

In summary, shared IRQs can affect DPC latency in Windows, which can lead to performance issues. Managing your shared IRQ devices is important to avoid conflicts and keep your system running smoothly.

Also, changing your (actual) hardware placement around can have a significant impact on your performance, especially when taking into account iconsitencies in BIOS or similar. Yup, it should not matter, but sometimes it does, sue somebody! We're NOT talking, only in the sense, of shared IRQ's either.

I recently had an ASUS motherboard, that provided the wrong voltage, to the CPU if you did not manually set its values.

Another way, is to install with the bare minimum approach. This way, you physically remove hardware and add it as you go. Doing this gives you a better baseline, and you can prioritize hardware to make it easier to pinpoint the actual bottlenecks of your system."
 
Last edited:

Necrosaro

Active Member
Informative, there're a few things not being dicussed, but we can start with this:

In computing, an Interrupt Request (IRQ) is a signal sent to the processor by a device, indicating that the device needs attention. When two or more devices share the same IRQ, they must take turns using it. This is called a shared IRQ. Shared IRQs can cause conflicts and affect the system's performance.

One area where shared IRQs can have a significant impact is in the area of Deferred Procedure Calls (DPCs) in Windows. DPCs are software routines that the operating system uses to handle time-critical tasks, such as disk I/O and audio processing. When a DPC is executed, it takes control of the CPU and prevents other DPCs from running until it has finished. This is where the problem arises: if two devices that share the same IRQ generate DPCs at the same time, they can conflict with each other, causing a delay in processing and an increase in DPC latency.
Managing your shared IRQ devices is important to avoid these conflicts and keep your system running smoothly. One way to do this is to assign different IRQs to each device. This can be done through the device manager in Windows. Another way is to disable devices that are not being used. This frees up IRQs and reduces the chances of conflicts.

In summary, shared IRQs can affect DPC latency in Windows, which can lead to performance issues. Managing your shared IRQ devices is important to avoid conflicts and keep your system running smoothly.

Also, changing your (actual) hardware placement around can have a significant impact on your performance, especially when taking into account iconsitencies in BIOS or similar. Yup, it should not matter, but sometimes it does, sue somebody! We're NOT talking, only in the sense, of shared IRQ's either.

I recently had an ASUS motherboard, that provided the wrong voltage, to the CPU if you did not manually set its values.

Another way, is to install with the bare minimum approach. This way, you physically remove hardware and add it as you go. Doing this gives you a better baseline, and you can prioritize hardware to make it easier to pinpoint the actual bottlenecks of your system."
We just need to wait till Nvidia comes out with some fixes and no need to do much right now till then unless you are having issues.

I am done with it till that time.
 

Hellbovine

Well-Known Member
Updated post no 17 to include Windows 10.
I don't think it's possible for the display driver to have 0's, especially after that long (1 hour). If you sort the columns by "Total execution" time and look at all the ones that do have numbers above 0, I'm wagering your integrated graphics will appear, meaning it's what is actually being used to display your desktop. If you disable integrated graphics at the BIOS then run the test again, it will allow the AMD display drivers to be used.
 

Clanger

Polisher Extraordinaire
Staff member
Hellbovine that sounds reasonable, i'll give it a try. If not tonight then tomorrow, its late here.
But the monitor is connected to the r5, not the onboard igpu connector, will try anyway, hell, i got this damn far,,,,

Edit - im on an F cpu, i aint got no igpu, will switch in the bios anyway.
Edit - Bios is set to pci slot.
Edit - card is set to msi mode automatically after driver installation.
 
Last edited:

Hellbovine

Well-Known Member
Open YouTube and play a video for a few seconds while LatencyMon is running, does the display driver go above 0? If not, I think there is a problem somewhere, like autologgers that are needed are disabled, or something along these lines. I just don't know how it's possible to get 0's across the board on a driver that's in-use 24/7.
 
Top