none
frequent systemfreezes

    Question

  • If there's already a thread concerning this issue I apologize for reposting but there's just too many questions to look through.

    Since I installed Windows 7 RC I've been experienceing total systemfreezes frequently. My laptop won't win any awards for it's hardwarepreformance so maybe it's a CPU or RAM -related problem, but I thought I should ask to see if anyone else has experienced this.

    The problem occurs when I work with two windows (or more) open, one of them has often been Mozilla Firefox 3. The computer freezes after a link is clicked or when I scroll through a site, but also from just enlarging a window from the taskbar. This results in me having to force shut-down and reboot. I don't know how accurate the RAM/CPU preformance -gadget is, but according to it my computer runs smoothly, hence my suspicion of the RC being the cause.
    Wednesday, May 20, 2009 7:52 PM

Answers

All replies

  • Big-L....the first thing you may want to do is check the event log (if you haven't already done so), I know it sounds redundant, but sometimes it can give you a clue. The other thing I might suggest, is go into advenced system properies and check your virtual memory settings. By default, it's set to let Windows manage, it will say what the recommended setting (max) should be, like 2500mb. Check "custom" box and you'll see the min & max settings become available. For example, if the Windows recommendation is 2500mb, then increase it a bit to, say....3000mb, and enter that number as both min & max. That way the system will permanently allocate that preset amount on your hard drive for virtual memory. Will reduce a lot of the spin & seek the drive is doing for virtual memory, reducing system overhead, and allow the hard drive to concentrate on seeking info demanded by the instruction sets being processed on behalf of the apps you have running. Can't say if it will help, but it won't hurt, and your system will run more efficiently. Oh, yeah, I'd do a defrag bfore setting the virtual memory.
    I love the smell of diesel in the morning.... you know, that smell....that diesel fuel smell.
    Thursday, May 21, 2009 3:09 AM
  • What kind of CPU do you have and how much RAM?

    -Nick
    Tuesday, May 26, 2009 6:09 PM
  • I am having similar issues.  It seems that about every 15 to 20 minutes the system all but locks up completely.  I can still move the mouse, I can still click on icons, but nothing happens.  The HD light is on but I do not hear any disk access.  Then after about 5 minutes of this, all of a sudden, everything I had tried to do happens.  After that my computer works fine again for about 15 to 20 minutes.  (I told this to a coworker and she joked that it must be in the OS union contract for when the CPU gets breaks.)

    I am running this on a Dell Dimension 9100.  It has two HDs installed.  I loaded Windows 7 on HD1 (350 GB) and kept HD0 (180 GB) as a spare.  It has 2GB of RAM.

    Just a few of the errors that I've gotten:

    (There were 48 of the following)

    Event[0]:
      Log Name: System
      Source: cdrom
      Date: 2009-05-25T17:44:20.762
      Event ID: 7
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    The device, \Device\CdRom0, has a bad block.



    Event[49]:
      Log Name: System
      Source: EventLog
      Date: 2009-05-25T22:07:21.000
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    The previous system shutdown at 10:03:38 PM on ?5/?25/?2009 was unexpected.

    Event[50]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2009-05-25T22:07:00.942
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: Lucas-PC
      Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    (Then some like these)

    Event[53]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-25T22:22:42.214
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    A timeout was reached (30000 milliseconds) while waiting for the Windows Defender service to connect.

    Event[54]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-25T22:22:42.214
      Event ID: 7000
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    The Windows Defender service failed to start due to the following error:
    The service did not respond to the start or control request in a timely fashion.

    Event[55]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-25T22:30:26.970
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.

    Event[56]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-25T22:46:23.971
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.

    Event[57]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-25T23:03:13.974
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.

    (Others like these)

    Event[63]:
      Log Name: System
      Source: Disk
      Date: 2009-05-27T22:44:14.447
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    The driver detected a controller error on \Device\Harddisk2\DR2.

    Event[64]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-28T01:09:28.255
      Event ID: 7022
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    The DNS Client service hung on starting.

    Event[65]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-28T01:13:05.619
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect.

    Event[66]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-28T01:13:05.619
      Event ID: 7000
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    The Software Protection service failed to start due to the following error:
    The service did not respond to the start or control request in a timely fashion.

    Event[67]:
      Log Name: System
      Source: EventLog
      Date: 2009-05-28T01:30:13.000
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    The previous system shutdown at 1:28:33 AM on ?5/?28/?2009 was unexpected.

    (And a lot like these)

    Event[162]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2009-05-29T09:51:46.190
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: Lucas-PC
      Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Event[163]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-29T09:51:59.723
      Event ID: 7026
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    The following boot-start or system-start driver(s) failed to load:
    AvgLdx86

    Event[164]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2009-05-29T13:31:54.128
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: Lucas-PC
      Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Event[165]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-29T13:32:04.933
      Event ID: 7026
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    The following boot-start or system-start driver(s) failed to load:
    AvgLdx86

    Event[166]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-29T13:34:11.968
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.

    Event[167]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-29T13:57:49.973
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Lucas-PC
      Description:
    A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.


    This is all on a stand alone machine that is connected to the internet through dial-up, if at all.

    • Edited by Illvatar Monday, June 1, 2009 1:21 AM More info
    • Proposed as answer by SJir Wednesday, June 3, 2009 4:45 AM
    Wednesday, May 27, 2009 1:55 AM
  • Could you post details about your lap top. like the CPU speed/FSB, RAM MHZ speed
    Wednesday, May 27, 2009 2:40 AM
  • Run the following from an elevated command prompt (right-click - Run as administrator):

    wevtutil qe System "/q:*[System[(Level=1 or Level=2)]]" /f:text > C:\errors.txt

    Then post the results here.
    Wednesday, May 27, 2009 5:57 AM
  • i had the same problem on my laptop i could not get the system to respond the computer just froze
    i couldent even get task maniger to come up i tryed to get the start meun up and it look like it was going to come up but then it stopped and i pulled the battery and power cord out and restarted it ! i get this at least 3x a day
    but when i had vista i had a computer rateing of 3.0 in the user index which is kinda low on my standards.
    but other then the problems i had it works great but they all do untill they get older. (lol)
    hope some one has a solution or windows will figer before the year is up!
    i got this computer for who may want to know http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01069708&cc=us&dlc=en&lc=en&jumpid=reg_R1002_USEN

    but i have a 120 gb hd installed from my 360
    and 2 gb of ram
    Wednesday, May 27, 2009 5:27 PM
  • I'm having the exact same problem! On my Dell M1530 windows Vista worked perfectly. Also other builds of windows 7 worked just fine. Now I installed Windows 7 RC and it totaly freezes every few hours. I doesn't mather if i play games or just watch a movie. Even when i am programming (java for school) in notepad it gets freezes. These are the things i've allready done:

    - start > run > msconfig > startup < Here i only have the Operating System and Nvidia drivers marked. Everything else is off.
    - Updated to the latest drivers from windows update.

    When i do: wevtutil qe System "/q:*[System[(Level=1 or Level=2)]]" /f:text > C:\errors.txt      (the idea of Ryan Capp)

    These are the results:

    Event[0]:
      Log Name: System
      Source: Microsoft-Windows-HAL
      Date: 2009-04-25T10:40:05.212
      Event ID: 12
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: N/A
      User Name: N/A
      Computer: Mark-PC
      Description:
    The platform firmware has corrupted memory across the previous system power transition.  Please check for updated firmware for your system.

    Event[1] is the same as Event[0].

    Event[2]:
      Log Name: System
      Source: BTHUSB
      Date: 2009-04-29T22:07:10.857
      Event ID: 17
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Mark-PC
      Description:
    The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.

    Event[6]:
      Log Name: System
      Source: Service Control Manager
      Date: 2009-05-04T09:45:57.746
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Mark-PC
      Description:
    A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.

    Events between 2 and 6 are Unexpected shutdowns and the same as Event[1]

    Hope someone can help to figure this out.
    Thursday, May 28, 2009 9:25 PM
  • I am having a similar problem that seems to happen mostly,but not all the time, with firefox and flash video.

    My Acer Aspire 5100 with 4 gigs ram (2.7 available) freezes and then does an ole time DOS like dump to the video ram - lots of abstract patterns and flashing lines... This also seemed to be occurring with the blackberry desktop software until I upgraded that.

    So far I'm pretty happy though overall - I hope the rumor that MS will charge more that Vista is unfounded.

    Please give us a decent operating system at a reasonable price (<$200) that I can install on all my home machines (3) and I just might swear off linux for good.

    But if its more than $200 - my acer gets its XP reinstalled.........
    Friday, May 29, 2009 12:13 AM
  • Check out this thread..:

    http://social.technet.microsoft.com/Forums/en/w7itproperf/thread/2468b339-211c-4776-91cc-b1068456c30c

    I t solved the hanging problem for me and a few others

    Friday, May 29, 2009 7:43 AM
  • Hi,

    I faced the same problem. After install Windows 7 RC, the system was freezed ramdomly.

    I tried to resolve the problem with many solutions suggested in the cyber but it wasn't fix out.

    I noticed in the event log, there is an event "A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect." so I checked the Windows Error Reporting Service in services and found it was stopped.

    So I changed to Automatic and started the service. Since then, my windows works fine and not facing system freeze until now.

    Hope this helps.
    Wednesday, June 3, 2009 4:56 AM
  • This fixed the issue for me.

     

    Thanks,

    Jay

    Sunday, February 13, 2011 9:56 PM
  • I am facing the same problem

    A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.

    Event[0]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-25T00:09:58.731
      Event ID: 7023
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The Windows Update service terminated with the following error: 
    %%-2147467243


    Event[1]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T11:44:42.986
      Event ID: 7024
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The Windows Search service terminated with service-specific error %%-1073473535.


    Event[2]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T11:44:42.986
      Event ID: 7031
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The Windows Search service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service.


    Event[3]:
      Log Name: System
      Source: EventLog
      Date: 2012-03-24T12:21:12.000
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The previous system shutdown at 12:17:15 PM on ?3/?24/?2012 was unexpected.


    Event[4]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2012-03-24T12:20:01.896
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: EZRA-PC
      Description: 
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


    Event[5]:
      Log Name: System
      Source: Disk
      Date: 2012-03-24T12:26:11.995
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The driver detected a controller error on \Device\Harddisk1\DR1.


    Event[6]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T12:29:07.729
      Event ID: 7030
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The UDisk Monitor service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly.


    Event[7]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T20:53:15.175
      Event ID: 7026
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The following boot-start or system-start driver(s) failed to load: 
    cdrom


    Event[8]:
      Log Name: System
      Source: EventLog
      Date: 2012-03-24T22:00:39.000
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The previous system shutdown at 9:50:17 PM on ?3/?24/?2012 was unexpected.


    Event[9]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2012-03-24T22:00:26.175
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: EZRA-PC
      Description: 
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


    Event[10]:
      Log Name: System
      Source: EventLog
      Date: 2012-03-24T22:31:53.000
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The previous system shutdown at 10:21:16 PM on ?3/?24/?2012 was unexpected.


    Event[11]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2012-03-24T22:31:41.814
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: EZRA-PC
      Description: 
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


    Event[12]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:06.796
      Event ID: 7024
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The Windows Search service terminated with service-specific error %%-1073473536.


    Event[13]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:06.796
      Event ID: 7031
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The Windows Search service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service.


    Event[14]:
      Log Name: System
      Source: Microsoft-Windows-DistributedCOM
      Date: 2012-03-24T22:32:13.000
      Event ID: 10005
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    DCOM got error "1053" attempting to start the service WSearch with arguments "" in order to run the server:
    {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}


    Event[15]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:13.927
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.


    Event[16]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:13.927
      Event ID: 7000
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The Windows Search service failed to start due to the following error: 
    The service did not respond to the start or control request in a timely fashion.


    Event[17]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:16.745
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.


    Event[18]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:16.745
      Event ID: 7000
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The Windows Search service failed to start due to the following error: 
    The service did not respond to the start or control request in a timely fashion.


    Event[19]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:19.932
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.


    Event[20]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:19.932
      Event ID: 7000
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The Windows Search service failed to start due to the following error: 
    The service did not respond to the start or control request in a timely fashion.


    Event[21]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:21.804
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.


    Event[22]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:21.804
      Event ID: 7000
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The Windows Search service failed to start due to the following error: 
    The service did not respond to the start or control request in a timely fashion.


    Event[23]:
      Log Name: System
      Source: Microsoft-Windows-DistributedCOM
      Date: 2012-03-24T22:32:26.000
      Event ID: 10005
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    DCOM got error "1053" attempting to start the service WSearch with arguments "" in order to run the server:
    {9E175B6D-F52A-11D8-B9A5-505054503030}


    Event[24]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:26.421
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.


    Event[25]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:26.421
      Event ID: 7000
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The Windows Search service failed to start due to the following error: 
    The service did not respond to the start or control request in a timely fashion.


    Event[26]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:26.437
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.


    Event[27]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:26.437
      Event ID: 7000
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The Windows Search service failed to start due to the following error: 
    The service did not respond to the start or control request in a timely fashion.


    Event[28]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:29.561
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect.


    Event[29]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-24T22:32:29.561
      Event ID: 7000
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The Windows Search service failed to start due to the following error: 
    The service did not respond to the start or control request in a timely fashion.


    Event[30]:
      Log Name: System
      Source: EventLog
      Date: 2012-03-24T22:48:27.000
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The previous system shutdown at 10:44:41 PM on ?3/?24/?2012 was unexpected.


    Event[31]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2012-03-24T22:48:19.459
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: EZRA-PC
      Description: 
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


    Event[32]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-25T17:00:30.780
      Event ID: 7026
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The following boot-start or system-start driver(s) failed to load: 
    cdrom


    Event[33]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-25T17:29:44.089
      Event ID: 7011
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.


    Event[34]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-25T17:30:14.103
      Event ID: 7011
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.


    Event[35]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-25T17:30:45.366
      Event ID: 7011
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.


    Event[36]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-25T17:31:15.380
      Event ID: 7011
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.


    Event[37]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-25T21:29:18.380
      Event ID: 7026
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The following boot-start or system-start driver(s) failed to load: 
    cdrom


    Event[38]:
      Log Name: System
      Source: EventLog
      Date: 2012-03-25T21:39:25.000
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The previous system shutdown at 9:31:05 PM on ?3/?25/?2012 was unexpected.


    Event[39]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2012-03-25T21:39:14.158
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: EZRA-PC
      Description: 
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


    Event[40]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-25T21:39:27.234
      Event ID: 7026
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The following boot-start or system-start driver(s) failed to load: 
    cdrom


    Event[41]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-25T21:47:50.388
      Event ID: 7026
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    The following boot-start or system-start driver(s) failed to load: 
    cdrom


    Event[42]:
      Log Name: System
      Source: Service Control Manager
      Date: 2012-03-25T22:32:49.478
      Event ID: 7009
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EZRA-PC
      Description: 
    A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.

    Sunday, March 25, 2012 5:20 PM
  • bump.

    Testing this solution on a Server 2012 R2 RDS. Have this error preceding system slowdowns and eventual hanging. After this error, the server normally <g class="gr_ gr_16 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar multiReplace" data-gr-id="16" id="16">have</g> a lot of the following errors:

    The server {bla-<g class="gr_ gr_22 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="22" id="22">bla</g>-bla} did not register with DCOM within the required timeout.

    We normally have to cold boot the server to recover.


    Kind Regards Jaco Smit


    • Edited by Jaco Smit Thursday, November 30, 2017 6:49 AM
    Thursday, November 30, 2017 6:46 AM