[HELP] Misbehaving driver

What about the other scans? Already tried them?

The other scans below, except for Malwarebytes and your AV, are the onces I mean. Did you also run them?

axe0 said:

Diagnostics Test

 Malware scan

Please run a threat scan with Malwarebytes*, a full scan with your AV, scan your system with Adwcleaner, Kaspersky TTDSKiller, ESET Online Scanner and SuperAntiSpyware

   Note

*(Uncheck trial version in the installation process)

No, before I hadn't but now I ran each AV programs except the Kasperkey's (as it was taking too long to download, probably because it was coming from all the way in america and I was in UK, maybe).

I received no problems except SuperAntiSpyware showed me loads of tracking stuff that is not really harmful so I didn't remove those.

---

I received a new BSOD with error message system_thread_exception_not_handled(fltmgr.sys).
I noticed that I get these Blue Screens every time I try to start my PC when I had shutted it down from Windows 10 (instead of hard shutting it or restarting it.)
I think I link this to a HDD problem not becoming 'ready' in time for the hybrid Windows 10 startup.
Like I suggested from this website. <<<Click here

The DM Log collector file is attached, like always.

What are your thoughts upon this?

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 including PSU, cooling system and other used stuff. PSU, cooling system and other used stuff are not mentioned in the tool.

How to fill in your system specs:

Please disable fast startup
Fast Startup - Turn On or Off in Windows 10 - Windows 10 Forums

Code:

Event[4562]:  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2016-01-16T12:31:09.607
  Event ID: 29
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: amodi
  Description: 
Windows failed fast startup with error status 0xC0000001.

It is only for testing purpose, if it seems to help then you need to contact Microsoft about it as there might be a bug somewhere.