WDF_Violation on start up 50% of the time.

Toggle sidebar Toggle sidebar
F

ffttggyy579

Reputable
Nov 8, 2014
32
0
4,530
For about a month now, when ever I start up my PC in the morning, half the time I will encounter a WDF_Violation blue screen error and I don't know what is causing it or how to even go about finding out how. It always occurs after logging in, and happens when the initial programs load up after logging in, that being Skype and Steam, and other background processes, and I have noticed after this blue screen the PC will always boot up fine after, and my steam setting will have been reset (I will have to log in manually, verify with phone, and personal setting like notification noises and stuff are set back to default, and I believe I only have to verify with phone for the first time I log into any PC).
Is there any way I can identify what is causing this issue and how to fix it.

Thanks for the help, if you need any other pieces of info, just ask, and probably tell me how to find it (not the most tech savvy person).
 
Sort by date Sort by votes


System Information (local)
--------------------------------------------------------------------------------

Computer name: CKEE2015
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., MAXIMUS VIII HERO
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17096728576 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 28/02/2017 11:35:42 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\022817-5093-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x7C6F6)
Bugcheck code: 0x10D (0x7, 0x767389394578, 0xFFFF898C76C6BA80, 0xFFFF898C76B77E20)
Error: WDF_VIOLATION
file path: C:\WINDOWS\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 28/02/2017 11:35:42 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x7C6F6)
Bugcheck code: 0x10D (0x7, 0x767389394578, 0xFFFF898C76C6BA80, 0xFFFF898C76B77E20)
Error: WDF_VIOLATION
file path: C:\WINDOWS\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 27/02/2017 12:08:50 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\022717-5531-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x7C6F6)
Bugcheck code: 0x10D (0x7, 0x487AA3960988, 0xFFFFB7855C69F670, 0xFFFFB7855C633670)
Error: WDF_VIOLATION
file path: C:\WINDOWS\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 26/02/2017 12:20:43 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\022617-5531-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x7C6F6)
Bugcheck code: 0x10D (0x7, 0x3CFCDBFD8B98, 0xFFFFC30324027460, 0xFFFFC30324024500)
Error: WDF_VIOLATION
file path: C:\WINDOWS\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 21/02/2017 11:46:59 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\022117-5531-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x7C6F6)
Bugcheck code: 0x10D (0x7, 0x42F8C2EF5A08, 0xFFFFBD073D10A5F0, 0xFFFFBD073A820010)
Error: WDF_VIOLATION
file path: C:\WINDOWS\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

11 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 
Upvote 0 Downvote
Bugcheck code: 0x10D - WDF_VIOLATION
The WDF_VIOLATION bug check has a value of 0x0000010D. This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.

0x7 - A driver attempted to delete a framework object incorrectly by calling WdfObjectDereference to delete a handle instead of calling WdfObjectDelete.

MS LInk

that is all well and good but it didn't tell me what driver caused it.
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)
 
Upvote 0 Downvote


There is a section in "WhoCrashedIt" with dump files, would one of those listed under WDF_violation be the kind of file your looking for?
looks like this: http://imgur.com/a/JSAGT
 
Upvote 0 Downvote


Just uploaded the one file with the wdf_violation. Link here:
https://drive.google.com/file/d/0B91T_NYvYdowcFZQYjI5UzZ6YzQ/view?usp=sharing
Hopefully that link works
 
Upvote 0 Downvote
Another update, another crash, same thing happened as usual, only I saw a small pop up breifly of a corsair window saying no device detected and then crash. The connecting and disconnecting of a device sound windows makes was also made just before the crash, and the only device plugged in via usb is the keyboard (which is corsair) and an xbox one controller via the keyboard.
I ran "whocrashed" after the crash and it gave back this:

On Sat 4/03/2017 12:24:02 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\030417-5203-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x7C6F6)
Bugcheck code: 0x10D (0x7, 0x2BF15E342A48, 0xFFFFD40EA1CBD5B0, 0xFFFFD40EA1B1E930)
Error: WDF_VIOLATION
file path: C:\WINDOWS\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 4/03/2017 12:24:02 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x7C6F6)
Bugcheck code: 0x10D (0x7, 0x2BF15E342A48, 0xFFFFD40EA1CBD5B0, 0xFFFFD40EA1B1E930)
Error: WDF_VIOLATION
file path: C:\WINDOWS\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Link is to the mini dump file:
https://drive.google.com/open?id=0B91T_NYvYdowRE52ZHZlTkRHMUk

The memory dump is fairly large (700mb) so I haven't uploaded it yet, but if you need a copy of it I can do so.
 
Upvote 0 Downvote
no one who can read dumps seems to be looking at this thread so I would read the instructions on top of this forum and post a question to them as they might find an answer I can't yet - https://www.tenforums.com/bsod-crashes-debugging/

Sorry I couldn't help more. If they can't help, come back and I see what else to try :)
 
Upvote 0 Downvote
Update, same thing happened this morning, only this time "whocrashed" has given a new message, same crash error code (wdf_violation) but the end message was different.

Message was:
13 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

xboxgip.sys (Game Input Protocol Driver, Microsoft Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Main thing being the "xboxgip.sys (Game Input Protocol Driver, Microsoft Corporation)" part.
Now I am making an assumption this is referring to my xbox one controller which is almost always plugged in, so I have re-downloaded the drivers for it, and hopefully things work out, though again, this is an assumption as to what its referring to, net search also pointed to a logitec g920 which is a steering wheel. Ill try to keep you guys posted on results.
If anyone else has any idea on the cause/solutions feel free to chime in.

Thanks for all the help.
 
Upvote 0 Downvote
If you get any more errors, you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, run Who crashed and see what driver it reveals

if it reveals driver verifer itself crashed PC, it means there may be no bad drivers

Rarely this can put PC in boot loop so download the Windows 10 media creation tool and use it to make a win 10 installer on USB, just in case. its a handy boot drive

This page seems to verify your assumption about driver, driver itself was causing errors for people in December, so its possible you found the cause. Only a lack of BSOD will prove it though
 
Upvote 0 Downvote
Been a week now, and haven't crashed on start up once, so I am assuming it was the xbox one controller drivers that were playing up, either that or I've gotten a really lucky streak. Thanks for all the help.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom