The Windows error, as opposed to Python traceback, is a crash. My machine is probably too fast even if it did have XP.

Serhiy: 'wish' is not a normal Windows command.

https://social.msdn.microsoft.com/Forums/en-US/2a65c068-4bf7-42ff-94b1-283105d5548d/fatal-errorexception-error-c0000005?forum=visualfoxprogeneral

says C0000005 is an
"Exception Error that occurs when a process (application, driver, etc.) tries to execute a processor command that references memory outside the space allocated to that process by the Operating System. 

There are many possible causes ranging from corrupt data tables, to a bad network connection, ActiveX controls, or  Printer or Video driver errors. WIthout knowing what type of error you are seeing, it is impossible to guess what the cause may be."

It can result either from corrupt system files on a particular machine or a bug in a particular application or a particular use of an application. Searching 'Windows c0000005 error tcl tk' lead to a stackoverflow answer reporting that running Tk.mainloop in a non-main thread without a command queue could lead to this error.

tkinter.filedialog.askopenfilename ends up running tcl command "tk_getSaveFile".  See tkinter.commondialog.  Searching "Windows c0000005 tk_getOpenFile" leads to

http://comp.lang.tcl.narkive.com/miTBmbe1/crash-in-tk-getopenfile
which ends on 2014-11-14 with "fixed in the trunk*. Even in the released 8.6.3 you should see the problem only if you are on a Windows version prior to Vista AND pass the same string to -typevariable and -filetypes." *8.6.4, delivered with 3.5.

So until there is a problem with tk 8.6.4+ on Vista+ on more than one machine, I am going to assume that you either have a bad file on your machine or that you ran into this known now-fixed tk bug.  Hence closing.