bsod ntoskrnl.exe

[bananaphone5]

I thought changing ram timings can't damage them.
I have this ram http://www.kingston.com/dataSheets/KHX1333C7AD3_4G.pdf
My motherboard gigabyte ga-b75m-d2v ism for some reasonm underclocking them to cl9.
So i changed it manually and i started getting bluescreens, i didn't change voltage, my mobo can't even do it, so i changed it back and even i reinstall my os, i am still getting them.
+ i checked them with memtest and 0 errors, it is weird.
I am getting ntoskrnl.exe bsod, which is caused by bad ram.
What you think about it please ?

 

[mikeymikec]

ntoskrnl.exe is the NT Kernel. If a BSOD occurs, it means that the kernel couldn't handle an unexpected situation any better and so reports it like this. It does not mean bad RAM specifcally, it could be a multitude of different things.

When you get a BSOD it normally states a number like 0x00000024, and maybe a message in all caps like NTFS_FILE_SYSTEM. That's the most useful thing to google when you need a bit of help.

If you are worried about RAM being a problem, you could burn memtest86+ to a CD and boot your system from it, run that for a few passes and see if any errors show up.

 

[bananaphone5]

I have bad_pool_header under bug check string and 0x00000019 under bug check code and i wasn't still able google specific thing. It is still to general.

 

[mikeymikec]

bad pool header has a tendency to be RAM related IIRC. Worth a few passes with memtest86+, especially if you have been playing with timings.

 

[bananaphone5]

I already have tested them with memtest, how i write, and i did it again right now, 3 passes 0 errors.
I didn't play with them, but my motherboard set them to cl9 for some reason.
I only set them to their default timings.
And i read from multiple sources, that changing timings can only cause instability and it can't damage ram.
I didn't change voltage, my mobo even can't do it i think.
It looks like ram issue, because it started when i changed timings, but i am confused with 0 errors in memtest.

 

[Coup27]

Tried resetting CMOS just incase your BIOS has got messed up?

 

[bananaphone5]

It feels pointless to me.
I only changed timings and then put it back, exactly how it was, which is auto, so i am certain, it is default.

 

[Coup27]

You are probably correct, however you have a fault which you can't diagnose so if you want to get to the bottom of it you are going to have to work logically and rule things out, even if that means spending some time on things just to eliminate them. Your call though.

 

[bananaphone5]

If it will happen again, i give it try, thanks.

 

[mikeymikec]

Btw, I hadn't noticed that you said you had run memtest already, sorry about that, though bear in mind that sometimes RAM issues only come to light with a lot of passes; if you want to try it again, try it overnight, but for now if I were you I'd focus my efforts on other suggestions during daytime.

BIOS's can be funny things too. I had a board once where the RAM would have problems if I set the same timings but manually (as it would when it was set to auto), but it would work fine on auto.

Running Prime95 might be worth a shot, I tend to run it for half an hour at a time.

Is it always the same BSOD?

- edit - When I posted this, your 07:22AM post appeared afterwards.

 

[bananaphone5]

I reinstalled my pc.
And before, i didn't check, bug check string and code.
I only know it was ntoskrnl.exe, which could be a lot of stuff, since it is kernel.
If it will happen again i let you know.

 

[redzo]

1. This module has been tested to run at DDR3-1333 at a low latency
timing of 7-7-7-20 at 1.65V.
2. The SPD is programmed to JEDEC
standard latency DDR3-1333 timing of 9-9-9.

http://www.kingston.com/dataSheets/KHX1333C7AD3_4G.pdf

1. Your memory can run stable at ddr3-1333 / 7-7-7-20 @1.65 v. But you probably have to set everything manually in BIOS.

2. This tells you that when running at 1333Mhz, the bios auto adjusts the memory according to their SPD profile. In this case, it's 9-9-9@1333.

Maybe the voltage is your issue to begin with. Have you checked the current voltage? According to kingston it is safe to set the voltage to 1.65v.

As for memtest86+,
If I under-volt my ram, windows BSODs in 15 minutes max, but it takes memtest at least 24 hours in order to generate only one memory error. This is the thing with memtest: sometimes it is very time consuming in order to get a confident test result.