- Dec 17, 2014
- 27
- 0
- 4,530
Since Skyrim SE was launched I thought I'd try and have some fun with the Original Skyrim and see if I could mod it to make it look better than the SE. So I popped open Nexus Mod manager and started downloading some mods for it. I started then game and a new character and everything seemed to be running smoothly and like a charm until about half way through the opening cinematic CHUNK it froze for about 1 minute and then resumed smoothly for about another minute and the same thing happened. Knowing this could very well be some of the mods I've installed I closed Skyrim and started uninstalling the mods. To keep a long story short some of the mods were taking an abnormally long time to uninstall- and I'm talking big like 20+ minutes long for 300 MB. I opened up task manager and noticed that while my HDD's read right chart was devoid of much reading and writing (unless I'm reading that chart incorrectly) the HDD activity time chart was at a constant 100% without any sign of spiking. essentially "| | 100%"
Here are the steps I've taken so far:
1. I've tried to defrag the HDD that took a long time but didn't yeild any sign of improvement
2. I've tried to decrease the ammount of data on the drive by almost 50% which hasn't worked either.
3. I've ran a chkdsk /b /f /v /scan e: command through an elevated session of command prompt, making sure that all ties to my E:\ drive were not running, Results returned with nothing to show that would indicate that my drive is bad, also- interestingly enough- read/write and active time were behaving normally when I did this. Results from chkdsk here. I tried uninstalling a mod and it still jumped straight up to 100%.
4. I've also tried using Seagate's tools to check the disk and see if everything's okay, but nothing seems to want to install or uninstall for me today. The seagate tools just sit there not installing. I have now used up my entire day off to figure this out.
5. Going to be running an sfc /scannow command through an elevated session of command prompt and checking that the SATA connections to my motherboard and hte disks are okay are okay and (supposedly) good to go. I had also disabled the services "Windows Search" and "Superfetch" since I had read in a forum from earlier that those might be causing this issue, but I believe that will require I computer restart and since I need to get into the computer case anyway, may as well do that too.
The HDD in question is a ST31000340NS 1TB 7200 RPM HDD
The rest of my setup is:
CPU: AMD Richland 760K
Motherboard: MSI A88X-G43
Memory: 8 GB DDR3 2133 MHz
Video Card: EVGA NVIDIA GTX 750 Ti 2GB Superclocked Ed.
OS: Windows 10
Another useful tidbit of information: My motherboard has recently been on an RMA to MSI as the northbridge screw was not present. MSI told me that I didn't need to worry about static protecting my MoBo since they were going to be either sending me a refund or a refurbished of the same model. I wrapped it in bubble wrap and shipped it off. 3 weeks later I called in since I hadn't heard anything from them, they told me they were going to be doing a refund. The next day I received an email from MSI stating that my motherboard was on it's way to me. I called in, they said they had no records of anyone telling me anything about a refund. They also assured me that the board was tested in their lab and it seemed to be in working condition. The board arrived that same morning so here I am about 5 days later. Could this be a result of ESD? If so, I don't think I'll ever go with MSI MoBos again.
I will add my notes from step 5 as soon as I finish those tasks, in the mean time any help is appreciated. Also, thanks for bearing with me through this long and arduous novel.
Here are the steps I've taken so far:
1. I've tried to defrag the HDD that took a long time but didn't yeild any sign of improvement
2. I've tried to decrease the ammount of data on the drive by almost 50% which hasn't worked either.
3. I've ran a chkdsk /b /f /v /scan e: command through an elevated session of command prompt, making sure that all ties to my E:\ drive were not running, Results returned with nothing to show that would indicate that my drive is bad, also- interestingly enough- read/write and active time were behaving normally when I did this. Results from chkdsk here. I tried uninstalling a mod and it still jumped straight up to 100%.
4. I've also tried using Seagate's tools to check the disk and see if everything's okay, but nothing seems to want to install or uninstall for me today. The seagate tools just sit there not installing. I have now used up my entire day off to figure this out.
5. Going to be running an sfc /scannow command through an elevated session of command prompt and checking that the SATA connections to my motherboard and hte disks are okay are okay and (supposedly) good to go. I had also disabled the services "Windows Search" and "Superfetch" since I had read in a forum from earlier that those might be causing this issue, but I believe that will require I computer restart and since I need to get into the computer case anyway, may as well do that too.
The HDD in question is a ST31000340NS 1TB 7200 RPM HDD
The rest of my setup is:
CPU: AMD Richland 760K
Motherboard: MSI A88X-G43
Memory: 8 GB DDR3 2133 MHz
Video Card: EVGA NVIDIA GTX 750 Ti 2GB Superclocked Ed.
OS: Windows 10
Another useful tidbit of information: My motherboard has recently been on an RMA to MSI as the northbridge screw was not present. MSI told me that I didn't need to worry about static protecting my MoBo since they were going to be either sending me a refund or a refurbished of the same model. I wrapped it in bubble wrap and shipped it off. 3 weeks later I called in since I hadn't heard anything from them, they told me they were going to be doing a refund. The next day I received an email from MSI stating that my motherboard was on it's way to me. I called in, they said they had no records of anyone telling me anything about a refund. They also assured me that the board was tested in their lab and it seemed to be in working condition. The board arrived that same morning so here I am about 5 days later. Could this be a result of ESD? If so, I don't think I'll ever go with MSI MoBos again.
I will add my notes from step 5 as soon as I finish those tasks, in the mean time any help is appreciated. Also, thanks for bearing with me through this long and arduous novel.
Facebook
Twitter
Instagram