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

Similar Messages

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.

Satellite A300-1IW: HDD access light blinks every seconds

Hello everyone, and sorry for the english, I'm french :)
I bought a Satellite A300-1IW few days ago and suddently (didn't remember exactly when) the HDD access light start to blink every seconds and it continues even after several reboots!
It only does this with Vista; I checked the disk activity with "diskmon" and I saw that even if there were *no* *disk* *writing* *or* *reading* the led continued blinking, so I think it's not related to some vista services (superfetch, indexing...)
I saw on a Microsoft support a similar problem but it was under windows 98 and with old motherborads!
see : Link: [http://support.microsoft.com/kb/138598]
It seems so that it's related to Vista SCSI or DVD quering...
I now that's not critical but it's annoying to have this led blinking all the time
Have any idea? Do you think it could be related to the bios? I want to be sure before touching this because it's always delicate.
Thanks for your help

In my opinion nobody must offer any comment because you already given the answer. This is nothing unusual and definitely no reason for panic.
What to do about it? What you want to do? Sorry but it is really stupid question. I can just offer you one stupid answer. ;) Take some black adhesive tape and cower the LED. ;)

ITunes 10.3.1 pops up with Accessing iTunes Store every second

When trying to type something into the upper right search field in iTunes 10.3.1, it pops up with the "Accessing iTunes Store" after every single letter I try to type in. It makes it so even writing a single word takes like a full minute. The previous version of iTunes had just started doing it too. I updated to 10.3.1 hoping that it would fix it, but it didn't.

Hi all, iTunes streaming victims.
I struggled long with the streaming buffer problem of iTunes and indeed could solve it with increasing the buffer size, which features has been removed in iTunes 10. And this without updating the instructions by Apple!
In the end also the reinstall didn't work.
Here is my latest solutions:
http://www.rogueamoeba.com/airfoil/
perfect for all wireless audio streaming not only for itunes, but any source on the Mac.
solved the problem completely for my 3 MacBooks, 2 airports, iphones etc.
it is not for free but a very good value for money.
cheers, Wil

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.

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

Why arch always access ext4 every second?

I've read one related topic https://bbs.archlinux.org/viewtopic.php?id=113516.
$ pacman -Q linux
linux 3.10.10-1
$ mount -o defaults,noatime,commit=60 /dev/sdb2 /mnt/home
# it access my disk every second
$ mount | grep sdb2
/dev/sdb2 on /mnt/home type ext4 (rw,noatime,commit=60,data=ordered)
Any tip to debug it?

> f it has just been created, the link you posted may contain the answer i.e. it might still be creating the inodes.
Thanks, I just notice it
man mkfs.ext4
# default enabled lazy_itable_init and lazy_journal_init.
# and related mount option: uninit_bg
But how to know all the inode have already created?
Here I list my another PC's ext4 partition information.
$ smartctl --all /dev/sda
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.10.10-1-ARCH] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: HITACHI HDS7225SCSUN250G 0710B99GZK
Serial Number: VFA140R1D99GZK
LU WWN Device Id: 5 000cca 210d25271
Firmware Version: V5DOA7BA
User Capacity: 250,056,000,000 bytes [250 GB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA/ATAPI-7 T13/1532D revision 1
Local Time is: Tue Sep 17 10:03:25 2013 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 4949) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 83) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 161 161 050 Pre-fail Offline - 195
3 Spin_Up_Time 0x0007 135 135 024 Pre-fail Always - 260 (Average 292)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 73
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 134 134 020 Pre-fail Offline - 32
9 Power_On_Hours 0x0012 096 096 000 Old_age Always - 32356
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 73
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 208
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 208
194 Temperature_Celsius 0x0002 181 181 000 Old_age Always - 33 (Min/Max 17/54)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
$ tune2fs -l /dev/sda2
tune2fs 1.42.8 (20-Jun-2013)
Filesystem volume name: arch64
Last mounted on: /
Filesystem UUID: xxx(omit)
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 15138816
Block count: 60548805
Reserved block count: 3027440
Free blocks: 8208333
Free inodes: 12058767
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1009
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Thu Jan 5 17:01:16 2012
Last mount time: Mon Sep 2 08:58:15 2013
Last write time: Mon Sep 2 08:58:15 2013
Mount count: 12
Maximum mount count: 34
Last checked: Fri Jul 12 11:00:12 2013
Check interval: 15552000 (6 months)
Next check after: Wed Jan 8 11:00:12 2014
Lifetime writes: 1724 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
First orphan inode: 13159924
Default directory hash: half_md4
Directory Hash Seed: 5deea733-f866-4478-add5-a98235057da4
Journal backup: inode blocks

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

PXE-T04: Access Violation

We are running SCCM 2012 R2 Primary Site Server
We configured PXE Service Point in Microsoft System Center Configuration Manager 2012, booting new bare metal vms fail with the following errors:
PXE-T04: Access Violation
PXE-E36: Error Received from TFTP Server
PXE-M-F Exiting PXE Rom
No errors in the SMSPXE.log.
We configured IP Helper settings on routers
next-ser er "IP Address of SCCM PXE Server"
filename smsboot\x64\wdsnbp.com
Below are WDS logs
Windows Deployment Services Management Utility [Version 6.3.9600.16384]
© 2013 Microsoft Corporation. All rights reserved.
SETUP INFORMATION FOR SERVER
Server State:
     OS version: 6.3
     WDS operational mode: Native
     Standalone configuration: No
Installation State:
     RemoteInstall location: E:\RemoteInstall
     RemoteInstall share up-to-date: Yes
     Boot files installed:
         x86     - Yes
         x64     - Yes
         ia64    - No
         arm     - Yes
         x86uefi - Yes
         x64uefi - Yes
CONFIGURATION INFORMATION FOR SERVER
Server Authorization:
     Authorization state: Not Authorized
Answer Policy:
     Answer clients: No
     Answer only known clients: No
     Response delay: 0 seconds
Active Directory Use Policy:
     Preferred DC:
     Preferred GC:
     Prestage devices using MAC: No
     New computer naming policy: %61Username%#
     Domain search order: Global Catalog Only
     New computers join domain: Yes
New Computer OU:
     OU type: Server Domain
     OU: CN=Computers,DC=nb,DC=com
DHCP Configuration:
     DHCP service status: Not Installed
     DHCP option 60 configured: <Not Applicable>
PXE Bind Policy:
     Use DHCP ports: Yes
     Rogue detection: Disabled
     RPC port: 5040
Interface Bind Policy:
     Policy: Exclude Registered
     Registered interfaces:
Boot Program Policy:
     Known client PXE prompt policy: OptIn
     New client PXE prompt policy: OptIn
     Allow N12 for new clients: <Not Applicable>
     Reset boot program: Disabled
     Default boot programs:
         x86     - boot\x86\pxeboot.com
         x64     - boot\x64\pxeboot.com
         ia64    - boot\ia64\bootmgfw.efi
         arm     - boot\arm\bootmgfw.efi
         x86uefi - Boot\x86\bootmgfw.efi
         x64uefi - Boot\x64\bootmgfw.efi
     Default N12 boot programs:
         x86     - boot\x86\pxeboot.n12
         x64     - boot\x64\pxeboot.n12
         ia64    - boot\ia64\bootmgfw.efi
         arm     - boot\arm\bootmgfw.efi
         x86uefi - Boot\x86\bootmgfw.efi
         x64uefi - Boot\x64\bootmgfw.efi
Banned GUIDs list:
Boot Image Policy:
     Default image type for x64 clients: Both
     Default boot images:
         x86     -
         x64     -
         ia64    -
         arm     -
         x86uefi -
         x64uefi -
Driver Policy:
     Avoid duplicate driver packages: Yes
WDS Client Policy:
     Logging policy:
         Enabled: No
         Logging level: Info
     Unattend policy:
         Enabled: No
         Command-line precedence: No
         WDS unattend files:
             x86     -
             x64     -
             ia64    -
             arm     -
             x86uefi -
             x64uefi -
Server Automatic Refresh Policy:
     Refresh period: 900 seconds
BCD Refresh Policy:
     Enabled: No
     Refresh period: 60 minutes
Pending Device Policy:
     Policy: Disabled
     Poll interval: 10 seconds
     Max retry count: 2160 times
     Message to pending clients:
     Retention period:
         Approved devices: 30 days
         Other devices: 1 days
     Defaults for x86:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for x64:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for ia64:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for arm:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for x86uefi:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Join Only
         Join domain: Yes
     Defaults for x64uefi:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Join Only
         Join domain: Yes
WDS PXE Providers:
     Name: SMSPXE
     Path: C:\Program Files\Microsoft Configuration Manager\bin\x64\smspxe.dll
     Order: 1
     Critical: No
     Name: WDSDCPXE
     Path: C:\Windows\system32\wdsdcpxe.dll
     Order: 2
     Critical: No
WDS Device Controllers:
     Name: WDSADDC
     CLSID: {1F05CFEA-D4E4-4049-9C76-7B4F0013ECC9}
     Priority: 32768
     Enabled: Yes
     Name: WDSSDC
     CLSID: {17FD4B68-06B7-48EB-97B7-1575A171AED9}
     Priority: 32768
     Enabled: No
WDS Transport Server Policy:
     IPv4 source: Range
         Start address: 239.192.0.2
         End address: 239.192.0.254
     IPv6 source: Range
         Start address: FF15::1:1
         End address: FF15::1:FF
     UDP Port Policy: Dynamic
         Start port: <Not Applicable>
         End port: <Not Applicable>
     Network profile: <Not Applicable>
     TFTP Properties:
         Maximum block size: 0
         Variable window extension enabled: Yes
     Multicast session policy:
         Slow client handling policy: None
         AutoDisconnect threshold: 256 KBps
         Multistream stream count: 2
         Slow client fallback: Yes
     Multicast Content Providers:
         Name: WDS
         Description: Default Content Provider
         File path: C:\Windows\system32\wdscp.dll
         Initialization routine: WdsTransportProviderInit
IMAGE INFORMATION FOR SERVER
BOOT IMAGES
===============================================================================
Boot Images for x86
Image count: 0
Image Information:
There are no images that match the specified criteria.
Boot Images for x64
Image count: 0
Image Information:
There are no images that match the specified criteria.
Boot Images for ia64
Image count: 0
Image Information:
There are no images that match the specified criteria.
Boot Images for arm
Image count: 0
Image Information:
There are no images that match the specified criteria.
===============================================================================
Summary:
Total number of boot image stores: 4
Total number of boot images: 0
INSTALL IMAGES
===============================================================================
There are no image groups that match the specified criteria.
===============================================================================
Summary:
Total number of install image groups: 0
Total number of install images: 0
NON-NATIVE IMAGES
===============================================================================
===============================================================================
Summary:
Total number of non-wim image groups: 0
Total number of non-wim images: 0
OVERALL IMAGE SUMMARY:
Total number of boot image stores: 4
Total number of boot images: 0
Total number of install image groups: 0
Total number of install images: 0
Total number of non-wim image groups: 0
Total number of non-wim images: 0
The command completed successfully.
SMSPXE:
======
<![LOG[Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll]LOG]!><time="14:43:49.110+240" date="04-28-2014" component="SMSPXE" context=""
type="1" thread="6808" file="wimfile.cpp:344">
<![LOG[Opening image file E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim]LOG]!><time="14:43:49.110+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:422">
<![LOG[Found Image file: E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim
PackageID: PRI00002
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="14:43:49.113+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:925">
<![LOG[Closing image file E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim]LOG]!><time="14:43:49.113+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:458">
<![LOG[Begin validation of Certificate [Thumbprint 8B278656F312633DA23BDEAA99A625C7933019A2] issued to '{0D51C1EC-638A-4904-938E-58C733731F10}']LOG]!><time="14:43:49.119+240" date="04-28-2014" component="SMSPXE" context=""
type="1" thread="6032" file="ccmcert.cpp:1662">
<![LOG[Completed validation of Certificate [Thumbprint 8B278656F312633DA23BDEAA99A625C7933019A2] issued to '{0D51C1EC-638A-4904-938E-58C733731F10}']LOG]!><time="14:43:49.119+240" date="04-28-2014" component="SMSPXE"
context="" type="1" thread="6032" file="ccmcert.cpp:1803">
<![LOG[PXE Provider finished loading.]LOG]!><time="14:43:49.119+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6032" file="smspxe.cpp:184">
<![LOG[InstallBootFilesForImage failed. 0x80004005]LOG]!><time="14:43:49.392+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1608">
<![LOG[Warning: Failed to copy the needed boot binaries from the boot image E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim.
The operation completed successfully. (Error: 00000000; Source: Windows)]LOG]!><time="14:43:49.392+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1275">
<![LOG[Failed adding image E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim. Will Retry..
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="14:43:49.392+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1180">
<![LOG[File E:\RemoteInstall\SMSTemp\2014.04.28.14.43.49.03.{E7B944DA-FDBA-4579-8AC8-B91550B1EA89}.boot.bcd deleted.]LOG]!><time="14:43:49.393+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="bootimagecache.cpp:267">
<![LOG[File E:\RemoteInstall\SMSTemp\2014.04.28.14.43.49.03.{E7B944DA-FDBA-4579-8AC8-B91550B1EA89}.boot.bcd.log deleted.]LOG]!><time="14:43:49.393+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="bootimagecache.cpp:282">
<![LOG[Found new image PRI00005]LOG]!><time="14:43:49.393+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:1123">
<![LOG[Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll]LOG]!><time="14:43:49.394+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="wimfile.cpp:344">
<![LOG[Opening image file E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim]LOG]!><time="14:43:49.394+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:422">
<![LOG[Found Image file: E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim
PackageID: PRI00005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="14:43:49.397+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:925">
<![LOG[Closing image file E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim]LOG]!><time="14:43:49.397+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:458">
<![LOG[InstallBootFilesForImage failed. 0x80004005]LOG]!><time="14:43:49.713+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1608">
<![LOG[Warning: Failed to copy the needed boot binaries from the boot image E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim.
The operation completed successfully. (Error: 00000000; Source: Windows)]LOG]!><time="14:43:49.713+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1275">
<![LOG[Failed adding image E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim. Will Retry..
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="14:43:49.713+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1180">
<![LOG[File E:\RemoteInstall\SMSTemp\2014.04.28.14.43.49.04.{9C5C9A39-428B-4B20-B844-3454CB63F230}.boot.bcd deleted.]LOG]!><time="14:43:49.713+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="bootimagecache.cpp:267">
<![LOG[File E:\RemoteInstall\SMSTemp\2014.04.28.14.43.49.04.{9C5C9A39-428B-4B20-B844-3454CB63F230}.boot.bcd.log deleted.]LOG]!><time="14:43:49.714+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="bootimagecache.cpp:282">
<![LOG[Found new image PRI00002]LOG]!><time="14:43:50.812+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:1123">
<![LOG[Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll]LOG]!><time="14:43:50.813+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="wimfile.cpp:344">
<![LOG[Opening image file E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim]LOG]!><time="14:43:50.813+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:422">
<![LOG[Found Image file: E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim
PackageID: PRI00002
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="14:43:50.815+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:925">
<![LOG[Closing image file E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim]LOG]!><time="14:43:50.815+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:458">
<![LOG[InstallBootFilesForImage failed. 0x80004005]LOG]!><time="14:43:51.094+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1608">
<![LOG[Warning: Failed to copy the needed boot binaries from the boot image E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim.
The operation completed successfully. (Error: 00000000; Source: Windows)]LOG]!><time="14:43:51.095+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1275">
<![LOG[Failed adding image E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim. Will Retry..
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="14:43:51.095+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1180">
<![LOG[File E:\RemoteInstall\SMSTemp\2014.04.28.14.43.50.05.{2A90265D-C49E-433D-868E-7CF173CB4B93}.boot.bcd deleted.]LOG]!><time="14:43:51.095+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="bootimagecache.cpp:267">
<![LOG[File E:\RemoteInstall\SMSTemp\2014.04.28.14.43.50.05.{2A90265D-C49E-433D-868E-7CF173CB4B93}.boot.bcd.log deleted.]LOG]!><time="14:43:51.095+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="bootimagecache.cpp:282">
<![LOG[Found new image PRI00005]LOG]!><time="14:43:51.095+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:1123">
<![LOG[Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll]LOG]!><time="14:43:51.096+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="wimfile.cpp:344">
<![LOG[Opening image file E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim]LOG]!><time="14:43:51.096+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:422">
<![LOG[Found Image file: E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim
PackageID: PRI00005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="14:43:51.099+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:925">
<![LOG[Closing image file E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim]LOG]!><time="14:43:51.099+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:458">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\wdsnbp.com' does not exist. Ignore it]LOG]!><time="14:43:51.452+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\abortpxe.com' does not exist. Ignore it]LOG]!><time="14:43:51.452+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\pxeboot.com' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\pxeboot.n12' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\bootmgr.exe' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\wdsnbp.com' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\abortpxe.com' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\wdsmgfw.efi' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\EFI\bootmgfw.efi' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\Fonts\segmono_boot.ttf' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context=""
type="2" thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\Fonts\segoe_slboot.ttf' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context=""
type="2" thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\Fonts\segoen_slboot.ttf' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context=""
type="2" thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\Fonts\wgl4_boot.ttf' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Cannot read the registry value of MACIgnoreListFile (800703e5)]LOG]!><time="14:43:53.086+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="provsettings.cpp:353">
<![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="14:43:53.086+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="provsettings.cpp:468">
<![LOG[Found new image PRI00002]LOG]!><time="14:43:56.973+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:1123">
<![LOG[Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll]LOG]!><time="14:43:56.974+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="wimfile.cpp:344">

\\smsboot\x64\wdsnbp.com fixed the issue.

TFTP Read Access Violation in Snoop while doing network boot

Hi
I have setup my Oracle dhcp server and AI on oracle 11.1.
configure the /etc/ethers and /etc/hosts file as well.
pntadm and dhtam is also setup with macro
I deplou solaris 11.1 AI sparc image as my service
create-client and manifest is also associated as per client machine Mac interface
On client machine
I created the devalias entry for my Nic interface
did now
boot net:dhcp
Requesting Internet Address for 0:e:1E:8:bf:f8
Requesting Internet Address for 0:e:1E:8:bf:f8
Time out waiting for tftp reply
On server machine in snoop its showing
tftp read "01010F19" (octet)
TFTP Error : Access violation
I check tftp service is running on server as below
/usr/sbin/in.tftpd -s /etc/netboot
Please help me i am not able to figure out whats the problem
Thanks

But even on dhcp it doesn't work without setting network-boot-arguments on OBP
If i don't feed any entry in /etc/ethers and /etc/hosts
whenvever I do on client side boot net:dhcp it always give rarp messages in the snoop on server.
What can be the reason.

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 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 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 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

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

Similar Messages

Maybe you are looking for