Indexoutofrangeexception in vb2010 after installing windows 8.1

Question

I created an app in vb 2010, which works fine on a windows Vista laptop. I have bought a new laptop with Window 8.1 and wanted to use the app on that machine. I installed VB 2010 and imported the source-code. The app works ok until closing. Then I get the
indexoutofrange exception. Because i thought that VB2010 could have issues with Windows 8.1. I installed Visual Studio Express 2013 without succes. I get the same exception. 
While debugging the app runs ok with <F5> until closing. With a break just before me.close() it runs ok until the break. Stepping into me.close() results in hanging of the app with no error.
What should i do to solve this problem. 

Answer 1

I can't display any code or line, because the exception doesn't give any line number. It is located in the autogenerated code. The exception appears during closing. It makes no difference how the program is closed. 
Accepting or cancelling the exception box seemed at first to repeat endlessly  the same exception. Closer looking showed that the exception was thrown multiple times with one character changing every three times (0,0,0,1,1,1,2,2,2,etc) and visible data
disappearing  in the datagridview. After discovering that fact it became clear that all 3 datagridviews in the app cause the problem. It seems to me now that the method I used to display linked data in a datagridview has caused the exception. In fact
I changed numeric values for text. This results during closing in several index null errors. 
For some reason this causes in Win 8.1 (and/or Framework?) exception errors, where it does not in Vista and Win 7. Because the problem appeared for the first time when I used Win 8.1 I assumed that it was caused by the difference between the operating systems.
Which in a way it is. 
Though the solution was not given in the replies. The mails were helpful, because no one mentioned these differences between the operating systems. Which made me start to look for problems in the program. The problem was solved this way. But I am still curious,
why there where no errors in Vista and Win 7. 
For Mr Monkeyboy:
I installed VSE 2013, because i thought that maybe the combination VB 2010 en Windows 8.1 caused my problem. In VSE 2013 the error still existed. Therefore 'installing without succes'. My app still threw the same exception errors. 
You say the problem was solved. Which of course doesn't explain what the problem was or how it was solved. Therefore how would anybody be able to know what the problem was in order to advise why it did not occur in Vista or Win 7?
You say in a way it is a problem with Win 8.1. I should think the problem would be you wrote a program that was not compatable with Win 8.1 rather than there was a problem with Win 8.1. New OS's usually have more requirements and may be stricter in some
areas, especially with regard to security, than older OS's. Which is why applications which worked on older OS's may have to be altered to work on newere OS's. Especially if the programmer was not adhering to programming practices for MS OS's in general when
a program was initially created.
I only have Win 7 and am not a developer so I am not knowledgable or experienced with those issues though they occur often enough regarding questions about programs working on one OS but not another in these forums.
La vida loca