MCS is Crashing

[Demon]

Well then, I guess I'll just keep an eye open and report back f anything happens. But MCSP has never bombed on me in over a year on this laptop.

I honestly cannot see how graphic drivers have anything to do with data entry, especially in software that emulates Notepad (no special characters).

But then again, my specialty was mainframe programming. I only program PCs when I sleep at the Holiday Inn.

Robert

[picster]

Just crashed, not using italics. So much for that theory. HOWEVER, it still crashed while I was typing in a comment field, which has always been the case for me.

[Amoque]

I find it highly unlikely that it has anything at all to do with PBP (other than the obvious interruption to it). If so, I would think every user (having the exact same files loaded) would have the exact same issue - and, one would suppose, it would not be difficult to duplicate for the same reasons. I think that it must be some interaction with another process or service - perhaps a background application using the com port, USB access or internet connection- there are dozens of running programs active from the moment the power is turned on.

Has anyone disabled the files that start at power up? It is one of my pet peeves is manufacturers who seem to believe they own all of my computer's resources because I use one of their applications. I have found HP, Nvidia, and Adobe to be nearly criminal in their dis-care, but they are far from the only culprits. Starting with a minimal set-up and adding one line or application at a time may help to isolate what resource is causing the issue?

[picster]

crashed again this morning, while typing a comment (same as always).

Faulting application name: CodeStudioPlus.exe, version: 5.0.0.5, time stamp: 0x2a425e19
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x00000000
Faulting process id: 0x1fb0
Faulting application start time: 0x01d2d7bae18ebaac
Faulting application path: C:\Program Files (x86)\Mecanique\MCSPX\CodeStudioPlus.exe
Faulting module path: unknown
Report Id: 1f0308d8-43b0-11e7-a3d0-ac72892a9ffd

and 23 seconds later,

Faulting application name: CodeStudioPlus.exe, version: 5.0.0.5, time stamp: 0x2a425e19
Faulting module name: ntdll.dll, version: 6.1.7601.23796, time stamp: 0x59028db3
Exception code: 0xc0000025
Fault offset: 0x000904b0
Faulting process id: 0x1fb0
Faulting application start time: 0x01d2d7bae18ebaac
Faulting application path: C:\Program Files (x86)\Mecanique\MCSPX\CodeStudioPlus.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 2d149eb5-43b0-11e7-a3d0-ac72892a9ffd

Any further suggestions?

This is the ONLY program that halts and displays an error, ALWAYS when typing in comments.

[mark_s]

Just a quick scan through the error list and this sticks out "Faulting module name: ntdll.dll." A quick Google of "ntdll.dll" and found this, along with a lot of other hits.

https://www.lifewire.com/how-to-fix-...errors-2624474

Maybe a solution?

[Scampy]

NTDLL.DLL is a windows system file containing library data for the core windows kernel. This would suggest that the issue is more likely a conflict between it and other system files rather than MSC itself crashing. Typical suspects are driver files, with prim suspects being graphics drivers. ATI and NVidia both have been know to have drivers that can cause this issue (as I stated in you other thread).

Often ensuring that your system is as up to day as possible is recommend, however I have found that on the odd occasion using an older driver, such as the one supplied with the graphics card has resolved a similar issue. Other possible causes can be a corrupt registry, but only a totally clean re-install on a freshly low level formatted drive will resolve that, but is often the last resort.

If you have access to another machine, try installing MCS etc and see if the issue is easily replicated. Unless the two machines use identical components I doubt that the problem will occur

[HenrikOlsson]

NTDLL.DLL is a windows system file containing library data for the core windows kernel. This would suggest that the issue is more likely a conflict between it and other system files rather than MSC itself crashing

If it's conflict between ntdll.dll and other system files then why is MCS the only program crashing with that particular error message? Do you believe MCS is the only program using a particular function exported by ntdll.dll?

MCS is the only program I've seen do this and it's done it to me hundreds of times on 3 different computers, it's done it to many other users as well yet the notion that it's got nothing to do with MCS keeps comming back.

The enduser (me) doesn't really care if the actual error is in the MCS source or in any of the supporting files MCS is using, it's MCS that crashes. If it does that due to a bug in MCS code itself or the way it calls some library function or an actual bug IN that library it ought to be in the developers interest to fix it but but he's already got my money and doesn't seem to care that much despite multiple threads and reports for YEARS. And MeLabs claims they can't do anything about it since they're not the developers, handy isn't it?

[picster]

NTDLL.DLL is a windows system file containing library data for the core windows kernel. This would suggest that the issue is more likely a conflict between it and other system files rather than MSC itself crashing. Typical suspects are driver files, with prim suspects being graphics drivers. ATI and NVidia both have been know to have drivers that can cause this issue (as I stated in you other thread).

Often ensuring that your system is as up to day as possible is recommend, however I have found that on the odd occasion using an older driver, such as the one supplied with the graphics card has resolved a similar issue. Other possible causes can be a corrupt registry, but only a totally clean re-install on a freshly low level formatted drive will resolve that, but is often the last resort.

If you have access to another machine, try installing MCS etc and see if the issue is easily replicated. Unless the two machines use identical components I doubt that the problem will occur

This isn't directed at you Scampy, but it's an acknowledgement of a lot of wasted time and effort, caused by ONE program that the developer isn't fixing.

The problem has occurred on 3 of 3 machines of mine, different graphics card, ALWAYS while running MCS and ALWAYS while typing comments. No other programs are crashing with this error. I repeat for clarity, NO other programs are crashing with this error, my system is rock solid stable otherwise. Seeing as MCS is always the offending (crashing) party, I would thing the manufacturer would be held somewhat accountable. I know there is a number of users who have reported this issue, and are met with frustration and denial "it's peculiar to your system" - "and yours" "and yours". More than one (I have THREE) means it's not a single system. More than one operating system means the same. It all points to MCS being the uncooperative player, since nothing else is crashing, all the other kids "play nicely together".

There is no guarantee that any of the "fixes" noted will work, when this isn't a windows problem, it's a MCS problem. There is some aspect of it that's doing this or a number of other users and I would all see this same error on OTHER programs on our multiple (non-identical) systems as well. Yet there is NO cooperation from the software developer because they "cannot replicate the problem". Too many of us have it, and there should be some accountability for paid software that not only crashes, but loses our work. That really sucks.

This isn't directed toward any individual - except perhaps the developer - but the whole ostrich thing of "one off" isn't helpful when you are one of a NUMBER of "one-offs" that this is recurring with, and you've tried it on no less than 3 different laptop system configurations with the same results.