MicroCodeStudioPlus keeps crashing.

[picster]

I have not tried in XP compatible mode, but will try that prior to trying it in a virtual machine. I have tried ADMIN status. Windows is managing my paging file, I have 16G of ram installed, and crashes occur in MCS when I've done a clean boot with very little running. No other apps that I use crash on my system, literally, ever. The error is not a BSOD, it's a program crash error (see below, if I can paste the image properly).



Same happens in each of 3 laptops that I've tried this on, so it's not related to video card (which are different), and one was a pristine machine that I had just restored to factory settings. All are DELL.

[Ioannis]

All are DELL.

This can't be a coincidence.

Maybe a Dell software or driver?

Ioannis

[HenrikOlsson]

I've had MCSP crash on at least two different Machines, none of them DELL so no, that's not the key - either.
It seems that everytime this issue is brought up people have forgot that it's been reported over and over again - for years - by a varity of users. It is NOT an isolated event on a single computer. Many users have experienced the problem - and reported it.

It's clear that there are more people not noticing the issue than there are people who do but that doesn't make it any less "real".

I don't mean to sound negative, it's great that we're throwing ideas up in the air and one day or another we might find the issue and if/when we do we MIGHT get Mecanique to fix it because one thing is clear, as is they don't give a shit.

With that said, I don't think I've had a single crash on my (now not so) new machine running W10.

[Ioannis]

Glad your are crash-free now Henrik.

There must be something in common to all these machines that crash on MCS.

Can you give more details as to what your machines were composed of?

Ioannis

[picster]

Glad your are crash-free now Henrik.

There must be something in common to all these machines that crash on MCS.

Can you give more details as to what your machines were composed of?

Ioannis

Just curious, where does one begin with this? Hardware or software, driver versions, or ? I ask because my "main" laptop is a 2012 model and has served like a loyal horse, and has accumulated lots of software for all purposes over that time - it's not just used for this. Meanwhile, a "too slow" laptop "give it to dad" from one of my kids that I just wiped back to factory has minimal installs, and still exhibits the issue (I tried in a desperate attempt to rid myself of the problem). Obviously that would be an easier place to start, but on an established, somewhat loaded multipurpose system, it's really not viable - maybe the COMMON software/hardware elements with the "bare bones" system would be helpful.

[picster]

Compatibility mode for XP results in a crash as well.

[Ioannis]

The error is the same all the time?

Seems like a problem with memory address.

But on a factory state? My suggestion is to try to find what all machines have in common. A driver, a USB chip, something.

Ioannis

[HenrikOlsson]

If you read this thread on the MELABS forum you'll get some information and background to the problem. I just browsed thru it and see that I apparently had 80 logged crashes during the course of 2 years and that was back in 2014 meaning it's been crashing on me, personally since 2012.

Here's another one

So it's me, BigWumpus, Norton, c_moore, picster, Dick Ivers, BrianT and even Darrel across two or three threads. I'm fairly certain others have chimed in as well but again, whenever one does it feels like someone else says "I've never seen it so it must be something with your computer". I know everbody is just trying to help but it's pretty frustrating.

Here's another thread where I've posted some details about the machines I had at the time: http://support.melabs.com/forum/picb...-studio-issues

I've said it before but I'll say it again. It may very well be some other software or driver or whatever that is the actual culprit but then MCSP is overly sensitive to whatever is because it's the only spftware that crashes like this.

[picster]

Unfortunately, I just discovered that I cannot try it on a Windows XP machine - virtual or otherwise, since the PIC I'm using requires PBP 3.1 and it is incompatible with XP... so unless I can pick up a cheap W7 laptop somewhere, I'm no further ahead and at somewhat of a dead end. I *can* try it on a machine that I recently upgraded to W10 - although - it previously crashed on that machine running W7.

Picster

[Ioannis]

Of course Mecanique should fix this, but I am trying to see anything in common to all the cases.

If indeed there is a driver, a program or something else that we miss this moment, maybe it will lead to a solution.

Do all crashes (of different users) give the same error message?

Ioannis

[pedja089]

If I may add, to me, problem probably doesn't have anything with hardware, drivers, etc...
A List index out of bauds(0) points to me, that some of list isn't initialized. I don't know how they triggering recognition of keywords, and auto correct etc.
I think that error probably jump out while typing. So it needed to be specific combination, I think someone mention that error is related with typing comments.
I don't know what programing language they use, but simple TRY ... CATCH should do a trick, or in VB on error resume next in every sub routine. That isn't a lot of work, but it can ignore error, or point to line of code where is happening.
Anyway, that I use in my programs to prevent crashes, and when error do happen, user can send me print screen with detailed description in MSGBOX. Saved me lot of times...