UhuruNUru: Regardless, you should still Dual Boot it with W7.
Especially if you use mods, as W10 has hardcoded 4GB system memory limits for DX9 games.
Certain tools that allow a DX9 game to access more RAM than that, don't work on W10.
Most Notably, ENBoost, in Skyrim, which can theoretically use upto 128 GB of System RAM, to supplement the 3.1 GTB VRAM limit Skyrim has.
MadalinStroe: I was intrigued by the issue you brought up, so I did some searching around and the limit you mentions refers to video card RAM. And guess what,
somebody from Microsoft, has been hard at work and apparently the Fall Creators update will fix this bug.
VRAM is limited to 4GB in DX9 specifically because it's 32-bit, and so is Skyrim, which actually has a hardcoded VRAM limit of 3.1GB. That causes a known CTD if VRAM ever goes over that 3.1 GB limit.
This is a long term limit, that only heavy mod use exposes, and Boris Vorontsov, the ENB Series Developer, came up with a workaround for 64-bit systems with spare system RAM.
This is part of ENBSeries but can be used without the Graphical ENB Presets.
ENB Download When used separately it is called ENBoost, which is actually an ENB preset, without the Graphical enhancements
Crash Fix ENBoost by Boris Vorontsov The mod page states this
//++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
// REQUIREMENTS
//++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SOFTWARE
ENBSeries 0.303 or NEWER binaries (older do not have memory patches), donwload
it from
http://enbdev.com HARDWARE
OS:
Patch work with both x86 and x64 OS, but to see full potential i advise to
run Windows Vista/7 x64. Less effective will be with x86 versions of XP/Vista/7.
Windows 8 and Windows 10 from users reports have limitations of available video
memory, while some Windows 7 users have much more available, so it's the best OS
for modded Skyrim at this moment, especially for videocards with more than 4 Gb VRAM.
However the issue I speak of appeared in the old version, available at the launch of W10.
I'm not familiar enough with the changes to v6.0, to know if iut's changed that much, but as far as I know the issue with W10 still exists.
CTD and Memory patch ENBoost by Boris Vorontsov It's requirements state.
//++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
// REQUIREMENTS
//++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SOFTWARE
ENBSeries 0.196 or NEWER binaries (older do not have memory patches), donwload
it from
http://enbdev.com HARDWARE
OS:
Patch work with both x86 and x64 OS, but to see full potential i advise to
run Windows Vista/7/8 x64. Less effective will be with x86 versions of XP/Vista/7/8.
RAM:
Greater means better, but optimal with current version of the patch is 8 Gb,
in that case 4 Gb will be fully utilized by the game and 4 for OS and cache.
VRAM:
Greater means better, users with NVidia Titan 6 GB will have amazing stability
results, because patch use video memory as much as possible.
What I say from here is based on how ENBoost worked at the time of W10 launch, and ENBoost is the only thing I know for certain was affected, but any mod/tool that provided 32-bit games, with access to more than 4GB of System RAM would be affected.
4GB it a 32-bit maximum address limitation, and applies to both VRAM, and RAM.
This is an hardwarte limitation of 32-bit PC's, 64-bitPC's don't have this limit.
ENBoost worked by creating an
ENBHoist.exe, to divert excess VRAM usage to the spare, and unused System RAM, a 64-bit machine may have.
Each ENBHost.exe was limited to the 4GB, but they could stack to a theoretical limit of 12GB.
THis system worked fine until a W10 update, when Boris discovered ENBHost had stopped working.
At first, it was only showing up with Nvidia users, and Boris made this post on thew NVidia Forums
Remove 4GB limit of VRAM for dx9 games Later reports showed that it was also affecting AMD cards, and the W10 update was found to be at fault
Heres a DuckDuckGo search on the Topic.
W10 4GB DX9 limit at DuckDuckGo TLDR
Basically while the VRAM/RAM limitation is real in 32-bit, ENBoost allowed 64-bit systems to access RAM above that limit, and use it to stop the VRAM exceeding the 3.1 GB CDT of Skyrim.
It's this workaround that was then broken when W!0, hardcoded a 4GB limit on DX9 games.
Whateever was changed, end result was ENBoost didn't work on W10, but W7 was fine.
Boris may have changed how ENBoost works, but as far as I know W10 still has the issue.
I've not modded Skyrim for a while, so I'm not up to speed on the new ENBSeries release.
It's changed enough to be posted as a new mod, so maybe windows has not fixed the issue.