I've expanded on my previous recommendations here: http://forums.guru3d.com/showpost.php?p=5298570&postcount=14 Check it out, lots of new goodies! I'm very sorry for abandoning the thread for so long. I suffer with insane levels of insomnia and generally feel like this smiley without the coffee :coffee:. I finally slept after 60 hours awake and happened to see a post about DPC latency earlier. Before I know it the post was done. That's just how I work. Also, I was wrong!: This is incorrect, I hadn't realized the LatencyMon is ONLY MEASURING DPC LATENCY ON CORES 0 & 1! That was why it appeared as if all the interrupts were going to those cores when they are probably going to all cores. I wonder if there is a sort of "scheduler' that decides which cores handle what DPC/ISR routines or if the program decides. Being able to manage which go where would be EXTREMELY advantageous in the fight against latency! MORE ON WINDOWS MEMORY MANAGEMENT! @johnathonm Sorry I dropped the ball on the Memory Management tweaks! I've been sitting on this for a while, I don't have enough information to say this is the best configuration, and in fact I cannot find a CLEAR ANSWER THAT MAKES SENSE on how to correctly calculate the IoPageLockLimit value for your amount of RAM, so I've disincluded that tweak from the recommended configuration entirely. That means this configuration is UNIVERSAL! You can use it on any PC with any amount of RAM. However, for a system running primarily as a server it MAY be better enable large system cache. And on a system where security is paramount it may be better to enable deletion of pagefile on shutdown at the cost of potentially increased shutdown time. (It may increase by almost nothing on a good SSD, but I've also seen some systems with SSD's take 3 or more minutes to shut down after enabling this setting). Don't be afraid to try smaller/larger values and experiment a little after reading from the links below! Most of the answers I've found on IoPageLockLimit conflict with each other or even themselves! Take for example this post by Onna. (Just above #8). What he says and the values he posts give us THREE DIFFERENT ANSWERS FOR THE SAME AMOUNT OF RAM!! I've PM'd back and forth with him and due to the language barrier have gotten no further in understanding what the fuc'k kind of logic he's using to set this value. If we follow these instructions from him for 16GB: "Your RAM MB* 1024 * 0.125 *2 = ??", we end up with a decimal value of 4194304. We enter this value and select Hexidecimal which turns it into a value of 400000. That's what I'm using. - "IoPageLockLimit"=dword:00400000 I put it on the line below DisablePagingExcutive. Yet even though he says his configuration is for 16GB ONLY, his value looks like this: Code: "IoPageLockLimit"=dword:0040e100 Then he throws another curve ball at us with even more conflicting information that gives us two more different values for the same amount of RAM RIGHT THERE ON THE SAME LINE: :bang: So from this single post has already given us three separate "correct answers" for what value to use if youhave 16GB: Code: "IoPageLockLimit"=dword:00400000 "IoPageLockLimit"=dword:0040e100 "IoPageLockLimit"=dword:7cf83000 Which one is it Onna? Which one is the REAL value for 16GB? :bang: Feel free to quote me and ask him yourself. I give up. He doesn't understand that we don't understand, if he did I'm sure he would just simply write the answers for 4, 8, 16, and 32GB to get it over with. The language barrier makes it impossible. Here are the links to most of the information I used to help me find the best values for everything else, and get a little more confused with IoPageLockLimit (Yes there are EVEN MORE ways to calculate the value, such as the "Your RAM amount -64MB" rule from Microsoft, but they didn't date the article so it could be from 2006 and entirely inapplicable). (On another note, yes I have read plenty of negative things claiming IoPageLockLimit dos not do what we think it does, but these claims are extremely outdated and have no sources or logical reasons as to why this is the case). There are a lot of conflicts. My exact recommended configuration doesn't match any of these guides exactly. But that's because no guide I've read has all the best answers. http://www.registryrecycler.com/blog/2013/07/enhance-windows-memory-management-through-registry/ https://technet.microsoft.com/en-us/library/cc951698.aspx http://forums.laptopvideo2go.com/topic/23980-registry-database-tweaks-optimizations/ Anyway, to merge these changes simply create a text file and rename it with a .reg extension. This is my latest configuration and I recommend it over the ones posted above! Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management] "ClearPageFileAtShutdown"=dword:00000000 "DisablePagingExecutive"=dword:00000001 "LargeSystemCache"=dword:00000000 "NonPagedPoolQuota"=dword:00000000 "NonPagedPoolSize"=dword:00000000 "PagedPoolQuota"=dword:00000000 "PagedPoolSize"=dword:00000000 "PhysicalAddressExtension"=dword:00000001 "PoolUsageMaximum"=dword:00000060 "SecondLevelDataCache"=dword:00000c00 "SessionPoolSize"=dword:00000080 "SessionViewSize"=dword:00000060 "SystemPages"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters] "EnablePrefetcher"=dword:00000003 "EnableSuperfetch"=dword:00000003 "SfTracingState"=dword:00000001 For now if you want to try to use a value for IoPageLockLimit I'm going to say calculate it like this: [Your RAM in MB] * 1024 * 0.125 * 2 = [IoPageLockLimit Value in Decimal. Enter into regedit first then select hexidecimal so it converts.] Here are the values already converted to hexadecimal for your convenience! Simply copy and paste the corresponding line into the main configuration and merge. No need to even open regedit. 2GB: "IoPageLockLimit"=dword:0080000 4GB: "IoPageLockLimit"=dword:00100000 6GB: "IoPageLockLimit"=dword:00180000 8GB: "IoPageLockLimit"=dword:00200000 12GB: "IoPageLockLimit"=dword:00300000 16GB: "IoPageLockLimit"=dword:00400000 24GB: "IoPageLockLimit"=dword:00600000 32GB: "IoPageLockLimit"=dword:00800000 64GB: "IoPageLockLimit"=dword:01000000 128GB: "IoPageLockLimit"=dword:02000000 *NOTE* I may be completely and entirely wrong about this method! Don't worry, Windows sets any incorrect/incompatible values back to default.