What's causing this BSOD (0x50, 0x1a, 0x7f)?

[Swaggy P]

I've experiencing the Blue Screen of Death errors recently
I followed the posting steps and attached the .zip files on this thread
All help will be appreciated

 

[HonorGamer]

Hello, Welcome to SF!

Probably caused by :memory_corruption ( nt!MiAgeWorkingSet+1d1 ) 
BugCheck [COLOR="Red"]50[/COLOR], {fffff6837f7e0df8, 0, fffff80002c7e55b, 5} 
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)

BugCheck 50 can actually be caused by quite a lot of things. Memory, device drivers, corrupt installs, and anti-virus.

After looking at the MSINFO32 file, I found this line:

Security Processor Loader Driver	ROOT\LEGACY_SPLDR\0000	This device is not present, is not working properly, or does not have all its drivers installed.

This basically means that the anti-virus you currently have is corrupt. From the looks of it, you are just using Windows Defender:

[COLOR="red"]msmpeng.exe[/COLOR]	c:\program files\microsoft security client\msmpeng.exe

I suggest disabling it(you can follow this tutorial: http://www.sevenforums.com/tutorials/6397-windows-defender-turn-off.html), as it also has some application errors, and just installing Download Microsoft Security Essentials from Official Microsoft Download Center

This is weird to me because I have never seen a problem with Windows Defender before, but that does not mean it isn't possible.

And to be on the safe side, lets run a http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Tip

Run Memtest86 for a minimum of 8 passes

Post back results.
-Justin

 

[Swaggy P]

That's weird...I tried to turn off Windows Defender, but it was already off, and I got MSE installed already.
*about to run a RAM memtest*

EDIT: I might run it overnight while I'm sleeping since it takes a long time to finish

I really hope my RAM is fine. I don't feel like testing my motherboards

 

[HonorGamer]

If you already have it installed, then I suggest reinstalling it with a fresh downloaded copy.

 

[Swaggy P]

I double checked the Windows Defender issue and found out that the Administrator setting is still checked (it was "off" because I have MSE installed)...silly me

I re-installed MSE and it is currently updating. I hope this permanently solves the issue

NOTE: I have no BSODs so far today even before doing something with Windows Defender and MS Essentials

Thanks for your help!!!

 

[Swaggy P]

UPDATE: Just got a BSOD error...

 

[HonorGamer]

Once you did all of the above, did you restart your computer?

Have you ran a Memtest yet?

 

[Swaggy P]

I haven't ran a memtest (planning on doing it tonight)
I don't remember restarting after re-installing MSE.
Is there anything that's different about the latest BSOD error, or is it still about my anti-virus programs?

 

[HonorGamer]

It's showing all the above possible errors, I am going to look at them in detail here soon.

-Justin

 

[Swaggy P]

Im doing the memtest right now (typing this using my phone)

 

[HonorGamer]

Whenever your memtest is done, Let's try the following.

Follow this tutorial http://www.sevenforums.com/tutorials/2495-services-start-disable.html and disable this service:

Microsoft Antimalware Service , MsMpEng.exe

And follow this one for good measures http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Note: You got me determined on this one. We will get this solved for you!

-Justin

 

[Swaggy P]

After 8-9 hours of testing, memtest has only done three passes. I had to leave for school, so I stopped it and turned my laptop off. Unfortunately, it encountered at least 1029 errors by the time I stopped the test. I don't know where to find the official results, but that's the number that I remember.

I will now follow the steps above.

I appreciate the determination that you've put into this! Thanks!

 

[Swaggy P]

It appears that I cannot disable Microsoft Antimalware Service. I couldn't change its settings since they're all grayed out. What do I do?

 

[HonorGamer]

Sorry for the late reply, just got off work.

If you have that many errors then it may be your memory causing the error.

Does your laptop have 2 sticks?
-Justin

 

[Swaggy P]

I believe so

 

[HonorGamer]

Switch em up. Take one out and ect. Test everything

-Justin

 

[Swaggy P]

Is it a foregone conclusion that the issue is associated with my RAM?
(Haven't tested my sticks, yet...too busy yesterday)

 

[HonorGamer]

We will see once you have done the tests.

If an error showed like it did, then it is very well possible.

-Justin

 

[Swaggy P]

It probably is, because I've noticed that whenever I plug my laptop to the TV using the HDMI cable it starts to heat up really quick, so I've gotten a couple of BSODs whenever it's plugged in to the TV due to a toasted RAM. BUT I have to tell you that I've had these same BSOD errors (ntoskrnl.exe) before, and it didn't require me to mess with my RAM. What's coincidental though is the fact that in both situations (then and now), I factory restored my laptop, then boom BSODs everywhere. I managed to fix the BSODs back then NOT by messing with my RAMs but with my Anti-Virus Programs (like you said), Windows Update (especially .NET Framework), Intel Rapid Storage Technology/Drivers, etc. My laptop worked for about one and a half years until now, after I reformatted my laptop back to factory restore (dumb move).

*about to test my RAM sticks*

EDIT: BTW I've also been getting a Windows Update Error about 80073712 for the "Security Update for Windows 7 x64-based Systems" and SURT doesn't seem to be able to fix it. Maybe that's another clue.

Thanks For Your Help!

 

[HonorGamer]

I've had these same BSOD errors (ntoskrnl.exe) before, and it didn't require me to mess with my RAM.

The thing about that is it blamed on the POSSIBLE cause. And in all honesty out of all the BSODs I have done, I want to say around 90% of the "Probably caused by" has been wrong. So you can't always blame it on that.

I want to take a deeper look so post up the new files, well all of them as before. I will take a much deeper look into it to see if it isn't the RAM.

Once we figure out this BSOD we can focus on that.

-Justin