Thread_stuck_in_device_driver

axe0 said:

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.

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.

BorisTheAnimal said:

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

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.

axe0 said:

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 specs

Please 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.

axe0 said:

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).

axe0 said:

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?

axe0 said:

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

The black screen was there for more than 10 minutes. Now even if I try to boot from Ubuntu dvd, I got the black screen because it uses same driver settings as before.

I'm planing on buying new motherboard, processor and RAM. Only thing I'm afraid of is that maybe hard disk isn't the one to blame, what do you think?