New
#31
The thing is I have things that no other third party company has including the webcam driver for example since it only ships with the system and even ASUS can no longer provide it.
Anyways, just a update as I will be doing a reboot after I finish typing this message.
But this is what happened.
Before I rebooted, I did the chkdsk c: /x /f /r which produced the following:
C:\WINDOWS\system32>chkdsk c: /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y
This volume will be checked the next time the system restarts.
C:\WINDOWS\system32>
At this point, I uninstalled the Intel Wireless driver package and rebooted.
I see "To skip disk checking, press any key within 8 seconds" and then I see the spinning circle for about 10 seconds, then it went straight into the Windows Welcome logon screen.
At this point, I login and check event viewer in the Windows Logs -> Application but there is nothing from the source "Wininit", unless I am looking in the wrong place.
At this point, I came back to this thread to write down the "chkdsk c: /x /f /r" on paper after I did
C:\WINDOWS\system32>chkdsk c: /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y
This volume will be checked the next time the system restarts.
C:\WINDOWS\system32>
I installed the Intel WiFi driver package and rebooted.
This time, I see "To skip disk checking, press any key within 8 seconds" and then I see the spinning circle for about 10 seconds, followed by "Scanning and repairing drive C:" with the WIndows logo above it. After 30 minutes, it was still at 10% so I decided to do something else and stepped away from the computer for an hour or so. Somehow writing down that chkdsk command on paper made windows do it's thing.
When I came back, it was already on the Windows Welcome logon screen so I logged on and check event viewer,
in the Windows Logs -> Application but there is nothing from the source "Wininit", unless I am looking in the wrong place.
At this point, I get a window from "Security and Maintenance" that says "Restart your PC to repair drive errors" so I click on restart now and it said Repairing drive and it can take up to an hour except I took a few minute break and the system restarted windows started booting for 1/2 a second and then it BSOD saying NTFS File System so I powered down by holding down the power button and then turned the system on again, this time within 1/2 a second, it BSOD saying NTFS File System so I powered down by holding down the power button and then turned the system on again and Windows automatically ran Automatic System Repair and then I chose the one saying problems with Starting up. It did the Repairing Disk errors and then back to the Windows Welcome Login screen.
I logged on and check event viewer, in the Windows Logs -> Application but there is nothing from the source "Wininit", unless I am looking in the wrong place.
I used the tool to try to generate the BSOD logs except I noticed the latest minidumps was June 15, 2017 as seen below so I aborted the process:
C:\WINDOWS\system32>dir c:\windows\minidump
Volume in drive C is OS
Volume Serial Number is 2484-EBDD
Directory of c:\windows\minidump
06/15/2017 11:11 PM <DIR> .
06/15/2017 11:11 PM <DIR> ..
06/10/2017 03:39 PM 346,499 061017-16968-01.dmp
06/14/2017 04:05 AM 307,643 061417-18859-01.dmp
06/14/2017 08:47 AM 308,283 061417-19437-01.dmp
06/14/2017 06:16 AM 309,691 061417-20703-01.dmp
06/15/2017 12:13 PM 308,411 061517-17250-01.dmp
06/15/2017 07:30 AM 310,843 061517-19031-01.dmp
06/15/2017 11:11 PM 319,099 061517-19921-01.dmp
7 File(s) 2,210,469 bytes 2 Dir(s) 1,544,694,919,168 bytes free
C:\WINDOWS\system32>
So right now, I did the following with the respective output just to see if there are any issues:
Running sfc /scannow 3 times
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\WINDOWS\system32>
C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0
No component store corruption detected.
The operation completed successfully.
C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.
C:\WINDOWS\system32>
Hopefully there is a way to find out what files were corrupted as part of the drive repair process so I can replace them if they are not Windows OS files.
I'm going to reboot to see if the following actually runs chkdsk again at boot:
C:\WINDOWS\system32>chkdsk c: /x /f /r
The type of the file system is NTFS.Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y
This volume will be checked the next time the system restarts.
C:\WINDOWS\system32>