Sign in with
Sign up | Sign in
Your question
Solved

Having performance issues on new PC, possibly due to corrupt system files?

Last response: in Windows 7
Share
December 7, 2013 7:24:11 AM

Okay I apologize in advance, but I have a feeling this will be a relatively long breakdown. I also apologize if this is the wrong forumf or such discussion, I just thought since it dealt at least in part with corrupted system files this would be the place to start.

Built my first PC several months ago, worked great initially but of late i am having some problems.

I first noticed an issue upon trying to auto-diagnose/repair a network connection. It would begin and then fail saying :"Scripted Diagnostics Native Host has stopped working", giving me the option to debug or close. if I attempt to debug it said there was no registered JIT debugger specified. At this point allI can do is retry and close. So I close.

Did a quick google search for this, and the most common reply was to run a system file check. so I sfc /scannow'd 2 or 3 times, and got the same result each time.. A positive test for corrupted/missing system files, and an access denial upon attempting to correct them. I have the log generated by the scan if it would be helpful

Now my problems have turned more into serious performance issues. I can't launch an application (even VLC which is notoriously easy ons ystem resources) without having a 10-20 second latency. Attempting to play a game is almost out of the question.

My specs are as follows:
Windows 7 Home Ultimate
MSI 970A G46 MoBo,
MSI Twin Frozr GeForce GTX 760 GPU
AMD FX8350 CPU (8 Cores, 4.0GHz)
2x4GB 1866 MHz DRAM
10,000 RPM 1 TB WD Caviar, with 3GB/S sata connection

I'm not sure if I missed some crucial point int he setup of the new computer where I sort of"synchronize" things so the timing as optimized, or if maybe I should have done a proper NTFS formatting before installing windows, and am now getting corrupted files because I did not?

Anyway, I'm willing to try just about anything to get this back in proper working order-- it's a bummer having shelled out almost a grand on a new PC to find it runs like any old piece of junk

Best solution

December 7, 2013 7:29:39 AM

is reinstalling a clean version of windows 7 out of the question ? or trying repair from the original media cd.
Share
December 7, 2013 7:33:31 AM

Lee-m said:
is reinstalling a clean version of windows 7 out of the question ? or trying repair from the original media cd.


It is not out of the question, was hoping to avoid it if possible. I did dig out the w7 CD and attempt to run an install, but the only option it gave me while windows was running was to isntall windows 7.. should it bring up repair options if I boot from it?
m
0
l
Related resources
December 7, 2013 7:46:33 AM

The original media has at least a few repair options. One is a start up repair which will be no good to you.
I haven't encountered this type of, issue before. I would just go straight for a re-install, no telling how long it would take to trouble shoot and fix this issue.

Thats the way I would go unless some one else can come up with a better idea.

It sounds like maybe a service pack or windows update failed to install correctly. But thats just a guess.
m
0
l
a b $ Windows 7
December 7, 2013 8:12:17 AM

you mark that you did not format before the install of win does this drive was ahving another os on or use with another system and if the answer is yes ,i sugest you refomat and reinstall the os .
m
0
l
December 7, 2013 9:18:57 AM

scout_03 said:
you mark that you did not format before the install of win does this drive was ahving another os on or use with another system and if the answer is yes ,i sugest you refomat and reinstall the os .



Suppose Icould have been more clear, the Hard drive was brand new out of box. I just meant that I didn't give the drive any more than the standard formatting that takes place during the OS installation.
m
0
l
a b $ Windows 7
December 7, 2013 9:24:31 AM

this brand new drive did you try the data lifeguard diagnostic tool from wd to see if it was good it could have bad sector on .
m
0
l
December 8, 2013 1:33:14 PM

I actually started having more drastic problems the more I messed with it, got to the point that it wouldn't boot, then when I removed the drive and tried to boot from a disc it started taking me to some EFI command shell.. I wound up just loading up the UBCD (where I did in fact see the WD lifeguard tool, but wasnt sure which, if either of the versions of it would work for my drive), and used one of the utilities to format my HDD completely. On a fresh install of windows and everything seems ot be working now.
m
0
l
December 8, 2013 1:52:05 PM

Hopefully it will stay that way for you. Glad its sorted out.
m
0
l
a b $ Windows 7
December 8, 2013 7:02:31 PM

let hope that your issue is solve .
m
0
l
December 8, 2013 10:42:31 PM

It certainly didn't! just out of curiosity I ran a SFC almost immediately after installing and it came ip with corrupted or missing files that couldn't be reapired-- so either my windows dvd is bad, or my hard drive is going.. going to run a chkdsk and a memtest..

Quick question in regardsto that: will a chkdsk tell me if it is actually physically a problem with the hard drive? or will it just inform me of corruption/bad sectors?
m
0
l
December 9, 2013 10:06:07 AM

After a reformat, at this point I would just suspect a bad disk. As far as I remember (its been a real long time since I ran check disk, or scan disk) it really just ensures the integrity of the windows file system.

The gui version (drive > properties > tools) has an option to attempt recovery of bad sectors.

Maybe its time to start pricing up that SSD ;) 
m
0
l
!