02-11-2015 03:27 AM
Hello John,
You have to write in Windbg the command .dump /ma <path\file.dmp> . This will create the file you specify. File attached.
The file that is created is fairly big so I think you can't attach it here. You can upload it to ftp://ftp.ni.com/incoming. If you put it into a zip archive the file size should be reduced about 3 times.
Constantin
02-11-2015 05:49 PM
Constantin:
OK, I think I have uploaded it to the ftp site. It's called crashdumpFeb11,2015 at 1445 hrs.zip. Hopefully I did it correctly but I was sorely confused with the ftp site. Hopefully it's useful. I couldn't figure out how to look at it but possibly with a hex viewer program? I'll download one and see if I can view the file.
Thanks,
John
02-13-2015 10:14 AM
Hello John,
The dump file can be opened with Windbg(File->Open Crash Dump...)
Unfortunately I can't get much information from the crash dump. It says an exception breakpoint occurred while calling some functions from ntdll.dll. But I can't see how these functions get called, the stack seems to be corrupt at crash time.
Constantin.
02-13-2015 10:56 AM
Constantin:
Oh, my, that's unfortunate. But maybe there is info from the ntdll.dll error. I did a search and found some info about that. Possibly or probably my Win7 is corrupted. Possibly I can fix it up. I did have a problem many months ago when Win7 was updating and my wife closed down my ASUS PC before it all got updated. It has seemed to be ok as far as I can tell from other work I have done on my PC but the corruption may be showing up now with CVI. Your suggestion about reloading Win7 is probably the thing to do but I don't have the Win7 CD and also, if I had the Win7 CD I would hate to go through the process/trouble to reload it.
John
02-13-2015 11:50 PM
Constantin:
Got CVI running ok. I had to restore my ASUS' original state and reinstall CVI. So far so good. I can browse and load a project, compile and run it. Also I can SAVEAS to a new prj name. So all seems ok now.
Sorry for all the trouble and thanks again for all your help. Reinstalling Win7 was the trick, suggested by your info about the ntdll.dll file problem and your suggestion to reinstall Win7.
John