nt4 memory issues

I have written a VB.NET application and have been running it and testing it in windows 2000. I recently tried it in windows NT and it runs for a while but then all of a sudden it completely dissapears. I think this is a memory issue as i changed some of the code around and there is no particuar piece of code that it crashes on. While running it i have had task manager open and when the app reaches around the 15,000 K memory usage mark the program dissapears. This is perculiar because i have tried opening ms word and making it go over 15,000 K and it was ok.
any help would be appreciated.

-adrian
aids_at_workAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LichienCommented:
Am not too sure about VB.NET application running on NT4... Will check whether this is indeed possible...

By the way..did you check your event logs... if anything may have been log?
0
aids_at_workAuthor Commented:
here is the event log:

The description for Event ID ( 4104 ) in Source ( Transaction Server ) could not be found. It contains the following insertion string(s):      (IID: {208B3651-2B48-11CF-BE10-00AA00A2FA25}) (Method: 3)  (Microsoft Transaction Server Internals Information: File: i:\viperqfe\src\resdisp\mtxdm\cholder.cpp, Line: 153) (Exception: C0000005) (Address: 0x77f6ce4c)
ntdll!_RtlpWaitForCriticalSection@4 + 0x95
ntdll!_RtlEnterCriticalSection@4 + 0x46
SQLWNTM + 0x52A1D
SQLWNTM + 0x52201
SQLWNTM + 0x50ECB
SQLWNTM + 0x50D05
SQLWNTM + 0x50CA9
SQLWNTM + 0x367D0
SQLWNTM + 0x4B327
SQLWNTM + 0x4680E
SQLWNTM + 0x39E8F
SQLWNTM + 0x36523
SQLWNTM!sqlcch + 0x80
c2gup14!GupConnection::connectLogon(void) + 0x196
0
aids_at_workAuthor Commented:
I installed the latest odbc driver and that seemed to fix the problem
0
ee_ai_constructCommented:
PAQed, with points refunded (125)

ee_ai_construct - (re-order part number #xm34)
Community Support Moderator
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Programming

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.