Windows 10 don't shut down due to a driver problem

Hi all,
My HP EliteBook 8540w with windows 10 Pro 64, don't shut down, with fast startup enabled.
It creates a Kernel Dump file.
I have used WinDbg and got this result:
On Thu 01-12-2016 23:06:19 your computer crashed
crash dump file: C:\WINDOWS\Minidump\win32k.sys-20161201-2306.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3D7D53)
Bugcheck code: 0xAB (0x1, 0x1D0, 0x1D0, 0x300000003)
Error: SESSION_HAS_VALID_POOL_ON_EXIT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a session unload occurred while a session driver still held memory.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

This can be an outdated driver, right?
How can I identify it and solve it?

Thanks

Please upload the .dmp file for analysis.

I am uploading it.
Thanks

Jorge Martins said:

Hi all,
My HP EliteBook 8540w with windows 10 Pro 64, don't shut down, with fast startup enabled.
It creates a Kernel Dump file.
I have used WinDbg and got this result:
On Thu 01-12-2016 23:06:19 your computer crashed
crash dump file: C:\WINDOWS\Minidump\win32k.sys-20161201-2306.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3D7D53)
Bugcheck code: 0xAB (0x1, 0x1D0, 0x1D0, 0x300000003)
Error: SESSION_HAS_VALID_POOL_ON_EXIT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a session unload occurred while a session driver still held memory.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

This can be an outdated driver, right?
How can I identify it and solve it?

Thanks

Fast Startup is more trouble than worth. I have it turned off on everyone of my computers. Including my wife's computers.

Winuser said:

Fast Startup is more trouble than worth. I have it turned off on everyone of my computers. Including my wife's computers.

Can you explain why, please?
Thank You