MCS is Crashing

[picster]

Nope, long-winded comments, a DEFINE OSC 10 thrown in, more comments, no problem.

Robert

Perhaps I'm not approaching this with the same attack...

If this was a "sure thing" that ALWAYS happened, it would be pretty easy to resolve. However, my experience is it's very hit and miss - hence I don't believe a crash can be "forced", there are other undetermined variables involved, but... again... because it ALWAYS when I'm typing, I believe that says something. It can sit idle for DAYS and nothing happens. I'm wondering if others who are experiencing this can avoid crashes by trying this change, thereby contributing to the validation of the theory - not try to FORCE another crash when it's unpredictable and not a "sure thing".

[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