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: Random BSODs on a brand-new PC (ntoskrnl.exe)

14 Mar 2013   #71

Windows 7 Ultimate x64
 
 

Lent 1 of my RAM to another friend, to see if he gets any BSOD on his machine.
1 day past, no BSOD at all.
Neither in mine, with the current configuration above.

Should we enable D. Verifier?
Would it make the system crash due to RAM and not any driver issue?

My System SpecsSystem Spec
.

15 Mar 2013   #72

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

Was this one of the old RAM that supposedly is causing the BSODs? Where did he put it in his system? Be aware that depending what slot he placed it in, the system may not even be using it at all (as in the system never reaches a point where it needs to use it). Kernel activity (Windows n drivers) sits at the very top of the memory range (last stick of RAM), and userland (applications and services) start at around the bottom and grow upwards. Keep that in mind when setting up the RAM for testing. If you want to make quite sure the RAM is bad, make sure it's placed in the last numbered slot on the mobo since there it'll hold Windows kernel and drivers.

Anyways, remember that this may not be an issue with the RAM itself but your configuration of it. The mix of RAM and their amounts could've been enough to bug your mobo out. When you got the new RAM kit, was it same make/model as the old?

Btw, what happened with the mobo? The warranty on it is looking pretty tight right now, have you considered RMAing it?

As for Driver Verifier, not really. It will make the system panic more in the event of an issue, as in more prone to BSOD, and will take up a modicum of more RAM and CPU activity to do all the extra checks, but that doesn't necessarily mean it'll catch bad RAM. Driver Verifier is just as its name says, it's designed to verify drivers. It has absolutely nothing to do with testing any form of hardware. If you want to do that, it'll be through Memtest, but we've already proven the issues evading that program. Again, I really do think we're dealing with a motherboard incompatibility problem or just a bad mobo altogether.
My System SpecsSystem Spec
15 Mar 2013   #73

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by Vir Gnarus View Post
Was this one of the old RAM that supposedly is causing the BSODs?
The RAM I lent was from the NEW kit I got Tuesday. I followed my intuition at this.
Lent one stick, stayed with the other.
If his machine had BSOD on tests, we would have found the problem.
As mine would crash in any way.

Quote   Quote: Originally Posted by Vir Gnarus View Post
Where did he put it in his system? Be aware that depending what slot he placed it in, the system may not even be using it at all (as in the system never reaches a point where it needs to use it). Kernel activity (Windows n drivers) sits at the very top of the memory range (last stick of RAM), and userland (applications and services) start at around the bottom and grow upwards. Keep that in mind when setting up the RAM for testing. If you want to make quite sure the RAM is bad, make sure it's placed in the last numbered slot on the mobo since there it'll hold Windows kernel and drivers.
This stick is the only one he's using on his machine to help me.
In this case, would it matter the slot?
I don't really know which slot he's using.

Quote   Quote: Originally Posted by Vir Gnarus View Post
When you got the new RAM kit, was it same make/model as the old?
Yes, it's exactly the same RAM model as before.

Quote   Quote: Originally Posted by Vir Gnarus View Post
The mix of RAM and their amounts could've been enough to bug your mobo out.
Quote   Quote: Originally Posted by Vir Gnarus View Post
Btw, what happened with the mobo? The warranty on it is looking pretty tight right now, have you considered RMAing it?
I'm still not considering MoBo.
But im really scared about the warranty, though.
I'll just test RAMs as far as I can.
Something is telling me the problem is the stick I lent. Intuition.
My System SpecsSystem Spec
.


15 Mar 2013   #74

Windows 7 Ultimate x64
 
 

UPDATE:

By the time I was writing the reply, my friend called me.
HE HAVE HAD BSOD TWICE, CONSECUTIVELY!
So the RAM stick I lent him is with problem.

I'll just have to check my machine now.
As said before, I am using ATM:
1 RAM from the NEW kit + 1 RAM another friend lent me (spent 15 days with this stick without crashes).
No crashes yet.

So, I guess we can finally forget about the motherboard..?
Just have to find out if BOTH RAM sticks are with problems, or just the one I lent him. (:
My System SpecsSystem Spec
18 Mar 2013   #75

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

Here's hoping the BSODs weren't coincidental and caused by something else. Nevertheless, we'll approach that RAM as the suspect for now.
My System SpecsSystem Spec
18 Mar 2013   #76

Windows 7 Ultimate x64
 
 

Would be too much coincidence if not true.
His computer has been built over a year and never had crashes.
When working with the RAM I lent, gone BSOD.
Took that RAM out, no BSODs again.

This afternoon I went to the store to RMA them again.
The vendor was a really nice guy, and gave me another kit once again, without tests this time.

Running system with new RAM kit, lets hope for the best
My System SpecsSystem Spec
08 Apr 2013   #77

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

Hi there. It's been a while. Any update on that RAM and how it's working?
My System SpecsSystem Spec
11 Apr 2013   #78

Windows 7 Ultimate x64
 
 

It has crashed BSOD again..
XMP Profile 1 at 2400mhz
Took a week to do so.

I changed to XMP Profile 2 at 2132mhz: BSOD at windows start up.. twice
Went for JEDEC Profile at 1333mhz: no problems since.. computer stabilized. 2 weeks.

Then I gave up..
Since there are not any more problems with JEDEC Profile, I'm letting as it is..
My System SpecsSystem Spec
12 Apr 2013   #79

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

Looks like timing may have been the problem after-all. Glad to hear it's stable. You can mark this thread as solved at your discretion.
My System SpecsSystem Spec
Reply

 Random BSODs on a brand-new PC (ntoskrnl.exe)





Thread Tools



Similar help and support threads for2: Random BSODs on a brand-new PC (ntoskrnl.exe)
Thread Forum
Random different BSODs, ntoskrnl.exe BSOD Help and Support
Random BSODs in brand new build BSOD Help and Support
Solved Random BSODs. Seems to be ntoskrnl.exe+7e569. BSOD Help and Support
Solved Random BSODs about once a day or so with ntoskrnl.exe and tcpip.sys. BSOD Help and Support
Random BSODs ntoskrnl.exe+26ee0 & ntoskrnl.exe+5063dc BSOD Help and Support
Random BSODs by ntoskrnl.exe BSOD Help and Support
Random BSODs ntoskrnl.exe 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 02:31 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33