I'll bet a lot of those processes are programs that have added themselves to start-up that aren't necessary -- programs that you don't use regularly and can easily be accessed via Program Files. An easy way to manage those programs is with WinPatrol. (It has many other features too.)
Bill Pytlovany, the developer of WinPatrol, provides personal support for WinPatrol but also approved an unofficial help forum that I manage. You can see how easy it is to disable programs from start-up in this short tutorial: Start Up Programs: Remove, Add, Disable.
Hmm, I just got 3 BSoDs in a row. First BSoD happened, and the other two happened on the login screen. Guess the issue has not been fully resolved.. Sorry, but could you guys help me out again? I think one of the crashes was due to a Logitech thing (which I am uninstalling right now), but I have no idea what caused the other two. :/
Probably nothing but just to be sure I would make a restore point and have bootable media. If something complains about the change you should be able to safe boot(F8) so that you can rename it back.
The reason I am stressing it is that it is both 3+ years old, and some sort of tool that might be adding to the instability. AMD has an auto detect download that should tell you if you need the update and if they have it but since I dont have AMD I cant run it
You might eliminate this problem faster by doing a clean install. I realize it is a PITA but you are spending a lot of time and effort trying to fix this one problem at a time. In either case we will be happy to help.
@Satrow. Yep and was editing it when you posted. Thanks for the heads up
4 dumps attached: x2 *A, x1 *7e, and the final is a C4 Driver Verifier enabled dump. Based off of all of these different and random bugcheck codes pointing to core MS files, I'd like to say that this is hardware related. It could be software, but Driver Verifier isn't catching any drivers at fault that Windows can pinpoint.
However, interestingly enough, in the C4 verifier enabled dump, it lists the process fault as plugin-contain (or better known as plugin-container.exe). plugin_container.exe is essentially a process that allows Firefox to remain running and responsive if a plugin crashes. It may be a long shot, and it may just have been the process that Windows pinpointed because it's what THOUGHT caused the crash, but it's something worth nothing (as everything is worth noting in BSOD analysis)!
Checking the modules list of the latest dump, there's a few things that stick out:
AmdTools64.sys - Mon Apr 28 13:03:39 2008 (Related to AmdTools64.sys Special Tools Driver from Special Tools Driver).
I can't rename AMDTools64.sys, it says I need permission from SYSTEM..
I disabled UltraMon and it did nothing.
Renamed AMDTools64.sys in two instances (one in the System32/drivers folder, the other in the System32\DriverStore\FileRepository\amdtools.inf_amd64_neutral_17e9bcdeeb1f33d5). Not sure if it has done anything yet, we will have to wait and see.
I'm going to reformat if this doesn't work, might as well. I can't do anything with my laptop in this state anyways. But the biggest problem is I don't have a disc for Windows 7, I'm currently using the preinstalled one.
That's because Windows system files are protected, this is done to protect your system as renaming drivers and integral drivers and files can cause serious OS corruption (in your case, that's irrelevant). Give the "Take Ownership" script a try.
I managed to rename it by editing the Properties > Security thing. Thanks anyways! Gonna leave my laptop overnight and see how it goes. I uninstalled UltraMon this time, and changed the name of both AMDTools64.sys files.