New
#1
Intel SSD Freezes Windows Exporer
Hi there SevenForums. My name is Nic and I am having an issue with my solid state drive in my custom built desktop.
I am currently running Windows 7 Home Premium 64 bit on an Intel SSD 530 Series (240 GB) in IDE mode with a Western Digital 1TB HDD as a secondary drive.
Both are currently active and are running in my desktop computer with the specs described in my profile.
The issue is that my computer will randomly freeze at times and cease to allow input for about 15 seconds. After waiting the 15 seconds it seems that my computer "picks back up where it left off" and every program that I attempted to open during the freeze opens at the same time.
During the freeze Windows Explorer is unusable, however the mouse does move but will not open any programs until the freeze is finished.
This problem only happens on my SSD as I have tested a fresh installation on my HDD and there is no freezing. I have also tested two different fresh home premium installations on my SSD as well as a fresh installation of ultimate with no change.
I have noticed that after looking at my desktop tower during the freeze the hard drive light does not come on at all. Once the 15 seconds is up (generally around 15 seconds but not exactly) I see that my hard drive is accessed and once this happens every single action that I attempted to make during the freeze with my mouse happens at once and the computer begins to function as normal.
I have also used Intel's SSD Toolbox and used their update tool iso to update my SSD. However, after running the update tool on a bootable disc it said that my SSD was up-to-date with the latest drivers.
I may also note that this freezing problem only seems to happen when using Google Chrome. However it is not limited to, since once it happens it will freeze every part of the OS, including Windows Explorer.
It never freezes while in a game such as Diablo or Battlefield 4. It also doesn't freeze on Internet Explorer, Firefox, or just browsing the file system.
This is a pretty confusing bug and I'm looking for any insight. Thanks in advance,
- Nic