MicroCode studio crashes while typing in code.

[CuriousOne]

Windows 10 Pro 21H2 or whatever the last build is called.

[HenrikOlsson]

Several threads on this over the years, as far as I can remember no definitive cause or cure found. It used to crash a lot on my old W7 machine - to the point where it was barely usable, then I built I new machine (5-ish years ago) with W10 and I don't think I've had a crash since.

[Ioannis]

One could say it might have to do with a driver, but I guess Henrik you transferred the same stuff on the new machine, right?

And how possible can it be you have the same configuration with of your old W7 with CuriousOne new W10 machine?

Tough one it is.

Ioannis

[CuriousOne]

Well, I took some more time to investigate this issue - I even set-up high speed camera to record my screen, to capture the moment when this error happens. And here are the results.
In most cases, this error happens when you just finish typing in the statement, and it should change it's color to blue. Or the crash occurs when you start typing after the statement become blue.
On my old machine - i3-9100F/16GB/RX550 this was not happening. So, for testing purposes, I installed a new SSD on it, did clean install and tested again - no problems found.
Configuration of new PC is as follows: i3-12100F/16GB/RX6500XT. So since that error was happening when text changes color, I thought that graphics card might be messing up, so I installed that RX6500XT into my old machine and there are no errors, so graphics card is excluded. The only major difference between my PCs are that the new one has new office and visual studio installed too. So maybe they install some dotnetfx or something like that, which messes up PBP.
I've got another SSD, and will do clean install on the "new" pc, to ensure that everything is ok.

[HenrikOlsson]

First of all we need to be clear that it's not PBP that crashes - it's MicroCodeStudio, which is a separate executable. MicroCode studio is developed by a third party, which does not make it easier getting it fixed.

On my old machine I had VisualStudio of some sort, on the new one I don't. Obviously there are literaly THOUSANDS of other things that are different but that is ONE clue.

Video / graphics issue is another angle and one that Darrel brought up in one of the threads from many years ago. Again, no definitive cause or cure found.

[Ioannis]

I guess safe mode does not produce crashes, right?

Ioannis

[tumbleweed]

Have you tried setting a compatibility mode?