locked
SQL 2008 hungs RRS feed

  • Question

  • I have installed a  Windows Server 2008 R2 Foundation installed on HPserver. After that, I installed ERP software which installs SQL 2005 EXPRESS. After that all worked fine.

    Later we changed SQL2005 EXPRESS by "SQL Server 2008 Standard Edition for Small Business". After that, SQL hungs after any odbc connection (ERP software has been installed previously with SQL2008 and SQL2008R2 and no problems have been reported)  

    The most extrange thing is that the same database, with the same ERP software, runs properly using SQL 2005 EXPRESS and hungs running on SQL 2008.

    I attach part of the sql error log.

    Any idea about how to solve it?

    2011-02-15 15:07:43.11 Server      Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)
     Mar 29 2009 10:11:52
     Copyright (c) 1988-2008 Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

    2011-02-15 15:07:43.11 Server      (c) 2005 Microsoft Corporation.
    2011-02-15 15:07:43.11 Server      All rights reserved.
    2011-02-15 15:07:43.11 Server      Server process ID is 6080.
    2011-02-15 15:07:43.11 Server      System Manufacturer: 'HP', System Model: 'ProLiant ML110 G6'.
    2011-02-15 15:07:43.11 Server      Authentication mode is MIXED.
    2011-02-15 15:07:43.11 Server      Logging SQL Server messages in file 'C:\MSSQL10.TEOWIN\MSSQL\Log\ERRORLOG'.
    2011-02-15 15:07:43.11 Server      This instance of SQL Server last reported using a process ID of 6764 at 15/02/2011 15:07:42 (local) 15/02/2011 15:07:42 (UTC). This is an informational message only; no user action is required.
    2011-02-15 15:07:43.11 Server      Registry startup parameters:
      -d C:\MSSQL10.TEOWIN\MSSQL\DATA\master.mdf
      -e C:\MSSQL10.TEOWIN\MSSQL\Log\ERRORLOG
      -l C:\MSSQL10.TEOWIN\MSSQL\DATA\mastlog.ldf
    2011-02-15 15:07:43.12 Servidor    SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2011-02-15 15:07:43.12 Servidor    Detected 4 CPUs. This is an informational message; no user action is required.
    2011-02-15 15:07:43.18 Servidor    Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2011-02-15 15:07:43.21 Servidor    Node configuration: node 0: CPU mask: 0x000000000000000f Active CPU mask: 0x000000000000000f. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2011-02-15 15:07:43.24 spid7s      Starting up database 'master'.
    2011-02-15 15:07:43.37 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2011-02-15 15:07:43.52 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'TEOWIN'.
    2011-02-15 15:07:43.57 spid7s      SQL Trace ID 1 was started by login "sa".
    2011-02-15 15:07:43.57 spid7s      Starting up database 'mssqlsystemresource'.
    2011-02-15 15:07:43.58 spid7s      The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
    2011-02-15 15:07:43.69 spid7s      Server name is 'SERVIDORRP\TEOWIN'. This is an informational message only. No user action is required.
    2011-02-15 15:07:43.69 spid10s     Starting up database 'model'.
    2011-02-15 15:07:43.87 spid10s     Clearing tempdb database.
    2011-02-15 15:07:43.89 spid13s     A new instance of the full-text filter daemon host process has been successfully started.
    2011-02-15 15:07:43.90 Servidor    A self-generated certificate was successfully loaded for encryption.
    2011-02-15 15:07:43.91 Servidor    Server is listening on [ 'any' <ipv6> 50229].
    2011-02-15 15:07:43.91 Servidor    Server is listening on [ 'any' <ipv4> 50229].
    2011-02-15 15:07:43.91 Servidor    Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\TEOWIN ].
    2011-02-15 15:07:43.91 Servidor    Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$TEOWIN\sql\query ].
    2011-02-15 15:07:43.91 Servidor    Server is listening on [ ::1 <ipv6> 50230].
    2011-02-15 15:07:43.91 Servidor    Server is listening on [ 127.0.0.1 <ipv4> 50230].
    2011-02-15 15:07:43.91 Servidor    Dedicated admin connection support was established for listening locally on port 50230.
    2011-02-15 15:07:43.92 spid14s     Starting up database 'TeoWin'.
    2011-02-15 15:07:43.92 spid15s     Starting up database 'teotest'.
    2011-02-15 15:07:43.92 spid13s     Starting up database 'msdb'.
    2011-02-15 15:07:44.10 Servidor    The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SERVIDORRP.SEMACALOOMDOR.COM:TEOWIN ] for the SQL Server service.
    2011-02-15 15:07:44.10 Servidor    The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SERVIDORRP.SEMACALOOMDOR.COM:50229 ] for the SQL Server service.
    2011-02-15 15:07:44.10 Servidor    SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2011-02-15 15:07:46.06 spid10s     Starting up database 'tempdb'.
    2011-02-15 15:07:46.23 spid13s     The Service Broker protocol transport is disabled or not configured.
    2011-02-15 15:07:46.24 spid13s     The Database Mirroring protocol transport is disabled or not configured.
    2011-02-15 15:07:46.27 spid13s     Service Broker manager has started.
    2011-02-15 15:07:46.27 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2011-02-15 15:07:46.92 spid51      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2011-02-15 15:07:46.92 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'TEOWIN'.
    2011-02-15 15:07:46.95 spid51      Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2011-02-15 15:07:46.95 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'TEOWIN'.
    2011-02-15 15:07:46.98 spid51      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2011-02-15 15:07:46.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'TEOWIN'.
    2011-02-15 15:07:47.38 spid51      Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
    2011-02-15 15:07:47.38 spid51      Using 'xpsqlbot.dll' version '2007.100.1600' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
    2011-02-15 15:07:47.54 spid51      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    2011-02-15 15:07:47.55 spid51      Using 'xpstar.dll' version '2007.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
    2011-02-15 15:07:47.63 spid51      Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
    2011-02-15 15:07:47.64 spid51      Using 'xplog70.dll' version '2007.100.1600' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    2011-02-15 15:14:32.70 spid53      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2011-02-15 15:14:32.70 spid53      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'TEOWIN'.
    2011-02-15 15:14:32.74 spid53      Configuration option 'max server memory (MB)' changed from 2147483647 to 5000000. Run the RECONFIGURE statement to install.
    2011-02-15 15:14:32.74 spid53      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'TEOWIN'.
    2011-02-15 15:14:32.76 spid53      SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
    2011-02-15 15:14:32.76 spid53      SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
    2011-02-15 15:14:32.76 spid53      SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
    2011-02-15 15:14:32.82 spid53      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2011-02-15 15:14:32.82 spid53      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'TEOWIN'.
    2011-02-15 15:17:53.73 Server      Using 'dbghelp.dll' version '4.0.5'
    2011-02-15 15:17:53.73 Server      ***Unable to get thread context for spid 0
    2011-02-15 15:17:53.73 Server      * *******************************************************************************
    2011-02-15 15:17:53.73 Server      *
    2011-02-15 15:17:53.73 Server      * BEGIN STACK DUMP:
    2011-02-15 15:17:53.73 Server      *   02/15/11 15:17:53 spid 5408
    2011-02-15 15:17:53.73 Server      *
    2011-02-15 15:17:53.73 Server      * Non-yielding Scheduler
    2011-02-15 15:17:53.73 Server      *
    2011-02-15 15:17:53.73 Server      * *******************************************************************************
    2011-02-15 15:17:53.73 Server      Stack Signature for the dump is 0x0000000000000160
    2011-02-15 15:17:54.59 Server      External dump process return code 0x20000001.
    External dump process returned no errors.

    2011-02-15 15:17:54.59 Servidor    Process 0:0:0 (0x1964) Worker 0x00000000802981A0 appears to be non-yielding on Scheduler 3. Thread creation time: 12942256063570. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 70407 ms.
    2011-02-15 15:18:09.62 Servidor    Process 0:0:0 (0x1b90) Worker 0x00000000809361A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942256066272. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 93%. Interval: 71290 ms.
    2011-02-15 15:18:19.65 Servidor    Process 0:0:0 (0x1aec) Worker 0x000000008078C1A0 appears to be non-yielding on Scheduler 2. Thread creation time: 12942256066521. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 93%. Interval: 71318 ms.
    2011-02-15 15:18:54.71 Servidor    Process 0:0:0 (0x1964) Worker 0x00000000802981A0 appears to be non-yielding on Scheduler 3. Thread creation time: 12942256063570. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 131388 ms.
    2011-02-15 15:19:09.74 Servidor    Process 0:0:0 (0x1b90) Worker 0x00000000809361A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942256066272. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 131406 ms.
    2011-02-15 15:19:19.76 Servidor    Process 0:0:0 (0x1aec) Worker 0x000000008078C1A0 appears to be non-yielding on Scheduler 2. Thread creation time: 12942256066521. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 131434 ms.
    2011-02-15 15:19:54.83 Servidor    Process 0:0:0 (0x1964) Worker 0x00000000802981A0 appears to be non-yielding on Scheduler 3. Thread creation time: 12942256063570. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 191505 ms.
    2011-02-15 15:20:09.85 Servidor    Process 0:0:0 (0x1b90) Worker 0x00000000809361A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942256066272. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 191523 ms.
    2011-02-15 15:20:19.88 Servidor    Process 0:0:0 (0x1aec) Worker 0x000000008078C1A0 appears to be non-yielding on Scheduler 2. Thread creation time: 12942256066521. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 191551 ms.
    2011-02-15 15:20:54.94 Servidor    Process 0:0:0 (0x1964) Worker 0x00000000802981A0 appears to be non-yielding on Scheduler 3. Thread creation time: 12942256063570. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 251619 ms.
    2011-02-15 15:21:09.98 Servidor    Process 0:0:0 (0x1b90) Worker 0x00000000809361A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942256066272. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 251640 ms.
    2011-02-15 15:21:20.01 Servidor    Process 0:0:0 (0x1aec) Worker 0x000000008078C1A0 appears to be non-yielding on Scheduler 2. Thread creation time: 12942256066521. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 251674 ms.
    2011-02-15 15:21:55.07 Servidor    Process 0:0:0 (0x1964) Worker 0x00000000802981A0 appears to be non-yielding on Scheduler 3. Thread creation time: 12942256063570. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 311749 ms.
    2011-02-15 15:22:10.10 Servidor    Process 0:0:0 (0x1b90) Worker 0x00000000809361A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942256066272. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 311767 ms.
    2011-02-15 15:22:20.13 Servidor    Process 0:0:0 (0x1aec) Worker 0x000000008078C1A0 appears to be non-yielding on Scheduler 2. Thread creation time: 12942256066521. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 311795 ms.
    2011-02-15 15:22:55.18 Servidor    Process 0:0:0 (0x1964) Worker 0x00000000802981A0 appears to be non-yielding on Scheduler 3. Thread creation time: 12942256063570. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 371864 ms.
    2011-02-15 15:23:10.22 Servidor    Process 0:0:0 (0x1b90) Worker 0x00000000809361A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942256066272. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 371889 ms.
    2011-02-15 15:23:20.25 Servidor    Process 0:0:0 (0x1aec) Worker 0x000000008078C1A0 appears to be non-yielding on Scheduler 2. Thread creation time: 12942256066521. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 371919 ms.
    2011-02-15 15:23:55.32 Servidor    Process 0:0:0 (0x1964) Worker 0x00000000802981A0 appears to be non-yielding on Scheduler 3. Thread creation time: 12942256063570. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 431994 ms.
    2011-02-15 15:24:10.34 Servidor    Process 0:0:0 (0x1b90) Worker 0x00000000809361A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942256066272. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 432014 ms.
    2011-02-15 15:24:20.38 Servidor    Process 0:0:0 (0x1aec) Worker 0x000000008078C1A0 appears to be non-yielding on Scheduler 2. Thread creation time: 12942256066521. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 95%. Interval: 432045 ms.
    2011-02-15 15:24:55.43 Servidor    Process 0:0:0 (0x1964) Worker 0x00000000802981A0 appears to be non-yielding on Scheduler 3. Thread creation time: 12942256063570. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 95%. Interval: 492114 ms.
    2011-02-15 15:25:10.47 Servidor    Process 0:0:0 (0x1b90) Worker 0x00000000809361A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942256066272. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 95%. Interval: 492141 ms.
    2011-02-15 15:25:20.50 Servidor    Process 0:0:0 (0x1aec) Worker 0x000000008078C1A0 appears to be non-yielding on Scheduler 2. Thread creation time: 12942256066521. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 95%. Interval: 492169 ms.
    2011-02-15 15:25:55.56 Servidor    Process 0:0:0 (0x1964) Worker 0x00000000802981A0 appears to be non-yielding on Scheduler 3. Thread creation time: 12942256063570. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 552236 ms.
    2011-02-15 15:26:10.58 Servidor    Process 0:0:0 (0x1b90) Worker 0x00000000809361A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942256066272. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 552254 ms.
    2011-02-15 15:26:20.61 Servidor    Process 0:0:0 (0x1aec) Worker 0x000000008078C1A0 appears to be non-yielding on Scheduler 2. Thread creation time: 12942256066521. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 552282 ms.
    2011-02-15 15:26:55.68 Servidor    Process 0:0:0 (0x1964) Worker 0x00000000802981A0 appears to be non-yielding on Scheduler 3. Thread creation time: 12942256063570. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 612357 ms.
    2011-02-15 15:27:10.71 Servidor    Process 0:0:0 (0x1b90) Worker 0x00000000809361A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942256066272. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 612375 ms.
    2011-02-15 15:27:20.74 Servidor    Process 0:0:0 (0x1aec) Worker 0x000000008078C1A0 appears to be non-yielding on Scheduler 2. Thread creation time: 12942256066521. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 612410 ms.
    2011-02-15 15:27:55.81 Servidor    Process 0:0:0 (0x1964) Worker 0x00000000802981A0 appears to be non-yielding on Scheduler 3. Thread creation time: 12942256063570. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 94%. Interval: 672486 ms.

    Friday, February 18, 2011 10:18 AM

Answers

  • The main issue looks like the use of PCTLsp64 module which is present in the SQL address space and is raising an Access Violation. The non-yielding scheduler might be a side effect of this AV. From my searches on "Bing", I find that this module is part of virus monitoring program from PC Tools. If this program is active on your server, then please exclude all folders belonging to Microsoft SQL Server from this scan/monitoring.

    2011-02-21 14:52:02.45 Server * PCTLsp64 000000000B1E0000 000000000B251FFF 00072000

    2011-02-21 14:52:02.49 Server 000000000B1E40AD Module(PCTLsp64+00000000000040AD)
    2011-02-21 14:52:02.49 Server 000000000B1E4701 Module(PCTLsp64+0000000000004701)
    2011-02-21 14:52:02.49 Server 000000000B1E5434 Module(PCTLsp64+0000000000005434)

    And to get to the root cause of the AV, you would need to contact PC Tools support and find out why this issue is occuring. After that DLL has been unloaded from the SQL Server process space, continue to monitor the server and check if the issue re-surfaces.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog: http://troubleshootingsql.com
    Twitter: @banerjeeamit
    SQL Server FAQ Blog on MSDN: http://blogs.msdn.com/sqlserverfaq
    • Marked as answer by msoler Friday, February 25, 2011 8:53 AM
    Monday, February 21, 2011 5:22 PM

All replies

  • Have you change the compatibility level?
    "SQLSERVER DBA" "INDIA"
    Friday, February 18, 2011 1:29 PM
  • I would recommend that you consider upgrading to the latest service pack for SQL Server 2008.

    Out of interest, are you by any chance using AMD processor technology?

    Also you don't appear to have provided the full SQL Server Error log, are there more messages after the final one you posted?


    John Sansom | SQL Server DBA Blog | Twitter
    Sunday, February 20, 2011 9:56 AM
  • You have non-yielding messages for three different schedulers at the same time. It would be interesting to note if all the three threads detected as non-yielding were doing the same work. If you are not on the latest cumulative update for SQL Server, then I would suggest that you apply the same and monitor the server to see if that issue reoccurs. If the issue reoccurs with the latest build, please open a case with CSS so that the non-yielding dumps can be analyzed.
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog: http://troubleshootingsql.com
    Twitter: @banerjeeamit
    SQL Server FAQ Blog on MSDN: http://blogs.msdn.com/sqlserverfaq
    Sunday, February 20, 2011 4:05 PM
  • Now I've updated SQL 2008 to SP2 but the same problem remains. The processor is an Intel Xeon X3430.

    I attach the full log, I hope this helps

    Regards

    2011-02-21 14:51:59.53 Server      Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (X64)
     Sep 16 2010 19:43:16
     Copyright (c) 1988-2008 Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

    2011-02-21 14:51:59.53 Server      (c) 2005 Microsoft Corporation.
    2011-02-21 14:51:59.53 Server      All rights reserved.
    2011-02-21 14:51:59.53 Server      Server process ID is 6080.
    2011-02-21 14:51:59.53 Server      System Manufacturer: 'HP', System Model: 'ProLiant ML110 G6'.
    2011-02-21 14:51:59.53 Server      Authentication mode is MIXED.
    2011-02-21 14:51:59.53 Server      Logging SQL Server messages in file 'C:\MSSQL10.TEOWIN\MSSQL\Log\ERRORLOG'.
    2011-02-21 14:51:59.53 Server      This instance of SQL Server last reported using a process ID of 1640 at 21/02/2011 14:50:41 (local) 21/02/2011 14:50:41 (UTC). This is an informational message only; no user action is required.
    2011-02-21 14:51:59.53 Server      Registry startup parameters:
      -d C:\MSSQL10.TEOWIN\MSSQL\DATA\master.mdf
      -e C:\MSSQL10.TEOWIN\MSSQL\Log\ERRORLOG
      -l C:\MSSQL10.TEOWIN\MSSQL\DATA\mastlog.ldf
    2011-02-21 14:51:59.55 Servidor    SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2011-02-21 14:51:59.55 Servidor    Detected 4 CPUs. This is an informational message; no user action is required.
    2011-02-21 14:51:59.62 Servidor    Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2011-02-21 14:51:59.65 Servidor    Node configuration: node 0: CPU mask: 0x000000000000000f Active CPU mask: 0x000000000000000f. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2011-02-21 14:51:59.68 spid7s      Starting up database 'master'.
    2011-02-21 14:51:59.80 spid7s      1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
    2011-02-21 14:51:59.80 spid7s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
    2011-02-21 14:51:59.80 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2011-02-21 14:51:59.90 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'TEOWIN'.
    2011-02-21 14:51:59.94 spid7s      SQL Trace ID 1 was started by login "sa".
    2011-02-21 14:51:59.94 spid7s      Starting up database 'mssqlsystemresource'.
    2011-02-21 14:51:59.97 spid7s      The resource database build version is 10.00.4000. This is an informational message only. No user action is required.
    2011-02-21 14:52:00.09 spid7s      Server name is 'SERVIDORRP\TEOWIN'. This is an informational message only. No user action is required.
    2011-02-21 14:52:00.09 spid10s     Starting up database 'model'.
    2011-02-21 14:52:00.27 spid10s     Clearing tempdb database.
    2011-02-21 14:52:00.33 spid13s     A new instance of the full-text filter daemon host process has been successfully started.
    2011-02-21 14:52:00.37 spid15s     Starting up database 'TeoWin'.
    2011-02-21 14:52:00.37 spid14s     Starting up database 'teotest'.
    2011-02-21 14:52:00.37 spid13s     Starting up database 'msdb'.
    2011-02-21 14:52:00.41 Servidor    A self-generated certificate was successfully loaded for encryption.
    2011-02-21 14:52:00.42 Servidor    Server is listening on [ 'any' <ipv6> 50229].
    2011-02-21 14:52:00.42 Servidor    Server is listening on [ 'any' <ipv4> 50229].
    2011-02-21 14:52:00.42 Servidor    Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\TEOWIN ].
    2011-02-21 14:52:00.42 Servidor    Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$TEOWIN\sql\query ].
    2011-02-21 14:52:00.42 Servidor    Server is listening on [ ::1 <ipv6> 50230].
    2011-02-21 14:52:00.42 Servidor    Server is listening on [ 127.0.0.1 <ipv4> 50230].
    2011-02-21 14:52:00.42 Servidor    Dedicated admin connection support was established for listening locally on port 50230.
    2011-02-21 14:52:00.45 Servidor    The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SERVIDORRP.SEMACALOOMDOR.COM:TEOWIN ] for the SQL Server service.
    2011-02-21 14:52:00.45 Servidor    The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SERVIDORRP.SEMACALOOMDOR.COM:50229 ] for the SQL Server service.
    2011-02-21 14:52:00.45 Servidor    SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2011-02-21 14:52:02.11 spid10s     Starting up database 'tempdb'.
    2011-02-21 14:52:02.43 Servidor    Error: 17311, gravedad: 16, estado: 1.
    2011-02-21 14:52:02.43 Servidor    SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
    2011-02-21 14:52:02.43 Server      Using 'dbghelp.dll' version '4.0.5'
    2011-02-21 14:52:02.44 Server      **Dump thread - spid = 0, EC = 0x0000000000000000
    2011-02-21 14:52:02.44 Server      ***Stack Dump being sent to C:\MSSQL10.TEOWIN\MSSQL\LOG\SQLDump0024.txt
    2011-02-21 14:52:02.44 Server      * *******************************************************************************
    2011-02-21 14:52:02.44 Server      *
    2011-02-21 14:52:02.44 Server      * BEGIN STACK DUMP:
    2011-02-21 14:52:02.44 Server      *   02/21/11 14:52:02 spid 5728
    2011-02-21 14:52:02.44 Server      *
    2011-02-21 14:52:02.44 Server      * ex_handle_except encountered exception C0000005 - Server terminating
    2011-02-21 14:52:02.44 Server      *
    2011-02-21 14:52:02.44 Server      *
    2011-02-21 14:52:02.44 Server      *  MODULE                          BASE      END       SIZE
    2011-02-21 14:52:02.44 Server      * sqlservr                       0000000000DA0000  0000000004607FFF  03868000
    2011-02-21 14:52:02.44 Server      * ntdll                          0000000076FC0000  000000007716BFFF  001ac000
    2011-02-21 14:52:02.44 Server      * kernel32                       0000000076EA0000  0000000076FBEFFF  0011f000
    2011-02-21 14:52:02.44 Server      * KERNELBASE                     000007FEFCFD0000  000007FEFD03AFFF  0006b000
    2011-02-21 14:52:02.44 Server      * MSVCR80                        0000000074C00000  0000000074CC8FFF  000c9000
    2011-02-21 14:52:02.44 Server      * msvcrt                         000007FEFD790000  000007FEFD82EFFF  0009f000
    2011-02-21 14:52:02.44 Server      * MSVCP80                        0000000073D70000  0000000073E78FFF  00109000
    2011-02-21 14:52:02.44 Server      * ADVAPI32                       000007FEFDA40000  000007FEFDB1AFFF  000db000
    2011-02-21 14:52:02.44 Server      * sechost                        000007FEFD3B0000  000007FEFD3CEFFF  0001f000
    2011-02-21 14:52:02.44 Server      * RPCRT4                         000007FEFE190000  000007FEFE2BDFFF  0012e000
    2011-02-21 14:52:02.44 Server      * sqlos                          0000000073B50000  0000000073B56FFF  00007000
    2011-02-21 14:52:02.44 Server      * Secur32                        000007FEFCD40000  000007FEFCD4AFFF  0000b000
    2011-02-21 14:52:02.44 Server      * SSPICLI                        000007FEFCD80000  000007FEFCDA4FFF  00025000
    2011-02-21 14:52:02.44 Server      * pdh                            000007FEF31B0000  000007FEF31FDFFF  0004e000
    2011-02-21 14:52:02.44 Server      * SHLWAPI                        000007FEFD4A0000  000007FEFD510FFF  00071000
    2011-02-21 14:52:02.44 Server      * GDI32                          000007FEFD310000  000007FEFD376FFF  00067000
    2011-02-21 14:52:02.44 Server      * USER32                         0000000076DA0000  0000000076E99FFF  000fa000
    2011-02-21 14:52:02.44 Server      * LPK                            000007FEFD520000  000007FEFD52DFFF  0000e000
    2011-02-21 14:52:02.44 Server      * USP10                          000007FEFD3D0000  000007FEFD499FFF  000ca000
    2011-02-21 14:52:02.44 Server      * USERENV                        000007FEFB9C0000  000007FEFB9DDFFF  0001e000
    2011-02-21 14:52:02.44 Server      * profapi                        000007FEFCF20000  000007FEFCF2EFFF  0000f000
    2011-02-21 14:52:02.44 Server      * WINMM                          000007FEF3510000  000007FEF354AFFF  0003b000
    2011-02-21 14:52:02.44 Server      * opends60                       0000000073A60000  0000000073A67FFF  00008000
    2011-02-21 14:52:02.44 Server      * NETAPI32                       000007FEFA590000  000007FEFA5A5FFF  00016000
    2011-02-21 14:52:02.44 Server      * netutils                       000007FEFC560000  000007FEFC56BFFF  0000c000
    2011-02-21 14:52:02.44 Server      * srvcli                         000007FEFCB30000  000007FEFCB52FFF  00023000
    2011-02-21 14:52:02.44 Server      * wkscli                         000007FEFA570000  000007FEFA584FFF  00015000
    2011-02-21 14:52:02.44 Server      * LOGONCLI                       000007FEFC530000  000007FEFC55FFFF  00030000
    2011-02-21 14:52:02.44 Server      * SAMCLI                         000007FEF9E60000  000007FEF9E73FFF  00014000
    2011-02-21 14:52:02.44 Server      * BatchParser                    0000000073A00000  0000000073A2BFFF  0002c000
    2011-02-21 14:52:02.44 Server      * IMM32                          000007FEFD380000  000007FEFD3ADFFF  0002e000
    2011-02-21 14:52:02.44 Server      * MSCTF                          000007FEFDC10000  000007FEFDD18FFF  00109000
    2011-02-21 14:52:02.44 Server      * psapi                          0000000077190000  0000000077196FFF  00007000
    2011-02-21 14:52:02.44 Server      * instapi10                      0000000073CD0000  0000000073CDCFFF  0000d000
    2011-02-21 14:52:02.44 Server      * cscapi                         000007FEF9CC0000  000007FEF9CCEFFF  0000f000
    2011-02-21 14:52:02.44 Server      * sqlevn70                       0000000072FC0000  0000000073215FFF  00256000
    2011-02-21 14:52:02.44 Server      * sqlevn70                       00000000729E0000  0000000072BDEFFF  001ff000
    2011-02-21 14:52:02.44 Server      * CRYPTSP                        000007FEFC8A0000  000007FEFC8B6FFF  00017000
    2011-02-21 14:52:02.44 Server      * rsaenh                         000007FEFC480000  000007FEFC4C6FFF  00047000
    2011-02-21 14:52:02.44 Server      * CRYPTBASE                      000007FEFCE10000  000007FEFCE1EFFF  0000f000
    2011-02-21 14:52:02.44 Server      * BROWCLI                        000007FEF3080000  000007FEF3091FFF  00012000
    2011-02-21 14:52:02.44 Server      * AUTHZ                          000007FEFC980000  000007FEFC9AEFFF  0002f000
    2011-02-21 14:52:02.44 Server      * MSCOREE                        000007FEF9C20000  000007FEF9C8EFFF  0006f000
    2011-02-21 14:52:02.44 Server      * ole32                          000007FEFD830000  000007FEFDA31FFF  00202000
    2011-02-21 14:52:02.44 Server      * credssp                        000007FEFC420000  000007FEFC428FFF  00009000
    2011-02-21 14:52:02.44 Server      * pwdssp                         000007FEFC3A0000  000007FEFC3A7FFF  00008000
    2011-02-21 14:52:02.44 Server      * msv1_0                         000007FEFC6C0000  000007FEFC710FFF  00051000
    2011-02-21 14:52:02.44 Server      * cryptdll                       000007FEFCA30000  000007FEFCA43FFF  00014000
    2011-02-21 14:52:02.44 Server      * kerberos                       000007FEFC720000  000007FEFC7D2FFF  000b3000
    2011-02-21 14:52:02.44 Server      * MSASN1                         000007FEFCFC0000  000007FEFCFCEFFF  0000f000
    2011-02-21 14:52:02.44 Server      * schannel                       000007FEFC4D0000  000007FEFC526FFF  00057000
    2011-02-21 14:52:02.44 Server      * CRYPT32                        000007FEFD140000  000007FEFD2A5FFF  00166000
    2011-02-21 14:52:02.44 Server      * security                       0000000073610000  0000000073612FFF  00003000
    2011-02-21 14:52:02.44 Server      * WS2_32                         000007FEFDD20000  000007FEFDD6CFFF  0004d000
    2011-02-21 14:52:02.44 Server      * NSI                            000007FEFDC00000  000007FEFDC07FFF  00008000
    2011-02-21 14:52:02.44 Server      * SHELL32                        000007FEFE4A0000  000007FEFF225FFF  00d86000
    2011-02-21 14:52:02.44 Server      * OLEAUT32                       000007FEFDB20000  000007FEFDBF6FFF  000d7000
    2011-02-21 14:52:02.44 Server      * ftimport                       0000000060000000  0000000060024FFF  00025000
    2011-02-21 14:52:02.44 Server      * MSFTE                          0000000049980000  0000000049D2DFFF  003ae000
    2011-02-21 14:52:02.44 Server      * VERSION                        000007FEFBB70000  000007FEFBB7BFFF  0000c000
    2011-02-21 14:52:02.44 Server      * dbghelp                        0000000072650000  00000000727ADFFF  0015e000
    2011-02-21 14:52:02.44 Server      * WINTRUST                       000007FEFD040000  000007FEFD079FFF  0003a000
    2011-02-21 14:52:02.44 Server      * ntmarta                        000007FEFB890000  000007FEFB8BCFFF  0002d000
    2011-02-21 14:52:02.45 Server      * WLDAP32                        000007FEFE0A0000  000007FEFE0EFFFF  00050000
    2011-02-21 14:52:02.45 Server      * ncrypt                         000007FEFC930000  000007FEFC97DFFF  0004e000
    2011-02-21 14:52:02.45 Server      * bcrypt                         000007FEFC900000  000007FEFC921FFF  00022000
    2011-02-21 14:52:02.45 Server      * PCTLsp64                       000000000B1E0000  000000000B251FFF  00072000
    2011-02-21 14:52:02.45 Server      * mswsock                        000007FEFC840000  000007FEFC893FFF  00054000
    2011-02-21 14:52:02.45 Server      * wship6                         000007FEFC830000  000007FEFC836FFF  00007000
    2011-02-21 14:52:02.45 Server      * wshtcpip                       000007FEFB870000  000007FEFB876FFF  00007000
    2011-02-21 14:52:02.45 Server      * ntdsapi                        000007FEFC020000  000007FEFC046FFF  00027000
    2011-02-21 14:52:02.45 Server      * DNSAPI                         000007FEFC5B0000  000007FEFC60AFFF  0005b000
    2011-02-21 14:52:02.45 Server      * IPHLPAPI                       000007FEFAB50000  000007FEFAB76FFF  00027000
    2011-02-21 14:52:02.45 Server      * WINNSI                         000007FEFAB10000  000007FEFAB1AFFF  0000b000
    2011-02-21 14:52:02.45 Server      * rasadhlp                       000007FEF9EC0000  000007FEF9EC7FFF  00008000
    2011-02-21 14:52:02.45 Server      * fwpuclnt                       000007FEFAAB0000  000007FEFAB02FFF  00053000
    2011-02-21 14:52:02.45 Server      * bcryptprimitives               000007FEFC3B0000  000007FEFC3FBFFF  0004c000
    2011-02-21 14:52:02.45 Server      * SAMLIB                         000007FEFBA90000  000007FEFBAACFFF  0001d000
    2011-02-21 14:52:02.45 Server      * dbghelp                        00000000724F0000  000000007264DFFF  0015e000
    2011-02-21 14:52:02.45 Server      *
    2011-02-21 14:52:02.45 Server      *     P1Home: 0000000000000000: 
    2011-02-21 14:52:02.45 Server      *     P2Home: 00000000005C5C50:  005C003F003F0002  004D005C003A0043  004C005100530053  0054002E00300031  00490057004F0045  0053004D005C004E 
    2011-02-21 14:52:02.45 Server      *     P3Home: 00000000770D8288:  0000000077089860  0000000077092BD0  00000000770A62B0  0001000200010008  0001000200010003  0001000200010004 
    2011-02-21 14:52:02.45 Server      *     P4Home: 0000000000000000: 
    2011-02-21 14:52:02.45 Server      *     P5Home: 0000005600000200: 
    2011-02-21 14:52:02.45 Server      *     P6Home: 0000000000500001:  EA00000000000000  EE0100D8FA8C32D6  1800000000FFEEFF  28000000000C1600  0000000000005001  0000000000005000 
    2011-02-21 14:52:02.45 Server      * ContextFlags: 000000000010000F:  000000FFEEFFEE01  0000000060001800  0000000010012800  0000000010000000  0000000010000000  0000000000001000 
    2011-02-21 14:52:02.45 Server      *      MxCsr: 0000000000001F80: 
    2011-02-21 14:52:02.45 Server      *      SegCs: 0000000000000033: 
    2011-02-21 14:52:02.45 Server      *      SegDs: 000000000000002B: 
    2011-02-21 14:52:02.45 Server      *      SegEs: 000000000000002B: 
    2011-02-21 14:52:02.45 Server      *      SegFs: 0000000000000053: 
    2011-02-21 14:52:02.45 Server      *      SegGs: 000000000000002B: 
    2011-02-21 14:52:02.45 Server      *      SegSs: 000000000000002B: 
    2011-02-21 14:52:02.45 Server      *     EFlags: 0000000000000206: 
    2011-02-21 14:52:02.45 Server      *        Rax: 000000007853EC21: 
    2011-02-21 14:52:02.45 Server      *        Rcx: 000000000F4ACC50:  0000000000000000  00000000005C5C50  00000000770D8288  0000000000000000  0000005600000200  0000000000500001 
    2011-02-21 14:52:02.45 Server      *        Rdx: 0000000000000000: 
    2011-02-21 14:52:02.45 Server      *        Rbx: 0000000000000000: 
    2011-02-21 14:52:02.45 Server      *        Rsp: 000000000F4AD260:  0000000000000000  000000000F4AD510  0000000000000000  000000000C1BCBA8  00000000000042AC  0000000000000000 
    2011-02-21 14:52:02.45 Server      *        Rbp: 000000000F4AFB90:  0000000000000000  0000000000000000  0000000000000000  0000000000000000  0000000076F39220  0000000076F39220 
    2011-02-21 14:52:02.45 Server      *        Rsi: 000000000F4AD510:  000000000C1BCBA0  0000000000000000  0000000000000000  0000000000000000  0000000000000000  0000000000000000 
    2011-02-21 14:52:02.45 Server      *        Rdi: 0000000000000000: 
    2011-02-21 14:52:02.45 Server      *         R8: 0000000000000000: 
    2011-02-21 14:52:02.45 Server      *         R9: 0000000000000000: 
    2011-02-21 14:52:02.45 Server      *        R10: 0000000000000000: 
    2011-02-21 14:52:02.45 Server      *        R11: 000000000F4ADA50:  0000000000000000  00000000005C5C50  00000000770D8288  0000000000000000  0000005600000200  0000000000500001 
    2011-02-21 14:52:02.45 Server      *        R12: 000000000000003F: 
    2011-02-21 14:52:02.45 Server      *        R13: 0000000000000000: 
    2011-02-21 14:52:02.45 Server      *        R14: 000000000F4AE920:  0068005F00780065  006C0064006E0061  00780065005F0065  0074007000650063  0063006E00650020  0074006E0075006F 
    2011-02-21 14:52:02.45 Server      *        R15: 0000000000000001: 
    2011-02-21 14:52:02.45 Server      *        Rip: 000007FEFCFDAA7D:  C3000000C8C48148  9090909090909090  8348EC8348909090  00016A428D0F08F9  74894858245C8948  4D30247C89483824 
    2011-02-21 14:52:02.45 Server      * *******************************************************************************
    2011-02-21 14:52:02.45 Server      * -------------------------------------------------------------------------------
    2011-02-21 14:52:02.45 Server      * Short Stack Dump
    2011-02-21 14:52:02.45 spid13s     The Service Broker protocol transport is disabled or not configured.
    2011-02-21 14:52:02.45 spid13s     The Database Mirroring protocol transport is disabled or not configured.
    2011-02-21 14:52:02.46 Server      000007FEFCFDAA7D Module(KERNELBASE+000000000000AA7D)
    2011-02-21 14:52:02.46 Server      0000000002765A6D Module(sqlservr+00000000019C5A6D)
    2011-02-21 14:52:02.46 Server      0000000002774C56 Module(sqlservr+00000000019D4C56)
    2011-02-21 14:52:02.46 Server      00000000027752F9 Module(sqlservr+00000000019D52F9)
    2011-02-21 14:52:02.46 spid13s     Service Broker manager has started.
    2011-02-21 14:52:02.47 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2011-02-21 14:52:02.47 Server      000000000254954C Module(sqlservr+00000000017A954C)
    2011-02-21 14:52:02.48 Server      0000000076F39380 Module(kernel32+0000000000099380)
    2011-02-21 14:52:02.48 Server      0000000077056228 Module(ntdll+0000000000096228)
    2011-02-21 14:52:02.48 Server      0000000076FD4F48 Module(ntdll+0000000000014F48)
    2011-02-21 14:52:02.49 Server      0000000076FF4F6D Module(ntdll+0000000000034F6D)
    2011-02-21 14:52:02.49 Server      0000000076FD5B2C Module(ntdll+0000000000015B2C)
    2011-02-21 14:52:02.49 Server      000000007700F638 Module(ntdll+000000000004F638)
    2011-02-21 14:52:02.49 Server      000000007700C8F4 Module(ntdll+000000000004C8F4)
    2011-02-21 14:52:02.49 Server      000000007700C822 Module(ntdll+000000000004C822)
    2011-02-21 14:52:02.49 Server      000000000B1E40AD Module(PCTLsp64+00000000000040AD)
    2011-02-21 14:52:02.49 Server      000000000B1E4701 Module(PCTLsp64+0000000000004701)
    2011-02-21 14:52:02.49 Server      000000000B1E5434 Module(PCTLsp64+0000000000005434)
    2011-02-21 14:52:02.49 Server      0000000076EBF56D Module(kernel32+000000000001F56D)
    2011-02-21 14:52:02.49 Server      0000000076FF2CC1 Module(ntdll+0000000000032CC1)
    2011-02-21 14:52:02.49 Server      Stack Signature for the dump is 0x0000000188500D70
    2011-02-21 14:52:02.87 Server      External dump process return code 0x20000001.
    External dump process returned no errors.

    2011-02-21 14:52:02.87 spid9s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    2011-02-21 14:53:20.14 Server      ***Unable to get thread context for spid 0
    2011-02-21 14:53:20.14 Server      * *******************************************************************************
    2011-02-21 14:53:20.14 Server      *
    2011-02-21 14:53:20.14 Server      * BEGIN STACK DUMP:
    2011-02-21 14:53:20.14 Server      *   02/21/11 14:53:20 spid 3972
    2011-02-21 14:53:20.14 Server      *
    2011-02-21 14:53:20.14 Server      * Non-yielding Scheduler
    2011-02-21 14:53:20.14 Server      *
    2011-02-21 14:53:20.14 Server      * *******************************************************************************
    2011-02-21 14:53:20.14 Server      Stack Signature for the dump is 0x0000000000000160
    2011-02-21 14:53:20.88 Server      External dump process return code 0x20000001.
    External dump process returned no errors.

    2011-02-21 14:53:20.88 Servidor    Process 0:0:0 (0x830) Worker 0x00000000809D21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12942773522558. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 91%. Interval: 70460 ms.
    2011-02-21 14:53:20.90 Servidor    Process 0:0:0 (0xa98) Worker 0x00000000809961A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942773520892. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 91%. Interval: 71225 ms.
    2011-02-21 14:54:20.98 Servidor    Process 0:0:0 (0x830) Worker 0x00000000809D21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12942773522558. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 92%. Interval: 131303 ms.
    2011-02-21 14:54:21.00 Servidor    Process 0:0:0 (0xa98) Worker 0x00000000809961A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942773520892. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 92%. Interval: 131325 ms.
    2011-02-21 14:55:21.08 Servidor    Process 0:0:0 (0x830) Worker 0x00000000809D21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12942773522558. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 92%. Interval: 191408 ms.
    2011-02-21 14:55:21.11 Servidor    Process 0:0:0 (0xa98) Worker 0x00000000809961A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942773520892. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 92%. Interval: 191430 ms.
    2011-02-21 14:56:21.20 Servidor    Process 0:0:0 (0x830) Worker 0x00000000809D21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12942773522558. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 92%. Interval: 251511 ms.
    2011-02-21 14:56:21.22 Servidor    Process 0:0:0 (0xa98) Worker 0x00000000809961A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942773520892. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 92%. Interval: 251545 ms.
    2011-02-21 14:57:21.28 Servidor    Process 0:0:0 (0x830) Worker 0x00000000809D21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12942773522558. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 92%. Interval: 311608 ms.
    2011-02-21 14:57:21.31 Servidor    Process 0:0:0 (0xa98) Worker 0x00000000809961A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942773520892. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 92%. Interval: 311630 ms.
    2011-02-21 14:58:21.38 Servidor    Process 0:0:0 (0x830) Worker 0x00000000809D21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12942773522558. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 92%. Interval: 371705 ms.
    2011-02-21 14:58:21.41 Servidor    Process 0:0:0 (0xa98) Worker 0x00000000809961A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942773520892. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 92%. Interval: 371728 ms.
    2011-02-21 14:59:21.47 Servidor    Process 0:0:0 (0x830) Worker 0x00000000809D21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12942773522558. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 91%. Interval: 431801 ms.
    2011-02-21 14:59:21.50 Servidor    Process 0:0:0 (0xa98) Worker 0x00000000809961A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942773520892. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 91%. Interval: 431823 ms.
    2011-02-21 15:00:21.56 Servidor    Process 0:0:0 (0x830) Worker 0x00000000809D21A0 appears to be non-yielding on Scheduler 0. Thread creation time: 12942773522558. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 91%. Interval: 491887 ms.
    2011-02-21 15:00:21.59 Servidor    Process 0:0:0 (0xa98) Worker 0x00000000809961A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12942773520892. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 91%. Interval: 491909 ms.

    Monday, February 21, 2011 5:05 PM
  • The main issue looks like the use of PCTLsp64 module which is present in the SQL address space and is raising an Access Violation. The non-yielding scheduler might be a side effect of this AV. From my searches on "Bing", I find that this module is part of virus monitoring program from PC Tools. If this program is active on your server, then please exclude all folders belonging to Microsoft SQL Server from this scan/monitoring.

    2011-02-21 14:52:02.45 Server * PCTLsp64 000000000B1E0000 000000000B251FFF 00072000

    2011-02-21 14:52:02.49 Server 000000000B1E40AD Module(PCTLsp64+00000000000040AD)
    2011-02-21 14:52:02.49 Server 000000000B1E4701 Module(PCTLsp64+0000000000004701)
    2011-02-21 14:52:02.49 Server 000000000B1E5434 Module(PCTLsp64+0000000000005434)

    And to get to the root cause of the AV, you would need to contact PC Tools support and find out why this issue is occuring. After that DLL has been unloaded from the SQL Server process space, continue to monitor the server and check if the issue re-surfaces.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog: http://troubleshootingsql.com
    Twitter: @banerjeeamit
    SQL Server FAQ Blog on MSDN: http://blogs.msdn.com/sqlserverfaq
    • Marked as answer by msoler Friday, February 25, 2011 8:53 AM
    Monday, February 21, 2011 5:22 PM
  • I've uninstalled the AV and SQL runs properly !!!

    Thank you very much !!!

    Friday, February 25, 2011 8:52 AM