Question Constant system freezes with occasional BSOD - - - and something is logging on ?

[bkdoorbandit]

So this is a 3 months old fresh build.

MAG B650 TOMAHAWK WIFI (MS-7D75)
AMD Ryzen 5 7600
Kingston 32GB (2x16GB) DDR5 6000MHz CL36 FURY Beast
ZOTAC GeForce RTX 4070 SUPER
MSI MAG A750GL PCIE5 750W

Running W11 Pro (Not cracked!).

Since start I've had the same issue coming and going. Sometimes I'm OK for several days, some days I'm plagued every other minute.

What's happening is that the system freezes. I can't move anything, I can't open task manager or interact with the system in any way. After about 10-20 sec actions I've made during that time go through like opening task manager, although extremely slow for about another 5-10 sec. Sometimes it just doesn't recover and I get a BSOD.
It's primarily happening when I'm playing games, but the work load of the game doesn't seem to matter as it's happening in Apex, BG3, Destiny, WoW Classic. When it happens I usually lose sound in game.

Naturally my drivers are up to date and the problems have been happening over several versions.

I know Event Viewer doesn't say too much but there's one thing always happening the moment XXXXX [Moderator edit to remove profanity ], I don't know if it's relevant but it's the only thing I've found:

An account was successfully logged on.

Subject:
Security ID: SYSTEM
Account Name: ACCOUNTNAME$
Account Domain: WORKGROUP
Logon ID: 0x3E7

Logon Information:
Logon Type: 5
Restricted Admin Mode: -
Remote Credential Guard: -
Virtual Account: No
Elevated Token: Yes

Impersonation Level: Impersonation

New Logon:
Security ID: SYSTEM
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon ID: 0x3E7
Linked Logon ID: 0x0
Network Account Name: -
Network Account Domain: -
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x404
Process Name: C:\Windows\System32\services.exe

Network Information:
Workstation Name: -
Source Network Address: -
Source Port: -

Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

These types of logons happen all the time otherwise too without freezing.
I have no idea of how and where to look but it's driving me mad.
Any tip is very much appreciated.

Kind regards

 

[Ralston18]

Look in Reliability HistoryMonitor and Task Scheduler.

There may be some entries in Reliabiity History/Monitor that correspond with the times of the cited problems.

Also look in Task Scheduler for any circumstances or rules being used to "trigger" some app or process.

 

[ubuysa]

Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

 

[bkdoorbandit]

Thank you guys for replying.

And what a neat tool! @ubuysa
Some logs timed out, but I've uploaded a zip here - https://drive.internxt.com/sh/file/...00feaae46b4b418cb372da8610319f63b5ceea94f6d40

Also @Ralston18 thanks for the tip, I found some weird stuff.

I'm super curious about what type of hardware error occurred but they don't seem to be related to the BSOD's but I think they may be involved in some of the freezes as not all lead to BSOD. And I couldn't really find any related triggers except those going off after reboots.

How do I find out what the hardware errors were?

Edit: One relevant timestamp for the last BSOD yesterday was 22:01:39

 

[kira-faye]

Look in to DCP latency issues, that may point you in the direction of the problematic software or hardware. Sometimes all it takes is disabling something you weren't even using in hardware manager to make everything else get along.

 

[Ralston18]

@bkdoorbandit

Do you know if you may been the cause of those "not properly shutdown" errors? Being that at one time or another you had no other choice but to shut off system in order to recover.

Another place to look requires more time and effort to navigate and understand.

Event Viewer.

FYI:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

And as a general means resolve some issues try the built in Windows troubleshoots. The troubleshooters may find and fix something.

Also "dism" and "sfc /scannow" could resolve some issue

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Current objective being to things down as much as possible via elimination.

 

[ubuysa]

I think the problem here is a storage device, and it looks to be the Kingston XS1000 because, although we see the Windows storport.sys drive called in the two dumps, we don't see the Windows stornvme.sys driver called, which we would expect to see if this was your NVMe drive, but we do see the storachi.sys driver, which we would expect with an ACHI drive.

That it's a storage drive causing these two different power related BSODs can be seen in the dumps....

032424-11109-01.dmp
FAILURE_BUCKET_ID:  0xa0_1_storport!StorPortAdapterPowerRequiredStep2

012624-7859-01.dmp
FAILURE_BUCKET_ID:  0x9F_4_storahci_IMAGE_pci.sys

In both dumps they appear to fail on the power IRP - this is the mechanism that transitions the power state from idle to running - so I rather suspect that the Kingston XS1000 may be having power transition problems. One thing you can try is adjusting the Hard Disk setting in your active power plan so that the 'Turn Off Hard Disks After...' setting is set to 0. That stops hard disks turning off and thus stops them entering a low power state. See whether that stops these BSODs.

 

[bkdoorbandit]

Spoiler

@bkdoorbandit

Do you know if you may been the cause of those "not properly shutdown" errors? Being that at one time or another you had no other choice but to shut off system in order to recover.

Another place to look requires more time and effort to navigate and understand.

Event Viewer.

FYI:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

And as a general means resolve some issues try the built in Windows troubleshoots. The troubleshooters may find and fix something.

Also "dism" and "sfc /scannow" could resolve some issue

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Current objective being to things down as much as possible via elimination.

@Ralston18
No the shutdowns were forced by the system. I've done both dism and scannow actions now. Thank you for helping

Spoiler

I think the problem here is a storage device, and it looks to be the Kingston XS1000 because, although we see the Windows storport.sys drive called in the two dumps, we don't see the Windows stornvme.sys driver called, which we would expect to see if this was your NVMe drive, but we do see the storachi.sys driver, which we would expect with an ACHI drive.

That it's a storage drive causing these two different power related BSODs can be seen in the dumps....

032424-11109-01.dmp
FAILURE_BUCKET_ID:  0xa0_1_storport!StorPortAdapterPowerRequiredStep2

012624-7859-01.dmp
FAILURE_BUCKET_ID:  0x9F_4_storahci_IMAGE_pci.sys

In both dumps they appear to fail on the power IRP - this is the mechanism that transitions the power state from idle to running - so I rather suspect that the Kingston XS1000 may be having power transition problems. One thing you can try is adjusting the Hard Disk setting in your active power plan so that the 'Turn Off Hard Disks After...' setting is set to 0. That stops hard disks turning off and thus stops them entering a low power state. See whether that stops these BSODs.

@ubuysa
I really appreciate you taking the time to look at my logs!

What you found actually makes a lot of sense, I keep my games on an external drive as I switch computers every now and then. Haven't experience these problems on my laptop though. I've changed the power setting so we'll see if that does it. If not I'll try moving my games to my internal drive.

Can I ask which log you looked at and why?

I was thinking maybe my RAM was messing, I have EXPO active but to be honest I'm not sure in what way that works so I have no idea if that could interfere in any way.

Kind regards

 

[ubuysa]

Can I ask which log you looked at an why?

Those details came from the memory dumps. Why? Because that's where the most detailed information is to be found.

I was thinking maybe my RAM was messing, I have EXPO active but to be honest I'm not sure in what way that works so I have no idea if that could interfere in any way.

Bad RAM is always a potential cause, it's worth testing it...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Let us know how that goes.

 

[bkdoorbandit]

@ubuysa

I've turned off the disk sleep off monday.
Moved the game files to my internal C.
Worked flawlessly until yesterday when I got about 3 small freezes.
Today I've experienced several freezes and 2 unexpected shutdowns.
Will run memtest tonight.
If that doesn't find anything I might try downgrading to W10.


Is there any of the reports from the BSODcollection I can look in for the most recent crashes? The .dmp files seem to be of old occurrences.
Is there any monitoring tool that can capture what happens when I get the crashes like today?

Edit: Also while I ran a AIDA64 benchmark it crashed during a CPU-test.

 

[bkdoorbandit]

Bad RAM is always a potential cause, it's worth testing it...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Let us know how that goes.

Done, and 0 errors. I have tried to make windows create dump files on crashes where I've changed it from minidumps to use larger dump methods but it just won't create any. I have no idea what to check or with what anymore so I'm gonna try to downgrade to W10. Since I seem to have some random hardware errors too (far from every time the system freezes, and I get no info on what kind of error) I don't expect it to solve everything but hopefully maybe I can start getting some .dmp's.

 

[ubuysa]

Set your dump type to 'Automatic memory dumps' and nothing else.

The Memtest86 results are encouraging. The other common denominator in the two dumps is the Windows storport.sys driver, the Windows storage device driver. In one dump we also see the storachi.sys driver, the Windows SATA device driver. What we don;t see in either dump is the stornvme.sys driver, the Windows NVMe device driver, so it would appear then that the device having power problems is a SATA drive - that means it must be your Kingston XS100 drive.

I believe that's an external drive? That would also explain why we're seeing calls to Windows PnP functions. Make sure the device is connected properly and if it needs external power make sure it's getting power.

 

[bkdoorbandit]

Set your dump type to 'Automatic memory dumps' and nothing else.

The Memtest86 results are encouraging. The other common denominator in the two dumps is the Windows storport.sys driver, the Windows storage device driver. In one dump we also see the storachi.sys driver, the Windows SATA device driver. What we don;t see in either dump is the stornvme.sys driver, the Windows NVMe device driver, so it would appear then that the device having power problems is a SATA drive - that means it must be your Kingston XS100 drive.

I believe that's an external drive? That would also explain why we're seeing calls to Windows PnP functions. Make sure the device is connected properly and if it needs external power make sure it's getting power.

I have tried, and failed, to understand in which file you see everything and also how to properly read a .dmp file. I've tried BlueScreenView but I think I'm not using it right. Anyhow I downgraded to Win10 monday and that was problem free for a day. Then I froze for a while and then crashed while playing WoW Classic on my internal drive. I noticed that when running W10 I get a whole lot more Hardware issues that I managed to track down to being USB not working right.

The hardware errors are:

Spoiler

Problem signature
Problem Event Name: LiveKernel
EventCode: 144
Parameter 1: 3003
Parameter 2: ffffdc8ad4ad7030
Parameter 3: 40010007
Parameter 4: 0OS version: 10_0_19045
Service Pack: 0_0
Product: 256_1OS
Version: 10.0.19045.2.0.0.256.48
Locale ID: 8192

Code: 144 - This code generally indicates a USB-related error.
Parameter 1: 3003 - This specific parameter often points towards a USB device failing or triggering an error.

I have tried every USB port I have and they all produce the same error.

So I spent yesterday talking to chatgpt.

I have run memtest86 - no problems
Chkdsk - no problem
Windows drivers- up to date
BIOS - up to date
Snappydrivers - up to date
MSI center - up to date
Steelseries software - up to date
USB selective suspend setting - Disabled

Problems I get: Every USB port gets an error:Unknown USB device(Configuration Descriptor Request Failed) When connecting anything like keyboard, mouse or headset. But NOT external SSD.
All devices I connected are tested in 2 other systems where they did not produce any errors.

I booted from a Ubuntu stick to see if the USB problems were there too and this was the result:

Spoiler

$ sudo dmesg | grep -i usb
[ 0.289796] ACPI: USB4 _OSC: OS supports USB3+ DisplayPort+ PCIe+ XDomain+
[ 0.289798] ACPI: USB4 _OSC: OS controls USB3+ DisplayPort+ PCIe+ XDomain+
[ 0.341663] ACPI: bus type USB registered
[ 0.341663] usbcore: registered new interface driver usbfs
[ 0.341663] usbcore: registered new interface driver hub
[ 0.341663] usbcore: registered new device driver usb
[ 0.736949] xhci_hcd 0000:0e:00.0: new USB bus registered, assigned bus number 1
[ 0.793235] xhci_hcd 0000:0e:00.0: new USB bus registered, assigned bus number 2
[ 0.793238] xhci_hcd 0000:0e:00.0: Host supports USB 3.2 Enhanced SuperSpeed
[ 0.793949] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
[ 0.793953] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.793955] usb usb1: Product: xHCI Host Controller
[ 0.793957] usb usb1: Manufacturer: Linux 6.8.0-31-generic xhci-hcd
[ 0.793959] usb usb1: SerialNumber: 0000:0e:00.0
[ 0.794118] hub 1-0:1.0: USB hub found
[ 0.794708] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 0.794733] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.08
[ 0.794736] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.794738] usb usb2: Product: xHCI Host Controller
[ 0.794739] usb usb2: Manufacturer: Linux 6.8.0-31-generic xhci-hcd
[ 0.794741] usb usb2: SerialNumber: 0000:0e:00.0
[ 0.794820] hub 2-0:1.0: USB hub found
[ 0.795106] xhci_hcd 0000:10:00.3: new USB bus registered, assigned bus number 3
[ 0.795921] xhci_hcd 0000:10:00.3: new USB bus registered, assigned bus number 4
[ 0.795923] xhci_hcd 0000:10:00.3: Host supports USB 3.1 Enhanced SuperSpeed
[ 0.795948] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
[ 0.795950] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.795951] usb usb3: Product: xHCI Host Controller
[ 0.795952] usb usb3: Manufacturer: Linux 6.8.0-31-generic xhci-hcd
[ 0.795953] usb usb3: SerialNumber: 0000:10:00.3
[ 0.796024] hub 3-0:1.0: USB hub found
[ 0.797681] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[ 0.797698] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.08
[ 0.797699] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.797701] usb usb4: Product: xHCI Host Controller
[ 0.797702] usb usb4: Manufacturer: Linux 6.8.0-31-generic xhci-hcd
[ 0.797703] usb usb4: SerialNumber: 0000:10:00.3
[ 0.797769] hub 4-0:1.0: USB hub found
[ 0.799586] xhci_hcd 0000:10:00.4: new USB bus registered, assigned bus number 5
[ 0.800339] xhci_hcd 0000:10:00.4: new USB bus registered, assigned bus number 6
[ 0.800341] xhci_hcd 0000:10:00.4: Host supports USB 3.1 Enhanced SuperSpeed
[ 0.800365] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
[ 0.800367] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.800368] usb usb5: Product: xHCI Host Controller
[ 0.800369] usb usb5: Manufacturer: Linux 6.8.0-31-generic xhci-hcd
[ 0.800370] usb usb5: SerialNumber: 0000:10:00.4
[ 0.800436] hub 5-0:1.0: USB hub found
[ 0.801997] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[ 0.802013] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.08
[ 0.802014] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.802015] usb usb6: Product: xHCI Host Controller
[ 0.802016] usb usb6: Manufacturer: Linux 6.8.0-31-generic xhci-hcd
[ 0.802017] usb usb6: SerialNumber: 0000:10:00.4
[ 0.802079] hub 6-0:1.0: USB hub found
[ 0.803857] xhci_hcd 0000:11:00.0: new USB bus registered, assigned bus number 7
[ 0.805132] xhci_hcd 0000:11:00.0: USB3 root hub has no ports
[ 0.805553] xhci_hcd 0000:11:00.0: new USB bus registered, assigned bus number 8
[ 0.805555] xhci_hcd 0000:11:00.0: Host supports USB 3.0 SuperSpeed
[ 0.805583] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
[ 0.805585] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.805586] usb usb7: Product: xHCI Host Controller
[ 0.805587] usb usb7: Manufacturer: Linux 6.8.0-31-generic xhci-hcd
[ 0.805588] usb usb7: SerialNumber: 0000:11:00.0
[ 0.805652] hub 7-0:1.0: USB hub found
[ 0.806502] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
[ 0.806519] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.08
[ 0.806520] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.806521] usb usb8: Product: xHCI Host Controller
[ 0.806523] usb usb8: Manufacturer: Linux 6.8.0-31-generic xhci-hcd
[ 0.806524] usb usb8: SerialNumber: 0000:11:00.0
[ 0.806585] hub 8-0:1.0: USB hub found
[ 1.043195] usb 5-1: new full-speed USB device number 2 using xhci_hcd
[ 1.097362] usb 1-5: new high-speed USB device number 2 using xhci_hcd
[ 1.197314] usb 5-1: New USB device found, idVendor=046d, idProduct=c08e, bcdDevice=40.00
[ 1.197320] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.197323] usb 5-1: Product: MX518 Gaming Mouse
[ 1.197325] usb 5-1: Manufacturer: Logitech
[ 1.197326] usb 5-1: SerialNumber: 097F386B3637
[ 1.287586] usb 6-2: new SuperSpeed USB device number 2 using xhci_hcd
[ 1.300692] usb 6-2: New USB device found, idVendor=0781, idProduct=5581, bcdDevice= 1.00
[ 1.300697] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.300699] usb 6-2: Product: SanDisk 3.2Gen1
[ 1.300700] usb 6-2: Manufacturer: USB
[ 1.300701] usb 6-2: SerialNumber: 04017829d637bebff9322dee2efbbd4ce89215b2411d8c185814db9659f60d7dbf4400000000000000000000bafb5db3ff9b0b1881558107882f67cc
[ 2.307661] usb-storage 6-2:1.0: USB Mass Storage device detected
[ 2.307743] scsi host8: usb-storage 6-2:1.0
[ 2.307800] usbcore: registered new interface driver usb-storage
[ 2.322309] usbcore: registered new interface driver uas
[ 2.341354] usbcore: registered new interface driver usbhid
[ 2.341357] usbhid: USB HID core driver
[ 2.345883] input: Logitech MX518 Gaming Mouse as /devices/pci0000:00/0000:00:08.1/0000:10:00.4/usb5/5-1/5-1:1.0/0003:046D:C08E.0001/input/input3
[ 2.345957] hid-generic 0003:046D:C08E.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech MX518 Gaming Mouse] on usb-0000:10:00.4-1/input0
[ 2.346049] input: Logitech MX518 Gaming Mouse Keyboard as /devices/pci0000:00/0000:00:08.1/0000:10:00.4/usb5/5-1/5-1:1.1/0003:046D:C08E.0002/input/input4
[ 2.397759] hid-generic 0003:046D:C08E.0002: input,hiddev0,hidraw1: USB HID v1.11 Keyboard [Logitech MX518 Gaming Mouse] on usb-0000:10:00.4-1/input1
[ 3.368128] scsi 8:0:0:0: Direct-Access USB SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
[ 11.815061] usb 1-5: device descriptor read/all, error -110
[ 11.931674] usb 2-5: new SuperSpeed USB device number 2 using xhci_hcd
[ 11.947341] usb 2-5: New USB device found, idVendor=174c, idProduct=3074, bcdDevice= 0.01
[ 11.947346] usb 2-5: New USB device strings: Mfr=2, Product=3, SerialNumber=0
[ 11.947348] usb 2-5: Product: ASM107x
[ 11.947349] usb 2-5: Manufacturer: Asmedia
[ 11.953529] hub 2-5:1.0: USB hub found
[ 12.121575] usb 1-5: new high-speed USB device number 3 using xhci_hcd
[ 23.078760] usb 1-5: device descriptor read/all, error -110
[ 23.081010] usb usb1-port5: attempt power cycle
[ 23.522567] usb 1-5: new high-speed USB device number 4 using xhci_hcd
[ 33.830962] usb 1-5: device descriptor read/all, error -110
[ 34.210565] usb 1-5: new high-speed USB device number 5 using xhci_hcd
[ 44.583242] usb 1-5: device descriptor read/all, error -110
[ 44.585490] usb usb1-port5: unable to enumerate USB device
[ 44.761568] usb 1-6: new high-speed USB device number 6 using xhci_hcd
[ 46.643975] usb 1-6: New USB device found, idVendor=0db0, idProduct=422d, bcdDevice= 0.01
[ 46.643981] usb 1-6: New USB device strings: Mfr=3, Product=1, SerialNumber=0
[ 46.643982] usb 1-6: Product: USB Audio
[ 46.643984] usb 1-6: Manufacturer: Generic
[ 46.702533] hid-generic 0003:0DB0:422D.0003: hiddev1,hidraw2: USB HID v1.11 Device [Generic USB Audio] on usb-0000:0e:00.0-6/input7
[ 46.878581] usb 1-7: new high-speed USB device number 7 using xhci_hcd
[ 47.099974] usb 1-7: New USB device found, idVendor=0e8d, idProduct=0616, bcdDevice= 1.00
[ 47.099979] usb 1-7: New USB device strings: Mfr=5, Product=6, SerialNumber=7
[ 47.099981] usb 1-7: Product: Wireless_Device
[ 47.099982] usb 1-7: Manufacturer: MediaTek Inc.
[ 47.099983] usb 1-7: SerialNumber: 000000000
[ 47.317571] usb 1-8: new full-speed USB device number 8 using xhci_hcd
[ 47.738965] usb 1-8: New USB device found, idVendor=045e, idProduct=0768, bcdDevice= 1.50
[ 47.738971] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 47.738973] usb 1-8: Product: Microsoft® SiderWinderTM X4 Keyboard
[ 47.738975] usb 1-8: Manufacturer: Microsoft
[ 47.772897] input: Microsoft Microsoft® SiderWinderTM X4 Keyboard as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-8/1-8:1.0/0003:045E:0768.0004/input/input7
[ 47.824715] hid-generic 0003:045E:0768.0004: input,hidraw3: USB HID v1.11 Keyboard [Microsoft Microsoft® SiderWinderTM X4 Keyboard] on usb-0000:0e:00.0-8/input0
[ 47.876971] input: Microsoft Microsoft® SiderWinderTM X4 Keyboard Consumer Control as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-8/1-8:1.1/0003:045E:0768.0005/input/input8
[ 47.928699] input: Microsoft Microsoft® SiderWinderTM X4 Keyboard as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-8/1-8:1.1/0003:045E:0768.0005/input/input9
[ 47.928805] hid-generic 0003:045E:0768.0005: input,hidraw4: USB HID v1.11 Keyboard [Microsoft Microsoft® SiderWinderTM X4 Keyboard] on usb-0000:0e:00.0-8/input1
[ 48.104570] usb 1-9: new full-speed USB device number 9 using xhci_hcd
[ 48.746507] usb 1-9: New USB device found, idVendor=1038, idProduct=12aa, bcdDevice= 0.07
[ 48.746514] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 48.746517] usb 1-9: Product: SteelSeries Arctis 5
[ 48.746519] usb 1-9: Manufacturer: SteelSeries
[ 48.746520] usb 1-9: SerialNumber: 00000000
[ 48.874929] input: SteelSeries SteelSeries Arctis 5 as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-9/1-9:1.5/0003:1038:12AA.0006/input/input10
[ 48.926709] hid-generic 0003:1038:12AA.0006: input,hidraw5: USB HID v1.11 Device [SteelSeries SteelSeries Arctis 5] on usb-0000:0e:00.0-9/input5
[ 49.102564] usb 1-10: new full-speed USB device number 10 using xhci_hcd
[ 49.391798] usb 1-10: New USB device found, idVendor=1462, idProduct=7d75, bcdDevice= 0.01
[ 49.391803] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 49.391804] usb 1-10: Product: MYSTIC LIGHT
[ 49.391806] usb 1-10: Manufacturer: MSI
[ 49.391807] usb 1-10: SerialNumber: 7D7522120106
[ 49.418945] input: MSI MYSTIC LIGHT as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-10/1-10:1.0/0003:1462:7D75.0007/input/input11
[ 49.419076] hid-generic 0003:1462:7D75.0007: input,hiddev2,hidraw6: USB HID v1.10 Device [MSI MYSTIC LIGHT ] on usb-0000:0e:00.0-10/input0
[ 49.594565] usb 1-12: new high-speed USB device number 11 using xhci_hcd
[ 49.806992] usb 1-12: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=60.90
[ 49.806999] usb 1-12: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 49.807001] usb 1-12: Product: USB2.0 Hub
[ 49.819009] hub 1-12:1.0: USB hub found
[ 55.205108] usbcore: registered new interface driver btusb
[ 62.200571] usb 1-9: Warning! Unlikely big volume range (=4096), cval->res is probably wrong.
[ 62.200577] usb 1-9: [11] FU [Sidetone Playback Volume] ch = 1, val = 0/4096/1
[ 62.337064] usbcore: registered new interface driver snd-usb-audio

Key Points from the Output

- Device Detection: Various devices, including a gaming mouse and an SSD, are being successfully recognized, as evidenced by the lines that mention "New USB device found..." with details like manufacturer and product.
- Error Messages: The lines with error -110, such as usb 1-5: device descriptor read/all, error -110, indicate issues. Error -110 in Linux USB often signifies a timeout, meaning the device did not respond in time or there was a communication delay. This can be caused by various factors including poor USB connection, power issues, or a hardware fault.
- Attempt Power Cycle: There's an attempt to power cycle the port (usb usb1-port5: attempt power cycle), which is a method used to reset the port and attempt re-initialization.
- Enumeration Issues: The message usb usb1-port5: unable to enumerate USB device suggests that after repeated attempts, the system was unable to properly communicate with the device or fully initialize it.

At this point my very uneducated guess is that I either have a power supply problem or that my MOBO isn't quite right, but as before I'm not quite sure of how to test this except trying with another PSU however I only have another one with equal power.
Also another thing that stands out to me is that from the moment I press power on it takes about a minute before anything even happens on screen, I don't know if that's relevant but that feels like it's too long. My internal drive is boot prio 1.

BSOD collection from the new OS installation - https://drive.internxt.com/sh/file/...05fe36a6223a7823567b204e2e4500f7a6233fc8d9c99

 

[ubuysa]

You have to use WinDbg to properly analyse dumps, but it takes years of experience and a lot of background knowledge to be able to analyse dumps properly.

That's new information there, if you'd led with that we could have saved some time. A bad PSU could be the issue, but so could a bad motherboard, or even something as simple as bad chipset drivers. I would first ensure that all drivers, especially chipset drivers, are up to date. Then I'd look to see whether there is a BIOS update available.


FWIW that recent dump also points at a storage drive. The Windows ntfs.sys driver was called repeatedly in the lead-up to the bugcheck. Though if that's the Kingston drive and you know you have USB issues then that would be a symptom rather than a cause.

 

[bkdoorbandit]

You have to use WinDbg to properly analyse dumps, but it takes years of experience and a lot of background knowledge to be able to analyse dumps properly.

That's new information there, if you'd led with that we could have saved some time. A bad PSU could be the issue, but so could a bad motherboard, or even something as simple as bad chipset drivers. I would first ensure that all drivers, especially chipset drivers, are up to date. Then I'd look to see whether there is a BIOS update available.


FWIW that recent dump also points at a storage drive. The Windows ntfs.sys driver was called repeatedly in the lead-up to the bugcheck. Though if that's the Kingston drive and you know you have USB issues then that would be a symptom rather than a cause.

Yes, the USB information is new to me too.
I went to the store where I bought my parts and they've offered to take my mobo+ram+cpu+storage and do their own checks for free so that's very kind of them. I've been problem free for 5 days now though so I'm super confused.

I want to thank you for taking your time helping me, very much appreciated.

 

[ubuysa]

If they're offering to check the hardware for free then I would take that offer. Put the dumps on a USB stick for them too. I doubt that they have anyone who knows how to read and analyse them - but you never know.