"Run debuger configuration" in CVI 5.5 causes reboot the whole PC

[Gennady]

On some stage of development my project I found that the "Run debug congiguration" causes the reboot of PC (I use Intel Celeron 466MHz, 128MB, WIN98 4.10.2222A). Because of this I can not troubleshoot the system and understand what is going on. If I compile the same project in release mode everything is OK. But I need debug mode.
Hey, NI's gurus, can you help me with that?
Thanks.

[Jeremiah Cox]

Hello Gennady,
I am not sure why your system is rebooting, but I have a few ideas we can try in an attempt to locate the problem. First, does this only happen with a specific project or is this phenomena independent of project? Try debugging some of the projects located in the \samples directory to determine if we can reliably reproduce this behavior with multiple projects. If we cannot, then your project may be doing something unusual, or the project file may have become corrupted. If the behavior is reproducible with other projects, then there may be something wrong with your CVI installation (run Scandisk and/or re-install) or there may be some conflict with other software/hardware within your system. If you run Scandisk and re-install with no chan
ge, then you may try systematically uninstalling/disabling other software/hardware in an attempt to find which one may be interfering with CVI (some try booting to safe mode as a quick check as it disables most drivers). I have recently seen issues with virus scanners and versions of Windows 2000 prior to Service Pack 2 (these have been few and far between, but this gives you some idea of what can go wrong). If you continue to have difficulties, then I would recommend contacting us directly at http://www.ni.com/ask.

Jeremiah Cox
Applications Engineer
National Instruments
http://www.ni.com/ask

[Gennady]

Jeremiah, Thanks for ideas. I acctualy started to investigate this problem and found some answers to your qwestions. First, of course this is project related phenomena. For small projects, like CVI samples, I had never seen anything like that. For my project everything was OK when I started it. But than the code (or data) gets bigger (this is only one unusial thing with my project) at some critical point CVI debugger is not functional anymore! So this is perhaps memory related problem. I reduced the sizes of major arrays by 10 whithout changing anything else and debugger returned to the normal. If this is a case what is the right size of the project (code and data) for debugger and may CVI's debugger issue a message "Exeed maximum available memory"?

[Gennady]

Jeremiah, Thanks for ideas. I acctualy started to investigate this problem and found some answers to your qwestions. First, of course this is project related phenomena. For small projects, like CVI samples, I had never seen anything like that. For my project everything was OK when I started it. But than the code (and data) gets bigger (this is only one unusial thing with my project) at some critical point CVI debugger is not functional anymore! So this is perhaps memory related problem. I reduced the sizes of major arrays by 10 whithout changing anything else and debugger returned to the normal. If this is a case what is the right size of the project (code and data) for debugger and may CVI's debugger issue a message "Exeed maximum available memory"?