u2pitchjami

so, i saw that in the "windows event viewer" (observateur d'événements in french) - "system logs" it was like ---> Warning - Source : Ressource-Exhaustion-Detector - Event ID : 2004 Windows blablabla virtual memory blablabla now, to solve : Go to : Control Panel - System - advance system param - perf - Param - advance - Virtual Memory - Edit - and go to auto gestion blabla (for me, but maybe for you you must write your own mount of virtual memory). : For me : windows auto allocation is : 7936 MO (it was 3900 before...) yeah baby !!!!!!!!!!!! thanks i will come back to Bordeciel (in french lol)

ok well well well i found the problem !!! it was a bas set of virtual memory on windows 10 now it's all very good thanks for your help ;-)

Yes i tryed but the results was not logical and very fluctuant... the only interesting fact is : more 150 mods = random ctd (outside 95% of time) and more 200-250 mods = unplayable I think about memory problem... skse.ini ??? Windows 10 directx9 limitations (it's realy true ??) or i don't know what else... it's realy possible ? and if yes, some tweaks or advices about that ?? thanks in advance :) my rigs : i7 2700k ram : 8go GC : gtx 1070 win 10 ssd and tralala

hello everyone, thanks for this wonderful guide. i have a big problem with ctd, many many many ctd (when i go outside) and i don't know really where is problem is. When i have more 150 mods activated (60-70 esp esm), its a ctd party, the worste is Solitude. i followed the guide but... now is : test, test, test for find something but... i don't find i'm on Windows 10, it could be a problem ??? (i saw on the guide that you are on win 7) thanks in advance :) u2pitchjami