Event ID 1001 Bugcheck

Win10Warlord said:

It's the exact same issue as the previous crash and the same driver which I suspect is causing problems - xusb22.sys or the Xbox 360 controller driver. I assume that the dump file is from before you disconnected the controller?

Yes that's correct.

I have disconnected my controller now.

I'm running WDV but only the I/O verification as you recommended - so far nothing untoward.

Ive got an older controller that im going to test over the next few days - when i used it i had no issues.

My current controller i got in September 2020 and the issue i have had has been an intermittent one. Initially i didnt think anything of it because it didnt happen often but i would say in the last month it has surfaced alot more often.

Is this a case of the incorrect driver? I just used the one that was automatically found.
The controller is a Sparkfox Wired Vibration Controller - in device manager it was listed as an xbox 360 controller. Could this be the issue?

Coach81 said:

Is this a case of the incorrect driver? I just used the one that was automatically found.
The controller is a Sparkfox Wired Vibration Controller - in device manager it was listed as an xbox 360 controller. Could this be the issue?

The driver will be the correct one, it's just buggy; if it crashes with the other controller, then I would suggest checking for any available driver updates for controller.

I wouldn't worry about the name mentioned in device manager, it'll be okay, it's likely the device name which was specified in the driver's .INF file.

Win10Warlord said:

The driver will be the correct one, it's just buggy; if it crashes with the other controller, then I would suggest checking for any available driver updates for controller.

I wouldn't worry about the name mentioned in device manager, it'll be okay, it's likely the device name which was specified in the driver's .INF file.

Should i delete any reference of xusb22.sys - or is it ok to leave it provided the controller is unplugged?

It should be okay to leave it installed since the operating system should only load the driver when the PnP Manager has detected that you've plugged in the device. If you crash again, then I would completely uninstall the driver via device manager.

Win10Warlord said:

It should be okay to leave it installed since the operating system should only load the driver when the PnP Manager has detected that you've plugged in the device. If you crash again, then I would completely uninstall the driver via device manager.

Thank you for the help.

Going to test a bit over the next few days with different controllers and what not and see if the error arises again.

No problem, let me know if you have any further issues.

Good day

Apologies for not updating earlier i wanted to give it a week to try out one of my older controllers to see if the issue would changed.

Thankfully no BSOD's yet.

Im not actually sure though what the issue is with the newer controller - it looks like both controllers use the same driver so im not sure why one is fine while the other gives issues.

Is there a way i can possibly fix it or is my newer controller just a dud? I would prefer to use that one but if it gives issues then i have no choice but to discard it.

Also would a Windows 11 upgrade help or alleviate the problem? Im at this stage with Windows 10 where "if it aint broke dont fix it" mentality so i have been somewhat reluctant to upgrade.

I doubt upgrading to Windows 11 will make much difference. The latest Xbox controllers drivers from Windows Update are from 2014 and appear to be for testing purposes only?

Unfortunately, it would appear then, that the issue is with that specific controller. My only suggestion would to be contact the seller or retailer you purchased it from and see if they'll provide you with a replacement controller to test with.

Win10Warlord said:

I doubt upgrading to Windows 11 will make much difference. The latest Xbox controllers drivers from Windows Update are from 2014 and appear to be for testing purposes only?

Unfortunately, it would appear then, that the issue is with that specific controller. My only suggestion would to be contact the seller or retailer you purchased it from and see if they'll provide you with a replacement controller to test with.

Alright thanks, unfortuantely im out of the warranty period so that isn't an option anymore.

I wish i had known this months ago - i was adamant it was some system issue and had no idea that it would be a controller issue.

I will mark this post as "solved" in a few days. Just need to make sure i get no other issues but it looks to be ok now.

At least we've found the cause of your crashes, it's just unfortunate, that you haven't got any warranty available.