Double check your PSU cables are plugged in correctly at both ends (PSU side and components). Also, if you didn't plug the AC wall cable in properly at the back it can cause problems on some PSUs from my experience. If you can use a known good power supply to test

Double check you plugged things into the motherboard correctly (fans, front usb, power/reset etc)

Double check your graphics card to see if it is plugged in all the way into the PCI-e slot and the power is plugged in properly too.

I agree with you, though i did use regular DDR3 on this computer for a good year at least prior to this and i'm still going strong.

But since i couldn't run 2133 or loosen timings any primary timings at 1866, i tried going to the regular 1.35v and it is actually stable. I suppose it doesn't say 2133 was supported.

Also I reran the benchmark at 3.7GHz for comparison. Gained about 27fps overall.

After a bit of research, ive been able to locate some of the RAM settings in my BIOS. Honestly you should try tweaking RAM as well as CPU clock speed if you want improved fps.

Before I had no access, I had 1600Mhz DDR3 at 11-11-11-28. All i did was bump up voltage from 1.35 to 1.5, increased frequency to 1866MHz and increased tREFI to the max. Wasn't able to get 2133 working with my limited knowledge though unfortunately no matter how much i loosened the primary and secondary timings.

CPU: Intel Core i7 5700HQ @ 3.6GHz (HT on) core affinities 2-7
RAM: 16GB DDR3 11-11-11-28 @1.5V and 1866MHz
GPU: NVIDIA GeForce GTX 960M 2GB stock with 417.35 drivers
CFG: Mastercomfig low v6.10 @ DXLEVEL 81
Res: 1024x768, Fullscreen

3.6GHz

As a comparison before at 3.7GHz

Launch options:
-novid -noipx -threads 4 -nod3dex -w 1024 -h 768 -softparticlesdefaultoff

Windows 10 1809 x64 Home
No fullscreen optimizations
One single display

I wasn't seeing 100% CPU utilization on any active cores relating to TF2 before. Now i see much closer to 100%, which i speculate is due to NVIDIA and their copy system to the system RAM (optimus bleh). I say this because before I was getting lower FPS the higher resolution I went. Before I was getting about 21GB/s in memory tests at 80ns. Now I can get 26GB/s at 69ns. May be i'm wrong and these are expected gains from RAM tuning idk.

On an NVIDIA optimus system using Windows 7 with default driver settings i've seen FPS increases with lower mat_viewportscale values. But once you use NVIDIA profile inspector and change shim rendering mode to "SHIM_RENDERING_OPTIONS_ENABLE_DWM_ASYNC_PRESENT" i no longer see this behaviour and avg framerates are increased by a lot.

But I still see FPS scaling with lower resolutions, with avg FPS increasing by about 15 at lower resolutions. Probably because I have slow memory.

CPU: Intel Core i7 5700HQ
Graphics Card: NVIDIA GeForce GTX 960M

Driver version: 375.63
dxlevel (default is 90): 81
Resolution: 1024x768
Full-screen or windowed: Full
FPS configs enabled: Mastercomfig v6.7.0 low preset
Shadows enabled/disabled: disabled

3.5GHz default

3.7GHz

EDIT: appears I had badgpu addon enabled which ate a few fps

3.5Ghz default

3.7GHz

Additional notes:
Only -novid in launch options
2x 1080p displays
Windows 10 Version 1803 64 Bit
Dual channel DDR3 also

I had exactly your problem with a similar configuration. After the fall creators update my fps was hard capped at 60fps no matter what and I couldn't play the game unless it was in windowed mode.

What I did to fix it was reinstall windows 10 completely (I installed all my graphics drivers offline so I lowered my chances of windows getting its own from windows update). I then disabled the game bar and disabled fullscreen optimizations on hl2.exe (right click hl2.exe -> properties -> compatibility -> disable fullscreen optimizations) and then I had the fps i expected to get. Maybe this would help fix your problem?

Also maybe batteryboost is somehow interfering with this when its hard capped at 60? Just a thought. hope this works for you

ive used throttlestop before to change my cpu frequency down a bit when turboed up and it has worked, also intel XTU worked for me similarly. not sure of the effects of these programs long term but ive had no issues using them.

if you want your cpu to stay at top performance just set the power plan to high performance in power options

all of the default crosshairs are located in 1 vtf file. Open the tf2_textures_dir with a vpk viewer, go to materials -> sprites -> crosshairs.vtf. Then you would have to extract the default scout crosshair from that.

"cl_croshair_file default" and the rest of the crosshairs are one file and are located in the same textures vpk at materials -> vgui -> crosshairs -> default.vtf

[*]

BibleThump

sideshow's stream ends and so does my life FeelsBadMan ̿̿ ̿̿ ̿̿ ̿'̿'\̵͇̿̿\

Having no luck with one or both of them in launch options

I'm on a laptop with NVIDA Optimus enabled on Windows 10, and no matter what I do i can't for the life of me get stretching to work at any resolution while ingame.

Because NVIDIA Optimus is on, I can't get access to normal NVIDIA control panel things, such as stretching the resolution to fit the panel. But when I go into Intel's control panel, it stretches the resolution I want on the desktop just fine, but TF2 and CSGO have black bars, despite whatever panel settings I put in and what graphics processor I'm using.

I have the latest drivers on NVIDIA and Intel's side. I know it can do stretching of non-native resolutions because in the BIOS it seems to do this. I am in fullscreen mode. Any help would be appreciated. I have NVIDIA driver version 361.91 and intel driver version 20.19.15.4331 if that matters.

Any help is appreciated. Thanks!

delete his c:/ drive

I personally think that both teams were in the wrong. MF9K should of waited until Acooma rejoined the game. Acooma is a great spy, and they could of won the round. The rule of 5 minute pause is retarded. If someone needs to install a new driver or an other hardware or real life event, that could take longer than 5 minutes, it just doesn't work. Anyways, MF could of easily waited for Pulse or Acooma, but apparently ruwin left GC for some reason which I dont know about, and I suspect that might be one of the factors for that unpause