First step is to turn off fastboot.
Then run a system file check
Please run a system file check (SFC) & DISM (if necessary) if you are on win 8 or higher
All instructions are in our Wiki article below...
Should you have any questions please ask us.
System file check (SFC) Scan and Repair System
Files
Microsoft (R) Windows Debugger Version 10.0.10075.9 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\zigza\Desktop\060215-22640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8.1 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff802`24a1d000 PsLoadedModuleList = 0xfffff802`24cf6850
Debug session time: Tue Jun 2 14:17:11.588 2015 (UTC - 4:00)
System Uptime: 3 days 23:15:16.451
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
.......................
No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {ffffe000c2dc9000, 2, 1, fffff801ca285f40}
*** WARNING: Unable to verify timestamp for fastboot.sys
*** ERROR: Module load completed but symbols could not be loaded for fastboot.sys
Probably caused by : fastboot.sys ( fastboot+bf40 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffe000c2dc9000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff801ca285f40, address which referenced memory
Debugging Details:
------------------
SYSTEM_SKU: LENOVO_MT_20AA
SYSTEM_VERSION: ThinkPad T431s
BIOS_DATE: 06/13/2013
BASEBOARD_PRODUCT: 20AACTO1WW
BASEBOARD_VERSION: 0B98405 Std
BUGCHECK_P1: ffffe000c2dc9000
BUGCHECK_P2: 2
BUGCHECK_P3: 1
BUGCHECK_P4: fffff801ca285f40
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80224d80138
GetUlongPtrFromAddress: unable to read from fffff80224d80298
GetUlongPtrFromAddress: unable to read from fffff80224d80520
ffffe000c2dc9000 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
fastboot+bf40
fffff801`ca285f40 488911 mov qword ptr [rcx],rdx
CPU_COUNT: 4
CPU_MHZ: 704
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: System
ANALYSIS_VERSION: 10.0.10075.9 amd64fre
TRAP_FRAME: ffffd000b77f6ca0 -- (.trap 0xffffd000b77f6ca0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe000c2dc8fe8 rbx=0000000000000000 rcx=ffffe000c2dc9000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801ca285f40 rsp=ffffd000b77f6e38 rbp=fffff801ca288990
r8=0000000000000000 r9=0000000000000002 r10=000000000dc127e0
r11=ffffd000b77f70c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
fastboot+0xbf40:
fffff801`ca285f40 488911 mov qword ptr [rcx],rdx ds:ffffe000`c2dc9000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80224b797e9 to fffff80224b6dca0
STACK_TEXT:
ffffd000`b77f6b58 fffff802`24b797e9 : 00000000`0000000a ffffe000`c2dc9000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd000`b77f6b60 fffff802`24b7803a : 00000000`00000001 ffffe000`c2dc8fe8 ffffd000`bc5a0100 ffffd000`b75ef180 : nt!KiBugCheckDispatch+0x69
ffffd000`b77f6ca0 fffff801`ca285f40 : fffff801`ca2828f4 00000000`00000000 fffff802`24ac7b53 ffff869d`cd4d3fce : nt!KiPageFault+0x23a
ffffd000`b77f6e38 fffff801`ca2828f4 : 00000000`00000000 fffff802`24ac7b53 ffff869d`cd4d3fce fffff802`24ab6571 : fastboot+0xbf40
ffffd000`b77f6e40 00000000`00000000 : fffff802`24ac7b53 ffff869d`cd4d3fce fffff802`24ab6571 00000000`00000000 : fastboot+0x88f4
STACK_COMMAND: kb
FOLLOWUP_IP:
fastboot+bf40
fffff801`ca285f40 488911 mov qword ptr [rcx],rdx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: fastboot+bf40
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: fastboot
IMAGE_NAME: fastboot.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5178a9ac
BUCKET_ID_FUNC_OFFSET: bf40
FAILURE_BUCKET_ID: AV_fastboot!Unknown_Function
BUCKET_ID: AV_fastboot!Unknown_Function
PRIMARY_PROBLEM_CLASS: AV_fastboot!Unknown_Function
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_fastboot!unknown_function
FAILURE_ID_HASH: {0d901479-bf1f-b842-76f2-3db7e4feaedd}
Followup: MachineOwner
---------