Windows Vista 64 - random blue screens

[Route44]

so you want to say, that this last BSOD is not connected to previous ones?

We can't say with any finality because the previous one couldn't identify the offending driver. Also, keep in mind that the Creative driver couldn't load and not that it was cited as the probable cause. You may want to uninstall and reinstall or update your Creative software to see if that brings stability.

 

[rlyeh]

New one ((
Gamepanel closed

 

[Route44]

Same read as post #42: 0x50 error but could not read offending driver.

Uninstall Gamepanel. Do you still get BSODs?

Also, what did you do about your Creative drivers?

 

[rlyeh]

reinstalled them after cleaning with driver cleaner...
no help

here is latest 2, got them in few mins after previous.
its really strange. i can have no BSODs for 6 days then got 4 in a row

 

[Route44]

Okay, same error codes same read-out. however, every one also cites the Windows driver portcls.sys and so I decided to do some research on this one. it seems to have something to do with Audio controller.

Remember that Creative sound driver ctaud2k.sys your one minidump cited earlier?

Did you try to uninstall and then reinstall or update?

 

[rlyeh]

i tried resintalling creative drivers...
no luck... maybe they are just bad and i must take my audigy out.

 

[Route44]

It may come down to you needing to uninstall all the peripheral drivers and doing a Windows repair and then reinstalling your peripherals one at a time.

 

[rlyeh]

i have new idea about those BSODs
it seems i get BSOD when 2-3 programs are using my sound card (eq2, ventrilo, browser with youtube or something else.)

 

[Route44]

i have new idea about those BSODs
it seems i get BSOD when 2-3 programs are using my sound card (eq2, ventrilo, browser with youtube or something else.)

Do you get them at any other time? We've already seen Creative drivers in the mix.

 

[rlyeh]

im now testing it ..
will write here about results

 

[rlyeh]

New one..
..Again something concerning sound?

 

[Route44]

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).

 

[rlyeh]

and again
nah, i dunno what to do lol

 

[Route44]

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.

 

[rlyeh]

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

 

[rlyeh]

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

 

[Route44]

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