This is a problem that has been going on for a few weeks now, ever since i built my new PC.
Its been very frustrating, obviously.
I have already ran memtest for over 6 hrs, with no errors.
(I still ordered new RAM anyways - if it isnt the RAM i can always just run 32GB)
I have updated every driver on this PC.
I have reloaded windows 7 and windows 8 (I have valid keys for both) multiple times.
I thought that it had something to do with my SSd, and recently noticed in the BIOS that my PC had my SSD set up as a regular HDD so I changed its type to an SSD and formatted and reinstalled, but I still have the issues.
It seems to happen when I am in skype in voice chat.
I looked it up on some skype forums and tried loading and running an older version of skype.
I have been running it without skype pretty regularly and havent noticed any crashes without it, but I need skype for college, as I have online classes and it is the easiest way to communicate with many of my professors.
Any help would be greatly appreciated.
also, i know everyone needs the .dmp files to help, but as I have really never had these types of issues before im not sure exactly how to put them here.
but here is the info from the most recent:
(they are usually different messages but PAGE_FAULT_IN_NONPAGED_AREA is most common and it is always caused by ntoskrnl.exe but sometimes with different Addresses)
021714-11403-01.dmp 2/17/2014 11:47:06 PM
NT Kernel & System Microsoft® Windows® Operating System
your bugcheck listed is on a very old version of windows 7. You will want to install the windows 7 service pack and updates.
you might also consider going to control panel, find device manager, locate high definition audio devices and turn off all the ones you don't use.
(especially the one in your graphic driver if you don't get your sound via HDMI or Displayport cable.)
windows has two main portions ntoskrnl.exe and win32k.sys, nToskrnl.exe is used by device drivers, if the driver fails it will break in its own code, if windows finds that the driver is doing something wrong it will call a bugcheck using ntoskrnl.exe. In both cases it will be the drivers fault.