Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using
CCleaner looking at Tools > System Restore.
If there is no points,
make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.
___________________________________________________________________________________________
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 44, {fffffa8001b7f5d0, eae, 0, 0}
Probably caused by : bowser.sys ( bowser!BowserCancelQueuedIoForFile+112 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: fffffa8001b7f5d0, Address of the IRP
Arg2: 0000000000000eae
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
IRP_ADDRESS: fffffa8001b7f5d0
FOLLOWUP_IP:
bowser!BowserCancelQueuedIoForFile+112
fffff880`0303c732 488b4c2420 mov rcx,qword ptr [rsp+20h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x44
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001a6a8c0 to fffff80001a81bc0
STACK_TEXT:
fffff880`1409d858 fffff800`01a6a8c0 : 00000000`00000044 fffffa80`01b7f5d0 00000000`00000eae 00000000`00000000 : nt!KeBugCheckEx
fffff880`1409d860 fffff880`0303c732 : fffffa80`010de710 fffff8a0`00dbe6a0 fffffa80`023564b0 fffffa80`010deac8 : nt! ?? ::FNODOBFM::`string'+0x413f2
fffff880`1409d950 fffff880`030378e8 : fffffa80`010de710 fffffa80`0318ec50 fffff880`03037890 fffffa80`010de710 : bowser!BowserCancelQueuedIoForFile+0x112
fffff880`1409d990 fffff880`03031cd3 : fffff8a0`0a2ed610 fffff8a0`00dbe6a0 fffff8a0`0a2ed610 fffffa80`0318ec50 : bowser!BowserCancelRequestsOnTransport+0x58
fffff880`1409d9c0 fffff880`030260de : fffffa80`022c9010 fffffa80`02957aa0 fffffa80`0318ec50 00000000`00000000 : bowser!BowserForEachTransport+0x6f
fffff880`1409da00 fffff800`01d8a96f : fffffa80`022c9010 00000000`00000000 00000000`00000000 fffffa80`023564b0 : bowser!BowserFsdDispatch+0x56
fffff880`1409da30 fffff800`01d78964 : 00000000`00000000 fffffa80`02957aa0 00000000`00000c84 fffffa80`023564b0 : nt!IopCloseFile+0x11f
fffff880`1409dac0 fffff800`01d78721 : fffffa80`02957aa0 fffffa80`00000001 fffff8a0`00dbe6a0 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`1409db40 fffff800`01d78ce4 : 00000000`00000c84 fffffa80`02957aa0 fffff8a0`00dbe6a0 00000000`00000c84 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`1409dbd0 fffff800`01a80e53 : fffffa80`03303840 fffff880`1409dca0 00000000`00000090 fffffa80`0331ba80 : nt!ObpCloseHandle+0x94
fffff880`1409dc20 00000000`76e413aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`025df4d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e413aa
STACK_COMMAND: kb
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: bowser!BowserCancelQueuedIoForFile+112
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: bowser
IMAGE_NAME: bowser.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d649328
FAILURE_BUCKET_ID: X64_0x44_bowser!BowserCancelQueuedIoForFile+112
BUCKET_ID: X64_0x44_bowser!BowserCancelQueuedIoForFile+112
Followup: MachineOwner
---------