Emerson Exchange 365

• Not Answered

Has anybody seen a workstation PC just power itself off. This is on Ver 11.3 and is an Operator station

The PC just powers itself off, push the power on the PC and it restarts with no alarms or issues. Then it will run any where from 10 to 45 minutes and does it again?? This system has been online for 6 months and never have seen this problem before

DOUG DEWITT

• 3 Dec 2014 6:39 PM
• Cancel

20 Replies

• DOUG DEWITT

  

  • 8 Dec 2014 8:44 PM

  In reply to Matt Stoner:

  No I can not find the call in log and I do not remember it?? It was last Wednesday 12/3/14 I am sure that will not help much may get you to the hay stack that the needle is in?

  • Cancel
• Matt Stoner

  

  • 9 Dec 2014 5:06 PM

  In reply to DOUG DEWITT:

  I haven't found the "needle" but can you tell me the Customer/Site or System ID, I should be able to find the call by this information.

  • Cancel
• Youssef.El-Bahtimy

  

  • 9 Dec 2014 5:28 PM

  In reply to DOUG DEWITT:

  The next step I would recommend is re-installing DeltaV.
  If that doesn't correct things, then re-image/re-install the operating system and DeltaV (or simply jump to this step).
  Troubleshooting this type of problem takes a lot of first-person interaction, or a thorough data gathering effort (event logs, crash dumps etc). The more symptoms described, the better.
  Alternatively, tearing down the system layer by layer (first workstation config, then DeltaV application, then OS, then hardware components, then full replacement...) may be a faster, more cost-effective, and less frustrating solution.

  • Cancel
• Youssef.El-Bahtimy

  

  • 10 Dec 2014 4:36 AM

  In reply to Youssef.El-Bahtimy:

  Another potential cause (that popped into my head as I try to sleep), may be the Windows security policy to 'Shut down the computer when the security audit log is full' or 'Shut down system immediately if unable to log security audits' is active for the domain/machine.
  
  This could explain why the problem did not surface for many months and why it is now frequent, but spaced apart by days:
  
  "Typically, an event will fail to be logged when the security audit log is full and the retention method specified for the security log is either Do Not Overwrite Events or Overwrite Events by Days"

  http://technet.microsoft.com/en-us/library/cc938340.aspx

  
  You should be getting a blue screen with this, but perhaps it is too temporal to be seen.

  • Cancel
• Raimi

  

  • 10 Dec 2014 5:37 AM

  In reply to Youssef.El-Bahtimy:

  In any case, I recommend checking the following is in place for this system:
  
  a.- Go to My Computer, Right click on it and select “Properties”.
  
  b.- Go to the “Advanced” Tab and press the “Settings” button of the Startup and recovery group
  
  c.-Make sure the options for “System Failure” are checked as the following image:
  Send an administrative alert
  Automatic restart
  Write debugging information
  Kernel memory dump
  Dump file path: (If you need to modify this value to assign other directory than the default, just make sure is available all the time, for example do not assign a network drive or removable device)
  
  
  
  With this options, in the event of a BSOD or a system crash, you will have a memory dump from the instant before the crash, that will help to determine the issue.
  
  Other important data to capture during a BSOD event is the stop-code: In the following example, the STOP code is 0x000000D1. This also helps to determine the cause of the crash. This is harder to observe as somebody needs to watch the console while it happens.
  
  Or you can check the eventlog status for the System at System Manage
  a.- System Viewer
  b.- System
  You can check what are the error that came in there follow with the EventID
  
  Good Luck...

  • Cancel