Numerous BSoD Caused by ntoskrnl.exe

Molten-ice

Reputable
Apr 3, 2014
6
0
4,510
I have recently built my gaming pc and I have been experiencing the Bsod very frequently usually every few minutes. i have windows 8 pro and already did a clean install of everything. i have been getting several error codes such as:
(in order of most frequent)

ATTEMPTED_WRITE_ON_READONLY_MEMORY
DRIVER_IRQL_NOT_LESS_OR_EQUAL
PAGE_FAULT_IN_NONPAGED_AREA
KMODE_EXCEPTION_NOT_HANDLED
SYSTEM_SERVICE_EXCEPTION
BAD_POOL_HEADER
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

These are my specs:

Intel BX80646I54670K Core i5-4670K 3.4GHz 6MB LGA1150 Haswell Boxed CPU

EVGA GeForce GTX 780 Superclocked 3GB

ASRock Z87 Extreme4 Motherboard

SanDisk Extreme II Solid State Drive 120GB

Silverstone Strider Plus 850W ST85F-P

G.Skill Sniper 8G Kit(4Gx2) DDR3 1866 F3-14900CL9D-8GBSR

Seagate 3.5" Barracuda 2TB ST2000DM001 SATA3 7200rpm 64MB Cache Hard Disk

could someone please help me. This problem is really bothering me and i cant even use my pc for 5 minutes without it crashing. also how do i upload my mimidumps?
 
Looks like a Memory prob. Try reseating your sticks to make sure they're firmly seated, and if the problem persists, try removing one stick at a time to see if the system will run without fault. Also try in different slots in case it's a slot at fault.
 

Molten-ice

Reputable
Apr 3, 2014
6
0
4,510


i already tried that and there was not difference i also ran memtest for 4 hours with no errors.
how do i upload my dump files?
if u want to have a look at them
 

Not hot on Minidump analysis, tend to go for 'Whocrashed'
http://www.resplendence.com/downloads
About half way down the page...

 

Molten-ice

Reputable
Apr 3, 2014
6
0
4,510


how would you like me to show u the dump files?
 

Molten-ice

Reputable
Apr 3, 2014
6
0
4,510



Conclusion
--------------------------------------------------------------------------------

39 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

aswell as these files probably caused the crashes:

tcpip.sys = 7 times
ntoskrnl.exe = 20 times
netio.sys = 1 time
idsvia64.sys = 1 time
dxgmms1.sys = 2 times
cmudaxp.sys = 1 time
afd.sys = 7 times


Im not sure what to do from here
 

Molten-ice

Reputable
Apr 3, 2014
6
0
4,510



So i will reseat my gpu and do a clean reinstall of the drivers and ill keep u posted
for any improvements or if nothing changes.
Im not sure if my mobo has an onboard GPU but ill check and try it out.
If nothing changes would that mean that my GPU is faulty? and should i try put my GPU in another PSI-E slot?
Thanks for your help.
 

If no onboard, ideally try another GPU if you can borrow one from a pal, trying another slot won't do any harm, either!...

 
I can say with almost 100% certainty the issue is bad RAM. The fact you are BSOD'ing all over the kernel [such as within the TCP/IP driver, which is very unlikely to occur due to any other reason] is farther evidence of this.

ATTEMPTED_WRITE_ON_READONLY_MEMORY
DRIVER_IRQL_NOT_LESS_OR_EQUAL
PAGE_FAULT_IN_NONPAGED_AREA
KMODE_EXCEPTION_NOT_HANDLED
SYSTEM_SERVICE_EXCEPTION
BAD_POOL_HEADER
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Every one of these BSOD's gets generated if you have bad memory. That being said, many of them can be caused by faulty HW. The ATTEMPTED_WRITE_ON_READONLY_MEMORY BSOD is one I'd associate more with HW then RAM, for instance. But let's eliminate the most likely cause first.

Download/Run memtest86+ for at least three passes, and see if it picks up any errors. [This should really be the FIRST thing done for any BSOD except maybe VIDEO_TDR_ERROR and VIDEO_TDR_TIMEOUT, which point directly to the GPU]

ntoskrnl.exe = 20 times
Points to Graphics Card, again try re-seating, then uninstall/re-install GPU driver.
If your Mobo has an onboard GPU try that for a while...

Not really. ntoskrnl.exe is the main Windows executable. In most of the cases, when there's an error, Windows catches it, and tries to fix the problem, then crashes a second time [double-fault], causing the BSOD. Most crashes occur within the kernel for the reason that's where the error handlers are located. If it were a GPU problem, I'd expect to see crashes within one of the DX drivers, HAL.dll, and see at least one of the VIDEO_TDR BSOD's due to the driver locking up. Its possible the GPU could be faulty and generating these BSOD's if, say, an address on the GDDR RAM went bad, but its unlikely based on what I'm seeing.
 
@gamerk Agreed with all, but the OP says he checked out his RAM (perhaps not thoroughly enough!) If it's not the Video RAM the only other thing I can think of is the Memory Controller which of course is in the CPU and would be quite unusual. Bad DIMM slots are another possibility, but I've only met that once and it caused a complete failure.
 
One thing that can happen with RAM is that you get a few bits that need just a *little* bit more voltage then normal to flip bits. Most of the time, its OK, and will pass most any memory test. Load a full OS, and the second the PSU voltage fluctuates even a little (even if well within spec), BSOD. If each stick passed individually, it may not be the RAM itself though; its possible the problem is farther upstream the motherboard (Northbridge, etc). My old nforce 790i Ultra needed a 0.2V boost on the Northbridge for stability, for instance. Then of course, are the RAM timings, which also could be the problem.

Assuming each stick was tested individually (since I NEVER assume dual simultaneous failures)
1: Check the RAM timings against spec. You can try increasing the timings slightly to see if that helps.
2: Check system voltages against spec. You can try a slight bump to the NB voltage and see if that helps. [It does on lower end mobos which sometimes have trouble with large capacity RAM, though I doubt a X87 would have that problem...]
3: Update (or downgrade, if you have the latest official release) GPU drivers. While a lot of the BSOD's are RAM related, three [ATTEMPTED_WRITE_ON_READONLY_MEMORY, DRIVER_IRQL_NOT_LESS_OR_EQUAL, KMODE_EXCEPTION_NOT_HANDLED] can be thrown due to driver issues or issues with the underlying hardware.
4: Swap GPUs. I doubt this is it, but I can't rule it out at this stage.
5: Disable/Uninstall your AV (Norton/Semantic? idsvia64 is their core driver, which crashed once for you)

The drivers that are crashing:
tcpip.sys: The TCI/IP driver.
ntoskrnl.exe: The Windows Kernel [expected]
netio.sys: The Windows Networking I/O driver
idsvia64.sys: The Norton/Semantic Core driver
dxgmms1.sys: DirectX MMS driver
cmudaxp.sys: C-Media WDM Driver
afd.sys: Hardware Communication related driver

I'm actually leaning to your AV in all honesty; its the only one aside from Memory that could explain all the crashes within the TCP/IP driver and Networking driver, and would explain the crashes within the Norton/Semantic driver.
 


Sounds like a plan, who needs Norton anyway? I've only Defender/Security Essentials on all my machines, and never see a virus from one month to the next...
 

Molten-ice

Reputable
Apr 3, 2014
6
0
4,510


I have actually uninstalled Nortons and i haven't seen that error since.
I also recently did a clean reinstall of windows and all my drivers.I will retest my ram with for a few passes individually and i will reply back with my results.
Thanks

I ran memtest for 3 passes on each stick and they both were fine. They passed everytime with no errors. I am still experiencing crashing. i was thinking if i should retest each stick of ram in different slots. Would this be ideal. I moved the ram sticks into different slots and the crashing frequency is not as high but i am still getting them. They are all caused by ntoskrnl.exe.
Should i just send my ram back and get a new set even though i am not 100% sure that they are the problem.
please reply shortly.

I have replaced my ram and i am still getting the crashes and they are just as frequent. Would this now leave my motherboard as faulty or would it be my HDD/SSD or my GPU?

please reply this is very urgent!