Windows 10: Frequent BSOD Wdf01000.sys

I've been getting BSODs when leaving my computer idle. Not running anything intensive. From looking at the minidump file I can't find much other than it's probably because of the Wdf01000.sys driver. Hopefully you can get all of the information you need from the .zip file I attached.

But just in case, here's what I found from Windbg:

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.




Loading Dump File [C:\Windows\Minidump\112315-8171-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 10240 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`4da0b000 PsLoadedModuleList = 0xfffff800`4dd30070
Debug session time: Mon Nov 23 06:44:02.231 2015 (UTC - 8:00)
System Uptime: 0 days 0:32:33.854
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
..............
Cannot read PEB32 from WOW64 TEB32 0000b852 - Win32 error 0n30


************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified


You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 1000007E, {ffffffff80000003, fffff8004db5fb90, ffffd00025bed488, ffffd00025becca0}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : Wdf01000.sys ( Wdf01000+515fc )


Followup: MachineOwner
---------


2: kd> !thread
GetPointerFromAddress: unable to read from fffff8004ddd01c0
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_ETHREAD ***
*** ***
*************************************************************************
ffffe001da73a040: Unable to get thread contents
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff8004db5fb90, The address that the exception occurred at
Arg3: ffffd00025bed488, Exception Record Address
Arg4: ffffd00025becca0, Context Record Address


Debugging Details:
------------------


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************


ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.


FAULTING_MODULE: fffff8004da0b000 nt


DEBUG_FLR_IMAGE_TIMESTAMP: 55fa52b2


DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump


EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid


FAULTING_IP:
nt+154b90
fffff800`4db5fb90 cc int 3


EXCEPTION_RECORD: ffffd00025bed488 -- (.exr 0xffffd00025bed488)
ExceptionAddress: fffff8004db5fb90 (nt+0x0000000000154b90)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000


CONTEXT: ffffd00025becca0 -- (.cxr 0xffffd00025becca0;r)
rax=0000000000000000 rbx=00001ffe28746878 rcx=bf64e18798e60000
rdx=0000000000000008 rsi=00001ffe28746878 rdi=ffffe001d78beab0
rip=fffff8004db5fb90 rsp=ffffd00025bed6c8 rbp=fffff800e3e76040
r8=0000000000000065 r9=0000000000000001 r10=0000000000000000
r11=ffffd00025bed6c8 r12=0000000000000000 r13=fffff800e3eeb3d0
r14=ffffe001d78b9ae8 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000202
nt+0x154b90:
fffff800`4db5fb90 cc int 3
Last set context:
rax=0000000000000000 rbx=00001ffe28746878 rcx=bf64e18798e60000
rdx=0000000000000008 rsi=00001ffe28746878 rdi=ffffe001d78beab0
rip=fffff8004db5fb90 rsp=ffffd00025bed6c8 rbp=fffff800e3e76040
r8=0000000000000065 r9=0000000000000001 r10=0000000000000000
r11=ffffd00025bed6c8 r12=0000000000000000 r13=fffff800e3eeb3d0
r14=ffffe001d78b9ae8 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000202
nt+0x154b90:
fffff800`4db5fb90 cc int 3
Resetting default scope


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


BUGCHECK_STR: AV


CURRENT_IRQL: 0


ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre


EXCEPTION_STR: 0xb852


LAST_CONTROL_TRANSFER: from fffff800e3e915fc to fffff8004db5fb90


STACK_TEXT:
ffffd000`25bed6c8 fffff800`e3e915fc : fffff800`e3e75a40 ffffe001`da73a040 fffff800`e3e76040 00001ffe`28746878 : nt+0x154b90
ffffd000`25bed6d0 fffff800`e3e75a40 : ffffe001`da73a040 fffff800`e3e76040 00001ffe`28746878 ffffd000`00000002 : Wdf01000+0x515fc
ffffd000`25bed6d8 ffffe001`da73a040 : fffff800`e3e76040 00001ffe`28746878 ffffd000`00000002 ffffe001`d78bf920 : Wdf01000+0x35a40
ffffd000`25bed6e0 fffff800`e3e76040 : 00001ffe`28746878 ffffd000`00000002 ffffe001`d78bf920 ffffe001`d78bf920 : 0xffffe001`da73a040
ffffd000`25bed6e8 00001ffe`28746878 : ffffd000`00000002 ffffe001`d78bf920 ffffe001`d78bf920 fffff800`e3e4c924 : Wdf01000+0x36040
ffffd000`25bed6f0 ffffd000`00000002 : ffffe001`d78bf920 ffffe001`d78bf920 fffff800`e3e4c924 ffffd000`25bed900 : 0x00001ffe`28746878
ffffd000`25bed6f8 ffffe001`d78bf920 : ffffe001`d78bf920 fffff800`e3e4c924 ffffd000`25bed900 ffffffff`dc3cba00 : 0xffffd000`00000002
ffffd000`25bed700 ffffe001`d78bf920 : fffff800`e3e4c924 ffffd000`25bed900 ffffffff`dc3cba00 ffffe001`d78b9ae8 : 0xffffe001`d78bf920
ffffd000`25bed708 fffff800`e3e4c924 : ffffd000`25bed900 ffffffff`dc3cba00 ffffe001`d78b9ae8 00000000`00000000 : 0xffffe001`d78bf920
ffffd000`25bed710 ffffd000`25bed900 : ffffffff`dc3cba00 ffffe001`d78b9ae8 00000000`00000000 fffff800`0000003c : Wdf01000+0xc924
ffffd000`25bed718 ffffffff`dc3cba00 : ffffe001`d78b9ae8 00000000`00000000 fffff800`0000003c 00001ffe`00000001 : 0xffffd000`25bed900
ffffd000`25bed720 ffffe001`d78b9ae8 : 00000000`00000000 fffff800`0000003c 00001ffe`00000001 ffffe001`d78b9780 : 0xffffffff`dc3cba00
ffffd000`25bed728 00000000`00000000 : fffff800`0000003c 00001ffe`00000001 ffffe001`d78b9780 fffff800`e3e4b238 : 0xffffe001`d78b9ae8




FOLLOWUP_IP:
Wdf01000+515fc
fffff800`e3e915fc ?? ???


SYMBOL_STACK_INDEX: 1


SYMBOL_NAME: Wdf01000+515fc


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: Wdf01000


IMAGE_NAME: Wdf01000.sys


STACK_COMMAND: .cxr 0xffffd00025becca0 ; kb


BUCKET_ID: WRONG_SYMBOLS


FAILURE_BUCKET_ID: WRONG_SYMBOLS


ANALYSIS_SOURCE: KM


FAILURE_ID_HASH_STRING: km:wrong_symbols


FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}


Followup: MachineOwner
---------


2: kd> lmvm nt
start end module name
fffff800`4da0b000 fffff800`4e25d000 nt (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Wed Nov 04 20:15:48 2015 (563AD7F4)
CheckSum: 007B1BAB
ImageSize: 00852000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> .symfix; .reload
Loading Kernel Symbols
..


Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.


.............................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
..............
Cannot read PEB32 from WOW64 TEB32 0000b852 - Win32 error 0n30



In the past, I was getting a WHEA_UNCORRECTABLE_ERROR from more intensive programs like Unity 3D. I'm not sure if this is related at all.

Thanks in advance for your help!

:)

 

Windows 10 Error

Windows 10 fails frequently with different errors, could anyone help me with this.

System restarts after the fail.

Stop code:

-Kernal Security Check Failure,

-Driver IRQL not Less or Equal, What failed: Wdf01000.sys,

-System Thread Exception not Handled, what failed: UsbHub3.sys

 

Windows error on start up

Hi , I need some urgent help , this morning when I tried to start my PC , it shows BSOD on start up , like not even able to go to login page , I cannot start the automatic repair , as it also shows the BSOD . These are all the errors I got by sequence.

NEL_SECURITY_CHECK_FAILURE

KMODE_EXCEPTION_NOT_HANDLED

DRIVER IRQL NOT LESS OR EQUAL - storahci.sys - The most frequent one

REFS FILE SYSTEM ERROR

DRIVER OVERRUN STACK BUFFER

BAD_POOL_CALLER

ATTEMPtED WRITE TO READONLY MEMORY - Wdf01000.sys

ntfs.sys

Is there any ways to save my computer ? Thanks !

 

Upload a new log, the current one is empty.

You're getting symbol errors.
Is your symbol path correct? Have you saved your workspace?

 

I've attached the new zip file. Sorry it didn't work before.Attachment 50229

 

If you are overclocking, revert back to stock while troubleshooting.
Code: CPUID: "Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz" MaxSpeed: 4000 CurrentSpeed: 4080[/quote] Disable USB connections, except for mouse and keyboard, and see if it helps.
Code: ffffd000`923cc7f8 fffff801`43ae0430 ucx01000!Urb_LegacyTransferUrbCompletion ffffd000`923cc808 fffff801`43ae0e4e ucx01000!UrbHandler_USBPORTStyle_Legacy_BulkOrInterruptTransfer+0x1be ffffd000`923cce28 fffff801`43ae0430 ucx01000!Urb_LegacyTransferUrbCompletion ffffd000`923cce38 fffff801`43ae0e4e ucx01000!UrbHandler_USBPORTStyle_Legacy_BulkOrInterruptTransfer+0x1be ffffd000`923ccf48 fffff801`43ad53ee ucx01000!RootHub_Pdo_EvtInternalDeviceControlIrpPreprocessCallback+0x46e ffffd000`923cc9f8 fffff801`43a9e2a9 USBXHCI!WPP_RECORDER_SF_DDDqq+0x121 ffffd000`923cca88 fffff801`43a9b61c USBXHCI!Bulk_RetrieveNextStage+0x130 ffffd000`923ccb08 fffff801`43a9a82a USBXHCI!Bulk_MappingLoop+0xd2[/quote]