We are running Windows 2000 workstations and the strange thing is, it only occurs on 2 of the 5 workstations where we run the application. It only happens for those users under a single scenario. I can not reproduce the error on my development workstation and therefore am unable to debug. I started peppering the code with writes to the log to try to narrow down where the error is occuring. It is happening in some database access routines (though I have not completely narrowed down the cause). We use ADO for our data access.

Well, assuming it is a stop error you are getting this is the 'documented' reason for it according to Microsoft. If you can generate a crash dump file and post it here I can analyze it for you. That will, hopefully, reveal a little more.

>> Do you know how I might create a crash dump file?
This this is a stop error (BSOD) you should find a minidump in the c:\windows\minidumps folder. If it's not a BSOD then you can try using DebugDiag to generate a memory dump.

We are NOT seeing any dump files, nor any event logged. The workstation is configured to write a small memory dump. It is supposed to write to %systemroot%\minidump. There is no minidump directory. We are going to try to get a complete system dump.

>>>> This is a stop error, right? If so this is what it means...
From my experience the error must not be necessarily a stop error. It could be any wrong exception call e. g. by memory corruption. The instance that it happened only on certain machines possibly can be explained that these machines/users were using different libraries (dlls) e. g. have a different access or sql server driver. Or it could happen because these machines/users have more/less/different processes running than others so that a programming error leads to an exception while it doesn't on other machines.

I remember a similar problem with ADO maybe a year ago. The problem was that the buffer passed to ADO to take the result set was a local buffer which was freed after calling the ADO. Then crashing depended on whether the memory was used for other purposes in the meantime while ADO asynchronously wrote data to the wrong buffer address. If you could narrow the issue to ADO I would thoroughly analyze each ADO call whether the passed buffers actually were sized correctly and were pointing to heap memory which wasn't freed before ADO returned the result set.

Often, when implementing a feature, you won't know how certain events should be handled at the point where they occur and you'd rather defer to the user of your function or class. For example, a XML parser will extract a tag from the source code, wh…

Written by John Humphreys
C++ Threading and the POSIX Library
This article will cover the basic information that you need to know in order to make use of the POSIX threading library available for C and C++ on UNIX and most Linux systems.
[s…

The viewer will learn how to pass data into a function in C++. This is one step further in using functions. Instead of only printing text onto the console, the function will be able to perform calculations with argumentents given by the user.

The viewer will be introduced to the member functions push_back and pop_back of the vector class. The video will teach the difference between the two as well as how to use each one along with its functionality.