Multiple crashes and BSODs with random messages and filenames in them.

solshine2510 · 27 Oct 2012

Ive already had a few BSODs today since your last reply.
Immediate BSOD after starting Driver Verifier this morning displayed ksaud.sys error. I had read about Creative drivers conflicting with Windows 7 before, so I decided to get rid of it. I uinstalled software with Revo uninstaller and used Driver Fusion which you recommended earlier in this thread to delete any Creative related files (ksaud.sys still shows in drivers list when engabling Driver Verifier though).
After that I started Driver Verifier again and just had another two more consecutive BSODs after few hours.
I'm attaching new zipped file.

BTW. Does Driver Verifier actually continue to run between computer restarts? There is no similarly named process in the Task Manager.

Arc · 27 Oct 2012

It is Creative Technology Sound Blaster USB Audio

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff980086b0d20, 0, fffff880072d3503, 0}

*** WARNING: Unable to verify timestamp for ksaud.sys
*** ERROR: Module load completed but symbols could not be loaded for ksaud.sys

Could not read faulting driver name
Probably caused by : ksaud.sys ( ksaud+4503 )

Followup: MachineOwner
---------

And it is very old.

Code:

lmvm ksaud
start             end                 module name
fffff880`072cf000 fffff880`073e7580   ksaud    T (no symbols)           
    Loaded symbol image file: ksaud.sys
    Image path: \SystemRoot\system32\drivers\ksaud.sys
    Image name: ksaud.sys
    Timestamp:        Tue Dec 15 07:54:18 2009 (4B26F352)
    CheckSum:         0011ACFA
    ImageSize:        00118580
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Creative Worldwide Support

solshine2510 · 28 Oct 2012

BSODs still happen, not only ksaud.sys related. I saw usbport.sys once, memory management error as well, and something else.
Details: I updated the driver. The file I downloaded at Creative site was dated 2011. I enabled Driver Verifier and bam - immediate blue screen with ksaud.sys. So I cleared once again all occurences of Creative software with Driver Fusion and Revo uninstaller, this time in Safe mode to make sure I actually clear things. I downloaded new driver from Creative to make fresh installation. Enabled Driver Verifier. Next BSOD was not immediate, but after several minutes after starting computer.

Arc · 28 Oct 2012

Code:

........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {2558002b, 2, 0, fffff88004277dee}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Xdpc_Worker+3e )

Followup: MachineOwner
---------

What are the USB devices you use? Are the drivers of hose devices up to date? Let us know.
And, disable USB Selective Suspense : USB Selective Suspend - Turn On or Off.

solshine2510 · 28 Oct 2012

I have disabled the USB Selective Suspend.
I have 4 devices connected via USB ports: mouse, keyboard, speakers and that Creative Soundblaster card. Except the audio card, none of the devices had manually installed drivers, they always worked as plug and play.
Drivers available on manufacturers' sites are very old: Mouse driver is from 2008 (A4Tech SWOP-80). Keyboard Logitech ULTRAX Premium Keyboard driver is from 2009. The 2.0 speakers are poor noname quality as I mostly use headphones, and came with no drivers. Should I install those old mouse and keyboard drivers?
I also have "USB 2.0 PCI HOST ADAPTER 4 PORTS"' installed just in case I have to connect something extra via USB (it's not used right now). This card came with drivers on CD and it says only 2.0 driver on them.

Im attaching new file with more recent data after latest BSODs. One crash had no blue screen visible, just blank screen as if suddenly unplugged, without the usual half a sec freeze.

Arc · 28 Oct 2012

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

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

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

solshine2510 · 31 Oct 2012

I ran Driver verifier since 28 Oct. Crashes that happened that day:

17:50 (time roughly) Memory Management BSOD
20:45 Memory Management followed immediately by ksaud.sys BSOD after restart
21:04 Memory Management again followed by ksaud.sys after restart.

After that I definitively removed Sound Blaster X-FI external card - unplugged and uninstalled software/drivers. That last crash forced system restore and unfortunately I forgot to turn on Driver Verifier back, so the next BSOD (30 Oct, 00:46) was without Driver Verifier running (it stated: System Service Exception).

Then I reenabled Driver Verifier and next BSOD happened today at 16:17 - Memory Management.

Arc · 31 Oct 2012

That's the better idea, as the crashes without DV is not providing any information at all.

solshine2510 · 31 Oct 2012

Arc said:

That's the better idea, as the crashes without DV is not providing any information at all.

The attached file does contain the DV evoked BSODs I mentioned eaerlier (28 Oct & 31 Oct). What do you make of them, or at least the last one, after removing the sound card? Anyhow, if it doesn't say much, I'll continue having DV on so I'll post new data should any more BSODs happen.

Arc · 31 Oct 2012

The dumps those are after removing the sound card, not showing any viable cause at all, and that is why I told that DV will be a better idea again.