We had a customer report memory errors in MemTest86, but only after first booting windows.
If testing was done directly from a cold boot, there was no errors.
System specs
Intel Core i9-10980XE overclocked to 4.5 GHz, Gigabyte X299X DESIGNARE 10G motherboard, 4x32 GB Samsung M378A4G43AB2-CVF DDR4
Error details
Errors were mostly in tests 11 and 12 and happened in 10bits at a single memory address.
Speculation as to the cause
Speculation is that maybe booting into Windows enabled some piece of hardware (or changed the setting of some hardware). This hardware then started updating this single memory address, vias memory mapped I/O. Maybe a bit coded status field of some sort. So once enabled it stays enabled, corrupting RAM, unless there is a cold boot. Which implies this is really a BIOS bug as the device should have reserved that RAM from the start by use by this device.
If anyone has a similar problem let us know.
If testing was done directly from a cold boot, there was no errors.
System specs
Intel Core i9-10980XE overclocked to 4.5 GHz, Gigabyte X299X DESIGNARE 10G motherboard, 4x32 GB Samsung M378A4G43AB2-CVF DDR4
Manufacturer | BOXX Technologies |
Product Name | APEXX X3_03 |
Version | -CF |
Manufacturer | Gigabyte Technology Co., Ltd. |
Product Name | X299X DESIGNARE 10G |
Lowest Error Address | 0xC49883DF0 (50328MB) |
Highest Error Address | 0xC49883DF0 (50328MB) |
Bits in Error Mask | 00000000000003FF |
Bits in Error | 10 |
Max Contiguous Errors | 1 |
Speculation as to the cause
Speculation is that maybe booting into Windows enabled some piece of hardware (or changed the setting of some hardware). This hardware then started updating this single memory address, vias memory mapped I/O. Maybe a bit coded status field of some sort. So once enabled it stays enabled, corrupting RAM, unless there is a cold boot. Which implies this is really a BIOS bug as the device should have reserved that RAM from the start by use by this device.
If anyone has a similar problem let us know.
Comment