Nvidia Nforce Raid Class Device Update 80070103 error

does this error on this update simply mean i have the update already? or i
have a newer version of the update?... or something else entirely?
--
Cheers, Liam

Hello Liam,

Windows Update error 8007010
http://windowshelp.microsoft.com/win...dabcd1033.mspx
You should NOT use winupdate for hardware drivers, use only the
manufacturers sites, and then unless its to cure a bug or increase
functionality why update a driver?
If it aint broke, dont fix it
--

Good luck
--


"Liam Richmond" wrote:

> does this error on this update simply mean i have the update already? or i
> have a newer version of the update?... or something else entirely?
> --
> Cheers, Liam

"Engel" wrote:

> Hello Liam,
>
> Windows Update error 80070103
> http://windowshelp.microsoft.com/win...dabcd1033.mspx
> You should NOT use winupdate for hardware drivers, use only the
> manufacturers sites, and then unless its to cure a bug or increase
> functionality why update a driver?
> If it aint broke, dont fix it

I have never understood why people say stupid things like this. Clearly, if
there is an update, then it is "broke" - the one thing you know absolutely is
that there are some bugs, for which, you do not have the fixes. Clearly, if
Windows update has an update, then it was designed to be installed and
generally comes from the manufacturer.

Clearly, the OP couched the question in that form because they had already
read the message you point to, as had I.

The argument that you should not upgrade because you don't know if the
upgrade wil break things falls down on the fact that you now know for certain
that what you have is broken, even if you have not seen why yet.

And we still don't know what the error message means.

"Jim Idle" <JimIdle@discussions.microsoft.com> wrote in message
news:46EF329A-3D01-4189-89BA-7BE233FE722B@microsoft.com...
|
|
| "Engel" wrote:
|
| > Hello Liam,
| >
| > Windows Update error 80070103
| >
http://windowshelp.microsoft.com/win...dabcd1033.mspx
| > You should NOT use winupdate for hardware drivers, use only the
| > manufacturers sites, and then unless its to cure a bug or increase
| > functionality why update a driver?
| > If it aint broke, dont fix it
|
| I have never understood why people say stupid things like this. Clearly, if
| there is an update, then it is "broke" - the one thing you know absolutely is
| that there are some bugs, for which, you do not have the fixes. Clearly, if
| Windows update has an update, then it was designed to be installed and
| generally comes from the manufacturer.
|
| Clearly, the OP couched the question in that form because they had already
| read the message you point to, as had I.
|
| The argument that you should not upgrade because you don't know if the
| upgrade wil break things falls down on the fact that you now know for certain
| that what you have is broken, even if you have not seen why yet.
|
| And we still don't know what the error message means.


0x80070103 - If relating to a driver - the driver you are trying to install is already
installed or the driver that you're trying to install is an older driver than the one you
have already.
If relating to an installation:

Error message when you try to upgrade a computer to Windows Vista: "This computer does not
have enough space for temporary files. Error code 0x80070103"
http://support.microsoft.com/kb/928232/en-us

The reason it is mentioned to get updates for drivers from the manufacturer is because the
manufacturer has the most up to date driver etc.
If WU mentions you need a driver - then you automatically check the manufacturer's site to
see if in fact you do need it.
Many do not trust WU for drivers - nor do I. I simply use the notification to alert me to
the fact that a new driver may be available and whether or not I need/wish to install the
same.


--
====================================
TaurArian [MS-MVP] 2005-2008 - Australia
====================================
How to make a good post: http://www.dts-l.org/goodpost.htm
Defending your machine: http://defendingyourmachine2.blogspot.com/
http://taurarian.mvps.org/index.htm

Emails will not be acknowledged - please post to the newsgroup so all may benefit.

"Jim Idle" <JimIdle@discussions.microsoft.com> wrote in message
news:46EF329A-3D01-4189-89BA-7BE233FE722B@microsoft.com...
>
>
> "Engel" wrote:
>
>> Hello Liam,
>>
>> Windows Update error 80070103
....

> And we still don't know what the error message means.


<cmd_output OS="XPsp2">
F:\>set /a c = 0x103
259
F:\>net helpmsg %c%

No more data is available.
</cmd_output>


FWIW my guess is neither does the update. ; )

Find the code's context in the install log.
If that doesn't give enough clues activate verbose logging for the update
(if there is such an option.)
If that doesn't give enough clues use ProcMon to supplement both
with any interleaving registry and file accesses.


Good luck

Robert Aldwinckle
---

RE: "Find the code's context in the install log.
If that doesn't give enough clues activate verbose logging for the update
(if there is such an option.)
If that doesn't give enough clues use ProcMon to supplement both
with any interleaving registry and file accesses."

That sounds like a great idea ... if only I had a clue what it all meant.
It also sounds like a lot of work. In fact, resulting in an impossible
amount for dummies like me who will surely do more damage than good. Those
big words are impressive though!

Microsoft needs to fix this problem and not leave it up to hamheads like me.

For what it's worth, I too have this same problem & error code, regardless
of updating via the Vista updates or the nVidia site. In both cases, the
same thing happens. The driver installation goes seemingly smooth right
through the last screen that prompts a restart. During the restart, Vista
appears to load in a normal manner up to the point where (I think) it
switches away from the base VGA drivers to the installed ones. The monitor
will briefly flash a blue screen with the monitor throwing up the usual "no
video input" message. This only lasts a second or two then the screen goes
black (not from the monitor turning off ... just a black screen). The black
screen stays that way FOREVER, and while waiting, I saw that the hard drive
remained active doing who-knows-what (I finally gave up after waiting 12
hours). The system never really "locked up" it seemed. And the hard drive
activity was intermittent but not following any noticeable pattern. The only
way past this was booting to safe mode. Turning off all the unnecessary crap
via msconfig didn't help. Any attempt to do a normal boot ended at exactly
the same place and with the same unending hard drive use & lack of video.

An nVidia tech told me to try uninstalling then reinstalling in safe mode so
as to prevent possible corruption from all the Vista security stuff
interfering with the installation process (which he claimed was usually the
cause of driver problems when using the ones from windows updates). Sounded
promising, but still no dice. Same situation when trying to boot normally.
The only way around it has been to uninstall the device & drivers, then
reinstall the old ones that the Vista installation disk had.

As for the "well, if it ain't broke, don't fix it" mentality ... then why
bother changing the oil in your car ... or, buying new clothes while growing?
Or, in my case, why care about the fact that I have a second GeForce 7300 in
there just lounging around because I can't enable SLI with the WDDM drivers
(haven't found a way anyhow .. if anyone knows I'd sure like to hear it).
No, I spent way too much time & money here to stay satisfied without ever
being able to update the drivers. It also wasn't something I planned while
shelling out 380 clams for Vista Ultimate.

So, my friends, if someone actually knows the solution to this, I'd sure
appreciate the benefit of your knowledge. No guesses please ... they may be
cheap, but there's a reason for that.

Hi there,

Your graphic card is Nvidia so you should look at Nvidia for an updated
driver if needed.

Chanching oil in your car is needed to prevent the engine from getting
damaged, using an old good working driver will not damage your graphic
card;)

Your issue with not being able to use SLI might be driver or bios related.

The chipset and graphic cards somehow do not want to work well together, so
this is an Nvidia issue and the chipset brand you should try to get support
for the problem there.

Wish you good luck on solving the problem, searching with a search engine
might be helpfull in finding some clues.

Best regards,
Michel Denie

"JETHRO" <JETHRO@discussions.microsoft.com> wrote in message
news:23C71D47-D274-4111-A1A4-F6F454BEC6FF@microsoft.com...
> RE: "Find the code's context in the install log.
> If that doesn't give enough clues activate verbose logging for the update
> (if there is such an option.)
> If that doesn't give enough clues use ProcMon to supplement both
> with any interleaving registry and file accesses."
>
> That sounds like a great idea ... if only I had a clue what it all meant.
> It also sounds like a lot of work. In fact, resulting in an impossible
> amount for dummies like me who will surely do more damage than good.
> Those
> big words are impressive though!
>
> Microsoft needs to fix this problem and not leave it up to hamheads like
> me.
>
> For what it's worth, I too have this same problem & error code, regardless
> of updating via the Vista updates or the nVidia site. In both cases, the
> same thing happens. The driver installation goes seemingly smooth right
> through the last screen that prompts a restart. During the restart, Vista
> appears to load in a normal manner up to the point where (I think) it
> switches away from the base VGA drivers to the installed ones. The
> monitor
> will briefly flash a blue screen with the monitor throwing up the usual
> "no
> video input" message. This only lasts a second or two then the screen
> goes
> black (not from the monitor turning off ... just a black screen). The
> black
> screen stays that way FOREVER, and while waiting, I saw that the hard
> drive
> remained active doing who-knows-what (I finally gave up after waiting 12
> hours). The system never really "locked up" it seemed. And the hard
> drive
> activity was intermittent but not following any noticeable pattern. The
> only
> way past this was booting to safe mode. Turning off all the unnecessary
> crap
> via msconfig didn't help. Any attempt to do a normal boot ended at
> exactly
> the same place and with the same unending hard drive use & lack of video.
>
> An nVidia tech told me to try uninstalling then reinstalling in safe mode
> so
> as to prevent possible corruption from all the Vista security stuff
> interfering with the installation process (which he claimed was usually
> the
> cause of driver problems when using the ones from windows updates).
> Sounded
> promising, but still no dice. Same situation when trying to boot
> normally.
> The only way around it has been to uninstall the device & drivers, then
> reinstall the old ones that the Vista installation disk had.
>
> As for the "well, if it ain't broke, don't fix it" mentality ... then why
> bother changing the oil in your car ... or, buying new clothes while
> growing?
> Or, in my case, why care about the fact that I have a second GeForce 7300
> in
> there just lounging around because I can't enable SLI with the WDDM
> drivers
> (haven't found a way anyhow .. if anyone knows I'd sure like to hear it).
> No, I spent way too much time & money here to stay satisfied without ever
> being able to update the drivers. It also wasn't something I planned
> while
> shelling out 380 clams for Vista Ultimate.
>
> So, my friends, if someone actually knows the solution to this, I'd sure
> appreciate the benefit of your knowledge. No guesses please ... they may
> be
> cheap, but there's a reason for that.
>
>
>

Thanks for your response Michel but, as I stated, I have contacted nVidia for
a fix. And, they obviously weren't able to help ... not the few people I
spoke with anyway. Also, I'm not so sure it's an nVidia issue as much as a
Windows one. I've never, ever, had one single problem with nVidia driver
installs. Not until now. And, only after switching to Vista. Since the
drivers I DLed from the nVidia site didn't work out nor the ones from the
Visia automatic updates (yes, I realize MS gets them from nVidia), I'm more
inclined to believe that the problem lies with Vista. For all I know, maybe
there's just a setting that needs to be changed. Whatever the reason though,
my money goes on the operating system having both the fault and the answer.

Come on all you Geeks and Windows Wizards ... somebody who actually knows
about this help me out here!

"realcestmoi" wrote:

> Hi there,
>
> Your graphic card is Nvidia so you should look at Nvidia for an updated
> driver if needed.
>
> Chanching oil in your car is needed to prevent the engine from getting
> damaged, using an old good working driver will not damage your graphic
> card;)
>
> Your issue with not being able to use SLI might be driver or bios related.
>
> The chipset and graphic cards somehow do not want to work well together, so
> this is an Nvidia issue and the chipset brand you should try to get support
> for the problem there.
>
> Wish you good luck on solving the problem, searching with a search engine
> might be helpfull in finding some clues.
>
> Best regards,
> Michel Denie
>
> "JETHRO" <JETHRO@discussions.microsoft.com> wrote in message
> news:23C71D47-D274-4111-A1A4-F6F454BEC6FF@microsoft.com...
> > RE: "Find the code's context in the install log.
> > If that doesn't give enough clues activate verbose logging for the update
> > (if there is such an option.)
> > If that doesn't give enough clues use ProcMon to supplement both
> > with any interleaving registry and file accesses."
> >
> > That sounds like a great idea ... if only I had a clue what it all meant.
> > It also sounds like a lot of work. In fact, resulting in an impossible
> > amount for dummies like me who will surely do more damage than good.
> > Those
> > big words are impressive though!
> >
> > Microsoft needs to fix this problem and not leave it up to hamheads like
> > me.
> >
> > For what it's worth, I too have this same problem & error code, regardless
> > of updating via the Vista updates or the nVidia site. In both cases, the
> > same thing happens. The driver installation goes seemingly smooth right
> > through the last screen that prompts a restart. During the restart, Vista
> > appears to load in a normal manner up to the point where (I think) it
> > switches away from the base VGA drivers to the installed ones. The
> > monitor
> > will briefly flash a blue screen with the monitor throwing up the usual
> > "no
> > video input" message. This only lasts a second or two then the screen
> > goes
> > black (not from the monitor turning off ... just a black screen). The
> > black
> > screen stays that way FOREVER, and while waiting, I saw that the hard
> > drive
> > remained active doing who-knows-what (I finally gave up after waiting 12
> > hours). The system never really "locked up" it seemed. And the hard
> > drive
> > activity was intermittent but not following any noticeable pattern. The
> > only
> > way past this was booting to safe mode. Turning off all the unnecessary
> > crap
> > via msconfig didn't help. Any attempt to do a normal boot ended at
> > exactly
> > the same place and with the same unending hard drive use & lack of video.
> >
> > An nVidia tech told me to try uninstalling then reinstalling in safe mode
> > so
> > as to prevent possible corruption from all the Vista security stuff
> > interfering with the installation process (which he claimed was usually
> > the
> > cause of driver problems when using the ones from windows updates).
> > Sounded
> > promising, but still no dice. Same situation when trying to boot
> > normally.
> > The only way around it has been to uninstall the device & drivers, then
> > reinstall the old ones that the Vista installation disk had.
> >
> > As for the "well, if it ain't broke, don't fix it" mentality ... then why
> > bother changing the oil in your car ... or, buying new clothes while
> > growing?
> > Or, in my case, why care about the fact that I have a second GeForce 7300
> > in
> > there just lounging around because I can't enable SLI with the WDDM
> > drivers
> > (haven't found a way anyhow .. if anyone knows I'd sure like to hear it).
> > No, I spent way too much time & money here to stay satisfied without ever
> > being able to update the drivers. It also wasn't something I planned
> > while
> > shelling out 380 clams for Vista Ultimate.
> >
> > So, my friends, if someone actually knows the solution to this, I'd sure
> > appreciate the benefit of your knowledge. No guesses please ... they may
> > be
> > cheap, but there's a reason for that.
> >
> >
> >
>
>
>

Hi there,

You might want to check this out:
http://www.nvidia.com/object/vista_d...ws_030207.html

and this one describes your black screen problem:
http://www.theinquirer.net/en/inquir...-really-worked

Found with alittle googling;)

Best regards,
Michel Denie


"JETHRO" <JETHRO@discussions.microsoft.com> wrote in message
news:1977FA33-A8E7-4B8A-96E3-9830660F071C@microsoft.com...
> Thanks for your response Michel but, as I stated, I have contacted nVidia
> for
> a fix. And, they obviously weren't able to help ... not the few people I
> spoke with anyway. Also, I'm not so sure it's an nVidia issue as much as
> a
> Windows one. I've never, ever, had one single problem with nVidia driver
> installs. Not until now. And, only after switching to Vista. Since the
> drivers I DLed from the nVidia site didn't work out nor the ones from the
> Visia automatic updates (yes, I realize MS gets them from nVidia), I'm
> more
> inclined to believe that the problem lies with Vista. For all I know,
> maybe
> there's just a setting that needs to be changed. Whatever the reason
> though,
> my money goes on the operating system having both the fault and the
> answer.
>
> Come on all you Geeks and Windows Wizards ... somebody who actually knows
> about this help me out here!
>
> "realcestmoi" wrote:
>
>> Hi there,
>>
>> Your graphic card is Nvidia so you should look at Nvidia for an updated
>> driver if needed.
>>
>> Chanching oil in your car is needed to prevent the engine from getting
>> damaged, using an old good working driver will not damage your graphic
>> card;)
>>
>> Your issue with not being able to use SLI might be driver or bios
>> related.
>>
>> The chipset and graphic cards somehow do not want to work well together,
>> so
>> this is an Nvidia issue and the chipset brand you should try to get
>> support
>> for the problem there.
>>
>> Wish you good luck on solving the problem, searching with a search engine
>> might be helpfull in finding some clues.
>>
>> Best regards,
>> Michel Denie
>>
>> "JETHRO" <JETHRO@discussions.microsoft.com> wrote in message
>> news:23C71D47-D274-4111-A1A4-F6F454BEC6FF@microsoft.com...
>> > RE: "Find the code's context in the install log.
>> > If that doesn't give enough clues activate verbose logging for the
>> > update
>> > (if there is such an option.)
>> > If that doesn't give enough clues use ProcMon to supplement both
>> > with any interleaving registry and file accesses."
>> >
>> > That sounds like a great idea ... if only I had a clue what it all
>> > meant.
>> > It also sounds like a lot of work. In fact, resulting in an impossible
>> > amount for dummies like me who will surely do more damage than good.
>> > Those
>> > big words are impressive though!
>> >
>> > Microsoft needs to fix this problem and not leave it up to hamheads
>> > like
>> > me.
>> >
>> > For what it's worth, I too have this same problem & error code,
>> > regardless
>> > of updating via the Vista updates or the nVidia site. In both cases,
>> > the
>> > same thing happens. The driver installation goes seemingly smooth
>> > right
>> > through the last screen that prompts a restart. During the restart,
>> > Vista
>> > appears to load in a normal manner up to the point where (I think) it
>> > switches away from the base VGA drivers to the installed ones. The
>> > monitor
>> > will briefly flash a blue screen with the monitor throwing up the usual
>> > "no
>> > video input" message. This only lasts a second or two then the screen
>> > goes
>> > black (not from the monitor turning off ... just a black screen). The
>> > black
>> > screen stays that way FOREVER, and while waiting, I saw that the hard
>> > drive
>> > remained active doing who-knows-what (I finally gave up after waiting
>> > 12
>> > hours). The system never really "locked up" it seemed. And the hard
>> > drive
>> > activity was intermittent but not following any noticeable pattern.
>> > The
>> > only
>> > way past this was booting to safe mode. Turning off all the
>> > unnecessary
>> > crap
>> > via msconfig didn't help. Any attempt to do a normal boot ended at
>> > exactly
>> > the same place and with the same unending hard drive use & lack of
>> > video.
>> >
>> > An nVidia tech told me to try uninstalling then reinstalling in safe
>> > mode
>> > so
>> > as to prevent possible corruption from all the Vista security stuff
>> > interfering with the installation process (which he claimed was usually
>> > the
>> > cause of driver problems when using the ones from windows updates).
>> > Sounded
>> > promising, but still no dice. Same situation when trying to boot
>> > normally.
>> > The only way around it has been to uninstall the device & drivers, then
>> > reinstall the old ones that the Vista installation disk had.
>> >
>> > As for the "well, if it ain't broke, don't fix it" mentality ... then
>> > why
>> > bother changing the oil in your car ... or, buying new clothes while
>> > growing?
>> > Or, in my case, why care about the fact that I have a second GeForce
>> > 7300
>> > in
>> > there just lounging around because I can't enable SLI with the WDDM
>> > drivers
>> > (haven't found a way anyhow .. if anyone knows I'd sure like to hear
>> > it).
>> > No, I spent way too much time & money here to stay satisfied without
>> > ever
>> > being able to update the drivers. It also wasn't something I planned
>> > while
>> > shelling out 380 clams for Vista Ultimate.
>> >
>> > So, my friends, if someone actually knows the solution to this, I'd
>> > sure
>> > appreciate the benefit of your knowledge. No guesses please ... they
>> > may
>> > be
>> > cheap, but there's a reason for that.
>> >
>> >
>> >
>>
>>
>>

RE: "0x80070103 - If relating to a driver - the driver you are trying to
install is already installed or the driver that you're trying to install is
an older driver than the one you have already."

If relating to an installation:

"Error message when you try to upgrade a computer to Windows Vista: "This
computer does not have enough space for temporary files. Error code
0x80070103"

______________________________________________

OK ... then riddle me this ... how is it that I got the same error code when
trying to go from the drivers supplied on the Vista CD, which are listed as
nVidia release # 97 from about 6 months ago, to the latest ones on the nVidia
site (release # 163) ? Obviously, there has to be more to that code or else
it's just plain wrong.

As for the second point re: insufficient memory ... well, I don't see that
one holding water either. I have 4GB of RAM and about 17GB of free hard
drive ... surely a few temp installation files would fit in there somewhere?

"TaurArian [MS-MVP]" wrote:

>
> "Jim Idle" <JimIdle@discussions.microsoft.com> wrote in message
> news:46EF329A-3D01-4189-89BA-7BE233FE722B@microsoft.com...
> |
> |
> | "Engel" wrote:
> |
> | > Hello Liam,
> | >
> | > Windows Update error 80070103
> | >
> http://windowshelp.microsoft.com/win...dabcd1033.mspx
> | > You should NOT use winupdate for hardware drivers, use only the
> | > manufacturers sites, and then unless its to cure a bug or increase
> | > functionality why update a driver?
> | > If it aint broke, dont fix it
> |
> | I have never understood why people say stupid things like this. Clearly, if
> | there is an update, then it is "broke" - the one thing you know absolutely is
> | that there are some bugs, for which, you do not have the fixes. Clearly, if
> | Windows update has an update, then it was designed to be installed and
> | generally comes from the manufacturer.
> |
> | Clearly, the OP couched the question in that form because they had already
> | read the message you point to, as had I.
> |
> | The argument that you should not upgrade because you don't know if the
> | upgrade wil break things falls down on the fact that you now know for certain
> | that what you have is broken, even if you have not seen why yet.
> |
> | And we still don't know what the error message means.
>
>
> 0x80070103 - If relating to a driver - the driver you are trying to install is already
> installed or the driver that you're trying to install is an older driver than the one you
> have already.
> If relating to an installation:
>
> Error message when you try to upgrade a computer to Windows Vista: "This computer does not
> have enough space for temporary files. Error code 0x80070103"
> http://support.microsoft.com/kb/928232/en-us
>
> The reason it is mentioned to get updates for drivers from the manufacturer is because the
> manufacturer has the most up to date driver etc.
> If WU mentions you need a driver - then you automatically check the manufacturer's site to
> see if in fact you do need it.
> Many do not trust WU for drivers - nor do I. I simply use the notification to alert me to
> the fact that a new driver may be available and whether or not I need/wish to install the
> same.
>
>
> --
> ====================================
> TaurArian [MS-MVP] 2005-2008 - Australia
> ====================================
> How to make a good post: http://www.dts-l.org/goodpost.htm
> Defending your machine: http://defendingyourmachine2.blogspot.com/
> http://taurarian.mvps.org/index.htm
>
> Emails will not be acknowledged - please post to the newsgroup so all may benefit.
>
>
>

Thanks Michel ! I'll definitely check them out this evening after dinner.
I'd really like to get to the bottom of this. I miss playing COD2 in SLi !

"realcestmoi" wrote:

> Hi there,
>
> You might want to check this out:
> http://www.nvidia.com/object/vista_d...ws_030207.html
>
> and this one describes your black screen problem:
> http://www.theinquirer.net/en/inquir...-really-worked
>
> Found with alittle googling;)
>
> Best regards,
> Michel Denie
>
>
> "JETHRO" <JETHRO@discussions.microsoft.com> wrote in message
> news:1977FA33-A8E7-4B8A-96E3-9830660F071C@microsoft.com...
> > Thanks for your response Michel but, as I stated, I have contacted nVidia
> > for
> > a fix. And, they obviously weren't able to help ... not the few people I
> > spoke with anyway. Also, I'm not so sure it's an nVidia issue as much as
> > a
> > Windows one. I've never, ever, had one single problem with nVidia driver
> > installs. Not until now. And, only after switching to Vista. Since the
> > drivers I DLed from the nVidia site didn't work out nor the ones from the
> > Visia automatic updates (yes, I realize MS gets them from nVidia), I'm
> > more
> > inclined to believe that the problem lies with Vista. For all I know,
> > maybe
> > there's just a setting that needs to be changed. Whatever the reason
> > though,
> > my money goes on the operating system having both the fault and the
> > answer.
> >
> > Come on all you Geeks and Windows Wizards ... somebody who actually knows
> > about this help me out here!
> >
> > "realcestmoi" wrote:
> >
> >> Hi there,
> >>
> >> Your graphic card is Nvidia so you should look at Nvidia for an updated
> >> driver if needed.
> >>
> >> Chanching oil in your car is needed to prevent the engine from getting
> >> damaged, using an old good working driver will not damage your graphic
> >> card;)
> >>
> >> Your issue with not being able to use SLI might be driver or bios
> >> related.
> >>
> >> The chipset and graphic cards somehow do not want to work well together,
> >> so
> >> this is an Nvidia issue and the chipset brand you should try to get
> >> support
> >> for the problem there.
> >>
> >> Wish you good luck on solving the problem, searching with a search engine
> >> might be helpfull in finding some clues.
> >>
> >> Best regards,
> >> Michel Denie
> >>
> >> "JETHRO" <JETHRO@discussions.microsoft.com> wrote in message
> >> news:23C71D47-D274-4111-A1A4-F6F454BEC6FF@microsoft.com...
> >> > RE: "Find the code's context in the install log.
> >> > If that doesn't give enough clues activate verbose logging for the
> >> > update
> >> > (if there is such an option.)
> >> > If that doesn't give enough clues use ProcMon to supplement both
> >> > with any interleaving registry and file accesses."
> >> >
> >> > That sounds like a great idea ... if only I had a clue what it all
> >> > meant.
> >> > It also sounds like a lot of work. In fact, resulting in an impossible
> >> > amount for dummies like me who will surely do more damage than good.
> >> > Those
> >> > big words are impressive though!
> >> >
> >> > Microsoft needs to fix this problem and not leave it up to hamheads
> >> > like
> >> > me.
> >> >
> >> > For what it's worth, I too have this same problem & error code,
> >> > regardless
> >> > of updating via the Vista updates or the nVidia site. In both cases,
> >> > the
> >> > same thing happens. The driver installation goes seemingly smooth
> >> > right
> >> > through the last screen that prompts a restart. During the restart,
> >> > Vista
> >> > appears to load in a normal manner up to the point where (I think) it
> >> > switches away from the base VGA drivers to the installed ones. The
> >> > monitor
> >> > will briefly flash a blue screen with the monitor throwing up the usual
> >> > "no
> >> > video input" message. This only lasts a second or two then the screen
> >> > goes
> >> > black (not from the monitor turning off ... just a black screen). The
> >> > black
> >> > screen stays that way FOREVER, and while waiting, I saw that the hard
> >> > drive
> >> > remained active doing who-knows-what (I finally gave up after waiting
> >> > 12
> >> > hours). The system never really "locked up" it seemed. And the hard
> >> > drive
> >> > activity was intermittent but not following any noticeable pattern.
> >> > The
> >> > only
> >> > way past this was booting to safe mode. Turning off all the
> >> > unnecessary
> >> > crap
> >> > via msconfig didn't help. Any attempt to do a normal boot ended at
> >> > exactly
> >> > the same place and with the same unending hard drive use & lack of
> >> > video.
> >> >
> >> > An nVidia tech told me to try uninstalling then reinstalling in safe
> >> > mode
> >> > so
> >> > as to prevent possible corruption from all the Vista security stuff
> >> > interfering with the installation process (which he claimed was usually
> >> > the
> >> > cause of driver problems when using the ones from windows updates).
> >> > Sounded
> >> > promising, but still no dice. Same situation when trying to boot
> >> > normally.
> >> > The only way around it has been to uninstall the device & drivers, then
> >> > reinstall the old ones that the Vista installation disk had.
> >> >
> >> > As for the "well, if it ain't broke, don't fix it" mentality ... then
> >> > why
> >> > bother changing the oil in your car ... or, buying new clothes while
> >> > growing?
> >> > Or, in my case, why care about the fact that I have a second GeForce
> >> > 7300
> >> > in
> >> > there just lounging around because I can't enable SLI with the WDDM
> >> > drivers
> >> > (haven't found a way anyhow .. if anyone knows I'd sure like to hear
> >> > it).
> >> > No, I spent way too much time & money here to stay satisfied without
> >> > ever
> >> > being able to update the drivers. It also wasn't something I planned
> >> > while
> >> > shelling out 380 clams for Vista Ultimate.
> >> >
> >> > So, my friends, if someone actually knows the solution to this, I'd
> >> > sure
> >> > appreciate the benefit of your knowledge. No guesses please ... they
> >> > may
> >> > be
> >> > cheap, but there's a reason for that.
> >> >
> >> >
> >> >
> >>
> >>
> >>
>
>
>

If you install some of the latest NVIDIA drivers (WHQL even) from the NVIDIA
site, you will run into driver conflicts. I still cannot resolve the
conflicts between the driver for my GPU (NVIDIA's) and MediaShield SATA RAID
drivers with those from Microsoft.

If you only go with the MS drivers (from NVIDIA), everything runs fine but
you suffer a performance loss and a lot of the extras like the ability to
enable SATA HDD Command Queueing are lost. On the other hand, if you install
the latest (WHQL) NVIDIA drivers, you will start to have problems like lost
icons, programs where DLLs are "missing" (so it says), and eventually your
MBR, index and then MFT will become corrupted.

So, I think this issue is still up in the air. Right now -- mainly because
I'm tired of losing my *&^^%% RAID0 entire HDD information and starting from
scratch, I'm *not* installing any of the NVIDIA drivers.

Shawn Harvey
sparkinark@yahoo.com



"JETHRO" wrote:

> Thanks Michel ! I'll definitely check them out this evening after dinner.
> I'd really like to get to the bottom of this. I miss playing COD2 in SLi !
>
> "realcestmoi" wrote:
>
> > Hi there,
> >
> > You might want to check this out:
> > http://www.nvidia.com/object/vista_d...ws_030207.html
> >
> > and this one describes your black screen problem:
> > http://www.theinquirer.net/en/inquir...-really-worked
> >
> > Found with alittle googling;)
> >
> > Best regards,
> > Michel Denie
> >
> >
> > "JETHRO" <JETHRO@discussions.microsoft.com> wrote in message
> > news:1977FA33-A8E7-4B8A-96E3-9830660F071C@microsoft.com...
> > > Thanks for your response Michel but, as I stated, I have contacted nVidia
> > > for
> > > a fix. And, they obviously weren't able to help ... not the few people I
> > > spoke with anyway. Also, I'm not so sure it's an nVidia issue as much as
> > > a
> > > Windows one. I've never, ever, had one single problem with nVidia driver
> > > installs. Not until now. And, only after switching to Vista. Since the
> > > drivers I DLed from the nVidia site didn't work out nor the ones from the
> > > Visia automatic updates (yes, I realize MS gets them from nVidia), I'm
> > > more
> > > inclined to believe that the problem lies with Vista. For all I know,
> > > maybe
> > > there's just a setting that needs to be changed. Whatever the reason
> > > though,
> > > my money goes on the operating system having both the fault and the
> > > answer.
> > >
> > > Come on all you Geeks and Windows Wizards ... somebody who actually knows
> > > about this help me out here!
> > >
> > > "realcestmoi" wrote:
> > >
> > >> Hi there,
> > >>
> > >> Your graphic card is Nvidia so you should look at Nvidia for an updated
> > >> driver if needed.
> > >>
> > >> Chanching oil in your car is needed to prevent the engine from getting
> > >> damaged, using an old good working driver will not damage your graphic
> > >> card;)
> > >>
> > >> Your issue with not being able to use SLI might be driver or bios
> > >> related.
> > >>
> > >> The chipset and graphic cards somehow do not want to work well together,
> > >> so
> > >> this is an Nvidia issue and the chipset brand you should try to get
> > >> support
> > >> for the problem there.
> > >>
> > >> Wish you good luck on solving the problem, searching with a search engine
> > >> might be helpfull in finding some clues.
> > >>
> > >> Best regards,
> > >> Michel Denie
> > >>
> > >> "JETHRO" <JETHRO@discussions.microsoft.com> wrote in message
> > >> news:23C71D47-D274-4111-A1A4-F6F454BEC6FF@microsoft.com...
> > >> > RE: "Find the code's context in the install log.
> > >> > If that doesn't give enough clues activate verbose logging for the
> > >> > update
> > >> > (if there is such an option.)
> > >> > If that doesn't give enough clues use ProcMon to supplement both
> > >> > with any interleaving registry and file accesses."
> > >> >
> > >> > That sounds like a great idea ... if only I had a clue what it all
> > >> > meant.
> > >> > It also sounds like a lot of work. In fact, resulting in an impossible
> > >> > amount for dummies like me who will surely do more damage than good.
> > >> > Those
> > >> > big words are impressive though!
> > >> >
> > >> > Microsoft needs to fix this problem and not leave it up to hamheads
> > >> > like
> > >> > me.
> > >> >
> > >> > For what it's worth, I too have this same problem & error code,
> > >> > regardless
> > >> > of updating via the Vista updates or the nVidia site. In both cases,
> > >> > the
> > >> > same thing happens. The driver installation goes seemingly smooth
> > >> > right
> > >> > through the last screen that prompts a restart. During the restart,
> > >> > Vista
> > >> > appears to load in a normal manner up to the point where (I think) it
> > >> > switches away from the base VGA drivers to the installed ones. The
> > >> > monitor
> > >> > will briefly flash a blue screen with the monitor throwing up the usual
> > >> > "no
> > >> > video input" message. This only lasts a second or two then the screen
> > >> > goes
> > >> > black (not from the monitor turning off ... just a black screen). The
> > >> > black
> > >> > screen stays that way FOREVER, and while waiting, I saw that the hard
> > >> > drive
> > >> > remained active doing who-knows-what (I finally gave up after waiting
> > >> > 12
> > >> > hours). The system never really "locked up" it seemed. And the hard
> > >> > drive
> > >> > activity was intermittent but not following any noticeable pattern.
> > >> > The
> > >> > only
> > >> > way past this was booting to safe mode. Turning off all the
> > >> > unnecessary
> > >> > crap
> > >> > via msconfig didn't help. Any attempt to do a normal boot ended at
> > >> > exactly
> > >> > the same place and with the same unending hard drive use & lack of
> > >> > video.
> > >> >
> > >> > An nVidia tech told me to try uninstalling then reinstalling in safe
> > >> > mode
> > >> > so
> > >> > as to prevent possible corruption from all the Vista security stuff
> > >> > interfering with the installation process (which he claimed was usually
> > >> > the
> > >> > cause of driver problems when using the ones from windows updates).
> > >> > Sounded
> > >> > promising, but still no dice. Same situation when trying to boot
> > >> > normally.
> > >> > The only way around it has been to uninstall the device & drivers, then
> > >> > reinstall the old ones that the Vista installation disk had.
> > >> >
> > >> > As for the "well, if it ain't broke, don't fix it" mentality ... then
> > >> > why
> > >> > bother changing the oil in your car ... or, buying new clothes while
> > >> > growing?
> > >> > Or, in my case, why care about the fact that I have a second GeForce
> > >> > 7300
> > >> > in
> > >> > there just lounging around because I can't enable SLI with the WDDM
> > >> > drivers
> > >> > (haven't found a way anyhow .. if anyone knows I'd sure like to hear
> > >> > it).
> > >> > No, I spent way too much time & money here to stay satisfied without
> > >> > ever
> > >> > being able to update the drivers. It also wasn't something I planned
> > >> > while
> > >> > shelling out 380 clams for Vista Ultimate.
> > >> >
> > >> > So, my friends, if someone actually knows the solution to this, I'd
> > >> > sure
> > >> > appreciate the benefit of your knowledge. No guesses please ... they
> > >> > may
> > >> > be
> > >> > cheap, but there's a reason for that.
> > >> >
> > >> >
> > >> >
> > >>
> > >>
> > >>
> >
> >
> >

"JETHRO" <JETHRO@discussions.microsoft.com> wrote in message
news:23C71D47-D274-4111-A1A4-F6F454BEC6FF@microsoft.com...
> RE: "Find the code's context in the install log.
> If that doesn't give enough clues activate verbose logging for the update
> (if there is such an option.)
> If that doesn't give enough clues use ProcMon to supplement both
> with any interleaving registry and file accesses."
>
> That sounds like a great idea ... if only I had a clue what it all meant.
> It also sounds like a lot of work. In fact, resulting in an impossible
> amount for dummies like me who will surely do more damage than good. Those
> big words are impressive though!
>
> Microsoft needs to fix this problem and not leave it up to hamheads like me.


Perhaps someone who can read and understand and has the same symptoms
as you will try what I suggested and report back here. Otherwise there certainly
isn't enough information yet to even offer an explanation about them.

Hint: can't you at least search your harddrives for any files which changed
at the time of the update which contain the 80070103 code?


>
> For what it's worth, I too have this same problem & error code, regardless
> of updating via the Vista updates or the nVidia site. In both cases, the
> same thing happens. The driver installation goes seemingly smooth right
> through the last screen that prompts a restart. During the restart, Vista
> appears to load in a normal manner up to the point where (I think) it
> switches away from the base VGA drivers to the installed ones. The monitor
> will briefly flash a blue screen with the monitor throwing up the usual "no
> video input" message. This only lasts a second or two then the screen goes
> black (not from the monitor turning off ... just a black screen). The black
> screen stays that way FOREVER, and

> while waiting, I saw that the hard drive remained active doing who-knows-what

That's the sort of information that running ProcMon might help with.

> (I finally gave up after waiting 12
> hours). The system never really "locked up" it seemed. And the hard drive
> activity was intermittent but not following any noticeable pattern. The only
> way past this was booting to safe mode.

What all did you try? If you had something you could switch to which
would switch your display to a low-res mode, you might be able to get
something readable. E.g. in XP both command.exe and cmd.exe
have low-res Fullscreen modes which can be entered by pressing Alt-Enter.
Does Vista have that option? Then make sure that you have one of
those windows available to you when you get in the problem state
so you can try switching to it using Alt-Tab. E.g. perhaps your driver
is locked in that low-res mode but you don't have anything to display
in it, which the command window could then use. If you're lucky
then switching away from the low-res window to a normal Windows
display might provide an additional kick to your driver to get your
display working normally again.


> Turning off all the unnecessary crap
> via msconfig didn't help. Any attempt to do a normal boot ended at exactly
> the same place and with the same unending hard drive use & lack of video.
>
> An nVidia tech told me to try uninstalling then reinstalling in safe mode so
> as to prevent possible corruption from all the Vista security stuff
> interfering with the installation process (which he claimed was usually the
> cause of driver problems when using the ones from windows updates). Sounded
> promising, but still no dice. Same situation when trying to boot normally.
> The only way around it has been to uninstall the device & drivers, then
> reinstall the old ones that the Vista installation disk had.
>
> As for the "well, if it ain't broke, don't fix it" mentality ... then why
> bother changing the oil in your car ... or, buying new clothes while growing?
> Or, in my case, why care about the fact that I have a second GeForce 7300 in
> there just lounging around because I can't enable SLI with the WDDM drivers
> (haven't found a way anyhow .. if anyone knows I'd sure like to hear it).
> No, I spent way too much time & money here to stay satisfied without ever
> being able to update the drivers. It also wasn't something I planned while
> shelling out 380 clams for Vista Ultimate.
>
> So, my friends, if someone actually knows the solution to this, I'd sure
> appreciate the benefit of your knowledge. No guesses please ... they may be
> cheap, but there's a reason for that.

Until you can provide some details or until someone else diagnoses
the same symptoms and shares their resolution guesses are all
you are going to get.


HTH

Robert
---

RE: "Hint: can't you at least search your harddrives for any files which
changed
at the time of the update which contain the 80070103 code?"

If you mean doing a HD search for any file with the text "80070103" in them
then, yeah, sure I can. That much I know how to do, and will try. But, then
what do I do with the ones that are found? I probably won't be able to open
most of them and, even if I could, what would I be looking for? Also, I'm
expecting the there's gonna be a whole slew of them. Is there any particular
folder/path that I should focus on first?

BTW, thanks for the response and I'd also like to say that my words weren't
meant to be a jab at you. No, my frustration lies with Microsoft and nVidia
as this is such a BASIC thing, updating MB & video drivers ... with the
software being from the worlds largest software manufacturer and the
corresponding chipsets being from the worlds largest manufacturer of those.
It just doesn't add up, if you ask me. I have a much greater knowledge of
PCs than most people but far less, I'm sure, than the majority of folks in
this discussion group. I'll take all the help I can get. I just don't have
enough knowledge and time to chase down hunches.


"Robert Aldwinckle" wrote:

> "JETHRO" <JETHRO@discussions.microsoft.com> wrote in message
> news:23C71D47-D274-4111-A1A4-F6F454BEC6FF@microsoft.com...
> > RE: "Find the code's context in the install log.
> > If that doesn't give enough clues activate verbose logging for the update
> > (if there is such an option.)
> > If that doesn't give enough clues use ProcMon to supplement both
> > with any interleaving registry and file accesses."
> >
> > That sounds like a great idea ... if only I had a clue what it all meant.
> > It also sounds like a lot of work. In fact, resulting in an impossible
> > amount for dummies like me who will surely do more damage than good. Those
> > big words are impressive though!
> >
> > Microsoft needs to fix this problem and not leave it up to hamheads like me.
>
>
> Perhaps someone who can read and understand and has the same symptoms
> as you will try what I suggested and report back here. Otherwise there certainly
> isn't enough information yet to even offer an explanation about them.
>
> Hint: can't you at least search your harddrives for any files which changed
> at the time of the update which contain the 80070103 code?
>
>
> >
> > For what it's worth, I too have this same problem & error code, regardless
> > of updating via the Vista updates or the nVidia site. In both cases, the
> > same thing happens. The driver installation goes seemingly smooth right
> > through the last screen that prompts a restart. During the restart, Vista
> > appears to load in a normal manner up to the point where (I think) it
> > switches away from the base VGA drivers to the installed ones. The monitor
> > will briefly flash a blue screen with the monitor throwing up the usual "no
> > video input" message. This only lasts a second or two then the screen goes
> > black (not from the monitor turning off ... just a black screen). The black
> > screen stays that way FOREVER, and
>
> > while waiting, I saw that the hard drive remained active doing who-knows-what
>
> That's the sort of information that running ProcMon might help with.
>
> > (I finally gave up after waiting 12
> > hours). The system never really "locked up" it seemed. And the hard drive
> > activity was intermittent but not following any noticeable pattern. The only
> > way past this was booting to safe mode.
>
> What all did you try? If you had something you could switch to which
> would switch your display to a low-res mode, you might be able to get
> something readable. E.g. in XP both command.exe and cmd.exe
> have low-res Fullscreen modes which can be entered by pressing Alt-Enter.
> Does Vista have that option? Then make sure that you have one of
> those windows available to you when you get in the problem state
> so you can try switching to it using Alt-Tab. E.g. perhaps your driver
> is locked in that low-res mode but you don't have anything to display
> in it, which the command window could then use. If you're lucky
> then switching away from the low-res window to a normal Windows
> display might provide an additional kick to your driver to get your
> display working normally again.
>
>
> > Turning off all the unnecessary crap
> > via msconfig didn't help. Any attempt to do a normal boot ended at exactly
> > the same place and with the same unending hard drive use & lack of video.
> >
> > An nVidia tech told me to try uninstalling then reinstalling in safe mode so
> > as to prevent possible corruption from all the Vista security stuff
> > interfering with the installation process (which he claimed was usually the
> > cause of driver problems when using the ones from windows updates). Sounded
> > promising, but still no dice. Same situation when trying to boot normally.
> > The only way around it has been to uninstall the device & drivers, then
> > reinstall the old ones that the Vista installation disk had.
> >
> > As for the "well, if it ain't broke, don't fix it" mentality ... then why
> > bother changing the oil in your car ... or, buying new clothes while growing?
> > Or, in my case, why care about the fact that I have a second GeForce 7300 in
> > there just lounging around because I can't enable SLI with the WDDM drivers
> > (haven't found a way anyhow .. if anyone knows I'd sure like to hear it).
> > No, I spent way too much time & money here to stay satisfied without ever
> > being able to update the drivers. It also wasn't something I planned while
> > shelling out 380 clams for Vista Ultimate.
> >
> > So, my friends, if someone actually knows the solution to this, I'd sure
> > appreciate the benefit of your knowledge. No guesses please ... they may be
> > cheap, but there's a reason for that.
>
> Until you can provide some details or until someone else diagnoses
> the same symptoms and shares their resolution guesses are all
> you are going to get.
>
>
> HTH
>
> Robert
> ---
>
>
>

"JETHRO" <JETHRO@discussions.microsoft.com> wrote in message
news:4C9E755C-52AB-4061-9764-AC5ACEF4E4F9@microsoft.com...
> RE: "Hint: can't you at least search your harddrives for any files which
> changed
> at the time of the update which contain the 80070103 code?"
>
> If you mean doing a HD search for any file with the text "80070103" in them
> then, yeah, sure I can.


Note the second search criterion I suggested: "which changed at the time of
the update". Hint: if your search tool does not support that fine a search,
e.g. it only provides a search by date, get a list of the files on the day of the
update, then sort them by Date Modified. Doing that should order them
by their timestamps, so then you can scroll to the particular minute(s) that
the update was run.


> That much I know how to do, and will try. But, then
> what do I do with the ones that are found?

Try to find ones which seem readable.

> I probably won't be able to open most of them

Hint: you can open *any* file by dragging it to an open Notepad window.

> and, even if I could, what would I be looking for?

Files that looked as if they were meant to be read by humans. ; }

> Also, I'm expecting the there's gonna be a whole slew of them.

I'm not. ; )

> Is there any particular folder/path that I should focus on first?

I have no idea, I don't have your OS, or that particular video card.
However, frequently updates often create a log file which contains
their update name as the file name and .log as their extension.


>
> BTW, thanks for the response and I'd also like to say that my words weren't
> meant to be a jab at you. No, my frustration lies with Microsoft and nVidia
> as this is such a BASIC thing, updating MB & video drivers ... with the
> software being from the worlds largest software manufacturer and the
> corresponding chipsets being from the worlds largest manufacturer of those.
> It just doesn't add up, if you ask me. I have a much greater knowledge of
> PCs than most people but far less, I'm sure, than the majority of folks in
> this discussion group. I'll take all the help I can get. I just don't have
> enough knowledge and time to chase down hunches.


This shouldn't take you long and will be good practice for other troubleshooting
efforts you will undoubtedly need to take part in from time to time, if you are
doing self-support of your PC.


Good luck

Robert
---