Event ID 1001 Bugcheck

If possible run the various tests during the 48 hours so that each driver has been tested with each of the selected customized tests for 36 hours or more. You'll be the judge. If you're unsure just run WDV longer in the background so it can run without major performance problems.

The livekernelreport had displayed one misbehaving driver.
However this driver has not yet misbehaved during WDV testing.
The memory dump did not display a misbehaving driver.
If 48 hours or more of testing does not display any misbehaving drivers then they are typically ruled out as the cause of the crashes.
If there is relatively easy access the BIOS can be reset.
Then hardware can be stress tested.
In case there are any BSOD then post a new V2 and memory dump.

List any hardware that had been connected via Bluetooth or to USB ports earlier in the thread.

zbook said:

If possible run the various tests during the 48 hours so that each driver has been tested with each of the selected customized tests for 36 hours or more. You'll be the judge. If you're unsure just run WDV longer in the background so it can run without major performance problems.

The livekernelreport had displayed one misbehaving driver.
However this driver has not yet misbehaved during WDV testing.
The memory dump did not display a misbehaving driver.
If 48 hours or more of testing does not display any misbehaving drivers then they are typically ruled out as the cause of the crashes.
If there is relatively easy access the BIOS can be reset.
Then hardware can be stress tested.
In case there are any BSOD then post a new V2 and memory dump.

List any hardware that had been connected via Bluetooth or to USB ports earlier in the thread.

So any changes to the testing must i update here?

i.t.o hardware connected to usb ports:

-mouse
-keyboard
-xbox360 game controller
-headphones

I have no idea the numbering/usb port they are attached to all peripherals are usb.

I have no bluetooth devices currently connected.

One more trial and error step is to keep WDV running in the background and install only one hardware device at a time.
For example connect the headphones only for 12 hours while using various WDV customized tests.

The issue is most likely due to your Xbox 360 controller, it was the device which was being removed at the time of the crash.

Win10Warlord said:

The issue is most likely due to your Xbox 360 controller, it was the device which was being removed at the time of the crash.

Yeah i had that feeling as well - i have changed the USB port and i havnt had any issues so far but i cant be 100% sure it fixed the issue.

- - - Updated - - -

Ok so i have slightly adjusted the custom settings for WDV:



I found that "Force IRQL Checking" was causing the startup delays and "Kernel sync delay fuzzing" was causing the performance issues.

I will run with this and monitor progress.

Driver Verifier will probably find no issues since none of the tests have been designed to test the issue at hand. The reason why the system crashed is because a driver (highly suspect the Xbox 360 controller), likely forgot to release its I/O remove lock when processing the PnP IRP, so when a power request came along, the PnP manager wasn't able to return the number of currently present PnP capable devices in time.

The only two DV options which are likely to be useful in a similar situation are I/O Verification and Enhanced I/O Verification, the latter of which should automatically be enabled. If you have another crash, then I would consider booting without the controller connected and/or removing or updating the controller drivers if possible.

Unfortunately looks like im back to square one again.

I got the whole game freezing at the splash screen again - waited 5 minutes to see if it would do anything but nothing, unplugged the controller and game actually started up.

Played with mouse and keyboard fine for a few minutes. Went back to windows device manager and noticed HID-compliant game controller had an exclamation mark warning sign next to it again. Tried trying different ports and controller did not register.

Actually tried a few usb ports and funny thing is my system froze - nothing worked couldnt move mouse nothing worked.

So i pressed power button once and it went into "shutting down" mode except that took about 5 minutes when i got back to my pc it had already started up again.

Checked event viewer - same bugcheck error. Device manager showed no errors with HID-compliant game controller.

Since this last happened i made an effort to unplug the controller when i wasn't using it and i hadnt had any errors since.

So ive disabled WDV. Will upload memory.dmp file in due course - takes a while from my end.
Updated V2.

- - - Updated - - -

Win10Warlord said:

Driver Verifier will probably find no issues since none of the tests have been designed to test the issue at hand. The reason why the system crashed is because a driver (highly suspect the Xbox 360 controller), likely forgot to release its I/O remove lock when processing the PnP IRP, so when a power request came along, the PnP manager wasn't able to return the number of currently present PnP capable devices in time.

The only two DV options which are likely to be useful in a similar situation are I/O Verification and Enhanced I/O Verification, the latter of which should automatically be enabled. If you have another crash, then I would consider booting without the controller connected and/or removing or updating the controller drivers if possible.

Hi mate - only saw this post now after my system crashed again.

Controller issue again - i have disconnected for now. Strange i had no issue for a week with controller disconnected.

I plugged it in now cause i wanted to get a better feel of issue with WDV but with what you said it seems like its a waste of time trying to test.

I'll leave the controller completely unplugged for now and see if the system remains stable without any crashes. You can leave DV enabled if you wanted to, but the only option which would probably have any use, is I/O verification.

Latest Memory.dmp:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

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?