Jump to content
  • 0

Waveform 2015 v3.3.5 crashing on Windows 7 Enterprise 64 Bits


rk100

Question

Hi there,

after buying the Analog Discovery 2, I installed Waveforms without any problems, but when starting Waveform 2015 v3.3.5 it crashes immediately  on Windows 7 Enterprise 64 Bits.

I also tried v3.3.3 getting the same result.

 

Getting two problem reports immediately one after the other:

Problemsignatur:
  Problemereignisname:    APPCRASH
  Anwendungsname:    WaveForms.exe
  Anwendungsversion:    3.3.3.0
  Anwendungszeitstempel:    57332ffc
  Fehlermodulname:    ntdll.dll
  Fehlermodulversion:    6.1.7601.23455
  Fehlermodulzeitstempel:    573a54b7
  Ausnahmecode:    c0000005
  Ausnahmeoffset:    000000000004ba71
  Betriebsystemversion:    6.1.7601.2.1.0.256.4
  Gebietsschema-ID:    1031
  Zusatzinformation 1:    6844
  Zusatzinformation 2:    68446d351aa0616ef4ad51f70ac1e6ae
  Zusatzinformation 3:    43b5
  Zusatzinformation 4:    43b5d2ec0051e95cf2b7acee2fe203a8

 

Problemsignatur:
  Problemereignisname:    APPCRASH
  Anwendungsname:    WaveForms.exe
  Anwendungsversion:    3.3.3.0
  Anwendungszeitstempel:    57332ffc
  Fehlermodulname:    ntdll.dll
  Fehlermodulversion:    6.1.7601.23455
  Fehlermodulzeitstempel:    573a54b7
  Ausnahmecode:    c000041d
  Ausnahmeoffset:    000000000004ba71
  Betriebsystemversion:    6.1.7601.2.1.0.256.4
  Gebietsschema-ID:    1031
  Zusatzinformation 1:    d30d
  Zusatzinformation 2:    d30d5fccfe290dfec9f2cf555e634978
  Zusatzinformation 3:    ba06
  Zusatzinformation 4:    ba0672fff19d12af57868c0783d4e1fe

 

Any help appreciated.

Rolf

Link to comment
Share on other sites

8 answers to this question

Recommended Posts

Hello,

The software was tested on such system too, so I suppose the crash is related to something on your Windows.

I found several post on similar ntdll errors, one of them: http://pcsupport.about.com/od/fixtheproblem/a/ntdlldll.htm

You might try installing the 32bit version of the WaveForms Application by launching the installer from command line with /Architecture32 argument:
> digilent.waveforms_v3.3.5.exe /Architecture32

Link to comment
Share on other sites

We're seeing the same issue with version 3.3.5.  A coworker and I have been testing the install and software before deploying it to a teaching lab, and both of our Windows 7 64-bit machines are having this problem.

Usually after 2-3 tries, the Program Compatibility Assistant comes up and says "Windows detected that this program did not run correctly" and that it "has applied compatibility settings".  After that, Waveforms appears to run normally.

Found a log entry for the Program Compatibility Assistant:

The Program Compatibility Assistant was invoked to correct a compatibility problem. Information about the application is below.

Application name: Digilent WaveForms Application
Application version: 3.3.5.0
Executable path: C:\Program Files (x86)\Digilent\WaveForms3\WaveForms.exe
Scenario ID: 13
User action: Applied recommended settings
User action ID: 201
Compatibility layer: DISABLEUSERCALLBACKEXCEPTION
FileID: 0000e3dfe4c5e9f2c049b4b3f0ed1332c8e6225b005e
ProgramID: 0006135c5ade70741a62c43f4a6c95ce527b00000904

Also found this, not sure if related, and having trouble finding more information about it:

LogName Microsoft-Windows-Application-Experience/Program-Telemetry

Event ID 500

Compatibility fix applied to C:\Program Files (x86)\Digilent\Runtime\UsbDriver\DPinst.exe.
Fix information: Driver Install Frameworks (DIFx), {f662e2f8-1d5a-11dd-8d8c-0010180bf8d5}, 0x10101.

Link to comment
Share on other sites

Not on my test machine, no.  It's a virtual machine that I keep relatively clean for software install testing.  Base snapshot just has vmware tools, some utility software for archive files and mounting ISO files, and a few of the visual C redists.  Running Windows 7 Enterprise 64 bit.

Issue doesn't occur on a Windows 10 machine.

Link to comment
Share on other sites

I managed to reproduce the problem on a clear Windows 7 x64 Enterprise installation. On earlier installations it is working fine.

Until this problem problem gets solved, the current version seems to be useable with the automatically set DISABLEUSERCALLBACKEXCEPTION flag.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...