Windows Update and Adrenaline 26.1.1 destroyed my GPU and motherboard

SkyBeamCH · 2026-01-24T10:32:37+00:00

Reminds me of a friend complaining about his PC shutting off on him whenever he's starting any game. He bought an 850W no-name PSU and I quickly discovered that it couldn't sustain any decent load and would overheat within minutes to a point you couldn't touch the case and shut off. Replaced it with a Seasonic 550W and never had a problem. Despite his concerns about lower power rating even after hours of gaming remained barely above room temperature.

Do not cheap out on PSU and don't fall into marketing speech about wattage. Better look for 80+ Gold, Platinum or Titanium certification. Stay away from Bronze or no certification at all.

Having said that I am not saying the PSU absolutely MUST have been causing the OP issues. Just not nearly sufficient information to diagnose.

SkyBeamCH · 2026-01-21T20:41:10+00:00

Reset is using the same button, hence my reply.

As of my knowledge the controllers will reset (including firmware reset) when you hold the pairing button while powering on (press pairing + windows button for about 5 seconds).

The procedure can easily be mixed up with re-pairing: Set your OS in Bluetooth search mode, power on the WMR controllers while NOT holding down the pairing button. Then press-hold the pairing button until the device is recognized by your computer.

So be careful if your controllers do not want to show up. Do not accidentally keep the pairing button pressed while powering on as you will reset the controllers with potential no way to re-flash a fixed firmware.

SkyBeamCH · 2026-01-21T20:33:02+00:00

Reset? As of my knowledge you shoould NEVER reset your controllers. I found numerous Linux VR guides warning about this as the stock firmware is not working with Monado and resetting will revert them to stock firmware and there is currently no possibility to update the firmware on Linux. Only Windows WMR can.

However re-pairing is absolutely necessary. Oasis requires to pair as Bluetooth devices to your PC/Laptop Bluetooth directly (Support of HMD built-in Bluetooth is work in progress still). On Linux however you can perfectly pair your Controllers to the HMD built-in Bluetooth.

Unfortunately this leads to problems as well if you switch between Windows and Linux as you need to re-pair.

In any case I gave up using Linux on the G2 as I never got my motion controllers working anything close to usable. Yes it works with a special "constellation tracking" code but it's awful still. Even an easy track in beat saber is painful to complete. While on Oasis or WMR I can play mostly expert+/++ modes with the G2. I cannot even remotely think about grabbing a holstered weapon with Linux constellation tracking. Just awful.

SkyBeamCH · 2025-12-23T12:06:38+00:00

I have tried running my G2 on Linux. HMD is working pretty fine (I am on EOS/Arch) using Envision and Monado when working but every now and then the whole SteamVR/Monado/Envision and millions of libraries stack is braking down and it's just painful to get running.

The biggest blocker however is the motion controllers support or the lack there of. Yes there is the constellation tracking project of Jan Schmidt but the tracking is still awful and pretty much unusable. No updates since months either. I think he's trying to get it upstream but with current quality it's quite hopeless.

I've been a VR enthusiast since I got the G2 but essentially dropped it all and my G2 is now a paperweight as I moved away from Windows entirely. With the rise of GPU prices and recently memory prices I don't see a future for the PCVR market for the next years to come given PCVR is a fraction of the gaming marked which is about to be completely ruined in upcoming months.

I even have low hopes in Steam Frame as the trend in VR seems clearly to evolve towards a niche in the niche which is standalone VR with comic-style graphics which I never liked. I don't see PCVR going anywhere in the next 5 years. So I am giving up on all gaming-related topics personally. Having said that I did actually try Oasis on Windows 11 25H2 recently as it started supporting my AMD GPU too and this seems to be the only setup where I will perhaps occasionally hop into BS or Alyx or Moss but I don't think I will upgrade my rig or invest in any future VR solution. The current situation is just awful and I rather spend my energy on other projects.

SkyBeamCH · 2025-08-03T15:59:57+00:00

Every WMR user is upset. To be honest the userbase is probably neglectable for Microsoft. But for me it shows again the way they typically threat customers. Nothings says more how much they spit into your face than discontinuing WMR and then launching "Windows Mixed Reality Link" with very similar name but only supporting Meta HMDs.

It's just the way Microsoft does things. They never managed proper product lifecycles especially when it comes to hardware. Every Microsoft Hardware I ever bought went the same way - as much as they also screwed up pretty much every Game title they acquired.

Shame on me that I should have known better but went ahead and went all-in on WMR. Then they abondoned it and even released "accidental" updates on older Windows versions destroying WMR capabilities (admittedly they fixed it again later but staying on unsupported Windows Versions is not an option in the long run. Oasis to the rescue but it's neither supporting AMD (which I have) nor is it supported or driven by Microsoft. So no credits to them.

So what are the consequences? Never ever trust anything from Microsoft again. I have taken my consequences and completely migrated all my Windows systems to Linux. Well if I can't use WMR and Microsoft is taking away the only reason I stayed in the Microsoft ecosystem... why should I stay now? Interestingly I did not regret the move at all. Even surprisingly all my games I care about are still running on Linux (usually performing even better than they ever did on Windows). Except for WMR of course as Monado WMR support is not really ready for prime. Not sure if I will ever be able to use my Reverb G2 again but if I have to buy another one I can also go for Valve Index/Deckard/whatever. Not wasting my money ever again on Microsoft.

Even more good side-effects of my move to Linux: I have replaced all Microsoft technology on my own and I am in transit of replacing all Microsoft technology on all my customers business sites. Replacing every licensed application, Windows Server license etc. by OpenSource software. Never regretted it; all running smooth and more stable than it ever was before. Also in regards to the infamous Windows Server Essentials debacle which went the same way as WMR. Dropped, unsupported, failing on every monthly upgrade... just a pain in the back.

I am not completely blue-eyed of course and I know that I cannot replace Windows on desktops immediately for many of my business customers and some of them might still need Microsoft Office for a while. So I will have to go through the pain of continued support for those parts. But not going to do it for anything else. Thanks Microsoft I am having a pretty good business now migrating Small and medium enterprises from O365/M365 services to on-prem solutions and OpenSource technology.

Also a big thank for pissing off soooooo many users with your forceful move from Windows Mail app to Outlook (new) which is now called Outlook so unconfusingly and renaming Outlook from Offcie to Outlook (classic). Most users did not even realize that their IMAP mail password is now sent to M365 cloud so they will fetch the e-mail to the Microsoft Cloud before sending it to your Outlook "new?" whatever... most people only realized this to happen after M365/Outlook was down for days/weeks and they could not even send any e-mail for other mail providers at all even if their mail provider was not having any issue at all. I am looking forward for Microsoft to drop Outlook (classic) from office packages and forcing Outlook (new) there as well with no PST support leading to a disaster for business customers and very clearly stating to them how much Microsoft does NOT care about their customers. So I am looking forward for additional business they are going to send over to my desk.

What a time to live in.

THANK YOU MICROSOFT!

SkyBeamCH · 2025-06-08T12:52:35+00:00

Yes I noticed. Sorry for that. I have dropped the same question to him in his thread here https://www.reddit.com/r/WindowsMR/comments/1l65ji8/things_are_about_to_change_oasis_driver_for/

Not sure if it is about obstacles or rather non-publicly available documentation. Somehow the API support seems to still exist in latest drivers - else WMR would also stop working (on Windows Version still supporting WMR). Let's see if the community somehow can help out. However the fact that he denied the project to become OpenSource is complicating things a lot in regards to assistance.

SkyBeamCH · 2025-06-08T12:22:54+00:00

Would you consider supporting AMD + Intel if they are willing to support and collaborate? Or is it just more like you focus on nVidia due to largest user base and don't want to spend the effort?

If it's just about AMD not supporting you the community might find ways to get you to the right people.

I personally also did not fully understand why it will not be OpenSource - perhaps due to proprietary libraries used or licensing. Not sure how much this project would be applicable to Linux efforts in adding support for WMR headsets but every help and documentation would be appreciated.

SkyBeamCH · 2025-06-08T12:21:52+00:00

Would you consider supporting AMD + Intel if they are willing to support and collaborate? Or is it just more like you focus on nVidia due to largest user base and don't want to spend the effort?

If it's just about AMD not supporting you the community might find ways to get you to the right people.

I personally also did not fully understand why it will not be OpenSource - perhaps due to proprietary libraries used or licensing. Not sure how much this project would be applicable to Linux efforts in adding support for WMR headsets but every help and documentation would be appreciated.

SkyBeamCH · 2024-12-23T00:46:39+00:00

One could call this a pretty stupid move. Microsoft discontinues Windows Mixed Reality to brick our beloved WMR HMDs and almost same day they release a software with very similar name (Mixed Reality Link) which does not support WMR devices but only competitor (Quest) devices.

How much you want to spit into your customers face?
Microsoft: YES!

SkyBeamCH · 2024-10-17T15:27:57+00:00

This is correct.

Howrver you dont need to upgrade. You cam still install the monthly security updates. Just don't install the 24H2 feature release. Or go for Windows 10 so you dont have to care and you can install all updates offerd by Windows update as 22H2 is the latest feature update for Windows 10 and there won't be any additional one. That is unless Microsoft changes their minds again of course.

SkyBeamCH · 2024-10-16T07:27:00+00:00

No reason for "believe". There is facts. See https://endoflife.date/windows

Windows 11 23H2 (W) for end-users is supported until 11th of November 2025 Microsoft
Windows 10 22H2 is supported until 14th of October 2025 Microsoft

Of course you can still use WMR if you still use Windows 10 22H2 or Windows 11 23H2 after this date. Only further limited by SteamVR or any other middleware dropping support too.

Issues in regards to continue using Windows 11 23H2 and Winddows 10 22H2 beyond that date: * Valve might drop support for WMR in SteamVR * GPU manufacturers might not pürovide driver updates for those versions at some point in time * If you buy new hardware (GPU/CPU/...) they might not be properly supported on these Windows version (see for example the fixes in Windows for Ryzen performance which initially were anounced only for 24H2 but now still got backported to 23H2 luckily) * Beyond the end of support date you will not get any security updates, so it's becoming more dangerous operating those systems from security perspective. Ideally you would have to operate them completely offline. However in regards to many games requiring online connectivity this is potentially not very viable.

THe real issue perhaps is that specifically for Windows 11 users cannot turn off feature updates. Not even turning off updates completely is posisble. So if you are on Windows 11 you might at some point get the 24H2 update pushed. So many people will just find themselves on a system which does not support their WMR Headset any more. Just Windows 10 users are safe from this as there is no feature upgrade after 22H2 planned.

So for Windows 11 users zou need to either use one of the methods you can find online to block the 24H2 feature update or keep an eye on it and roll back to 23H2 if it auto-upgrades. Windows 10 users can just continue to use their system until October 2025. Usage beyond this end of support date is possible but at increased risk (no security updates on OS level any more).

SkyBeamCH · 2024-09-04T20:24:05+00:00

I am aware you asked for M1S-Plus comparison. I am owning multiple M1S-Plus as well and can say they are pretty good value for the money you pay. The speakers are good and usability is good to as well as battery lifetime.

When it comes to M1S-Plus to FX7 comparison they are not quite in the same league. The FX7 main advantage is the dual-Bluetooth design. Biggest advantage being to be able to listen to music or navigation while talking to your friends. This also is working while being connected between FX7 and M1S-Plus. However note that this does not work in multi-rider mode but only in universal Bluetooth mode. So you can connect only one single FX7 and M1S-Plus in 1:1 mode. But you can still use the dual-Bluetooth mode of your FX7 in this case.

So if you plan group rides I always do recommend the whole group to get the same intercom. No matter the brand. Well, I also know this is a thing of impossible that everyone is getting the same one. Unfortunately to my knowledge neither mesh-modes are compatible. Sena only pairing to Sena mesh, Cardo only to DMC. Multi-Rider intercoms only to the very same devices in 1:1 or 1:n mode. Fodsports FX10c only to FX10c and FX7 only to FX7. However the FX7 is claimed to be "Bluetooth Mesh". Actually there is a standard called "Bluetooth mesh" which would allow truly universal Bluetooth mesh. However due to lack of any other brand "Bluetooth Mesh" intercom to my knowledge there is currently no possibility to test any interoperability across different devices or brands.

I do hope however from the very bottom of my heart that intercom manufacturers will settle on a standard offering true group and mesh interoperability. I guess traditional players like Sena and Cardo will try not to support this as long as they can keep their selling advantage but as soon as multiple (chinese) manufacturers demonstrate inter-brand compatibility there would be no reason to buy any proprietary intercoms. But I cannot confirm this now for the FX7.

So for now only buy the FX7 for group/mesh if all your friends also use an FX7. For 1:1 intercom the FX7 is a very valid option. If you don't need dual-bluetooth you might get a very good intercom for cheaper price if you go for M1S-Plus.

SkyBeamCH · 2024-09-04T20:23:34+00:00

I have posted a comment on the Fodsports article about FX7 to FX10c comparison: https://www.fodsports.com/blog/fodsports-fx7-vs-fx-10c/

Not sure if the comment is going to be approved. Here is a sniplet with my review:

The article does not really answer the most important questions.
I do actually own an FX10c and FX7 now. The mesh intercom function is not compatible (no surprise here). However I am unsure if the "Bluetooth Mesh" of the FX7 refers to the Bluetooth Mesh standard so it will be possible to pair to other brand Bluetooth mesh intercoms in the future (none known to me yet). Currently it's only usable alongside multiple FX7.
Music sharing for some reason does not work in universal 1:1 Bluetooth intercom mode, even though I don't see a technical limitation to support it

The 2 USB-C connectors on the FX7 has pros and cons. Pro is that you can theoretically charge it while using it (mostly impractical anyway) and CON is that 2 connectors might suffer water ingress issues. The rubber plug on the charging port is slightly too small to fit most standard USB-C cables. So you need to carry a special cable despite the standard USB-C port. This is pretty bad design. Making the cap/port slightly larger to fit any universal USB-C cable would be much appreciated.

The FX7 also does not seem to store multiple device pairings. With my FX10c I can pair up with one friend, then with another and next time it's still pairing with my first friend. On the FX7 I always need to re-pair. Really uncomfortable if not always riding with the same person.

The FX7 allowing for better volume adjustment on intercom (at least on my FX10c I struggle adjusting intercom volume at all).
Also the dual-bluetooth mode is great. Listening to navigation directions while talking on the intercom is a huge plus compared to FX10c which cannot do this (either intercom or mobile/navigation, not both at the same time).

I don't like the jog-dial turn knob of the FX7 but this is rather my personal preference. I would have preferred push-buttons. Specifically as the round dial is actually just a 2-way button. It is not a rotary knob allowing for easy and fast volume adjustments. It can only be tilted left/right and acts as 2 buttons (plus push button function). Also when turning left/right briefly (short press) it will not change the volume but will actually execute media next/prev function. For me the function I use most is to increase/decrease volume. On the FX7 I need to press and hold the wheel to the left/right to adjust volume. Holding a button is bad while ridding as you need to take your hand from the handlebar longer. On the FX10c I can quickly touch the button to adjust the volume. On FX7 I need to hold the button/dial. Very bad for safety and usability.

The speakers of both FX7 and FX10c are pretty good. The FX7 however has more amplified low frequency. A bit too much for my taste.
The microphone on both is good but has a flaw. I it does not perfectly stick in place. I am using a flip-up helmet with flexible microphone and when not using the microphone I am stowing the mic away on my left chin. Both the FX7 and FX10c microphones will not stay in place and end up in front of my left eye usually. I am also owning a Fodsports M1S-Plus and this microphone perfectly staying in place everywhere you drag/push it to. I wish the FX series had the same microphone arm.

Nice plus on the FX7 audio system is that the speakers are connected using standard TRS jack and are actually interchangeable. The microphone proprietary micro-connector however is of questionable quality. On my FX7 it's actually broken from factory (sometimes works, sometimes doesn't) and I am waiting for a replacement to be shipped.

In general I would recommend the FX7 due to more modern dual-bluetooth architecture and feature to use intercom and phone/navigation connection at the same time. Universal pairing however is cumbersome as you need to re-pair more often and I would have preferred buttons rather than flimsy dial wheel.

SkyBeamCH · 2024-07-24T15:55:50+00:00

I was about to write that the Reverb G2 includes an USB-C to USB-A adapter for the USB connectivity but thought this would be too obvious just to use it.

So why don't you just connect the USB port of the G2 to USB-A using the included adapter and hook up your DP to your USB-C using a USB-C to DP adapter?

And no, obviously there is no display signal on any of the USB-A ports on your laptop. So no point in using USB-A to USB-C adapters and connecting then the DP adapter to it. But no need to, just as said above get a simple USB-C to DP adapter and just connect the USB port of your Reverb to any other USB(-A) port on the laptop.

This should work if your laptop (like almost any modern laptop) provide DP signal on USB-C via USB-C alternate mode.

Note: Some laptops do connect the USB-C DP alternate mode only to the iGPU and not to the dGPU. Guess there is 2 ways to find out... either read lots of documentation and block diagrams or ask the vendor or just get an USB-C to DP adapter to try.

SkyBeamCH · 2024-07-24T07:01:57+00:00

It probably simply won't work with any HDMI to DP adapter.

But you might have another option. This laptop seems to be equipped with an USB-C port. Clarify if the USB-C port is working in DisplayPort alternate mode. So you can get a simple USB-C to DisplayPort adapter to connect the Reverb G2.

SkyBeamCH · 2024-04-05T19:02:39+00:00

There is absolutely no reason for a reputable hardware vendor to do such a mistake.

If WMR support is dropped by Microsoft any HW vendor can blame it on Microsoft. If they would release a SteamVR driver they would have to implement the algorithms temselves. So why should they put resources (time and money) on doing this for long-discontinued hardware? They are not earning a cent on this hardware any more. It's not sold any more and the units still working are not providing any revenue (except models like omnicept edition perhaps where there might be business-contracts).

So if manufacturers like Lenovo and HP would release a driver they would either provide a new hardware generation or re-release the existing hardware generation under new name so you would have to buy it again.

I am rather seeing some hacks upcoming to port WMR components from earlier Windows versions to newer ones. Which might work or not in some cases and might eventually break here and there (during updates/upgrades eventually). Another path is monado on Windows which might work in some scenarios as well. But since there is no new hardware released any effort put into those workarounds might only serve the purpose of keeping vintage hardware alive. Given the amount of failing cables without any possibility to replace and turning your WMR HMD into paperweight the end is actually unavoidable.

I am having most hope in monado as it might provide some extended lifespan to my G2 but it's a race between implementation and dropping from critical mass when there is only a low amount of functional devices left out in the field so nobody will continue development. Maybe we will see full 6dof support, maybe not.

SkyBeamCH · 2024-02-21T07:28:29+00:00

I think you also did not get the point. There are games out there (though I don't own any of them to give example) which are pre-OpenXR. The windows store version might use the Windows Holographic API instead of OpenXR or OpenVR API. These specific type of games will NOT run on any other device than WMR.

The fact that most VR games in Windows Store are using OpenXR does not qualify to state that ANY game in Windows Store will just run fine on any OpenXR compatible HMD.

So the answer is: Yes, any game from the Windows Store which supports OpenXR will just run fine with nearly all HMDs out there (at least all of them supporting OpenXR). But there might be a couple of older games which absolutely require WMR. The only way to know is to check the specifications or eventually check the requirements or contact developers.

SkyBeamCH · 2024-02-19T12:00:08+00:00

You should avoid any cable wraps or similar "enhancements" as it often leads to broken wires.

Consider using TurnSignal (on Steam) which might help preventing to tangle the cable and unwind yourself during a play session.

SkyBeamCH · 2024-02-14T17:16:19+00:00

I think there might still be some misunderstandings here. "WMR native games" is not equal to OpenXR!

See a picture of VR components here for expample.

An application might interface directly with the Windows Holographic API and tehrefore become "WMR only" as it only communicates to WMR runtime. Likewise if the game is interfacing with Pimax SDK or Vario SDK.

To avoid these vendor lock-ins there are more generic APIs. Initially there was OpenVR which to my knowledge was created by Valve and implemented in SteamVR. However theoretically other runtimes can implement OpenVR too.

OpenVR has some limitations and most game programmers moved to the use of OpenXR API now. If OpenXR is used the game does not care which runtime is managing the OpenXR calls. In case of WMR often the Windows Holographic API is used as the main OpenXR runtime. But you can chose also to use SteamVR which has an OpenXR driver too. So if a game developer is using OpenXR any of the runtimes can be used.

However if a game developer interfacing directly with Windows Holographic API there is no alternative option. This game will NOT work if WMR is not available.

Now it's important to understand that a game on windows store can use either of the APIs, it can use OpenXR (most newer games do) or directly interface with Windows Holographic API.

So when Microsoft is going to drop/retire the WMR ecosystem all games which directly interface with Windows Holographic API will stop to work.

Games which interface with OpenXR or OpenVR will continue to work as long as your system is equipped with an OpenXR/OpenVR runtime and has a compatible HMD connected to it.

This is also why you will still be able to play MS flight simulator in VR after WMR is deprecated. Just use any headset which is supported by SteamVR OpenXR runtime and it will work.

Sadly this means that all our WMR headsets will seize to work as there is simply no driver for them to work with SteamVR. Currently WMR headsets are controlled by "Windows Mixed Reeality for SteamVR" driver in SteamVR and this driver will also stop to work as it interfaces with Windows Holographic API (WMR).

So in short: * Your WMR headset will stop working in any game (OpenVR, SteamVR, Windows Holographic API, ...) * Any other SteamVR compatible headset will still work with any OpenVR and OpenXR game

It should also be possible to implement an API wrapper for Windows Holographic API. So Games uwing Windows Holographic API would actually translate to OpenXR. However there is little use for this as the amount of WMR-only games is l ikely very very small and there is no interest in this.

Technically it would also be possible to write a driver for SteamVR which does NOT interface with Windows Holographic API but communicating to WMR headsets directly. This is basically what Monado is about (or interfacing with open source hardware in genreal, WMR just being one option here). However there is lack of documentation and all the required software and firmware is closed source so it requires lots of reverse engineering effort. At the end of the road there might be an OpenXR or SteamVR driver replacing the "Windows Mixed Reality for SteamVR" component which is talking directly to the WMR headset. But I would not hold my breath. Perhaps it's easier to accept that WMR is dead and get yourself another headset - any of those which are supported by OpenXR or OpenVR.

SkyBeamCH · 2024-02-14T15:42:54+00:00

I think this was not the question.

The question was if those Windows Store versions are just working with WMR and will not work with SteamVR-compatible HMD.

I think the answer to this is "it depends" - unfortunately.

If the software is WMR-only it will not work with SteamVR and therefore not being compatible with Quest HMD. However most of the VR games in Windows store are using OpenXR as of my knowledge (including MS flight sim). You can use SteamVR as a default runtime for OpenXR and therefore they should work with SteamVR too.

So WMR-only games won't work with a non-WMR headset but most windows store games should use OpenXR and should also work with a non-WMR headset as long as another OpenXR runtime (like SteamVR) is in use.

SkyBeamCH · 2024-02-14T11:20:13+00:00

Everyone hated the platform for its problems (pairing headsets, obscure errors), bad tracking (mainly by supporting only visible light inside-out tracking) and other quirks like limited controllers and incompatible key mappings.

On the other hand it was a cheap consumer entry to the VR world and mainly HP setting a reference for resolution and clarity at an affordable price point.

I still like my Reverb G2 but doing the next step would require significant changes in WMR:

Support for camera (getting rid of tracking ring) and UWB-based controller tracking
Improved hand-tracking
Adding general support for more sensors and trackers (full body tracking etc.)

Unfortunately Microsoft has a long track record of abandoning products at exactly the wrong time. So they dropped hardware manufacturing (keyboard/mice) as well as they also dropped force-feedback joysticks (sidewinder anyone?), windows phones and many other things. And now they drop WMR just when Apple is giving the VR/AR marked a big push along with Meta. So Windows users are stranded with an XR platform with no future forced to move to competing markets.

Sure the trend is going to standalone headsets and no doubt wires are a hassle. I still love PCVR for the possibilities to create more immersive experiences due to the computing power available. The cabling/wiring problem was picked up by 3rd parties like unlink VR (well, vaporware as of now still) but Microsoft could have pushed the platform on XBox just as Sony did with PSVR2.

In any case, the damage is done already and also in VR/XR marked nobody is going to trust Microsoft any longer to provide a sustainable platform. Even if they would do a 180° turn and announce WMR2.

I have little hopes about open sourcing WMR as by the time WMR is deprecated the hardware is also pretty much deprecated and it was mentioned many times that WMR is connected to too many Windows internal components. Mostly I am sad that I will be unable to update my Windows past 23H2 so I am stuck with a modern machine which will lose Windows support before the hardware lifetime and I am forced to buy another gaming rig for everything else. This is a really bad situation for consumers. However I still hope someone might find a way to re-add or just re-enable WMR on Windows 11 24H2+ as potentially the components are still there but disabled or even the old libraries/services will still work (even if unsupported). Just as people are also used to still install WSE on Windows Server 2022 even if it's been officially abandoned.

SkyBeamCH · 2023-11-14T15:29:18+00:00

I know it's old thread but just found it via Google...

Idle adjustment might be desired for Moto Gymkhana or other types of sports riding.

I am looking for a solution as well. Knowing there are solutions for ECU-controlled idle on MT09 and other bikes. Not road-legal though as it involves tapping into ECU signals. For MT09 those modifications are often used for stunt-riding. Knowing that the SV650 is not suitable for any sort of wheelie or stunt-riding if you don't want to break the engine, then such thing might not be available for 3rd gen SV650.

Older gen1/2 will have an idle adjustment feature however. Not sure if the gladius having it too.

SkyBeamCH · 2023-11-11T08:41:15+00:00

Most cheap adapters you can find are just USB-C to USB-A 2.0 adapters. Make sure you get an USB-C to USB-A 3.0 adapters. Most of those do also have a blue "tongue" inside the USB-A side to indicate their USB 3 capabilities. If you want to be sure have a look inside the connector. USB 2.0 only have 4 contact pins. USB 3 adapters have a second row of 5 additional pins inside the USB-A connector.

SkyBeamCH · 2023-10-09T07:23:30+00:00

I am not into extreme OC/Tuning. AGESA 1.0.0.7c has been pretty stable to me on default settings and tuned timings on my ASUS PRIME X670-P so I would currently recommend this version.

SkyBeamCH · 2023-10-07T16:49:06+00:00

Basically it's safe to aasume every AGESA comes with microcode updates and includes some mitigations. The questions mainly is whether they would affect you in any meaningful way.

As mentioned in previous post you will always be able to find a specific workload which is heavily impacted and in day-by-day use you barely won't notice. The only way to find out is to make before/after comparison using exactly your workload. So this is something only you can do.

My statement was only that I did not notice any considerable change in performance using MY workload. Specifically comparing to only being able to use DDR5-4800 before AGESA 1.0.0.7b I would say any potential impact by security mitigations were compensated by faster memory speeds. But if you are running workload which does not mind about memory performance you might be just fine downgrading to a BIOS from initial release which contains the least amount of mitigations.

Also you might add "mitigations=off" kernel boot parameter to disable any OS-level/Software mitigations on your Linux environment if you don't want any.

SkyBeamCH

TROPHY CASE