WinXP System Verification Error in STREAM.SYS WDM driver error 23b

  • Thread starter Thread starter Ciccio
  • Start date Start date
Also try this link:
http://www.google.co.uk/search?hl=en&q=RPC+Server&btnG=Search&meta=
Click to expand...

Hi Anonymous,
Yes. I agree. I had already read dozens of articles on RPC Server
Unavailable. For example ....

Remote Procedure Call
http://www.faqs.org/docs/linux_network/x-087-2-appl.rpc.html
http://searchwebservices.techtarget.com/sDefinition/0,,sid26_gci214272,00.html

And, I read these Microsoft KB Articles
224370 (http://support.microsoft.com/kb/224370/EN-US/)
Error Message: The RPC Server Is Unavailable

171781 (http://support.microsoft.com/kb/171781/EN-US/)
DNS Server Fails to Start Due to Unavailable RPC Server Error

196636 (http://support.microsoft.com/kb/196636/EN-US/)
XADM: RPC Server Unavailable Error During Setup On Cluster

The problem is that ALL these articles assume you WANT the RPC server
to be available. That is, they all ASSUME there is a domain controller
(I think) and that you KNOW what that domain controller is. Most say
"ask your system administrator". Great. I don't HAVE a system
administrator. I'm the system admistrator. The system is a single
computer on a home network. (Can you tell my frustration?)

I did run the freeware System Information for Windows by Gabriel
Topala which told me a bit more about stream.sys
http://www3.sympatico.ca/gtopala/about_siw.html

System Information said stream.sys is a WDM codec.
C:\WINDOWS\system32\drivers\stream.sys
WDM CODEC Class Device Driver 2.0

Now I have to learn what a CODEC is???
 
Could be video card related. Good luck.
Click to expand...

Hi Rock,
Apparently it's audio & video related based on this MS article
http://www.microsoft.com/whdc/device/audio/wdmaud-drv.mspx
which refers to this Microsoft WDM document
http://download.microsoft.com/download/5/b/5/5b5bec17-ea71-4653-9539-204a672f11cf/wdmaud-drv.doc
which is titled "Getting Started with WDM Audio Drivers".

From this, we see WDM stands for Windows Driver Model and "stream.sys"
is used for "kernel streaming" in non Windows XP systems (see the MS
article titled "Non-PCM Wave Formats and WDM Audio Drivers" at
http://www.microsoft.com/whdc/device/audio/Non-PCM.mspx
http://download.microsoft.com/download/5/b/5/5b5bec17-ea71-4653-9539-204a672f11cf/wdmaud-drv.doc

Specifically, Microsoft says, for non WinXP systems, "the Stream class
system driver (stream.sys) provides general streaming support for
audio and video devices.".

However, for Windows XP and later, Microsoft says "Stream has been
superseded by AVStream. Microsoft currently supports Stream on an
as-is basis for the benefit of existing Stream class minidrivers."

Hmmmmmmmm..... I wonder if this means instead of replacing the
stream.sys with a later driver, that maybe I should just delete it
since I'm on Windows XP and since Windows XP doesn't seem to need it
according to this document.

Maybe deletion is the solution here???
How does one eliminate a device driver such as stream.sys?

Do we just delete it and hope for the best?
Or is there a more proper way to eliminate device drivers?
 
Stream.sys is just a library for some vendor-specific driver. If that driver
misbehaves, stream.sys may well crash, but the blame is on a vendor-specific
driver.
 
Ciccio said:
Hi Rock,
Apparently it's audio & video related based on this MS article
http://www.microsoft.com/whdc/device/audio/wdmaud-drv.mspx
which refers to this Microsoft WDM document
http://download.microsoft.com/download/5/b/5/5b5bec17-ea71-4653-9539-204a672f11cf/wdmaud-drv.doc
which is titled "Getting Started with WDM Audio Drivers".

From this, we see WDM stands for Windows Driver Model and "stream.sys"
is used for "kernel streaming" in non Windows XP systems (see the MS
article titled "Non-PCM Wave Formats and WDM Audio Drivers" at
http://www.microsoft.com/whdc/device/audio/Non-PCM.mspx
http://download.microsoft.com/download/5/b/5/5b5bec17-ea71-4653-9539-204a672f11cf/wdmaud-drv.doc

Specifically, Microsoft says, for non WinXP systems, "the Stream class
system driver (stream.sys) provides general streaming support for
audio and video devices.".

However, for Windows XP and later, Microsoft says "Stream has been
superseded by AVStream. Microsoft currently supports Stream on an
as-is basis for the benefit of existing Stream class minidrivers."

Hmmmmmmmm..... I wonder if this means instead of replacing the
stream.sys with a later driver, that maybe I should just delete it
since I'm on Windows XP and since Windows XP doesn't seem to need it
according to this document.

Maybe deletion is the solution here???
How does one eliminate a device driver such as stream.sys?

Do we just delete it and hope for the best?
Or is there a more proper way to eliminate device drivers?
Click to expand...

Make a restore point, rename the driver, see if that helps.
 
Ciccio said:
Hi Rock,
Apparently it's audio & video related based on this MS article
http://www.microsoft.com/whdc/device/audio/wdmaud-drv.mspx
which refers to this Microsoft WDM document
http://download.microsoft.com/download/5/b/5/5b5bec17-ea71-4653-9539-204a672f11cf/wdmaud-drv.doc
which is titled "Getting Started with WDM Audio Drivers".

From this, we see WDM stands for Windows Driver Model and "stream.sys"
is used for "kernel streaming" in non Windows XP systems (see the MS
article titled "Non-PCM Wave Formats and WDM Audio Drivers" at
http://www.microsoft.com/whdc/device/audio/Non-PCM.mspx
http://download.microsoft.com/download/5/b/5/5b5bec17-ea71-4653-9539-204a672f11cf/wdmaud-drv.doc

Specifically, Microsoft says, for non WinXP systems, "the Stream class
system driver (stream.sys) provides general streaming support for
audio and video devices.".

However, for Windows XP and later, Microsoft says "Stream has been
superseded by AVStream. Microsoft currently supports Stream on an
as-is basis for the benefit of existing Stream class minidrivers."

Hmmmmmmmm..... I wonder if this means instead of replacing the
stream.sys with a later driver, that maybe I should just delete it
since I'm on Windows XP and since Windows XP doesn't seem to need it
according to this document.

Maybe deletion is the solution here???
How does one eliminate a device driver such as stream.sys?

Do we just delete it and hope for the best?
Or is there a more proper way to eliminate device drivers?
Click to expand...

I would also make sure you have an image to restore if something goes
wrong. If you need more info on this post back.
 
Ciccio said:
Maybe deletion is the solution here???
How does one eliminate a device driver such as stream.sys?

Do we just delete it and hope for the best?
Or is there a more proper way to eliminate device drivers?
Click to expand...


Just rename it and see what happens. Test it for about a week.
 
Back
Top