A CS2 performance guide covering automated Windows 11 unattended installs, BIOS tuning, driver and Windows optimizations, and how to benchmark results honestly with frame-time analysis.
Key Takeaways
- Measure optimizations instead of trusting claims, and verify benchmark screenshots with full-screen recordings.
- Automated unattended Windows installation saves time on future reinstalls and gives control over setup choices.
- Frame-time spikes and 1% lows reveal performance problems that average FPS can hide.
- Many BIOS and driver tweaks have small or inconsistent effects, so repeated testing is essential.
What the video covers
- The creator claims a 1,200 average FPS benchmark score on the DUST2 map and promises a free, open-source, measurable optimization guide.
- The video warns viewers about faked benchmark results, such as kicking bots or leaving the console open, and recommends recording benchmarks on camera or OBS.
- It is sponsored by Skins.com, a peer-to-peer CS2 skin trading site, promoted with an affiliate link and promo code.
- A fresh Windows install is the starting point, with an unattended installation method using an autounattend.xml answer file to automate setup.
- The creator advises keeping LAN and Wi-Fi drivers on the bootable USB in case internet is unavailable after installation.
- Benchmark results from a fresh system are compared using average FPS, P1, 1% lows, and 0.1% lows, with frame-time graphs recommended over raw averages.
- BIOS settings discussed include SVM, EXPO/XMP memory profiles, and disabling SMT, which can benefit dual-CCD CPUs such as the Ryzen 7900X3D.
- Other points include PCIe lane sharing that can drop a GPU from x16 to x8, memory overclocking stability, and removing unnecessary background applications.
- The creator recommends running benchmarks multiple times across different days to ensure consistent, reliable results.
- For low-end PCs, enabling G-Sync, VSync, and NVIDIA Reflex together may improve frame pacing.
Chapters
- 00:00Benchmark intro and testing methodology
- 01:45How benchmarks can be faked
- 03:21Sponsor segment: Skins.com
- 04:20Automated Windows 11 installation setup
- 07:05Fresh install benchmark results and frame-time analysis
- 08:47Software cleanup and system optimization
- 10:40BIOS settings, SVM, SMT, and PCIe lanes
- 13:00Memory tuning, FCLK, and benchmarking consistency
- 16:40Low-end PCs and sync settings
Full Transcript — Download SRT & Markdown
Speaker A
1,200 average FPS and a score of 466P1. And no, this isn't an empty map. This is the DUT2 benchmark map in CS2. Over the past few days, or weeks, should I say, I've been testing everything from Windows optimizations and Nvidia drivers
Speaker A
to CPU overclocking, memory timings, all the rest of the BIOS settings, and even individual CPU cores. And some of the results generally surprise me. In this video, I'm going to take you through this entire process from a fresh Windows
Speaker A
installation to a fully optimized gaming PC. And here's what makes this video different. I built my own custom hardware to measure a lot of these things. So, any tweak which says this is going to reduce your latency. Well, I
Speaker A
can measure it and I can tell you whether it works or not. No, it's the same.
Speaker A
Everything in this video is free and open source and all the data will be publicly available. so you can verify the results yourself. And no, I'm not going to be asking you for a payment for an optimization pack. I'm not going to
Speaker A
ask you to install a sketchy custom operating system. And no, I'm not going to be selling you some registry tweaks in a Discord server locked behind the pay wall. And yeah, you also don't need my hardware to follow along. Whether
Speaker A
you're getting 150 fps, 300 fps, or 500 fps, the goal is to extract as much performance as possible from the hardware while also maintaining a security and stability. We're going to discover which optimizations actually work, which ones don't, and more
Speaker A
importantly, how you can test them on your own system. But before we get into any of that, there's something we need to address. Remember those benchmark results I showed you at the beginning?
Speaker A
What if I told you I could have faked the entire thing and you would have probably believed me. Let me show you how. So, the first thing I could have done is just simply kick the bots. Now, since the bots are gone, the benchmark
Speaker A
becomes quite less stressful on the CPU and voila, I have higher FPS. I could take the screenshot and fool everyone.
Speaker A
Second thing I could do is just keep my console open. If I keep my console open, there's kind of a bug. And at the end again, you're going to see that I get a lot higher FPS. So just wait for it and
Speaker A
there you go. Of course, you can evaluate the picture, but there are other ways to cheat it as well. So the best thing you can do is let's say you are looking for somebody to optimize your PC and they just send you a
Speaker A
screenshot. Tell them, hey, could you please just record the entire benchmark on a camera or OBS? Make sure build info is on and you can see the numbers and try to match it. Make sure the entire screen is visible and then you look at
Speaker A
the end screen. So this way you're sure that nobody's fooling you, nobody's trying to scam you, nobody's trying to, you know, milk your money. And that way you are going to be more sure. And don't worry, I've included the full benchmark
Speaker A
at the end of this video. And now this video took a lot of time and effort to make. So I really want to thank the sponsor who were lenient enough to give me a lot of time to make this video.
Speaker A
Skins.com is a peer-to-peer skin trading website where you can buy and sell CS2 skins with 0% fees or trade directly with other users. They support a wide range of regions along with plenty of deposit and withdrawal options including
Speaker A
crypto, Apple Pay, bank transfers, and more depending on your region. So whether you're looking to upgrade your inventory or cash out some old skins, check out skins.com using the affiliate link in the description or use my code kitchen. Let's start from the very
Speaker A
beginning. The Windows installation itself. I personally prefer an automated Windows installation. Not only does it handle almost the entire installation process by itself, but every time I reinstall Windows in the future, it saves me a considerable amount of time.
Speaker A
It also gives me control over things that a normal Windows installation doesn't. But before we get into that, I want to address custom operating systems. Could a heavily stripped version of Windows improve your FPS and more importantly your 1% lows?
Speaker A
Absolutely, it's possible. But here's my problem. Yeah, I don't have the expertise to audit an entire operating system. Verify that it doesn't contain malware, back doors, or potentially unsafe modifications. Downloading Windows 11 is kind of pretty easy, except for the part where Microsoft is
Speaker A
asking you so many questions and you waste a lot of time doing it. So what if instead of answering them each every single time, can we just create some file which answers it for us? Well, yes, we can. That's what's called an
Speaker A
unattended installation. And that's what we're going to be doing today. We're going to automate the complete setup and make our future Windows installations also a lot less annoying. First, we're going to be downloading the Windows 11 from Microsoft's official website. Make
Speaker A
sure you have a USB drive plugged in and let it do its thing. Just follow along the options just as shown and it's going to erase the USB by the way. So, make sure you back up your data. So, another
Speaker A
thing that I want to add is that you should always download your LAN driver and Wi-Fi driver and just extract it because you're not going to be able to extract it on a new system. So, just extract it and place it in your bootable
Speaker A
drive just in case you don't get internet, you can use it. Yeah. And there is a really easy way to generate your answer file. We'll be using a website for it. Now we are going to this website called I'm not even going to
Speaker A
attempt to pronounce that. So what does this website do? Well, basically it helps you generate an answer file. So what does the answer file contain? Well, it's an XML file that contains answers to a lot of the questions. So let's say
Speaker A
Windows wants to know what username you want to keep, which version of the Windows you want to install, which drive do you want to install in, which of these features would you want? Do you want to use a Microsoft account or you
Speaker A
just want the normal local account? Now, some of these options is better to keep it manual like selecting which drive you want to install your Windows in because on different computers you want to install Windows in different drives. So
Speaker A
this is the only option that I actually keep it manual and other than that these are my settings. I recommend you just copy them. You really don't have to think much about them. Once you're happy with the settings, download the file. It
Speaker A
will be called autoattend.xml and just copy it into the main directory of your bootable USB drive. And that's basically it. Windows now has the answers before it even starts asking the questions. Now boot from your USB drive and Windows setup will read the
Speaker A
configuration file automatically. For example, boot menu on my computer starts by F12. On your computer, it might be something else. Make sure you check your motherboard manufacturer and you'll find out. Uh depending on which options you selected, a lot of the setup will be
Speaker A
automated except the part where you install Windows right here. So, I'm just going to select here and just do my Windows installation. The best part is that you can reuse this USB every single time you reinstall Windows. Windows is
Speaker A
getting installed and it is really, really rather fast. And once it's installed, make sure you update your Windows. And then on a freshly installed system, you get an average of 820 FPS, a P1 of 315, a 1% low average of 286, and
Speaker A
a P 0.1 of 268.7. Having a look at these captures, we can clearly see there's so many frame time spikes. This is why I highly recommend not to use the data from the benchmark map itself, but to capture it using
Speaker A
CFrame X or just Presmon. This way you can see the individual spikes because sometimes you could get a P1 above 400 and yet have these frame time spikes and that doesn't tell the full picture, right? So make sure you visualize the
Speaker A
frame time using graphs. So you can see individual spikes. As you can see here, there's too many. So we're going to need to smooth those out. Next up, we have a chipset driver update. And quite honestly, it doesn't really improve your
Speaker A
performance, but I highly recommend that you do this. One of the things that brilliantly works on my computer is disabling core zero. I get a lot of FPS boost especially for the 1% lows like about 18 FPS which is really really
Speaker A
good. So you can use process lasso to do the same. Try it out. If it doesn't work for you just don't use it. But this is something that can help a lot of you gain some good stability. Just want to
Speaker A
add I'm just disabling one core over here since I have SMT on. You can see CPU 0 CPU 1. So it's like multi-threading. So, it's the same core, guys. Do not disable two of your cores.
Speaker A
Now, I also tried to see what happens if I just disable the game mode. Is it really going to change something? But it really doesn't. And I also use crystal at this utility because everyone keeps asking me how much does it improve. Now,
Speaker A
to be honest, when I'm running things on my own system, I'm just uninstalling things on my own. I never use a script, which is external. So, I just do it manually by myself. And that is what I recommend everyone doing. But you could
Speaker A
also just use a script. That's completely fine. Now, when it comes to cooling out my main PC, there's not really much of a difference. It's almost the same because my PC is quite cold and there's not really any thermal
Speaker A
throttling. However, if I try to do the same on my laptop, so I'm kind of using no cooling pad and cooling pad. And with cooling pad, you can see so much difference. 25% in the average, 32% on P1, almost 40% on 1% lows, and a 29%
Speaker A
change in P 0.1. Now the thing is after two or three benchmarks even with the cooling pad it still gets hot so the averages come down a bit. So this is something which you need to account for like I highly recommend do not use
Speaker A
laptops and if you're using them please get some sort of cooling pad that is going to drop down the temperature but but even though you get improvements after a particular period of time once you thermal throttle the improvements
Speaker A
are not really there. So I have been using the ultimate performance profile and when I use balance I get a slight improvement in performance. However, things will change again when we use PBO and other stuff. But on my 7900 X3D PC
Speaker A
like I need to use balance because it gives me almost 100 FPS more on the average. So don't blindly just put the ultimate performance profile because some PCs work better with balance profile. The reality is most of your
Speaker A
performance gains are going to come from four things. the hardware you're using, your cooling and thermals, overclocking and some BIOS optimizations, and finally, Windows and software optimizations. And generally, things are in that order. No amount of Windows tweaking is going to compensate for
Speaker A
inadequate hardware. Another thing people often overlook is PCIe lane sharing. Depending on your motherboard and which NVME slots you're using, your graphics card might be running at X8 instead of X16. That's actually the case with my own system. I'm willingly
Speaker A
sacrificing some PCIe bandwidth because I need multiple drives for content creation, storage, and different operating system. It makes my workflow significantly easier. But if you are building a PC purely for gaming, check your motherboard's manual and make sure
Speaker A
you're not necessarily sacrificing bandwidth. Also, make sure your PC has adequate air flow and that your components aren't thermally restricted.
Speaker A
So, don't keep your PC in a place where it's going to get really, really hot, you know. Now, before we start tweaking the BIOS, there's one more important thing you should know. What happens if you change a setting and your PC refuses
Speaker A
to boot? Don't panic. In most cases, you simply just need to reset your BIOS setting by clearing the COS. First, just turn off your PC, switch off your power supply, and completely disconnect the power cable. Then, hold down the power
Speaker A
button for a few seconds to discharge any sort of residual power. Depending on your motherboard, you have three options. You can use the clear cos button, short the clear cos pins, or simply remove the cos battery for a few
Speaker A
minutes. Once you've done that, reconnect everything and turn your PC back on. Your BIOS settings should return to their defaults. Also, whenever you're making changes in the BIOS, make sure you're saving your stable configuration as profiles. I would also
Speaker A
recommend exporting them to a USB drive if your motherboard supports it. That way, if something goes wrong, you don't have to start from scratch. Now that you know how to recover from a failed overclock, let's get into the real
Speaker A
optimizations. So the first thing I want to talk about is SVM, EMO secure boot.
Speaker A
Basically, every kind of virtualization and security related feature. Now before you disable any of these, understand that you're potentially trading security for performance and you cannot play Face It. So just know that if you're not going to be playing Face It and you just
Speaker A
want to play Premiere and you're kind of sure that hey I can manage my security you can turn these features off and you get a significant amount of FPS boost.
Speaker A
So now jumping over to PBO I use motherboard limits and I do plus 200 right over here and and I use just the curve optimizer on all coursees and I set it to -35. Now you should not copy
Speaker A
me directly. I've gone through the curve shaper. I've tried doing things on separate curves and this is what works the best for me. And it is going to be different on every single machine even with the same hardware. In fact, the
Speaker A
values could be different in summer and winter. That's just how it works. Like because it's an algorithm, it depends on temperature, right? So yeah, so you need to go in like -5, - 10, -15. So you go this way. Make sure you do your
Speaker A
stability testing in OCCT. Make sure you're having no clock stretching. To those of you who don't understand what clock stretching is, is basically the difference between your effective clock and your reported clock should be very less. And also even if your effective
Speaker A
clock is really really high, but you're not really seeing any performance improvements, you should just stop there. Uh there's no point in going any further unless you want to decrease your temperature further. So for me, minus 35 works well. My chip is kind of lucky
Speaker A
regarding this, but everything other than this, like my chip is the worst, my RAM is the worst, and still I'm able to get this performance. Another thing that I was kind of interested in seeing was BIOS update. And a lot of people say
Speaker A
don't use the latest BIOS, just use a little earlier version of Aessa because it gives more performance like by 10%.
Speaker A
So, I already had a older bias, but then I installed the latest one and there was no difference. So, yeah, just update your bias. When I used expert 2 and expert one, I was able to see a slight
Speaker A
performance boost, but I was using expert one because my kit is CL30 6,000. However, since it's like highex HD die, it's not really that strong. And when I was increasing my TEF values, it would really really get hot. So, I had to be
Speaker A
very conservative with a lot of my timing. But yeah, tuning my RAM gave me the best P 0.1. So, it really helped flattening all those stutters which were happening. So these are my RAM timings for anyone with an SI. These are quite
Speaker A
safe and you can use them. Funnily enough, I've not seen a single person make a SI video. So this might be the first one. So if somehow you're unlucky like me and you have an SI, well here you go. And yeah, enabling your spect
Speaker A
spectrum is supposed to reduce the electromagnetic interference. I did not see any improvement, so I just disable it.
Speaker A
Now, what about the core tuning config? Well, for me, I set it on legacy. As you can see from this benchmark, like it works better for me, so I use it. Now, if you want to disable SMT or enable X3D
Speaker A
boot and you don't do anything else, I highly recommend that you do it. Like a lot of systems are going to benefit immensely by disabling SMT. Like it happens with my 7900 X3D which is dual CCD. It even happens on my main system
Speaker A
9800 X3D even though it's single CCD. Like you still get better performance and you're able to go -50 PB or even -60 and you don't even get clock stretching.
Speaker A
However, I still do not use it because you're completely disabling multi-threading. So yeah, even though it gives me additional stability, additional FPS, and additional options, as a content creator, I'm not going to disable SMT, right? I'm not going to
Speaker A
enable X3D mode. But if you are not getting such a high FPS, this is something that you can experiment with.
Speaker A
And yeah, for some PCs, it's just going to work with process lasso. But on a lot of systems, you need to do it from your BIOS. I cannot stress it enough. Like, you're not going to see the performance
Speaker A
improvement until you do it from your BIOS. Now, I highly recommend you do not uh turn your BCLK higher unless you have an asynchronous clock. However, I did it. It resulted in better performance up till 101. After that, it started
Speaker A
degrading. And you should only do it if you have a asynchronous clock in my opinion. So, a lot of tweakers, they post the results at 1280 960. So, I thought I'll post them as well. But this is heavily going to depend on whether
Speaker A
you're GPU limited or CPU limited and by how much you are limited. Like a lot of people can actually see better performance at 1440p if they have like a 1490 but they have a really big CPU. So yeah, you just need to be aware about
Speaker A
these things whether your GPU limited, CPU limited and by how much. I also tried to increase my overall bandwidth by increasing the FLK values. However, this was not stable so I had to go back.
Speaker A
The average FPS did decrease but the stability was better. If your infinity fabric is kind of stable even at 2200, it could make a marginal enough difference for you. So now you may be wondering like how much FPS am I really
Speaker A
getting on face it? So for face it I'm getting around,42 average, 374 P1, 1% low of 353 and P 0.1 of 335. If it surprises you on the map itself like I get around 415 420ish. Another thing you're going to notice is the load line
Speaker A
calibration which I put on extreme and by default it's on auto and for me auto is like the highest low portion.
Speaker A
However, I don't really get any gain in performance. So, I just leave on auto which is like level one for me. Then I also want to see the results with the GPU overclock and I was just gaining average FPS. However, P1 and 1% loss
Speaker A
didn't really increase that much. Maybe at 1440p they would increase more but at 1080p and 1280 960 you only saw mostly increase in average FPS. So this is what the face performance looks for me. As you can see every single damn frame here
Speaker A
is lower than 4.5 milliseconds. So there's not really a very very big spike anywhere. Of course in game when certain networking commands are happening in the server like that and stuff your frame time is going to spike and that's not
Speaker A
your PC issue. That's just how CS2 works. Now, let's come back to the Windows optimization. I've already tested this. I think this was a long time ago. And as you can see over here, 41 gives the best value. But this is not
Speaker A
what you're thinking. It's not that you put 41, you get the best value because I remember testing it in the morning as well. And then something else was giving the most highest value. As you can see, the difference is not really large. Your
Speaker A
computer at the night and daytime can be a little bit different depending on the temperature. As I've already said, it's not really a change that I see at night, then I see at day, then I see another day. It's just a random change that
Speaker A
happens due to how computers work. Now, if you want to copy my GPU settings, so these are my settings actually 2250. I do not do any curve editor because my temperatures are already fine. So, I can go till 3 uh 25,500 here and I can go
Speaker A
till 350 here and I don't get any error correction or something but I just leave it here because like I don't really see any performance increase. So, why am I really pushing my GPU that hard? And of course, you want to make your power
Speaker A
limit 116 like whatever the full amount is so that uh you don't get limited at any point. Uh the GPU is working. So, yeah, you could also change your fan speed. For me, cooling is fine, so I don't really do that. And just remember,
Speaker A
this is for like my 5070 Ti. If you have some other GPU, just like increase by 50, 50, 50, 50 and see where you start getting errors or where you start getting diminishing returns or where your PC starts getting too hot. So,
Speaker A
here's my straightforward advice. If you want to get the maximum performance out of your own PC in CS2, first start with the clear Windows installation. I personally prefer you using a local account. Make sure you understand your Bit Locker settings and have your
Speaker A
recovery key backed up before making any major BIOS changes. Update your chipset driver and BIOS to the recent stable version. I'm not asking you to install something that came out yesterday. But don't blindly stick to an outdated BIOS
Speaker A
because someone on the internet claims that yeah, this one gives more FPS, right? So, newer versions can also address security vulnerabilities and stability issues. Remove the applications you don't need. Will this massively improve your FPS? No. Even on
Speaker A
my laptop, I haven't seen a meaningful difference, but there's no reason to keep unnecessary software running on your PC. Next, make sure your hardware is actually performing as intended.
Speaker A
Check whether your GPU is running at its intended PCI speed and lane width. Make sure your PC has proper air flow and you're not keeping it shut in some corner collecting dust. Cooling is extremely important. One of the reasons
Speaker A
my laptop performed so poorly was how quickly it was reaching its thermal limits. You can have incredible hardware, but if it's constantly thermal throttling, you're not really going to get the performance you paid for. Then comes overclocking and memory tuning.
Speaker A
Simply enabling Expo and XMP can give you decent performance improvement, but manually tuning your memory can make things go further. When I started with my unimpressive memory kit, my RAM latency was close to 100 nconds and I was able to improve that significantly.
Speaker A
But please do not try to copy someone else's aggressive timings and expect them to work perfectly on your PC.
Speaker A
Change things gradually. Document every single change. And most important thing is stability. Whether you're tuning your RAM, using Curve Optimizer, or overclocking your GPU, just because your PC boots doesn't mean it's stable. GPU overclocking can also help even at
Speaker A
128960. And this is probably the most important advice in the entire video. Test everything yourself. Maintain a spreadsheet, use Google Sheets, Excel, or whatever works for you. You can even take screenshots and give them to Chat CPT to organize your results. I'll also
Speaker A
link a video showing you how to automate the benchmarking process. Don't just run a benchmark once or twice. Run it five or 10 times. If the results aren't consistent, repeat the test on some of the days as well. I performed thousands
Speaker A
of benchmark runs for this video across two different drives. There are numerous tweaks I haven't even included because I cannot confidently say whether they are making a difference. You know, that's also why you'll see gaps in my test
Speaker A
number. Not every experiment produce a meaningful result. You need to establish what works on your PC, not on someone else's PC. Now, let's also talk about some of the tweaks you should avoid. You should not be using high launch option.
Speaker A
You should not be changing your GPU priority. And no, modifying your MSI interrupt is not going to reduce your input latency. I have done a lot of these tests already. You can watch these videos. I don't want to repeat the same
Speaker A
information and make this video longer. The same goes for most registry optimizations. I've tested countless registry tweaks and posted so many of those results on X. I haven't found anything convincing, repeatable performance improvements from whatever people are posting on the internet. Now,
Speaker A
talking about audio, just use like a wired headphone or an IM. And if you're experiencing some electrical interference, just use a decent external deck. But be careful with too much heavy audio processing like virtual audio mixer, special audio and additional
Speaker A
processing can introduce latency. For example, on my FYC 3, the FPS mode introduces considerable audio latency whereas 2AC 2.0 mode adds no measurable additional latency in my testing.
Speaker A
Unfortunately, you lose some of those extra processing features and unless you're measuring audio latency yourself, it's difficult to know exactly how much delay your audio setup is introducing.
Speaker A
Finally, what if you have a low-end PC? This is something I've actually changed my opinion on. And after spending some time playing CS2 on my laptop, if you're struggling with inconsistent FPS and terrible frame pacing, try enabling G-Sync, VSync, and Reflex together,
Speaker A
assuming your hardware supports them. They can be a small latency trade-off, but the improvement in visual smoothness can make the game a little bit more playable or enjoyable. It's not the best, but like you're already playing on trash, so might as well do something to
Speaker A
improve your situation, right? And that brings me to the entire point of this video. Stop blindly chasing some tweaks.
Speaker A
Start measuring it yourself on your own PC. Like even on my own PC, I do some tests at daytime, at night time, and the results are different, right? So imagine how different they could be on your own PC. Of course, you can take some advices
Speaker A
which are very logical and apply to everybody, but you should make sure that you test these things on your own computer. Maintain a spreadsheet, maintain some documentation, so some guy cannot say, "Hey, this tweak is going to increase your FPS or something like
Speaker A
that." So, as long as you have the data, you're sure about what is helping you and what is not helping you. That was the whole point why I started doing this because some guy was saying, "Hey, do this." And I'm like, "I'm trying to fix
Speaker A
my input lag." and and I type it the command and I feel like my input like oh maybe it improved and then you again face the same situation you're like hey maybe I'm a fool maybe I'm just placebo
Speaker A
and that's the whole reason I started this the whole reason I'm doing this was because I was struggling from a problem and every solution on the internet was stupid or lying or people were just you know paring the same information and it
Speaker A
made me frustrated you know so yeah so I just started testing my own things and that's what you should do as Well, like you don't have to test the input latency. You don't have to test the audio latency. But FPS testing, you
Speaker A
could do it yourself. You have softares like Pressmon, Crax. There's so many things that you could be using to test your FPS improvements. So yeah, I hope when it comes to the FPS part, at least you start doing it yourself. You see
Speaker A
something, you apply it, you do the automated benchmark, you could use my script, and that's going to make life so easy for you. So yeah, you can watch the benchmark after this. And I want to thank all the channel members who
Speaker A
support this channel. And if you like this video, make sure you give a like and subscribe. If you have some comment, comment down. If you think I'm wrong, just list it down. I'm sorry for yapping a bit here. Um, but uh these things were
Speaker A
important for me to tell you, you know. So, yeah, that's it. Uh, it's one there's no script, by the way. I'm just rambling off. I'll see you next time.
Topics:CS2FPS boostWindows 11unattended installationautounattend.xmlBIOS optimizationSMTframe time1% lowsbenchmark











![[1/11] William Lane Craig x Jamal Badawi – LEGENDADO — Transcript](https://i.ytimg.com/vi/_RIkWg4XuNk/maxresdefault.jpg)