BSOD at totall random after updating intel drivers

[monkeymkb]

i updated my intel drivers the other day, and since then ive been getting random BSODs

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


Loading Dump File [C:\WINDOWS\Minidump\021016-90152-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.19135.amd64fre.win7sp1_gdr.160121-1718
Machine Name:
Kernel base = 0xfffff800`0d20d000 PsLoadedModuleList = 0xfffff800`0d454730
Debug session time: Wed Feb 10 05:15:16.240 2016 (UTC - 6:00)
System Uptime: 0 days 0:04:33.722
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {5, 0, 1024, fffffa8005d1d010}

Probably caused by : Wdf01000.sys ( Wdf01000!imp_WdfSpinLockAcquire+47 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000000000005, A framework object handle of the incorrect type was passed to
a framework object method.
Arg2: 0000000000000000, The handle value passed in.
Arg3: 0000000000001024, Reserved.
Arg4: fffffa8005d1d010, Reserved.

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


BUGCHECK_STR: 0x10D_5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff88000e7f903 to fffff8000d2813c0

STACK_TEXT:
fffff880`031a0668 fffff880`00e7f903 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001024 : nt!KeBugCheckEx
fffff880`031a0670 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!imp_WdfSpinLockAcquire+0x47


STACK_COMMAND: kb

FOLLOWUP_IP:
Wdf01000!imp_WdfSpinLockAcquire+47
fffff880`00e7f903 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: Wdf01000!imp_WdfSpinLockAcquire+47

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Wdf01000

IMAGE_NAME: Wdf01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 51c51641

FAILURE_BUCKET_ID: X64_0x10D_5_Wdf01000!imp_WdfSpinLockAcquire+47

BUCKET_ID: X64_0x10D_5_Wdf01000!imp_WdfSpinLockAcquire+47

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000000000005, A framework object handle of the incorrect type was passed to
a framework object method.
Arg2: 0000000000000000, The handle value passed in.
Arg3: 0000000000001024, Reserved.
Arg4: fffffa8005d1d010, Reserved.

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


BUGCHECK_STR: 0x10D_5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff88000e7f903 to fffff8000d2813c0

STACK_TEXT:
fffff880`031a0668 fffff880`00e7f903 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001024 : nt!KeBugCheckEx
fffff880`031a0670 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!imp_WdfSpinLockAcquire+0x47


STACK_COMMAND: kb

FOLLOWUP_IP:
Wdf01000!imp_WdfSpinLockAcquire+47
fffff880`00e7f903 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: Wdf01000!imp_WdfSpinLockAcquire+47

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Wdf01000

IMAGE_NAME: Wdf01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 51c51641

FAILURE_BUCKET_ID: X64_0x10D_5_Wdf01000!imp_WdfSpinLockAcquire+47

BUCKET_ID: X64_0x10D_5_Wdf01000!imp_WdfSpinLockAcquire+47

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

1: kd> lmvm Wdf01000
start end module name
fffff880`00e7b000 fffff880`00f3d000 Wdf01000 (pdb symbols) c:symcache\Wdf01000.pdb\03FC6AA4329F4372BE924775887225632\Wdf01000.pdb
Loaded symbol image file: Wdf01000.sys
Mapped memory image file: c:symcache\Wdf01000.sys\51C51641c2000\Wdf01000.sys
Image path: \SystemRoot\system32\drivers\Wdf01000.sys
Image name: Wdf01000.sys
Timestamp: Fri Jun 21 22:13:05 2013 (51C51641)
CheckSum: 000CC9CA
ImageSize: 000C2000
File version: 1.11.9200.16648
Product version: 1.11.9200.16648
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: wdf01000.sys
OriginalFilename: wdf01000.sys
ProductVersion: 1.11.9200.16648
FileVersion: 1.11.9200.16648 (win8_gdr.130621-1503)
FileDescription: Kernel Mode Driver Framework Runtime
LegalCopyright: © Microsoft Corporation. All rights reserved.

 

[Arc]

Please post a reply following the Blue Screen of Death (BSOD) Posting Instructions so that we can have the dumps and other necessary info.

 

[monkeymkb]

here.

 

[Arc]

Incomplete zip, missing a lot of files. So I cannot know which Xbox do you have. Whatever, uninstall the installed driver for it, download a fresh copy of the driver and install it.

Choose the driver for your Xbox:

• Xbox 360 Controller for Windows
• Xbox 360 Wireless Controller for Windows
• Xbox One Controller + Cable for Windows
• Xbox One Controller + Wireless Adapter for Windows

The available linked driver is not an update; but the above mentioned action sometimes solves this particular issue.

Reeport us for any further BSOD after doing it.
_______________________________________________________

[COLOR=Red]BugCheck 10D[/COLOR], {5, 0, 1024, fffffa8007c91010}

*** WARNING: Unable to verify timestamp for xusb21.sys
*** ERROR: Module load completed but symbols could not be loaded for xusb21.sys
[COLOR=Red]Probably caused by : xusb21.sys[/COLOR] ( xusb21+2888 )

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

    Image name: xusb21.sys
    Browse all global symbols  functions  data
[COLOR=Red]    Timestamp:        Fri Aug 14 03:40:17 2009[/COLOR] (4A848F49)

 

[monkeymkb]

I'm unsure what my controller has to do with this.

what files are missing? i did exactly as instructed.

 

[Arc]

Yours is Xbox 360 or Xbox one? The driver looks like a XBox 360 driver.

If it has a cable connected, get the first one.
If it does not have a cable, like the remote control of the TV, get the second one.

The most important missing file is MSINFO32,nfo. You can upload your MSINFO32.nfo file standalone.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

How to Create a System Information File in Windows.

 

[monkeymkb]

its a wired 360, but that doesn't answer my question of what my controller has to do with my BSOD

 

[axe0]

The xbox driver is causing bluescreen(s) and the 2009 version is known for being a BSOD maker
Driver Reference Table - xusb21.sys

XBox USB wireless controller
BSOD issues in Win7 with 2009 driver (found in mid-2012)

 

[monkeymkb]

ah, alright. what do i do if it blue screens again? it hasnt yet. but it tends to happen at total random.

 

[axe0]

Simply do what Arc suggested in post #2

 

[Arc]

The xbox driver is causing bluescreen(s) and the 2009 version is known for being a BSOD maker
Driver Reference Table - xusb21.sys

XBox USB wireless controller
BSOD issues in Win7 with 2009 driver (found in mid-2012)

And what is most unfortunate that Microsoft havent updated the driver after all the time.
Generally, this comes with bugcheck 10D, or 10E.

The failing xusb21.sys is of August 2009 from the dumps.
In the crash dumps what we see about the driver is ....

    Image name: xusb21.sys
    Timestamp:        Fri [COLOR=Red]Aug 14[/COLOR] 03:40:17 [COLOR=Red]2009[/COLOR] (4A848F49)

But there is no possibility of an update, till date. Because the driver from Microsoft's download location Xbox 360 Controller for Windows contains ....

CatalogFile=xusb21.cat
DriverVer=[COLOR=Red]08/13/2009[/COLOR],2.1.0.1349

What I have noticed that uninstallation of XBox controller and reinstallation sometimes solves the issue.

:ar: http://www.sevenforums.com/bsod-training/332842-specific-actions.html

 

[monkeymkb]

it seems the issue is fixed. but i can't be sure yet. i didn't reinstall the drivers yet. could the fact they auto-instal cause any issues? i havent had another blue screen in over a day now, but i think it would be best to wait a few days before deeming it fixed.

 

[Arc]

It is good that you havent got any BSOD recently. But if you get it again, do what was suggested.

 

[monkeymkb]

ok, it's been quite a while, but recently i used my controller for the first time since this happend, and it all worked out perfectly fine, but when i unplugged the controller, it blue screened again so i uninstalled it, unless anyone knows a way to fix this in particular are there any controllers i should get instead?