F5F Stay Refreshed Hardware Desktop Probably caused by HDD or RAM failure.

Probably caused by HDD or RAM failure.

Probably caused by HDD or RAM failure.

P
paperclip364
Member
174
12-25-2016, 12:53 PM
#1
Last night I installed a new server (Proliant DL360 g7). I upgraded it with 18x4gb RAM and dual X5650 CPUs earlier. After about an hour, it crashed and came back online after two hours. Then, seven hours later it failed again. In the Event Viewer logs, there was an issue reading from my boot HDD (which showed perfect SMART). I suspect either the RAM wasn’t seated correctly or there’s a driver problem. It’s possible temperatures were a factor, but the crashes didn’t happen during heavy use. This hasn’t occurred before the RAM/CPU upgrade, and I never ran it on for long without an HDD or OS installed. What should I do next? Should I swap the RAM back to its original state first?
P
paperclip364
12-25-2016, 12:53 PM #1

Last night I installed a new server (Proliant DL360 g7). I upgraded it with 18x4gb RAM and dual X5650 CPUs earlier. After about an hour, it crashed and came back online after two hours. Then, seven hours later it failed again. In the Event Viewer logs, there was an issue reading from my boot HDD (which showed perfect SMART). I suspect either the RAM wasn’t seated correctly or there’s a driver problem. It’s possible temperatures were a factor, but the crashes didn’t happen during heavy use. This hasn’t occurred before the RAM/CPU upgrade, and I never ran it on for long without an HDD or OS installed. What should I do next? Should I swap the RAM back to its original state first?

W
Wingman_41
Member
223
12-31-2016, 10:35 PM
#2
RAM failures really mess things up since a memory issue can trick the system into believing another part is faulty. The checks for problems are also kept inside RAM, which means a crash might point to something different than the actual cause. If the issue remains the same, it’s likely not a new RAM module.
W
Wingman_41
12-31-2016, 10:35 PM #2

RAM failures really mess things up since a memory issue can trick the system into believing another part is faulty. The checks for problems are also kept inside RAM, which means a crash might point to something different than the actual cause. If the issue remains the same, it’s likely not a new RAM module.

F
FinnCakePlayz
Member
75
01-01-2017, 12:10 AM
#3
Consider swapping the RAM back. Another odd detail is that it claims 1066MHz but shows 800MHz in HWiNFO and Task Manager. Unclear why. Also, I transferred its original RAM to another server, which adds a bit of hassle.
F
FinnCakePlayz
01-01-2017, 12:10 AM #3

Consider swapping the RAM back. Another odd detail is that it claims 1066MHz but shows 800MHz in HWiNFO and Task Manager. Unclear why. Also, I transferred its original RAM to another server, which adds a bit of hassle.

J
Juan2610
Posting Freak
875
01-05-2017, 08:11 PM
#4
This appears to be an issue with a CPU memory controller about 12 years old. Which memory interface are you configuring, and are you enabling maximum RAM usage?
J
Juan2610
01-05-2017, 08:11 PM #4

This appears to be an issue with a CPU memory controller about 12 years old. Which memory interface are you configuring, and are you enabling maximum RAM usage?

F
195
01-07-2017, 04:29 PM
#5
I replaced all my RAM and everything seems to function properly. No issues reported after two and a half hours. Likely resolved! These CPUs came new, so a failure is improbable. However, according to Event Viewer, there was a problem with CPU 1 not communicating with memory. But in this situation, the fault appears to be the RAM itself. There are no BIOS profiles set for the RAM.
F
Flashplayer551
01-07-2017, 04:29 PM #5

I replaced all my RAM and everything seems to function properly. No issues reported after two and a half hours. Likely resolved! These CPUs came new, so a failure is improbable. However, according to Event Viewer, there was a problem with CPU 1 not communicating with memory. But in this situation, the fault appears to be the RAM itself. There are no BIOS profiles set for the RAM.

J
JJ213
Member
62
01-08-2017, 10:07 PM
#6
It seems like you're describing a common PC setup challenge. The issue likely involves fitting RAM into the slots, and you might have overlooked the instructions Linus provided about gently guiding the RAM until it clicks into place.
J
JJ213
01-08-2017, 10:07 PM #6

It seems like you're describing a common PC setup challenge. The issue likely involves fitting RAM into the slots, and you might have overlooked the instructions Linus provided about gently guiding the RAM until it clicks into place.

V
valkyrie115
Member
65
01-09-2017, 08:11 AM
#7
I’m typically reliable, but installing 18 sticks in just 10 minutes made me a bit careless…
V
valkyrie115
01-09-2017, 08:11 AM #7

I’m typically reliable, but installing 18 sticks in just 10 minutes made me a bit careless…

I
ItzJereBear
Junior Member
14
01-09-2017, 05:07 PM
#8
Only 18 sticks needed! That should take just about 10 minutes, right? It’s probably just a small oversight.
I
ItzJereBear
01-09-2017, 05:07 PM #8

Only 18 sticks needed! That should take just about 10 minutes, right? It’s probably just a small oversight.

B
black_energy_
Member
137
01-11-2017, 11:38 AM
#9
Yes, it's a dual socket LGA 1366 design. It features a triple channel configuration with three memory channels per socket, giving nine channels total for each processor. Newer Xeons support up to four channels per CPU and three sticks per channel, which is impressive. There are also 24 memory slots available on the dual socket.
B
black_energy_
01-11-2017, 11:38 AM #9

Yes, it's a dual socket LGA 1366 design. It features a triple channel configuration with three memory channels per socket, giving nine channels total for each processor. Newer Xeons support up to four channels per CPU and three sticks per channel, which is impressive. There are also 24 memory slots available on the dual socket.