WinXP System Verification Error in STREAM.SYS WDM driver error 23b
Ciccio
My IBM Thinkpad WindowsXP all of a sudden won't boot properly.
I'm at my wit's end on what to do to debug & repair.
I can't even tell if it's a hardware or a software problem.
I get a dark blue screen with 2 lines across the top saying -
SYSTEM VERIFICATION ERROR IN STREAM_SYS
WDM Driver error 23b
I booted to safe mode with networking and searched for stream.sys.
C:\WINDOWS\ServicePack\stream.sys
C:\WINDOWS\System32\drivers\stream.sys
But, I don't know what to do with these same size same date files.
In safe mode, I ran verifier.exe and it only found a couple of
drivers. I ran sigverif.exe and it found only one unsigned driver
(whatever unsigned means) which was -
C:\WINDOWS\System32\drivers\csmbatt.sys
I went to the device manager and found a "PM" device, whatever that
is, which had a caution icon next to it and reinstalled that driver
using the troubleshooter.
I even tried to run the Windows Recovery Program but it failed to run.
Alas, my IBM Windows XP machine still won't boot except to safe mode.
Windows XP is a cryptic program to me as the error means me nothing.
Do you know how to solve a "WDM Driver error 23b"?
ANONYMOUS
Have you tried running sfc /scannow from the cmd prompt?
The full syntax os:
sfc [/scannow] [/scanonce] [/scanboot] [/revert] [/purgecache]
[/cachesize=x]
hth
Ciccio
<ANON...@NEWSGROUPS.COM> wrote:
>Have you tried running sfc /scannow from the cmd prompt?
Thank you so much for reading this and trying to help me!
I am stuck right now (in safe mode with networking) with this problem.
When I run "sfc /scannow" from the cmd prompt in safe mode, I get the
error that the "RPC service is unavailable" even though it is.
By the way, this reminds me, a lot of my install & uninstall activity
has been getting that RPC service error a lot lately. I wonder if it's
related? That's why I had run the Microsoft driver verifier.exe
program in the first place just before I got this dark blue screen.
Here is a paste of exactly what I see when I run sfc in WinXP:
C:\Documents and Settings\Administrator>sfc /scannow
Windows File Protection could not initiate a scan of protected system
files. The specific error code is 0x000006ba [The RPC server is
unavailable.].
Funny thing is that the RPC service is available, even in safe mode.
Remote Procedure Call (RPC) RpcSs status = started
There was another "RPC" service which was not started:
Remote Procedure Call (RPC) Locator RpcLocator status = stopped
So, I tried starting it (since it was set to Manual) while I was in
safe mode.
But doubleclicking on it in the Computer Management console gave:
Could not start the Remote Procedure Call (RPC) Locator Service on
Local Computer. Error 1084: This service cannot be started in Safe
Mode.
Do you think this is the problem?
ANONYMOUS
Have you got an OS CD with you? If so then then I would recommend you
to do a repair Install (to preserve your data and other programs) of the
OS so that it can re-copy the systems files from CD.
Please let us know so that we can give you instructions for this.
Ciccio
<ANON...@NEWSGROUPS.COM> wrote:
>Have you got an OS CD with you? If so then then I would recommend you
>to do a repair Install (to preserve your data and other programs) of the
>OS so that it can re-copy the systems files from CD.
Would a borrowed WinXP CDROM work with a valid serial number?
I made the mistake of not asking for the manufacturer's configuration
CDROM when I bought the machine two years ago. I found out later IBM
only ships you a repair CDROM if you ask for it in the first month or
so after purchase (I forget how long exactly).
Since I have a valid Windows XP Professional serial number on the
bottom of the IBM ThinkPad PC, would it work to borrow a Windows XP
CDROM (I don't know from where yet but I can ask around) and then
re-install the operating system using my valid serial number on the
sticker on the bottom of my ThinkPad?
That is, is it legal to borrow a Windows XP CDROM if I have a
perfectly valid Windows XP serial number but I don't have the
installation CDROM because the manufacturer didn't send it?
Carey Frisch [MVP]
only valid with IBM's recommended restore procedure
and is not valid with any other Windows XP CDs.
Contact IBM support for assistance.
--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/
-------------------------------------------------------------------------------------------
ANONYMOUS
No the borrowed one may not work becasue it has to be from IBM of the
same version as yours. These OEM CDs are all different and cause havocs
to systems trying to mismatch them.
However, it looks like your system has a hidden image of factory
settings and so restoring to factory level will solve all problems.
Before you do this you will need to backup your own files and documents
on a CD as we are trying to reset your system to the time when you first
received it from IBM.
Also, find all the CDs and documentations that came with the system as
this re required to bootup the system to start recovery and for proper
IBM instructions for doing so.
hth
Ciccio
<ANON...@NEWSGROUPS.COM> wrote:
>No the borrowed one may not work becasue it has to be from IBM of the
>same version as yours. These OEM CDs are all different and cause havocs
>to systems trying to mismatch them.
I found out some more information (after a few dozen reboots).
First off, the error starts with "IO" (I had omitted that by accident
from the first post).
IO System Verification Error in stream.sys
WDM Driver error 23b
What I did, in safe mode, was turn OFF the Windows "verifier.exe"
settings. Then, upon the next reboot, I was able to boot back into
Windows XP. Amazing!
You'd think the Microsoft verifier.exe program supplied in Windows XP
wouldn't prevent a reboot. I guess I'll just leave that Windows XP
verifier.exe program out of my repetoire!
Thanks for all the help. I think I'm up and running fine now. I have
no idea what that error message meant though.
ANONYMOUS
Windows verifier.exe program is very important. It verifies the drivers
and helps you to trouble shoot them.
You need to get to the bottom of this error. IO error indicates some
form of Input/Output errors which could be:
USB Camera,
Video Capture Devices
keyboard/mouse
etc etc.
I am glad everything works for now so good luck. I strongly recommend
you to back up your data everyday just in case the problem starts
again. I suspect, verifier.exe will come back as XP has the habbit of
reinstalling missing files!!
hth
Rock
Do some reading in these links from a Google search. Could be video
card related. Good luck.
http://www.google.com/search?hl=en&lr=&q=%22SYSTEM+VERIFICATION+ERROR+IN++STREAM.SYS%22&btnG=Search
--
Rock
MS MVP Windows - Shell/User
Ciccio
> Do some reading in these links from a Google search.
> Could be video card related. Good luck.
Hi Rock & Carey Frisch & ANONYMOUS,
I really (very really) appreciate your help. You stand way out in a
crowd by being willing to help a wayward soul get back on track!
It's ironic that Microsoft says to use VERIFIER.EXE as the premier
device driver check - yet, it seems everyone googled who used this
WinXP verifier.exe (http://support.microsoft.com/?kbid=244617) program
to verify device drivers was subsequently unable to reboot with the
IO System Verification Error in stream.sys WDM driver error message!
Given that the Microsoft Knowledge Base article says "The Driver
Verifier Manager tool (Verifier.exe) is the preferred way to create
and modify Driver Verifier settings and to gather statistics from
Driver Verifier. Verifier.exe is located in the %WinDir%\System32
folder for every Windows installation.", you'd think the tool would be
more robust or at least somewhat useful in its output.
There was a hint of the BSOD weaknesses when that Microsoft KB article
said "Windows kernel-mode components can cause system corruption or
system failures as a result of an improperly written driver, such as
an earlier version of a Windows Driver Model (WDM) driver.".
Hmmmmmmmm.......
Given my error message, apparently I have "an earlier version" of a
WDM driver. And, apparently that earlier WDM driver is "stream.sys".
But, what the dickens is "stream.sys"? Googling for "stream.sys wdm
driver" gave me many more of this same error, but unfortunately not
much by way of replacement information.
So, the question has now morphed into:
QUESTION:
How does one find a later version of stream.sys drivers that don't
have the WDM flaw?
Ciccio
<ANON...@NEWSGROUPS.COM> wrote:
>Windows verifier.exe program is very important. It verifies the drivers
>and helps you to trouble shoot them.
Apparently, from the Microsoft KB article
http://support.microsoft.com/?kbid=244617, the Windows XP "stream.sys"
is a "WDM" driver which is "improperly written".
My version of C:\windows\system32\drivers\stream.sys is version
5.3.2600.2180 (xpsp_sp2_rtm.040803-2158).
QUESTION:
What version is your stream.sys driver for WinXP SP2?
If I need a new stream.sys driver, where would I go to get one?
Ciccio
In some googled articles, the solution to the bad Microsoft stream.sys
WDM driver is to replace stream.sys with the OLDER WDM driver
(http://www.rage3d.com/board/showthread.php?s=&threadid=33639497)
which says to:
1. Rename the windows/driver cache/i386 folder to i386temp
2. Rename the stream.sys file in windows/system32/dllcache to
stream.old
3. Rename the stream.sys file in windows/system32/drivers folder to
stream.old
4. Extract the stream.sys file from the drivers.cab folder of the i386
folder on the XP CD ROM and copy it to the windows/systems/drivers
folder.
5. Reboot
6. Rename the windows/driver cache/i386temp folder to i386
Yet, other googling results inticate we need a newer stream.sys WDM
driver (e.g., MS KB article Q319632).
Still others indicate the problem with stream.sys WDM drivers is that
they are "not compatible with ATI's WDM drivers".
Wouldn't you know it, according to the freeware SiSoftware Sandra
(http://download.guru3d.com/sandra), my IBM Thinkpad uses ATI device
drivers!
Video Adapter: ATI MOBILITY FIRE GL 7800
Chipset : MOBILITY FIRE GL 7800 AGP (0x4C58)
Video BIOS Date: 04/11/02
File Name : System32\DRIVERS\ati2mtag.sys
Type : Kernel Device Driver
File Description : ATI Radeon WindowsNT Miniport Driver
File Version : 6.14.10.6462
Manufacturer : ATI Technologies Inc.
My problem now is where to obtain the latest stream.sys WDM driver?
Ciccio
>The OEM Product Key affixed to your IBM computer is
>only valid with IBM's recommended restore procedure
>and is not valid with any other Windows XP CDs.
>Contact IBM support for assistance.
I picked up the IBM Recovery CDROM instructions
ftp://ftp.software.ibm.com/pc/pccbbs/netvista_pdf/01r8023.pdf
by calling IBM at 1-800-IBM-SERV (1-800-426-7378) which was,
surprisingly, open 24/7. Since my PC is still under warranty (they
have a downloadable program that automatically verifies the warranty
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4VGUYW),
they said they'd ship the recovery CDROM.
In addition, they suggested I use their website program which
automatically verifies warranty information and automatically updates
the dozens of the IBM Thinkpad drivers
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=SOFT-UPDATE
Maybe one of these updated drivers will solve the stream.sys WDM error
bug! I'll let you know (please give ideas if you have any).
Ciccio
wrote:
>When I run "sfc /scannow" from the cmd prompt in safe mode, I get the
>error that the "RPC service is unavailable" even though it is.
What does the RPC server do anyway? What is it on a home network of
ONE computer? Which server is the RPC server?
I googled and found many people had the error "RPC Server is
Unavailable" but none that I found explained what the RPC server is
anyway?
To prove the RPC service was running, I ran:
C:\Documents and Settings\Administrator>net start
Which gave as its output:
These Windows services are started:
Cryptographic Services
DHCP Client
Event Log
IBM PM Service
Network Connections
Plug and Play
Print Spooler
Protected Storage
Remote Procedure Call (RPC)
Remote Procedure Call (RPC) Locator
Server
SoundMAX Agent Service
System Restore Service
Task Scheduler
Windows Audio
Windows Firewall/Internet Connection Sharing (ICS)
Windows Image Acquisition (WIA)
Windows Management Instrumentation
Windows Time
Wireless Zero Configuration
Workstation
The command completed successfully.
So, clearly the RPC service (note service, not server) is running.
But what is a RPC SERVER?
Ciccio
I'll try the troubleshooting hints at
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224370
It seems that I don't understand what a "RPC Server" is for a home
machine that is the only machine on the wireless network.
Do you?
Malke
I don't have the answer but I do have a suggestion: call Lenovo tech
support, particularly because this may be a hardware issue. Unlike
other OEM tech support, I've always found IBM (now Lenovo) support to
be excellent and their support people extremely knowledgeable.
Malke
--
MS-MVP Windows User/Shell
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"
ANONYMOUS
I too have this version:
5.3.2600.2180 (xpsp_sp2_rtm.040803-2158)
hth
Ciccio
<ANON...@NEWSGROUPS.COM> wrote:
>> What version is your stream.sys driver for WinXP SP2?
>> If I need a new stream.sys driver, where would I go to get one?
> 5.3.2600.2180 (xpsp_sp2_rtm.040803-2158)
Thanks Anonymous for taking the time to help me.
1. In order to get a new stream.sys, I first tried to update ALL my
drivers using the IBM (now called Lenovo Group Limited) all-in-one
automated driver installation engine at
http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-4VGUYW
2. Unfortunately, for 3/4 of those drivers, when they installed, one
by one, I had to click on the OK for the "RPC Server Unavailable"
error dialog. Rats.
3. So, assuming the badly written Windows stream.sys WDM driver was
updated in the IBM (now Lenovo) Mobility-RADEON/FIREGL Display Driver,
I tried to update JUST that one driver using its setup.exe installer.
4. Rats. Again I was confounded in my quest to replace stream.sys with
a newer driver when the error came up "Setup failed to launch
installation engine: The RPC server is unavailable".
5. What is this RPC Server anyway? I started researching it more and
more and I can found hundreds of people with the same error but NONE
of the postings (including the MS KB articles) seem to describe how to
determe WHO the RPC server is that Windows is trying to connect.
If I knew THAT, I could see WHY it's trying to connect to this RPC
server (whatever that is).
So I opened a separate thread asking "How do we tell WHO the RPC
server is that a WinXP machine THINKS it needs to connect to".
ANONYMOUS
ANONYMOUS
Also try this link:
http://www.google.co.uk/search?hl=en&q=RPC+Server&btnG=Search&meta=
You have lot of reading to do. In future, always make a point of
getting the original media from the vendor (even if you have to pay $20
for this service) so that resolution of problems becomes little bit
easier!
Best regards,
Ciccio
<ANON...@NEWSGROUPS.COM> wrote:
>Also try this link:
>http://www.google.co.uk/search?hl=en&q=RPC+Server&btnG=Search&meta=
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???
Ciccio
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?
Alexander Grigoriev
misbehaves, stream.sys may well crash, but the blame is on a vendor-specific
driver.
"Ciccio" <franc...@comcast.net> wrote in message
news:e51a125ma8ab4ubse...@4ax.com...
Rock
Make a restore point, rename the driver, see if that helps.
Rock
I would also make sure you have an image to restore if something goes
wrong. If you need more info on this post back.
ANONYMOUS
Ciccio wrote:
>
> 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?
Just rename it and see what happens. Test it for about a week.
adrian_b
> RPC SERVER
>
> Try this link:
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224370
>
> hth
The indicated link is out-dated.
Skiffle
news:A7294E54-090B-4AAF...@microsoft.com...
I Googled your subject line (minus the "Re: ") and surveyed the results.
The following is a post from 4 years ago but may prove helpful. You will
have some reading to do.
Skiffle