ntdll exception
Locked
 
|
Hello, all, My customer has run into some vwnt application errors that sometimes
produce Dr. Watsons that look something like this: The application vwnt.exe generated an application error.
The error occurred on 11/12/2010 @ 08:41:00.703. The exception generated
was 80000003 at address 7C901230 (ntdll! DbgBreakPoint). There are several events in the Event Viewer that point to
ntdll.dll. As far as I can tell, there is no memory growth occurring. I realize it might be a stretch to hope for a solution on
this forum, because it looks like some generic memory management problem.
However, y’all are a smart bunch of folks and someone may have run across
this problem and found a way to resolve it. The only common thread I can
see is that screens with DataSets were the last screens visited before the
crashes. Any thoughts or ideas would be appreciated! Becky
Cooper
([hidden email]) Deputy Director of Equipment Control Products, DARBU/PCG 1100 West Campbell Road Cell: (972-369-6844) _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
|
|
Which version of VisualWorks is your customer running?
On 12/15/2010 3:19 PM, Cooper, Becky wrote: > Hello, all, > > My customer has run into some vwnt application errors that sometimes > produce Dr. Watsons that look something like this: > > The application vwnt.exe generated an application error. The error > occurred on 11/12/2010 @ 08:41:00.703. The exception generated was > 80000003 at address 7C901230 (ntdll! DbgBreakPoint). > > There are several events in the Event Viewer that point to ntdll.dll. As > far as I can tell, there is no memory growth occurring. > > I realize it might be a stretch to hope for a solution on this forum, > because it looks like some generic memory management problem. However, > y’all are a smart bunch of folks and someone may have run across this > problem and found a way to resolve it. The only common thread I can see > is that screens with DataSets were the last screens visited before the > crashes. > > Any thoughts or ideas would be appreciated! > > *Becky Cooper*([hidden email] > <mailto:[hidden email]>) > > Deputy Director of Equipment Control Products, DARBU/PCG > > Rudolph Technologies, Inc. <http://www.rudolphtech.com/> > > 1100 West Campbell Road > Richardson, TX 75080 > Ph:(469) 624-4684 > > Cell: (972-369-6844) > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
|
|
I forgot to mention that; my apologies. They are running 7.4.
-----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Andres Valloud Sent: Wednesday, December 15, 2010 6:00 PM To: [hidden email] Subject: Re: [vwnc] ntdll exception Which version of VisualWorks is your customer running? On 12/15/2010 3:19 PM, Cooper, Becky wrote: > Hello, all, > > My customer has run into some vwnt application errors that sometimes > produce Dr. Watsons that look something like this: > > The application vwnt.exe generated an application error. The error > occurred on 11/12/2010 @ 08:41:00.703. The exception generated was > 80000003 at address 7C901230 (ntdll! DbgBreakPoint). > > There are several events in the Event Viewer that point to ntdll.dll. > far as I can tell, there is no memory growth occurring. > > I realize it might be a stretch to hope for a solution on this forum, > because it looks like some generic memory management problem. However, > y'all are a smart bunch of folks and someone may have run across this > problem and found a way to resolve it. The only common thread I can see > is that screens with DataSets were the last screens visited before the > crashes. > > Any thoughts or ideas would be appreciated! > > *Becky Cooper*([hidden email] > <mailto:[hidden email]>) > > Deputy Director of Equipment Control Products, DARBU/PCG > > Rudolph Technologies, Inc. <http://www.rudolphtech.com/> > > 1100 West Campbell Road > Richardson, TX 75080 > Ph:(469) 624-4684 > > Cell: (972-369-6844) > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
|
|
Hmmm... I'd suggest upgrading the VMs. There are numerous things we
have corrected since then that I can see could be behind the issue you're having. Of course it's hard to tell (guess correctly) without more information, but perhaps a good first step is to remove the known problems that are removable. On 12/16/2010 7:11 AM, Cooper, Becky wrote: > I forgot to mention that; my apologies. They are running 7.4. > > -----Original Message----- > From: [hidden email] [mailto:[hidden email]] On > Behalf Of Andres Valloud > Sent: Wednesday, December 15, 2010 6:00 PM > To: [hidden email] > Subject: Re: [vwnc] ntdll exception > > Which version of VisualWorks is your customer running? > > On 12/15/2010 3:19 PM, Cooper, Becky wrote: >> Hello, all, >> >> My customer has run into some vwnt application errors that sometimes >> produce Dr. Watsons that look something like this: >> >> The application vwnt.exe generated an application error. The error >> occurred on 11/12/2010 @ 08:41:00.703. The exception generated was >> 80000003 at address 7C901230 (ntdll! DbgBreakPoint). >> >> There are several events in the Event Viewer that point to ntdll.dll. > As >> far as I can tell, there is no memory growth occurring. >> >> I realize it might be a stretch to hope for a solution on this forum, >> because it looks like some generic memory management problem. However, >> y'all are a smart bunch of folks and someone may have run across this >> problem and found a way to resolve it. The only common thread I can > see >> is that screens with DataSets were the last screens visited before the >> crashes. >> >> Any thoughts or ideas would be appreciated! >> >> *Becky Cooper*([hidden email] >> <mailto:[hidden email]>) >> >> Deputy Director of Equipment Control Products, DARBU/PCG >> >> Rudolph Technologies, Inc.<http://www.rudolphtech.com/> >> >> 1100 West Campbell Road >> Richardson, TX 75080 >> Ph:(469) 624-4684 >> >> Cell: (972-369-6844) >> >> >> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
|
|
Thanks, Andres. I've been Skyping with James Savidge about this very
thing. I will see if the customer is willing to try this on their lab tools. I don't think their customer will want to try it on a production tool without some evidence that 7.7.x fixes a ntdll.dll problem, though! In other words, if there's a known problem that I can articulate to them, they would be more willing to try it. Thanks again! -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Andres Valloud Sent: Thursday, December 16, 2010 1:52 PM To: [hidden email] Subject: Re: [vwnc] ntdll exception Hmmm... I'd suggest upgrading the VMs. There are numerous things we have corrected since then that I can see could be behind the issue you're having. Of course it's hard to tell (guess correctly) without more information, but perhaps a good first step is to remove the known problems that are removable. On 12/16/2010 7:11 AM, Cooper, Becky wrote: > I forgot to mention that; my apologies. They are running 7.4. > > -----Original Message----- > From: [hidden email] [mailto:[hidden email]] On > Behalf Of Andres Valloud > Sent: Wednesday, December 15, 2010 6:00 PM > To: [hidden email] > Subject: Re: [vwnc] ntdll exception > > Which version of VisualWorks is your customer running? > > On 12/15/2010 3:19 PM, Cooper, Becky wrote: >> Hello, all, >> >> My customer has run into some vwnt application errors that sometimes >> produce Dr. Watsons that look something like this: >> >> The application vwnt.exe generated an application error. The error >> occurred on 11/12/2010 @ 08:41:00.703. The exception generated was >> 80000003 at address 7C901230 (ntdll! DbgBreakPoint). >> >> There are several events in the Event Viewer that point to ntdll.dll. > As >> far as I can tell, there is no memory growth occurring. >> >> I realize it might be a stretch to hope for a solution on this forum, >> because it looks like some generic memory management problem. >> y'all are a smart bunch of folks and someone may have run across this >> problem and found a way to resolve it. The only common thread I can > see >> is that screens with DataSets were the last screens visited before the >> crashes. >> >> Any thoughts or ideas would be appreciated! >> >> *Becky Cooper*([hidden email] >> <mailto:[hidden email]>) >> >> Deputy Director of Equipment Control Products, DARBU/PCG >> >> Rudolph Technologies, Inc.<http://www.rudolphtech.com/> >> >> 1100 West Campbell Road >> Richardson, TX 75080 >> Ph:(469) 624-4684 >> >> Cell: (972-369-6844) >> >> >> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
«
Return to VisualWorks
|
1 view|%1 views
| Free forum by Nabble | Edit this page |