Have you checked to verify the linked server referenced in the stack dump? Could be an issue there (security/external to the linked server) and whenever this query gets run, it causes a fatal error, generating the dump?
While there are many errors in your prior log posts, this appears to show up in the stack dump frequently
Process ID 57 was killed by hostname HAILINLI-WS, host process ID 9312.
2013-08-28 22:33:08.35 spid54 Using 'dbghelp.dll' version '4.0.5'
2013-08-28 22:33:08.36 spid54 ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.ION_INST_ETL_02\MSSQL\LOG\SQLDump0005.txt
2013-08-28 22:33:08.36 spid54 SqlDumpExceptionHandler: Process 54 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2013-08-28 22:33:08.36 spid54 * *******************************************************************************
2013-08-28 22:33:08.36 spid54 *
2013-08-28 22:33:08.36 spid54 * BEGIN STACK DUMP:
2013-08-28 22:33:08.36 spid54 * 08/28/13 22:33:08 spid 54
2013-08-28 22:33:08.36 spid54 *
2013-08-28 22:33:08.36 spid54 *
2013-08-28 22:33:08.36 spid54 * Exception Address = 0000000076E120E0 Module(ntdll+00000000000520E0)
2013-08-28 22:33:08.36 spid54 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
2013-08-28 22:33:08.36 spid54 * Access Violation occurred reading address 0000000000000000
2013-08-28 22:33:08.36 spid54 * Input Buffer 510 bytes -
2013-08-28 22:33:08.36 spid54 * select top 1 * from OPENQUERY(CG1PRD,'SELECT B.order_number
2013-08-28 22:33:08.36 spid54 * ,A.line_number ,nvl(A.option_number,0) as option_numb
2013-08-28 22:33:08.36 spid54 * er --,D.set_name as ship_set_number --,C.organization_
2013-08-28 22:33:08.36 spid54 * code ,A.ordered_item as item_number ,A.item_type_code
...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience