I am operate on Win10 virtual machine and at time of switching between Host and VM some time buffer corrupted or in case network time out it can be happened. My suggestion is to change priority of the DAX task via command START /REALTIME DAX.EXE with admin privileges. of course you can create a BAT file and out into the Start Menu, BTW do not forget disable initial autostart of dax.exe
However DAX is stable on my Surface Pro 3 & 4. So it seems that Win10 has issues with certain hardware. Just my observation.
- different OS management: Power settings
- drivers update, BTW with drivers not everything are clear, even native drivers for HW are not always optimal
also useful links:
check your drivers - https://sdi-tool.org/
P.S. I have read many times issues related with ROG ASUS MB series
For instance, I listen to Disturbed in VLC and I hear a pop. Dang. But that's it. It popped and went away and all is back to normal.
Then I transmit a single tone with DAX and I see this:
That's not a pop. It doesn't clear up by itself and it probably sounds strange on the air. In fact, maybe it sounds like something from Disturbed. This is what happens to me every 24+ hours or so.
I restart DAX and get this:
Is this covered by whatever #2391 is about? As 2391 has been around at least six months and I believe the problem has been around longer is it just something that can't be fixed?
I guess there's lots of people very happy with the remote feature in the new software version. But for me, it is the same old software with pretty much all the same old issues. Almost exactly the same old issues.
Yes. Sustained, predictable, issues are not likely to be DPC related.
Some other driver issue? Certainly. Triggered as a result of a few really long instances of ISR to DPC Latency? Maybe. But not a DPC problem as we classically discuss them here on the forum.
(no point in paying for a software version I can't use with a DSL internet connection).
I had noticed that other stations that should have heard me loud and quickly (I run a big 8x7 6M array and high power) were not decoding me as often as they normally do. This morning while working WSJT MSK144 I turned on the RX audio so the TX audio monitor would work (I don't often listen to audio when I do digital) and heard the audio stream on the monitor sounded distorted similar to being over driven (ie too much audio gain). My CW ID sounded like it had an echo and it all ran together.
I checked the TX Stream level and it was at the normal setting, cut it back then restored it and it responded correctly on the P/CW window's level meter (I run it flat EQ, no compression in DIGU mode). I tested it with another station and he said it also sounded distorted and was not getting decodes commensurate with the strength and frequency of my signal bursts. Another station was SWL and said the same.
I have three computers running DAX (I often run WSJT or N1MM off different networked computers than the Flex - sometimes I run the Flex on the Maestro), all of them had the same MSK144 TX audio distortion in the monitor when they went to DAX TX. I then brought up N1MM and tested the voice keyer. It was horribly distorted in both the monitor and over the air on all three computers. So I tried rebooting the SmartSDR program. Same problem.
Since the three computers all have different instances of DAX and WSJT running (as well as use different com ports and slices to the DAX RX/TX), the only other thing in common was the radio itself, So I did not reboot DAX, but rather power cycled the radio with the front panel switch and reconnected. Bingo - all working normally again per the monitor. The other stations I was testing with got solid decodes again too and one said that the over the air audio from the N1MM voice keyer was normal. I never had to stop/restart DAX on any machine.
I was on N0UK Ping Jockey chat at the time and noted my experience with the DAX. I immediately got back 2 replies from other stations indicating similar problems with distorted DAX TX audio that had occurred for them. They both said they had solved the problem by closing and reinitiating DAX. One told me he had had the problem with previous versions of DAX and SmartSDR too. I see now that others in the community have had this problem and all seem to solve it by reinitiating DAX. My experience was different, I had 3 instances of DAX running and shutting down the radio then rebooting it solved the problem for all three.
Hope this helps you find and solve this long standing problem.
73 de Bob K2DRH
Picture of Distorted TX Signal:
Picture of normal TX Signal:
I have the Asus Z97A I7-4790 board that will not run DAX [receive] reliably on Win10; However, just fine on Win7 Pro. The transmit buffer does get corrupted if the radio runs for 24 hours or more.
My two Surface Pro tablets will run DAX [receive] just fine on Win10 Pro. Have not checked for the transmit buffer issue on the Surfaces.
So it seems the receive problem may be hardware related, at least in my case. Any chance you can try a different computer or go back to Win7?
This have been discussed many times before.
Yes I see that it has Bill TU.
I've also discussed it with other Flex owners outside these forums. Tried it on 3 computers with similar results all Win10. I do leave my radio and computers both on for extended periods to monitor 6M FT8 when I am not in the shack and now understand that not rebooting for days at a time probably contributes to the problem.
I found the best thing in my case was not to allow Dax or Cat to auto load that has stopped most of the issue. But on occasion Dax will get corrupt and i just close Dax and restart it and i am fixed.
This issues has went on for years look up Dax corruption.
I had an intense support session with Neil from FlexRadio support on this issue. We started with getting rid of DPC's (I had DPC's caused by the nvidia grafics drivers) but that did not help at all. I updated all the drivers and the BIOS - still the same. The PC is a fast ASUS ROG with 7th generation i7 and 32 GB of memory. Processing power is not an issue. I can DEFINITELY influence the occurrence (it happens between several times a day to once a week) by disconecting/connecting USB devices. I got rid of a creative USB sound blaster that I used to interface my IC-7800 with. Things improved, but DAX corruption is still there. I am still in the debugging process. It is very difficult to say if a measure helps or not because it may take a long time for the problem to show again.
I attached two pictures to show you what I see as RX DAX corruption: On the first picture FT8 waterfall traces become fuzzy and the spectrum looks like it went through a low pass filter. Nothing gets decoded in that state. The second pictures is a comparison between my FLEX-6700 and my IC-7800. on 20m FT8. You can see that the waterfall traces on the 6700 become fuzzy, while the IC-7800 is OK.
When I reset DAX (I use the batch file from Cédric, HB9HFN) all is fine, until corruption occurs again. If you have any hints on what else I could try (short of a complete Windows 10 clean install) please let us know! This issue has cost me countless hours.
Thank you very much and 73, Frédéric, HB9CQK
- 5300 Conversations
- 1623 Followers
- 3117 Conversations
- 639 Followers
- 3658 Conversations
- 949 Followers
- 3011 Conversations
- 863 Followers
- 987 Conversations
- 254 Followers