Main Forum > General Computer Support

(Solved) win seven ulti hangs at shutdown for the past few days . fix wanted

<< < (3/4) > >>

jraju:
Hi, boggins the problem got resolved by doing sfc /scannow two times and chkdsk /f/r one time. I think power surge sudden closure would have made some corruption in the files system and made some correction.
                    now the problem solved and i do not think the cause is dlink usb, but some other services. Can i see the log for it in event viewer. Which log should i see to know, what caused the problem?
                         In the meanwhile, i contacted dlink support and he asked me to download ammyy.com a download to let him access my computer for a while. He asked me to browse network settings , and after seeing the usb adapter shown there, he asked my permission to shut down. i did. the computer obeyed and shut down cleanly without any problem. Probably the sfc and chkdsk would have solved the problem by then.  I did not stop verbose, as it gives a clue to what the window is doing. it shows menu wise action while shutting down. It stops at services, probably meaning that some services are waiting for something , but could not get that to close.

Boggin:
To read the chkdsk report, go into Event Viewer and when it has read the data, expand Windows Logs - click on the name Application/Action/Find and in the Find box type chkdsk or wininit and press enter.

Cancel the Find box and read the report in the scrollable window.

To read the CBS log, from an admin cmd prompt enter or copy & paste this cmd -

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt

This will put an icon onto the desktop which when double clicked will open the CBS log into Notepad, reporting what it has found and repaired.

jraju:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  97280 file records processed.                                          File verification completed.
  100 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              44 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  124816 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  97280 file SDs/SIDs processed.                                         Cleaning up 465 unused index entries from index $SII of file 0x9.
Cleaning up 465 unused index entries from index $SDH of file 0x9.
Cleaning up 465 unused security descriptors.
Security descriptor verification completed.
  13769 data files processed.                                            CHKDSK is verifying Usn Journal...
  35568008 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  97264 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  44592390 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 204696575 KB total disk space.
  26078392 KB in 78807 files.
     43812 KB in 13770 indexes.
         0 KB in bad sectors.
    204807 KB in use by the system.
     65536 KB occupied by the log file.
 178369564 KB available on disk.

      4096 bytes in each allocation unit.
  51174143 total allocation units on disk.
  44592391 allocation units available on disk
some index files have been corrected. would this fix the problem. how to identify.

Boggin:
If you ran a sfc /scannow twice before the chkdsk and the first one did the repairs required, then the chkdsk will have found nothing to repair and the CBS log which that cmd will pick up may also come up clean because of that.

jraju:
Hi, Boggins. Understand that but will it not leave of logs which created the problem.
                I  went to event viewer and saw all the logs under chkdsk, and it has done some index correction on some items not easily  to be understood.
                  I also went to sevenforum, where there was a tutorial about looking in to shutdown event id, 6008 and how to see.
                   i went to event viewer and see the system log , and then select current log in the right pane and in the dialogbox , selected the user 32 and event id 1074. But all the logs contain no error message or any yellow exclamation in that .
                   where to see the logs of services? when i saw the services log it does not contain any error.
                      So i raised a query on the tutorial to Brink, the author of tutorial. But surfing the net, i came to understand, though you forcibly poweroff, it does register as a normal log. log expert could only tell that. i have seen all the logs

Navigation

[0] Message Index

[#] Next page

[*] Previous page