DjinnKiller

also locking the framerate must be done.......... their is multiple ways you can lock the framerate. 1. ENB have a framerate lock, found in their ENBlocal.ini File 2. Msi Afterburner - Rivatuner (My Personal Choice) for me this is much more prefeered, as msi afterburner has a lot of very useful additions such as hardware monitoring. now for me personally i have never had any major issues with msi afterburner with regards to crashing the game, in the many years i have used it, not too mention it running along side ENB for both skyrim and Fallout, we are talking 7+ years. as i also used to run msi afterburner back in Skyrim LE days (2012) to current 2019 fallout 4. i have always ran ENBs and heavily modded games for both Skyrim LE, SE and Fallout 4, and always ran Msi i am a power user (Power user/ Pc Enthusiast) and as such constantly monitoring my hardware, eliminating anything that would affect performance, and optimizing for maximum performance (basically the definiation of a power user), and since i have always had a 60hz monitor i have to lock framerate for every game i play to 60, due to my 1070 easily pumping out 90+ fps on a heavily modded fallout, even higher framerates in other games i play, and as i cannot stand screen tearing, i must lock my games to 60 fps, and msi (Rivatuner) does it perfectly and never fails. so just writing that extra bit to prove that msi afterburner is essential. What G4M3W1NN3R says....... Loosing sync is almost always caused by high FR's..... @OP a FR of 140 will mess the game up.

Amen brother! :smile: I've been playing games for 40 years (Atari, VIC20, ZX81/ZX Spectrum, CP/M based computers anyone?), and I can't remember the last time I disabled anti-malware software on a Windows PC, maybe back in the early days of Win 95, Win 98 and Win XP......? Regarding load times, yeah, my RAID0 with a sequential read speed of around 6.5 GB/s vs RAMdisk didn't make much of a difference. (Would be cool to test with a couple of more NVMe's in the stripe set though :devil: ).

The loading times of FO4 is not susceptible to magic, black or otherwise. Two factors heavily influences your LT. One, your hardware (the biggest one). Two, frame rate (after you get the hardware above a certain level). I run a setup with around 170 mods, some of them are fairly heavy texture mods, I typically load around 6-7GB of VRAM. My loading times, loading a save or new areas typically resides in the 5-30 sec range. As another poster here said, the loading is dependent on frame rate . How much of a difference you'll actually notice depends on your hardware. I disable the frame rate manually between load screens, and have FO4 installed on RAID0/Stripe Set with two Samsung 970 PRO 1TB NVMe SSD's. (With a RTX2080Ti and a 2950X Threadripper). Depending on what it loads the FR mostly fluctuates in the 700-950 range during load (some low valleys in the 300 range, and some peaks in the 1000-1200 range) And then there is the engine, even with the FR removed I hit a bottleneck because the engine can't fully utilize hardware above a certain level. I even loaded most parts of the game into a RAMdisk, and it didn't change the LT from my RAID0...... So, fast hardware will get you to good LTs (when removing the frame capper), but then, above a certain point you hit a wall. EDIT: This is with Windows 10 1909 64-bit, and with Windows Defender with stock settings. Disabling anti-malware software will not increase your load times, but it will make your computer less secure.

I have no statistics, but remember the first releases of Windows 7. There was problems to be sure, but it became very good down the line. Switching off core security features like Defender is a non-issue for me, I don't do it, but ymmv. Defender scores pretty high in the latest tests and and at work we use Defender ATP in combination with the full security stack from Azure (Office ATP and Azure ATP). Can't say that this has caused any major problems both on my private PC's or at work, rather the opposite. I have the impression that Defender is rather well behaved, but again, no solid statistics to lean on.

Yeah, I've been using Windows 10 64-bit both private and professionally since at least release 1703. And while Win10 in many areas have it's problems, I would sure as shite have heard about an artificial limitation like that in the OS. (Having users with professional grade multi-display solutions, 4-8 displays with combinations of 27-32" monitors up close and large wall-mounted displays in the 50-70" range)

They didn't. The case (back around 2016) was much more convoluted with a mix of Win8, Win10, DX9-games, 32-bit vs 64-bit, potential driver issues (both Nvidia and AMD), and so on and so forth. Ie. the usual confusion and FUD on this beautiful thing called the Internet.... :)

That game engine is dung heap of epic proportions, and it can't utilise the hardware in any efficient way. And if it wasn't for all the absolutely brilliant modders on Nexus, I would have ditched this game a very, very long time ago. Btw, I've drastically cut down on my load times by binding the fps limiter in my ENB to a key. When the load screen starts I push the key to remove the limiter (thanks to a tip from RedRocketTV), the fps goes up to anything from 400 to 900 fps and the load screen takes 3-5 seconds. In heavy areas, maybe 10-15 secs....huge difference. When the loading has finished I enable the limiter again. Doesn't solve the fps problem in-game, but at least no more endless waiting...... :)

And You would be correct, in the title screen the engine is essentially "freewheel burning". That number, while funny to look at, has little implication on the game.I have 1200+ fps in the title screen, I still get low thirties in some bad areas (Trinity Tower anyone) with full mod loadout.

Thank you very much for the update. Sorry to hear it didn't fix your problem, that is a bummer. And, thanks for the links, they are stored for future reference. :)

I've done both and haven't noticed anything either way. But (my usual disclaimer) ymmv. Just make a backup, test and if it goes pear shaped, roll it back.

The load time is in some insane way also connected to the FPS. I guess this is what the accelerator does trickery with? I use an ENB to lock it. Did a bind of the enable/disable (thanks to a tip from RedRocketTV). Before loading I switch off the limiter, the FPS goes up to 8-900, after loading I enable the limiter. The difference in load times with and without limiting the FPS is pretty staggering. (At least in my game, ymmv and all the usual stuff.....)

Interesting. Please keep us posted after you apply the fix, if you wouldn't mind!

Wise words. Don't overclock if you don't know why you should! I can't imagine there is anything noticeable to gain with FO4 using XMP. For me it actually was the other way around, I run some workloads that put heavy load on the CPU and memory (and the Threadripper likes fast memory). The overclock is 100% stable. But, at the end of the day when I was ready for a beer and mess around in the wasteland, it all went pear shaped. That's why I asked the OP about XMP.....

Fans are a dime a dozen. It is the same manufactures that makes non-branded and branded ones. If having fans branded with Cooler Master, Corsair etc gives you a warm and fuzzy feeling inside :) by all means, buy those. If cost is an issue, buy non-branded ones. If noise is an issue, use the largest fans possible. Fans are basically......fans. Don't make this into some kind of art. Thermal paste is the same, unless you want a metallic one, then there are considerations regarding the metal used in the cooler. If you de-lid the cpu you are in another complexity hell altogether.

Cool that you got it sorted. As to why XMP fcuks shite up, who knows. My newest build is a Threadripper 2950, G.Skill 64GB, RTX 2080 Ti system. When I flip on XMP profile 2 (3200 MHz) I can load the system very heavily, have screenshots where the mem use is above 62GB and the average load across all cores is above 70%, and everything is rock stable. ...then, reboot the system, start FO4, and it all goes to hell...... switch off XMP and FO4 behaves. Edit: Btw, SLI is fine. My old system with dual GTX 980's was a blast. But the relatively minor increase in performance does not justify (in my case) the cost of two cards.....

It may not make any difference at all, as said, I have no clue why this happens on my PC, and haven't had time to try to find the cause. Built it my self so I know the hardware, but not why it is such biatch regarding FO4 and XMP! :)

Try switching off XMP and see if makes any difference. It's a matter of timing (I think), not faulty RAM (Memtest). I can run my RAM with the second XMP profile (3200 MHz) and all plays along nicely, I can max out my memory and really put load on the CPU, no errors. Then firing up FO4 and things become very unstable. I don't know why, haven't dug into it, but switching off XMP (down to 2666 MHz if I remember correctly atm), and there is no problem.

...or a XMP profile activated in BIOS?

You need to get some facts on what is actually happening at the time of the crash (assuming this is hw/temp/something related and not a sw problem). Download GPU-Z (link to the portable version), got to the Sensor tab, set it to log to file, and then let it run until the crash occurs. https://portableapps.com/apps/utilities/gpu-z-portable Download Generic Log Viewer, and load the log file from GPU-Z, see if the sensor data show anything strange, just before and up until the crash https://www.hwinfo.com/add-ons/ If you want to go full bore, download HWiNFO (link to the portable version), start it in sensor view only, log to file, and then let it run until the crash occurs. https://portableapps.com/apps/utilities/hwinfo-portable Open the log file in Generic Log Viewer (it supports GPU-Z, HWiNFO and AIDA 64) and look for anomalies.

As for Windows, I rarely have BSOD's, when I do they always dumps into two categories. 1. Hardware, either me doing something stupid regarding overclock, or some hardware that is faulty. 2. Some driver or software that runs in admin context (RAID-drivers in particular, or buggy security software). Btw, I run Windows Defender with default settings, never touched it, and it doesn't cause trouble, for me at least, ymmv! If you have a Corsair with a Link-module (hw thingy), you can use the Corsair Link software to read some metrics from the PSU. But, what is the BSOD-error, especially since it only happens when playing FO4. I'm starting to get curious! :) Good luck!

How is 60 to 65 overheating? Mine gets up to the high 70ies without any problems. And I haven't got the strongest horse in the race with a 650 GTX. There has to be something else causing you to CTD. I'm with cossayos on this one.... A stock 1060 should: - start the fans at around 60C - start thermal throttling at around 83C - shut itself down at around 92C to prevent damage (it can usually handle higher temps, but that is the safety limit) My card (not a 1060, but Nvidia) fluctuates at around 70-75 under heavy load.

Weird stuff. I've been using PRC for a long time, but have tried a lot of different ENB's and never had problems like you describe. Got some problems with an ENB a while ago, but that was tied to the version, think I had to roll back to 0.307 or something. After roll back everything was working fine. Currently using 0.355, and it has been un-problematic. Gonna have a look at the newest version soon.

Cool that you got it sorted. I've never had any problems with ENB, and I use ENB all the time.....strange! But thanks for thorough explanation.

Not an answer to your question I'm afraid (you said nothing about price range, I have a RTX 2080 Ti, it works excellent but costs a small fortune....). But something seems seriously wrong with the setup. The 1060 starts thermal throttling at 83C, and the fans starts at around 60C (if I got my specs right). You sure that it's not something that can be fixed, like airflow and such?

First of all, apologies to the OP for hijacking this thread and going off-topic.... @Di3sIrae The tool you keep posting links to is nothing more than a CLI to some memory management functions in the core OS. There is no clever programming going on, there is no magic. For example flushing the Working Set of a process does nothing more than create a lot of page faults as the OS has to swap (parts of) the information back in. I suggest downloading VMMap from Sysinternals, attach it to a process, clear the working set and watch what happens. When there is a problem with FO4 (or possibly hardware) you don't start to randomly mess around with the memory management of the OS. You methodically troubleshoot the problem. As for the ENB-setting, for those who got it working, good for them. I have not, on two very different hardware configurations, and after many hours of testing different values. Why 4GB (4096) and 13.7GB (14000) should be considered "normal" values I have no clue at all.