I have found a bug that only alder lake is dealing with. I have two pimax headsets. I have tried 2 kits of ram, 4 motherboards, 3 ssd boot drives, and much much more to diagnose this issue. it is an issue with pimax and alder lake intel cpus.
for some strange reason when a 5k super or a 8kx is turned on using alder lake cpus, the headset will try to connect to the cpu’s internal usb controller. this is the controller inside the actual cpu not a controller hub. this can even happen using a pcie usb card. when this happens the headset will cause some usb ports to disconnect and connect rapidly. this is confirmed for me after months of testing using a 12700kf and a 12600k on windows 11. this issue is so severe that it even destroys the ram timings and other functions in the cpu. I have proof that this happens using hwinfo64 you can see the ddr5 ram voltages freaking out and you will get random crashes of the pc as a result of this. this is only fixed after rebooting multiple times and completely disconnecting the headset from the pc. this has been the case on 3 different motherboards: z690 aorus pro and master and msi z690 unify x. this is not a motherboard specific issue or a headset one as it does not occur on amd builds.
this is a massive issue that I am unaware that pimax knows is happening. it may be related to windows usb configuring things completely wrong. pitool should be updated to work properly on windows 11. windows 11 is the future whether pimax thinks it is or not. these issues are completely gone on both of my amd pc builds.
I have spent like 3k trying to diagnose this on my own and it has come down to the headsets and alder lake.
Your finding is very interesting, thank you for sharing.
"windows 11 is the future whether pimax thinks it is or not. "
maybe… therefore OpenXR may allow to use it on ancient outdated platforms like Windows10, or even alien ones like any Linux distro, eg. Proton / Steam.
For me, your finding it is just another preventing reason not to use Win11.
Anyone requested you to role back? At least, not here, not from me.
The feedback about found bugs is important. So you helped me with an argument for my decision regarding hardware and OS.
It may sound awkward, but did you consider multi boot environment, until W11 issues have been solved? If W10 has same issues and others confirm, it may require a BIOS update.
Unfortunately I have a different platform, so I cannot even check. At least, AMD had a similar USB related hick up issue, seemed to be solved with a new AGESA firmware blob.
Our software developer appears to be aware of the Win11 compatibility.
I agree that Windows 11 is the future, and our team does as well.
To avoid any unpleasant experiences or regular usage, our IT specialist recommended reverting to Windows 10 before this issue could be resolved entirely.
Aside from that, could you please share the ticket # with me so that I may review it and discuss it with our developer?
hello quorra. okay so I returned my pimax 8kx the other day to newegg and purchased a second pimax 5k super. this headset is perfect. so I think the new 8kx i recieved was pretty bugged or broken… I will continue monitoring for any issues. my ticket number was 27657. I didn’t go crazy with them. I got 3 different firmwares, and different ones fixed different things. but that headset was really really bugged…
If you have any problems with the new 5K Super, please retrieve the log files from Pitool and forward them to me.
I’ll have our engineer go at the errors.
Does using the 5k super resolves this problem on Windows 11 ? Im also on alder lake with ddr 5 using windows 11, it would save me a lot of trouble to know this ?
i dont know if this has been fixed but i have a new usb pcie card and everything has been perfect since then. I could try it out again on normal usb ports.
I got a additional usb out on my nvidia card, which has a own controler as well as a deloc card(for additional sata) i think it has usb too.i will rather try it that way and hope i do not get this.
did you try different efi usb settings ?
both of you have asus boards… I tested this stuff on both gigabyte and msi boards and had the issue. issue may have been fixed by windows update by now but im afraid to even plug it into the mobo directly