The driver may not actually be a system driver but belonging to a 3rd party program and uninstalling/reinstalling that program when identified could resolve.
You seem to be using a lot of memory in the log report.
I don't have time to run the program to check mine at the moment but memory can be taken up when there are a lot of programs enabled in Task Manager/Start-up.
I have very little running in mine as you will see from the attached snip.
If you've never been into Task Manager before, right click on the taskbar and select Task Manager.
You may be presented with a blank window where you will need to click on More details on the bottom left and then click on Start-up.
When you open Event Viewer, ensure Event Viewer (Local) is highlighted in the left pane - if it isn't, just click on it and when it has read the data you will see the headings for Critical, Error etc.
Click on either then on View All Instances of This Event in the lower right pane.
Clicking on any of the Event IDs will produce more details in the pane below.
BlueScreenView will analyse the mini dump files which you can copy & paste into your reply.
http://www.nirsoft.net/utils/blue_screen_view.htmlThere is a member who is quite experienced in dealing with BSODs who may pick up on your thread if/when he comes on.
I don't have anything on my computer that can read a mini dump file, so would have to rely on what BlueScreenView reported.
In Device Manager click on View/Show hidden devices and that will display more sections to check.