Nistune 9.14.7 and 9.14.2 Crashing

[bachig24u]

Getting Program Crashes within 10seconds to a minute of opening Nistune App;

Using 9.14.7 and 9.14.2 and type 1 rev3 with CR31 addy and VL-NA Bin.
MS-XP Pro
USB-Serial Belkin adapter for Innovate LC-1

order of events;
1.Nistune opens and connects to Consult automatically.
2. WB LC-1 is opened which is connected via a Belkin USB-serial adapter (com7).
3. Log recorder is fired up.

and then intermittently the program crashes.

problem seemed to be a little less often with stream mode enabled.
not crashing without Wideband opened, never in log player mode or just consult when making changes or burning/writing Rom.
Either Log recorded or Wideband made issue worse.

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 21/04/2010
Time: 8:17:42 PM
User: N/A
Computer: TUNER
Description:
Faulting application nistune.exe, version 1.0.0.1, faulting module nistune.exe, version 1.0.0.1, fault address 0x0013191f.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6e 69 73 ure nis
0018: 74 75 6e 65 2e 65 78 65 tune.exe
0020: 20 31 2e 30 2e 30 2e 31 1.0.0.1
0028: 20 69 6e 20 6e 69 73 74 in nist
0030: 75 6e 65 2e 65 78 65 20 une.exe
0038: 31 2e 30 2e 30 2e 31 20 1.0.0.1
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 31 33 31 39 t 001319
0050: 31 66 0d 0a 1f..

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 21/04/2010
Time: 7:04:25 PM
User: N/A
Computer: TUNER
Description:
Faulting application nistune.exe, version 1.0.0.1, faulting module nistune.exe, version 1.0.0.1, fault address 0x00069395.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6e 69 73 ure nis
0018: 74 75 6e 65 2e 65 78 65 tune.exe
0020: 20 31 2e 30 2e 30 2e 31 1.0.0.1
0028: 20 69 6e 20 6e 69 73 74 in nist
0030: 75 6e 65 2e 65 78 65 20 une.exe
0038: 31 2e 30 2e 30 2e 31 20 1.0.0.1
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 30 36 39 33 t 000693
0050: 39 35 0d 0a 95..

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 21/04/2010
Time: 6:59:04 PM
User: N/A
Computer: TUNER
Description:
Faulting application nistune.exe, version 1.0.0.1, faulting module nistune.exe, version 1.0.0.1, fault address 0x00069395.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6e 69 73 ure nis
0018: 74 75 6e 65 2e 65 78 65 tune.exe
0020: 20 31 2e 30 2e 30 2e 31 1.0.0.1
0028: 20 69 6e 20 6e 69 73 74 in nist
0030: 75 6e 65 2e 65 78 65 20 une.exe
0038: 31 2e 30 2e 30 2e 31 20 1.0.0.1
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 30 36 39 33 t 000693
0050: 39 35 0d 0a 95..

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 21/04/2010
Time: 6:29:04 PM
User: N/A
Computer: TUNER
Description:
Faulting application nistune.exe, version 1.0.0.1, faulting module nistune.exe, version 1.0.0.1, fault address 0x00069395.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6e 69 73 ure nis
0018: 74 75 6e 65 2e 65 78 65 tune.exe
0020: 20 31 2e 30 2e 30 2e 31 1.0.0.1
0028: 20 69 6e 20 6e 69 73 74 in nist
0030: 75 6e 65 2e 65 78 65 20 une.exe
0038: 31 2e 30 2e 30 2e 31 20 1.0.0.1
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 30 36 39 33 t 000693
0050: 39 35 0d 0a 95..

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 21/04/2010
Time: 6:13:28 PM
User: N/A
Computer: TUNER
Description:
Faulting application nistune.exe, version 1.0.0.1, faulting module nistune.exe, version 1.0.0.1, fault address 0x00069395.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6e 69 73 ure nis
0018: 74 75 6e 65 2e 65 78 65 tune.exe
0020: 20 31 2e 30 2e 30 2e 31 1.0.0.1
0028: 20 69 6e 20 6e 69 73 74 in nist
0030: 75 6e 65 2e 65 78 65 20 une.exe
0038: 31 2e 30 2e 30 2e 31 20 1.0.0.1
0040: 61 74 20 6f 66 66 73 65 at offse
0048: 74 20 30 30 30 36 39 33 t 000693
0050: 39 35 0d 0a 95..

[Matt]

thanks for the info. have a look at the log tonight and see if i can repeat

try turning off the auto connect to consult and see if it still happens?

[bachig24u]

Matt,
Is there a best practices (preffered order) in which things should be started;
eg, click WB, then Log recorder, then consult or log recorder, consult, WB?

Kind Regards

[Matt]

it should just work. if you do WB and consult first then log player (should) be fine

[Matt]

yeah I cant seem to make it happen here. I'm using a VLT ECU but tried both CR31 and VLT address files with consult auto connect, then wideband then log recorder.

what if you open the logger by itself - does it crash then or only when all three are used?

[bachig24u]

Would it help if I enable debug logging next time I run the car?

Will debug logging causes any known issues? I'll get a chance this wed@WSID if the weather is good

KR
Sime

[Matt]

if you can enabled then i can compare that log against mine to determine an exact sequence of events

enable it and then restart nistune. it will output a log file to the logs folder

[bachig24u]

Hi Matt,
I have compressed 3 logs. 2 crashed, wibeband caused one I think as Nistune couldn't comms with wideband device. I don't know why it occured as the car was driving back down the return lane after it's run at WSID.

[Matt]

Programmed up a board with CR31 ROM image and running against wideband (Innovate) with USB-serial converter (ATEN)

Trying again now in the debugger and will leave it for a while

One of the logs saw a crash almost immediately

Do you have any other problem with programs on that PC? In the past when I've seen memory issues on PCs (including my desktop which needed a memory stick replaced) it caused continuous crashes on various programs. Eventually I took the PC back and they ran a memtest on the stick and replaced it, crashes gone. Other people arent seeing this and I certainly dont. Although one run Initial run left for 1/2 hour did have a crash ... that was running outside the debugger so I will check that out

I'm only saying this because it seems you are having crashes randomly with the streaming data.

Logs:
0505-1802
Stream usb consult data 6 mins
Start logger (noticed some errors reported here - not causing crash but will check them out)
Logger closed, nistune closed (normally?)

0505-1926
MTS connected and running. USB consult (Type 1) running and streaming
Crash occurs after MTSMonitor loop print but before data. Perhaps string clobbering due to 2 data streams?

0505-2022
10 minutes using logger
Connect to USB consult (Type 1)
Disconnect from USB errors (no data recieved on USB port)
Reconnect and stay connected 3 minutes then crash.
This happened after transmitting request for stream data, and before response received. No reason for this unless the FTDI drivers crashed us receiving the data. No data processing was occurring yet since data not received

0512-1851
Connected with wideband and USB consult (type 1)
Running 13 minutes with both. Transmitted request for single byte, received response and crashed. Perhaps string clobbering again on text data as per 0505-1926? not enough data

0512-1911
Various stuff and then 5 minutes both wideband/usb consult. Crash after data received

0512-1925
Wideband lost comms here. Innovate MTS reported no data received. At this same time we trasnmitted a request for data and before response it crashed. Similar to 0505-2022

0512-2243
Config dialog opened. Change COM port for innovate (COM1) and crash

This last one is really suspicious. Its as if the Innovate driver crashed when we were using it. Something is suspicous. Does logworks crash if you use it for long periods. What about Nistune with Type 1 and logworks running same time?

Can you confirm if this is correct
(a) nistune crash occurs when only Type 1 is active
(b) nistune crash doesnt occur if wideband only (need to run for sometime with this one)

[Matt]

no difference Type 1 with stream/tuner mode. this will change soon though

[bachig24u]

Matt, More testing has localised issue.

Replaced laptop motherboard and ram, connect WB, connect Consult, try to either sync up or down (F8).
Message on Innovate WB dialog "can not communicate with device" , Nistune Crashes MS-XPpro-SP3 closes app.

Completely different laptop: connect WB, connect consult, try either sync up or down (F8).
same, Message on Innovate WB dialog "can not communicate with device" , Nistune Crashes MS-XPpro-SP3 closes app.

Connecting Innovate LC-1 via serial port (com1) instead of Belkin usb-serial adapter,
same, Message on Innovate WB dialog "can not communicate with device" ,Nistune Crashes MS-XPpro-SP3 closes app.

Ran LC-1 in Logworks under com1 and Virtual Com 6 (using USB-serial adapter) , Connect Consult, try sync either up or down (F8).
Could not reproduce fault using LC-1 using Logworks for AFR logging.

note: In all testing I had engine running then also with dashboard 'reds' ignition only with engine stopped.

Please let me know if you require further info or tests.

KR
Sime

[Matt]

Sime

Found same issue today on R31 during testing and all fixed now. Let me know if still any problems with crashing. Sorry this took so long

[bachig24u]

Matt,
Latest beta has resolved App crash issue "when LM-2 and LC-1 connected and sync/write operation performed"

Thanks
Sime

[Matt]

Good stuff. Sorry it took so long to find. Sometimes these are a pain