No announcement yet.

burn in has stop working

  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    We have seen, when running 72-hour burnintests in Xen virtual machines:

    On Vista SP1 32bit, running burnintest 1012:
    Faulting application bit.exe, version 5.3.1012.0, time stamp 0x4715ab72, faulting module unknown, version, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x01010101, process id 0xefc, application start time 0x01c8c3d48f8decae.

    On Vista SP1 32bit, running burnintest 1022:
    Faulting application bit.exe, version 5.3.1022.0, time stamp 0x4850d46a, faulting module unknown, version, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x28272634, process id 0xc94, application start time 0x01c8de315c210b78.

    I'm afraid I don't have access to the burnintest log files from those runs right now.

    Earlier posts from Ian suggest that you think errors like these are caused by something in Vista, or a driver, interacting poorly with burnintest. Is there anything more known about that?

    We have also seen other failures that look like test patterns have overwritten something but that was on 2k3 and that's not something that's been reported on real hardware.

    Once again: I don't think this is a bug in your software. But if there is a bug (in Windows?) that makes burnintest do this (as reported above by jimyin) it would be great to know whether it's understood, fixed, or can be worked around so we can get back to our own bugs.




    • #32
      You should upgrade to the latest patch release to start with. Which is V5.3 Build 1026 as of today.

      The fault offsets 0x01010101 and 0x28272634 don't match the posts above. You are also not using the the same software release and are not running in the same environment. So there is no immediate reason to think this is the same as one of the issues above.

      Crashes at high addresses like 0x28272634 are often device driver faults however. Nothing more can be added based on the information provided.

      Otherwise initially debugging steps have already been covered in the many posts above.