I might have missed it. If you alter a post, that does not change the thread subscription status. From the next time, please supply information in a subsequent post.
The crash dump is kinda silent. Nothing significant is obtained from it about the reason of the BSOD. Before proceeding to further steps let us know one thing .... was the BSOD occurred with the apple device connected? If you dont connect the Apple device via USB .... what is the situation?
Try to update it from Apple - Downloads
Code:
usbaapl64.sys | Apple Mobile USB Driver
Probably it is controlled by iTunes? I dont have any clear idea about apple .... use windows OS and samsung device only 
If the update does not solve the issue, 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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
_____________________________________________________________
BSOD ANALYSIS:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff800ff252380, 2, 0, fffff800030dfceb}
Probably caused by : afd.sys ( afd!AfdPoll32+771 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff800ff252380, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030dfceb, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330c100
GetUlongFromAddress: unable to read from fffff8000330c1c0
fffff800ff252380 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiInsertTimerTable+13b
fffff800`030dfceb 488b42f8 mov rax,qword ptr [rdx-8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: firefox.exe
TRAP_FRAME: fffff8800d9d94d0 -- (.trap 0xfffff8800d9d94d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff800ff252388 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030dfceb rsp=fffff8800d9d9660 rbp=fffff80003252388
r8=fffffa800a802020 r9=0000000000000008 r10=fffff88003765180
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KiInsertTimerTable+0x13b:
fffff800`030dfceb 488b42f8 mov rax,qword ptr [rdx-8] ds:fffff800`ff252380=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030d41a9 to fffff800030d4c00
STACK_TEXT:
fffff880`0d9d9388 fffff800`030d41a9 : 00000000`0000000a fffff800`ff252380 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0d9d9390 fffff800`030d2e20 : 00000000`00000000 fffffa80`0a802000 00000000`d0646641 fffffa80`0a802060 : nt!KiBugCheckDispatch+0x69
fffff880`0d9d94d0 fffff800`030dfceb : fffffa80`0f8fb0d0 d0646641`00000000 00000000`00000000 00000000`a0000003 : nt!KiPageFault+0x260
fffff880`0d9d9660 fffff800`030df9b0 : ffffff67`6a189680 fffff880`03765180 fffffa80`0a802060 00000000`00000000 : nt!KiInsertTimerTable+0x13b
fffff880`0d9d96c0 fffff800`030df8b4 : fffffa80`0a802000 ffffff67`6a189680 00000000`00000000 fffffa80`0f5c3290 : nt!KiSetTimerEx+0xf0
fffff880`0d9d9750 fffff880`04d5e5f1 : ffffff67`6a189680 fffffa80`0a802000 ffffff67`6a189680 fffffa80`0f8fb010 : nt!KeSetTimer+0x14
fffff880`0d9d9790 fffff880`04d50f3b : fffffa80`0b1a2000 fffffa80`0a802001 00000000`00000000 00000000`0000010b : afd!AfdPoll32+0x771
fffff880`0d9d98a0 fffff800`033f2f37 : fffffa80`0752e610 fffff880`0d9d9b60 fffffa80`0f8fb200 fffffa80`0f8fb010 : afd! ?? ::GFJBLGFE::`string'+0x17a5
fffff880`0d9d98d0 fffff800`033f3796 : fffff880`0d9d9ab8 00000000`0000024c 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0d9d9a00 fffff800`030d3e93 : fffff880`0d9d9b60 fffffa80`0f773910 fffff880`0d9d9ab8 00000000`0422aa01 : nt!NtDeviceIoControlFile+0x56
fffff880`0d9d9a70 00000000`74ef2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02dbf038 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74ef2e09
STACK_COMMAND: kb
FOLLOWUP_IP:
afd!AfdPoll32+771
fffff880`04d5e5f1 488b86b8000000 mov rax,qword ptr [rsi+0B8h]
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: afd!AfdPoll32+771
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: afd
IMAGE_NAME: afd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4efa9418
FAILURE_BUCKET_ID: X64_0xA_afd!AfdPoll32+771
BUCKET_ID: X64_0xA_afd!AfdPoll32+771
Followup: MachineOwner
---------
Quote