Whenever your memtest is done, Let's try the following.
Follow this tutorial Services - Start or Disable and disable this service:
And follow this one for good measures SFC /SCANNOW Command - System File CheckerCode:Microsoft Antimalware Service , MsMpEng.exe
Note: You got me determined on this one. We will get this solved for you!
-Justin
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!
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?
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
Is it a foregone conclusion that the issue is associated with my RAM?
(Haven't tested my sticks, yet...too busy yesterday)
We will see once you have done the tests.
If an error showed like it did, then it is very well possible.
-Justin
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!
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've had these same BSOD errors (ntoskrnl.exe) before, and it didn't require me to mess with my RAM.
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
Quote