Solved Random codes BSOD while gaming, sufring or using Teamspeak

Hi! Please, help me to defeat this plague!

I'm in random BSODs (and random codes... most of the time DRIVER IRQ_NOT_LESS_OR_EQUAL pointing to ntoskrnl.sys) while gaming or just surfing and talking with friends in Teamspeak.

:shock:

Last 2 BSODs pointed to DMM Directx or something similar.

SF Diag. Attached.


Thanks Guys!

Hey,

Uninstall RealTemp and when done, make sure this folder no longer exists:

C:\Program Files (x86)\RealTemp 3.70

Reboot.

50/50 chance that will fix it. If not, please attach new crash dump(s). Also, run CPU-Z and make a screenshot of the first tab, the Memory tab and one each for each stick of RAM of the SPD tab. Attach those too.

Ok, i will uninstall RealTemp and will watch'n'wait.

If new bsods occurs, i'll post what you requested.

Very thanks!

Nothing changed. It wasn't Realtemp

New BSOD happened while talking in Teamspeak, after some gaming.


New SF Diag. and CPUZ shots attached.




I'm in your hands! :shock:

Ok. Your memory is way overclocked and that is surely the issue at hand.

It needs to run at 1600 MHz (what it will show in bios, it will show as 800 MHz in SPD tab when correct.)

Also equally important, the timings need to be set to 9-11-10-28-2N.

Again, also equally important - the VDIMM (RAM voltage) should be increased. 1.5v is standard. Your modules are tested by maker at 1.65v. I would set it to 1.6v as a start, to see how it do (to use slang, heh.)

In addition, it is possible that it may not work at all, since modules appear to be somewhat different from one another. To be guaranteed of no issues, only use EXACT same memory modules and remove the rest. Use CPU-Z, Google and G-Skill site to base your attempts on.

OK i got another 3 bsods in few hours with current settings.

First and second while talking in Teamspeak and gaming, the third while talking (it refers to Headset drivers....?!)

New BSODs Attached.

About memory: i passed hours of memtest without problems and also using tighter timings.
but
i will slow down freq. to 1600mhz (even if they are rated 2133mhz) and timings to 9-11-10-28-2N.
Memory voltage is correct. CPUZ cannot read memory voltage properly (AIDA64 says 1.670v - 1.680v, and bios even more, so its good.)

Memory modules are different but in pair and they got the same specs (apart from one kit, wich has tighter timings... that i relaxed).
If the bsods continue without a culprit, also after lowering freq.s, i will try each kit of ram separately.

Thanks again!

MasterChief said:

Ok. Your memory is way overclocked and that is surely the issue at hand.

It needs to run at 1600 MHz (what it will show in bios, it will show as 800 MHz in SPD tab when correct.)

Click to expand...

They are rated 2133mhz cl 9-11-20-28-2T 1.65v and this is the current setting!

No crash dumps needed any longer. Alleviate mismatched RAM situation as per above.

Set proper frequency too. (800 MHz to be shown in CPU-Z. Try your luck with whatever else if you want, after stable and mismatch no longer exists.)

Best of luck with it.

Update or uninstall while testing:

Updated ladfGSCamd64 (headset driver) and set ram to 1866mhz, cl 9-11-10-28-2N, 1.65v (4930k IMC is certified for 1866mhz).

NO BSODS SO FAR, SO I THINK WE'GOING GOOD!

I'll keep you updated, thanks man!

Very cool.

Don't bother getting hung up about speeds, timings of RAM. There is absolutely no difference in the real world about them. None. The only place ever you can see a difference is in benchmarking the actual RAM (not benchmarking encode time for audio/video or things like that) - so unless you enjoy staring at a screen to see how fast RAM is, it's quite pointless to worry about it. heh heh

Tom's Hardware website has many fascinating conclusions about it, complete with real-world charts and all.

You're welcome.

It did the trick.
Non more BSODs!

THANKS FOR EVERYTHING!