Solved Computer Restarts When I Shutdown

[Giaccovitch]

Thanks - but apparently I asked for the wrong list

Please open an Elevated Command Prompt, and run the following commands

fsutil hardlink list C:\Windows\winsxs\amd64_microsoft-windows-tabletpc-journal_31bf3856ad364e35_6.1.7601.21955_none_7636f0d7d474e080\Pretty_Peacock.jpg >>%userprofile%\desktop\nphl.txt
fsutil hardlink list C:\Windows\System32\en-US\iassdo.dll.mui >>%userprofile%\desktop\nphl.txt
fsutil hardlink list C:\Windows\winsxs\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui >>%userprofile%\desktop\nphl.txt
 
.

Post the resulting nphl.txt file from your desktop - this should check that I now have some clue what I'm talking about

Attached

 

[NoelDP]

Let's see what happens when we try a manual cleanup.

Please open an Elevated Command Prompt, and run the following commands

Takeown /F C:\Windows\SysWOW64\en-US\iassdo.dll.mui /A
ICACLS C:\Windows\SysWOW64\en-US\iassdo.dll.mui /grant Administrators:(F)
DEL C:\Windows\SysWOW64\en-US\iassdo.dll.mui
DIR C:\Windows\iassdo.* /S >>%userprofile%\desktop\nphl.txt
fsutil hardlink list C:\Windows\SysWOW64\en-US\iassdo.dll.mui >>%userprofile%\desktop\nphl.txt
fsutil hardlink list C:\Windows\System32\en-US\iassdo.dll.mui >>%userprofile%\desktop\nphl.txt
fsutil hardlink list C:\Windows\winsxs\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui >>%userprofile%\desktop\nphl.txt
 
.

Post the resulting nphl.txt file

 

[Giaccovitch]

Let's see what happens when we try a manual cleanup.

Please open an Elevated Command Prompt, and run the following commands

Takeown /F C:\Windows\SysWOW64\en-US\iassdo.dll.mui /A
ICACLS C:\Windows\SysWOW64\en-US\iassdo.dll.mui /grant Administrators:(F)
DEL C:\Windows\SysWOW64\en-US\iassdo.dll.mui
DIR C:\Windows\iassdo.* /S >>%userprofile%\desktop\nphl.txt
fsutil hardlink list C:\Windows\SysWOW64\en-US\iassdo.dll.mui >>%userprofile%\desktop\nphl.txt
fsutil hardlink list C:\Windows\System32\en-US\iassdo.dll.mui >>%userprofile%\desktop\nphl.txt
fsutil hardlink list C:\Windows\winsxs\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui >>%userprofile%\desktop\nphl.txt
 
.

Post the resulting nphl.txt file

Alright

 

[NoelDP]

Good - now run SFC /scannow again, and we'll see what we get. Post the new CBS.log file

 

[Giaccovitch]

Good - now run SFC /scannow again, and we'll see what we get. Post the new CBS.log file

CBS.log file is contained in the ZIP

 

[NoelDP]

Here's the critical section of the SFC log...

2014-06-20 17:09:38, Info                  CSI    0000031c [SR] Repairing 1 components
2014-06-20 17:09:38, Info                  CSI    0000031d [SR] Beginning Verify and Repair transaction
2014-06-20 17:09:38, Info                  CSI    0000031e Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-06-20 17:09:38, Info                  CSI    0000031f [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-06-20 17:09:38, Info                  CSI    00000320 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-06-20 17:09:38, Info                  CSI    00000321 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-06-20 17:09:38, Info                  CSI    00000322 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Windows Foundation Language Pack"
2014-06-20 17:09:38, Info                  CSI    00000323 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}

I'll post the fix protocol for that later - when I can get away from work!

 

[Giaccovitch]

Here's the critical section of the SFC log...

2014-06-20 17:09:38, Info                  CSI    0000031c [SR] Repairing 1 components
2014-06-20 17:09:38, Info                  CSI    0000031d [SR] Beginning Verify and Repair transaction
2014-06-20 17:09:38, Info                  CSI    0000031e Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-06-20 17:09:38, Info                  CSI    0000031f [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-06-20 17:09:38, Info                  CSI    00000320 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}
2014-06-20 17:09:38, Info                  CSI    00000321 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-06-20 17:09:38, Info                  CSI    00000322 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Windows Foundation Language Pack"
2014-06-20 17:09:38, Info                  CSI    00000323 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-n..ce_iassdo.resources_31bf3856ad364e35_6.1.7600.16385_en-us_e86c80b89a3f77b7\iassdo.dll.mui do not match actual file [l:28{14}]"iassdo.dll.mui" :
  Found: {l:32 b:tfmxBgEeHYSqU0nOhrdrRtqL98a1xYC32if7l90WiOg=} Expected: {l:32 b:hLMYgoYEaSd6WHNAcMpQlj3ndwYSJanHCJ0EaEjgsTg=}

I'll post the fix protocol for that later - when I can get away from work!

Alright cheers mate.

 

[NoelDP]

Ooops - sorry!
Back in a minute...

 

[NoelDP]

I've uploaded a file - gcvaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\gcvaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\gcvaa
or
DIR E:\hznaa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\gcvaan <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[Giaccovitch]

I've uploaded a file - gcvaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\gcvaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\gcvaa
or
DIR E:\hznaa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\gcvaan <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

CBS included in ZIP

 

[NoelDP]

It looks as if that worked

Whether it had anything to do with your other problems, I really have no idea - but at least the SFC scan is good now.

 

[andrew129260]

Thanks noel.

@Giaccovitch

Did you ever enable verbose messages to see where windows is hanging?

Have you tried resetting the bios to factory defaults?

Could you please run a disk check as mentioned here?

http://www.sevenforums.com/tutorials/433-disk-check.html

Then report back and let us know if the shut down error still exists.

 

[Giaccovitch]

Thanks noel.

@Giaccovitch

Did you ever enable verbose messages to see where windows is hanging?

Have you tried resetting the bios to factory defaults?

Could you please run a disk check as mentioned here?

http://www.sevenforums.com/tutorials/433-disk-check.html

Then report back and let us know if the shut down error still exists.

Thanks Noel.

Nothing hangs at when shutting down in verbose messages.
I ran the disk check, all good.
I have overclocked my cpu to 4.5Ghz, I reset to factory defaults and I have successfully shutdown 4 times.
I am going to see if I can still be able to shutdown with my overclock settings. (I used to be able to shutdown normally for around 2 months with the overclock).

 

[Giaccovitch]

Overclocked again, shutdown the first time, the second time it didn't shutdown but restarted my computer. There must be a setting in my motherboard that is triggering this problem.

 

[sygnus21]

Had a similar issue where my backup machine would restart after shutdown. What ultimately solved my issue was, in addition to a BIOS update, to clear the CMOS, go back into the BIOS and choose optimized settings. If you read through the tread you could see a number of steps I took to solve it, but ultimately clearing the CMOS helped. See your owners manual on how to clear the CMOS, though it may be as simple as removing the CMOS battery for about 5 minutes. Be aware this will reset your BIOS to default settings all the way down to the clock.

And you might check that your overclocks aren't causing your issues as well...

Overclocked again, shutdown the first time, the second time it didn't shutdown but restarted my computer. There must be a setting in my motherboard that is triggering this problem.

 

[Giaccovitch]

My overclocks are causing the issue, I'm pretty sure

 

[sygnus21]

Well it looks like you'll have to give up, or drop down your overclocks. Remember overclocks aren't always guaranteed to work or be stable.

The other possibility may be you that you stressed the system to the point that something may have gone bad. Try running at default speeds for a while and see what happens. Than, if you still wish to overclock, do it gradually and let it sit for a while before moving one.

I usually do no more than 20 percent overclocking, if that. This way I can have the increased performance with long term stability and longevity.

Anyway good luck.

 

[Giaccovitch]

Well it looks like you'll have to give up, or drop down your overclocks. Remember overclocks aren't always guaranteed to work or be stable.

The other possibility may be you that you stressed the system to the point that something may have gone bad. Try running at default speeds for a while and see what happens. Than, if you still wish to overclock, do it gradually and let it sit for a while before moving one.

I usually do no more than 20 percent overclocking, if that. This way I can have the increased performance with long term stability and longevity.

Anyway good luck.

Well i ran prime95 for 24 hours, and temps barely raised. The voltage I am using is pretty low for the type of overclock I am performing which is good, so I have no idea why this all of a sudden happens. If I use default cpu clocks I can shutdown normally

 

[Giaccovitch]

The problem is that sometimes it actually shuts down properly.

 

[andrew129260]

Very odd Beauvoir. I do not have much knowledge on overclocking, so I cannot offer much else. I will see if anyone else has ideas.