Blue Screen crash on SmartSDR v3.1.7

Bill / VA3QB

William Osborne

ctate243

Mike Webb KC0YHM

Konstantinos Vardakis

David

Dave - N6XVZ

Burt Fisher

Who releases software with the comment, "We are working to identify the cause and resolve the behavior?"
Boeing does with a lot worse results.

Pat N6PAT

As a systems designer and software developer for over 3 decades I have to say that I am very surprised that changes that cause the dreaded BSoD would be released without first identifying and correcting the cause of such a serious error.

If you don't know the cause of a problem then you don't know what other problems can manifest themselves due to the original problem.

I'm concerned that the complexity of SSDR is getting beyond the capabilities of FRS to properly debug. My case was a perfect example.

Clay N9IO

I've come to expect comments like this from you. That last paragraph was an insult my friend. Until time you're pitching with staff that work on this might be nice to refrain from such comments. Getting old.

Bill -VA3WTB

Two things
#1
Gerald said that in some cases a release could be released with a known problem depending on how critical the problem is. In this case while the BSoD seems critical, we can recover from it with a re boot and ussualy the problem does not happen again. So the problem is anoying but not critical. If we could not move on from it then it would be considered critical and the release would stop.
And, it is hit and miss. Most people have had no issues after installing the update, me for one. But some have had problems and soon the problem went away.

2nd
Because the Windows updates makes Dax stop working it was very important to release as soon as possible taking the huge strain off the Help Desk every time it happens.
Buy releasing this update it has made many people very happy.

Bill / VA3QB

Bill , while installing it on Harold's computer the BSOD was a little worry some as I was remote into his computer and he is 30 minute drive while the radio is an hour drive  away and he is in his late 70's.  

On an other note , I installed the update on two on my Windows 10 computers with no issues as well as on a friend of mines two computers whom I allow access to my radio due to HOA restrictions

73
Bill
VA3QB.

Burt Fisher

Clay did you know that the Boeing Max problem was rare and only affected a few planes? That said Boeing released the software thinking it was OK. The difference here (other than that was air safety is this is for those that play ham radio) is that Flex knew it was an issue (BSOD) and released the software anyway. I know if I tried to update and saw the BSOD I would be pooping in my pants that I was going to spend hours rebuilding my data. There is no need to put people through that, that's what you have Alpha testers for. Flex mantra has been no software released before its time, except this time.
Flex generally has been a company which others should try to equal. It looks like Elecraft may slay the king.

Bill -VA3WTB

If one took the time to read the release notes this problem was mentioned in the notes, that it may happen,,but it will also clear after the reboot. So no need to poop your pants, it was all explained.

They did a fine job releasing the update, it was badly needed.

Also, when Gerald said software will not be released till it's ready means that there are no critical bugs that will provent the radio from funtioning properly.
As I stated before, this bug is not considered critical because it will correct after a reboot, sounds like a reboot is needed on some computers to correct a registry problem.

Steve K9ZW

Burt Fisher

Clay N9IO

Boeing Max really??? The man's comment was out of line, not going further with this. Enough.

Andy M5ZAP

Yet again the forums are reduced to insults by “Elmer” Steve K9ZW. Someone has a problem so they reach out to the forum and get insulted and ridiculed. Unfortunately flex chose to use the windows operating system so we have to live with it. The forums will by there nature have people who are frustrated and irritated with there flex. Surely the forums are there to help these people ?

Andy M5ZAP

Yet again the forums are reduced to insults by “Elmer” Steve K9ZW. Someone has a problem so they reach out to the forum and get insulted and ridiculed. Unfortunately flex chose to use the windows operating system so we have to live with it. The forums will by there nature have people who are frustrated and irritated with there flex. Surely the forums are there to help these people ?

Erik EI4KF

The Forum is not "reduced" to insults by K9ZW. His deplorable postings are just a pimple on otherwise unblemished skin. Give due respect to the 99.9% superb support on here, unparelled on any other similar Forum. There will always be the gutter snipes who somehow evade moderation, Just ignore.

Andy M5ZAP

Fair comment

Pat N6PAT

@Andy, I agree with you. I find comments that insult others of no value and a detriment to the purpose of a forum.

If you do not agree with a post then either engage the poster in a mutually beneficial exchange of viewpoints or just ignore it. Resorting to juvenile tactics serves no one.

John - K3MA

Burt Fisher

David

Andy M5ZAP

What I found previously was that multiple reboots did somewhat stabilise the system. Unfortunately a change to the windows environment like installing another software package or a windows update would then destabilise it and the same blue screen returned. Sometimes stabilising quickly other times taking many reboots. This was on a windows 10 pro fresh install. My other system on windows 10 home was from a upgrade path and was always stable. I have no data to back this up but it feels like anything that’s makes a change to the registry (or similar) destabilised the system again.

Robert White

Same experience.  Sort of glad to see this here, as I did not know Flex was the culprit.  I purchased a new Surface Pro 7  for Christmas, 2019 and this happened right away - first software installed on my system.   Had to reboot 4-5 times and it seems to have settled. Thought it might have something to do with Surface Pros as it used to happen on my old Surface Pro 3 too.  Running the latest version 3 software.  73 Robert K0RCW

Burt Fisher

I got a Icom 7300, turned it on and it worked. Noise filter worked too.
The downside is the screen is smaller than the 6400M but it came on in 5 seconds.

John - K3MA

Installed on another 4 systems and blue screen on all 4.  So from my experience 8 of 9 system with the error.  Lucky multiple reboots seems to fix on all systems except one in which it seems to return every now and then.  I have a couple dozen different software packages installed on many of these systems and the issue only comes with the install of SmartSDR.  I have tried installing SmartSDR as the first program on a clean system and the problem still happens.