Hello everybody,
I have encountered very weird problem with writing files on disk (saving files) in my system.
My configuration is:
Sometimes writing files on disk (all of the disks are affected both SSD and HDD) gets stuck and the only thing that helps is a system restart (logoff -> logon doesn't work). I will list of programs that are affected the most and the ones that are not affected:
Does anyone know what could cause this type of behaviour and if there is any way to fix it?
I have encountered very weird problem with writing files on disk (saving files) in my system.
My configuration is:
■ core i5 2500k @ 4.5GHz
■ Asus P8Z78-V Motherboard
■ 16 GB RAM (2x 4GB + 1x 8GB) @ 1600MHz
■ Crucial M4 128GB SSD (system drive)
■ WD 2TB (7200rpm) + 2x Seagate 4TB (5900rpm)
■ MSI GTX 970 Gaming
■ Windows 7
Sometimes writing files on disk (all of the disks are affected both SSD and HDD) gets stuck and the only thing that helps is a system restart (logoff -> logon doesn't work). I will list of programs that are affected the most and the ones that are not affected:
■ Eclipse IDE - after a random amount of saving project the IDE freezes and does not save anymore
■ CodeBlocks - pretty much the same behaviour as Eclipse. The saving option freezes and you are stuck till restart
■ Chrome (not very common) - finishes downloading a file till 100% but does not rename the temporary file to its proper name. If you try to access the file manually the explorer gets stuck in loading the green ribbon in the address bar infinitely
■ Resident Evil 7 - the game gets stuck with the autosave option after a number of saves. You can play and everything is ok but manual save is not available anymore. When you restart the final autosave is correct and everything behaves normally till the issue appears next time
■ Starcraft 2 - I play the game very often and have made a lot of saves during the campaign and it never had any problem whatsoever
■ It seems that the rest of the applications are not affected or there is not such obvious sign of malfunction.
Does anyone know what could cause this type of behaviour and if there is any way to fix it?