Constant BSODs the past week or so

What utility are you using? You should not use a utility to update drivers, update drivers yourself from the Motherboard's/Manufacturer's web site.

Chimi, let's try something else. This will make your computer seem to run slow and a little sluggish, but use it anyway. There is always a risk of having to reinstall Windows, but we are going to take every precaution to see that that does not happen. I want you to use it and do anything you want to do with the computer and run it at least 24 hours of actual use, not just idling. Do anything you want and if there is something you do to make it BSOD, do it a lot. What we are going to do is put stress on all drivers NOT supplied by Microsoft. Sort the drivers by Provider and select all drivers not supplied by Microsoft. The first thing I want you is manually create a Restore Point, the link to how to do that is below. It is the same link to how to turn it off.

   Warning

Be sure to create a System Restore point before proceeding further System Restore Point - Create

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Chimi, what we are doing is putting extra stress on all of the third party drivers trying to make the one at fault crash the computer and catching it in the dump file. So, for once, if you have a BSOD, it isn't a bad thing.

You're right

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000096, fffff88005a88cb9, fffff880080322f0, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7ecb9 )

Try another driver, maybe an earlier one, and install it the same way, like this,
NVIDIA Drivers - Avoid Problems

Chimi, did you follow the guide I linked to, when you installed the last driver? If you did, you had a very clean install and there was nothing to roll it back to. If you didn't, please follow the guide I have linked to so you will get a clean install and have no other drivers to conflict with your new ones.
NVIDIA Drivers - Avoid Problems

Chimi, the 3 dump files all list a different thing. There is nothing consistent about the problem you have other than several of them have not blamed but mentioned problems with Audiology.exe which is a sound driver from Creative The 3 you just uploaded show:

Code:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000044, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800034ce018, address which referenced memory

This one also mentioned Audiology.

Code:

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000006, USBBUGCODE_BAD_SIGNATURE An Internal data structure (object)
 has been corrupted.
Arg2: fffffa800c4f9c70, Object address
Arg3: 0000000066725045, Signature that was expected
Arg4: 0000000000000000

Code:

Use !analyze -v to get detailed debugging information.
BugCheck D1, {ffffffff00000007, 2, 0, fffff880030c0a07}
Probably caused by : afd.sys ( afd!AfdPoll32+427 )
Followup: MachineOwner

So far nothing is consistent. Every dump has had a different cause and a different bug code. I believe we have had Bug codes of 1E, A, fe, 3B, D1 in this thread. All blame something different, from Graphics driver to USB driver to network problems and sound drivers. That, in my experience is usually a sign of memory problems. If you haven't already, please turn off Driver Verifier.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask