Check Disk while windows updated and now getting driver errors?

[sublimening]

I was working on a friends computer and wanted to check everything so I scheduled a chkdsk without knowing that there was an update going through. After it completed the update looked like it pushed fine but the scan now jumped to 100 % super quick.

I also couldn't find a log of it at all.

Now he is getting tons of driver errors from NVidia and Logitech saying BAD IMAGE and a couple blue screens saying Driver_POWER_STATE_FAILURE

He is doing a system restore which I'm hoping will fix it. Does this sound like something that could happen by doing those both at the same time?

 

[Colif]

Can he do next part just in case system restore doesn't fix problem, that way we can figure out cause

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it


What sort of update was it? windows update runs at shut down/startup... SFC runs in windows? What sort of update could it effect?

 

[sublimening]

Can he do next part just in case system restore doesn't fix problem, that way we can figure out cause

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it


What sort of update was it? windows update runs at shut down/startup... SFC runs in windows? What sort of update could it effect?

Scan now on the drive that has the os requires you to do it on a restart. That restart pushed the update to go through at the same time. Idk what update it was but created a whole windows.old folder.


The system restore worked in fixing the errors so it did corrupt something.

 

[Colif]

I have run SFC /scannow on my SSD many times from within windows... never needed to restart to run it.

It is a chkdsk that needs a restart to run?

i mean, you can run SFC at startup doing this but you don't need to.

Is it fixed now?

 

[sublimening]

I have run SFC /scannow on my SSD many times from within windows... never needed to restart to run it.

It is a chkdsk that needs a restart to run?

i mean, you can run SFC at startup doing this but you don't need to.

Is it fixed now?

yup, nope, it was chkdsk. Sorry I did both and had a brain fart about which was which. It was chkdsk that needed the restart and somehow conflicted with the update... idk

Yeah its fixed now. But you would think that windows would have some kinda case that would stop chkdsk and an update from running on the same restart. Or who knows, maybe the update itself just installed bad and chkdsk had nothing to do with it.

 

[Colif]

Well, a chkdsk is checking the file system so it might have a hard list of right files it needs to find, and if you updating windows 10 at same time, it will be changing some of the files, so I can see chkdsk might alter them back. Or as you say, chkdsk did nothing and the update was messed up.

Next time, think to check updates before running chkdsk