Windows Vista 64 - random blue screens

New one..
..Again something concerning sound?

Yep, audio. The error is 0x50 and the Windows OS driver cited is PORTCLS.SYS which I believe is a Windows sound system driver. It has to do with your onboard audio chipset.

Also this process was listed: audiodg.exe which is a part of Windows Vista. System services like adio driver runs in different and isolated login session as the locally logged-in user in Windows Vista. This ensure that content and plug-ins cannot be modified by other applications (e.g. by spyware).

and again
nah, i dunno what to do lol

0xD1 and the driver cited is usbechi,sys which is belongs to your Windows OS. It is a Microsoft USB 2.0 Enhanced Host Controller Miniport Driver.

Also, once again, the driver sptd.sys was cited as not being able to load. This belongs to Daemon Tools, and Alcohol 120% and 52%. This is a CD/DVD emulation program and from what I have gathered engaes soon after boot-up and can cause instability.

Some have cited that this driver, even after the software is uninstalled, can be so deep it is like a rootkit and hard to remove.

know what? i did absolutely nothing, but BSODs just stopped..
more then 12 days - 0 BSOD.

UPDATE
This is sooo damn weird..
My BSODs stopped for like 2 months or so. About a week ago i did complete clean format of my system and installed Vista64 with intergrated SP2. At first everything went ok, but 2 days ago BSOD's returned, and now happen more often... I got about 3 in 20 min one day. The difference is, they are not random anymore. Im getting page_fault_in_nonpaged_area bsod, every time... (last time it was tdx.sys stated)

any ideas?
thanks in advance..
p.s find all last dumps attached

I read your first Zip file minidumps.

Five of the six are 0x50 errors and all cite the Windows OS driver usbccgp.sys See this link for suggestions on how to resolve: http://www.computerhope.com/cgi-bin/process.pl?p=usbccgp.sys There quite a bit on the'net concerning issues with this driver.

The remaining error is 0xD1 and these are usually caused by faulty drivers and this one cited the Nvidia display driver nvlddmkm.sys