Announcement

Collapse
No announcement yet.

System Freezes During Burn In Test

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

  • System Freezes During Burn In Test

    Dear Experts,

    Performed BurnIn Test (64-bit) V8.1 Pro (1009) on 12-Apr-16 8:27:54PM on Dell Latitude E5470: i7-6820HQ (Quad Core, 2.7GHz, 8MB cache), 512GB Samsung SSD (WAVE-encrypted), 2x8GB 2133MHz DDR4 Memory, and Integrated HD Graphics 530 only.

    System hanged after 8hours 49mins 8s of BurnIn Test. Laptop display stayed at 13-Apr-16 5:17AM when I visited the machine at 13-Apr-16 8:24AM. Mouse and keyboards were not responsive at all. Had to perform 4s Power Shutdown. The frozen GUI displayed information as below:

    1. 3D Graphics - 70 cycles - 2.121Million - 0 Error
    2. Advanced Net - 207 cycles - 223Billion - 2 Errors - Unable to connect to Endpoint
    3. CPU - 1143 cycles - 99.19Trillion - 0 Error
    4. Disk(C) - 947 cycles - 10.31Trillion - 0 Error
    5. GPGPU - 1045 cycles - 263Trillion - 0 Error
    6. Memory (RAM) - 865 cycles -17.046Trillion - 0 Error
    7. OpticalDisk(E) - 28 cycles - 245Billion - 0 Error
    8. Serial Port 1 - 987 cycles -56.901Million - 0 Error
    9. Temperature - (100C Threshold) - 0 Error
    10. USB3 - 84 cycles - 2.778Trillion - 0 Error

    There was only 1EA e1dexpress error logged at 12-Apr-16 5:15:14AM in the Event Viewer during BurnIn Test period. e1dexpress states that "Ethernet connection I219-LM Network link is disconnected". Unexpected shutdown was recorded to happen at 5:16:10AM.

    Nonetheless, able to successfully execute 12hours BurnIn Test for a total of 3 times now on the machine and no error is found. My question is how do I figure out what are the possible causes to the past event of system freeze?

  • #2
    Freezes are hard to debug. Could be bad hardware, could be bad device drivers, could be some random external event (power spike, EMI, etc..)

    If the problem isn't reproducible then I don't think you are going to be able to find the cause.

    If you can reproduce the problem, then there are some other options, like narrowing the problem down to just a specific test (e.g. just the 3D test), or running a remote kernel debug session via a null modem cable if the lock up is in the O/S.

    Comment

    Working...
    X