Access violation occurs intermittently (msvcr71.dll)

Any help regarding this problem is appreciated.
We created an ODBC system data source to communicated to one of our products. Here the purpose is to transfer data from ProductA to ProductB when certain criteria matches. We start the service from control panel services list. The product uses MFC library "CRecordset"
Some times access violation occurs and transfer stops.
Here is the dll information..,
C:\ORACLE\PRODUCT\10.2.0\DB_1\BIN\MSVCR71.DLL 7.10.3052.4 348160 June 25, 2005 03:22:00 Microsoft® C Runtime Library Microsoft® Visual Studio .NET 7.10.3052.4
Error is: Exception code: C0000005 ACCESS_VIOLATION
Fault address: 7C352089 01:00011089 d:\oracle\product\10.2.0\db_1\bin\MSVCR71.dll
Registers:
EAX:0528A788
EBX:0000052B
ECX:0000052B
EDX:00000007
ESI:00000000
EDI:00D75938
CS:EIP:001B:7C352089
SS:ESP:0023:034B1EF8 EBP:034B1F04
DS:0023 ES:0023 FS:003B GS:0000
Flags:00210246
Call stack:
Address Frame
7C352089 00000000 isalnum+35
065CE75F 00000000 SQLTablesW+43C0F
065CE98E 00000000 SQLTablesW+43E3E
06588312 00000000 SQLPrepareW+16A
06588250 00000000 SQLPrepareW+A8
488B3E95 00000000 SQLAllocHandleStd+3C5
488B41AF 00000000 SQLPrepare+77
4C631DB0 00000000 Ordinal9+1DB0
4C6367A5 00000000 Ordinal9+67A5
4C63586A 00000000 Ordinal9+586A
4C637E70 00000000 SQLPrepare+6A
488B3E95 00000000 SQLAllocHandleStd+3C5
488B41AF 00000000 SQLPrepare+77
7828B301 00000000 Ordinal5188+38
63205443 00000000 STANDA_S+4767

Thanks a lot for the information.
Do you have any ideas regarding if Oracle has already provided fix for this issue ? I am not sure..., I have been trying installing patches as well. Following are the Oracle versions tried so far 10.2.0.1, 10.2.0.2, 10.2.0.3 (P3 Patch). This highly intermittent issue is reproduced on these.
Please advise.

Similar Messages

Sql2005Sp4 x64 (9.0.5000) SqlDump (Access violation) occurs every second

i am getting around 10 dumps a second. The dump analysis is below. It looks like Service Broker may be involved. We do use service broker so that is a possibility.
Can anyone read this and make more sense out of it? Is there another command i can use that will produce more useful information?
this is SQL2005 so calling MS is probably not a good option.
(edit) it certainly looks like a background task (Service Broker)
(edit2) if it matters this is Sql2005 clustered on Win2008R2
CSession @0x00000003305B22B0
m_spid = 156 m_cRef = 12 m_rgcRefType[0] = 1
m_pstackBhfPool = 0x0000000000000000 m_dwLoginFlags = 0x0000 m_fBackground = -1
In other stack dumps i have found, that value is a 0. -1 apparently indicates 'true'.
0:000> !analyze -v
* Exception Analysis *
*** WARNING: Unable to verify checksum for mscorlib.ni.dll
FAULTING_IP:
sqlservr!GenGetFromObject+91
00000000`023fa991 488b4500 mov rax,qword ptr [rbp]
EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00000000023fa991 (sqlservr!GenGetFromObject+0x0000000000000091)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
CONTEXT: 0000000000000000 -- (.cxr 0x0;r)
rax=0000000000000000 rbx=0000000000000000 rcx=000000002f347580
rdx=0000000000000000 rsi=0000000000000064 rdi=0000000000002e1c
rip=0000000076e212fa rsp=000000003a0ea2d8 rbp=0000000000000001
r8=0000000000000001 r9=000000002f347580 r10=0000000000000000
r11=000000003a0e93a8 r12=000000003a0ea308 r13=000000003a0ec8c0
r14=0000000000001d4c r15=000000012f717a83
iopl=0 nv up ei ng nz na po cy
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000287
ntdll!NtWaitForSingleObject+0xa:
00000000`76e212fa c3 ret
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
PROCESS_NAME: sqlservr.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
READ_ADDRESS: 0000000000000000
FOLLOWUP_IP:
sqlservr!GenGetFromObject+91
00000000`023fa991 488b4500 mov rax,qword ptr [rbp]
NTGLOBALFLAG: 0
APP: sqlservr.exe
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
MANAGED_STACK: !dumpstack -EE
No export dumpstack found
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 00000000023fbe22 to 00000000023fa991
STACK_TEXT:
00000000`3a0ecfe0 00000000`023fbe22 : 00000002`6ceb8050 00000000`00000000 00000007`c9768150 00000008`9c6608c0 : sqlservr!GenGetFromObject+0x91
00000000`3a0ed050 00000000`0242450d : 00000007`c9768110 00000002`50b4beb0 ffffffff`fffffffe 00000000`01618b9b : sqlservr!XRelGenGet+0x22
00000000`3a0ed0a0 00000000`02425231 : 00000002`50b4bfb0 00000008`9c6608c0 00000002`6ceb8050 00000000`024118b1 : sqlservr!CStmtRecvMsg::GenGetCGLockWhereConvGroup+0x15d
00000000`3a0ed1b0 00000000`029744ec : 00000007`9b3c69f0 00000007`9b3c69f0 00000002`a3858140 00000000`01715375 : sqlservr!CStmtRecvMsg::GenMessageGet+0xe1
00000000`3a0ed240 00000000`0299ca63 : 00000002`569d33b0 00000002`f324da00 00000002`f324da00 00000002`68f1f1e0 : sqlservr!CStmtRecvMsg::BuildBoundQuery+0x19c
00000000`3a0ed310 00000000`0152f239 : 00000007`9b3c6320 00000000`00337588 00000002`6ceb8050 00000000`01644e24 : sqlservr!CStmtRecvMsg::FBind+0x73
00000000`3a0ed380 00000000`01565dbe : 00000007`6f16a5a0 00000006`a11f09c0 00000000`0124c400 00000002`0000111b : sqlservr!CProchdr::FNormalizeStep+0x389
00000000`3a0edae0 00000000`0176d7e1 : 00000000`00000000 00000000`015b9121 00000000`3a0ee380 ffffffff`fffffffe : sqlservr!CSQLSource::FCompile+0x60e
00000000`3a0edd70 00000000`015b97eb : 00000000`3a0ee380 00000002`f324da00 00000002`f324da00 00000000`3a0ee380 : sqlservr!CSQLSource::FCompWrapper+0x121
00000000`3a0ede30 00000000`015cc4c1 : 00000000`00000000 00000008`61052b00 00000003`00000000 00000000`0000011b : sqlservr!CSQLSource::Transform+0x35b
00000000`3a0edef0 00000000`02b9829c : 00000000`00000000 00000008`610521c0 00000000`80d7a960 00000000`00000000 : sqlservr!CSQLSource::Execute+0x291
00000000`3a0ee040 00000000`02bad4e8 : 00000008`61052080 00000000`00000070 00000008`61052570 00000000`01627718 : sqlservr!CSbActivationTask::Invoke+0x44c
00000000`3a0ee970 00000000`02bad7d9 : 00000000`00000000 00000000`0aff8080 00000000`0aff4768 00000008`610521c0 : sqlservr!CSbTask::TaskStart+0x278
00000000`3a0efaa0 00000000`015c483e : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`0aff4750 : sqlservr!CSbTask::BeginTaskStart+0x9
00000000`3a0efad0 00000000`015c4ad9 : 00000000`00000000 00000000`0aff8080 00000000`0aff4718 00000000`0aff8080 : sqlservr!SOS_Task::Param::Execute+0xee
00000000`3a0efbe0 00000000`015bb254 : 00000000`0aff4718 00000000`00000000 00000000`0aff8080 00000008`610521c0 : sqlservr!SOS_Scheduler::RunTask+0xc9
00000000`3a0efc70 00000000`014d4687 : 00000008`610521c0 00000000`00338270 000007ff`fff314a8 00000000`0aff8080 : sqlservr!SOS_Scheduler::ProcessTasks+0xb4
00000000`3a0efce0 00000000`017be7b9 : 00000008`610521c0 00000000`0aff8080 00000000`00000000 00000000`00000788 : sqlservr!SchedulerManager::WorkerEntryPoint+0xe7
00000000`3a0efd80 00000000`017be585 : 00000000`3a0efdf0 00000000`00000200 00000000`00000000 00000000`3a0efda0 : sqlservr!SystemThread::RunWorker+0x59
00000000`3a0efdc0 00000000`017eade8 : 00000000`00000000 00000000`00000000 00000000`003b6b00 00000000`00000000 : sqlservr!SystemThreadDispatcher::ProcessWorker+0xb5
00000000`3a0efe60 00000000`746e37d7 : 000007ff`fff314a8 00000000`00000000 00000000`00000000 00000000`00000000 : sqlservr!SchedulerManager::ThreadEntryPoint+0x128
00000000`3a0eff00 00000000`746e3894 : 00000000`747995c0 00000000`04397f60 00000000`00000000 00000000`00000000 : msvcr80!endthreadex+0x47
00000000`3a0eff30 00000000`76cc59ed : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msvcr80!endthreadex+0x104
00000000`3a0eff60 00000000`76dfc541 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
00000000`3a0eff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: sqlservr!GenGetFromObject+91
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: sqlservr
IMAGE_NAME: sqlservr.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d02b641
FAILURE_BUCKET_ID: WRONG_SYMBOLS_c0000005_sqlservr.exe!GenGetFromObject
BUCKET_ID: X64_APPLICATION_FAULT_WRONG_SYMBOLS_sqlservr!GenGetFromObject+91
ANALYSIS_SOURCE: UM
FAILURE_ID_HASH_STRING: um:wrong_symbols_c0000005_sqlservr.exe!gengetfromobject
FAILURE_ID_HASH: {f8a83b33-1e6a-af53-1838-793e524bdc68}
-- dan http://dnhlmssql.blogspot.com/

Hi,
Check the error message in the SQL Server Error Log. The dump file points that the wrong symbol is sqlservr!GenGetFromObject.
Verify if symbols are loaded for SQL Server by using the debugger command lmvm.
lmvm sqlservr!GenGetFromObject
Please check the following articles for more information:
http://mssqlwiki.com/2012/10/16/sql-server-exception_access_violation-and-sql-server-assertion/
http://support.microsoft.com/kb/315263
Hope it helps.
Tracy Cai
TechNet Community Support

Access Violation in module RunPci.dll

Getting error message of "Access violation at address 0146139C in module 'RunPci.dll'. Read of address 00000000."
This happens when trying to load/run the "Utility" setup on the MSI Utility&Drivers CD.
Fuzzy Logic III not loading and bootup/bootdown takes 10 minutes. Mouse works but won't Drag&Drop, kb works. Device Manager is empty, all COM and OLE functions fail. Trying to reload Drivers and Utilities, but access violation in RunPci.dll seems to be what prevents this.
All problems started when parallel scanner cable mistakenly plugged into serial port. System is KT3 Ultra2 running W2kPro, no firewalls or A-V software, no Internet connection.

Can you check the lenght of the FORMSxx_PATH and please tel;l me if:
1) This happens in a simple (no code) form.
2)Details of o/s and Forms versions numbers
Thanks
Grant Ronald
Forms Product Management
null

ORACLIENT8.DLL Access Violation

Hi All
I am facing a severe problem with ORACLIENT8.DLL driver , sometimes when my database application is running, suddendly it crashes giving error as : Access violation occurred in ORACLIENT8.DLL.I dont know at what instance this error occurs and when I try to debug, I can see something as OCI, please help me to solve this problem, its very crucial for me.
Thanking in advance
Sudhikg

If I had to take a wild guess, I'd suggest that you look to see whether your application is failing to catch the proper error code for a connection being dropped (from when you're shutting down the database). If the application continues to use handles after it has been notified that they aren't valid any longer, you're likely to run into this sort of problem.
Justin Hi Justin, thank you...the access violation happens in a SQLPrepare function (in my simulation)!!!
I can catch the exception so my application doesn4t crash, but the driver doesn4t work anymore in this application if I try to connect after up Oracle Server!!!!
I have a NEW (this morning)!!! I was using Oracle ODBC Driver 8.01.07.00 BUT when I installed the Oracle Client 9i with the Oracle ODBC Driver 9.00.11.00 the exception disappear, the SQLPrepare/SQLExecute returns error!!!!!I only changed the client version, I use ORACLE 8.0.5 Database!!!!
What do you think about this?
Fernando

Access violation in ORAGENERIC8.dll

We are seeing an intermittent access violation arising in ORAGENERIC8.dll when running a Window ISAPI web app from IIS. We're not familiar with this DLL but assume its part of the Oracle8i client. Our app seems perfectly healthy until this AV suddenly pops up--no pattern as to load, duration of processing, etc. Alert logs are clean. Any tips or thoughts? We're stumped!

Well, to start, you are aware that Win2003 and IE7 are very old and generally speaking probably no longer supported by Microsoft (unless you have extended support)? I bring this up not because I care that you are using software that is 10 years old, but because it is important to realize that at some point old software and new software simply won't play well together.
I would suggest you do the following:
1. Close ALL open browser and uninstall ALL installed JRE versions
2. If you are using Adobe Acrobat Reader to open your pdf files, uninstall it.
3. Ensure that you have installed all of the latest Windows (Microsoft) updates which are available. This can be determined by going to the Microsoft Update page. Here is the URL:
http://www.update.microsoft.com/microsoftupdate/v6/default.aspx
4. If any updates are installed, reboot regardless of the instructions provided by the update.
5. After rebooting, install the latest Adobe Acrobat Reader from the Adobe.com website.
6. Download JRE 1.6.0_37. You can download it from Oracle here:
http://www.oracle.com/technetwork/java/javase/downloads/jre6u37-downloads-1859589.html
Before attempting to install the JRE, close ALL open browser.
7. Now retest.
If the problem continues to reproduce, I would recommend you do some basic troubleshooting and ask youself some obvious questions. For example:
<blockquote><li>Does the problem reproduce on any other machine? If not, what is the difference between the machines?
<li>Did this ever reproduce before? If so, what has changed?
<li>Does this reproduce with any other application that accesses the pdf viewer? If not, what is unique about the way in which your app uses it?
<li>And so on....</blockquote>

OLE32.dll access violation

Not sure whether this is in the right place, but here goes:-
We have an ASP.NET application running on IIS 7 (Windows 2008 R2). It is a 32-bit application, and accesses SQL Server databases, sometimes directly, sometimes via Crystal Reports (CRVS2010). Occasionally, under seemingly random circumstances, w3wp.exe crashes
out with an access violation (0xc000005) in OLE32.dll (at offset 0x0003bc41). Any ideas as to how we can go about debugging this? (Also posted on the SAP Crystal Reports support site). As we haven't been able to determine the cause (the only symptom is that
users lose there session variables as w3wp.exe is recycled), we don't know if this is a Crystal Reports issue or something else.
If there is a more appropriate forum to post this, please suggest.

Hi JohnHorb,
Please post your thread on ASP.NET forum. It’s more related to ASP.NET.
http://forums.asp.net/.
Thank you for understanding.
Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Oracle 8.1.6 and 8.1.61 ODBC Driver Access Violation

Using Oracle ODBC for Windows to Oracle 8.1.6 database to get a list of the tables/views in the database.
The following code worked on 8.0.4, 8.0.5, and 8.1.5 databases and their respective ODBC Drivers. It gives me an access violation with 8.1.6.
The 8.1.61 ODBC Drivers was able to run the code once, but when I ran it a second time, it gave me an access violation.
The access violation occurs on the SQLFetch somewhere in the middle of the loop.
Here is the abbreviated sample code:
SQLAllocHandle(SQL_HANDLE_STMT, m_hdbc, &hCursor);
SQLSetStmtAttr (hCursor, SQL_ATTR_CURSOR_TYPE, (SQLPOINTER) SQL_CURSOR_STATIC, 0);
SQLTables(hCursor, NULL, 0, NULL, 0, NULL, 0, NULL, 0);
SQLBindCol(hCursor, 1, SQL_C_CHAR, sQualifier, sizeof(sQualifier), &indQualifier);
SQLBindCol(hCursor, 2, SQL_C_CHAR, sOwner, sizeof(sOwner), &indOwner);
SQLBindCol(hCursor, 3, SQL_C_CHAR, sTableName, sizeof(sTableName), &indTableName);
nReturn = SQL_SUCCESS;
while ((nReturn = SQLFetch(hCursor) ) == SQL_SUCCESS)
// after a 100 or so iterations, it crashes
nReturn = SQLFreeHandle(SQL_HANDLE_STMT, hCursor);
Please let me know if there are other ODBC drivers I could use, or if 8.1.62 will fix this.
null

I am using Visual Basic as front end to oracle 8 i as the
database.When I am connecting to database from Visual Basic
I am getting an error SQl Handle failed. When i am tring to
create a DSN through Microsoft Oracle ODBC Driver I am getting
an Error "The Oracle(tm) client and networking components were
not found. These componenets are supplied are supplied by Oracle
Corporation and are part of The Oracle Version (or greater)
client software installation. You will be unable to use this
Driver until these componenst have been installed" . Please give
me a solution to his as it is critical to me.
Please email the solution or tips at [email protected]

TestExec Access violation After Exit !!

Appreciate Any help I can get with this error !! Its driving me nuts !!
Firstly, on my development PC all the compiled applications function as expected, the problem lies with the target PC. I have set all applicable executable files (labview compiled projects) to run with admin rights, even though I am using a admin windows user account just to be sure. Both PC's are running windows 7 professional with the latest service packs and updates installed. No virus software is running on the target machine either.
Overview Description of my implementation:
Parent Application (labview compiled) - launches using the command prompt (system exec) a shortcut link to my TEST STAND operator interface which through the parent application allows the operator to select specific sequence test files. I setup system exec to run minimized and wait until completion.
Operator Interface - Runs the sequence file, all error handing comes back clean and once I quite the operator interface. Returns me back to the parent application from which it was called.
As the operator interface is closed down, (modified SIMPLE USER INTERFACE, which comes standard with TESTSTAND) I get a access violation error as the parent application regains focus. This error only occurs on my test PC, not on my development PC which would indicate there is probably nothing wrong with my logic but a mystery setting on the target PC.
Has anyone encountered a similar problem before, if so how did you fix it. ANy help is appreciated.
Best regards,
Sven

Sven.S wrote:
I have done further investiation.
1 - if I call the operator interface shortcut file directly through windows, the same access violation occurs !!
So you already tested the UI without the "parent application"?
Does it crash when it shuts down or if it loses the focus?
Does the unmodified Simple OI run without crash on this machine?
Does the crash occur if you call an example sequence (the crash might be connected to your custom sequence....)?
Do you use a default process model?
You should have posted this question in the TestStand forums.....
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Access Violation calling GetMethodId

Hi !
I'm getting an access violation on the jvm.dll when trying to execute a call from the native side. Well, in fact, the exception is raised when a try to get the method reference, by calling GetMethodId ().
The _javaClass variable is a class attribute and is correctly initialized since I'm being able to execute other calls.
Can somebody help me, please ?
This is the code:
void JavaBridge::pushJava (const char* str)
// To java push
// Get some variables
jmethodID javaMethod;
jstring javaString;
// Get the string
javaString = _env->NewStringUTF(str);
if (javaString == 0) {
JCB_ERROR ("JavaBridge::pushJava: Out of memory...");
return;
// Get the process() method
javaMethod = env->GetMethodID(javaClass, "process", "(Ljava/lang/String;)V");
if (javaMethod == 0) {
JCB_ERROR ("Can't find CppBridge's process() method.");
return;
// Call it
env->CallVoidMethod (javaObject, javaMethod, javaString);

I think your class reference is null.

Error Occuring While Processing Data With DIAdem 8.1Exception EAccessViolation in module ntdll.dll at 000111DE. Access violation at address 7C9111DE in module 'ntdll.dll". Read address 37363430

Hello,
We are having an issue running Diadem 8.1 on a new HP XW 9400 with Windows XP SP2. 3 errors have been occuring with frequent crashes, they are:
1) "1Exception EAccessViolation in module ntdll.dll at 000111DE. Access violation at address 7C9111DE in module 'ntdll.dll". Read address 37363430.
2) The instruction at "0x7c9111de" referenced memory at "0x352e302d". The memory could not be "read".
3) ---Error--- DIAdem
Error in Autosequence - processing in line: 74 (IARV_VAR_GET)
Runtime Error while executing command "Iarv2Txt$ := FR(T9,L1)"
Error type: ACCESS VIOLATION
Error address: 000101DE
Module name:ntdll.dll
We are using the same scripts and version 8.1 on a variety of Dell desktop computers (W2K and XP SP2) without any issue, looking for suggestions as this affects no other software on the HP XW 9400 other than DIAdem. Appreciate any suggestions.
Message Edited by swillh on 06-25-2007 08:55 AM

Christian,
I will answer your questions in the text below. Thanks for your help.
Hi swillh,
I also would like to help you.
Unfortunately, The reported access violation in the central Windows ntdll.dll is very unspecific.
May be the following questions will help you to provide me more info.
1. You mentioned that the aut's and - I think - also the accessed text file reside on a server.
Is there a stable network connection?
The server can sometimes be a little slow but the connection is good. This computer is using the same connection that the prior computer utilized without issue.
Are the files accessed by multiple clients simultaneously?
It is possible that more than one computer can be accessing the same file, but again, this has never been an issue. We are reading the files only, not writing to them.
The processing routines we are running have used for over 5 years without any issues until adding this computer.
Is the text file read by one client while another client is writing the same file?
No, files are "read only"
2. Have you already tested opening the file with the FileOpen command before calling FR?
Yes
Do you see any chance to convert the aut to a vbs file? This gives you more alternatives in accessing text files.
3. What do you mean with "processing ATD's with 30 or more channels of data"? Where is the relation between ATD files and data channels?
Processing Crash Dummy data with file sets low in channel count (15 channels) result in successful processing without any crashes or access errors. When processing dummies with more than 20 channels we sometimes encounter these issues. The higher channel count may be the only common factor I can find in these faults.
Steve
Message Edited by swillh on 07-09-2007 08:44 AM

0xC0000005 Access Violation in cvirte.dll (SetWindowsErrorMode?)

Hello,
We will occasionally see a crash with our CVI LabWindows based 2010 SP1 application, a 0xC0000005 Access Violation exception thrown from within cvirte.dll. The app is working primarily from a spawned thread when the crash occurs. I've been able to get it consistently on a Win7 x64 VirtualBox VM and have some data that may be of use if someone there would like to investigate.
When I track down the location of the instruction pointer (work below) it seems to be in the "SetWindowsErrorMode()" function (at least going by the exports in DependencyWalker):
1. The IP is 0x687B5F1C at the time of the crash.
2. The base module address for cvirte.dll is 0x68420000, so the IP is 0x395F1C bytes into the DLL.
3. Using DependencyWalker on cvirte.dll and sorting by entry point indicates that the IP is inside of "SetWindowsErrorMode()" at 0x003938D0, which comes before "MinimizeAllWindows()" at 0x003984B0.
Coincidentally, this crash happens in CVI 2013 F1 as well, the offset within "SetWindowsErrorMode()" is a bit different (0x264C past entry in 2010 SP1, 0x2D0C past entry in 2013), but locally the code looks the same in my VS2010 disassembler:
CVI2010 SP1
*Address *Code Bytes *Instruction
687B5F02 89 17 mov dword ptr [edi],edx
687B5F04 8B 48 5C mov ecx,dword ptr [eax+5Ch]
687B5F07 89 78 6C mov dword ptr [eax+6Ch],edi
687B5F0A 89 4F 04 mov dword ptr [edi+4],ecx
687B5F0D 89 58 5C mov dword ptr [eax+5Ch],ebx
687B5F10 C7 40 60 00 00 00 00 mov dword ptr [eax+60h],0
687B5F17 5E pop esi
687B5F18 85 DB test ebx,ebx
687B5F1A 74 09 je 687B5F25
687B5F1C 8B 13 mov edx,dword ptr [ebx] <--- CRASH
CVI2013 F1
*Address *Code Bytes *Instruction
687CA2B2 89 17 mov dword ptr [edi],edx
687CA2B4 8B 48 5C mov ecx,dword ptr [eax+5Ch]
687CA2B7 89 78 6C mov dword ptr [eax+6Ch],edi
687CA2BA 89 4F 04 mov dword ptr [edi+4],ecx
687CA2BD 89 58 5C mov dword ptr [eax+5Ch],ebx
687CA2C0 C7 40 60 00 00 00 00 mov dword ptr [eax+60h],0
687CA2C7 5E pop esi
687CA2C8 85 DB test ebx,ebx
687CA2CA 74 09 je 687CA2D5
687CA2CC 8B 13 mov edx,dword ptr [ebx] <--- CRASH
I have dump files (mini, or mini+heap) for both builds if it would help.
This bug seems semi-similar to the thread "Is InstallPopup not threadsafe?":
http://forums.ni.com/t5/LabWindows-CVI/Is-InstallPopup-not-threadsafe/m-p/716822/highlight/true#M359...
Just for posterity, I'll add the data for the 2013 build. IP is 0x687CA2CC, DLL Module address is 0x68420000-0x68A28000, so offset is 0x3AA2CC. "SetWindowsErrorMode()" enters at 0x003A75C0 in this dll, and "MinimizeAllWindows()" is at 0x003ACB20.
Thanks-
Baker

Hi Kelsey,
Apologies for the long response time, I didn't receive a notification for your post.
> What does your application do?
Our application is used in this context to setup and run our vehicle simulations on a Windows based PC.
> And, what is it doing at the time of the crash?
At the time of the crash a simulation is being launched and run on another thread from the default thread pool like this:
CmtScheduleThreadPoolFunctionAdv (DEFAULT_THREAD_POOL_HANDLE,
sRun,
NULL,
THREAD_PRIORITY_NORMAL,
NULL,
EVENT_TP_THREAD_FUNCTION_END,
NULL,
RUN_IN_SCHEDULED_THREAD,
&sThreadFuncId);
That spawned thread will load a simulation DLL, read some data as input, run the simulation, output the results, then close the DLL.
As I noted earlier, I couldn't get it to happen on my desktop, but I could get it on the VM when I used a very slow storage device for the I/O of the simulation (a slow thumb drive attached to the VM). My boss was seeing the issue on his virtualized PC on his Mac, typically only when he used a slower storage device as well (network storage for example).
> When you reproduce this issue in 2010 and 2013 f1, are you using the same computer or using different machines?
Both of these crash dumps were produced on the virtual machine as described.
> For each dump file, which version of LabWindows/CVI were you running? You can find the version number by selecting Help»About LabWindows/CVI within LabWindows/CVI. Which version of cvirte.dll do you have? This will be located in System32 and/or SysWOW64.
The development environment installed was CVI 2010 SP1. So the 2010 dump was just using the runtimes bundled with that installation. I then installed the 2013 F1 runtimes to see if the same issue persisted.
It's possible I did a clean install with the 2013 F1 dev environment, I will double check this tomorrow when I have access to the virtual machine.
Thanks for looking into this--
Baker

Access Violation in DllMain of coherence.dll

I have an issue with C++ project, that using coherence (version 3.7). During loading the exe file dialog box is shown with the message: "The application failed to initialize properly (0xc0000005)". After clicking "OK" the process terminates.
Running under debugger I discovered the error place:
The error: 0xC0000005: Access violation writing location 0x00000010.
The call stack:
 ntdll.dll!_RtlpWaitForCriticalSection@4() + 0x5b bytes
 ntdll.dll!_RtlEnterCriticalSection@4() + 0x46 bytes
 iphlpapi.dll!76d626fd()
 [Frames below may be incorrect and/or missing, no symbols loaded for iphlpapi.dll]
 iphlpapi.dll!76d6605b()
 dnsapi.dll!_IpHelp_GetAdaptersInfo@4() + 0x32 bytes
 dnsapi.dll!_NetInfo_Build@4() + 0x2c bytes
 dnsapi.dll!_NetInfo_Get@8() + 0x28 bytes
 dnsapi.dll!_GetDnsServerRRSet@8() + 0x36 bytes
 dnsapi.dll!_DnsQuery_W@24() + 0xa8 bytes
 mswsock.dll!_myhostent_W@0() + 0xf8 bytes
 mswsock.dll!_RNRPROV_NSPStartup@8() + 0x47 bytes
 mswsock.dll!_NSPStartup@8() + 0x20dc bytes
 ws2_32.dll!NSPROVIDER::Initialize() + 0xa7 bytes
 ws2_32.dll!NSCATALOG::LoadProvider() + 0x4a bytes
 ws2_32.dll!LookupBeginEnumerationProc() + 0x154e bytes
 ws2_32.dll!DCATALOG::EnumerateCatalogItems() + 0x25 bytes
 ws2_32.dll!NSQUERY::LookupServiceBegin() + 0x98 bytes
 ws2_32.dll!_WSALookupServiceBeginW@12() + 0x84 bytes
 ws2_32.dll!_WSALookupServiceBeginA@12() + 0x6f bytes
 ws2_32.dll!getxyDataEnt() + 0x5d bytes
 ws2_32.dll!_gethostname@8() + 0xa7 bytes
 coherence.dll!coherence::native::NativeInetHelper::getLocalHostName() Line 250 + 0x43 bytes C++
 coherence.dll!coherence::net::InetAddress::getLocalHost() Line 84 + 0x10 bytes C++
 coherence.dll!coherence::util::`anonymous namespace'::InetAddressInfo::InetAddressInfo() Line 56 + 0xd bytes C++
 coherence.dll!coherence::lang::factory<coherence::util::`anonymous namespace'::InetAddressInfo>::create() Line 389 + 0x44 bytes C++
 coherence.dll!coherence::lang::class_spec<coherence::util::`anonymous namespace'::InetAddressInfo,coherence::lang::extends<coherence::lang::Object,void>,coherence::lang::implements<void,void,void,void,void,void,void,void,void,void,void,void,void,void,void,void> >::create() Line 143 + 0x12 bytes C++
 coherence.dll!coherence::util::`anonymous namespace'::getInetAddressInfo() Line 252 + 0x2a bytes C++
 coherence.dll!coherence::util::`anonymous namespace'::`dynamic initializer for 'coh_static_init_func255''() Line 255 + 0xf bytes C++
 msvcr80.dll!78131742()
 coherence.dll!_CRT_INIT(void * hDllHandle=0x00440000, unsigned long dwReason=0, void * lpreserved=0x0012fd30) Line 316 + 0xf bytes C
 coherence.dll!__DllMainCRTStartup(void * hDllHandle=0x00440000, unsigned long dwReason=0, void * lpreserved=0x00000000) Line 492 + 0x8 bytes C
 coherence.dll!_DllMainCRTStartup(void * hDllHandle=0x00440000, unsigned long dwReason=1, void * lpreserved=0x0012fd30) Line 462 + 0x11 bytes C
 ntdll.dll!_LdrpCallInitRoutine@16() + 0x14 bytes
 ntdll.dll!_LdrpRunInitializeRoutines@4() + 0x205 bytes
 ntdll.dll!_LdrpInitializeProcess@20() - 0x96d bytes
 ntdll.dll!__LdrpInitialize@12() + 0x6269 bytes
 ntdll.dll!_KiUserApcDispatcher@20() + 0x7 bytes
According to [http://msdn.microsoft.com/en-us/library/ms682583(v=vs.85).aspx] :
The entry-point function should perform only simple initialization or termination tasks. It must not call the LoadLibrary or LoadLibraryEx function (or a function that calls these functions), because this may create dependency loops in the DLL load order. This can result in a DLL being used before the system has executed its initialization code. Similarly, the entry-point function must not call the FreeLibrary function (or a function that calls FreeLibrary) during process termination, because this can result in a DLL being used after the system has executed its termination code.
Because Kernel32.dll is guaranteed to be loaded in the process address space when the entry-point function is called, calling functions in Kernel32.dll does not result in the DLL being used before its initialization code has been executed. Therefore, the entry-point function can call functions in Kernel32.dll that do not load other DLLs. For example, DllMain can create synchronization objects such as critical sections and mutexes, and use TLS. Unfortunately, there is not a comprehensive list of safe functions in Kernel32.dll.
Windows 2000: Do not create a named synchronization object in DllMain because the system will then load an additional DLL.
Calling functions that require DLLs other than Kernel32.dll may result in problems that are difficult to diagnose. For example, calling User, Shell, and COM functions can cause access violation errors, because some functions load other system components. Conversely, calling functions such as these during termination can cause access violation errors because the corresponding component may already have been unloaded or uninitialized.
Perhaps the coherence developers should define init/cleanup functions (i.e. coherence_init(), coherence_cleanup()) and perform all initialization/cleanup actions there.

The test with many dll's does not reproduced this issue. I don't have much time to continue playing with it. BTW look at the simple test application log (the source of the test you can find on my another thread: {thread:id=2286271}) You can see how many times called LoadLibrary() from coherence.dll!DllMain (marked in red). And it doesn't matter, that it works most of the time. It is so called undefined behavior.
Started "TEST.EXE" (process 0x1694) at address 0x00400000 by thread 1. Successfully hooked module.
Loaded "NTDLL.DLL" at address 0x7C900000 by thread 1. Successfully hooked module.
Loaded "KERNEL32.DLL" at address 0x7C800000 by thread 1. Successfully hooked module.
DllMain(0x7C900000, DLL_PROCESS_ATTACH, 0x00000000) in "NTDLL.DLL" called by thread 1.
DllMain(0x7C900000, DLL_PROCESS_ATTACH, 0x00000000) in "NTDLL.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C800000, DLL_PROCESS_ATTACH, 0x00000000) in "KERNEL32.DLL" called by thread 1.
DllMain(0x7C800000, DLL_PROCESS_ATTACH, 0x00000000) in "KERNEL32.DLL" returned 1 (0x1) by thread 1.
Injected "DEPENDS.DLL" at address 0x08370000 by thread 1.
DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in "DEPENDS.DLL" called by thread 1.
DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in "DEPENDS.DLL" returned 1 (0x1) by thread 1.
Loaded "COHERENCE.DLL" at address 0x10000000 by thread 1. Successfully hooked module.
Loaded "WS2_32.DLL" at address 0x71AB0000 by thread 1. Successfully hooked module.
Loaded "ADVAPI32.DLL" at address 0x77DD0000 by thread 1. Successfully hooked module.
Loaded "RPCRT4.DLL" at address 0x77E70000 by thread 1. Successfully hooked module.
Loaded "SECUR32.DLL" at address 0x77FE0000 by thread 1. Successfully hooked module.
Loaded "MSVCRT.DLL" at address 0x77C10000 by thread 1. Successfully hooked module.
Loaded "WS2HELP.DLL" at address 0x71AA0000 by thread 1. Successfully hooked module.
Loaded "MSVCP80.DLL" at address 0x7C420000 by thread 1. Successfully hooked module.
Loaded "MSVCR80.DLL" at address 0x78130000 by thread 1. Successfully hooked module.
Loaded "IMAGEHLP.DLL" at address 0x76C90000 by thread 1. Successfully hooked module.
DllMain(0x77FE0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "SECUR32.DLL" called by thread 1.
DllMain(0x77FE0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "SECUR32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77E70000, DLL_PROCESS_ATTACH, 0x0012FD30) in "RPCRT4.DLL" called by thread 1.
DllMain(0x77E70000, DLL_PROCESS_ATTACH, 0x0012FD30) in "RPCRT4.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77DD0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "ADVAPI32.DLL" called by thread 1.
DllMain(0x77DD0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "ADVAPI32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77C10000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCRT.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "InitializeCriticalSectionAndSpinCount") called from "MSVCRT.DLL" at address 0x77C379C2 and returned 0x7C80B8C9 by thread 1.
DllMain(0x77C10000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCRT.DLL" returned 1 (0x1) by thread 1.
DllMain(0x71AA0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "WS2HELP.DLL" called by thread 1.
DllMain(0x71AA0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "WS2HELP.DLL" returned 1 (0x1) by thread 1.
DllMain(0x71AB0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "WS2_32.DLL" called by thread 1.
DllMain(0x71AB0000, DLL_PROCESS_ATTACH, 0x0012FD30) in "WS2_32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x78130000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCR80.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "FlsAlloc") called from "MSVCR80.DLL" at address 0x78133001 and returned NULL by thread 1. Error: The specified procedure could not be found (127).
[snip]
GetProcAddress(0x7C800000 [KERNEL32.DLL], "GetSystemWindowsDirectoryW") called from "MSVCR80.DLL" at address 0x78131F1A and returned 0x7C80ADC9 by thread 1.
DllMain(0x78130000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCR80.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C420000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCP80.DLL" called by thread 1.
DllMain(0x7C420000, DLL_PROCESS_ATTACH, 0x0012FD30) in "MSVCP80.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76C90000, DLL_PROCESS_ATTACH, 0x0012FD30) in "IMAGEHLP.DLL" called by thread 1.
DllMain(0x76C90000, DLL_PROCESS_ATTACH, 0x0012FD30) in "IMAGEHLP.DLL" returned 1 (0x1) by thread 1.
DllMain(0x10000000, DLL_PROCESS_ATTACH, 0x0012FD30) in "COHERENCE.DLL" called by thread 1.
GetProcAddress(0x71AB0000 [WS2_32.DLL], "accept") called from "WS2_32.DLL" at address 0x71AB737E and returned 0x71AC1040 by thread 1.
[snip]
GetProcAddress(0x71AB0000 [WS2_32.DLL], "freeaddrinfo") called from "WS2_32.DLL" at address 0x71AB737E and returned 0x71AB2B0B by thread 1.
LoadLibraryA("C:\WINNT\System32\mswsock.dll") called from "WS2_32.DLL" at address 0x71AB4EA0 by thread 1.
Loaded "MSWSOCK.DLL" at address 0x71A50000 by thread 1. Successfully hooked module.
DllMain(0x71A50000, DLL_PROCESS_ATTACH, 0x00000000) in "MSWSOCK.DLL" called by thread 1.
DllMain(0x71A50000, DLL_PROCESS_ATTACH, 0x00000000) in "MSWSOCK.DLL" returned 1 (0x1) by thread 1.
LoadLibraryA("C:\WINNT\System32\mswsock.dll") returned 0x71A50000 by thread 1.
GetProcAddress(0x71A50000 [MSWSOCK.DLL], "NSPStartup") called from "WS2_32.DLL" at address 0x71AB4EB7 and returned 0x71A5A830 by thread 1.
LoadLibraryA("DNSAPI.dll") called from "MSWSOCK.DLL" at address 0x71A5C714 by thread 1.
Loaded "DNSAPI.DLL" at address 0x76F20000 by thread 1. Successfully hooked module.
DllMain(0x76F20000, DLL_PROCESS_ATTACH, 0x00000000) in "DNSAPI.DLL" called by thread 1.
DllMain(0x76F20000, DLL_PROCESS_ATTACH, 0x00000000) in "DNSAPI.DLL" returned 1 (0x1) by thread 1.
LoadLibraryA("DNSAPI.dll") returned 0x76F20000 by thread 1.
GetProcAddress(0x76F20000 [DNSAPI.DLL], "DnsQueryConfigAllocEx") called from "MSWSOCK.DLL" at address 0x71A5C6FD and returned 0x76F27A55 by thread 1.
LoadLibraryW("rpcrt4.dll") called from "RPCRT4.DLL" at address 0x77E8B42D by thread 1.
LoadLibraryW("rpcrt4.dll") returned 0x77E70000 by thread 1.
GetProcAddress(0x76F20000 [DNSAPI.DLL], "DnsApiFree") called from "MSWSOCK.DLL" at address 0x71A5C6FD and returned 0x76F237A1 by thread 1.
GetProcAddress(0x76F20000 [DNSAPI.DLL], "DnsQuery_W") called from "MSWSOCK.DLL" at address 0x71A5C6FD and returned 0x76F22DA3 by thread 1.
LoadLibraryA("iphlpapi.dll") called from "DNSAPI.DLL" at address 0x76F2AB0A by thread 1.
Loaded "IPHLPAPI.DLL" at address 0x76D60000 by thread 1. Successfully hooked module.
Loaded "USER32.DLL" at address 0x7E410000 by thread 1. Successfully hooked module.
Loaded "GDI32.DLL" at address 0x77F10000 by thread 1. Successfully hooked module.
DllMain(0x77F10000, DLL_PROCESS_ATTACH, 0x00000000) in "GDI32.DLL" called by thread 1.
DllMain(0x77F10000, DLL_PROCESS_ATTACH, 0x00000000) in "GDI32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7E410000, DLL_PROCESS_ATTACH, 0x00000000) in "USER32.DLL" called by thread 1.
DllMain(0x7E410000, DLL_PROCESS_ATTACH, 0x00000000) in "USER32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76D60000, DLL_PROCESS_ATTACH, 0x00000000) in "IPHLPAPI.DLL" called by thread 1.
DllMain(0x76D60000, DLL_PROCESS_ATTACH, 0x00000000) in "IPHLPAPI.DLL" returned 1 (0x1) by thread 1.
LoadLibraryA("iphlpapi.dll") returned 0x76D60000 by thread 1.
GetProcAddress(0x76D60000 [IPHLPAPI.DLL], "GetAdaptersInfo") called from "DNSAPI.DLL" at address 0x76F2AB5F and returned 0x76D66051 by thread 1.
GetProcAddress(0x76D60000 [IPHLPAPI.DLL], "GetPerAdapterInfo") called from "DNSAPI.DLL" at address 0x76F2AB5F and returned 0x76D66769 by thread 1.
GetProcAddress(0x76F20000 [DNSAPI.DLL], "DnsRecordListFree") called from "MSWSOCK.DLL" at address 0x71A5C6FD and returned 0x76F25B12 by thread 1.
LoadLibraryA("C:\WINNT\System32\winrnr.dll") called from "WS2_32.DLL" at address 0x71AB4EA0 by thread 1.
Loaded "WINRNR.DLL" at address 0x76FB0000 by thread 1. Successfully hooked module.
Loaded "WLDAP32.DLL" at address 0x76F60000 by thread 1. Successfully hooked module.
DllMain(0x76F60000, DLL_PROCESS_ATTACH, 0x00000000) in "WLDAP32.DLL" called by thread 1.
DllMain(0x76F60000, DLL_PROCESS_ATTACH, 0x00000000) in "WLDAP32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76FB0000, DLL_PROCESS_ATTACH, 0x00000000) in "WINRNR.DLL" called by thread 1.
DllMain(0x76FB0000, DLL_PROCESS_ATTACH, 0x00000000) in "WINRNR.DLL" returned 1 (0x1) by thread 1.
LoadLibraryA("C:\WINNT\System32\winrnr.dll") returned 0x76FB0000 by thread 1.
GetProcAddress(0x76FB0000 [WINRNR.DLL], "NSPStartup") called from "WS2_32.DLL" at address 0x71AB4EB7 and returned 0x76FB1688 by thread 1.
LoadLibraryA("C:\WINNT\System32\mswsock.dll") called from "WS2_32.DLL" at address 0x71AB4EA0 by thread 1.
LoadLibraryA("C:\WINNT\System32\mswsock.dll") returned 0x71A50000 by thread 1.
GetProcAddress(0x71A50000 [MSWSOCK.DLL], "NSPStartup") called from "WS2_32.DLL" at address 0x71AB4EB7 and returned 0x71A5A830 by thread 1.
LoadLibraryA("C:\WINNT\system32\ws2_32") called from "COHERENCE.DLL" at address 0x100A70B4 by thread 1.
LoadLibraryA("C:\WINNT\system32\ws2_32") returned 0x71AB0000 by thread 1.
GetProcAddress(0x71AB0000 [WS2_32.DLL], "getaddrinfo") called from "COHERENCE.DLL" at address 0x100A70C6 and returned 0x71AB2A6F by thread 1.
[snip]
GetProcAddress(0x76F20000 [DNSAPI.DLL], "DnsNameCompare_W") called from "MSWSOCK.DLL" at address 0x71A5C6FD and returned 0x76F2349A by thread 1.
LoadLibraryA("rasadhlp.dll") called from "WS2_32.DLL" at address 0x71AB4FB8 by thread 1.
Loaded "RASADHLP.DLL" at address 0x76FC0000 by thread 1. Successfully hooked module.
DllMain(0x76FC0000, DLL_PROCESS_ATTACH, 0x00000000) in "RASADHLP.DLL" called by thread 1.
DllMain(0x76FC0000, DLL_PROCESS_ATTACH, 0x00000000) in "RASADHLP.DLL" returned 1 (0x1) by thread 1.
LoadLibraryA("rasadhlp.dll") returned 0x76FC0000 by thread 1.
GetProcAddress(0x76FC0000 [RASADHLP.DLL], "WSAttemptAutodialAddr") called from "WS2_32.DLL" at address 0x71AB4FCF and returned 0x76FC1AF3 by thread 1.
[snip]
GetProcAddress(0x76FC0000 [RASADHLP.DLL], "WSNoteSuccessfulHostentLookup") called from "WS2_32.DLL" at address 0x71AB4FF3 and returned 0x76FC13A0 by thread 1.
LoadLibraryA("kernel32.dll") called from "COHERENCE.DLL" at address 0x100AC4E3 by thread 1.
LoadLibraryA("kernel32.dll") returned 0x7C800000 by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "RtlCaptureContext") called from "COHERENCE.DLL" at address 0x100AC4F8 and returned 0x7C90331A by thread 1.
LoadLibraryA("C:\WINNT\system32\DBGHELP.dll") called from "IMAGEHLP.DLL" at address 0x76C97327 by thread 1.
Loaded "DBGHELP.DLL" at address 0x59A60000 by thread 1. Successfully hooked module.
Loaded "VERSION.DLL" at address 0x77C00000 by thread 1. Successfully hooked module.
DllMain(0x77C00000, DLL_PROCESS_ATTACH, 0x00000000) in "VERSION.DLL" called by thread 1.
DllMain(0x77C00000, DLL_PROCESS_ATTACH, 0x00000000) in "VERSION.DLL" returned 1 (0x1) by thread 1.
DllMain(0x59A60000, DLL_PROCESS_ATTACH, 0x00000000) in "DBGHELP.DLL" called by thread 1.
DllMain(0x59A60000, DLL_PROCESS_ATTACH, 0x00000000) in "DBGHELP.DLL" returned 1 (0x1) by thread 1.
LoadLibraryA("C:\WINNT\system32\DBGHELP.dll") returned 0x59A60000 by thread 1.
GetProcAddress(0x59A60000 [DBGHELP.DLL], "SymGetOptions") called from "IMAGEHLP.DLL" at address 0x76C97350 and returned 0x59A7B7AD by thread 1.
[snip]
GetProcAddress(0x7C900000 [NTDLL.DLL], "RtlDestroyQueryDebugBuffer") called from "DBGHELP.DLL" at address 0x59A7E675 and returned 0x7C954BC0 by thread 1.
DllMain(0x10000000, DLL_PROCESS_ATTACH, 0x0012FD30) in "COHERENCE.DLL" returned 1 (0x1) by thread 1.
Loaded "SXWMON32.DLL" at address 0x00CC0000 by thread 1. Successfully hooked module.
Loaded "SHELL32.DLL" at address 0x7C9C0000 by thread 1. Successfully hooked module.
Loaded "SHLWAPI.DLL" at address 0x77F60000 by thread 1. Successfully hooked module.
Loaded "OLE32.DLL" at address 0x774E0000 by thread 1. Successfully hooked module.
DllMain(0x77F60000, DLL_PROCESS_ATTACH, 0x00000000) in "SHLWAPI.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "CreateTimerQueue") called from "SHLWAPI.DLL" at address 0x77F65CF9 and returned 0x7C82BFE6 by thread 1.
[snip]
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DeleteTimerQueueTimer") called from "SHLWAPI.DLL" at address 0x77F65D35 and returned 0x7C821130 by thread 1.
DllMain(0x77F60000, DLL_PROCESS_ATTACH, 0x00000000) in "SHLWAPI.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C9C0000, DLL_PROCESS_ATTACH, 0x00000000) in "SHELL32.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "CreateActCtxW") called from "SHELL32.DLL" at address 0x7C9FAB3E and returned 0x7C8154FC by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "ActivateActCtx") called from "SHELL32.DLL" at address 0x7C9E7639 and returned 0x7C80A6E4 by thread 1.
LoadLibraryW("comctl32.dll") called from "SHELL32.DLL" at address 0x7C9FA774 by thread 1.
Loaded "COMCTL32.DLL" at address 0x773D0000 by thread 1. Successfully hooked module.
DllMain(0x773D0000, DLL_PROCESS_ATTACH, 0x00000000) in "COMCTL32.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "GetSystemWindowsDirectoryW") called from "COMCTL32.DLL" at address 0x7745B789 and returned 0x7C80ADC9 by thread 1.
[snip]
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DeactivateActCtx") called from "COMCTL32.DLL" at address 0x7745B6F4 and returned 0x7C80A715 by thread 1.
DllMain(0x773D0000, DLL_PROCESS_ATTACH, 0x00000000) in "COMCTL32.DLL" returned 1 (0x1) by thread 1.
LoadLibraryW("comctl32.dll") returned 0x773D0000 by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DeactivateActCtx") called from "SHELL32.DLL" at address 0x7C9E76A4 and returned 0x7C80A715 by thread 1.
LoadLibraryW("comctl32.dll") called from "SHELL32.DLL" at address 0x7C9FA8A6 by thread 1.
Loaded "COMCTL32.DLL" at address 0x5D090000 by thread 1. Successfully hooked module.
DllMain(0x5D090000, DLL_PROCESS_ATTACH, 0x00000000) in "COMCTL32.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "InitializeCriticalSectionAndSpinCount") called from "COMCTL32.DLL" at address 0x5D095338 and returned 0x7C80B8C9 by thread 1.
[snip]
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DeactivateActCtx") called from "COMCTL32.DLL" at address 0x5D0FF2BF and returned 0x7C80A715 by thread 1.
DllMain(0x5D090000, DLL_PROCESS_ATTACH, 0x00000000) in "COMCTL32.DLL" returned 1 (0x1) by thread 1.
LoadLibraryW("comctl32.dll") returned 0x5D090000 by thread 1.
GetProcAddress(0x5D090000 [COMCTL32.DLL], "InitCommonControlsEx") called from "SHELL32.DLL" at address 0x7C9FA8B6 and returned 0x5D093619 by thread 1.
DllMain(0x7C9C0000, DLL_PROCESS_ATTACH, 0x00000000) in "SHELL32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x774E0000, DLL_PROCESS_ATTACH, 0x00000000) in "OLE32.DLL" called by thread 1.
DllMain(0x774E0000, DLL_PROCESS_ATTACH, 0x00000000) in "OLE32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x00CC0000, DLL_PROCESS_ATTACH, 0x00000000) in "SXWMON32.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "FlsAlloc") called from "SXWMON32.DLL" at address 0x00CD8086 and returned NULL by thread 1. Error: The specified procedure could not be found (127).
[snip]
GetProcAddress(0x7C900000 [NTDLL.DLL], "ZwQueryVirtualMemory") called from "SXWMON32.DLL" at address 0x00CC1958 and returned 0x7C90D97E by thread 1.
DllMain(0x00CC0000, DLL_PROCESS_ATTACH, 0x00000000) in "SXWMON32.DLL" returned 1 (0x1) by thread 1.
GetProcAddress(0x59A60000 [DBGHELP.DLL], "StackWalk64") called from "IMAGEHLP.DLL" at address 0x76C97350 and returned 0x59A83492 by thread 1.
[snip]
GetProcAddress(0x59A60000 [DBGHELP.DLL], "SymGetModuleInfo64") called from "IMAGEHLP.DLL" at address 0x76C97350 and returned 0x59A7C94E by thread 1.
First chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "KERNEL32.DLL" at address 0x7C812AFB by thread 1.
First chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "KERNEL32.DLL" at address 0x7C812AFB by thread 1.
Thread 2 started in "KERNEL32.DLL" at address 0x7C8106F9.
DllMain(0x7C900000, DLL_THREAD_ATTACH, 0x00000000) in "NTDLL.DLL" called by thread 2.
DllMain(0x7C900000, DLL_THREAD_ATTACH, 0x00000000) in "NTDLL.DLL" returned 1 (0x1) by thread 2.
DllMain(0x7C800000, DLL_THREAD_ATTACH, 0x00000000) in "KERNEL32.DLL" called by thread 2.
DllMain(0x7C800000, DLL_THREAD_ATTACH, 0x00000000) in "KERNEL32.DLL" returned 1 (0x1) by thread 2.
DllMain(0x10000000, DLL_THREAD_ATTACH, 0x00000000) in "COHERENCE.DLL" called by thread 2.
DllMain(0x10000000, DLL_THREAD_ATTACH, 0x00000000) in "COHERENCE.DLL" returned 1 (0x1) by thread 2.
DllMain(0x71AB0000, DLL_THREAD_ATTACH, 0x00000000) in "WS2_32.DLL" called by thread 2.
DllMain(0x71AB0000, DLL_THREAD_ATTACH, 0x00000000) in "WS2_32.DLL" returned 1 (0x1) by thread 2.
DllMain(0x77DD0000, DLL_THREAD_ATTACH, 0x00000000) in "ADVAPI32.DLL" called by thread 2.
DllMain(0x77DD0000, DLL_THREAD_ATTACH, 0x00000000) in "ADVAPI32.DLL" returned 2147344385 (0x7FFDE001) by thread 2.
DllMain(0x77E70000, DLL_THREAD_ATTACH, 0x00000000) in "RPCRT4.DLL" called by thread 2.
DllMain(0x77E70000, DLL_THREAD_ATTACH, 0x00000000) in "RPCRT4.DLL" returned 4294967041 (0xFFFFFF01) by thread 2.
DllMain(0x77C10000, DLL_THREAD_ATTACH, 0x00000000) in "MSVCRT.DLL" called by thread 2.
DllMain(0x77C10000, DLL_THREAD_ATTACH, 0x00000000) in "MSVCRT.DLL" returned 1 (0x1) by thread 2.
DllMain(0x78130000, DLL_THREAD_ATTACH, 0x00000000) in "MSVCR80.DLL" called by thread 2.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DecodePointer") called from "MSVCR80.DLL" at address 0x78132C33 and returned 0x7C9132FF by thread 2.
[snip]
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DecodePointer") called from "MSVCR80.DLL" at address 0x78132D4A and returned 0x7C9132FF by thread 2.
DllMain(0x78130000, DLL_THREAD_ATTACH, 0x00000000) in "MSVCR80.DLL" returned 1 (0x1) by thread 2.
DllMain(0x71A50000, DLL_THREAD_ATTACH, 0x00000000) in "MSWSOCK.DLL" called by thread 2.
DllMain(0x71A50000, DLL_THREAD_ATTACH, 0x00000000) in "MSWSOCK.DLL" returned 1 (0x1) by thread 2.
DllMain(0x76F60000, DLL_THREAD_ATTACH, 0x00000000) in "WLDAP32.DLL" called by thread 2.
DllMain(0x76F60000, DLL_THREAD_ATTACH, 0x00000000) in "WLDAP32.DLL" returned 1 (0x1) by thread 2.
DllMain(0x77C00000, DLL_THREAD_ATTACH, 0x00000000) in "VERSION.DLL" called by thread 2.
DllMain(0x77C00000, DLL_THREAD_ATTACH, 0x00000000) in "VERSION.DLL" returned 1 (0x1) by thread 2.
DllMain(0x00CC0000, DLL_THREAD_ATTACH, 0x00000000) in "SXWMON32.DLL" called by thread 2.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DecodePointer") called from "SXWMON32.DLL" at address 0x00CD7CB0 and returned 0x7C9132FF by thread 2.
[snip]
GetProcAddress(0x7C800000 [KERNEL32.DLL], "DecodePointer") called from "SXWMON32.DLL" at address 0x00CD7D94 and returned 0x7C9132FF by thread 2.
DllMain(0x00CC0000, DLL_THREAD_ATTACH, 0x00000000) in "SXWMON32.DLL" returned 1 (0x1) by thread 2.
DllMain(0x7C9C0000, DLL_THREAD_ATTACH, 0x00000000) in "SHELL32.DLL" called by thread 2.
DllMain(0x7C9C0000, DLL_THREAD_ATTACH, 0x00000000) in "SHELL32.DLL" returned 1 (0x1) by thread 2.
DllMain(0x774E0000, DLL_THREAD_ATTACH, 0x00000000) in "OLE32.DLL" called by thread 2.
DllMain(0x774E0000, DLL_THREAD_ATTACH, 0x00000000) in "OLE32.DLL" returned 1 (0x1) by thread 2.
First chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in "KERNEL32.DLL" at address 0x7C812AFB by thread 1.
DllMain(0x5D090000, DLL_PROCESS_DETACH, 0x00000001) in "COMCTL32.DLL" called by thread 1.
Thread 2 exited with code 0 (0x0).
GetProcAddress(0x7C800000 [KERNEL32.DLL], "ReleaseActCtx") called from "COMCTL32.DLL" at address 0x5D0FF202 and returned 0x7C8130FF by thread 1.
DllMain(0x5D090000, DLL_PROCESS_DETACH, 0x00000001) in "COMCTL32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x773D0000, DLL_PROCESS_DETACH, 0x00000001) in "COMCTL32.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "ReleaseActCtx") called from "COMCTL32.DLL" at address 0x7745B656 and returned 0x7C8130FF by thread 1.
DllMain(0x773D0000, DLL_PROCESS_DETACH, 0x00000001) in "COMCTL32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x00CC0000, DLL_PROCESS_DETACH, 0x00000001) in "SXWMON32.DLL" called by thread 1.
DllMain(0x00CC0000, DLL_PROCESS_DETACH, 0x00000001) in "SXWMON32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x774E0000, DLL_PROCESS_DETACH, 0x00000001) in "OLE32.DLL" called by thread 1.
DllMain(0x774E0000, DLL_PROCESS_DETACH, 0x00000001) in "OLE32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C9C0000, DLL_PROCESS_DETACH, 0x00000001) in "SHELL32.DLL" called by thread 1.
GetProcAddress(0x7C800000 [KERNEL32.DLL], "ReleaseActCtx") called from "SHELL32.DLL" at address 0x7C9FDF7B and returned 0x7C8130FF by thread 1.
DllMain(0x7C9C0000, DLL_PROCESS_DETACH, 0x00000001) in "SHELL32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77F60000, DLL_PROCESS_DETACH, 0x00000001) in "SHLWAPI.DLL" called by thread 1.
DllMain(0x77F60000, DLL_PROCESS_DETACH, 0x00000001) in "SHLWAPI.DLL" returned 1 (0x1) by thread 1.
DllMain(0x59A60000, DLL_PROCESS_DETACH, 0x00000001) in "DBGHELP.DLL" called by thread 1.
DllMain(0x59A60000, DLL_PROCESS_DETACH, 0x00000001) in "DBGHELP.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77C00000, DLL_PROCESS_DETACH, 0x00000001) in "VERSION.DLL" called by thread 1.
DllMain(0x77C00000, DLL_PROCESS_DETACH, 0x00000001) in "VERSION.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76FC0000, DLL_PROCESS_DETACH, 0x00000001) in "RASADHLP.DLL" called by thread 1.
DllMain(0x76FC0000, DLL_PROCESS_DETACH, 0x00000001) in "RASADHLP.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76FB0000, DLL_PROCESS_DETACH, 0x00000001) in "WINRNR.DLL" called by thread 1.
DllMain(0x76FB0000, DLL_PROCESS_DETACH, 0x00000001) in "WINRNR.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76F60000, DLL_PROCESS_DETACH, 0x00000001) in "WLDAP32.DLL" called by thread 1.
DllMain(0x76F60000, DLL_PROCESS_DETACH, 0x00000001) in "WLDAP32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76D60000, DLL_PROCESS_DETACH, 0x00000001) in "IPHLPAPI.DLL" called by thread 1.
DllMain(0x76D60000, DLL_PROCESS_DETACH, 0x00000001) in "IPHLPAPI.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7E410000, DLL_PROCESS_DETACH, 0x00000001) in "USER32.DLL" called by thread 1.
DllMain(0x7E410000, DLL_PROCESS_DETACH, 0x00000001) in "USER32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77F10000, DLL_PROCESS_DETACH, 0x00000001) in "GDI32.DLL" called by thread 1.
DllMain(0x77F10000, DLL_PROCESS_DETACH, 0x00000001) in "GDI32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76F20000, DLL_PROCESS_DETACH, 0x00000001) in "DNSAPI.DLL" called by thread 1.
DllMain(0x76F20000, DLL_PROCESS_DETACH, 0x00000001) in "DNSAPI.DLL" returned 1 (0x1) by thread 1.
DllMain(0x71A50000, DLL_PROCESS_DETACH, 0x00000001) in "MSWSOCK.DLL" called by thread 1.
DllMain(0x71A50000, DLL_PROCESS_DETACH, 0x00000001) in "MSWSOCK.DLL" returned 1 (0x1) by thread 1.
DllMain(0x10000000, DLL_PROCESS_DETACH, 0x00000001) in "COHERENCE.DLL" called by thread 1.
DllMain(0x10000000, DLL_PROCESS_DETACH, 0x00000001) in "COHERENCE.DLL" returned 1 (0x1) by thread 1.
DllMain(0x76C90000, DLL_PROCESS_DETACH, 0x00000001) in "IMAGEHLP.DLL" called by thread 1.
DllMain(0x76C90000, DLL_PROCESS_DETACH, 0x00000001) in "IMAGEHLP.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C420000, DLL_PROCESS_DETACH, 0x00000001) in "MSVCP80.DLL" called by thread 1.
DllMain(0x7C420000, DLL_PROCESS_DETACH, 0x00000001) in "MSVCP80.DLL" returned 1 (0x1) by thread 1.
DllMain(0x78130000, DLL_PROCESS_DETACH, 0x00000001) in "MSVCR80.DLL" called by thread 1.
DllMain(0x78130000, DLL_PROCESS_DETACH, 0x00000001) in "MSVCR80.DLL" returned 1 (0x1) by thread 1.
DllMain(0x71AB0000, DLL_PROCESS_DETACH, 0x00000001) in "WS2_32.DLL" called by thread 1.
DllMain(0x71AB0000, DLL_PROCESS_DETACH, 0x00000001) in "WS2_32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x71AA0000, DLL_PROCESS_DETACH, 0x00000001) in "WS2HELP.DLL" called by thread 1.
DllMain(0x71AA0000, DLL_PROCESS_DETACH, 0x00000001) in "WS2HELP.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77C10000, DLL_PROCESS_DETACH, 0x00000001) in "MSVCRT.DLL" called by thread 1.
DllMain(0x77C10000, DLL_PROCESS_DETACH, 0x00000001) in "MSVCRT.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77DD0000, DLL_PROCESS_DETACH, 0x00000001) in "ADVAPI32.DLL" called by thread 1.
DllMain(0x77DD0000, DLL_PROCESS_DETACH, 0x00000001) in "ADVAPI32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77E70000, DLL_PROCESS_DETACH, 0x00000001) in "RPCRT4.DLL" called by thread 1.
DllMain(0x77E70000, DLL_PROCESS_DETACH, 0x00000001) in "RPCRT4.DLL" returned 1 (0x1) by thread 1.
DllMain(0x77FE0000, DLL_PROCESS_DETACH, 0x00000001) in "SECUR32.DLL" called by thread 1.
DllMain(0x77FE0000, DLL_PROCESS_DETACH, 0x00000001) in "SECUR32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x08370000, DLL_PROCESS_DETACH, 0x00000001) in "DEPENDS.DLL" called by thread 1.
DllMain(0x08370000, DLL_PROCESS_DETACH, 0x00000001) in "DEPENDS.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C800000, DLL_PROCESS_DETACH, 0x00000001) in "KERNEL32.DLL" called by thread 1.
DllMain(0x7C800000, DLL_PROCESS_DETACH, 0x00000001) in "KERNEL32.DLL" returned 1 (0x1) by thread 1.
DllMain(0x7C900000, DLL_PROCESS_DETACH, 0x00000001) in "NTDLL.DLL" called by thread 1.
DllMain(0x7C900000, DLL_PROCESS_DETACH, 0x00000001) in "NTDLL.DLL" returned 1 (0x1) by thread 1.
Exited "TEST.EXE" (process 0x1694) with code 0 (0x0) by thread 1.
-----

Access Violation in NIPALU.DLL

When using Traditional NIDAQ in Visual C++ 6, I get an Access Violation exception whenever I run any NIDAQ code. Even the examples cause them from time to time.
It always occurs in pairs (that is, the same exception gets thrown twice in a row) and seems to happen most inside of Init_DA_Brds and Get_DAQ_Device_Info. I set a breakpoint on those functions and there is no exception, step over them and the access violations appear.
What's causing this and how can I make it stop?
"First-chance exception in --- (NIPALU.DLL): 0xC0000005: Access Violation."

Hello Matt,
I believe that the problem you are experiencing is documented in this Knowledge Base article. The article includes several steps for troubleshooting this issue.
If this does not resolve your issue or you believe your error condition is not covered by the article, please reply with the results of the additional steps.
Thank you,
Kyle Bryson
National Instruments

How can I repair "an access violation has occurred"

I found this message after you install the update of an audio software (Pro Tools 8.0.5) and after trying to listen to an audio recording "an access violation has occurred." In a later appeared to me the message "/ System / Library / Extensions / CDSDAAudioCaptureSupport.Kext". I removed the software completely reinstalled all audio and I havethe previous version but to no avail. I also reinstalled operating system from OS 10.6.2 Leopard up to 10.6.8 but still nothing. The message reappears when I use the audio software is not allowing me to listen to the audio (only with ProTools, while iTunes feature regularly. I do not know what to do yet.

Linc Davis wrote:
It's the PACE DRM rootkit that's installed along with the Pro Tools application. Its purpose is to cripple your computer so that you can only do what the developer chooses to let you do. If you have a problem with that, you'll have to take it up with DigiDesign, or get rid of their product.
Most absurd response to a question I have ever read...
DRM protects composers life myself from theft. I just hate it when people steal my stuff. Don't you?
I've been a PT professional user for well over a decade. My computer is in no way "crippled". I can do what I want with it and what I want with that software. I run PT with iTunes open all day long with no issue. I can import audio from my iTunes library into PT with no issue. If the audio you are trying to import is protected (from being stolen and remixed etc.) than no, you can't import it into PT. I'm pretty sure that most law abiding citizens would agree that having thier own personal livelyhood protected under law would be a good thing. But for some reason, this society thinks that musicians and other creative professionals don't deserve the same level of protection and don't need to feed thier families...

Error while executing "" command Error type ACCESS VIOLATION Error Address: 0006898E Module name:gfsdesk.DLL

Hi All,
I'm using diadem from .net Program. While on the run I'm getting the following error.
Error While executing "" Command
Error type ACCESS VIOLATION
Error Address: 0006898E
Module name:gfsdesk.DLL
Anyone have any idea why this is happening?
regards,
Swaroop

Hi Swaroop,
It would be helpful to better understand what your code really does. The information that you called DIAdem from your enviroenment is not yet sufficient to understand what the problem might be.
Andreas

Access violation occurs intermittently (msvcr71.dll)

Similar Messages

Maybe you are looking for