Had to look at some BIOS screenshots. What is your SA voltage shown at ?
Show Image
(http://i1.ytimg.com/vi/-4OePNpOGs8/maxresdefault.jpg)
You could bump it by 0.005-0.010V from what you have currently and see if it helps. If it's set on auto, you could set SA offset to +0.005 or +0.010.
http://tinypic.com/r/20zo2a0/8
Should I change anything?
You really need to run your diagnostics at the lowest level possible. I would not run them from Windows. Especially since Win is already unstable. You may not get accurate results.
http://www.ultimatebootcd.com/
I don't think "need" is the right word there. His system is not crashing at boot. It's more of a fine-tuning issue, it seems, based on the symptoms. That could be analyzed from within windows.
Well your system can actually still boot when you have bad components. It'll just be unstable and crash often.
You hear this alot when somebody has a cheap PSU which is in the middle of dying.
So he does "need" to do it from the lowest level possible.
Going back to what's been said:
What he actually needs to do is conduct a proper basic trouble shooting and isolate his variables.
At this point, the amount information provided is too lackluster for definitive results
More
Usually when everything else checks out - it's a bad stick of ram or it's a failing PSU.
That being said, since we don't know if everything checks out, it could be anything from the above, it could be an attached printer with a bad driver, some other peripheral like a usb dongle or it could even be something like his room's power wiring is giving out due to the load from his PC and whatever else is plugged in the outlet.
Preferably, if the issue persists, he should post 2-3 dmp files because some geek here can probably pinpoint the probably cause AFTER he's done the basic check.
It's really as simple as that and it needs to be done.
I don't mean to sound like an ******* to the OP but I get this feeling you're looking for a quick fix but you're not applying enough of your own elbow grease.
I get this impression because of your replies or rather lack off substance in them.
We haven't heard anything about you going inside and checking on your components. Nothing about basic checks either.
You still also haven't provided us with dump files and error codes.
I mean if you had also google'd Ntsokrnl.exe you'd know that it's just a core windows component crashing because of either a bad driver, bad pin sometimes or a component failing on you.
Which pretty tells you it's kind of a generic error and you need to post more information.
You really need to run your diagnostics at the lowest level possible. I would not run them from Windows. Especially since Win is already unstable. You may not get accurate results.
http://www.ultimatebootcd.com/
I don't think "need" is the right word there. His system is not crashing at boot. It's more of a fine-tuning issue, it seems, based on the symptoms. That could be analyzed from within windows.
Well your system can actually still boot when you have bad components. It'll just be unstable and crash often.
You hear this alot when somebody has a cheap PSU which is in the middle of dying.
So he does "need" to do it from the lowest level possible.
Going back to what's been said:
What he actually needs to do is conduct a proper basic trouble shooting and isolate his variables.
At this point, the amount information provided is too lackluster for definitive results
More
Usually when everything else checks out - it's a bad stick of ram or it's a failing PSU.
That being said, since we don't know if everything checks out, it could be anything from the above, it could be an attached printer with a bad driver, some other peripheral like a usb dongle or it could even be something like his room's power wiring is giving out due to the load from his PC and whatever else is plugged in the outlet.
Preferably, if the issue persists, he should post 2-3 dmp files because some geek here can probably pinpoint the probably cause AFTER he's done the basic check.
It's really as simple as that and it needs to be done.
I don't mean to sound like an ******* to the OP but I get this feeling you're looking for a quick fix but you're not applying enough of your own elbow grease.
I get this impression because of your replies or rather lack off substance in them.
We haven't heard anything about you going inside and checking on your components. Nothing about basic checks either.
You still also haven't provided us with dump files and error codes.
I mean if you had also google'd Ntsokrnl.exe you'd know that it's just a core windows component crashing because of either a bad driver, bad pin sometimes or a component failing on you.
Which pretty tells you it's kind of a generic error and you need to post more information.
?
As I already have stated: "I'm not very knowledgable about computers, so just keep that in mind." I'm not going to open up my computer when I don't even know what's what. I'm currently checking my HDD's for errors (which takes hours). The other tests I don't know how to do myself, so I will get help from an irl friend later today.
Edit: And I'm by no means looking for an 'quick fix'. I came here to see if someone could help me with the little information I had, and I got some nice replies which was very helpful.