Announcement

Collapse
No announcement yet.

BIT 8 Error

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

  • BIT 8 Error

    This came out of nowhere after a few thousand reboots but I don't think it's actually caused by BIT. We have several SSDs which run the same environment. I would like to find out what did cause it if possible.
    Click image for larger version

Name:	Passmark error.jpg
Views:	1
Size:	55.0 KB
ID:	35269Click image for larger version

Name:	Passmark error2.jpg
Views:	1
Size:	56.9 KB
ID:	35270

    I do have a .DMP which was generated at the time which was 94MB but I 7-Zipped to less than 8MB. Can I send that in an email? Thanks -
    Earl

  • #2
    Yes, send in the dump.
    8MB by Email is OK.

    Also what are the hardware specs for the machine and which version of BurnInTest are you using?

    Comment


    • #3
      P a s s M a r k B u r n I n T e s t L o g f i l e - h t t p : / / w w w . p a s s m a r k . c o m
      = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

      D a t e : T u e M a r 0 1 0 8 : 5 3 : 0 8 2 0 1 6

      B u r n I n T e s t V 8 . 1 P r o 1 0 1 0 ( 6 4 - b i t )

      **************
      SYSTEM SUMMARY
      **************
      Windows Server 2003 "R2" Enterprise Edition Service Pack 2 build 3790 (32-bit),
      1 x Intel(R) Core(TM)2 Duo CPU L9400 @ 1.86GHz,
      7.9GB RAM,
      Mobile Intel(R) 4 Series Express Chipset Family,
      238GB HDD,

      GENERAL
      System Name: SNE-7788280-SM2
      System Model: Montevina platform
      Motherboard Manufacturer: RadiSys
      Motherboard Name: CEGSXTT2A-SL9-8GB
      Motherboard Version: 067-10878-0003
      Motherboard Serial Number: 711128800327
      BIOS Manufacturer: American Megatrends Inc.
      BIOS Version: 18.02.04
      BIOS Release Date: 05/23/2011
      CPU
      CPU manufacturer: GenuineIntel
      CPU Type: Intel(R) Core(TM)2 Duo CPU L9400 @ 1.86GHz
      Codename: Penryn
      CPUID: Family 6, Model 17, Stepping A, Revision E0
      Socket: BGA956
      Lithography: 45nm
      Physical CPU's: 1
      Cores per CPU: 2
      Hyperthreading: Not capable
      CPU features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 DEP PAE Intel64 VMX SMX
      Clock frequencies:
      Measured CPU speed: 1866.8 MHz
      Multiplier: x8.0
      Scalable Bus Speed: 233.4 MHz [Stock: 267.7 MHz]
      Front Side Bus: 933.4 MHz [Stock: 1066.0 MHz]
      Cache per CPU package:
      L1 Instruction Cache: 2 x 32 KB
      L1 Data Cache: 2 x 32 KB
      L2 Cache: 1 x 6144 KB
      MEMORY
      Total Physical Memory: 8061MB
      Available Physical Memory: 7377MB
      Memory devices:
      A1_DIMM0:
      - DDR2, 4096MB, 667MHz,
      A1_DIMM1:
      - DDR2, 4096MB, 667MHz,
      Virtual memory: C:\pagefile.sys (allocated base size 2046MB)
      GRAPHICS
      Mobile Intel(R) 4 Series Express Chipset Family
      Chip Type: Mobile Intel(R) 4 Series Express Chipset Family
      DAC Type: Internal
      Memory: 256MB
      BIOS: Intel Video BIOS
      Driver provider: Intel Corporation
      Driver version: 6.14.10.5132
      Driver date: 9-23-2009
      Monitor 1: 1024x768x32 60Hz (Primary monitor)

      Sending dump as well. Thank You,
      Earl

      Comment


      • #4
        For future reference, there were two I/O error codes in the crash dump, 0xc0000006 (In-page I/O error) and 0xc0000185 (The I/O device reported an I/O error). The actual crash happened outside of BurnInTest in the oleaut32 library when trying to allocate some memory (using SysAllocString).


        According to these error codes it's possible that some paged memory was being read from disk at the time and that read failed though that would normally also result in a bsod in a lot of cases. According to this, https://blogs.msdn.microsoft.com/old...04-00/?p=19963, it can also happen when running a program across a network connection and the network drops.

        In this case, after consulting the system event logs it was seen there were controller errors being logged when accessing the disk and system file corruption that could not be fixed was found when using disk scanning tools.

        Comment

        Working...
        X