Hi guys. I'm having a bit of trouble with the creation kit freezing up in Windows 10. I've done a lot of searching online, and I feel like I've covered most of the standard quick solutions. I was wondering if anyone could offer up any new ideas to try to get it working long-term, rather than for just a few short minutes. Here is what I'm working with, off the top of my head:

- AMD FX-6300 (six core) Processor: I have this overclocked to about 4.2Ghz (although it turbos to 4.1Ghz anyways), so that the other cores won't throttle down dynamically just to push one core. It's been working great for gaming on a lot of platforms for almost a year.

- SATA SSD, 60GB of free space

- 16GB RAM

- GTX 660 GPU: fully updated drivers, and I'm fairly certain it has 2GB of video RAM

- Dual Dell 24" monitors

- The game is retail, and is the latest version with all of the expansions. I did a fresh install off of Steam about a week ago.



What I've tried:

- Going through the tutorial stuff, like that creating your first mod guide that gets linked here and there (Not my first mod, but I am rusty, and it's a new rig since I modded a couple of years ago)

- Giving full control to users on the Skyrim folder

- Running the creation kit as an admin

- Running the creation kit in Win 7 compatibility mode

- updating drivers

(I might be forgetting some standard steps I tried out)

How it's behaving:

I can open the creation kit as an admin, load data files, make changes to the active mod and save it, and everything works fine in-game. The problem that I'm having is that I have to be fast. I can just make small quick edits to existing mods. It doesn't take long before I get a random freeze, and it just no longer works. If I click on anything in the CK after it locks up, it just makes a dinging noise, and doesn't respond. I've kept my task manager open while running it, and my system doesn't appear to be getting challenged at all.

I don't know if it is a coincedence, but doing things in my second monitor and moving back to the CK in my primary monitor seemed to force the lockup. It could be timing, but it happened twice. I've had it happen many times though, just using my primary monitor, and not interacting with the secondary.