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

[skysurferdude12]

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.

 

[Golden]

The last 4 .dmp files point to a possible RAM problem. The only way to check that is to run a minimum of 8 consecutive passes of Memtest86+ as described here:

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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

 

[skysurferdude12]

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]

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.

 

[skysurferdude12]

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.

 

[Arc]

But what I posted makes no sense to you?

Statement does not many any sense. Troubleshooting is fact oriented only.

The little sense that it makes .... suggests memtest86+ to run. There is some things to discriminate between. And it is only memtest86+ that can do it.

 

[skysurferdude12]

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]

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.

 

[skysurferdude12]

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

 

[skysurferdude12]

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.

 

[Arc]

In less than 7 -8 passes, memtest86+ results are not reliable. And it will take a time with 8 GB RAM.

Here the primary suspect is the memory. Not the RAM only, but also the DIMM slots too. That is why the test is necessary.

If the test is not properly done, there will always remain a chance that the troubleshooting did not cover the primary aspects of the issue.

The more passes it runs, th better results it gives. But 8 passes is a fair amount of test.

If it turns out to be no error at all, we will pay attention to teh other possible aspects of the issue, which may take more time.

 

[skysurferdude12]

Ran memtest. No errors. I am re uploading all dump files which has a lot more bsod's, same ones mostly. I can't keep running these long tests on brand new equipment. I"d like to be certain it is in fact faulty hardware. I need help trying a shotgun trial and error approach. I can return all my parts including the 2 used parts I bought which was cpu and gpu. I don't have much time left on return. I have swapped out and tried different parts with all except motherboard and cpu. I am getting a new motherboard tomorrow so I will swap out and see if that fixes. I don't think its gpu because I had a older gpu I put and I still got bsod errors. After that if I still get bsod's last thing would be to swap out cpu, which I think I am going to do tomorrow night if I have errors again on new motherboard. Keep in mind I have done a fresh install everytime I swapped parts. Always updated all drivers and did all windows updates everytime. I will do again with new mb. If that doesn't take care, once more with new processor. If that doesnt' work, I will give up and just return all and take some loss on shipping.

 

[Arc]

Two of today's BSODs are stop 0x50 and one is 0x1E.

The 0x50 ones are not saying anything about the BSOD other than a hardware error, but the 0x1E one causes symbol error, which indicates that it may be a third party hardware controlling driver that is causing that issue.

Do the following things one by one ....

► Uninstall the following things:

• Start Menu\Programs\ASRock Utility
• Start Menu\Programs\ASRock Utility\InstantBoot
• Start Menu\Programs\Fatal1ty Utility
• Start Menu\Programs\Fatal1ty Utility\F-Stream Tuning
• Start Menu\Programs\MagicDisc
• Start Menu\Programs\MagicISO

► Stop ox50, as described in Carrona.Org ....

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

And you have McAfee installed. Which I did not notice earlier. McAfee alone can cause all those issues. Uninstall McAfee Using McAfee Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

► Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Now run the computer normally. If it BSODs again in this state, we will stress the drivers.

 

[skysurferdude12]

Thank you. I am uninstalling all right now. I had a 0x0000000a IRQL_NOT_LESS_OR_EQUAL happen after posting bsod dump files( that happened before I left for work and while browsing internet). That was ten this morning, none after that and pc was on for 6 hours in idle. Anyways, I know how to make it bsod though, try to install that one game. It happens always during that but it happens random too and that the part I don't like. Will post update soon/. Thank you so much for all your help and taking the time to respond. I really appreciate it.

 

[skysurferdude12]

Uninstalled all the recommended things. As soon as I went to install that game, I got bsod with error 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA. It has to be hardware like you said, but I don't think it's ram. Maybe it can be, I have read on other forums that some mem tests have taken over 100 hours. But it just gets me cause I just tested ram, have tried other ram that has been running in pc for years and even another brand new stick of ram. Couldn't it be slots on motherboard if it is memory related? Any way this could be my processor?

 

[skysurferdude12]

I also asked if it's processor related because I don't know if you read all my posts. I used to get a clock watchdog timeout error 0x124 really bad at first. Pc wouldn't stay on 5 to ten mins with out bsod or random hang. But after changing voltage settings to manual from auto in mb, that problem disappeared.

 

[skysurferdude12]

It was my motherboard. I got a new one. Everything works flawless. Did a fresh install. Not one single bsod. All updates ran fine and fast. The game I couldn't install and would bsod on, installed and runs fine. I had a bad feeling about that board when default settings wouldn't work on processor. Anyways thanks for all the help. If I have any problems in the future, I"ll come back here. Thanks.

 

[Arc]

All is well that ends well.