The system limits use of the processor.

When a process is actively loading the CPU some time (in my experience - until 14:00 CPU time for a given process, according to the monitoring system). After the occurrence of the above events process uses only one core (up to this point - used 8 "cores", 4 real + 4 virtual). Problem persists in Safe Mode, then reinstalling the OS (but keeping all the data). I can not solve this problem. The question is very critical, because in fact I can not use the computer for any intensive tasks.
Hardware Information
MacBook Pro Retina (mid-2012)
OS - Yosemite 10.10
Processor - 2.3GHz i7
Previously, such a notice is not started about 1-2 weeks ago (could be wrong).

CPU load:

Similar Messages

  • Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system. I have a wndiws 7 system and use a Intel core processor. I have restarted several times and still ge this

    Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system. I have a wndows 7 system and use a Intel core processor. I have restarted several times and still ge this error. I have also tried to reinstall firefox and get the same error
    == This happened ==
    Every time Firefox opened
    == today ==
    == User Agent ==
    Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MDDS; InfoPath.2; .NET4.0C; AskTbUT2V5/5.8.0.12304)

    <u>'''Kill Application'''</u>
    In Task Manager, does firefox.exe show in the <u>'''Processes'''</u> tab?
    See: [http://kb.mozillazine.org/Kill_application Kill Application]
    '''<u>Causes and solutions for Firefox hanging at exit:</u>'''
    [[Firefox hangs]]
    [http://kb.mozillazine.org/Firefox_hangs#Hang_at_exit Firefox hangs at exit]
    [[Firefox is already running but is not responding]]
    <u>'''Safe Mode'''</u>
    You may need to use '''[[Safe Mode]]''' (click on "Safe Mode" and read) to localize the problem. Firefox Safe Mode is a diagnostic mode that disables Extensions and some other features of Firefox. If you are using a theme, switch to the DEFAULT theme: Tools > Add-ons > Themes <u>'''before'''</u> starting Safe Mode. When entering Safe Mode, do not check any items on the entry window, just click "Continue in Safe Mode". Test to see if the problem you are experiencing is corrected.
    See:
    '''[[Troubleshooting extensions and themes]]'''
    '''[[Troubleshooting plugins]]'''
    '''[[Basic Troubleshooting]]'''
    If the problem does not occur in Safe-mode then disable all of your Extensions and Plug-ins and then try to find which is causing it by enabling <u>'''one at a time'''</u> until the problem reappears. <u>'''You MUST close and restart Firefox after EACH change'''</u> via File > Restart Firefox (on Mac: Firefox > Quit). You can use "Disable all add-ons" on the Safe mode start window.

  • WHY DOES MY MAC BOOK PRO SHUT OFF ON ME? SO FAR THE INFO I GOT 4 IT IS A MAC OS X VERSION 10.7.3 THE PROCESSOR IS 2.4 GHZ INTEL CORE 2 DUO MEMORY IS 2 GB 667MHZ DDR2 SDRAM I DON'T KNOW HOW OLD IT IS BECAUSE I BOUGHT IT USED SORRY I HOPE THIS HELPS THANK Y

    WHY DOES MY MAC BOOK PRO SHUT OFF ON ME? SO FAR THE INFO I GOT 4 IT IS A MAC OS X VERSION 10.7.3 THE PROCESSOR IS 2.4 GHZ INTEL CORE 2 DUO MEMORY IS 2 GB 667MHZ DDR2 SDRAM I DON'T KNOW HOW OLD IT IS BECAUSE I BOUGHT IT USED SORRY I HOPE THIS HELPS THANK YOU

    Sounds to me like you may have gotten a machine with hardware issues, but it's hard to say.  It will shut down if it gets too hot, but that's not a normal occurrence.  I have never seen a MacBook Pro shut down due to heat, even after lengthy 3D gaming sessions where the fans are running fast and the bottom of the machine is unpleasant to touch.
    First thing I would try to do is reset the SMC.  If that doesn't help, erase the hard drive and reinstall the system from scratch, which you should always do with a used machine anyway.
    If a fresh system doesn't help, you'll need to get it checked out by Apple.
    Edit: Oh, and sig is absolutely right...  please don't post in all caps!  It's very irritating.

  • Bug: Unhandled Exception: System.IO.IOException: The requested operation could not be completed due to a file system limitation

    Hello, I have a 35GB text file that I'm copying from one folder to another folder via c#
    (I simply open a StreamReader and a StreamWriter and copy line by line (something like sw.WriteLine(sr.ReadLine());)
    If [the destination folder is a "windows compress folder" (right click folder > properties > Advanced > Compress content to save disk space)] then it fails else it works well.
    Any idea how to solve the issue?
    I have windows 8.1 with all latest updates. The ssd is a samsung 850 pro, and I tried on 2 machines, same results.
    So to recap, it seems the issue is with the writing of big files on a compress folder, the reading is fine.
    thanks.
    w
    Error:
    2015.01.08 10:15:27] Unhandled Exception: System.IO.IOException: The requested operation could not be completed due to a file system limitation
    [Err, 2015.01.08 10:15:27] 
    [Err, 2015.01.08 10:15:27]    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
    [Err, 2015.01.08 10:15:27]    at System.IO.FileStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
    [Err, 2015.01.08 10:15:27]    at System.IO.FileStream.Write(Byte[] array, Int32 offset, Int32 count)
    [Err, 2015.01.08 10:15:27]    at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
    [Err, 2015.01.08 10:15:27]    at System.IO.StreamWriter.Write(String value)
    w.

    Hi w,
    Per my understanding. This is not a C# code issue. I doubt the issue related your OS.
    After search the error info,
    here is a possible solution, please take a look
    “The requested operation
    could not be completed due to a file system limitation.”
    <copied>
    Please use Disk Defragmenter to defrag the NTFS volume on your side, which should fix this issue.
    Please refer to:
    A heavily fragmented file in an NTFS volume may not grow beyond a certain size
    http://support.microsoft.com/kb/967351
    For the limitation of NTFS, please check the following online guide.
    How NTFS Works
    http://technet.microsoft.com/en-us/library/cc781134(WS.10).aspx
    </copied>
    Best of luck!
    Kristin
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • ITunes using 100 % of the processor

    Hello,
    I have Leopard 10.5.6 on the new MacBook with the actual iTunes. The problem I am having is that iTunes are taking 100 % of the processor even when there is not any song playing. Tryed to remove all the plugins but it does not make any difference.
    My music collection is not so big. There are both MP3s and AACs.
    Have no idea, what I can try or do.
    Thanks.

    I had (and sometimes still have) CPU usage issues, although I'm running iTunes from a Mac mini, which is likely less powerful than your MacBook.
    I spent so much time trying to figure out the cause. I only knew that iTunes was the culprit from staring at Activity Monitor. One of the major causes of CPU usage in iTunes is Smart Playlists. If you have a large number of Smart Playlists that are set to Live Updating then iTunes will be very busy as it automatically populates those playlists when you make changes to your library.
    Think about the Smart Playlists you have in your library and what Rules they use to build themselves. Then think about what activity in iTunes (playing a track? changing a genre?) would cause the contents of your Smart Playlists to change.
    Another issue to look at is the location of your library files (not your music files). Is it on the same system iTunes is running from?
    Jason

  • How to find the processor we are using in C code

    I have to run a code on both solaris and linux.But before running the code i want to know which processor it is going to run and accordingly i can insert processor specific functions or code........is there are any preprocessors in c which can help to find it

    By "processor" do you mean the computer chip compiling the code, the computer chip executing the application, or something else?
    Standard C provides no way to find out what chip you are using, but most platforms provide a way, different for every platform. By "platform", I mean the combination of computer and operating system.
    Using Sun Studio on Solaris, the compiler predefines some macros that tell you the class of computer being compiled for. See the C Users Guide for details. On a SPARC system, the compiler predefines the macro __sparc. If I'm compiling for 64 bits, it predefines the macro __sparcv9. On an x86 or Opteron system, it predfines the macro __i386. On an Operton system in 64-bit mode, it predefines the macros
    __x86_64 __x86_64__ amd64   _amd64__
    The Solaris OS provides ways to find out the architectural characteristics, mostly via command-line utilities such as prtconf, psrinfo, and others. Linux provides x86conf.

  • Since updating my IPAD 4 to IOS 7 my wifi seems to be running slower. At the same time it seems to be using less power. I wonder if Apple have tweaked the processor speed or something. Any ideas?

    Since running IOS 7 on my IPAD 4 I have noticed that safari or Google APP are running slower. When loading data there is a noticeable delay in the 'bar' running across the screen. The IPAD also seems to be lasting longer between charges. I wonder if Apple have tweaked how the processor is being used for wifi.

    Same issue on my 9 month old IPad4. Turned of all the new fancy additions but no real increase in speed.
    One thing I noticed when I  installed IOS7 was that my free space Immediated jumped from 17Gb on IOS6 to 18.5Gb.
    I then noticed the much slower performance. On IOS6 my pad performed so quickly it often brought  a smile to my face, now I'm watching and waiting while it staggers along loading a page(. Fibre Broadband 45mb/sec so no hold up there and this on my usual browsing sites so it's not their servers ) .
    I'm wondering whether Apple have increased the compression of the system files, so they take longer to unpack - or is am I clutching at straws. Anyone else notice extra space after update.

  • Sir i am using datasocket read ,i am communicating with java but my problem is that bcz im using while loop to see if value has changed my labview consumes all the processors time ,sir i want a event like thing so that while loop is not in continuous loop

    sir i have given lot of effort but i am not able to solve my problem either with notifiers or with occurence fn,probably i do not know how to use these synchronisation tools.

    sir i am using datasocket read ,i am communicating with java but my problem is that bcz im using while loop to see if value has changed my labview consumes all the processors time ,sir i want a event like thing so that while loop is not in continuous loopHi Sam,
    I want to pass along a couple of tips that will get you more and better response on this list.
    1) There is an un-written rule that says more "stars" is better than just one star. Giving a one star rating will probably eliminate that responder from individuals that are willing to anser your question.
    2) If someone gives you an answer that meets your needs, reply to that answer and say that it worked.
    3) If someone suggests that you look at an example, DO IT! LV comes with a wonderful set of examples that demonstate almost all of the core functionality of LV. Familiarity with all of the LV examples will get you through about 80% of the Certified LabVIEW Developer exam.
    4) If you have a question first search the examples for something tha
    t may help you. If you can not find an example that is exactly what you want, find one that is close and post a question along the lines of "I want to do something similar to example X, how can I modify it to do Y".
    5) Some of the greatest LabVIEW minds offer there services and advice for free on this exchange. If you treat them good, they can get you through almost every challenge that can be encountered in LV.
    6) If English is not your native language, post your question in the language you favor. There is probably someone around that can help. "We're big, we're bad, we're international!"
    Trying to help,
    Welcome to the forum!
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • HT1206 I need a work iTunes account for my work system, but used my work email address as an associated email to my personal iTunes account. Now I can't use the work email to create the new iTunes account.  how do I remove the email from my personal accou

    Since I upgraded to Mavericks from Snow Leopard I need a work iTunes account for my work system, but used my work email address as an associated email to my personal iTunes account.
    Now I can't use the work email to create the new iTunes account.  how do I remove the email from my personal account?

    You can long into an account via this page and update the email addresses that you have on it : http://appleid.apple.com

  • What is the logical system name used for in R/3?

    We have a R/3 server. The production client has a logical system name. What is the logical system name used for?
    Tony Tam

    Hi Tony
    Following Links will help you in understanding the concept
    http://benstudycenter.blogspot.com/2008/02/logical-system.html
    http://help.sap.com/saphelp_sm32/helpdata/en/78/217dc151ce11d189570000e829fbbd/frameset.htm
    http://help.sap.com/saphelp_sm32/helpdata/en/78/217dc151ce11d189570000e829fbbd/frameset.htm
    thanks
    Bhudev

  • What is the model number of the processor used in MacBook Pro 13 inch late 2011 ?

    What is the model number of the processor used in MacBook Pro 13 inch late 2011 ?

    Click on the Apple logo in the upper left corner of your screen and select About This Mac. Click on the More Info...  button and you should see what your processor is.

  • Are there any known issues with the latest update to iTunes on Windows 7 maxing out the processor and nearly bringing the system to a hault.

    Has anyone experienced an issue with the latest update to iTunes (11.2.0.115) for Windows where iTunes pegs out the processor at 97%, 98%, and holds there for maybe 15 minutes before dropping to 50%. During that time, the system is basically useless. You just have to ride it out. I'm running Windows 7 Home Premium.

    Hi OnceBeforeIDie,
    Welcome to Apple Support Communities!
    Take a look at the article below, it has some some tips that will resolve a performance issues like the one you described.
    Apple software on Windows: May see performance issues and blank iTunes Store
    http://support.apple.com/kb/ts4123
    -Jason

  • Adobe Reader XI use 100 % of the processor in Internet Explorer

    We have sequenced Adobe Reader XI with App-V 5.0 SP2 hotfix 5. This package is deployed in our Windows 2008 R2 Citrix XenApp 7.6 server. When we open a PDF document in Internet Explorer, after about 10 seconds IE freeze and this process use 100% of one processor.
    The first 10 seconds, we can do watever we want with the PDF file.
    We are searching a fix for this problem for many weaks, with no success. We have virtualized Adobe Reader X and we have no problem with PDF in Internet Explorer. 
    I know that installing Reader localy will solve the problem, but we want to virtualised the maximum of application without installing it natively.
    Thanks for your help!

    I have run a procmon and i have discover that when the processor is 100%, the Internet Explorer process query the registry with those key to the infinite : 
    14:21:54.1307690 IEXPLORE.EXE 7800 RegQueryKey HKU\S-1-5-21-854245398-789336058-725345543-8900_CLASSES\AppV\Client\Packages\E9C21601-2C25-4417-92E9-35A059B30C37 SUCCESS Query: HandleTags, HandleTags: 0x100
    14:21:54.1307944 IEXPLORE.EXE 7800 RegOpenKey HKU\S-1-5-21-854245398-789336058-725345543-8900_CLASSES\AppV\Client\Packages\E9C21601-2C25-4417-92E9-35A059B30C37\Registry\User\S-1-5-21-854245398-789336058-725345543-8900_Classes\Local Settings\MuiCache\1FB\D9B7F780 NAME NOT FOUND Desired Access: Maximum Allowed
    14:21:54.1308273 IEXPLORE.EXE 7800 RegQueryKey HKU\S-1-5-21-854245398-789336058-725345543-8900_CLASSES\AppV\Client\Packages\E9C21601-2C25-4417-92E9-35A059B30C37\Versions\4679E4EB-4D2A-4D8F-9CB8-481E6FEFBC20 SUCCESS Query: HandleTags, HandleTags: 0x100
    14:21:54.1308517 IEXPLORE.EXE 7800 RegOpenKey HKU\S-1-5-21-854245398-789336058-725345543-8900_CLASSES\AppV\Client\Packages\E9C21601-2C25-4417-92E9-35A059B30C37\Versions\4679E4EB-4D2A-4D8F-9CB8-481E6FEFBC20\Registry\User\S-1-5-21-854245398-789336058-725345543-8900_Classes\Local Settings\MuiCache\1FB\D9B7F780 NAME NOT FOUND Desired Access: Maximum Allowed
    14:21:54.1308819 IEXPLORE.EXE 7800 RegOpenKey HKU\S-1-5-21-854245398-789336058-725345543-8900_Classes\Local Settings\MuiCache\1FB\D9B7F780 SUCCESS Desired Access: Maximum Allowed, Granted Access: Read, Create Link
    14:21:54.1309094 IEXPLORE.EXE 7800 RegSetInfoKey HKU\S-1-5-21-854245398-789336058-725345543-8900_CLASSES\Local Settings\MuiCache\1FB\D9B7F780 SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
    14:21:54.1309478 IEXPLORE.EXE 7800 RegQueryKey HKU\S-1-5-21-854245398-789336058-725345543-8900_CLASSES\AppV\Client\Packages\E9C21601-2C25-4417-92E9-35A059B30C37 SUCCESS Query: HandleTags, HandleTags: 0x100
    14:21:54.1309732 IEXPLORE.EXE 7800 RegCreateKey HKU\S-1-5-21-854245398-789336058-725345543-8900_CLASSES\AppV\Client\Packages\E9C21601-2C25-4417-92E9-35A059B30C37\Registry ACCESS DENIED Desired Access: Maximum Allowed
    14:21:54.1310056 IEXPLORE.EXE 7800 RegCloseKey HKU\S-1-5-21-854245398-789336058-725345543-8900_CLASSES\Local Settings\MuiCache\1FB\D9B7F780 SUCCESS
    14:21:54.1310313 IEXPLORE.EXE 7800 RegEnumKey HKU\S-1-5-21-854245398-789336058-725345543-8900_CLASSES\Local Settings\MuiCache\1FB SUCCESS Index: 0, Name: D9B7F780
    Thanks!

  • Is there a way to get photos off of a thumb drive onto something that can be uploaded to the ipad. I am doing away with my windows systems and using the ipad exclusively?

    is there a way to get photos off of a thumb drive onto something that can be uploaded to the ipad. I am doing away with my windows systems and using the ipad exclusively?

    iPad Photo Recovery: How to Recover Deleted Photos
    http://www.iskysoft.com/iphone-data-recovery-mac/ipad-photo-recovery.html
    How to Restore Lost or Deleted Files from iPad
    http://www.iphone-ipad-recovery.com/recover-ipad-mini-files.html
    How to Recover Deleted Files from iPad
    http://www.kvisoft.com/tutorials/recover-deleted-files-from-ipad.html
    How to Recover Photos from iPad
    http://www.ipubsoft.com/idevice-tips/recover-deleted-photos-on-ipad-mini.html
    iSkysoft Free iPhone Data Recovery
    http://www.iskysoft.com/iphone-data-recovery/
    Recover iPhone/iPad/iPod touch lost data, Free.
    Free recover iPhone/iPad/iPod touch lost contacts, photos, videos, notes, call logs and more
    Recover data directly from iPhone or from iTunes backup
    Preview and recover lost iOS data with original quality
    Wondershare Dr.Fone for iOS
    http://www.wondershare.net/data-recovery/iphone-data-recovery.html?gclid=CJT7i9e 6gb4CFcvm7AodbUEAJQ
    Recover contacts, messages, photos, videos, notes, call history, calendars, voicemail, voice memos, reminders, bookmarks and other documents.
    iPad Data Recovery Software (PC & Mac)
    http://www.anysoftwaretools.com/ipad-data-recovery.html
    Jihosoft Mobile Recovery for iOS
    http://www.fonerecovery.com/iphone-data-recovery.html
     Cheers, Tom

  • SSIS 2008 package conversion to SSIS 2012 using SQL Data Tools generating warning There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWra

    I am seeing the following warning is a SSIS C# script and receive a SSIS abort when I attempt to run the package.
    The SSIS log indicates the package is failing at about this same step in the process.  
    I have also included the file SSQLDUMPER_ERRORLOG.log that SSIS generates when it aborts below.
    My SSIS package has been set to 64-bit and I only have 64-bit SQL Server 2012 installed on the box.
    I migrated the package using the latest version of Data Tools that came out around mid July 2014.
    I edited all connection manager strings to point to 64-bit SQL Server and I run using the following command
    I edited the run string to point to the new 64 bit DTExec and attempted to run.
    C:\Program Files\Microsoft SQL Server\110\DTS\Binn\DTExec.exe" /Rep V /F PkgMigration.dtsx .........................
    A significant amount of work does occur as reflected by the log steps prior to DTEXEC aborting but the log does just quit in mid sentence so not sure if it might have actually got a bit further.
    Any help on understanding what is happening here would be most appreciated.
    Warning               1              There was a mismatch between the processor
    architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWrap, Version=11.0.0.0, Culture=Neutral, PublicKeyToken=89845dcd8080cc91", "x86". This mismatch may
    cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a
    processor architecture that matches the targeted processor architecture of your project.                C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets             
    1605       5                sc_5756696d96034309a51afe69fed2eb44
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 6100
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00A8B770
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 6100
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00A8B770
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0007.mdmp
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (1CBC:1808) 08/14/14 10:36:47, ACTION,                DTExec.exe, Watson Invoke: No
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 1: 10124
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 2: 0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 3: 0:0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 4: 0012B770
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 10124
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0012B770
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0008.mdmp
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (2724:2488) 08/14/14 10:43:09, ACTION,                DTExec.exe, Watson Invoke: No
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 1: 8716
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 2: 0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 3: 0:0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 4: 0072B770
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8716
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0072B770
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0009.mdmp
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (2240:89C) 08/14/14 10:51:56, ACTION,                DTExec.exe, Watson Invoke: No
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 1: 8856
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 2: 0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 3: 0:0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 4: 009AB770
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8856
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x009AB770
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0010.mdmp
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (7B8:1E68) 08/14/14 11:01:36, ACTION,                DTExec.exe, Watson Invoke: No
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 1292
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00BFB770
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 1292
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00BFB770
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0011.mdmp
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (229C:1CD8) 08/14/14 11:45:45, ACTION,                DTExec.exe, Watson Invoke: No
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 1: 4220
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 2: 0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 3: 0:0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 4: 0019B770
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 4220
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0019B770
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0012.mdmp
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (2520:2624) 08/14/14 12:05:47, ACTION,                DTExec.exe, Watson Invoke: No
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 8408
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00000000003ECC18
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8408
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000003ECC18
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0001.mdmp
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION,                DTExec.exe, Watson Invoke: No

    Hi GaryAMiller,
    It seesm this is a know ssue. Please take a look at the following simialr issue at Microsoft Connect site:
    MSB3270: Mismatch between the processor architecture:
    https://connect.microsoft.com/VisualStudio/feedback/details/804933/msb3270-mismatch-between-the-processor-architecture-fakes-framework
    If this issue still persists, I would suggest
    opening a case with Microsoft Customer Support Services (CSS)(http://support.microsoft.com), so that a dedicated Support Professional can assist you in a more efficient manner.
    If you have any feedback on our support, please click
    here.
    Elvis Long
    TechNet Community Support

Maybe you are looking for

  • I am getting ORA-01008:not all variables bound error

    Hi all, i am getting ORA-01008:not all variables bound error while executing the following code... Could any one help me to find out the problem...i am very new to ODP.net and Oracle .. I am using VC++.net for run this code. Here is the code..... #in

  • Problem installing CS2 on Windows 7

    I downloaded and attempted to install CS2 from the Adobe website and have been unsuccessful in getting past the "install disc 2" message. I spoke with a rep via chat and they referred me here. I have followed the directions that were included with th

  • Dynamic selection in alv

    hai   How to display a column in alv(Container) in dynamic manner at runtime. specify the code if u have. thx in advance.

  • Deletion of records

    Hello, i am getting from user..and i want to delete the records that starts with that user input...how to write query for this? delete * from emp where emp_name like 's%'... the above query is for deleting records of the employee whose name starts wi

  • Confused with hardware tests / s.m.a.r.t. failing

    This morning I opened disk utility and with fear read the text saying smart status failing on my startup disk. Since then, I did several backups and decided that i will most probably need to purchase a new disk. I also did some other tests with other