By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,180 Members | 1,016 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,180 IT Pros & Developers. It's quick & easy.

vb.net problem in Windows2003 sp1

P: n/a
Please help....
My vb.net 2003 application running as service fails on Windows 2003 SP1 with
error "The exception generated was c0000005 at address 7C8224B2
(ntdll!ExpInterlockedPopEntrySListFault)". It just crashes with no other
expanations.
It works fine on Win2003 and WinXP SP2. What is changed in
Win2003 and what does this error mean?
My service uses dotnet framework 1.1, system.runtime.remoting, SQL 2000.
Does anyone know what has changed in Win2003 sp1?

Nov 23 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
My service also uses .net sockets.....thanks

"Sukhi R" wrote:
Please help....
My vb.net 2003 application running as service fails on Windows 2003 SP1 with
error "The exception generated was c0000005 at address 7C8224B2
(ntdll!ExpInterlockedPopEntrySListFault)". It just crashes with no other
expanations.
It works fine on Win2003 and WinXP SP2. What is changed in
Win2003 and what does this error mean?
My service uses dotnet framework 1.1, system.runtime.remoting, SQL 2000.
Does anyone know what has changed in Win2003 sp1?

Nov 23 '05 #2

P: n/a
Hi, Sukhi!

C0000005 is an out-of-bounds memory exception. It means that the method was expecting a valid pointer to reference, but instead got something else outside the bounds of the memory space.

What does this mean in the VB world? One possible meaning would be if you were calling an external API (using Declare, for example) and passed in data by value instead of by reference, when a reference was called for, and the target API suddenly began checking the value and thought it was a reference (whereas previously it was ignoring it). Or, it may mean that some intermediate layer of (non-VB) code you were using had a buffer overrun which wasn't revealed until the service pack came out (and is not guarded against). I'd suspect the latter, though without seeing your code this would be just a guess.

Calvin Hsia has a blog entry which discusses this type of failure further. You can find it at http://blogs.msdn.com/calvin_hsia/ar...30/170344.aspx.

Hope this is helpful,
--Matt Gertz--*
VB Compiler Dev Lead

-----Original Message-----
From: SukhiR
Posted At: Thursday, November 17, 2005 10:25 AM
Posted To: microsoft.public.dotnet.languages.vb
Conversation: vb.net problem in Windows2003 sp1
Subject: RE: vb.net problem in Windows2003 sp1
My service also uses .net sockets.....thanks

"Sukhi R" wrote:
Please help....
My vb.net 2003 application running as service fails on Windows 2003 SP1 with
error "The exception generated was c0000005 at address 7C8224B2
(ntdll!ExpInterlockedPopEntrySListFault)". It just crashes with no other
expanations.
It works fine on Win2003 and WinXP SP2. What is changed in
Win2003 and what does this error mean?
My service uses dotnet framework 1.1, system.runtime.remoting, SQL 2000.
Does anyone know what has changed in Win2003 sp1?

Nov 23 '05 #3

P: n/a
Hi Mathew,
Thank you for your help. This information was very usefull, but I had
different problem. My program uses third party dll called commbase and I
found newer version of it. My problem is gone after installing newer version.
Thanks again.

Sukhi

"Ma***********@feedback.microsoft.com" wrote:
Hi, Sukhi!

C0000005 is an out-of-bounds memory exception. It means that the method was expecting a valid pointer to reference, but instead got something else outside the bounds of the memory space.

What does this mean in the VB world? One possible meaning would be if you were calling an external API (using Declare, for example) and passed in data by value instead of by reference, when a reference was called for, and the target API suddenly began checking the value and thought it was a reference (whereas previously it was ignoring it). Or, it may mean that some intermediate layer of (non-VB) code you were using had a buffer overrun which wasn't revealed until the service pack came out (and is not guarded against). I'd suspect the latter, though without seeing your code this would be just a guess.

Calvin Hsia has a blog entry which discusses this type of failure further. You can find it at http://blogs.msdn.com/calvin_hsia/ar...30/170344.aspx.

Hope this is helpful,
--Matt Gertz--*
VB Compiler Dev Lead

-----Original Message-----
From: SukhiR
Posted At: Thursday, November 17, 2005 10:25 AM
Posted To: microsoft.public.dotnet.languages.vb
Conversation: vb.net problem in Windows2003 sp1
Subject: RE: vb.net problem in Windows2003 sp1
My service also uses .net sockets.....thanks

"Sukhi R" wrote:
Please help....
My vb.net 2003 application running as service fails on Windows 2003 SP1 with
error "The exception generated was c0000005 at address 7C8224B2
(ntdll!ExpInterlockedPopEntrySListFault)". It just crashes with no other
expanations.
It works fine on Win2003 and WinXP SP2. What is changed in
Win2003 and what does this error mean?
My service uses dotnet framework 1.1, system.runtime.remoting, SQL 2000.
Does anyone know what has changed in Win2003 sp1?

Nov 23 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.