Jump to content
|Topic||Stats||Last action by|
|IOS 8 now live!||
|Welfare recipients can use debit cards for marijuana||
|The Big Wrestling Thread!||
|Apple iOS 8 is now available - here is how to download it||
|Merits of using prefix vs postfix increment operator||
Posted 17 May 2012 - 20:40
Posted 21 May 2012 - 08:05
A couple of questions:
1. Are you overclocking?
2. Are you manually setting dram timings / voltages?
3. When did this start happening? Recently? As soon as you put the machine together? After changing a component?
4. What BIOS settings are you using?
There are a few things you can do:
1. Run Prime95 to stress test your cpu independently of the GPU.
2. Run Memtest86 all the way though.
3. Run 3DMark test.
4. Load up a different OS, for example Ubuntu, and try running a game there. Does it BSOD on all games, or just high end ones?
5. You seem to have a lot of memory there. Try just 4GB.
6. If you changed hardware recently, Ι'd suggest resetting the bios to defaults.
7. Try updating your BIOS.
Posted 21 May 2012 - 08:17
Posted 21 May 2012 - 08:24
This only ever happened to me for a couple of reasons, the card I had when I inspected it showed that the fan was clogged full of dust, the PC was dusty too, cleaning everything out and reseating the fan fixed the problem.
Another (more common than you would believe) is that the PC unit doesn't have enough "breathing space" so ensure there is at least a minimum of 2 to 3 inches space on each side and at the back.of the unit, if you've enclosed it in a desk that could be another reason as well (overheating).
Posted 21 May 2012 - 08:27
As I mentioned, it is always ntoskrnl.exe causing the problem, and I don't really know how to remedy that.
Posted 21 May 2012 - 08:31
Hi there What version of Windows is it? Maybe a dumb question but are you up to date with Windows Update? Another thing you might want to try is to check your motherboard manufacturer site and see if there is a BIOS update (look why there is an update if there is).
Can't really think of anything else other than trying to reinstall Windows? If you do that try to see if you can image your current C:\ drive so you can restore it if that doesn't help.
Posted 21 May 2012 - 08:35
Posted 21 May 2012 - 09:06
ntoskrnl.exe exits, but isn't the cause of the problem (it's a protected system file that can't be modified) so your ntoskrnl.exe is the same as mine It's probably still driver related. You might also want to do a search for the graphics card + driver version you are using on Google and see if others are having the same problem.
Sometimes rolling back to an earlier driver version fixes weird issues too.
Posted 21 May 2012 - 09:08
Ok. I was thinking ntoskrnl.exe WAS the problem, but it makes more sense that it's failing due to something else. I did a little research and it seems there is a fairly large community who believes catalyst 11.9 is the best version, especially when it comes to gaming.
I'm gonna give the older drivers a shot. I'll report back....
Posted 21 May 2012 - 11:09
Posted 21 May 2012 - 11:21
Posted 21 May 2012 - 11:28
Alright, so I used the Catalyst 11.9 uninstall feature to remove 12.4, then installed. I didn't use driver sweeper because I figured the uninstall feature would have removed them.....
I then played Diablo III for almost 2 hours. Gameplay was choppy to say the least. My framerate was hovering right at about 100fps the whole time, but it was extremely choppy anyway. This eventually ended with a blue screen and of course a mixture of anger/sadness from me =P.
Sooooo. I just used driver sweeper to remove all traces of AMD/ATI drivers, and reinstalled Catalyst 11.9. Stay tuned...
Could you post the error dump please? This way you could get real help other than speculations.
Posted 21 May 2012 - 13:58
I gather from that statement that your copy of windows is not legit? You should open an elevated command prompt and run:
My friend has this same "copy" of windows, and his gets the same errors. Do I have a corrupt version, or a corrupt ntoskrnl.exe? Is there any way to replace just this file? If I boot my windows disc and go to repair will it find and replace this corrupt file? Is this even possible if the file on the disc is corrupt itself?
sfc/scannowthis process will take a long time, but it will identify and (hopefully) correct any system files that are corrupted.
Posted 25 May 2012 - 06:28
Posted 25 May 2012 - 06:33