Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Serius software? problem with Devialet D200
#1
I just changed my laptop which I use for the Devialet D200 and I am having serious trouble.

I keep having blue screen in Windows when I activate Devialet Air. Reason of failure is AirAudioDriver.sys
I unistall and reinstall the drivers, software without any luck.

Any suggestions?

[Image: 20190810.jpg]
Reply
#2
All started after the latest window upgrade...
Reply
#3
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
Reply
#4
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
Reply
#5
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
Reply
#6
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.
Reply
#7
I will check it out this weekend. I might unistall the update. It is really unusable!
Reply
#8
Hi again,

After a while of not getting any blue screens, I got one yesterday again. I found out that I can cause it by first selecting AIR as the Windows sound output when the Devialet is not powered on, and then having the computer (trying to) output sound. So in this case the blue screen doesn't happen before there is sound playing.

Of course this doesn't mean that other things don't also trigger the blue screen, but it seems that I can now avoid at least some of them Smile

EDIT: Apparently the sound playing isn't the triggering thing after all. If I have AIR as the Windows sound output while the Devialet is powered off, just opening Tidal will cause the blue screen.
Reply
#9
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.
Reply
#10
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)
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)