Thread_stuck_in_device_driver

harko · 18 Mar 2016

BorisTheAnimal said:

harko, please do these two things:

right click on the Windows logo key in the left bottom corner -> command prompt(admin) and type these commands:

sfc /scannow - press enter and let it run, it might take some time.

Dism /Online /Cleanup-Image /CheckHealth - same as above, press enter and let it run.

So I did this sfc scan and got the following:

Code:

"Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios."

Dism returned the following:

Code:

Deployment Image Servicing and Management tool
Version: 10.0.10586.0


Image Version: 10.0.10586.0


No component store corruption detected.
The operation completed successfully.

I attached this log from sfc.

BorisTheAnimal · 18 Mar 2016

Alright thanks, I'll have a look tomorrow, off to bed!

axe0 · 19 Mar 2016

The SFC log isn't required, it is ONLY required when SFC cannot fix the problem(s) :)

axe0 · 19 Mar 2016

harko said:

As much as it's reasonable to think my gpu is faulty there is as much reason to think it's not. I mean, I tried it in another configuration few days ago (after I got this issue) and it worked like the first day I bought it. It still does the job even on my computer, only problem is that damn startup. At my friend's computer there was no startup issues whatsoever, but here on mine there is.
Is it possible that my motherboard is one to blame, I kinda get that feeling because that's the only thing that we cannot really test. Is there a way that there's some hardware related issue on motherboard that make's it look like it's GPU's fault when in fact, that's not the case??

That could be, but that is usually a very last resort as there are a lot of things to try before.

I've been digging a bit through the event logs, because you say the problem occurs at startup, that makes me think this might be a fast startup problem and fast startup errors occur in the event logs.
Please disable fast startup and let us know if it helps :
Fast Startup - Turn On or Off in Windows 10 - Windows 10 Forums

Code:

Event[1144]:  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2016-03-18T01:25:17.628
  Event ID: 29
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-8Q27U7R
  Description: 
Windows failed fast startup with error status 0xC0000001.

BorisTheAnimal · 19 Mar 2016

In the SFC log it says that opencl.dll was fixed and I bet that this was the issue you had with the GPU.

axe0 · 19 Mar 2016

Opencl.dll was replaced with a driver update for the GPU, but it has no effect on the performance and stability of the system, that has been tested. It is nothing to worry about :)

BorisTheAnimal · 19 Mar 2016

axe0 said:

Opencl.dll was replaced with a driver update for the GPU, but it has no effect on the performance and stability of the system, that has been tested. It is nothing to worry about :)

Not really, he did the install earlier.

Code:

2016-03-19 01:03:48, Info                  CSI    00005179 [SR] Repairing corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll" from store

axe0 · 19 Mar 2016

What do you mean?

Opencl.dll is replaced with an update of the GPU drivers, because of that it was being flagged as corrupted.

BorisTheAnimal · 19 Mar 2016

What I meant was that the file was corrupted and if he hadn't run SFC, we would never have thought of it.

harko, have you tried running any game since you did the scans?

axe0 · 19 Mar 2016

It wouldn't have mattered