Announcement

Collapse
No announcement yet.

burn in has stop working

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • burn in has stop working

    Dear Sir,

    There is an error message when I test burn in under Vista,OS pop up an error message which showing"burn in has stop working",SW hang up,but OS is active,intel G31 and AMD RS740 all have the issue,and it is random,please help the to check and give your comment,many thanks.

  • #2
    Can you email us the crash address from the system event log to help [at] passmark [dot] com


    This is often caused by BurnInTest exercising a faulty device driver.

    I would start by checking you have the latest graphics card device driver - in our experience this is the most likely candidate.

    If this does not resolve the problem, then start reducing the test set until you have the smallest test set that causes the problem (e.g. just the Network test running). This should help direct you to the problem hardware or device driver.

    Can you describe the problem in more detail, such as what tests are running, how long into the tests does the problem occur? Which version of BurnInTest are you using, eg. 5.3.1014

    Regards,
    Ian

    Comment


    • #3
      BurnIn test stop working

      Dear Sir:
      Same issue find too,
      Some units appear this fail symptom only run burnin program, and fail appear between 2~8 hours test. and fail rate about 3%.

      BurnIn V5.3 1012 & 1014

      Both fail on Intel and AMD platform:
      Intel Platform: CPU: Intel(R) Core(TM)2 Duo P8600 & P9300
      Chipset: Intel Cantiga (GM & PM)/ICH9M
      OS: Windows Vista Ultimate, Service Pack 1
      AMD Platform: CPU: AMD Turon QL60, M82
      Chipset: AMD RS780M/SB700
      OS: Windows Vista Ultimate, Service Pack 1

      Test Items:
      CPU-Maths
      CPU-SIMD
      Memory(RAM)
      2D Graphics
      3D Graphics
      Disk
      Sound
      Last edited by jimyin; 04-30-2008, 08:38 AM. Reason: add fail picture

      Comment


      • #4
        Did you try Ian's suggestion to reduce the test set to insolate the problem.

        How many machines did you test to calculate the 3% rate? If you are seeing a 3% failure after testing 100's of machines, and all the machine are in exactly the same configuration, then it might be a real hardware issue. 3% failure wouldn't be too surprising for new PC's.

        More details of the actual error would also help. I note that you post says you added a picture. But I don't see any picture.

        Comment


        • #5
          In addition, for a "BurnInTest has stopped working" error we also need the following information:
          - The specific build number: eg. BurnInTest Professional v5.3.1014
          - The address related to this problem, eg 0x00412345. If this information is not available from a link from the "BurnInTest has stopped working" error window then you can normally get this information from the Windows Application event log. In XP (other operating systems will be similar) the Application event log is here:

          Start-> right click "My Computer" and select Manage, double click "Event Viewer" on the left hand side of the window, double click "Application" and find the event of type "Error" around the time the problem occurred. This will contain information like:
          "Faulting application bit.exe, version 5.0.1003.0, faulting module bit.exe, version 5.0.1003.0, fault address 0x00412345."

          So if you could also send this information.

          Regards,
          Ian

          Comment


          • #6
            Dear Sir:
            "Did you try Ian's suggestion to reduce the test set to insolate the problem" -->Not have this test yet, for the units on my hand is not enought and the symptom is not easy to reappear.

            We have more than 5 project all appear the symptom. And HW design have huge different of the five project, so we don't think it is HW issue.

            There is one of failure unit error messae
            "Faulting application bit.exe, version 5.3.1014.0, time stamp 0x479fa8c3, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x27262535, process id 0xc18, application start time 0x01c8452a70f1139d."

            Comment


            • #7
              BTW, did you the test burnIn program on OS: Windows Vista Ultimate, Service Pack 1

              Comment


              • #8
                This address is outside the BurnInTest software address space and the faulting module is Unknown (not bit.exe). The address would typically imply that there is a fault in a dll (dynamic link library) that BurnInTest has loaded and exercised, e.g. a DirectX library such as d3d9.dll. Please check some of your other systems and see if the fault information (as posted) is the same for other systems. Also, when you next find a system with this problem, please start reducing the tests to find the minimum test set.

                I would make sure you have the latest DirectX 9.0c installation and device drivers.

                Regards,
                Ian

                Comment


                • #9
                  Dear sir:
                  For burinin program stop working issue, there are 12 units fail again. All the fail units have the same error code 0X005. (test items:CPU-Maths,CPU-SIMD,Memory(RAM),2D Graphics,3D Graphics,Disk,Sound)
                  We take the 12 units to two group to do below reducing test(GroupA: uints 1~6, GroupB: units 7~12) base on below test result, would you give us some sugestion?
                  -----------------------------------------------------------------------
                  Step1: GroupA: 2D+3D, 6h test PASS
                  GroupB: CPU-Maths+CPU-SIMD+Memory(RAM)+Disk+Sound, 6h test fail 5 units of 6 units.
                  -----------------------------------------------------------------------
                  Step2: GroupA:CPU-Maths+CPU-SIMD+Memory(RAM)+Disk, 6h test fail 3 units
                  GroupB:CPU-Maths+CPU-SIMD+Memory(RAM)+Sound, 6h test PASS
                  -----------------------------------------------------------------------
                  Step3: GroupA: CPU-Maths+CPU-SIMD+Disk, 6h test PASS
                  GroupB: Memory(RAM)+Disk, 6h test one unit fail
                  -----------------------------------------------------------------------
                  Step4: GroupA: Memory(RAM) 6h test PASS
                  GroupB: Disk 6h test PASS
                  -----------------------------------------------------------------------

                  Comment


                  • #10
                    All the fail units have the same error code 0X005
                    In your previous quote you said it was 0xC0000005. It would help to be precise. Does the fault offset address 0x27262535 also always remain the same for each crash or is it somewhat random?

                    If it is somewhat random then it might be a temperature related issue or EMI. If the fault offset address is always the same then it is more likely a software issue.

                    Comment


                    • #11
                      When you get "... has stopped working" then the useful information is:
                      - the software address where the problem occurs. On 32-bit Windows this is always a 32-bit number, i.e 0x12345678 (8 hexadecimal digits). This address can be in the software, BurnInTest (.exe), a device driver (.sys) , a Library (such as a DirectX dll) or the Windows Operating System. The previous address you sent was not in the BurnInTest address space and was not in the Windows Operating System address space (but rather appeared to be a dll). The new address is not complete, and I guess is not actually the address.
                      - the type of error, again this is a 32-bit number , i.e 0x12345678 (8 hexadecimal digits) (e.g. 0xC0000005 is an Access Violation).

                      If you could go through the Windows application event log on ALL systems that failed and post this information it may help (as described in a previous post). This should help determine if it is the same problem on all systems. The Number you sent does not help as it is not complete.

                      Your testing would seem to suggest that there is a problem when the Memory and Disk tests are run together. This may imply a problem like your Disk drive controller device driver failing under a low memory resource scenario. I would suggest looking at updating your Disk drive controller device drivers and RAID BIOS (if relevant).

                      Which Memory test are you running?
                      What type of Disk arrangement do you have?

                      Regards,
                      Ian

                      Comment


                      • #12
                        Add another 8 units fail information:
                        1. Faulting application bit.exe, version 5.3.1014.0, time stamp 0x479fa8c3, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x2221203a, process id 0x4e8, application start time 0x01c84758cf1a031e.
                        2. Faulting application bit.exe, version 5.3.1014.0, time stamp 0x479fa8c3, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x2221203a, process id 0x874, application start time 0x01c8473921ff6fa9.
                        3. Faulting application bit.exe, version 5.3.1014.0, time stamp 0x479fa8c3, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x3f800021, process id 0xe7c, application start time 0x01c84751a7037476.
                        4. Faulting application bit.exe, version 5.3.1014.0, time stamp 0x479fa8c3, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x55594f87, process id 0xb98, application start time 0x01c847992464f3e6.
                        5. Faulting application bit.exe, version 5.3.1014.0, time stamp 0x479fa8c3, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x2221203a, process id 0xfa8, application start time 0x01c8474c1b87a996.
                        6. Faulting application bit.exe, version 5.3.1014.0, time stamp 0x479fa8c3, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x27262535, process id 0x200, application start time 0x01c8479983355285.
                        7. Faulting application bit.exe, version 5.3.1014.0, time stamp 0x479fa8c3, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x27262535, process id 0xe84, application start time 0x01c8479b911fa94c.
                        8. Faulting application bit.exe, version 5.3.1014.0, time stamp 0x479fa8c3, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x55594f87, process id 0xd14, application start time 0x01c84785affb3c28.
                        9. Faulting application bit.exe, version 5.3.1014.0, time stamp 0x479fa8c3, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x2221203a, process id 0xdb4, application start time 0x01c8479c2d2efc82.

                        Comment


                        • #13
                          Dear Ian sir:
                          We have 5 project have the same failing, Memory and Disk not with the same type.
                          Memory: DDR2 (667)1G, 2G, 4G, DDR3 2G
                          Disk: Sata 120G,160G, 250G

                          Comment


                          • #14
                            Had done below test:
                            Step5: 12 uints only test Memory (100% loading), 6h test PASS
                            Step6: 12 uints only test Disk (100% loading), 6h test PASS
                            Step7: 12 units test 2D+3D+CPU-Maths+CPU-SIMD+sound+Memory(RAM), 6h test pass
                            Step8: 12 units test 2D+3D+CPU-Maths+CPU-SIMD+sound+Disk, 6h test one unit fail

                            Base on above test, it seems Disk + other test items lead BurnIn program stop working.
                            Would you have some opinion?

                            Best regards
                            Jim

                            Comment


                            • #15
                              It is not conclusive, but yes it would seem that it is the disk test with another test. Are you submitting the error to Microsoft when you get the error (from the error Window, select the "Send Error Report" button) as this will give us more information about the problem.

                              Regards,
                              Ian

                              Comment

                              Working...
                              X