Announcement

Collapse
No announcement yet.

BurnInTestV7.1 Shutdown When System Runs on CFAST But w/o Connecting to any Monitor

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    BurnInTestV7.1 Shutdown When System Runs on CFAST But w/o Connecting to any Monitor

    Hi, I got a Bray Trail box PC and used BurnInTest 7.1 to run the test. When using HDD, SSD or CFAST and connecting to any monitor, it works fine. However, if we test this box PC without monitor for around 4 hours, we'd find BurnInTest shutdown. This happens only with the following scenario. Anything you can suggest?

    1. Bay Trail box PC without connecting to any monitor
    2. Storage must be CFAST
    3. BurnInTest 7.1 nees to stress CPU, memory, storage, 2D, 3D
    Tags: bay trail, cfast, monitor, shutdown
  • #2
    If you don't have a monitor connected how do you know what is happening or happened?

    Does the whole PC shut down or just BurnInTest?

    Is there any error messages, e.g. a crash?

    Are there any errors in the log from BurnInTest?

    What version of Windows are you using?

    32bit or 64bit?

    Video card device drivers are the most common cause of problems. Did you try the same test without the 2D and 3D tests running.

    I assume CFAST is a compact flash card? Are you booting the O/S from the card, or is it acting as an additional hard drive in the a machine, that you are testing with BurnInTest?

    Comment

    • #3
      If you don't have a monitor connected how do you know what is happening or happened?
      => After running BurnInTest for one day, we connected it to a monitor to check the status. This was the time when we noticed this issue.

      Does the whole PC shut down or just BurnInTest?
      => All the s/w, including BurnIn test shut down, but not the PC. (We recorded the LED behavior as well as the system signal. Both showed shutdown wasn't ocurred)

      Is there any error messages, e.g. a crash?
      => When reconnecting the monitor, BurnInTest was found shut down. No error message can be found.

      Are there any errors in the log from BurnInTest?
      => When reconnecting the monitor, BurnInTest was found shut down. No log can be found.

      What version of Windows are you using?
      => Win 8.1 professional

      32bit or 64bit?
      => 64-bit

      Video card device drivers are the most common cause of problems. Did you try the same test without the 2D and 3D tests running.
      => System works OK when w/o 2D and 3D running.

      I assume CFAST is a compact flash card? Are you booting the O/S from the card, or is it acting as an additional hard drive in the a machine, that you are testing with BurnInTest?
      => CFast is kind of compact flash card but in SATA interface. We boot from CFast and run BurnInTest on this card too.

      We have a new finding today. When we use BurnInTest to stress CPU and memory only, but use Winthrax to stress stoarge, the system has been running for over 115 hrs w/o problem. See picture below.
      Click image for larger version Name: BIT+Winthrax.jpg Views: 1 Size: 57.0 KB ID: 34886

      Comment

      • #4
        If all the software on the machine stopped running, the most likely cause is that the machine rebooted.

        As you sure the machine didn't get run Windows update and then reboot itself to update the O/S?

        You can turn on logging from the BurnInTest preferences window to get a log written to disk. So then you can see any errors that occurred, and when the reboot / crash / error happened.

        It is also probably a good idea to check the Windows Event logs around the time to suspect there was the unexpected behaviour.

        Comment

        • #5
          Thank you for the reply. We changed the preference to get a log written to disk. Will see what happened.

          Meanwhile, could you tell me if there's a minimum storage capacity requirement to run stress graphics using BurnInTest and run Win 8.1 Pro at the same time? The CFAST we used is 16GB only. Could it be insufficient buffer capacity during the test program execution that causes the s/w to stop?

          Comment

          • #6
            Following your instruction, we got the log files written to disk. Here's the scenario:
            1. Connect the box PC with a monitor to do the set up and run BurnInTest. Once done, we unplugged the cable.
            2. After running for a couple of hours, we plugged in the cable again to find the BurnInTest shutdown.
            3. We checked the log files and found that once the monitor was unplugged, the system kept getting log note, saying "2D Graphics, Surface lost: Restoring"
            4. The log files, starting from beginning till we reconnect the monitor, take 673MB of capacity.

            3 log files are attached for your reference. Got any clue how this would happen?
            - BIT_log_140604_140324: the first log
            - BIT_log_140605_001459: the second last log
            - BIT_log_140605_001655: the last log (the capacity is relative small)

            It is also probably a good idea to check the Windows Event logs around the time to suspect there was the unexpected behaviour.
            => Could you tell me where the windows event logs are? Do I need to change any setting to get them?

            Please also give us your comment on the mininum storage capacity requirement. Thank you.
            Attached Files
            Last edited by ACHU; Jun-05-2014, 10:55 AM.

            Comment

            • #7
              The 2D and 3D tests should have a monitor connected.

              To see if you system crashed (e.g. unrecoverable device driver crash), you can check the Windows event log by running Windows "Event Viewer", selecting Windows Logs->System, sort the event in chronological order, then look for an "Error" level events around the time of the problem. Specifically you are looking for a system restart. If your system crashed there may be a minidump in C:\Windows\Minidump that may contain useful information.

              To see if BurnInTest crashed, you can check the Windows event log by running Windows "Event Viewer", selecting Windows Logs->Application, sort the event in chronological order, then look for an "Error" level events around the time of the problem. Specifically you are looking for an application error for bit.exe. If you find this, please email us the information for this event.

              The Minimum disk storage capacity required is 30MB, so having 16GB disk storage should not be an issue.

              Comment

              • #8
                Since the system has no monitor connected, it'd keep receiving log files with error note. Is it possible that when the log files accumulated to certain level and the BurnInTest would stop running?

                Comment

                • #9
                  Originally posted by ACHU View Post
                  Since the system has no monitor connected, it'd keep receiving log files with error note. Is it possible that when the log files accumulated to certain level and the BurnInTest would stop running?
                  If the BurnInTest logging ran out of disk space, it would get an internal error writing to the disk and simply not write the log event to the disk. BurnInTest would not stop in this case.

                  Comment

                  Previous template Next
                  Working...
                  X