I Keep Getting BSODs with Different Errors

[Vausch]

So a few weeks ago I found out my RAM wasn't running at the advertised speed, so I set it to go from 1600 to 2133 by using its default profile to make Fallout 4 run smoother.

Since then I've been getting a BSOD almost every day, and often the reason changes.

Sometimes (most commonly) it's "Not less or equal", and most recently was "System Service Exception".

I've updated all my drivers, ran a virus scan (nothing), updated my video card, am running the latest BIOS, ran a system check for OS errors (none found), but nothing seems to stop them.

Admittedly I haven't switched my RAM back to 1600 but I'd like to at least get the speed I was promised.

MOBO Is a MSI Z87-GD65
Intel core i7 4470K @ 3.5ghz
16gb DDR3 2133
Seagate 2tb Hybrid drive
850W PSU
Nvidia GTX 760
Windows 7 Ultimate 64-bit

 

[Loonyyy]

Switch the RAM back down.

I know, it's not what you want to hear, but that's your problem there.

It could be the timings, RAM can be problematic when you change the clock speed. It's not my area of expertise, but the RAM timings can mess with you, and IIRC, it's important when changing the clock.

 

[Vausch]

Switch the RAM back down.

I know, it's not what you want to hear, but that's your problem there.

It could be the timings, RAM can be problematic when you change the clock speed. It's not my area of expertise, but the RAM timings can mess with you, and IIRC, it's important when changing the clock.

Is the RAM the cause of all of them?

The second to last one said it was related to "iusb3(couldn't read)". I read that was due to a driver issue on the USB side.

Is there something I can do for the RAM to fix it? It's this one http://www.newegg.com/Product/Product.aspx?Item=N82E16820231689 if it helps.

 

[Loonyyy]

Switch the RAM back down.

I know, it's not what you want to hear, but that's your problem there.

It could be the timings, RAM can be problematic when you change the clock speed. It's not my area of expertise, but the RAM timings can mess with you, and IIRC, it's important when changing the clock.

Is the RAM the cause of all of them?

The second to last one said it was related to "iusb3(couldn't read)". I read that was due to a driver issue on the USB side.

Is there something I can do for the RAM to fix it? It's this one http://www.newegg.com/Product/Product.aspx?Item=N82E16820231689 if it helps.

I reckon. I reckon it's the change to the RAM clock, and it's probably causing a variety of errors.

I'd look up the optimal RAM timings and check that they're correct. I did a bit of googling, and it seems that board should be fine with that clock speed, although there's potential stability problems depending on the CPU clock.

The other thing to remember is that RAM clock doesn't really matter that much. It's sort of a so-so thing, messing with RAM clocks is often avoided, because it doesn't provide increases in performance in line with CPU and GPU clock, and runs a risk of stability issues.

 

[Vausch]

Switch the RAM back down.

I know, it's not what you want to hear, but that's your problem there.

It could be the timings, RAM can be problematic when you change the clock speed. It's not my area of expertise, but the RAM timings can mess with you, and IIRC, it's important when changing the clock.

Is the RAM the cause of all of them?

The second to last one said it was related to "iusb3(couldn't read)". I read that was due to a driver issue on the USB side.

Is there something I can do for the RAM to fix it? It's this one http://www.newegg.com/Product/Product.aspx?Item=N82E16820231689 if it helps.

I reckon. I reckon it's the change to the RAM clock, and it's probably causing a variety of errors.

I'd look up the optimal RAM timings and check that they're correct. I did a bit of googling, and it seems that board should be fine with that clock speed, although there's potential stability problems depending on the CPU clock.

The other thing to remember is that RAM clock doesn't really matter that much. It's sort of a so-so thing, messing with RAM clocks is often avoided, because it doesn't provide increases in performance in line with CPU and GPU clock, and runs a risk of stability issues.

Far as I can see they are. When I go to the click BIOS it has a preset to get the ram at the advertised 2133 speed and timing. Though I couldn't figure out how to alter the voltage, but it didn't seem to need changes as many said 1.6v is enough for that setting.

I guess if it doesn't matter I can just reset it but it feels a little obnoxious that the RAM won't run at the speed it was advertised. Far as I can tell Haswell chips are able to handle 2133mhz without problems.

 

[Vausch]

snip

Just got another, first time in a week. This time it was "Reference by pointer". Never seen that one before.

I don't understand how or why putting my RAM at the default speed would cause this. I have a good CPU and everybody else is telling me Haswell chips are more than capable of handling 2133mhz. The timing shouldn't be a problem because it's set to a default XMP profile and the voltage should be fine.

If this does keep up I'll return it to 1600mhz but I'd really rather get the speed I paid for.

 

[Albino Boo]

snip

Just got another, first time in a week. This time it was "Reference by pointer". Never seen that one before.

I don't understand how or why putting my RAM at the default speed would cause this. I have a good CPU and everybody else is telling me Haswell chips are more than capable of handling 2133mhz. The timing shouldn't be a problem because it's set to a default XMP profile and the voltage should be fine.

If this does keep up I'll return it to 1600mhz but I'd really rather get the speed I paid for.

You have the erroneous idea that 2133 is native speed of the RAM, that's not true. 2133 is an overclocked speed and if it boots at 1600 then that's the actual native speed as programmed into the SPD chip on the RAM sticks. Depending on a particular system the RAM is installed in it may or may not reach 2133. The differences in voltage regulators, memory controllers etc. from one system to another can be enough that one will get 2133 and another may only reach 1866 and run stable in the system. Look all the issues you have are related errors with RAM, you have made a change to your RAM settings so the logical thing to do is reverse the changes. Now if you want get more than 1600 manually overclock to see how fast you can get without the system going unstable.

 

[Vausch]

snip

Just got another, first time in a week. This time it was "Reference by pointer". Never seen that one before.

I don't understand how or why putting my RAM at the default speed would cause this. I have a good CPU and everybody else is telling me Haswell chips are more than capable of handling 2133mhz. The timing shouldn't be a problem because it's set to a default XMP profile and the voltage should be fine.

If this does keep up I'll return it to 1600mhz but I'd really rather get the speed I paid for.

You have the erroneous idea that 2133 is native speed of the RAM, that's not true. 2133 is an overclocked speed and if it boots at 1600 then that's the actual native speed as programmed into the SPD chip on the RAM sticks. Depending on a particular system the RAM is installed in it may or may not reach 2133. The differences in voltage regulators, memory controllers etc. from one system to another can be enough that one will get 2133 and another may only reach 1866 and run stable in the system. Look all the issues you have are related errors with RAM, you have made a change to your RAM settings so the logical thing to do is reverse the changes. Now if you want get more than 1600 manually overclock to see how fast you can get without the system going unstable.

Are you sure? This is the RAM in question http://www.newegg.com/Product/Product.aspx?Item=N82E16820231689 and its rated memory speed is 2133.

And the XMP profile is defaulted to 2133.

I've seen similar situations in which a friend's computer defaulted to 1600 despite his RAM being 1333.

But if that's the case then next time I get a BSOD I'll lower it.

 

[Albino Boo]

Are you sure? This is the RAM in question http://www.newegg.com/Product/Product.aspx?Item=N82E16820231689 and its rated memory speed is 2133.

And the XMP profile is defaulted to 2133.

I've seen similar situations in which a friend's computer defaulted to 1600 despite his RAM being 1333.

But if that's the case then next time I get a BSOD I'll lower it.

The max Ram speed on a haswell is 1600, anything quicker comes from overclocking the memory controller. Your friend probably had a sandy bridge cpu which has max ram speed of 1333

 

[Vausch]

Are you sure? This is the RAM in question http://www.newegg.com/Product/Product.aspx?Item=N82E16820231689 and its rated memory speed is 2133.

And the XMP profile is defaulted to 2133.

I've seen similar situations in which a friend's computer defaulted to 1600 despite his RAM being 1333.

But if that's the case then next time I get a BSOD I'll lower it.

The max Ram speed on a haswell is 1600, anything quicker comes from overclocking the memory controller. Your friend probably had a sandy bridge cpu which has max ram speed of 1333

You got it backwards on his. His ram speed defaulted to 1600 when his ram was 1333.

Still, if that's the case then shoot, I wasted money. I found nothing that said Haswell couldn't handle 2133 but if it's seriously maxed at 1600 then what the hell?

 

[Albino Boo]

You got it backwards on his. His ram speed defaulted to 1600 when his ram was 1333.

Still, if that's the case then shoot, I wasted money. I found nothing that said Haswell couldn't handle 2133 but if it's seriously maxed at 1600 then what the hell?

1600 is the max speed at which the voltage regulators, memory controllers etc tolerances will add to make the system unstable. The Haswell can potentially handle faster speeds but that comes at the risk of instability. When you load an XMP profile you are overclocking the RAM, so you run the risk of instability because of the tolerances of parts made by different manufacturers stacking up. You can either try manually overclocking the RAM is find a stable speed or load a slower XMP profile You also could check XMP bios settings, it should configure the voltage and timings correctly but sometimes it misses. Look at the Memory tab against the XMP profile in the SPD tab.

 

[residentout1]

I am also getting BSOD all the time when am on the internet it seems to happen when my pc loads pages but it can crash on steam pages or when I download on it the error goes from 0000000007e of 000000000d1 (number of zeros I don't know but I know the last two)