PSoC Creator 3.1崩溃然后蓝屏死机

好吧，我？我喜欢使用软件的版本，我知道，我总是试图禁用自动更新。
然而，我发现从PSoC Creator 2.2升级到3.1最近合理。我想是星期五，也许是星期四。我立刻遇到了一个重现性的崩溃。那么今天，我得到一个蓝屏死机和损坏的项目文件，将不再打开。它暂时失去了我的顶级设计和代码编辑。幸运的是，我有每小时自动备份。我能恢复的项目，包括最新的顶层设计的变化（超过一小时），然后复制我的独立的C文件到回收项目，我最近的代码编辑。我只是失去了约2小时，包括启动和其他东西加载状态。
所以我必须找到这个问题的底部，或者回到2.2。
重复出现死机的情况几乎任何**的时候我试图在源代码编辑#宏。这个软件尝试做实时预编译和语法检查，无论你怎么称呼。我相信这是一个问题。如果我试图在#类型包括“文件名。H”，然后出现大跌，100的每一次当我键入“E”完成了“#包括“。我已经附加了错误信息的JPG。而我能型”#如果0“我经常做暂时删除一段代码，我后来当我键入“# endif”得到同样的崩溃，对整理后的单词以字母“F”。
我不知道我在做什么死亡蓝色屏幕时发生。我想，如果再发生这种事，我会担心的。
非常感谢您的帮助。
-赫尔穆特
错误MSG JPG
50.6 K



     以下为原文
  Well, me?  I like to stick with the version of software that I know works, and I always try to disable automatic updates.
    Nevertheless, I found it reasonable recently to upgrade from PSoC Creator 2.2 to 3.1.  I think it was Friday; maybe Thursday.  I was immediately met with a reproducible crash.  Then today, I got a blue screen of death and a corrupted project file that would no longer open.  It temporarily lost my top design and code edits.  Fortunately, I have *hourly* automatic backups.  I was able to restore the project, including most recent top design changes (more than an hour old), then copy my free-standing c file back into the project, recovering my recent code edits.  I only lost about 2 hours, including the reboot and reload of other status stuff.
    So I must get to the bottom of this problem, or go back to 2.2.
    The reproducible crash situation occurs pretty much *any* time I try to edit a #macro in the source code.  This software tries to do real-time advance compiling and syntax checking, whatever you call that.  And I believe it is a problem with this and #macros.  If I try to type in  #include "filename.h", then the crash occurs 100% every time when I type the "e" finishing up "#include".  I've attached a jpg of the error message.  While I can type "#if 0" as I often do to temporarily remove a chunk of code, I get the same crash when I later type "#endif", right after finishing the word with the letter "f".
    I don't know exactly what I was doing when the blue screen of death occurred.  I'll worry about that, I guess, if it happens again.
    Your assistance with this is greatly appreciated.
    -Helmut

•    error msg.jpg 50.6 K