ACCESS VIOLATION error in Report

Hi,
I am getting an access violation when trying to save a report. The report only has two worksheets. ONe is a table of contents and one of them is a template for plotting data.
Error while executing "PicSaveAs(FileDlgName)" command
Error Type: ACCESS VIOLATION
Error Address: 89FFEE10
Module Name: DIAdem.exe
I am using Diadem 2011.
Basically, I am trying to create a template file to make plots with. I have a script that copies my template plot, plots the next channel, and repeats for all channels in the data portal. The script works fine, and I got it to run once. HOwever, I wanted to make a change, and something happened to my original template file. So I open my report with 100 pages, delete all pages (and by the way WHY CAN I NOT DELETE MORE THAN ONE PAGE AT ONCE? this is very annoying that i have to do this one at a time (and confirm every time) either by manage or delete options) except one, and I try to save this as my template plot and I get this error...tried several times...Any ideas?
jason

Hello Jason,
a workaround for you could be to open two instances of DIAdem. Open your report in DIAdem one.
Open first page and select "Edit->Select All" and "Edit->Copy" go to your second DIAdem and open Report with an empty report. Select "Edit->Paste" and your template is restored.
Greetings
Andres
P.S.: Please post your report anyway if possible to help us to find the issue.

Similar Messages

Access Violation error with Diadem 2011

I've started using Diadem 2011, and have run into an Access Violation error when loading some of my existing reports. I've created a simple example which shows what's happening:
I've created a simple Bar plot:
If I change the left hand bar to be "Filled" instead of "Right Diagonal", Diadem throws up an access violation error. I've attached the TDM and TDR files used to create the graph. The error in the log file is:
139 Error while executing "" command
     Error type: ACCESS VIOLATION
     Error address: 0004F5E5
     Module nameIAdem.exe
Diadem: 11.0.3f4563 TDM
USI: 1.9.0f4551
DataFinder: 3.0.0f4556
(By the way, it would be great to be able to copy those version details directly from the About page!)
Attachments:
Data.zip ‏7 KB

I've tried this as administrator, and have exactly the same issues, so it doesn't appear to be a permissions problem. I've uninstalled and reinstalled DIAdem and everything's the same.
Here's another ZIP file with hopefully all of the required files. I've created the data files from scrathc several times, and see the same problem. One other thing I've just noticed is that it only occurs when filling the bars with the color Black, not blue or red or anything else.
Attachments:
Data.zip ‏9 KB

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

JDeveloper 3.2 Problems - Access violation errors

Hi,
I suddenly got the following error message on a dialog box when I was editing code in the visual designer:
QUOTE
Access violation at address 00402FC8 'jdeveloper.exe'. Read of address FFFFFFF
UNQUOTE
When I tried to save my work, I was not able to received a similar message. When I tried to exit, I recived the following message:
QUOTE
JDeveloper was unable to autosave the current workspace. Do you wish to close the workspace anyway?"
UNQUOTE
After exiting the workspace, I was not able to reopen the workspace. I created a new workspace and added my projects to the new workspace. I was happy that I did not lose my work.
I have received the access violation error before. I do not know what causes it and I would appreciate very much if the JDev team explains why such an error occurs.
Thanks.

Hi,
We intermittently see postings of this kind. The more information you can provide us about your environment and what you are doing when you get the error, the better:
1. What OS are you running (include version and SP).
2. What kind of processor does your machine run?
3. Do you have a single processor or multiple?
4. What kind of project were you working on? Did you create an empty project and a new class file and were just editing source code, or did you create some initial content using one of the wizards from the Object Gallery and were modifying the generated code, or did you import existing code from some other location?
5. How many source files did you have in the project?
6. Was the source file you were editing a .java file, or a .jsp, .xml, .html?
7. Does this happen frequently, or is this the first time? Has it happened since?
Again, the more detail you can provide, the better we are able to identify possible sources of trouble.

How to resolve and debug access violation Error.

Hello
I'm stucked with an access violation error which forces my exe build to shut down. I tried also from development environment but its the same there. The error happens after 5-60minutes.
I played around with disabling a part of the program where it was possible and I think I'm now able to accuse the vi "gastimer.vi". But since this vi leads through the measurement procedure, there are some commands outgoing which I was not able to map one to one.
My question is: what can cause such access violation errors? I have no dll calls, no third party library, actually the hardware communication is done serial by COM ports. The architecture principle is something adapted from producer consumer loop, except that i have often more than one consumer, so I called them like controller loop - multiple task. The communication within this loops (tasks) are done by queue cluster with an enumerator and variant.
The indicted vi "gastimer.vi" was transfered from an older and more simply architecture. This vi works with sequence structure and a lot of local variables.
Since I'm testing sensor on their response to gas concentration I have 10 comports to which I'm listening in parallel.
What styles or archtiecture are prone to access violations? Where can they happened? where should I look more carefully in the code?
How can I use the desktop execution trace toolkit to get more information about the cause of the access violation?
Attached are two different lvlog but I guess with the same error source. In the second lvlog are two vi's named. What have they to do with the access violation error? What kind of information can i get from these lvlog files?
Last attachement shows a runtime fatal error which happens quite a bit frequently in the recent time when working with this project. Might there be a connection, propably a crashed vi, typedef or whatever?
Thanks for any help
U. Siegenthaler
Solved!
Go to Solution.
Attachments:
first.zip ‏203 KB
second.zip ‏40 KB
Fatalerror.PNG ‏21 KB

Have you checked your code to try to isolate any areas of possible memory leaks? I was able to find some discussion forums with similar problems. Check out the links below to see if any of these resources can be of assistance to you.
"Exception: Access violation (0xC0000005) at EIP=0xFDD76383"
http://forums.ni.com/t5/LabVIEW/Exception-Access-violation-0xC0000005-at-EIP-0xFDD76383/m-p/2257502
"Exception: access violation (0xc0000005) at EIP=0x00BD0984 "
http://forums.ni.com/t5/LabVIEW/Exception-access-violation-0xc0000005-at-EIP-0x00BD0984/m-p/2303864
"Access violation (0xC0000005)"
http://forums.ni.com/t5/LabVIEW/Access-violation-0xC0000005/m-p/2269694
Let me know what you find and if you have any other questions.
Best regards
Matijas

Java.exe Access Violation Error(URGENT)

Hi all,
I have created a application for my company. This application requires a user to login into the site by giving his userid/pwd. Once the person logs into the site, there is this error "Java.exe Access Violation Error" which pops up and terminates the Web Server.
My Login page is a HTML page which inturns calls a Jsp which authenticates the user.Once the authentication is completed, the user id is put into the session so i can check for the existence of user session on each subsequent page. After the user successfully logs in, the error pops up.
Please get back to me incase u have ever encountered this error and what might be the solution.
I am using Tomcat Webserver 3.2.3, Sql Server 7.0 as the Database Server, JDK1.3 .
Regards,
Yatin

As far as i remember i faced this problem when the memory of my pc was broken. So it may not be a problem of java or html code.

"Access Violation" error messages in Diadem 9.1

We have recently purchased Diadem V.9.1 and are encountering numerous "Access violation" errors as well as Runtime errors.The most frustrating aspect of trying to run this software are the constant crashes we are experiencing.
It is taking us 3X as long to process one subject as it should. I posted a request to NI technical help but I think it is the Thanksgiving holiday in the US.

Actually, DIAdem 9.1 is a very stable version. If you are continuously
experiencing crashes this might be due to some problems with your
computer hardware or configuration.
Is your PC matching the recommended system requirements as found in the
helpfile? What OS are you using, did you install the most recent
servicepacks?
Do you have similar problems with other software on this computer as
well? Unexpected system crashes often occure because of corrupt
RAM chips. DIAdem is using a lot of memory - so maybe you are accessing
regions that other programs dont use and - for that reason - see
the crashes only in DIAdem.
You are writing that the processing takes 3 times longer than expected.
How do you compare? Have you been using elder versions of DIAdem which
were faster, or are you comparing with the processing speed of another
computer?
There are some things I would do to try to improve the performance.
Check that you have at least 256MB RAM
Check that you are using Windows 2000 with servicepack 4 or XP with servicepack 1 at least
Reinstall DIAdem, use the version 9.1 SP2 instead of the installer you have been using. You can download this installer here.
Add servicepack 2b afterwards. The latter is a selfextracting zipfile
which has to be unpacked in the DIAdem directory while the first is a
complete DIAdem installer.
Replace the RAM modules of your PC.
You are welcome to post again if you dont get any further. In this case
please give some more information about the system such as CPU, OS,..
and the crashes. When do they occure? Is it a specific function or
module you are using when DIAdem crashes. What does the error messages
tell you about the module in which the exeptions occure?
Regards
Ingo Schumacher
Systems Engineer Sound&VibrationNational Instruments Germany

Access violation error with 1.4.0

Our client/server application (RMI) ran fine in 1.3.1. When we compiled and deployed with 1.4.0, an error of "access violation" were thrown by Windows NT or Windown 2000 at run time. Stack trace posted as below. Anyone has any ideas on the cause of it. Thanks you very much.
Application exception occurred:
App: (pid=346)
When: 6/18/2002 @ 17:18:40.166
Exception number: c0000005 (access violation)
----> System Information <----
Computer Name: PAUL
User Name: paul
Number of Processors: 1
Processor Type: x86 Family 6 Model 4 Stepping 2
Windows Version: 4.0
Current Build: 1381
Service Pack: 6
Current Type: Uniprocessor Free
Registered Organization: Quarry Technologies
Registered Owner: Quarry Technologies
----> Task List <----
0 Idle.exe
2 System.exe
20 SMSS.exe
24 CSRSS.exe
34 winlogon.exe
40 SERVICES.exe
43 LSASS.exe
68 SPOOLSS.exe
81 defwatch.exe
86 inetd32.exe
93 MGABG.exe
94 mgasc.exe
97 mgactrl.exe
99 rtvscan.exe
45 rtsserv.exe
112 RPCSS.exe
117 portserv.exe
127 wtxregds.exe
130 WinVNC.exe
137 PSTORES.exe
140 mstask.exe
144 NOPDB.exe
200 NDDEAGNT.exe
122 explorer.exe
186 systray.exe
187 mgaqdesk.exe
44 vptray.exe
113 point32.exe
91 realplay.exe
209 winampa.exe
211 loadqm.exe
213 aim.exe
215 msmsgs.exe
218 wftpd32.exe
192 OSA.exe
238 esserver.exe
240 vpexrt.exe
241 CMD.exe
63 vncviewer.exe
255 JBuilder.exe
277 DDHELP.exe
274 CMD.exe
287 CMD.exe
293 SYSLOGD.exe
313 SYSLOGD.exe
270 P4Win.exe
310 javaw.exe
346 javaw.exe
443 javaw.exe
433 javaw.exe
354 DRWTSN32.exe
0 _Total.exe
(00400000 - 00406000)
(77f60000 - 77fbe000) dll\ntdll.dbg
(77dc0000 - 77dff000) dll\advapi32.dbg
(77f00000 - 77f5e000) dll\kernel32.dbg
(77e70000 - 77ec5000) dll\user32.dbg
(77ed0000 - 77efc000) dll\gdi32.dbg
(77e10000 - 77e67000) dll\rpcrt4.dbg
(78000000 - 78046000)
(6d330000 - 6d330000)
(77fd0000 - 77ffa000) dll\winmm.dbg
(6bd00000 - 6bd14000) K:\DDK\lib\i386\free\cm-pci.dll
(6d1d0000 - 6d1d7000)
(6d300000 - 6d30d000)
(6d210000 - 6d228000)
(6d320000 - 6d32d000)
(6d2d0000 - 6d2dd000)
(776d0000 - 776d8000) dll\wsock32.dbg
(776b0000 - 776c4000) dll\ws2_32.dbg
(776a0000 - 776a7000) dll\ws2help.dbg
(74ff0000 - 74ffe000) dll\rnr20.dbg
(77bf0000 - 77bf7000) dll\rpcltc1.dbg
(77660000 - 7766f000) dll\msafd.dbg
(77690000 - 77699000) dll\wshtcpip.dbg
(6d2f0000 - 6d2f5000)
(6d000000 - 6d0f6000)
(77c00000 - 77c18000) drv\winspool.dbg
(76ab0000 - 76ab5000) dll\imm32.dbg
(77b20000 - 77bd7000) dll\ole32.dbg
(6d180000 - 6d1d0000)
State Dump for Thread Id 0x18b
eax=6d3fb8cc ebx=00000000 ecx=00762700 edx=00000000 esi=0000012c edi=00000000
eip=77f682db esp=0006fc10 ebp=0006fc34 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:00f6e617=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0006fc34 77f04f37 0000012c ffffffff 00000000 6d38b719 ntdll!NtWaitForSingleObject
0006fc7c 6d3b14c0 00000000 ffffffff 0076219c 007e0330 kernel32!WaitForSingleObject
----> Raw Stack Dump <----
0006fc10 a0 cc f1 77 2c 01 00 00 - 00 00 00 00 00 00 00 00 ...w,...........
0006fc20 50 05 7e 00 10 2f 76 00 - 30 03 7e 00 00 30 00 00 P.~../v.0.~..0..
0006fc30 04 01 00 00 7c fc 06 00 - 37 4f f0 77 2c 01 00 00 ....|...7O.w,...
0006fc40 ff ff ff ff 00 00 00 00 - 19 b7 38 6d 2c 01 00 00 ..........8m,...
0006fc50 ff ff ff ff 9c 21 76 00 - 10 2f 76 00 a0 21 76 00 .....!v../v..!v.
0006fc60 00 00 00 00 02 00 00 00 - 00 00 00 00 30 03 7e 00 ............0.~.
0006fc70 30 03 7e 00 10 2f 76 00 - 01 00 00 00 c0 fc 06 00 0.~../v.........
0006fc80 c0 14 3b 6d 00 00 00 00 - ff ff ff ff 9c 21 76 00 ..;m.........!v.
0006fc90 30 03 7e 00 30 03 7e 00 - 00 00 00 00 30 03 7e 00 0.~.0.~.....0.~.
0006fca0 d0 fc 06 00 05 86 36 6d - 5c 05 41 6d d8 fc 06 00 ......6m\.Am....
0006fcb0 00 00 00 00 00 00 00 00 - 75 85 36 6d 30 03 7e 00 ........u.6m0.~.
0006fcc0 d0 fc 06 00 b7 85 36 6d - 50 9c 77 00 30 03 7e 00 ......6mP.w.0.~.
0006fcd0 14 ff 06 00 d2 14 40 00 - bc 03 7e 00 56 00 00 00 ......@...~.V...
0006fce0 10 28 07 00 00 00 00 00 - 43 3a 5c 6a 32 73 64 6b .(......C:\j2sdk
0006fcf0 31 2e 34 2e 30 5c 6a 72 - 65 00 6a 61 76 61 77 2e 1.4.0\jre.javaw.
0006fd00 65 78 65 00 12 00 00 00 - a0 fe 06 00 00 e0 fd 7f exe.............
0006fd10 00 00 00 00 a9 a0 f6 77 - 9c fe 06 00 00 00 00 80 .......w........
0006fd20 70 fe 06 00 00 e0 fd 7f - 00 f0 fd 7f 00 00 00 00 p...............
0006fd30 5c 00 52 00 65 00 67 00 - 69 00 73 00 74 00 72 00 \.R.e.g.i.s.t.r.
0006fd40 79 00 5c 00 4d 00 61 00 - 63 00 68 00 69 00 6e 00 y.\.M.a.c.h.i.n.
State Dump for Thread Id 0x156
eax=02c29d90 ebx=007648d0 ecx=02c29d90 edx=00000009 esi=02c29d90 edi=26dbfd64
eip=6d3318d5 esp=26dbfc6c ebp=26dbfc88 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206
function: <nosymbols>
6d3318c0 8d4df0 lea ecx,[ebp-0x10] ss:27cbe68e=????????
6d3318c3 e875000000 call 6d33193d
6d3318c8 5f pop edi
6d3318c9 5e pop esi
6d3318ca c9 leave
6d3318cb c3 ret
6d3318cc 56 push esi
6d3318cd 8bf1 mov esi,ecx
6d3318cf 8b5604 mov edx,[esi+0x4] ds:03b28796=????????
6d3318d2 83c208 add edx,0x8
FAULT ->6d3318d5 8b4210 mov eax,[edx+0x10] ds:00efea0f=????????
6d3318d8 85c0 test eax,eax
6d3318da 7f25 jg 6d331901
6d3318dc 7d1b jge 6d3318f9
6d3318de 83c9ff or ecx,0xff
6d3318e1 6a04 push 0x4
6d3318e3 2bc8 sub ecx,eax
6d3318e5 8b4608 mov eax,[esi+0x8] ds:03b28796=????????
6d3318e8 d3e0 shl eax,cl
6d3318ea 8b4a4c mov ecx,[edx+0x4c] ds:00efea0f=????????
6d3318ed 8d440807 lea eax,[eax+ecx+0x7] ds:03b28797=????????
6d3318f1 59 pop ecx
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26dbfc88 6d34d03a 02c29d90 02c37c48 22fc8df4 02c37c48 <nosymbols>
State Dump for Thread Id 0x160
eax=00000004 ebx=00000000 ecx=052c2748 edx=00000000 esi=00000320 edi=00000000
eip=77f682db esp=26dffc10 ebp=26dffc34 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:27cfe617=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26dffc34 77f04f37 00000320 ffffffff 00000000 6d38d2fe ntdll!NtWaitForSingleObject
26dffc7c 6d39ead0 00000000 00000000 00000001 00767d30 kernel32!WaitForSingleObject
State Dump for Thread Id 0x11a
eax=00000004 ebx=00000000 ecx=052c2a60 edx=00000000 esi=00000430 edi=00000000
eip=77f682db esp=26e3fbd4 ebp=26e3fbf8 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:27d3e5db=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26e3fbf8 77f04f37 00000430 ffffffff 00000000 6d38d2fe ntdll!NtWaitForSingleObject
26e3fc40 6d39ead0 00000000 00000000 00000001 007670b0 kernel32!WaitForSingleObject
----> Raw Stack Dump <----
26e3fbd4 a0 cc f1 77 30 04 00 00 - 00 00 00 00 00 00 00 00 ...w0...........
26e3fbe4 b0 70 76 00 4c b3 75 00 - 10 87 76 00 30 04 00 00 .pv.L.u...v.0...
26e3fbf4 2a 14 39 6d 40 fc e3 26 - 37 4f f0 77 30 04 00 00 *.9m@..&7O.w0...
26e3fc04 ff ff ff ff 00 00 00 00 - fe d2 38 6d 30 04 00 00 ..........8m0...
26e3fc14 ff ff ff ff 00 00 00 00 - 40 27 2c 05 b0 70 76 00 ........@',..pv.
26e3fc24 00 00 00 00 b0 70 76 00 - 30 04 00 00 00 00 00 00 .....pv.0.......
26e3fc34 f4 8f 76 00 02 00 00 00 - 00 00 00 00 64 fc e3 26 ..v.........d..&
26e3fc44 d0 ea 39 6d 00 00 00 00 - 00 00 00 00 01 00 00 00 ..9m............
26e3fc54 b0 70 76 00 40 27 2c 05 - b0 70 76 00 70 3c b3 22 .pv.@',..pv.p<."
26e3fc64 84 fc e3 26 aa e7 36 6d - 00 88 76 00 00 00 00 00 ...&..6m..v.....
26e3fc74 00 00 00 00 b0 70 76 00 - b0 70 76 00 ac 3c b3 22 .....pv..pv..<."
26e3fc84 b8 fc e3 26 0d 96 ab 00 - b0 70 76 00 d0 fc e3 26 ...&.....pv....&
26e3fc94 00 00 00 00 00 00 00 00 - 9c fc e3 26 00 00 00 00 ...........&....
26e3fca4 d0 fc e3 26 c8 52 b7 22 - 00 00 00 00 70 3c b3 22 ...&.R."....p<."
26e3fcb4 c8 fc e3 26 f8 fc e3 26 - 9f 2d ab 00 00 00 00 00 ...&...&.-......
26e3fcc4 51 76 ab 00 00 00 00 00 - 00 00 00 00 40 27 2c 05 Qv..........@',.
26e3fcd4 03 00 00 00 40 27 2c 05 - d4 fc e3 26 34 0a b8 22 ....@',....&4.."
26e3fce4 20 fd e3 26 78 0c b8 22 - 00 00 00 00 c8 09 b8 22 ..&x.."......."
26e3fcf4 18 fd e3 26 40 fd e3 26 - 76 2e ab 00 00 00 00 00 ...&@..&v.......
26e3fd04 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
State Dump for Thread Id 0x1ca
eax=00000000 ebx=00000000 ecx=00000001 edx=00000000 esi=26e7ff28 edi=00000000
eip=77f6791f esp=26e7ff14 ebp=26e7ff30 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206
function: NtDelayExecution
77f67914 b827000000 mov eax,0x27
77f67919 8d542404 lea edx,[esp+0x4] ss:27d7e91b=????????
77f6791d cd2e int 2e
77f6791f c20800 ret 0x8
77f67922 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26e7ff30 77f1cebe 0000000a 00000000 6d39138c 0000000a ntdll!NtDelayExecution
26e7ff5c 6d3af3f5 0076a380 0000000a 00000000 00000000 kernel32!Sleep
State Dump for Thread Id 0x1c8
eax=78002432 ebx=00000000 ecx=6d38ac38 edx=00000000 esi=00000120 edi=00000000
eip=77f682db esp=26ebfef4 ebp=26ebff18 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:27dbe8fb=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26ebff18 77f04f37 00000120 ffffffff 00000000 6d38b6bf ntdll!NtWaitForSingleObject
26ebff60 6d3af53e 00000001 ffffffff 22b40f78 0076a210 kernel32!WaitForSingleObject
State Dump for Thread Id 0x15e
eax=78002432 ebx=00000000 ecx=0006fa28 edx=00000000 esi=0000069c edi=00000000
eip=77f682db esp=26effe3c ebp=26effe60 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:27dfe843=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26effe60 77f04f37 0000069c ffffffff 00000000 6d390d49 ntdll!NtWaitForSingleObject
26effea0 6d390d8d 00000001 6d38e927 0076b370 0076b2c0 kernel32!WaitForSingleObject
State Dump for Thread Id 0x1c4
eax=00000001 ebx=00000000 ecx=26f3fc28 edx=00000000 esi=000001f4 edi=00000000
eip=77f682db esp=26f3fe80 ebp=26f3fea4 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:27e3e887=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
26f3fea4 77f04f37 000001f4 ffffffff 00000000 6d38b719 ntdll!NtWaitForSingleObject
26f3feec 6d3c1f67 00000000 ffffffff 0076b190 01e37000 kernel32!WaitForSingleObject
*----> Raw Stack Dump <----*
26f3fe80 a0 cc f1 77 f4 01 00 00 - 00 00 00 00 00 00 00 00 ...w............
26f3fe90 10 c3 76 00 50 29 76 00 - 30 b0 76 00 30 b0 76 00 ..v.P)v.0.v.0.v.
26f3fea0 e0 c3 76 00 ec fe f3 26 - 37 4f f0 77 f4 01 00 00 ..v....&7O.w....
26f3feb0 ff ff ff ff 00 00 00 00 - 19 b7 38 6d f4 01 00 00 ..........8m....
26f3fec0 ff ff ff ff 90 b1 76 00 - 90 b1 76 00 50 29 76 00 ......v...v.P)v.
26f3fed0 00 00 00 00 02 00 00 00 - cc 03 00 00 30 b0 76 00 ............0.v.
26f3fee0 30 b0 76 00 50 29 76 00 - 01 00 00 00 00 00 00 00 0.v.P)v.........
26f3fef0 67 1f 3c 6d 00 00 00 00 - ff ff ff ff 90 b1 76 00 g.<m..........v.
26f3ff00 00 70 e3 01 40 ff f3 26 - 00 00 00 00 46 29 3c 6d .p..@..&....F)<m
26f3ff10 e0 b0 76 00 30 b0 76 00 - 80 c2 76 00 30 b0 76 00 ..v.0.v...v.0.v.
26f3ff20 e0 c3 76 00 00 d8 76 00 - 08 d8 76 00 f4 db 76 00 ..v...v...v...v.
26f3ff30 54 ff f3 26 30 b0 76 00 - 30 b0 76 00 08 d8 76 00 T..&0.v.0.v...v.
26f3ff40 6c ff f3 26 02 f9 3a 6d - 30 b0 76 00 30 b0 76 00 l..&..:m0.v.0.v.
26f3ff50 30 b0 76 00 30 b0 76 00 - e0 c3 76 00 00 d8 76 00 0.v.0.v...v...v.
26f3ff60 08 d8 76 00 f4 db 76 00 - c0 c3 76 00 84 ff f3 26 ..v...v...v....&
26f3ff70 d2 f8 3a 6d 18 88 b5 02 - 30 b0 76 00 cb fe 38 6d ..:m....0.v...8m
26f3ff80 80 c2 76 00 b8 ff f3 26 - 8d 24 00 78 30 b0 76 00 ..v....&.$.x0.v.
26f3ff90 18 88 b5 02 d0 f8 06 00 - 80 c2 76 00 ff ff ff ff ..........v.....
26f3ffa0 90 ff f3 26 91 76 11 80 - dc ff f3 26 6a f5 00 78 ...&.v.....&j..x
26f3ffb0 d0 33 03 78 00 00 00 00 - ec ff f3 26 de 4e f0 77 .3.x.......&.N.w
State Dump for Thread Id 0x1ac
eax=00000004 ebx=00000000 ecx=02b73c40 edx=00000000 esi=00000500 edi=2717fbfc
eip=77f682db esp=2717fbe0 ebp=2717fc04 iopl=0 ov up ei pl nz na pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000a03
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:2807e5e7=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
2717fc04 77f04f37 00000500 000493e0 00000000 6d38d2fe ntdll!NtWaitForSingleObject
2717fc4c 6d39ead0 000493e0 00000000 00000001 0077f5e0 kernel32!WaitForSingleObject
*----> Raw Stack Dump <----*
2717fbe0 a0 cc f1 77 00 05 00 00 - 00 00 00 00 fc fb 17 27 ...w...........'
2717fbf0 e0 f5 77 00 ec b2 75 00 - f0 f4 77 00 00 a2 2f 4d ..w...u...w.../M
2717fc00 ff ff ff ff 4c fc 17 27 - 37 4f f0 77 00 05 00 00 ....L..'7O.w....
2717fc10 e0 93 04 00 00 00 00 00 - fe d2 38 6d 00 05 00 00 ..........8m....
2717fc20 e0 93 04 00 00 00 00 00 - 38 b1 32 05 e0 f5 77 00 ........8.2...w.
2717fc30 00 00 00 00 e0 f5 77 00 - 00 05 00 00 00 00 00 00 ......w.........
2717fc40 02 00 00 00 02 00 00 00 - 00 00 00 00 70 fc 17 27 ............p..'
2717fc50 d0 ea 39 6d e0 93 04 00 - 00 00 00 00 01 00 00 00 ..9m............
2717fc60 e0 f5 77 00 38 b1 32 05 - e0 f5 77 00 70 3c b3 22 ..w.8.2...w.p<."
2717fc70 90 fc 17 27 aa e7 36 6d - a0 e3 76 00 e0 93 04 00 ...'..6m..v.....
2717fc80 00 00 00 00 e0 f5 77 00 - e0 f5 77 00 ac 3c b3 22 ......w...w..<."
2717fc90 c4 fc 17 27 0d 96 ab 00 - e0 f5 77 00 dc fc 17 27 ...'......w....'
2717fca0 e0 93 04 00 00 00 00 00 - a8 fc 17 27 ac 3c b3 22 ...........'.<."
2717fcb0 dc fc 17 27 c8 52 b7 22 - 00 00 00 00 70 3c b3 22 ...'.R."....p<."
2717fcc0 d4 fc 17 27 0c fd 17 27 - 9f 2d ab 00 00 00 00 00 ...'...'.-......
2717fcd0 51 76 ab 00 e0 93 04 00 - 00 00 00 00 c0 ae 32 05 Qv............2.
2717fce0 01 00 00 00 00 00 00 00 - 01 00 00 00 c0 ae 32 05 ..............2.
2717fcf0 e0 fc 17 27 b9 c8 d6 22 - 3c fd 17 27 60 ca d6 22 ...'..."<..'`.."
2717fd00 00 00 00 00 b0 c7 d6 22 - 3c fd 17 27 5c fd 17 27 ......."<..'\..'
2717fd10 9f 2d ab 00 00 00 00 00 - 00 00 00 00 e8 a7 66 05 .-............f.
State Dump for Thread Id 0x1be
eax=02b621d8 ebx=7766b100 ecx=00000001 edx=00000000 esi=0007b2b8 edi=00000568
eip=77f682db esp=271bf6a4 ebp=271bf6f8 iopl=0 nv up ei ng nz ac pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000293
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:280be0ab=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
271bf6f8 77661202 00000568 0000052c 00000002 00000004 ntdll!NtWaitForSingleObject
271bfb60 776bb101 0000052c 271bfc00 271bfc10 00000000 msafd!<nosymbols>
271bfb98 776bb08c 0000052c 271bfc00 271bfc10 00000000 ws2_32!WSAAccept
271bfc14 00ab960d 0076fe84 271bfc58 271bfc54 271bfc28 ws2_32!accept
*----> Raw Stack Dump <----*
271bf6a4 ce 89 66 77 68 05 00 00 - 01 00 00 00 d0 f6 1b 27 ..fwh..........'
271bf6b4 d4 b2 07 00 bc b2 07 00 - 1a 00 00 00 00 44 be ab .............D..
271bf6c4 0d 17 c2 01 ff ff ff ff - ff ff ff 7f ff ff ff ff ................
271bf6d4 ff ff ff 7f 00 00 00 00 - 58 ae 07 00 ad 1f 6a 77 ........X.....jw
271bf6e4 d8 11 66 77 2c 05 00 00 - 00 00 00 00 00 00 00 00 ..fw,...........
271bf6f4 00 00 00 00 60 fb 1b 27 - 02 12 66 77 68 05 00 00 ....`..'..fwh...
271bf704 2c 05 00 00 02 00 00 00 - 04 00 00 00 00 00 00 00 ,...............
271bf714 18 69 07 00 28 88 07 00 - 66 00 02 00 00 00 00 00 .i..(...f.......
271bf724 00 00 00 00 00 00 00 00 - 08 00 00 00 00 00 00 00 ................
271bf734 00 00 00 00 00 00 00 00 - 00 00 00 00 e9 03 00 00 ................
271bf744 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf754 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf764 00 00 00 00 02 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf774 01 00 00 00 06 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf784 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf794 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf7a4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf7b4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf7c4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271bf7d4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
State Dump for Thread Id 0x1ce
eax=00ab017d ebx=7766b100 ecx=00000011 edx=00000000 esi=0007b548 edi=000005cc
eip=77f682db esp=271ff6a4 ebp=271ff6f8 iopl=0 nv up ei ng nz ac pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000293
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:280fe0ab=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
271ff6f8 77661202 000005cc 00000590 00000002 00000004 ntdll!NtWaitForSingleObject
271ffb60 776bb101 00000590 271ffc00 271ffc10 00000000 msafd!<nosymbols>
271ffb98 776bb08c 00000590 271ffc00 271ffc10 00000000 ws2_32!WSAAccept
271ffc14 00ab960d 00777e44 271ffc58 271ffc54 271ffc28 ws2_32!accept
*----> Raw Stack Dump <----*
271ff6a4 ce 89 66 77 cc 05 00 00 - 01 00 00 00 d0 f6 1f 27 ..fw...........'
271ff6b4 64 b5 07 00 4c b5 07 00 - 1a 00 00 00 f0 7a 09 b5 d...L........z..
271ff6c4 0d 17 c2 01 ff ff ff ff - ff ff ff 7f ff ff ff ff ................
271ff6d4 ff ff ff 7f 00 00 00 00 - 84 ae 07 00 ad 1f 6a 77 ..............jw
271ff6e4 d8 11 66 77 90 05 00 00 - 00 00 00 00 00 00 00 00 ..fw............
271ff6f4 00 00 00 00 60 fb 1f 27 - 02 12 66 77 cc 05 00 00 ....`..'..fw....
271ff704 90 05 00 00 02 00 00 00 - 04 00 00 00 00 00 00 00 ................
271ff714 50 aa 07 00 28 88 07 00 - 66 00 02 00 00 00 00 00 P...(...f.......
271ff724 00 00 00 00 00 00 00 00 - 08 00 00 00 00 00 00 00 ................
271ff734 00 00 00 00 00 00 00 00 - 00 00 00 00 e9 03 00 00 ................
271ff744 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff754 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff764 00 00 00 00 02 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff774 01 00 00 00 06 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff784 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff794 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff7a4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff7b4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff7c4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
271ff7d4 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
State Dump for Thread Id 0x1c2
eax=00ab017d ebx=00000000 ecx=00000019 edx=00000000 esi=000005b0 edi=00000000
eip=77f682db esp=2723fba0 ebp=2723fbc4 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:2813e5a7=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
2723fbc4 77f04f37 000005b0 ffffffff 00000000 6d38d2fe ntdll!NtWaitForSingleObject
2723fc0c 6d39ead0 00000000 00000000 00000001 00780730 kernel32!WaitForSingleObject
*----> Raw Stack Dump <----*
2723fba0 a0 cc f1 77 b0 05 00 00 - 00 00 00 00 00 00 00 00 ...w............
2723fbb0 30 07 78 00 2c b3 75 00 - 00 07 78 00 b0 05 00 00 0.x.,.u...x.....
2723fbc0 2a 14 39 6d 0c fc 23 27 - 37 4f f0 77 b0 05 00 00 *.9m..#'7O.w....
2723fbd0 ff ff ff ff 00 00 00 00 - fe d2 38 6d b0 05 00 00 ..........8m....
2723fbe0 ff ff ff ff 00 00 00 00 - 38 ae b5 02 30 07 78 00 ........8...0.x.
2723fbf0 00 00 00 00 30 07 78 00 - b0 05 00 00 00 00 00 00 ....0.x.........
2723fc00 2c b3 75 00 02 00 00 00 - 00 00 00 00 30 fc 23 27 ,.u.........0.#'
2723fc10 d0 ea 39 6d 00 00 00 00 - 00 00 00 00 01 00 00 00 ..9m............
2723fc20 30 07 78 00 38 ae b5 02 - 30 07 78 00 70 3c b3 22 0.x.8...0.x.p<."
2723fc30 50 fc 23 27 aa e7 36 6d - 20 14 78 00 00 00 00 00 P.#'..6m .x.....
2723fc40 00 00 00 00 30 07 78 00 - 30 07 78 00 ac 3c b3 22 ....0.x.0.x..<."
2723fc50 84 fc 23 27 0d 96 ab 00 - 30 07 78 00 9c fc 23 27 ..#'....0.x...#'
2723fc60 00 00 00 00 00 00 00 00 - 68 fc 23 27 ac 3c b3 22 ........h.#'.<."
2723fc70 9c fc 23 27 c8 52 b7 22 - 00 00 00 00 70 3c b3 22 ..#'.R."....p<."
2723fc80 94 fc 23 27 c4 fc 23 27 - 9f 2d ab 00 00 00 00 00 ..#'..#'.-......
2723fc90 51 76 ab 00 00 00 00 00 - 00 00 00 00 08 ac 32 05 Qv............2.
2723fca0 01 00 00 00 08 ac 32 05 - a0 fc 23 27 34 0a b8 22 ......2...#'4.."
2723fcb0 ec fc 23 27 78 0c b8 22 - 00 00 00 00 c8 09 b8 22 ..#'x.."......."
2723fcc0 e4 fc 23 27 0c fd 23 27 - 76 2e ab 00 00 00 00 00 ..#'..#'v.......
2723fcd0 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
State Dump for Thread Id 0x1cd
eax=00000004 ebx=00000000 ecx=22d8b980 edx=00000000 esi=000005c0 edi=2727fc48
eip=77f682db esp=2727fc2c ebp=2727fc50 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:2817e633=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
2727fc50 77f04f37 000005c0 0000ea60 00000000 6d38d2fe ntdll!NtWaitForSingleObject
2727fc98 6d39ead0 0000ea60 00000000 00000001 00781270 kernel32!WaitForSingleObject
*----> Raw Stack Dump <----*
2727fc2c a0 cc f1 77 c0 05 00 00 - 00 00 00 00 48 fc 27 27 ...w........H.''
2727fc3c 70 12 78 00 6c b3 75 00 - c0 11 78 00 00 ba 3c dc p.x.l.u...x...<.
2727fc4c ff ff ff ff 98 fc 27 27 - 37 4f f0 77 c0 05 00 00 ......''7O.w....
2727fc5c 60 ea 00 00 00 00 00 00 - fe d2 38 6d c0 05 00 00 `.........8m....
2727fc6c 60 ea 00 00 00 00 00 00 - 98 d3 32 05 70 12 78 00 `.........2.p.x.
2727fc7c 00 00 00 00 70 12 78 00 - c0 05 00 00 00 00 00 00 ....p.x.........
2727fc8c 4b 96 34 6d 02 00 00 00 - 00 00 00 00 bc fc 27 27 K.4m..........''
2727fc9c d0 ea 39 6d 60 ea 00 00 - 00 00 00 00 01 00 00 00 ..9m`...........
2727fcac 70 12 78 00 98 d3 32 05 - 70 12 78 00 70 3c b3 22 p.x...2.p.x.p<."
2727fcbc dc fc 27 27 aa e7 36 6d - 20 28 78 00 60 ea 00 00 ..''..6m (x.`...
2727fccc 00 00 00 00 70 12 78 00 - 70 12 78 00 ac 3c b3 22 ....p.x.p.x..<."
2727fcdc 10 fd 27 27 0d 96 ab 00 - 70 12 78 00 28 fd 27 27 ..''....p.x.(.''
2727fcec 60 ea 00 00 00 00 00 00 - f4 fc 27 27 00 00 00 00 `.........''....
2727fcfc 28 fd 27 27 c8 52 b7 22 - 00 00 00 00 70 3c b3 22 (.''.R."....p<."
2727fd0c 20 fd 27 27 50 fd 27 27 - 9f 2d ab 00 00 00 00 00 .''P.''.-......
2727fd1c 51 76 ab 00 60 ea 00 00 - 00 00 00 00 98 d3 32 05 Qv..`.........2.
2727fd2c 03 00 00 00 98 d3 32 05 - 2c fd 27 27 92 ea d8 22 ......2.,.''..."
2727fd3c 74 fd 27 27 28 ed d8 22 - 00 00 00 00 20 ea d8 22 t.''(..".... .."
2727fd4c 74 fd 27 27 84 fd 27 27 - 7d 01 ab 00 00 00 00 00 t.''..''}.......
2727fd5c 00 00 00 00 00 00 00 00 - 00 00 00 00 98 d3 32 05 ..............2.
State Dump for Thread Id 0x1b8
eax=00000004 ebx=00000000 ecx=2323ba90 edx=00000000 esi=00000924 edi=276cfc38
eip=77f682db esp=276cfc1c ebp=276cfc40 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:285ce623=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
276cfc40 77f04f37 00000924 00007530 00000000 6d38d2fe ntdll!NtWaitForSingleObject
276cfc88 6d39ead0 00007530 00000000 00000001 007dc330 kernel32!WaitForSingleObject
State Dump for Thread Id 0x18a
eax=00000004 ebx=00000000 ecx=02bbf9a0 edx=00000000 esi=000009b0 edi=00000000
eip=77f682db esp=2770fbe0 ebp=2770fc04 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: NtWaitForSingleObject
77f682d0 b8c5000000 mov eax,0xc5
77f682d5 8d542404 lea edx,[esp+0x4] ss:2860e5e7=????????
77f682d9 cd2e int 2e
77f682db c20c00 ret 0xc
77f682de 8bc0 mov eax,eax
----> Stack Back Trace <----
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
2770fc04 77f04f37 000009b0 ffffffff 00000000 6d38d2fe ntdll!NtWaitForSingleObject
2770fc4c 6d39ead0 00000000 00000000 00000001 007dda00 kernel32!WaitForSingleObject
----> Raw Stack Dump <----
2770fbe0 a0 cc f1 77 b0 09 00 00 - 00 00 00 00 00 00 00 00 ...w............
2770fbf0 00 da 7d 00 ec b3 75 00 - 80 c1 7d 00 b0 09 00 00 ..}...u...}.....
2770fc00 2a 14 39 6d 4c fc 70 27 - 37 4f f0 77 b0 09 00 00 *.9mL.p'7O.w....
2770fc10 ff ff ff ff 00 00 00 00 - fe d2 38 6d b0 09 00 00 ..........8m....
2770fc20 ff ff ff ff 00 00 00 00 - e8 ef bb 02 00 da 7d 00 ..............}.
2770fc30 00 00 00 00 00 da 7d 00 - b0 09 00 00 00 00 00 00 ......}.........
2770fc40 ec b3 75 00 02 00 00 00 - 00 00 00 00 70 fc 70 27 ..u.........p.p'
2770fc50 d0 ea 39 6d 00 00 00 00 - 00 00 00 00 01 00 00 00 ..9m............
2770fc60 00 da 7d 00 e8 ef bb 02 - 00 da 7d 00 70 3c b3 22 ..}.......}.p<."
2770fc70 90 fc 70 27 aa e7 36 6d - 20 dc 7d 00 00 00 00 00 ..p'..6m .}.....
2770fc80

I am seeing exactly the same error. I started seeing it after we started making extensive use of introspection in our code. It happens repeatably when we are load testing our software.

Access violation error message 'WMP54GSv1_1.exe'

Hi,
Each time I start my Compaq Presario, I get the following Error message: "Access violation at address 004A55F7 in module ‘WMP54GSv1_1.exe’. Read of address 00000000." I cannot view wireless networks or access internet.
I have a Linksys wireless card in my PC and it just came back from HP for faulty on/off switch servicing.
How do I rememdy this situation?
Thanks!!
TJ

The drivers you need to download are your correct product model number and version which you may find underneath the card itself on one of the stickers... or with the card box (if you still have it)
After you have downloaded them, just 1st transfer them into the non-working PC... the file might be zipped... so you might need to unzip them first... you then uninstall the card from the PC... either go to add/remove programs and add/remove hardware....
Then restart the PC... after you restart it, you will probably be prompted for a "found new hardware wizard"... just go through the process... if it asks your for the drivers.. select "specify a location and specify the folder where you actually unzipped the files...
Sounds lengthy I know...

Access violation error

Hi, When starting my computer I get the following error messages - "Access violation at address ___________ in module____________. Read of address ________________." Any suggestions for quick fixes for these annoying messages would be greatly appreciated. Thanks, mred

The two most common causes for "Access violation" are:
1) Windows is not up to date, and/or
2) You are running a very old program
Message Edited by toomanydonuts on 07-18-2007 02:57 AM

EvaluatingTteststand 4.2.1: Null pointer access violation (error 17502) when attempting to use a mixed-mode std::map / boost shared_ptr class contained in a DLL through an interface from a different DLL

Hi there.
I have been working on a test system which will potentially have TestStand at its core, and downloaded/installed the 4.2.1 evaluation. Current details from the information dialog are:
TestStand Engine version 4.2.1 (4.2.1.83)
Sequence Editor Verison 4.2.1.83
The system will drive mobile radio devices using RS232 serial interfaces, usnig a variety of serial protocols (Hayes, and a couple of proprietary binary protocols for other work).
We already have in existence a soak tester, written in VS2005 with MFC unmanaged DLLs and also managed DLLs, which are mixed up together to provide different aspects of the functionality required for the binary protocols.
I have created:
1. a "master wrapper" DLL for the constellation of other DLLs - this offers up a simple C-API interface which I hope TestStand will use. It's called "SerialSessionMgr.dll""
2. a mixed managed / unmanaged "IJW" (it just works) DLL which wraps up the binary logging protocol control interfaces, which are entirely in managed C++/CLI: the "master wrapper" DLL calls into this through an unmanaged interface to create instances of the CLI-compiled class which interfaces to the underlying managed DLLs imlpementing the logging protocol. This is called "WinTseInterface.dll".
Before I started evaluating TestStand, I knocked up a test harness using CPPUnit / MFC, with which I was able to test SerialSessionMgr.dll and its' use of WinTseInterface.dll and verify they worked. The harness loads the DLL dynamically at run-time using AfxLoadLibrary() to try to emulate the way TestStand uses it.
When we open a
TSE session:
The SerialSessionManager makes a call to the
WinTseInterface.dll to "create" a logging instance. The instance is
created in a std::map which is held by the CWinApp derived class, this map
contains boost::shared_ptr of the class which works with a managed class. So we
have a call trace: Client
app->SerialSessionManager{TseStartSession()}->WinTseInterface{WINTSE_GetWinTseBridge()} - WINTSE_GetWinTseBridge()
just creates a new instance of the unmanaged class which interfaces through to
the managed CLI/C++ class beneath, and returns the address to the
SerialSessionManager, which stores it.
The SerialSessioManager actually initialises the WinTseBridge using a method of a C++ pure virtual interface class to the class in the std::map in the WinTseInterface DLL
implements. The initialise call passes miscellaneous details and actually calls
"gcnew" to create the managed class which interfaces to the
underlying managed DLLs which implement the logging protocol.
My logs of the DLL loading as seen in VS2005 debug output are attached this message as PDFs
While trying to fix this, I have tried:
Enhancing the WinTseInterface DLL so it manually loads all the other assemblies in the logging system, including the managed portion of WinTseInterface itself (no effect)
All the different options for the way the C DLL adapter loads and unloads the DLL in the DLL adapter steptype in TestStand
I've even tried calling directly into the WinTseInterface DLL before trying any SerialSessionManager DLL calls to try to load the WinTseInterface DLL completely beforehand
and I cannot stop this exception.
It seems like the object is created in the WinTseInterface DLL OK (I have debugged the creation step which runs for WINTSE_GetWinTseBridge() and the object is created OK) when the SerialSessionManager makes the call, but when it calls the first managed function, which creates the managed object, the DLL is reloaded as managed - I suspect this causes the object to be destroyed or overwritten, and thus the call to initialise bombs with null pointer violation.
Have I done something obviously wrong, and what other approaches can I take?
Does TestStand 4.2.1 have issues with driving DLLs which use managed/unmanaged DLLs beneath them?
My nuclear option is to throw the WinTseInterface DLL out completely and wrap up the managed C++ CLI code in a new interface, entirely managed, and use the TestStand ".Net" adaptor to drive that, creating my step library to run to that directly. This isn't ideal as I have some co-ordination of the protocols which is implemented in the SerialSessionMgr DLL.
I hope someone can help. This one's low level, dirty and a stumper to me.
Many thanks to the NI community. This is my first posting!
Solved!
Go to Solution.
Attachments:
CPPUnit Test Harness DLL load debug output.pdf ‏18 KB
TestStand DLL load & crash debug output.pdf ‏43 KB

Hi there Ray.
First - many thanks for engaging with this thorny problem. Love the avatar BTW.
I've been using the C/C++ DLL adapter: the original premise of the Serial Session Manager DLL was to provide a simple C type functional interface, using simple data types, so that TestStand would be able to drive the underlying functionality easily through a single DLL.
Seeing as you've been kind enough to respond, I should explain the makeup of the DLLs a little more, I think.
The SerialSessionManager (SSMgr) DLL uses C++ and MFC internally. This is the DLL which TestStand calls into directly through the C/C++ adapter. This DLL does have one odd feature though - because the it uses the Windows Multimedia Timer (implemented in WinMM.dll) I had to artificially create a scenario where it would load the .Net mscoree DLL _before_ it loads WinMM.dll - (http://connect.microsoft.com/VisualStudio/feedback/details/329819/freelibrary-in-the-winmm-dlls-modu...), basically WinMM.dll's init code gets rather upset when .Net DLLs load, which causes the entire executable to be unloaded with subsequent crashes.
To work around this crash, the SSMgr has a single, completely empty, file which is compiled for CLR, effectively forcing a dependency into the DLL on the .Net subsystems and turning the DLL into a "IJW" binary. The resulting DLL doesn't actually have any executable managed .Net assemblies, but I'm guessing that it does contain enough .Net related stubs and information that when the DLL is loaded, mscoree.dll loads before WinMM.dll - and this means the system doesn't crash.
Now, on to the WinTseInterface DLL. My initial description of this little software system was done in something of a hurry.
This DLL is the C++/CLI "IJW" DLL which actually contains managed and unmanaged code. Underneath the WinTseInterface DLL is another system of (this time exclusively C++/CLI) DLL assemblies which implement the TSE protocol interpretation system.
When the SSMgr DLL needs to start a TSE protocol session, it calls a C-API function in the WinTseInterface which creates a new CWinTseBridge class. Here's the steps in a little more detail:
SSMgr DLL calls WINTSE_GetWinTseBridge(), passing in the name of the device which needs it (this is used to put the new WinTseBridge into a std::map in the WinTseInterface DLL) - this call runs just fine, and returns the address of the CWinTseBridge C++ object. This is stored in the SSMgr, because the CWinTseBridge class implements a pure virtual interface which is used by the SSMgr as a way of accessing the CWinTseBridge methods.
We now use the address from (1) to make a call to CWinTseBridge::Initialise(), passing some basic configuration details.
I've run VS2005 debug on the Sequence Editor when running the test, and done F11 step-throughs of the code loading each parameter in the Initialise() call onto the stack, and what appears to happen is that when the call is made, the whole lot steps off into oblivion (a reference to 0x00000000 is made, I think).
Do you think it's worth trying to get this approach to work? It would be useful to retain the control surface in the top of the SSMgr as there is co-ordination of the protocols within the logic of that component. If I move the Wintse control out into a separate managed DLL I may not have that co-ordination (this might be overcome with some design, as I've confirmed that it is possible to "reach into" the WinTseInterface DLL with TestStand and create and use managed objects from assemblies contained within).
Are there any known issues with this version of TestStand using C/C++ CLI IJW DLLs? I haven't found much out there on the web.
Attachments:
Tse_Test.seq ‏7 KB

Labview 2012 Runtime Application Crash: Access Violation Error

hi All,
my rather large app that I been develping over teh last few years has recently been crashing.
I do not know if it is since I began compiling it in LV2012 SP1 that the problem occurred or I have some programming error
that I cannot track down.
It use to run with uptimes over months, even with some memory leaks.
If I monitor using Task Manager there is no decernable increase in memory usage.
It crashes on two different systems - both running Windows XP.
The developer version running in LabVIEW 2012 f5 ( Windows XP ) does not crash. Only the runtime version crashes.
It also crashes either if the program sits idle for a few days - 5 or so ( memeory footprint stable ), or if it is used extensively to actively gather and control several instruements ( memory increase matches data size increase )
It does call several external API via ActiveX to spawn off processes, however from the lvlog.txt it seems the crashing is a simple open file that uses the NI supplied String to Config.vi.
I have double/triple check my code and I close any refernces open by the calling vi.
I am sure how to read teh mini-dump files so if someone can look at these it would be apreciated
thanks
Michael
Here are two crash logs:
Attachments:
fde86f7f-a024-417d-ac1c-d38b2e9a41e3.zip ‏61 KB
4f75c413-793d-46db-b66c-889a2f2daf69.zip ‏59 KB
00660fb7-749d-4af5-bcb1-ac5cad73a5cb.zip ‏56 KB

Hi Michael,
It's tough to tell what's going on, especially since it seems like you've really covered your bases! I'm curious about the fact that you don't see the crashes in LabVIEW (LV), just in the Run-Time Engine (RTE). Have you ever tried running it in LV for an extended period of time?
Also, do you have any loops in your program? Perhaps shrinking any waits that might be present and allowing your program to run faster would decrease the amount of time to see these errors from days to shorter.
In the future, when you get a dump file, submit it to our R&D department. It then pops up on a website that allows me to read them. I can also use win debug but that will take me a bit, so I'll have to get back to you on that.
Also, if you could take a picture of the error, that would help as well.
Julian R.
Applications Engineer
National Instruments

How to address access violation error message

Hi Experts,
I got message as
~Errors in file d:\oracle\product\10.2.0\admin\sale\bdump\sale_p003_5996.trc:~ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_kxsdcbc+506] [PC:0x8AAE62] [ADDR:0x18] [UNABLE_TO_READ] []~ORA-00600: internal error code, arguments: [5351], [4425995], [1712], [], [], [], [], []~
What means about this message?
What do I need to do?
our system as oracle10gR2 in window 2003
Thank
Jim

user589812 wrote:
Hi Experts,
I got message as
~Errors in file d:\oracle\product\10.2.0\admin\sale\bdump\sale_p003_5996.trc:~ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_kxsdcbc+506] [PC:0x8AAE62] [ADDR:0x18] [UNABLE_TO_READ] []~ORA-00600: internal error code, arguments: [5351], [4425995], [1712], [], [], [], [], []~
What means about this message?
What do I need to do?
our system as oracle10gR2 in window 2003
Thank
Jimora-07445 and ora-0600 are deep internal errors. You need to go to MetaLink, where they have a lookup tool specifically for these error codes.

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

Error ACCESS VIOLATION 6E00655D

Hello,
I get the following error when running my script in Diadem 2014. The same script does not cause any errors when it is executed in Diadem 11. Any ideas?
Error while executing "ChnTimeAreaCopy" command
Error type: ACCESS VIOLATION
Error address: 6E00655D
Module nameIAdem.exe

HI Kevin
Overall, the script is looping through about 30 channels in a group and chopping the data between -.1 and .5 seconds using ChnTimeAreaCopy. Yes the script is being used on the same data set in both DIAdem 2014 and DIAdem 2011.

ACCESS VIOLATION error in Report

Similar Messages

Maybe you are looking for