Author Topic: PC won't shutdown (Read 13378 times)

suzy · « **on:** December 06, 2015, 06:28:04 am »

My PC won't shutdown when I click on power > then shut down (freezes). I have to kill the power with the button. The new win 10 update gets to 71% and when it wants to restart it freezes. I ran tweaking.com repair but it didn't help.

Shane · « **Reply #1 on:** December 08, 2015, 02:09:26 am »

Have you ran a check on the hard drive yet?

The system locking up during shutdown or even during an install of an OS normally means bad hardware, either bad memory or bad sectors on the hard drive.

If you are able, open a cmd.exe window as administrator and put in

chkdsk c: /r

when you run it it will say the drive is in use, hit Y to have it run at next boot, then have it do it and let me know the results

Shane

suzy · « **Reply #2 on:** December 08, 2015, 02:43:12 pm »

Won't get past 11% on check disk at start up, will try again tonight.

Boggin · « **Reply #3 on:** December 08, 2015, 03:32:10 pm »

Use the green download button to download the 30 day free trial of HDSentinel which will give a written report on the status of your HDD.

http://www.hdsentinel.com/

Uninstalling it when done will stop the clock should you need to use it again.

suzy · « **Reply #4 on:** December 09, 2015, 07:37:09 am »

ran HD sentinel and HD is fine. Check Disk will not get past 11% after 1 hour and a half. redownloaded repair tool last night and ran (in safe mode) still will not shutdown clicking on power > shutdown. New build of windows 10 gets to 71% of installation completion and freezes (had similar problem with installation of win 10 from win 7). Runs fine after startup.
Gateway ZX 6971
Intel G630
4 GB memory
64 bit OS

Boggin · « **Reply #5 on:** December 09, 2015, 09:48:32 am »

Can you run a sfc /scannow from the Command Prompt (Admin) to see what that reports.

If it reports it is unable to repair some files then download SFCFix.exe from http://www.majorgeeks.com/files/details/sfcfix.html which will produce its own report on what it can and cannot repair which you can then copy & paste into the reply box.

There are two other commands you can run and they are -

dism /online /cleanup-image /startcomponentcleanup

dism /online /cleanup-image /restorehealth

(This one can hang at 20% but does complete)

Then run another sfc /scannow to see what it reports then if a previous one reported errors.

MS may have upgraded the MCT to include the latest update and clicking on the Upgrade now button may install the latest update without any problems.

https://www.microsoft.com/en-gb/windows/windows-10-upgrade

suzy · « **Reply #6 on:** December 09, 2015, 12:51:38 pm »

Did a sfc scannow and no problems but as I was doing an update earlier today, my pc froze and it would not shutdown due to a MS webcheck monitor

Boggin · « **Reply #7 on:** December 09, 2015, 01:59:16 pm »

That looks like it is another of MS Spies and isn't necessary to the running of Win 10 on your part.

This article gives a bit more info on it and how to uninstall it.

http://www.file.net/process/webcheck.dll.html

Does the machine otherwise shutdown and does it update okay now ?

suzy · « **Reply #8 on:** December 10, 2015, 10:42:47 am »

The machine shutdown like it was supposed to last night but today no luck, I have trouble with updates, in fact it took 6 tries to upgrade from win 7 to 10, now the new 10 I can't get

Boggin · « **Reply #9 on:** December 10, 2015, 10:54:53 am »

Have you run those two dism commands in Win 10 ?

Shane · « **Reply #10 on:** December 10, 2015, 11:28:32 pm »

If checkd isk got stuck at 11% it is either because it hit a bad sector OR you have bad memory. chkdsk will fill your memory when doing a scan, so if you have a bad memory module then it would cause it to lock up.

If you have a lot of memory installed it may be the higher section of memory where it might be bad and might be the reason you only see the problem shutting down.

So you ran another program to check the drive, I never used that one, but if it is correct and the drive has no bad sectors then I would do a memory test next.

Shane