Announcement

Collapse
No announcement yet.

BurnInTest V5.3 pro (1004) with Error "access violation at 0x55594FD8"

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

  • BurnInTest V5.3 pro (1004) with Error "access violation at 0x55594FD8"

    BurnInTest Version : V5.3 pro (1004)
    Common Information
    1.OS : Windows 2008 SP2 32-bit
    2.Chipset : Tylersburg 36D + ICH10-R
    3.VGA : ASPEED 2050
    4. Disk : SATAII x 6 (1st + 2nd SATAII HDDs are set to be RAID 1). So there are 5 HDDs in the OS.
    5. Test Set : a. CPU-Maths b. CPU-SIMD c. Memory (RAM) - standard d. Disk Test (all of the testing item are set to 100%)

    Failed Sympton@platform-1 :
    CPU Type : Intel Xeon(R) CPU X5650 @ 2.66GHz
    a. Duration : 002h 46m 38s
    b. error information (Error : Access violation at 0x55594FD8 (tried to write to (0x03790FFC), program terminated.)

    Failed Sympton@platform-2 :
    CPU Type : Intel Xeon(R) CPU L5530 @ 2.40Hz
    a. Duration : 000h 32m 54s, 000h 14m 07s,
    b. error information (Error : Access violation at 0x55594FD8 (tried to write to (0x03ED0FFC), program terminated.)

    The platform-2 have run the testing over 20hrs and 0 errors are found at 1st time. But we got the error when we ran BurnIn Test for testing again.

    Q1. What does the" Access violation at 0x55594FD8 (tried to write to (0x03ED0FFC / 0x03790FFC)" mean?
    Q2. How could i check the " Access violation at 0x55594FD8 " which is caused by memory allocation, H/W or driver issues ?

  • #2
    Access violation means some piece of software on the machine tried to read or write some RAM that wasn't allocated to it. Causing a crash.

    The release you are using it over 4 years old. And we don't support it any more.
    http://www.passmark.com/products/bit_history.htm
    You should upgrade to the latest release and see if the problem persists.

    Comment

    Working...
    X