New
#11
Run an sfc scan to fix corrupted system files.
SFC /SCANNOW Command - System File Checker
If that doesnt help, run a repair install.
Repair Install
Run an sfc scan to fix corrupted system files.
SFC /SCANNOW Command - System File Checker
If that doesnt help, run a repair install.
Repair Install
Thanks. SFC returned no integrity violations.
DD.
Thanks, I can try a repair install, am just not keen on it. Other than the very lengthy shutdown, the system is working more or less fine. I don't want to risk messing up the installation with a repair install especially since SFC did not find anything out of the ordinary. Win7x64 has only been installed on that comp since August, it is still relatively new.
The comp is triple-booted with Vista x64 and XP x32. I plan on eventually removing Vista since Win7 is more or less the same (but better) and going back to a dual-boot system with XP hanging around to provide access to the file system should anything catastrophic happen to Win7.
Any other ideas?
Thanks,
DD.
Hi,
Yeah, tried that this past weekend. Doesn't seem to make a difference. That prog is just one of those "is your firewall installed? Is your AV on?" type of programs which my ISP uses to try to cut down on support calls. It is just the messages component which used to start up anyway, it doesn't have any actual power. At any rate, it is no longer in my startup config.
DD.
Have you checked to make sure TRIM is working properly in Windows 7(if your SSD supports it that is)? Longshot, but just trying to get every option checked here. You could also install a trial of Tune Up Utilities 2010. It may be able to find your problem for you and fix it. You could then uninstall it and if the problem comes back at least you know what it is.
Would you mind posting a HJT log, so we can see what's running at start up?
Download HijackThis!
HijackThis - Trend Micro USA
Right click and run as Administrator. Click 'scan and save log'. The log will be saved to Notepad.
Next go back to start HJT, click 'open misc tools section', then click "Generate startup log".
Copy and paste both logs back in your next post.
Here is an extract from my own little blog on how you can check Trim support:
Another thing to check is the SSD alignment. Here is how:If you are not certain whether your SSD controller supports TRIM, there is an easy way to find out.
Open an elevated Command Prompt (run as admin) and paste this command into the Command Prompt window:
fsutil behavior query DisableDeleteNotify
If Command Prompt returns a 0 (zero), your drive supports TRIM and it is enabled.
If it returns 1 (one), the file system has disabled TRIM for your drive. This means your drive's controller does not support TRIM.
Source: SSD AlignmentIf you want to verify the alignment (e.g. for a SSD where you are not certain whether the proper alignment was done), you use the following commands.
Diskpart
List disk
Select disk n
List partition
Now you should see a result like this.
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 59 GB 1024 KB
The offset has to be divisible by 4.