bsod BSOD - Need Help reading dumps

[Phycoforce]

Hi Guys,

 

This BSOD is bizare, as it happens everyday I turn on my computer. It always blue screens on the first loadup, restarts, then is fine the rest of the day. I have tried the following action:

 

1. Reinstall Graphics Driver (Display Driver Uninstaller in Safe Mode)

2. Made sure all drivers are up to date.

3. Fresh Install of Windows.

4. sfc /scannow

5. Full stress test of CPU (Prime95), GPU (FurMark)

 

This problem persisted after all of this. I have also run a full memory test using: MemTest86, and no issue have come up in that test. I need help understanding how to break down these logs, as it seems to die on the same address, same driver, which seems very generic. My information below:

 

OS: Windows 10 Pro (64bit) Build 19042.746

OS Type: Retail

Age: 5 Years

Age of Install: 3 Weeks

CPU Model: i7 5820k

Video Card Model: Nvidia Geforce 1080 (Gigabyte)

Motherboard: X99S SLI PLUS

Power Supply: RM Series™ RM1000 — 1000 Watt 80 PLUS® Gold Certified Fully Modular PSU (UK Plug)

Desktop System

 

Link to Logs: https://drive.google.com/drive/folders/12nRbxnkOyg-97egoGvwCDF0DFR7TrMJ8?usp=sharing

 

PERFMON was running for over an hour, with no actual change to the files, so I had to attach them as is. I would have liked to save it all as a big report, but that doesn't seem to be working also.

 

Thank you in advance for any help regarding this.

[Radium_Angel]

1 hour ago, Phycoforce said:

Thank you in advance for any help regarding this.

Give me some time to work on these dumps, hold please!

[Radium_Angel]

1 hour ago, Phycoforce said:

Thank you in advance for any help regarding this.

Lost power, so I lost my post.

 

Let me re-create. I'll post thoughts at the end

____

DRIVER_VERIFIER_DMA_VIOLATION (e6)
An illegal DMA operation was attempted by a driver being verified.
Arguments:
Arg1: 0000000000000026, IOMMU detected DMA violation.
Arg2: ffffdd82643ca120, Device Object of faulting device.
Arg3: 0000000000100001, Faulting information (usually faulting physical address).
Arg4: 0000000000000005, Fault type (hardware specific).

 

_____

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffd586b1e29cd0, Physical Device Object of the stack
Arg3: fffff8072b86f850, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd586b00848f0, The blocked IRP
 

DRIVER_OBJECT: ffffd586b02ee310

IMAGE_NAME:  xusb22.sys

MODULE_NAME: xusb22

FAULTING_MODULE: fffff8077f960000 xusb22

 

______

Same crash repeats.

 

So, looks like something attached to USB is causing issues (or the USB hub is defective)

[Phycoforce]

3 minutes ago, Radium_Angel said:

Same crash repeats.

 

So, looks like something attached to USB is causing issues (or the USB hub is defective)

Oh, so it looks like it's the USB Hub? That would make sense. I'll explore potential drivers for the hub, switching the USB port it's attached too, or potentially forgoing it all together.

 

I do have a USB hub attached, which I use to switch the keyboard/mouse between two machines. I'll have to diagnose what device is causing the issue via trial and error.

Is this the consistent error between multiple reports?

[Radium_Angel]

3 minutes ago, Phycoforce said:

Oh, so it looks like it's the USB Hub? That would make sense. I'll explore potential drivers for the hub, switching the USB port it's attached too, or potentially forgoing it all together.

 

I do have a USB hub attached, which I use to switch the keyboard/mouse between two machines. I'll have to diagnose what device is causing the issue via trial and error.

Is this the consistent error between multiple reports?

Yes, consistent. and that specific XUSB.SYS file? Looks like from an xbox controller? Are you using one of those?

[Phycoforce]

2 minutes ago, Radium_Angel said:

Yes, consistent. and that specific XUSB.SYS file? Looks like from an xbox controller? Are you using one of those?

Interesting you quote that. I currently use a Nvidia Shield controller connected via bluetooth (Only works if Geforce Experience is installed). Perhaps Windows is trying to connect to this controller on startup, and causing isues?

 

I see the device recognised as a Nvidia Shield controller in bluetooth settings (See Screenshot).

But I find it slightly bizare that it'd recognise that in someway, as an Xbox controller.

[Radium_Angel]

1 minute ago, Phycoforce said:

Interesting you quote that. I currently use a Nvidia Shield controller connected via bluetooth (Only works if Geforce Experience is installed). Perhaps Windows is trying to connect to this controller on startup, and causing isues?

 

I see the device recognised as a Nvidia Shield controller in bluetooth settings (See Screenshot).

But I find it slightly bizare that it'd recognise that in someway, as an Xbox controller.

Yeah, I'd look into disabling that and see if your system will boot cleanly.

 

[Phycoforce]

6 minutes ago, Radium_Angel said:

Yeah, I'd look into disabling that and see if your system will boot cleanly.

 

Thank you. Googling this driver in conjunction with this controller has led to a lot of other people suffering with the same issue. Thank you for the help, I appreciate it. I'll give it a go, and monitor it for the time being.