Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD, "ntoskrnl.exe"

09 Jun 2014   #11
Erox

Winsows 7 Ultimate x64
 
 

OK, seems like we got a breakthrough here- did 1-2 passes of memtest, it detected more than 300 000 errors and it keeps detecting more as im writing this post from my laptop. (wow...)

This is really, really. Reason why is because i sent my RAM stick to support a couple of months ago, I recieved them a a few of weeks later with a picture of a successful 9-pass memtest and a letter telling me there was nothing wrong with my RAM. But obviously there is (?)

What do i do now? do i send them back to support and hope they detect the errors this time and give me a refund?

Thank you so much for your help by the way, I really appreciete your time and effort!

The screen just went grey while running memtest, >400 000 errors detected overall.. i think ill power off the computer now and wait for your reply before i proceed with anything


My System SpecsSystem Spec
.
09 Jun 2014   #12
Thedoctor44

 

Because you've had errors then you'll need to swap your RAM sticks around to determine whether or not it's the RAM sticks or motherboard DIMM slots.

If the output is like this then you have bad RAM so the stick(s) need replacing.

TestSlot 1Slot 2
RAM 1ErrorError
RAM 2GoodGood

If the output is like this then you should replace the motherboard, however you can leave that DIMM slot empty although it's not advised to use a system with a faulty motherboard.

TestSlot 1Slot 2
RAM 1ErrorGood
RAM 2ErrorGood
My System SpecsSystem Spec
10 Jun 2014   #13
Erox

Winsows 7 Ultimate x64
 
 

Test Slot 1 Slot 2
RAM 1 Good Good
RAM 2 Good Good

Those were my overall test results, and this seems weird to me. The only time memtest would detect errors was when I tested both sticks simultaneously (my previous post). When I tested the sticks individually, they would pass the test no matter which slot they were plugged in. (tested slots 1 and 2, my motherboards recommended slots).

May this mean the sticks are not compatible with each other? And if so- may removing one stick solve the problem temporarily?
My System SpecsSystem Spec
.

10 Jun 2014   #14
Thedoctor44

 

I know just the man for this situation, I've seen this before but I've forgot how to determine the fault.
My System SpecsSystem Spec
10 Jun 2014   #15
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

Erox, it could mean the sticks are not compatible or it could mean the memory controller on the CPU is weak, or it could mean the board will not run correctly with 2 slots occupied. I had a board like that once. You state slots 1 and 2, were both slots the same color. Look at your manual again. Most boards have 4 slots, 2 of one color and 2 of another color. Both sticks should go in slots of the same color, and it is normally slots 1 and 3 or slots 2 and 4.
My System SpecsSystem Spec
10 Jun 2014   #16
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

It could also mean the ram is not compatible with the board, but your board has 4 slots, for dual channel mode the ram should be in slots 2 and 4 (or the white slots). Did you check the board's QVL list? I believe you can find out the correct slots on page 16 of your manual.
My System SpecsSystem Spec
10 Jun 2014   #17
Erox

Winsows 7 Ultimate x64
 
 

Hello Essenbe

(I apologise in advance for my amateur explanation, i hope this is not confusing)

My motherboard's RAM slots are set up in this order
DDR3_4 ===========
DDR3_2 ===========
DDR3_3 ===========
DDR3_1 ===========

The slots I've marked as red in this post (slot 1 & 2) are marked white on my motherboard, and is the preferred slots according to the User's Manual:
Quote:
For optimum performance, when enabling Dual Channel mode with two memory modules, we recommend that you install them in the DDR3_1 and DDR3_2 sockets
The slots 3 and 4 are marked blue.
My System SpecsSystem Spec
10 Jun 2014   #18
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

No problem, that looks right, to me.
My System SpecsSystem Spec
10 Jun 2014   #19
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

Erox, if I may make a suggestion, put the ram in the other 2 slots and run the test again. You can do that with memtest without any problem. The worse thing that could happen is you may have to move it back to get the computer to boot after the test, but I don't really think that would happen. But the reason you have 2 colored dim slots is because you have 2 channels for memory and 2 memory controllers on the CPU. You have tried one and have errors on it. Try the other one and see if both channels give you errors. Do you have any spare DDR3 memory around or another computer with DDR3 memory you could try? If not, perhaps you have a friend with spare memory or a computer he would swap memory with you for a day or so, just to see if it makes a difference. Just make sure it is DDR3 memory and you know the correct frequency, timings and voltage for the new ram. Also, make sure you run the memtest86+ from http://www.memtest.org/ You can use either version 5.01 or 4.20, it won't matter.
My System SpecsSystem Spec
Reply

 BSOD, "ntoskrnl.exe"




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD - ntoskrnl.exe "driver power state failure" at shutdown
I'm getting a BSOD pretty much every time I shutdown the PC. Has only just started happening in the last couple of weeks. DRIVER_POWER_STATE_FAILURE caused by driver: ntoskrnl.exe I've attached the SFDiagnostic here - thanks.
BSOD Help and Support
BSOD every few hours: mostly "STOP: 0x00000F4", "c00021a" & "c0000135"
Hi everyone! Yesterday my HP laptop (Windows 7) started getting BSOD with various types of errors (mostly "STOP: 0x00000F4", "STOP: 0x0000007A", "c00021a" and one "missing %hs, c0000135"). Most of the time it restarts without any issues and works fine right after the BSOD and then an hour or two...
BSOD Help and Support
BSOD - "ntkrnlmp.exe" and "ntoskrnl.exe" are the cause
Hello all, a friend was helping me to find out what this BSOD all of a sudden was from but he is out of the country now away on business. We got the point of him looking at the crash files and us using WhoCrashed, and we found that the last handful of crashes I have are all caused by...
BSOD Help and Support
BSOD "Driver power state failure" caused by: ntoskrnl.exe
Hi Folks, I really hope you can help me, I followed the instructions to create the attachement. What I know so far is that this machine has BSOD'd several times...The last 2 times a ultilty called BlueScreenViewer.exe says it's due to "Driver power state failure" caused by: ntoskrnl.exe ...
BSOD Help and Support
BSOD at "random": 0x1a, 0x50, 0x3b ntoskrnl.exe+7cc80
I have been running into BSOD's on my new computer and just can't seem to figure out what the problem is. I say random in that I can't find a trigger, sometimes I can play skyrim for hours without a BSOD, other times just opening explorer results in an issue. Computer is a ASUS g74sx-dh72,...
BSOD Help and Support
No BSOD. Endless startup repair loop. "ntoskrnl.exe corrupted"
I can't get Windows to load properly. Can't get into any safe modes. Just the startup repair screen, over and over. It tells me that there are no system restore points. I have tried copying the ntoskrnl.exe from another Win 7 computer. I have tried the "How to get out of the endless system repair...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 21:23.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App