Xbox 1 controller BSOD every time it connects. No avast

Discus and support Xbox 1 controller BSOD every time it connects. No avast in XBoX on Consoles to solve the problem; I am trying to connect an Xbox 1 controller to my windows computer, and each time it does a bluescreen with the error message IRQ_NOT_LESS_OR_EQUAL I... Discussion in 'XBoX on Consoles' started by Sean Taylor4, Feb 3, 2024.

  1. Sean Taylor4
    Sean Taylor4 Guest

    Xbox 1 controller BSOD every time it connects. No avast


    I am trying to connect an Xbox 1 controller to my windows computer, and each time it does a bluescreen with the error message IRQ_NOT_LESS_OR_EQUAL

    I saw this question elsewhere stating that Avast was the problem, but I do not have Avast. Below is the code from the minidump (did not see where to attach the minidump itself)

    *******************************************************************************
    * *
    * 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: 0000000000000028, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8077e7b3f74, address which referenced memory

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

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 3061

    Key : Analysis.Elapsed.mSec
    Value: 7541

    Key : Analysis.IO.Other.Mb
    Value: 7

    Key : Analysis.IO.Read.Mb
    Value: 21

    Key : Analysis.IO.Write.Mb
    Value: 57

    Key : Analysis.Init.CPU.mSec
    Value: 702

    Key : Analysis.Init.Elapsed.mSec
    Value: 28286

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 107

    Key : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key : Failure.Bucket
    Value: AV_xinputhid!BroadcastDevicesFocusChanged

    Key : Failure.Hash
    Value: {86237f49-e812-2c3d-43b7-926b511731c0}

    Key : WER.OS.Branch
    Value: vb_release

    Key : WER.OS.Version
    Value: 10.0.19041.1

    BUGCHECK_CODE: d1

    BUGCHECK_P1: 28

    BUGCHECK_P2: 2

    BUGCHECK_P3: 0

    BUGCHECK_P4: fffff8077e7b3f74

    FILE_IN_CAB: 020224-10078-01.dmp

    READ_ADDRESS: fffff8077ccfb390: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
    unable to get nt!MmSpecialPagesInUse
    0000000000000028

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXPNP: 1 (!blackboxpnp)

    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: dwm.exe

    TRAP_FRAME: fffffa07626f44d0 -- (.trap 0xfffffa07626f44d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=ffffaa0848b64160
    rdx=fffffa07626f46b0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8077e7b3f74 rsp=fffffa07626f4660 rbp=0000000000000000
    r8=000055f7b749be98 r9=0000000000001024 r10=0000fffff8077e7b
    r11=ffffce7e4aa00000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    Wdf01000!FxObjectHandleGetPtrQI+0x40:
    fffff807`7e7b3f74 488b4028 mov rax,qword ptr [rax+28h] ds:00000000`00000028=????????????????
    Resetting default scope

    STACK_TEXT:
    fffffa07`626f4388 fffff807`7c411aa9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffffa07`626f4390 fffff807`7c40d563 : ffffde80`0294c100 fffffa07`00000000 00000000`00000000 00000000`0000001e : nt!KiBugCheckDispatch+0x69
    fffffa07`626f44d0 fffff807`7e7b3f74 : 00000001`00000000 00000000`00000001 00000000`00000006 00000000`0000001e : nt!KiPageFault+0x463
    fffffa07`626f4660 fffff807`7e7ce58c : ffffaa08`48b64160 ffffb20a`af7c0710 ffffb20a`afb87710 fffffa07`626f4808 : Wdf01000!FxObjectHandleGetPtrQI+0x40 [minkernel\wdf\framework\shared\object\handleapi.cpp @ 376]
    fffffa07`626f46d0 fffff807`811d908e : 00000000`00000000 00000000`00000000 ffffb20a`af7c0710 ffffaa08`47e16e30 : Wdf01000!imp_WdfSpinLockAcquire+0x1bb1c [minkernel\wdf\framework\shared\support\fxspinlockapi.cpp @ 126]
    fffffa07`626f4710 fffff807`811d9e31 : ffff850d`2ef48a01 ffffb20a`b21103f0 ffff850d`2ef48a01 00000000`00000001 : xinputhid!BroadcastDevicesFocusChanged+0x14a
    fffffa07`626f47b0 fffff807`7c70cf47 : ffffffff`ffffffff 00000000`00000000 ffff850d`2e55c340 00000000`00000037 : xinputhid!focusChangedCallback+0x121
    fffffa07`626f47f0 fffff807`7c70ccf9 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpWnfDispatchKernelSubscription+0x1e3
    fffffa07`626f4880 fffff807`7c5f17f4 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffb20a`af3ab8d0 : nt!ExpWnfStartKernelDispatcher+0x49
    fffffa07`626f48b0 fffff807`7c5ef6b1 : ffff850d`2e55c340 00000000`00000004 fffffa07`00000001 00000000`00000001 : nt!ExpWnfNotifyNameSubscribers+0x168
    fffffa07`626f4920 fffff807`7c5ef3ce : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpNtUpdateWnfStateData+0x2d5
    fffffa07`626f4a40 fffff807`7c411238 : ffff591f`ffd26460 fffffa07`626f4b80 00000000`00000000 00000231`64a6a710 : nt!NtUpdateWnfStateData+0x2e
    fffffa07`626f4a90 00007ff8`350909d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
    000000b0`bfa9f048 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`350909d4

    SYMBOL_NAME: xinputhid!BroadcastDevicesFocusChanged+14a

    MODULE_NAME: xinputhid

    IMAGE_NAME: xinputhid.sys

    IMAGE_VERSION: 10.0.19041.3930

    STACK_COMMAND: .cxr; .ecxr ; kb

    BUCKET_ID_FUNC_OFFSET: 14a

    FAILURE_BUCKET_ID: AV_xinputhid!BroadcastDevicesFocusChanged

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {86237f49-e812-2c3d-43b7-926b511731c0}

    Followup: MachineOwner

    *** Moved from Windows / Windows 10 / Performance and system failures ***

    :)
     
    Sean Taylor4, Feb 3, 2024
    #1
  2. Tomm_A Win User

    Xbox 1 controller BSOD every time it connects. No avast

    Hello Sean Taylor4,



    Greetings!



    Thank you for posting in Microsoft Community.



    It seems that that you're experiencing issues with your Xbox 1 controller. The error message you're seeing, "IRQ_NOT_LESS_OR_EQUAL," typically indicates a problem with a hardware device or driver. Let us help you find the possible solution by performing some troubleshooting steps.

    Before we proceed any further, we would like to ask few questions to help us isolate the issue further.

    1. Is this working before?

    2. Does the controller work on Xbox console?

    3. What troubleshooting steps have you done so far to help resolve your concern?

    For the meantime, here are the troubleshooting steps that we can perform:

    1. Make sure your Windows operating system is up to date.

    • Press the Start button on the taskbar, type settings, and then select Settings.
    • Select Update & Security.
    • On the Windows Update page, select Check for updates to see if any updates are available including optional updates for your device.
    • Once the updates have downloaded, select Install now to start the installation.
    • Following installation, we recommend that you restart your device so that the latest updates can take effect.

    2. Try updating the driver for your Xbox 1 controller. You can do this by going to Device Manager, finding the controller under "Xbox Peripherals," right-clicking on it, and selecting "Update driver."



    3. If updating the driver doesn't work, try uninstalling and reinstalling the controller. To do this, go to Device Manager, find the controller under "Xbox Peripherals," right-click on it, and select "Uninstall device." Then, unplug the controller and plug it back in to reinstall the driver.



    4. If none of these steps work, it's possible that there's a hardware issue with your controller. You may want to try connecting it to a different computer to see if the issue persists.

    I hope this helps! Let me know if you have any other questions.



    We look forward to your response. Kindly let us know, if there is any misunderstanding or clarifications of our description by sending us a reply.



    Sincerely,

  3. azur640 Win User

    XBox One Wireless Adapter Driver (BSOD)

    Also having this issue. Only every had the latest driver installed as only purchased two weeks ago. BSOD only occurs after about 10-30min of gaming. Controller otherwise connects and works without issue. This is an older controller without thru 3.5mm headphone
    jack. I updated the controller firmware
  4. Mark Talbot Win User

    XBox One Wireless Adapter Driver (BSOD)

    Hi

    Bought the dongle this week and BSOD mt7612us.sys every time very shortly after starting to stream from XBONE. Controller works perfectly hard wired. The PC is Win 10 32bit. Updated the firmware on the controller, the mediatek update on the PC and the wireless
    adapter driver update but still BSOD. It is not interference. The wireless adapter works fine on my other Win 10 PC, which is a 6 month old 64bit machine but I didn't buy it for this one. Not happy!
  5. RandomSashaLove Win User

    Xbox Game Pass for PC: Slay the Spire Virus

    Avast tend to flag things as a false positive from time to time. I use Avast as an Antivirus software and I have only struck one false positive in the years I used Avast.
  6. blacksoul Win User

    XBox One Wireless Adapter Driver (BSOD)

    Sadly, the new driver (12/8) didn't fix the issue for me either. I'm on Windows 10, 32-bit as well, running version 1511.

    I'm still getting a BSOD after few minutes and then immediately after the reboot that's been caused by the BSOD, if the controller stays connected.
Thema:

Xbox 1 controller BSOD every time it connects. No avast

Loading...

  1. Xbox 1 controller BSOD every time it connects. No avast - Similar Threads - controller BSOD every

  2. Elite 2 controller hasn't been since I bought it!

    in XboX Insiders
    Elite 2 controller hasn't been since I bought it!: Elite 2 controller hasn't had a proper function since I bought into the hype. In menus you literally have to hold the button down for it select anything can't run in most games. Wth 150 purchase...

  3. Stop artificially software-limiting controller polling rates on legacy consoles—let us use...

    in XboX Insiders
    Stop artificially software-limiting controller polling rates on legacy consoles—let us use...: It is completely absurd that players on older-gen consoles like the Xbox One S are stuck dealing with unnecessary software bottlenecks when the console and third-party hardware is fully capable of...

  4. Controller stops working when headset connects

    in XboX Insiders
    Controller stops working when headset connects: Hi all, this intermittent issue only happens sometimes and only with a few games. I power up the Xbox and when my headset pairs with the Xbox my controller no longer works with the game. The home...

  5. Controllers constantly disconnecting and reconnecting

    in XboX Insiders
    Controllers constantly disconnecting and reconnecting: I've played with multiple controllers over the past 10 days and every one of them eventually keeps disconnecting and then reconnecting. It's incredibly frustrating. Has anyone else experienced...

  6. Elite Series 2 controller connectivity problem on Series X

    in XboX Insiders
    Elite Series 2 controller connectivity problem on Series X: The day before yesterday, I joined the insider program and I have had an elite series 2 xbox controller for the past 2 years and I never had a problem with it. Yesterday I was playing siege in My...

  7. Controller inputs "hijacked" when opening Game Bar

    in XboX Insiders
    Controller inputs "hijacked" when opening Game Bar: When I open the Game Bar—whether via controller or keyboard—while a game is running on xCloud through the Xbox app for PC, the Game Bar "steals" the controller input focus. I am forced to...

  8. Momentary disconnection on wired controllers. ASA

    in XboX Insiders
    Momentary disconnection on wired controllers. ASA: I'm having an issue with Alpha Skip Ahead, possibly using a wired controller specifically the Wolverine V3 TE Edition. Sometimes during gameplay, it's sorta like the controller disconnects...

  9. XBOX controller - BSOD when connect

    in XBoX on Consoles
    XBOX controller - BSOD when connect: StartFragment Connecting xbox controllers to my pc, cause BSOD - everytime via bluetooth and occasionally via usb. Windows 11 64 pro MSI Tomahawk X570 Ryzen 5700x3D 32GB CL14 3600Mhz Ram...

  10. My Xbox Series X Controller causes a BSOD when connecting via bluetooth

    in XBoX on Consoles
    My Xbox Series X Controller causes a BSOD when connecting via bluetooth: i have suddenly had this issue where my PC randomly started boot looping. i thought it was some overheating issue but then It works again perfectly fine. then I got to play a game so I turn on my...