Hardware Odd BSOD problem.

[DinohScene]

I've encountered this odd BSOD problem when I upgraded me "server" PC's RAM from 8GB (4x2GB) to 16GB (4x4GB)

First, it wouldn't boot so after updating the BIOS it proceeded booting into windows.
(after some trouble with the BIOS being corrupt somehow...)

It would BSOD when the system was running for a few minutes and give me a PAGEFAULT_IN_NONPAGED_AREA error.
It also gave me two bluescreens saying that the LAN driver of me motherboard crashed and the HD 5450 GPU driver crashed.
I've reinstalled the drivers and it kept on bluescreening to the PAGEFAULT one.
After doing a RAM test (which came up clear without issues) it kept on bluescreening
Anyway, I proceeded to reinstall windows on the 16GB kit and when it reached ~80% expanding windows files, it BSOD into a BAD_POOL_HEADER error.

I knew that nothing could cause it and suspected it was the RAM somehow.
I've inserted a 4GB kit (4x1GB) that's known to be good and reinstalled windows.
After reinstalling, I've inserted the RAM sticks one by one (1 4GB one at the time) and checked if the system kept on running stable.
I've also done 2 at the time and it kept on being stable.
Now I've got all 4 inserted again (4x4GB) and ran AIDA64's stress test (stressing CPU + FPU + cache + RAM)
It's been running the stresstest for 30 minutes and hasn't bluescreened yet.

Specs of me "server"
Mobo: MSI 790XT-G45
CPU: Athlon 64 x2 6000+
RAM: Samsung DDR2 PC2-6400 4x4GB (16GB in total)
GPU: Sapphire Radeon HD 5450 1GB
SSD: Solidata 32GB.

Me mobo has the latest BIOS update (v2.5)
RAM settings in BIOS are on auto and the system isn't overclocked (restored it to stock to eliminate that possibility)

Any insight would be amazing!

 

[Tom Bombadildo]

Sometimes reseating RAM just fixes random problems like that, but it'd probably be best to keep running tests for a bit to see if anything goes wrong.

 

[DinohScene]

Done that multiple times.
30 minute stresstest where the RAM gets filled up to 95% capacity, no issues what so ever.

 

[Armadillo]

Might have just needed reseating. I would'nt be happy to declare it as fine with just 30min though. I've had memory where errors haven't show until 6+ hours of memtest. I normally let memtest run overnight for at least 12 hours before I'm happy the memory is fine.

 

[Tom Bombadildo]

Yeah, try running an extended test overnight to see if any errors pop up. If so, you know something is up somewhere. If not, you're probably in the clear.

 

[DinohScene]

I'll deffo run a 12 hour test on it.
Any recommendations?

 

[Armadillo]

I'll deffo run a 12 hour test on it.
Any recommendations?

Asus Realbench for full system stablity (despite the name, you can use it on anything). Runs various stress test that will put all the components under load.

For just memory, either memtest86 or memtest86+, these are far more thorough on testing the memory. 86+ is a fork of 86 originally made to add support for more cpus etc. Memtest was sold to passmark at some point and has since been updated and is now the more up to date one. Either will do though.

 

[DinohScene]

Cheers.
I'll run memtest86 then for 24 hours.

Update on the situation (untested)
It's been stable.
Have put it back into use with media streaming again and hasn't thrown any error or anomaly.

 

[DinohScene]

Declared the RAM dead.
It had really odd issues when memtest ran.

I can't sleep properly knowing there's bad RAM in me server ;/

Cheers anyone who helped me.