multiple bsod by ntoskrnl.exe, 0x0000000a, 0x0000001e, 0x00000050

I had more bsd, but I think the 0x3b and 0xd1 are fixed. Any help would be appreciated. This is so frustrating. If its hardware related, I need help figuring out what. All my parts are new from newegg except for gpu and processor. I don't think its my ram because I swapped out different ram from my old pc and got same errors and that ram works flawless in other pc. Ran sfc scan now and chk disk and no errors. I am uploading the files you requested posted in instructions.

Ram is brand new. I tried 2 other sticks of ram from old computer, in old pc, been running for years not a problem. I took that old ram and put into new pc, still got bsod. I tried one at a time, different slots. Still produced bsod. Will run memtest tonight(because it takes a while to run memtest I hear). I really doubt it is my ram. Any possibily on the motherboard having issues? It is a asrock 970 performance and I should of read reviews first Another guy had a lot of bsod problems with this motherboard.
Also, I was getting the watchdog clock error bad few days ago, over and over, and many random hangs. At first I thought my processor may of been bad, but after reading many forums. One post was to increase voltage on processor through bios. Worked perfect. My motherboard had it on auto (max 1.550), but changed to manual and put at max volt at 1.550 volts for processor and the 0x101 error I had disappeared, no more clock watchdog timeout. My Pc when had clockdog error wouldn't stay on for over 10 mints without bsod, now been 2 days without clock_watchdog_timeout. But I am getting other bsod now. These aren't bad, because I have only been noticed these from when I try to install one game,(middle earth shadow of mordor). I can play assassins creed unity or other games fine on high to ultra for hours no prob. So if you think its ram, You think I may need more volts on ram? Maybe auto isn't just cutting it like it wasn't on processor? Any feedback would be much appreciated.

Arc said:

Follow Golden's post #2 ... it will help you to discriminate between a failing RAM and failing motherboard.

When something is suggested by an experienced member, there must be some rational behind it.

It is not sufficient to install the RAM into a different system as a test.

We cannot ignore it.

Thanks for your input. But what I posted makes no sense to you? I have tried 3 brands of ram now. Old pc all work fine, new pc all get errors, but mainly get those 4 different bsod's when I try to install a specific game. Happens every time at install at around same time of install of that game, one of those bsod's. Otherwise Pc runs perfect. It runs other games and programs perfect. That is why I asked. And I am running memtest tonight to be 100% certain. I was trying to figure out other possibilities in the meantime because a simple answer such as faulty ram just seems standard to me and doesn't make sense when I have posted so much other info about the situation.

So I got this in random now just browsing internet. I am running mem test now. I got bsod 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA caused by driver hal.dll.

Arc said:

I noticed your earlier post, but considered that it was out of that frustration that you mentioned in the original post, and so did not take it very seriously for the first instance.

Network related BSODs were present in you previous dump files too, alongwith a lot of other failing modules (sata, usb, display etc). So much of failing modules is a very strong indication of failing hardware, specially RAM.

RAM failures do take place not only for the RAM itself, but also for a failing DIMM slot, which is a motherboard component. You said your board is new too. So we need to try to test it as far as we can. And that is why memtest86+ is required, it can do the job. Why and how ... we will tell you at the proper time if situation demands.

Run the test with all your RAM modules connected.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing and report us. A single error is enough to determine that something is going bad there.

Thanks for the info. I'm sorry if I came off rude. These bsod's have gotten me so frustrated. I'm running memtest now. Almost on 2nd pass and no errors so far. But few more hours to go before it finishes. I really think its motherboard. Because even for the processor auto settings didnt work as I mentionted in second post, and I had to patch so many other bsod errors with windows update, etc. Finally these bsod's wouldnt go away. I only have one new ram module in my new build which is (1x8gb). I have tested with other ram like mentioned which were 1x4gb and even 2x4gb incase it needed 2 and even in different slots. I have tested all possible scenarios with ram and I still get bsod. Is there any way my gpu or cpu can be causing this? I think its either those or motherboard really, especially if you say a lot of my modules were failing.They are the only used items I bought, and watchdog error was processor related, but that one seems to be fixed. Anyways So like you guys have mentioned, I have been running memtest now for almost 2 hours. I'm guessing will be done by midnight eastern time. Is there a file I will need to post for memtest results or does that get pulled up auto if i relaod dump files? Regardless I will repost all the current dump files after memtest has finished. Thanks

Been running for well over 7 hours now. Almost on its 5th pass, no errors. Taking a lot longer that I had estimated. Probably wont be ready for another 6 to 7 hours. Is that much more necessary? Its a brand new stick. I have read 3 to 5 passes suffice on new stick on other forums? Then again I have also read, there have been machines to take 72 hours to find errors. This mem test has ran longer than my computer has in windows without having some form of bsod. Also, after this is done, what tests do I perform next? I have ran fury and prime before, but not for long at all like this. Like 30 mins each, My pc did have bsod once when I ran fury, but I didnt think much of it because I googled error and there was a fix for that error, I forget but something to do with expanding atsys_ or? (forget exact file name) file and replacing it. so I ran afury again twice and it didnt' bsod during test again. This was about 1.5 days ago.