Hello Wayne,

The application is third-party. I am in contact with the developers to make the application better 😉

Thank you for suggestions everyone! I have also asked the same question on another forum and the cumulative take-aways would be the following:

* MAXDOP value of 1024 with running value...

Hello Jeff, thank you very much for your comprehensive response.

What do you make of the server memory dump values? Is MSDN link that I've posted above correct about issues with...

Here's what I found on MSDN site:

http://blogs.msdn.com/b/karthick_pk/archive/2010/06/23/how-to-analyze-quot-deadlocked-schedulers-quot-dumps.aspx

2. If most of threads are stuck while trying to write profiler events

to the destination you might find stack similar to one below

sqlservr!CTraceWriteRequest::InitForRowsetTrace

There...

Thank you for answering! Could you please confirm what the 'server-side trace' is?

Thank you,

Does profiler leave any 'residue' in the system if I was saving the trace to file?

And here is the script from this article:

http://www.sqlskills.com/blogs/paul/wait-statistics-or-please-tell-me-where-it-hurts/

WaitType Wait_S Resource_S Signal_S WaitCount Percentage AvgWait_S AvgRes_S AvgSig_S

LATCH_EX 2.35 2.06 0.29 6554 62.62 0.0004 0.0003 0.0000

CXPACKET 1.10 ...

Hello GilaMonster,

So if I ran the trace at 3 PM and the crash took place at 6 PM, it still would have caused it?

Thanks,

Thank you for your reply, Grant!

Could my profiling cause the crash listed above?

Also, here are the other stats:

wait_typewaiting_tasks_countwait_time_msmax_wait_time_mssignal_wait_time_ms

CXPACKET5682620066314514119590733499132

BROKER_TASK_STOP50299084649277926100332181434

FT_IFTS_SCHEDULER_IDLE_WAIT297923844088436000163477

LAZYWRITER_SLEEP23268143824421671571772179345

LCK_M_RS_U2202093094436804632853979

CLR_AUTO_EVENT440305166910707720866

ASYNC_NETWORK_IO2270203920710732630251822400

REQUEST_FOR_DEADLOCK_SEARCH396461913096095131191309609

XE_TIMER_EVENT637619130951530019191308951

XE_DISPATCHER_WAIT1165191129317151270420

FT_IFTSHC_MUTEX56081191091553377397007871

LOGMGR_QUEUE6730450191018829600247495016

SQLTRACE_INCREMENTAL_FLUSH_SLEEP474791903350936720295

DBMIRROR_EVENTS_QUEUE2596974918985005245391447246

LATCH_EX587554181885471182221009073509

SLEEP_TASK1085288818373993260016798757

CHECKPOINT_QUEUE316918303238032790984462

DBMIRRORING_CMD1308461514607044899889918718

DBMIRROR_DBM_EVENT1165667014538029013363753796

THREADPOOL11651011172919514850323

BROKER_TO_FLUSH9290995661106479112314

LCK_M_U170943837357646241838000

DBMIRROR_DBM_MUTEX61252756821468638466130286

PAGEIOLATCH_SH187778596832393979225654

If there are too many queries accessing the same tables, and all of...