Windows 10: Thread_stuck_in_device_driver

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.[/quote]

 

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

 

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 *Smile

 

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[/quote]

 

What do you mean?

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

 

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?

 

It wouldn't have mattered *Wink

 

[/quote] I disabled fast startup.

After turning my computer on after shutdown, still no progress but this time I didn't see BSOD, my screen was just black and then computer restarted.

No, currently I just want to make my computer not BSOD every time I turn it on after shutdown.




What does Windows do differently when it boots after shutdown, and when it boots after BSOD, because there is no BSOD after it boots from BSOD??? So Windows somehow manages to solve that problem on restart, but when recovering from shutdown/sleep, there are errors.

attaching dump file just in case something changed.

 

What hard drive do you have? I can't check the files currently because I'm away of my PC.
Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:

 

Updated. It's ST3320620AS ATA Device.

 

What Windows does differently is that an image of the state of the kernel and drivers in the hiberfil.sys aren't saved anymore since you have disabled Fast startup, fast startup caused some problems for you.

Could you clarify what you mean with 'there are errors'?

 

You didn't understand my question. Disabling fastboot didn't fix anything, my computer behaves exactly the same as before (BSOD).
I meant what's the difference when Windows is booting, and then BSOD happens, then after BSOD there is automatic restart, but then Windows boot normally without BSOD. What's the difference between the first boot where BSOD happens and second boot right after the BSOD when computer manages to boot properly.

I meant BSOD (thread_stuck_in_device_driver).

 

I indeed didn't understand your question, probably because it was a little late for me.

When a BSOD occurs, Windows modificates the system in an attempt to resolve the problem, it would be that either the modifications aren't saved (a bug) or they don't work with the next BSOD as it might be possible that modifications don't work for other causes with a crash. The 0xEA occurs when a driver is in an infinite loop waiting for something, for example the display drivers that are waiting for the video card to enter an idle state, this is a frequently occuring example, but it may not have to do anything at all with the display (note that this doesn't have to be the case)

 

So here's an update. I installed ubuntu 14.04, with all the updates and when I tried to enter "suspend" mode, upon turning my computer back on, I only get black screen so I'm sure now that this is due to hardware problem.

Is there a way to test what might be causing this, since gpu worked fine on another computer?

 

I'm unfamiliar with Ubuntu, how long did you wait?