I've been getting some BSODs lately. 2 of 0x50 BSOD, and 1 0x3b BSOD, all three refering to ntokrnl.exe. Reading up on the BSODs, it seems these are usually caused by memory problems. All of these happened while playing BF4, though to be fair, I haven't been playing much else lately. But, I haven't had any issues with the game crashing or BSODs in the past until just a couple of days ago.
I ran the windows version of memtest (needed to keep my computer online at the time). I think I opened up 8 or 9 instances to use up all of the available memory. Let it ran for a few hours, and it found one error.
Time for more detailed tests. I ran memtest86 on two of the sticks, then one of the remaining sticks, then the last stick. All of them came back error-free after one pass.
I put all the sticks back in, and then my computer proceeded to get past POSTing only to restart on a "Recovering Lost DRAM Size" error. It restarted 3 times, until I finally switched the PSU off and let it sit for a couple of minutes. Started it back up, but noticed in the POST details that it only detected 8GB of RAM this time. But, it at least booted into Windows. Windows detects 16GB of RAM, but says 8GB of it is unusable.
So, what the heck? Is my computer possessed? Should I just call the current set of RAM a loss and buy a whole new set?
The worst part is, this computer also acts as my bitcoin mining host, so I need to keep downtime to a minimum. I can't let it run memtest for 10 hours while I'm away at work.
Specs:
Windows 7 x64
16GB G.Skill DDR3
Gigabyte X58-USB3
i7 920
AMD 5870
No overclocks, default BIOS settings
That's kind of what I'm thinking... 1 pass of memtest wasn't enough.
PSU is a Seasonic 550w.
I've also heard of issues where running 4 sticks can cause problems, but it won't show up on a single-stick memtest because the voltage is slightly higher? Is this something I should be worried about when conducting my tests?
Well that's what I tried to do, but none of them came up with errors during memtest. I kind of wanted to avoid doing 2 full days of memtesting, but it looks like that might be the route I have to take.
Well that's what I tried to do, but none of them came up with errors during memtest. I kind of wanted to avoid doing 2 full days of memtesting, but it lookslike that might be the route I have to take.
Well that whole thing of testing a stick for 24hours is not necessary. Test a single stick for about 4 hours should be enough for errors to show up. Could also be your mainboard /dimm slots being faulty but I admit the probability for the RAM to be faulty is a lot higher.
Well that whole thing of testing a stick for 24hours is not necessary. Test a single stick for about 4 hours should be enough for errors to show up. Could also be your mainboard /dimm slots being faulty but I admit the probability for the RAM to be faulty is a lot higher.
Problem is, it takes me just about as long either way. Between work, kids, and sleep, I'd be lucky to test two sticks in a day even if they only needed 4 hours of testing each.
Bleh, maybe I'll just buy a new set and scrap this one.
Problem is, it takes me just about as long either way. Between work, kids, and sleep, I'd be lucky to test two sticks in a day even if they only needed 4 hours of testing each.
Bleh, maybe I'll just buy a new set and scrap this one.
I've had very similar problems while running more than 2 sticks on in my system. I tested individual sticks and they all seemed fine, but when combined something was just wrong(error seemed to move to different slots and sticks of ram) and I got BSODs or system hangs. Ended up doing exactly what you suggested yourself, bought another set of ram and voila no problem at all.
I've had very similar problems while running more than 2 sticks on in my system. I tested individual sticks and they all seemed fine, but when combined something was just wrong(error seemed to move to different slots and sticks of ram) and I got BSODs or system hangs. Ended up doing exactly what you suggested yourself, bought another set of ram and voila no problem at all.
Do you think a touch more voltage might help the situation? I know with DDR2, if the ram was having issues trying to overclock, giving it some more juice would help with stability. Not sure if the same is the case with DDR3 though.
My brother had this exact same issue where it said 16 GB installed (8.0 GB usuable) This was due to ram sticks being mixed, E.g Kingston + G.Skill Ram (They had different required voltages and CAS timings). Most likely you have a faulty ram chip if the sticks are identical. I'm assuming you have 2x 8GB Sticks.
Are they just called G.Skill or G.Skill ARES/G.Skill RIPJAWS?
You have 16GB of total memory, but that isn't even possible with triple-channel memory. This is probably a stupid question, but are you running your RAM in sets of 3, like you're supposed to? How do you even have 16GB of RAM when you're supposed to be running triple channel memory?
Anyway, bumping up the voltage a tiny bit is how I keep my RAM stable. I have problems at 1.5v/1333, but adding a little bit more fixes it.
My brother had this exact same issue where it said 16 GB installed (8.0 GB usuable) This was due to ram sticks being mixed, E.g Kingston + G.Skill Ram (They had different required voltages and CAS timings). Most likely you have a faulty ram chip if the sticks are identical. I'm assuming you have 2x 8GB Sticks.
Are they just called G.Skill or G.Skill ARES/G.Skill RIPJAWS?
They're the G.Skill Ripjaws series, I think 1333 stock speed but running at 1066. Should be all exactly the same.
I actually swapped two of them from the second to the third set of slots, and also bumped up the voltage to the next step (from 1.5v to 1.54v), and all 16 was detected properly. I am wondering if it was a seat problem, or if maybe the extra voltage bump helped.
Anyway, I've been running memtest86 for more than 12 hours now, awaiting my wife to text me back with the results.
Quote:
Originally Posted by brucethemoose
Wait a second... this is the i7-920 rig right?
You have 16GB of total memory, but that isn't even possible with triple-channel memory. This is probably a stupid question, but are you running your RAM in sets of 3, like you're supposed to? How do you even have 16GB of RAM when you're supposed to be running triple channel memory?
Anyway, bumping up the voltage a tiny bit is how I keep my RAM stable. I have problems at 1.5v/1333, but adding a little bit more fixes it.
I believe the motherboard allows running in dual channel if 4/6 slots are filled. Certainly I don't NEED 16 GB, so if I can identify the bad stick, I'll probably just take it out and run 3 of them in triple channel mode.
Thanks for the tip on the voltage. I am hoping that will cure my problem, at least for now.
That's pretty bad memory if it can't run 1066Mhz at 1.5v, maybe RMA bad if you just bought it.
And I think I'm being OCD, but the fact that you aren't running triple channel is really bothering me, lol. I could swear someone else on some other forum had the same memory problem when he/she was trying to run dual-channel.
That's pretty bad memory if it can't run 1066Mhz at 1.5v, maybe RMA bad if you just bought it.
And I think I'm being OCD, but the fact that you aren't running triple channel is really bothering me, lol. I could swear someone else on some other forum had the same memory problem when he/she was trying to run dual-channel.
Yeah I need to double check the speeds again. I am almost certain it is 1333mhz RAM, but am also almost certain that I saw it @ 1066mhz in the BIOS.
Anyway, the bump in voltage may have done it. After ~14 hours of memtest86, 0 errors appeared. I'll try my normal usage on it again and see if I have any additional problems.
Thanks for the tip regarding triple channel, I'll keep that in mind as well if problems crop up again in the future.
CPU-Z does report that it is running in Dual Channel mode.
DRAM Frequency is 539.7 MHz
FSBRAM is 2:8
NB Freq = 2,158.6
The ram itself is PC3-10700 (667 Mhz)
So I am assuming this means the ram is indeed running at 1080 mhz, and is made for running at 1333 mhz?
If that is the case, I agree it is a bad sign when it is having trouble running at that lower speed! Probably a stick on its way out...
If I put the voltage back at stock, and up the speed to where it is made to run (667/1333), it would be potentially easier to find the bad stick through memtest?
CPU-Z does report that it is running in Dual Channel mode.
DRAM Frequency is 539.7 MHz
FSBRAM is 2:8
NB Freq = 2,158.6
The ram itself is PC3-10700 (667 Mhz)
So I am assuming this means the ram is indeed running at 1080 mhz, and is made for running at 1333 mhz?
If that is the case, I agree it is a bad sign when it is having trouble running at that lower speed! Probably a stick on its way out...
If I put the voltage back at stock, and up the speed to where it is made to run (667/1333), it would be potentially easier to find the bad stick through memtest?
Yes, I SHOULD! But kids and lack of time to fiddle with stuff for hours on end means I'm still stuck back in the age of DDR2 as far as deeper knowledge goes.
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Related Threads
?
?
?
?
?
Ask a question
Ask a question
Overclock.net
27.8M posts
541.2K members
Since 2004
A forum community dedicated to overclocking enthusiasts and testing the limits of computing. Come join the discussion about computing, builds, collections, displays, models, styles, scales, specifications, reviews, accessories, classifieds, and more!