Posts: 33
Threads: 7
Joined: Nov 2017
Reputation:
0
All started after the latest window upgrade...
Posts: 698
Threads: 14
Joined: Sep 2014
Reputation:
57
Did you do a search on this forum? I'm not a windows user but I recall a discussion about software and OS updates causing some difficulties. It may or may not be current with your situation. My memory is that both window and Mac OS had a few incompatibility issues with AIR.
Damon
Powernode, NAD M32, Cambridge CD transport, Analysis Plus, Nordost, iFi Nova, CSS Criton 1TDX, KEF C62
Vancouver, Canada
Posts: 1,999
Threads: 23
Joined: May 2014
Reputation:
44
This indeed happened in the past as well with new versions of Windows/MacOS. Back then Devialet had to issue driver/software updates to support the new versions.
I myself no longer use Air so can’t confirm if the issue is a general one that would apply to anyone running Air on this latest version of Windows. Perhaps others can chime in here but I think it’s best to contact Devialet support as well, perhaps it’s already a known issue they’re working on. It’s probably not something you’d want to do but it is possible to roll back to the previous version of Windows.
PS Audio P3, Shunyata ΞTRON Alpha Digital and HC/Furutech power cables, Paul Hynes SR7EHD-MR4, DIY Roon Server & Roon Endpoint running AudioLinux Headless, Phasure Lush^2 USB cable, Audioquest Diamond RJ/E ethernet, Uptone Audio etherREGEN, Mutec MC-3+ USB, Shunyata ΞTRON Anaconda Digital XLR AES/EBU, Devialet Expert 250 Pro CI, Nordost Tyr Reference LS cables, Von Schweikert VR-5 SE Anniversary Edition, Anti-Mode Dual Core 2.0, JL Audio Fathom F112. More detail here.
The Netherlands
Posts: 45
Threads: 7
Joined: Jun 2014
Reputation:
2
Hi...
I have had exactly the same problem. From looking at dates on dumps etc I think my problem started after
'KB4506991 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10, version 1903' which was auto installed on my Dell XPS 13 on 13th July. On 20th July I started getting the same error as you using Qobuz. As soon as Qobuz loaded I would get the blue screen. I deleted the Air driver and reinstalled and it was OK for a few days and then went again. Since then I have not bothered, using IPAD and AirPlay even though sound quality is not great. I might try again as there have been a couple of cumulative updates since which may have fixed the problem?. Would be useful to know if you are using Qobuz as I guess that may be a contributing factor.
Chord Blu > D200 > Martin Logan Ethos : Saddleworth, England
Posts: 44
Threads: 4
Joined: Jun 2015
Reputation:
0
Hi,
I also got lots of similar blue screens about a week ago after a Windows update, but since then less frequently and for the last few days none at all.
At the beginning even trying to uninstall AIR caused the blue screen to happen. But just today I managed to both uninstall and reinstall AIR successfully so I hope it stays this way.
Posts: 33
Threads: 7
Joined: Nov 2017
Reputation:
0
I will check it out this weekend. I might unistall the update. It is really unusable!
Posts: 33
Threads: 7
Joined: Nov 2017
Reputation:
0
13-Sep-2019, 16:20
(This post was last modified: 13-Sep-2019, 16:29 by Drioannis.)
Yes the problem is with the Air. I already sent an email to Devialet and I suggest you do the same. This makes Air totally useless.
Posts: 445
Threads: 7
Joined: Jul 2015
Reputation:
4
Hmmm... we all know how long it will take them to fix a buggy AIR version.
Which version are you guys using? I used to have a lot of blue screens of death in the past.
My Windows is up to date and I'm having no problems with the older AIR 3.0.1 public beta (which I'm using because I prefer the sound quality of this version).
Devialet Expert 200 (FW 7.1.3) / Magnepan 1.7i / Rel T5 / Foobar (WASAPI event 24bit) / AIR 3.0.1 public beta (best Air 3.x.x SQ by far)