LV 8.0.1 'NOT RESPONDING' and/or 'split' and unusable front panel while scrolling

Question

Hello,
Is anyone aware of any display or front-panel glitches and bugs with LV 8.0.1?  I have been using LV for years, but I have never seen the front panel tear itself (literally) in sections while I use the standard scoll bars at the edges of teh screen, then become completely unusable and go into [NOT RESPONDING] mode (???). In other words, my front panel displays have always moved as one continuous piece when scrolling.  During these recent episodes, I would use the scroll bars and parts of my front panel displays would not move while the other section(s) tore away and scrolled as I commanded.  When this happens, my entire PC would slow down, the CPU usage would rise and a approach 100%, and the VI was unusable.  I have been writing a particular VI for several months, starting in LV 6.1, then LV 8.0 PRO-DEV, and recently upgraded to the LV 8.0.1 'maintenance' release.  The problem that  I describe here began to occur within two weeks of the maintenance upgrade.  The problem seemed to be propagating to my back-up version after I opened each VI in unsuccessful attempts to find a VI that did not appear corrupted.  It seemed as if any VI that I opened was going to be plagued by the bug that I described above and I thought that I was going to lose months of expensive work and my job!!!!.  In a last ditch effort ( and a stroke of pure genius) I started saving some of these coorupt version as 'PREVIOUS' in LV7.1 format.  This seems to have turned the situation around, for now, and saved my VIs from becoming corrupted and completely unusable. 
Please let me know if anyone else has seen this.  Also, please let me know how to avoid this, in the future.  Does this indicate corruption of my LV 8.0.1 PRO-DEV environment or the VI files (or both)?  Does NI have tools to correct these corruptions?
Thank you.

Answer 1

Thank you. I can only point to the following events/ techniques that were somewhat different from my previous experiences/ techniques:
1) Performed 'SAVE AS... ' new file name to these files over several months and several times a day using similar filenames with only one number character different between them
2) Logging long data files to the root C: drive and closing in on less < 5GB HDD remaining (could this be overwriting soem temp files that LV uses to manag graphics???)
3) After saving to LV 7.1 and re-opening with LV 8.0, I get a message that is new to me that explained something about wiring a Boolean constant to a case structure and how LV 7.1 or previous used this to keep a sub-vi in memory (???).  Unfortunately for me, I did not capture the exact syntax of this message and I do not wish to intentionally repeat this graphical feature.
4) I copied a small block of code that contained a 'cloned' sub-vi from one block diagram to the a similar VI that , shortly afterward, exhibited the front-panle 'tearing' feature.  This is something that I usually do not do, and, again, is one of the only new actions from anything that I have done in LV for the past several years.
5) After the message described in (3), above, the rescued LV 7.1 version had moved a handful of the most recently added indicators to a very remote location, about 30 seconds of edge-scrolling time, to the left of my front panel graphics.  I perfromed a 'drag' operation by selecting these and bumping them to the right edge of the screen for about 30 seconds to get them back to the vicinity of my front-panel graphics.  I have never experienced a VI that shifted inidcators so far off the edge of the screen.
These are the only ' unique' events that I can recall before the 'tear; effect.
Thank you.