04-15-2011 05:35 AM
Hi all,
today I had two DIAdem crashes
Can anybody give me a hint how to isolate and avoid this problem?
Thank you
gemu
OS: XP/32 prof., SP3
--- System Error Log ---
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 15.04.2011
Time: 10:58:41
User: N/A
Computer: SW301
Description:
Faulting application diadem.exe, version 11.2.0.4346, stamp 4cec5ca8,
faulting module ntdll.dll, version 5.1.2600.6055, stamp 4d00f27d, debug? 1, fault address 0x000673be.
Event Type: Information
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1001
Date: 15.04.2011
Time: 10:58:57
User: N/A
Computer: SW301
Description:
Bucket -1895173773, bucket table 1,
faulting application diadem.exe, version 11.2.0.4346, stamp 4cec5ca8,
faulting module ntdll.dll, version 5.1.2600.6055, stamp 4d00f27d, debug? 1, fault address 0x000673be.
--- DIAdem logfile ---
1 10:58:39 Error:
Error while executing "" command
Error type: UNKNOWN
Error address: 0004387F
Module name:ntdll.dll
2 10:58:39 Error:
Error while executing "" command
Error type: UNKNOWN
Error address: 0004387F
Module name:ntdll.dll
04-15-2011 11:18 AM
Hi gemu,
I asked DIAdem R&D to take a look at your error log, but they were not able to learn anything from it. It looks to me like it's your .NET Runtime Engine doing the complaining...
What's the history here? Did DIAdem used to work on that computer? If so, what changed between then and now? Have you installed anything recently-- applications, updates, etc.? Does DIAdem work on any other computers?
Brad Turpin
DIAdem Product Support Engineer
National Instruments
04-18-2011 08:15 AM
Hi Brad,
DIAdem did run stable for a long time. There were no changes on the computer from my side.
However I have a creeping suspicion that Patch Tuesday relates to this issue.
Time will tell.
Thank you
gemu
.