For the people that did the 18 updates for windows 7, are you experiencing some weird problems?
1) After first restart. Processor was pegged at 3.5-3.6 ghz and fans on full blast. Restarted
2) Second restart. Processor bounced for 1.3 to 2.9 ghz and seem to use an extra 0.2 Gb of ram
3) When to restore point, but I lost a file for my Alien Respawn and would not run. Restarted
4) Undid restore, got an error saying that something about Softtools Qtool Lite. Would not go away. Restarted
5) This restart seems to be better. Boot-up took about 20 longer and start-up services took longer to get running. Also using that extra 0,2 Gb of ram.
Haven't not done anything else yet.
-
Possibly one of the updates was corrupted when downloaded. Or, something was changed, deleted, or not deleted (in the system folder or registry) that shouldn't have. One thing I've noticed with the last couple monthly rounds of updates. Everytime the group of updates contains anything for .NET services, the .NET optimization runtime app will always run on the next reboot and it always takes up loads of CPU and RAM. I just let it sit for about 5 minutes to let it do it's thing, and eventually (famous last words) the optimization runtime will finish and everything will go back to normal. One thing to check, look at the Windows update log and see if any updates had failed or are pending. You can also look in the reliability history and check if there are any errors or warnings present for today, or whichever date the updates were installed.
PS: I would recommend you NEVER use system restore. It's like Windows Cancer. It leaves all the current problems whilst restoring any old ones as well. If you need to restore, use Alienspawn...but I see Respawn didn't want to work for you. -
My clock speeds seem to back to normal so I think I maybe fine there.
I wish I knew that about Windows restore, because that obviously causes problems with windows updates .
P.S. I have only basic Respawn , so I couldn't do the alien restore, but I guess that is a possible reason to get it. -
Definitely agree with radji. I just did the W7 update and after the restart, the .NET optimization ran like crazy. Took almost 15% cpu load and fan ran at full load.
Did you let the fan slow down before restarting? If you force a reset while .NET optimization is running, I think .NET might crash.
One possible solution is to remove every .NET programs on your laptop and just reinstall them, if you still uncertain... -
Can't remove .NET. Catalyst Control Center requires it to run.
-
Well, every thing seems to be fine after undoing the restore. Ran disk check and that didn't find any errors. ( I would assume it would notice any important windows files if they were corrupted). There were no errors from programs trying to start up. So I guess it is safe to assume every thing is fine. Unless there is something else to check?
I'm not sure where there extra memory is going since don't have anything to compare with.
Edit: On my first go around, I did not wait for the fans to slow down before I restarted, but I don't think that fact should matter since I restored and undid the restore. Those two things would probably cause problems. -
My bad. I always disable Enduro so I pretty much never use the Catalyst Control. Didn't know it runs on .NET environment. Well, you can disable Enduro and reinstall .NET but I guess it won't be necessary anymore.
Being patient is one of the few lessons I've learnt from using computers. And that lesson cost me quite a lot in the past.
-
After few hours of use, the only thing out of the ordinary was the processor clocking up to 3.5 ghz for a few minutes after 30 mins of use,, but has been good for the past 2 hours. I'll just keep an eye on it -
When I heard the fan blasted, I thought something was wrong so I opened the task manager to see what's wrong. The .net optimization was taking a toll on my CPU but I guessed it was because of the recent update. So I left it there for a few mins. Luckily, I guessed it right. If your laptop hasn't shown anything abnormal, I don't think you have to worry about it. Crashing .net is certainly not the end of the world
.
-
-
Not just the recent updates. Last month's updates, and then when I updated Catalyst to 12.10, the .NET optimizer ran then as well. I think it detects changes to any APIs that use a .NET environment and then auto-runs the optimizer for whatever ridiculous reason.
-
At least I can say I learned something from it.
Update: Amount of memory being used is back to normal.
Sent from my SGH-T999
Window 7 Update November problems.
Discussion in 'Alienware 17 and M17x' started by CryoBolt, Nov 15, 2012.