If it starts up at all then it's probably recognizing the memory okay. The fact that it blue screens later sounds like the memory is bad or not fully seated or something.
The specs on the memory seem okay, but that's Kingston's "ValueRAM" line which isn't exactly top quality. I've probably used their ValueRAM in some desktops but I don't think I'd try it on a server.
I guess I'd try just one module at a time and see if it works okay, then try the other by itself. Maybe just one is bad. Find a good memory testing program and give it a good stress test.
I've had genuine HP memory that was bad, right out of the box, so it can happen even with their own stuff... my track record with 3rd party memory like Axiom, Kingston, etc. is even worse, like I might get one bad module out of 50. If I'm putting together a system on a budget and using off brand modules, I'm going to stress test as much as possible and immediately exchange any modules that show problems.
The specs on the memory seem okay, but that's Kingston's "ValueRAM" line which isn't exactly top quality. I've probably used their ValueRAM in some desktops but I don't think I'd try it on a server.
I guess I'd try just one module at a time and see if it works okay, then try the other by itself. Maybe just one is bad. Find a good memory testing program and give it a good stress test.
I've had genuine HP memory that was bad, right out of the box, so it can happen even with their own stuff... my track record with 3rd party memory like Axiom, Kingston, etc. is even worse, like I might get one bad module out of 50. If I'm putting together a system on a budget and using off brand modules, I'm going to stress test as much as possible and immediately exchange any modules that show problems.