F5F Stay Refreshed Hardware Desktop 奇怪的Ram问题中，使用中文标注x99，Huananzhi F8

奇怪的Ram问题中，使用中文标注x99，Huananzhi F8

奇怪的Ram问题中，使用中文标注x99，Huananzhi F8

M
martino433
Member
Find
54
06-06-2016, 09:30 PM
#1
Before I powered down to tidy up my fans, I follow the usual six-month routine. In a dusty environment, my media system handled all 32 gigabytes from two kits of dd4 one teamgroup running at 3k and a samsung kit at 2400. Because the board supports up to 2400, it actually managed quad channel. After rebooting, I noticed the board stuck on boot code 67, indicating a failure to load the CPU. Initially, I removed one samsung stick, leaving it in slot 1 on channel 1, which also triggered code 67. It was curious that I could have wiped a memory channel—though it’s unlikely and the board had been reliable for three years. Then I swapped the stick to slot one, channel 2, and it worked! Oddly enough, for my intended use I didn’t mind if the memory wasn’t perfectly configured. I moved all four sticks to channel 2 and again hit code 67, pulling the team group. The samsung remained partially populated on channel 2, with the os loading. At this point, I gave up and tried a 32 kit of eec ddr4 I had for another project on channel 1, which worked. I’m considering a bios flash now, though I’m not sure since it seems to be functioning properly. All drives are recognized so far, but I’m still puzzled by this behavior.
Reply
Reply
M
martino433
06-06-2016, 09:30 PM #1

Before I powered down to tidy up my fans, I follow the usual six-month routine. In a dusty environment, my media system handled all 32 gigabytes from two kits of dd4 one teamgroup running at 3k and a samsung kit at 2400. Because the board supports up to 2400, it actually managed quad channel. After rebooting, I noticed the board stuck on boot code 67, indicating a failure to load the CPU. Initially, I removed one samsung stick, leaving it in slot 1 on channel 1, which also triggered code 67. It was curious that I could have wiped a memory channel—though it’s unlikely and the board had been reliable for three years. Then I swapped the stick to slot one, channel 2, and it worked! Oddly enough, for my intended use I didn’t mind if the memory wasn’t perfectly configured. I moved all four sticks to channel 2 and again hit code 67, pulling the team group. The samsung remained partially populated on channel 2, with the os loading. At this point, I gave up and tried a 32 kit of eec ddr4 I had for another project on channel 1, which worked. I’m considering a bios flash now, though I’m not sure since it seems to be functioning properly. All drives are recognized so far, but I’m still puzzled by this behavior.

Reply
Reply
S
SkyInsane
Senior Member
Find
718
06-08-2016, 02:02 AM
#2
Have you changed the CMOS yet? Those Chinese boards have some serious issues—they often use low-quality parts, like reused chips and cheap power regulators. They usually don’t hold up well and can fail quickly.
Reply
Reply
S
SkyInsane
06-08-2016, 02:02 AM #2

Have you changed the CMOS yet? Those Chinese boards have some serious issues—they often use low-quality parts, like reused chips and cheap power regulators. They usually don’t hold up well and can fail quickly.

Reply
Reply
_
_TheSpirit
Member
Find
116
06-09-2016, 03:21 PM
#3
I started with CMOS first. I thought it might be time to rebuild or replace the board since I mainly purchased this one for eight SATA ports. I’m a bit worried about dismantling this system—it has a lot of moving parts and mechanical drives—and it was running smoothly today.
Reply
Reply
_
_TheSpirit
06-09-2016, 03:21 PM #3

I started with CMOS first. I thought it might be time to rebuild or replace the board since I mainly purchased this one for eight SATA ports. I’m a bit worried about dismantling this system—it has a lot of moving parts and mechanical drives—and it was running smoothly today.

Reply
Reply