Author Topic: multiple random BSOD ntoskrnl.exe common  (Read 1623 times)

0 Members and 1 Guest are viewing this topic.

Offline Redstreblo

  • Darth Lobster
  • 26
  • Current Project: Vasudan Imperium (\/) (;,;) (\/)
multiple random BSOD ntoskrnl.exe common
I have had many random blue screens for a while now and nothing seems to be fixing the issue, I have tried 2 different types of ram, different hard drives and configurations. I have removed one of my graphics cards at a time (SLI) to see if it was a problem with that.

I went into BlueScreenView and put into the options for the lower pane "only drivers found in stack" and there are different files and different messages about why the bsod happend. however in each of the .dmp files in the lower pane with the exception of one blue screen it had "ntoskrnl.exe."

What is "ntoskrnl.exe", could it be the cause of my blue screens and if so how do I fix it?

There are a lot of .dmp files so I am giving the link to a folder on mediafire that contains all of the .dmp files in my C:\Windows\Minidump folder here.

EDIT: Repaired broken link.
« Last Edit: August 26, 2012, 12:34:41 am by Redstreblo »
I, Aries one, have proved myself superior to the legendary Terran pilot Alpha one! Let the Vasudan people take pride in this accomplishment, and take the Parliamentary Vasudan Empire to victory over the inferior Galactic Terran Alliance! Long live the Emperor!

 

Offline Nuke

  • Ka-Boom!
  • 212
  • Mutants Worship Me
Re: multiple random BSOD ntoskrnl.exe common
wiggle your ram
I can no longer sit back and allow communist infiltration, communist indoctrination, communist subversion, and the international communist conspiracy to sap and impurify all of our precious bodily fluids.

Nuke's Scripting SVN

 

Offline The E

  • He's Ebeneezer Goode
  • 213
  • Nothing personal, just tech support.
    • Steam
    • Twitter
Re: multiple random BSOD ntoskrnl.exe common
ntoskrnl.exe is the main kernel executable, in other words, Windows' core. I would recommend doing the following:
1. Open a commandline with admin priviledges
2. Run the following command: sfc /scannow
This will check all Windows system files for integrity, and will attempt to repair things that are faulty. It may take a while.
If I'm just aching this can't go on
I came from chasing dreams to feel alone
There must be changes, miss to feel strong
I really need lifе to touch me
--Evergrey, Where August Mourns

 

Offline Redstreblo

  • Darth Lobster
  • 26
  • Current Project: Vasudan Imperium (\/) (;,;) (\/)
Re: multiple random BSOD ntoskrnl.exe common
Well, I ran sfc/scannow and it says "Windows Resource Protection did not find any integrity violations."

It seems to happen randomly, sometimes in a game, sometimes on the desktop. Sometimes it has a BSOD other times it just straight up freezes.

@Nuke, I have on multiple occasions removed and replaced the RAM modules, I have tried pressing them in further to make sure they are properly installed and tried using a different brand/model modules. I am running 12GB RAM (3X4GB) 1.5v (Core i7 960 likes this voltage i hear, not 1.65v). I think it unlikely that the RAM is bad because it also had issues with the other RAM unless I have a bad module in both the Corsair and the Patriot options.

My temps are fine, no spikes or apparent correlation with the BSOD screens. I get BSOD when on the desktop processor at idle at around 45-50 degrees C (remember this is an i7, they tend to run on the hotter side) and when under load at 75-80 degrees C (again this is below the i7 100 degree max). My processor (Core i7 960) is overclocked to 4Ghz from stock 3.3Ghz (Yes I backed off my OC to stock speeds BSOD still happens).

My graphics cards also run within specified temperature ranges (GTX 560 Ti SLI). Usually my GPU 1 Temps are 10-20 degrees C higher than my GPU2 because of the lack of space between the cards (Cannot put GPU 2 onto a lower PCI slot due to the power supply blocking it so I have to run my SLI setup with them right next to each other). GPU1 tends to run at between 70-80 degrees C under load and 55-60 degrees C at idle, and GPU 2 runs at between 60-70 degrees C under load and 45-50 degrees C at idle (dangerous temps for the GTX 560 Ti is 90+ (max 100 degrees C)). My graphics cards are overclocked to 1Ghz Core Clock from stock 850MHz (technically 822MHz, but my model apparently came from the factory with a modest OC) (again I backed of the OC to stock and BSOD still happens).

Because I backed off my overclock to stock and the problem still exists I put my settings back because I don't think they are related.
I, Aries one, have proved myself superior to the legendary Terran pilot Alpha one! Let the Vasudan people take pride in this accomplishment, and take the Parliamentary Vasudan Empire to victory over the inferior Galactic Terran Alliance! Long live the Emperor!

 

Offline Nuke

  • Ka-Boom!
  • 212
  • Mutants Worship Me
Re: multiple random BSOD ntoskrnl.exe common
memtest86. even with new ram things might me screwey. if it tests failures its usually just a matter of timing issues. timing is so critical these days where if you had a bios reset, it would be enough to seriously destabilize your memory.
I can no longer sit back and allow communist infiltration, communist indoctrination, communist subversion, and the international communist conspiracy to sap and impurify all of our precious bodily fluids.

Nuke's Scripting SVN

 

Offline Water

  • 210
Re: multiple random BSOD ntoskrnl.exe common
Agree with memtest86+. Put it on usb and boot from it.

If you test the ram and it passes, also check it again from a cold boot (the next morning)

I've got some ram that works perfectly after a reboot. But will fail memtest86+ 50% of the time the next morning. If i then do a soft reboot by exititing memtest86+ using esc it will still be faulty. Have to use the front power button to reboot. Thats with four sticks. With just two sticks it works every time.



 

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: multiple random BSOD ntoskrnl.exe common
If your mem passes, do you have a known good PSU around that you can try?  A flaky PSU can bring on intermittent problems that are hard to see.  You can test it while the computer is running (under load), but if it's intermittent, it might not be visible even then.

 

Offline Redstreblo

  • Darth Lobster
  • 26
  • Current Project: Vasudan Imperium (\/) (;,;) (\/)
Re: multiple random BSOD ntoskrnl.exe common
Well ran my first run of memtest86 and no errors detected. I'll re-run after the computer has sat off overnight.

@jr2 PSU has come up quite a bit in my conversations about this with other people, I don't have a known good one and I don't know how to test mine to see if it's any good. I'm running a Corsair AX1200 PSU bought new. Are there programs out there that I can use to test it or do I need to pull out my digital multimeter and test it manually?
I, Aries one, have proved myself superior to the legendary Terran pilot Alpha one! Let the Vasudan people take pride in this accomplishment, and take the Parliamentary Vasudan Empire to victory over the inferior Galactic Terran Alliance! Long live the Emperor!

  

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: multiple random BSOD ntoskrnl.exe common
multimeter whilst running under load