🚀 go-pugleaf

I had the same thing when palying RtCW.  Rebooted and uninstalled 21.83, but
the game won't play using the default XP driver (an older version of Detonador).


Hong Ooi wrote:

> Failing to leave well enough alone, I decided to try out the new Nvidia
> 23.11 Detonators on my XP Pro box. Up to this point, using the 21.83
> drivers, my system had been quite stable, without any major hangups. After
> installing the new drivers, I got the dreaded infinite loop BSOD in
> nv4_disp.dll on running 3dmark2001.
>
> I tried to roll back the drivers to the previous version, but there were
> still some remnants behind. So I deleted all the drivers and rebooted, upon
> which XP redetected the video card and reinstalled the 21.83 drivers from
> scratch.
>
> The problem now is that whenever I login as admin, I get a dialog box
> saying that "Windows has recovered from a serious error", and offering to
> send the dump info to MS. There is also the following entry in the system
> event log:
>
>
> Event Type:   Error
> Event Source: System Error
> Event Category:       (102)
> Event ID:     1003
> Date:         4/12/2001
> Time:         11:28:37 PM
> User:         N/A
> Computer:     C3Y9M9
> Description:
> Error code 100000ea, parameter1 816ab648, parameter2 81696cd8, parameter3
> 823d1510, parameter4 00000001.
>
>
> I only get this error when I login as admin, not as my usual userid.
> Everything still seems to run fine, however the refresh rate fix to enable
> rates above 60Hz doesn't work anymore.
>
> What does this error mean, and how do I fix it? I've already tried going
> back to a system restore point, but Windows said it was unsuccessful and
> didn't change anything. Argh.
>
>
> System specs:
> AMD Athlon 1.33GHz (not overclocked in any way)
> MSI MS-6341 mobo, with 512MB RAM
> Asus V7700 Deluxe Geforce2 GTS, 32MB
> Hercules GTXP, with the 6.1 drivers
> AOpen AON-325 NIC (Realtek chip)
> IBM 60GXP 40GB hard disk
> Pioneer DVD-105 DVD drive
> Ricoh MP-7125A CDRW
>
>

I have an intel MB and I still have to find a working XPdriver for my
GForce2.

"Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
news:sm7P7.581$m5.125759@news11-gui.server.ntli.net...
> Take a look, everyone with the AMD/Via chipset has Infinate_Loop errors,
> everyone with Intel chipsets/CPU's does not.
>
> Work it out.....
>
>

Asus A7V-133 + Athlon 1.2 gig (overclocked to 1.4gig) + Via 4in1 4.35
drivers = NO PROBLEM.

He who makes blanket statements is a fool!

"Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
news:sm7P7.581$m5.125759@news11-gui.server.ntli.net...
> Take a look, everyone with the AMD/Via chipset has Infinate_Loop errors,
> everyone with Intel chipsets/CPU's does not.
>
> Work it out.....
>
>
>
>
> "Hong Ooi" <hong.ooi@maths.anu.edu.au> wrote in message
> news:achp0us61k469htqu233qnjtfkgi567s74@4ax.com...
> > Failing to leave well enough alone, I decided to try out the new Nvidia
> > 23.11 Detonators on my XP Pro box. Up to this point, using the 21.83
> > drivers, my system had been quite stable, without any major hangups.
After
> > installing the new drivers, I got the dreaded infinite loop BSOD in
> > nv4_disp.dll on running 3dmark2001.
> >
> > I tried to roll back the drivers to the previous version, but there were
> > still some remnants behind. So I deleted all the drivers and rebooted,
> upon
> > which XP redetected the video card and reinstalled the 21.83 drivers
from
> > scratch.
> >
> > The problem now is that whenever I login as admin, I get a dialog box
> > saying that "Windows has recovered from a serious error", and offering
to
> > send the dump info to MS. There is also the following entry in the
system
> > event log:
> >
> >
> > Event Type: Error
> > Event Source: System Error
> > Event Category: (102)
> > Event ID: 1003
> > Date: 4/12/2001
> > Time: 11:28:37 PM
> > User: N/A
> > Computer: C3Y9M9
> > Description:
> > Error code 100000ea, parameter1 816ab648, parameter2 81696cd8,
parameter3
> > 823d1510, parameter4 00000001.
> >
> >
> > I only get this error when I login as admin, not as my usual userid.
> > Everything still seems to run fine, however the refresh rate fix to
enable
> > rates above 60Hz doesn't work anymore.
> >
> > What does this error mean, and how do I fix it? I've already tried going
> > back to a system restore point, but Windows said it was unsuccessful and
> > didn't change anything. Argh.
> >
> >
> > System specs:
> > AMD Athlon 1.33GHz (not overclocked in any way)
> > MSI MS-6341 mobo, with 512MB RAM
> > Asus V7700 Deluxe Geforce2 GTS, 32MB
> > Hercules GTXP, with the 6.1 drivers
> > AOpen AON-325 NIC (Realtek chip)
> > IBM 60GXP 40GB hard disk
> > Pioneer DVD-105 DVD drive
> > Ricoh MP-7125A CDRW
> >
> >
> > --
> > Hong Ooi                    | "You are inundated with SQUARES!"
> > hong.ooi@maths.anu.edu.au   |    -- JEM
> > http://www.zip.com.au/~hong |
> > Canberra, Australia         |
>
>

IMHO Intel chipsets are the worst out there(especially the old bx chipset).
Yes they work fine, it's just my opinion. I'm running a Intel 1ghz PIII with
Via Apollo Pro 133 and eveything is fine(not even the most recent 4 in 1
drivers). I've had 2 crashes running XP since july and right now I don't
have one problem with XP at all.

Phil


"Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
news:au8P7.2697$J42.568579@news6-win.server.ntlworld.com...
>
> "Richard Urban" <rurban@frontiernet.net> wrote in message
> news:udbI37OfBHA.1628@tkmsftngp03...
> > Asus A7V-133 + Athlon 1.2 gig (overclocked to 1.4gig) + Via 4in1 4.35
> > drivers = NO PROBLEM.
> >
> > He who makes blanket statements is a fool!
>
> What that should have said was
>
> "Take a look, anyone with the AMD/Via chipset may have Infinate_Loop
errors,
> everyone with Intel chipsets/CPU's will not.  Work it out....."
>
> Agreed not all Via/AMD systems will exhibt this fault, but those that do
> will be Via/AMD.  Intel chipsets do not suffer from this problem.
>
>
>
> > "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> > news:sm7P7.581$m5.125759@news11-gui.server.ntli.net...
> > > Take a look, everyone with the AMD/Via chipset has Infinate_Loop
errors,
> > > everyone with Intel chipsets/CPU's does not.
> > >
> > > Work it out.....
> > >
> > >
> > >
> > >
> > > "Hong Ooi" <hong.ooi@maths.anu.edu.au> wrote in message
> > > news:achp0us61k469htqu233qnjtfkgi567s74@4ax.com...
> > > > Failing to leave well enough alone, I decided to try out the new
> Nvidia
> > > > 23.11 Detonators on my XP Pro box. Up to this point, using the 21.83
> > > > drivers, my system had been quite stable, without any major hangups.
> > After
> > > > installing the new drivers, I got the dreaded infinite loop BSOD in
> > > > nv4_disp.dll on running 3dmark2001.
> > > >
> > > > I tried to roll back the drivers to the previous version, but there
> were
> > > > still some remnants behind. So I deleted all the drivers and
rebooted,
> > > upon
> > > > which XP redetected the video card and reinstalled the 21.83 drivers
> > from
> > > > scratch.
> > > >
> > > > The problem now is that whenever I login as admin, I get a dialog
box
> > > > saying that "Windows has recovered from a serious error", and
offering
> > to
> > > > send the dump info to MS. There is also the following entry in the
> > system
> > > > event log:
> > > >
> > > >
> > > > Event Type: Error
> > > > Event Source: System Error
> > > > Event Category: (102)
> > > > Event ID: 1003
> > > > Date: 4/12/2001
> > > > Time: 11:28:37 PM
> > > > User: N/A
> > > > Computer: C3Y9M9
> > > > Description:
> > > > Error code 100000ea, parameter1 816ab648, parameter2 81696cd8,
> > parameter3
> > > > 823d1510, parameter4 00000001.
> > > >
> > > >
> > > > I only get this error when I login as admin, not as my usual userid.
> > > > Everything still seems to run fine, however the refresh rate fix to
> > enable
> > > > rates above 60Hz doesn't work anymore.
> > > >
> > > > What does this error mean, and how do I fix it? I've already tried
> going
> > > > back to a system restore point, but Windows said it was unsuccessful
> and
> > > > didn't change anything. Argh.
> > > >
> > > >
> > > > System specs:
> > > > AMD Athlon 1.33GHz (not overclocked in any way)
> > > > MSI MS-6341 mobo, with 512MB RAM
> > > > Asus V7700 Deluxe Geforce2 GTS, 32MB
> > > > Hercules GTXP, with the 6.1 drivers
> > > > AOpen AON-325 NIC (Realtek chip)
> > > > IBM 60GXP 40GB hard disk
> > > > Pioneer DVD-105 DVD drive
> > > > Ricoh MP-7125A CDRW
> > > >
> > > >
> > > > --
> > > > Hong Ooi                    | "You are inundated with SQUARES!"
> > > > hong.ooi@maths.anu.edu.au   |    -- JEM
> > > > http://www.zip.com.au/~hong |
> > > > Canberra, Australia         |
> > >
> > >
> >
> >
>
>

> IMHO Intel chipsets are the worst out there(especially the old bx
chipset).

Then what is your basis for saying they're bad?  I read on here about
problem after problem people are having with VIA.  By and large, I'm sure
they're fine, but they are certainly over represented here.  Also, the 440BX
chipset was and one of the most reliable, hassle free chipsets available.  I
have it and have never had any issues.

"pc2k" <none@none.com> wrote in message news:#YN5cVPfBHA.816@tkmsftngp05...
> IMHO Intel chipsets are the worst out there(especially the old bx
chipset).
> Yes they work fine, it's just my opinion. I'm running a Intel 1ghz PIII
with
> Via Apollo Pro 133 and eveything is fine(not even the most recent 4 in 1
> drivers). I've had 2 crashes running XP since july and right now I don't
> have one problem with XP at all.
>
> Phil
>
>
> "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> news:au8P7.2697$J42.568579@news6-win.server.ntlworld.com...
> >
> > "Richard Urban" <rurban@frontiernet.net> wrote in message
> > news:udbI37OfBHA.1628@tkmsftngp03...
> > > Asus A7V-133 + Athlon 1.2 gig (overclocked to 1.4gig) + Via 4in1 4.35
> > > drivers = NO PROBLEM.
> > >
> > > He who makes blanket statements is a fool!
> >
> > What that should have said was
> >
> > "Take a look, anyone with the AMD/Via chipset may have Infinate_Loop
> errors,
> > everyone with Intel chipsets/CPU's will not.  Work it out....."
> >
> > Agreed not all Via/AMD systems will exhibt this fault, but those that do
> > will be Via/AMD.  Intel chipsets do not suffer from this problem.
> >
> >
> >
> > > "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> > > news:sm7P7.581$m5.125759@news11-gui.server.ntli.net...
> > > > Take a look, everyone with the AMD/Via chipset has Infinate_Loop
> errors,
> > > > everyone with Intel chipsets/CPU's does not.
> > > >
> > > > Work it out.....
> > > >
> > > >
> > > >
> > > >
> > > > "Hong Ooi" <hong.ooi@maths.anu.edu.au> wrote in message
> > > > news:achp0us61k469htqu233qnjtfkgi567s74@4ax.com...
> > > > > Failing to leave well enough alone, I decided to try out the new
> > Nvidia
> > > > > 23.11 Detonators on my XP Pro box. Up to this point, using the
21.83
> > > > > drivers, my system had been quite stable, without any major
hangups.
> > > After
> > > > > installing the new drivers, I got the dreaded infinite loop BSOD
in
> > > > > nv4_disp.dll on running 3dmark2001.
> > > > >
> > > > > I tried to roll back the drivers to the previous version, but
there
> > were
> > > > > still some remnants behind. So I deleted all the drivers and
> rebooted,
> > > > upon
> > > > > which XP redetected the video card and reinstalled the 21.83
drivers
> > > from
> > > > > scratch.
> > > > >
> > > > > The problem now is that whenever I login as admin, I get a dialog
> box
> > > > > saying that "Windows has recovered from a serious error", and
> offering
> > > to
> > > > > send the dump info to MS. There is also the following entry in the
> > > system
> > > > > event log:
> > > > >
> > > > >
> > > > > Event Type: Error
> > > > > Event Source: System Error
> > > > > Event Category: (102)
> > > > > Event ID: 1003
> > > > > Date: 4/12/2001
> > > > > Time: 11:28:37 PM
> > > > > User: N/A
> > > > > Computer: C3Y9M9
> > > > > Description:
> > > > > Error code 100000ea, parameter1 816ab648, parameter2 81696cd8,
> > > parameter3
> > > > > 823d1510, parameter4 00000001.
> > > > >
> > > > >
> > > > > I only get this error when I login as admin, not as my usual
userid.
> > > > > Everything still seems to run fine, however the refresh rate fix
to
> > > enable
> > > > > rates above 60Hz doesn't work anymore.
> > > > >
> > > > > What does this error mean, and how do I fix it? I've already tried
> > going
> > > > > back to a system restore point, but Windows said it was
unsuccessful
> > and
> > > > > didn't change anything. Argh.
> > > > >
> > > > >
> > > > > System specs:
> > > > > AMD Athlon 1.33GHz (not overclocked in any way)
> > > > > MSI MS-6341 mobo, with 512MB RAM
> > > > > Asus V7700 Deluxe Geforce2 GTS, 32MB
> > > > > Hercules GTXP, with the 6.1 drivers
> > > > > AOpen AON-325 NIC (Realtek chip)
> > > > > IBM 60GXP 40GB hard disk
> > > > > Pioneer DVD-105 DVD drive
> > > > > Ricoh MP-7125A CDRW
> > > > >
> > > > >
> > > > > --
> > > > > Hong Ooi                    | "You are inundated with SQUARES!"
> > > > > hong.ooi@maths.anu.edu.au   |    -- JEM
> > > > > http://www.zip.com.au/~hong |
> > > > > Canberra, Australia         |
> > > >
> > > >
> > >
> > >
> >
> >
>
>

There is this detonatordestroyer.zip file at nvdia you can download. It
really clears out all traces of nvidia drivers, including registry entries.
Than install a standard VGA device
Reboot and install the detonator drivers.

"Hong Ooi" <hong.ooi@maths.anu.edu.au> schrieb im Newsbeitrag
news:achp0us61k469htqu233qnjtfkgi567s74@4ax.com...
> Failing to leave well enough alone, I decided to try out the new Nvidia
> 23.11 Detonators on my XP Pro box. Up to this point, using the 21.83
> drivers, my system had been quite stable, without any major hangups. After
> installing the new drivers, I got the dreaded infinite loop BSOD in
> nv4_disp.dll on running 3dmark2001.
>
> I tried to roll back the drivers to the previous version, but there were
> still some remnants behind. So I deleted all the drivers and rebooted,
upon
> which XP redetected the video card and reinstalled the 21.83 drivers from
> scratch.
>
> The problem now is that whenever I login as admin, I get a dialog box
> saying that "Windows has recovered from a serious error", and offering to
> send the dump info to MS. There is also the following entry in the system
> event log:
>
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 4/12/2001
> Time: 11:28:37 PM
> User: N/A
> Computer: C3Y9M9
> Description:
> Error code 100000ea, parameter1 816ab648, parameter2 81696cd8, parameter3
> 823d1510, parameter4 00000001.
>
>
> I only get this error when I login as admin, not as my usual userid.
> Everything still seems to run fine, however the refresh rate fix to enable
> rates above 60Hz doesn't work anymore.
>
> What does this error mean, and how do I fix it? I've already tried going
> back to a system restore point, but Windows said it was unsuccessful and
> didn't change anything. Argh.
>
>
> System specs:
> AMD Athlon 1.33GHz (not overclocked in any way)
> MSI MS-6341 mobo, with 512MB RAM
> Asus V7700 Deluxe Geforce2 GTS, 32MB
> Hercules GTXP, with the 6.1 drivers
> AOpen AON-325 NIC (Realtek chip)
> IBM 60GXP 40GB hard disk
> Pioneer DVD-105 DVD drive
> Ricoh MP-7125A CDRW
>
>
> --
> Hong Ooi                    | "You are inundated with SQUARES!"
> hong.ooi@maths.anu.edu.au   |    -- JEM
> http://www.zip.com.au/~hong |
> Canberra, Australia         |

Take a look, everyone with the AMD/Via chipset has Infinate_Loop errors,
everyone with Intel chipsets/CPU's does not.

Work it out.....




"Hong Ooi" <hong.ooi@maths.anu.edu.au> wrote in message
news:achp0us61k469htqu233qnjtfkgi567s74@4ax.com...
> Failing to leave well enough alone, I decided to try out the new Nvidia
> 23.11 Detonators on my XP Pro box. Up to this point, using the 21.83
> drivers, my system had been quite stable, without any major hangups. After
> installing the new drivers, I got the dreaded infinite loop BSOD in
> nv4_disp.dll on running 3dmark2001.
>
> I tried to roll back the drivers to the previous version, but there were
> still some remnants behind. So I deleted all the drivers and rebooted,
upon
> which XP redetected the video card and reinstalled the 21.83 drivers from
> scratch.
>
> The problem now is that whenever I login as admin, I get a dialog box
> saying that "Windows has recovered from a serious error", and offering to
> send the dump info to MS. There is also the following entry in the system
> event log:
>
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 4/12/2001
> Time: 11:28:37 PM
> User: N/A
> Computer: C3Y9M9
> Description:
> Error code 100000ea, parameter1 816ab648, parameter2 81696cd8, parameter3
> 823d1510, parameter4 00000001.
>
>
> I only get this error when I login as admin, not as my usual userid.
> Everything still seems to run fine, however the refresh rate fix to enable
> rates above 60Hz doesn't work anymore.
>
> What does this error mean, and how do I fix it? I've already tried going
> back to a system restore point, but Windows said it was unsuccessful and
> didn't change anything. Argh.
>
>
> System specs:
> AMD Athlon 1.33GHz (not overclocked in any way)
> MSI MS-6341 mobo, with 512MB RAM
> Asus V7700 Deluxe Geforce2 GTS, 32MB
> Hercules GTXP, with the 6.1 drivers
> AOpen AON-325 NIC (Realtek chip)
> IBM 60GXP 40GB hard disk
> Pioneer DVD-105 DVD drive
> Ricoh MP-7125A CDRW
>
>
> --
> Hong Ooi                    | "You are inundated with SQUARES!"
> hong.ooi@maths.anu.edu.au   |    -- JEM
> http://www.zip.com.au/~hong |
> Canberra, Australia         |

"Richard Urban" <rurban@frontiernet.net> wrote in message
news:udbI37OfBHA.1628@tkmsftngp03...
> Asus A7V-133 + Athlon 1.2 gig (overclocked to 1.4gig) + Via 4in1 4.35
> drivers = NO PROBLEM.
>
> He who makes blanket statements is a fool!

What that should have said was

"Take a look, anyone with the AMD/Via chipset may have Infinate_Loop errors,
everyone with Intel chipsets/CPU's will not.  Work it out....."

Agreed not all Via/AMD systems will exhibt this fault, but those that do
will be Via/AMD.  Intel chipsets do not suffer from this problem.



> "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> news:sm7P7.581$m5.125759@news11-gui.server.ntli.net...
> > Take a look, everyone with the AMD/Via chipset has Infinate_Loop errors,
> > everyone with Intel chipsets/CPU's does not.
> >
> > Work it out.....
> >
> >
> >
> >
> > "Hong Ooi" <hong.ooi@maths.anu.edu.au> wrote in message
> > news:achp0us61k469htqu233qnjtfkgi567s74@4ax.com...
> > > Failing to leave well enough alone, I decided to try out the new
Nvidia
> > > 23.11 Detonators on my XP Pro box. Up to this point, using the 21.83
> > > drivers, my system had been quite stable, without any major hangups.
> After
> > > installing the new drivers, I got the dreaded infinite loop BSOD in
> > > nv4_disp.dll on running 3dmark2001.
> > >
> > > I tried to roll back the drivers to the previous version, but there
were
> > > still some remnants behind. So I deleted all the drivers and rebooted,
> > upon
> > > which XP redetected the video card and reinstalled the 21.83 drivers
> from
> > > scratch.
> > >
> > > The problem now is that whenever I login as admin, I get a dialog box
> > > saying that "Windows has recovered from a serious error", and offering
> to
> > > send the dump info to MS. There is also the following entry in the
> system
> > > event log:
> > >
> > >
> > > Event Type: Error
> > > Event Source: System Error
> > > Event Category: (102)
> > > Event ID: 1003
> > > Date: 4/12/2001
> > > Time: 11:28:37 PM
> > > User: N/A
> > > Computer: C3Y9M9
> > > Description:
> > > Error code 100000ea, parameter1 816ab648, parameter2 81696cd8,
> parameter3
> > > 823d1510, parameter4 00000001.
> > >
> > >
> > > I only get this error when I login as admin, not as my usual userid.
> > > Everything still seems to run fine, however the refresh rate fix to
> enable
> > > rates above 60Hz doesn't work anymore.
> > >
> > > What does this error mean, and how do I fix it? I've already tried
going
> > > back to a system restore point, but Windows said it was unsuccessful
and
> > > didn't change anything. Argh.
> > >
> > >
> > > System specs:
> > > AMD Athlon 1.33GHz (not overclocked in any way)
> > > MSI MS-6341 mobo, with 512MB RAM
> > > Asus V7700 Deluxe Geforce2 GTS, 32MB
> > > Hercules GTXP, with the 6.1 drivers
> > > AOpen AON-325 NIC (Realtek chip)
> > > IBM 60GXP 40GB hard disk
> > > Pioneer DVD-105 DVD drive
> > > Ricoh MP-7125A CDRW
> > >
> > >
> > > --
> > > Hong Ooi                    | "You are inundated with SQUARES!"
> > > hong.ooi@maths.anu.edu.au   |    -- JEM
> > > http://www.zip.com.au/~hong |
> > > Canberra, Australia         |
> >
> >
>
>

"Richard Urban" <rurban@frontiernet.net> wrote in message
news:udbI37OfBHA.1628@tkmsftngp03...
> Asus A7V-133 + Athlon 1.2 gig (overclocked to 1.4gig) + Via 4in1 4.35
> drivers = NO PROBLEM.
>
> (He who makes blanket statements is a fool!) <= Blanket Statement!!!
>
> "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> news:sm7P7.581$m5.125759@news11-gui.server.ntli.net...
> > Take a look, everyone with the AMD/Via chipset has Infinate_Loop errors,
> > everyone with Intel chipsets/CPU's does not.
> >
> > Work it out.....
> >
> >
> >
> >
> > "Hong Ooi" <hong.ooi@maths.anu.edu.au> wrote in message
> > news:achp0us61k469htqu233qnjtfkgi567s74@4ax.com...
> > > Failing to leave well enough alone, I decided to try out the new
Nvidia
> > > 23.11 Detonators on my XP Pro box. Up to this point, using the 21.83
> > > drivers, my system had been quite stable, without any major hangups.
> After
> > > installing the new drivers, I got the dreaded infinite loop BSOD in
> > > nv4_disp.dll on running 3dmark2001.
> > >
> > > I tried to roll back the drivers to the previous version, but there
were
> > > still some remnants behind. So I deleted all the drivers and rebooted,
> > upon
> > > which XP redetected the video card and reinstalled the 21.83 drivers
> from
> > > scratch.
> > >
> > > The problem now is that whenever I login as admin, I get a dialog box
> > > saying that "Windows has recovered from a serious error", and offering
> to
> > > send the dump info to MS. There is also the following entry in the
> system
> > > event log:
> > >
> > >
> > > Event Type: Error
> > > Event Source: System Error
> > > Event Category: (102)
> > > Event ID: 1003
> > > Date: 4/12/2001
> > > Time: 11:28:37 PM
> > > User: N/A
> > > Computer: C3Y9M9
> > > Description:
> > > Error code 100000ea, parameter1 816ab648, parameter2 81696cd8,
> parameter3
> > > 823d1510, parameter4 00000001.
> > >
> > >
> > > I only get this error when I login as admin, not as my usual userid.
> > > Everything still seems to run fine, however the refresh rate fix to
> enable
> > > rates above 60Hz doesn't work anymore.
> > >
> > > What does this error mean, and how do I fix it? I've already tried
going
> > > back to a system restore point, but Windows said it was unsuccessful
and
> > > didn't change anything. Argh.
> > >
> > >
> > > System specs:
> > > AMD Athlon 1.33GHz (not overclocked in any way)
> > > MSI MS-6341 mobo, with 512MB RAM
> > > Asus V7700 Deluxe Geforce2 GTS, 32MB
> > > Hercules GTXP, with the 6.1 drivers
> > > AOpen AON-325 NIC (Realtek chip)
> > > IBM 60GXP 40GB hard disk
> > > Pioneer DVD-105 DVD drive
> > > Ricoh MP-7125A CDRW
> > >
> > >
> > > --
> > > Hong Ooi                    | "You are inundated with SQUARES!"
> > > hong.ooi@maths.anu.edu.au   |    -- JEM
> > > http://www.zip.com.au/~hong |
> > > Canberra, Australia         |
> >
> >
>
>
>

There ia a APG driver that's newer than what was provided in 4.35

"Richard Urban" <rurban@frontiernet.net> wrote in message
news:udbI37OfBHA.1628@tkmsftngp03...
> Asus A7V-133 + Athlon 1.2 gig (overclocked to 1.4gig) + Via 4in1 4.35
> drivers = NO PROBLEM.
>
> He who makes blanket statements is a fool!
>
> "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> news:sm7P7.581$m5.125759@news11-gui.server.ntli.net...
> > Take a look, everyone with the AMD/Via chipset has Infinate_Loop errors,
> > everyone with Intel chipsets/CPU's does not.
> >
> > Work it out.....
> >
> >
> >
> >
> > "Hong Ooi" <hong.ooi@maths.anu.edu.au> wrote in message
> > news:achp0us61k469htqu233qnjtfkgi567s74@4ax.com...
> > > Failing to leave well enough alone, I decided to try out the new
Nvidia
> > > 23.11 Detonators on my XP Pro box. Up to this point, using the 21.83
> > > drivers, my system had been quite stable, without any major hangups.
> After
> > > installing the new drivers, I got the dreaded infinite loop BSOD in
> > > nv4_disp.dll on running 3dmark2001.
> > >
> > > I tried to roll back the drivers to the previous version, but there
were
> > > still some remnants behind. So I deleted all the drivers and rebooted,
> > upon
> > > which XP redetected the video card and reinstalled the 21.83 drivers
> from
> > > scratch.
> > >
> > > The problem now is that whenever I login as admin, I get a dialog box
> > > saying that "Windows has recovered from a serious error", and offering
> to
> > > send the dump info to MS. There is also the following entry in the
> system
> > > event log:
> > >
> > >
> > > Event Type: Error
> > > Event Source: System Error
> > > Event Category: (102)
> > > Event ID: 1003
> > > Date: 4/12/2001
> > > Time: 11:28:37 PM
> > > User: N/A
> > > Computer: C3Y9M9
> > > Description:
> > > Error code 100000ea, parameter1 816ab648, parameter2 81696cd8,
> parameter3
> > > 823d1510, parameter4 00000001.
> > >
> > >
> > > I only get this error when I login as admin, not as my usual userid.
> > > Everything still seems to run fine, however the refresh rate fix to
> enable
> > > rates above 60Hz doesn't work anymore.
> > >
> > > What does this error mean, and how do I fix it? I've already tried
going
> > > back to a system restore point, but Windows said it was unsuccessful
and
> > > didn't change anything. Argh.
> > >
> > >
> > > System specs:
> > > AMD Athlon 1.33GHz (not overclocked in any way)
> > > MSI MS-6341 mobo, with 512MB RAM
> > > Asus V7700 Deluxe Geforce2 GTS, 32MB
> > > Hercules GTXP, with the 6.1 drivers
> > > AOpen AON-325 NIC (Realtek chip)
> > > IBM 60GXP 40GB hard disk
> > > Pioneer DVD-105 DVD drive
> > > Ricoh MP-7125A CDRW
> > >
> > >
> > > --
> > > Hong Ooi                    | "You are inundated with SQUARES!"
> > > hong.ooi@maths.anu.edu.au   |    -- JEM
> > > http://www.zip.com.au/~hong |
> > > Canberra, Australia         |
> >
> >
>
>
>

"pc2k" <none@none.com> wrote in message news:#YN5cVPfBHA.816@tkmsftngp05...
> IMHO Intel chipsets are the worst out there(especially the old bx
chipset).
> Yes they work fine, it's just my opinion. I'm running a Intel 1ghz PIII
with

They work fine, but they are the worst???

Got me!  (o:

"RL" <rlaingDELETE@cfl.rr.com> wrote in message
news:op8P7.197203$zK1.51458908@typhoon.tampabay.rr.com...
>
> "Richard Urban" <rurban@frontiernet.net> wrote in message
> news:udbI37OfBHA.1628@tkmsftngp03...
> > Asus A7V-133 + Athlon 1.2 gig (overclocked to 1.4gig) + Via 4in1 4.35
> > drivers = NO PROBLEM.
> >
> > (He who makes blanket statements is a fool!) <= Blanket Statement!!!
> >
> > "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> > news:sm7P7.581$m5.125759@news11-gui.server.ntli.net...
> > > Take a look, everyone with the AMD/Via chipset has Infinate_Loop
errors,
> > > everyone with Intel chipsets/CPU's does not.
> > >
> > > Work it out.....
> > >
> > >
> > >
> > >
> > > "Hong Ooi" <hong.ooi@maths.anu.edu.au> wrote in message
> > > news:achp0us61k469htqu233qnjtfkgi567s74@4ax.com...
> > > > Failing to leave well enough alone, I decided to try out the new
> Nvidia
> > > > 23.11 Detonators on my XP Pro box. Up to this point, using the 21.83
> > > > drivers, my system had been quite stable, without any major hangups.
> > After
> > > > installing the new drivers, I got the dreaded infinite loop BSOD in
> > > > nv4_disp.dll on running 3dmark2001.
> > > >
> > > > I tried to roll back the drivers to the previous version, but there
> were
> > > > still some remnants behind. So I deleted all the drivers and
rebooted,
> > > upon
> > > > which XP redetected the video card and reinstalled the 21.83 drivers
> > from
> > > > scratch.
> > > >
> > > > The problem now is that whenever I login as admin, I get a dialog
box
> > > > saying that "Windows has recovered from a serious error", and
offering
> > to
> > > > send the dump info to MS. There is also the following entry in the
> > system
> > > > event log:
> > > >
> > > >
> > > > Event Type: Error
> > > > Event Source: System Error
> > > > Event Category: (102)
> > > > Event ID: 1003
> > > > Date: 4/12/2001
> > > > Time: 11:28:37 PM
> > > > User: N/A
> > > > Computer: C3Y9M9
> > > > Description:
> > > > Error code 100000ea, parameter1 816ab648, parameter2 81696cd8,
> > parameter3
> > > > 823d1510, parameter4 00000001.
> > > >
> > > >
> > > > I only get this error when I login as admin, not as my usual userid.
> > > > Everything still seems to run fine, however the refresh rate fix to
> > enable
> > > > rates above 60Hz doesn't work anymore.
> > > >
> > > > What does this error mean, and how do I fix it? I've already tried
> going
> > > > back to a system restore point, but Windows said it was unsuccessful
> and
> > > > didn't change anything. Argh.
> > > >
> > > >
> > > > System specs:
> > > > AMD Athlon 1.33GHz (not overclocked in any way)
> > > > MSI MS-6341 mobo, with 512MB RAM
> > > > Asus V7700 Deluxe Geforce2 GTS, 32MB
> > > > Hercules GTXP, with the 6.1 drivers
> > > > AOpen AON-325 NIC (Realtek chip)
> > > > IBM 60GXP 40GB hard disk
> > > > Pioneer DVD-105 DVD drive
> > > > Ricoh MP-7125A CDRW
> > > >
> > > >
> > > > --
> > > > Hong Ooi                    | "You are inundated with SQUARES!"
> > > > hong.ooi@maths.anu.edu.au   |    -- JEM
> > > > http://www.zip.com.au/~hong |
> > > > Canberra, Australia         |
> > >
> > >
> >
> >
> >
>
>

I had no problems with the 21.83, except for 1 crash, which I cannot say for
sure was caused by it, and I am also having no issues with 21.83.  I have a
Intel 440BX mobo with an old GeForce 256 card.

"Hong Ooi" <hong.ooi@maths.anu.edu.au> wrote in message
news:achp0us61k469htqu233qnjtfkgi567s74@4ax.com...
> Failing to leave well enough alone, I decided to try out the new Nvidia
> 23.11 Detonators on my XP Pro box. Up to this point, using the 21.83
> drivers, my system had been quite stable, without any major hangups. After
> installing the new drivers, I got the dreaded infinite loop BSOD in
> nv4_disp.dll on running 3dmark2001.
>
> I tried to roll back the drivers to the previous version, but there were
> still some remnants behind. So I deleted all the drivers and rebooted,
upon
> which XP redetected the video card and reinstalled the 21.83 drivers from
> scratch.
>
> The problem now is that whenever I login as admin, I get a dialog box
> saying that "Windows has recovered from a serious error", and offering to
> send the dump info to MS. There is also the following entry in the system
> event log:
>
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 4/12/2001
> Time: 11:28:37 PM
> User: N/A
> Computer: C3Y9M9
> Description:
> Error code 100000ea, parameter1 816ab648, parameter2 81696cd8, parameter3
> 823d1510, parameter4 00000001.
>
>
> I only get this error when I login as admin, not as my usual userid.
> Everything still seems to run fine, however the refresh rate fix to enable
> rates above 60Hz doesn't work anymore.
>
> What does this error mean, and how do I fix it? I've already tried going
> back to a system restore point, but Windows said it was unsuccessful and
> didn't change anything. Argh.
>
>
> System specs:
> AMD Athlon 1.33GHz (not overclocked in any way)
> MSI MS-6341 mobo, with 512MB RAM
> Asus V7700 Deluxe Geforce2 GTS, 32MB
> Hercules GTXP, with the 6.1 drivers
> AOpen AON-325 NIC (Realtek chip)
> IBM 60GXP 40GB hard disk
> Pioneer DVD-105 DVD drive
> Ricoh MP-7125A CDRW
>
>
> --
> Hong Ooi                    | "You are inundated with SQUARES!"
> hong.ooi@maths.anu.edu.au   |    -- JEM
> http://www.zip.com.au/~hong |
> Canberra, Australia         |

I didn't mean to sound like they are bad, just my personal opinion. I
believe the via chipsets are faster and very stable. The intel sets are
good, don't get me wrong, I just like the via. On bench tests I've seen Via
wins most (of course we all know bench tests can be done to make any product
look better). Some people like Chevy, some people like Ford. ;o)

Phil


"Thomas Becker" <tbecker@nospam.nc.rr.com> wrote in message
news:e0XgvtPfBHA.1936@tkmsftngp02...
> > IMHO Intel chipsets are the worst out there(especially the old bx
> chipset).
>
> Then what is your basis for saying they're bad?  I read on here about
> problem after problem people are having with VIA.  By and large, I'm sure
> they're fine, but they are certainly over represented here.  Also, the
440BX
> chipset was and one of the most reliable, hassle free chipsets available.
I
> have it and have never had any issues.
>
> "pc2k" <none@none.com> wrote in message
news:#YN5cVPfBHA.816@tkmsftngp05...
> > IMHO Intel chipsets are the worst out there(especially the old bx
> chipset).
> > Yes they work fine, it's just my opinion. I'm running a Intel 1ghz PIII
> with
> > Via Apollo Pro 133 and eveything is fine(not even the most recent 4 in 1
> > drivers). I've had 2 crashes running XP since july and right now I don't
> > have one problem with XP at all.
> >
> > Phil
> >
> >
> > "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> > news:au8P7.2697$J42.568579@news6-win.server.ntlworld.com...
> > >
> > > "Richard Urban" <rurban@frontiernet.net> wrote in message
> > > news:udbI37OfBHA.1628@tkmsftngp03...
> > > > Asus A7V-133 + Athlon 1.2 gig (overclocked to 1.4gig) + Via 4in1
4.35
> > > > drivers = NO PROBLEM.
> > > >
> > > > He who makes blanket statements is a fool!
> > >
> > > What that should have said was
> > >
> > > "Take a look, anyone with the AMD/Via chipset may have Infinate_Loop
> > errors,
> > > everyone with Intel chipsets/CPU's will not.  Work it out....."
> > >
> > > Agreed not all Via/AMD systems will exhibt this fault, but those that
do
> > > will be Via/AMD.  Intel chipsets do not suffer from this problem.
> > >
> > >
> > >
> > > > "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> > > > news:sm7P7.581$m5.125759@news11-gui.server.ntli.net...
> > > > > Take a look, everyone with the AMD/Via chipset has Infinate_Loop
> > errors,
> > > > > everyone with Intel chipsets/CPU's does not.
> > > > >
> > > > > Work it out.....
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Hong Ooi" <hong.ooi@maths.anu.edu.au> wrote in message
> > > > > news:achp0us61k469htqu233qnjtfkgi567s74@4ax.com...
> > > > > > Failing to leave well enough alone, I decided to try out the new
> > > Nvidia
> > > > > > 23.11 Detonators on my XP Pro box. Up to this point, using the
> 21.83
> > > > > > drivers, my system had been quite stable, without any major
> hangups.
> > > > After
> > > > > > installing the new drivers, I got the dreaded infinite loop BSOD
> in
> > > > > > nv4_disp.dll on running 3dmark2001.
> > > > > >
> > > > > > I tried to roll back the drivers to the previous version, but
> there
> > > were
> > > > > > still some remnants behind. So I deleted all the drivers and
> > rebooted,
> > > > > upon
> > > > > > which XP redetected the video card and reinstalled the 21.83
> drivers
> > > > from
> > > > > > scratch.
> > > > > >
> > > > > > The problem now is that whenever I login as admin, I get a
dialog
> > box
> > > > > > saying that "Windows has recovered from a serious error", and
> > offering
> > > > to
> > > > > > send the dump info to MS. There is also the following entry in
the
> > > > system
> > > > > > event log:
> > > > > >
> > > > > >
> > > > > > Event Type: Error
> > > > > > Event Source: System Error
> > > > > > Event Category: (102)
> > > > > > Event ID: 1003
> > > > > > Date: 4/12/2001
> > > > > > Time: 11:28:37 PM
> > > > > > User: N/A
> > > > > > Computer: C3Y9M9
> > > > > > Description:
> > > > > > Error code 100000ea, parameter1 816ab648, parameter2 81696cd8,
> > > > parameter3
> > > > > > 823d1510, parameter4 00000001.
> > > > > >
> > > > > >
> > > > > > I only get this error when I login as admin, not as my usual
> userid.
> > > > > > Everything still seems to run fine, however the refresh rate fix
> to
> > > > enable
> > > > > > rates above 60Hz doesn't work anymore.
> > > > > >
> > > > > > What does this error mean, and how do I fix it? I've already
tried
> > > going
> > > > > > back to a system restore point, but Windows said it was
> unsuccessful
> > > and
> > > > > > didn't change anything. Argh.
> > > > > >
> > > > > >
> > > > > > System specs:
> > > > > > AMD Athlon 1.33GHz (not overclocked in any way)
> > > > > > MSI MS-6341 mobo, with 512MB RAM
> > > > > > Asus V7700 Deluxe Geforce2 GTS, 32MB
> > > > > > Hercules GTXP, with the 6.1 drivers
> > > > > > AOpen AON-325 NIC (Realtek chip)
> > > > > > IBM 60GXP 40GB hard disk
> > > > > > Pioneer DVD-105 DVD drive
> > > > > > Ricoh MP-7125A CDRW
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Hong Ooi                    | "You are inundated with SQUARES!"
> > > > > > hong.ooi@maths.anu.edu.au   |    -- JEM
> > > > > > http://www.zip.com.au/~hong |
> > > > > > Canberra, Australia         |
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

I guess I should have phrased it different. Intel has good chipsets, I just
like Via. If I was getting a via or intel chipset for free, I would pick the
via. A personal opinion based on my experience and articles I have read.
Some people like Chevy, some like Ford. ;o)

Phil


"Darren Greenwald" <darrenmail@earthlink.net> wrote in message
news:OfJ1bqRfBHA.2284@tkmsftngp05...
>
> "pc2k" <none@none.com> wrote in message
news:#YN5cVPfBHA.816@tkmsftngp05...
> > IMHO Intel chipsets are the worst out there(especially the old bx
> chipset).
> > Yes they work fine, it's just my opinion. I'm running a Intel 1ghz PIII
> with
>
> They work fine, but they are the worst???
>
>
>

"Mauro Leibelt [436991]" <mleibelt@home.com> wrote in message
news:OjUZ81PfBHA.2120@tkmsftngp07...
> I have an intel MB and I still have to find a working XPdriver for my
> GForce2.


I'm not suprised you are not getting much help.  Perhaps someone may be able
to help, if you said what the problem was (other than "I still have to find
a working XPdriver").

What problems do you have?

Hello,

I have the same question. But as a workaround,my athlon (AMD-761
northbridge) and GeForce2 TI works fine with the 23.11 drivers, XP, but
down-clocked to 100Mhz BUS/Multiplier13 (100/1300Mhz).  This is "livable"
until a real fix is found.

Mike

Sorry for not being more specific. The problems that most people have:
"Driver in infinite loop" (al builds) and "driver overwrite cache memory"
(using 23.10 and 23.11).


"Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
news:zlbP7.1246$m5.276432@news11-gui.server.ntli.net...
>
> "Mauro Leibelt [436991]" <mleibelt@home.com> wrote in message
> news:OjUZ81PfBHA.2120@tkmsftngp07...
> > I have an intel MB and I still have to find a working XPdriver for my
> > GForce2.
>
>
> I'm not suprised you are not getting much help.  Perhaps someone may be
able
> to help, if you said what the problem was (other than "I still have to
find
> a working XPdriver").
>
> What problems do you have?
>
>

On Tue, 4 Dec 2001 22:38:20 -0000, "Camera_Man" <bitbucket@bigfoot.com>
wrote:

>Go to http://www.guru3d.com/files/ and download the infinite loop patch.
>It is beta, so read the details on the site BEFORE you try it.

Is that patch only for Via chipsets? I have an AMD-761 northbridge; would
the patch still work?


--
Hong Ooi                    | "You are inundated with SQUARES!"
hong.ooi@maths.anu.edu.au   |    -- JEM
http://www.zip.com.au/~hong |
Canberra, Australia         |

"Mauro Leibelt" <mleibelt@home.com> wrote in message
news:OVcroocfBHA.424@tkmsftngp04...
| Sorry for not being more specific. The problems that most people have:
| "Driver in infinite loop" (al builds) and "driver overwrite cache memory"
| (using 23.10 and 23.11).

Did you up the AGP setting in BIOS?  tHE SUGGESTED SETTING IS 256m.  |
|
| "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
| news:zlbP7.1246$m5.276432@news11-gui.server.ntli.net...
| >
| > "Mauro Leibelt [436991]" <mleibelt@home.com> wrote in message
| > news:OjUZ81PfBHA.2120@tkmsftngp07...
| > > I have an intel MB and I still have to find a working XPdriver for my
| > > GForce2.
| >
| >
| > I'm not suprised you are not getting much help.  Perhaps someone may be
| able
| > to help, if you said what the problem was (other than "I still have to
| find
| > a working XPdriver").
| >
| > What problems do you have?
| >
| >
|
|

After working for over a year with VIA chipsets and 6 odd years before that
on Intel mainboards. I'll stick with Intel, specially if one was to use it
for a server and needed a reliable hardware setup they could depend on.

VIA just seems to have too many problems, especially with USB devices.

:)

            -=[Lurch]=-
http://lurchnz.hypermart.net

"pc2k" <none@none.com> wrote in message news:eUFa6nSfBHA.1552@tkmsftngp02...
> I didn't mean to sound like they are bad, just my personal opinion. I
> believe the via chipsets are faster and very stable. The intel sets are
> good, don't get me wrong, I just like the via. On bench tests I've seen
Via
> wins most (of course we all know bench tests can be done to make any
product
> look better). Some people like Chevy, some people like Ford. ;o)
>
> Phil
>
>
> "Thomas Becker" <tbecker@nospam.nc.rr.com> wrote in message
> news:e0XgvtPfBHA.1936@tkmsftngp02...
> > > IMHO Intel chipsets are the worst out there(especially the old bx
> > chipset).
> >
> > Then what is your basis for saying they're bad?  I read on here about
> > problem after problem people are having with VIA.  By and large, I'm
sure
> > they're fine, but they are certainly over represented here.  Also, the
> 440BX
> > chipset was and one of the most reliable, hassle free chipsets
available.
> I
> > have it and have never had any issues.
> >
> > "pc2k" <none@none.com> wrote in message
> news:#YN5cVPfBHA.816@tkmsftngp05...
> > > IMHO Intel chipsets are the worst out there(especially the old bx
> > chipset).
> > > Yes they work fine, it's just my opinion. I'm running a Intel 1ghz
PIII
> > with
> > > Via Apollo Pro 133 and eveything is fine(not even the most recent 4 in
1
> > > drivers). I've had 2 crashes running XP since july and right now I
don't
> > > have one problem with XP at all.
> > >
> > > Phil
> > >
> > >
> > > "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> > > news:au8P7.2697$J42.568579@news6-win.server.ntlworld.com...
> > > >
> > > > "Richard Urban" <rurban@frontiernet.net> wrote in message
> > > > news:udbI37OfBHA.1628@tkmsftngp03...
> > > > > Asus A7V-133 + Athlon 1.2 gig (overclocked to 1.4gig) + Via 4in1
> 4.35
> > > > > drivers = NO PROBLEM.
> > > > >
> > > > > He who makes blanket statements is a fool!
> > > >
> > > > What that should have said was
> > > >
> > > > "Take a look, anyone with the AMD/Via chipset may have Infinate_Loop
> > > errors,
> > > > everyone with Intel chipsets/CPU's will not.  Work it out....."
> > > >
> > > > Agreed not all Via/AMD systems will exhibt this fault, but those
that
> do
> > > > will be Via/AMD.  Intel chipsets do not suffer from this problem.
> > > >
> > > >
> > > >
> > > > > "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in
message
> > > > > news:sm7P7.581$m5.125759@news11-gui.server.ntli.net...
> > > > > > Take a look, everyone with the AMD/Via chipset has Infinate_Loop
> > > errors,
> > > > > > everyone with Intel chipsets/CPU's does not.
> > > > > >
> > > > > > Work it out.....
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Hong Ooi" <hong.ooi@maths.anu.edu.au> wrote in message
> > > > > > news:achp0us61k469htqu233qnjtfkgi567s74@4ax.com...
> > > > > > > Failing to leave well enough alone, I decided to try out the
new
> > > > Nvidia
> > > > > > > 23.11 Detonators on my XP Pro box. Up to this point, using the
> > 21.83
> > > > > > > drivers, my system had been quite stable, without any major
> > hangups.
> > > > > After
> > > > > > > installing the new drivers, I got the dreaded infinite loop
BSOD
> > in
> > > > > > > nv4_disp.dll on running 3dmark2001.
> > > > > > >
> > > > > > > I tried to roll back the drivers to the previous version, but
> > there
> > > > were
> > > > > > > still some remnants behind. So I deleted all the drivers and
> > > rebooted,
> > > > > > upon
> > > > > > > which XP redetected the video card and reinstalled the 21.83
> > drivers
> > > > > from
> > > > > > > scratch.
> > > > > > >
> > > > > > > The problem now is that whenever I login as admin, I get a
> dialog
> > > box
> > > > > > > saying that "Windows has recovered from a serious error", and
> > > offering
> > > > > to
> > > > > > > send the dump info to MS. There is also the following entry in
> the
> > > > > system
> > > > > > > event log:
> > > > > > >
> > > > > > >
> > > > > > > Event Type: Error
> > > > > > > Event Source: System Error
> > > > > > > Event Category: (102)
> > > > > > > Event ID: 1003
> > > > > > > Date: 4/12/2001
> > > > > > > Time: 11:28:37 PM
> > > > > > > User: N/A
> > > > > > > Computer: C3Y9M9
> > > > > > > Description:
> > > > > > > Error code 100000ea, parameter1 816ab648, parameter2 81696cd8,
> > > > > parameter3
> > > > > > > 823d1510, parameter4 00000001.
> > > > > > >
> > > > > > >
> > > > > > > I only get this error when I login as admin, not as my usual
> > userid.
> > > > > > > Everything still seems to run fine, however the refresh rate
fix
> > to
> > > > > enable
> > > > > > > rates above 60Hz doesn't work anymore.
> > > > > > >
> > > > > > > What does this error mean, and how do I fix it? I've already
> tried
> > > > going
> > > > > > > back to a system restore point, but Windows said it was
> > unsuccessful
> > > > and
> > > > > > > didn't change anything. Argh.
> > > > > > >
> > > > > > >
> > > > > > > System specs:
> > > > > > > AMD Athlon 1.33GHz (not overclocked in any way)
> > > > > > > MSI MS-6341 mobo, with 512MB RAM
> > > > > > > Asus V7700 Deluxe Geforce2 GTS, 32MB
> > > > > > > Hercules GTXP, with the 6.1 drivers
> > > > > > > AOpen AON-325 NIC (Realtek chip)
> > > > > > > IBM 60GXP 40GB hard disk
> > > > > > > Pioneer DVD-105 DVD drive
> > > > > > > Ricoh MP-7125A CDRW
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Hong Ooi                    | "You are inundated with
SQUARES!"
> > > > > > > hong.ooi@maths.anu.edu.au   |    -- JEM
> > > > > > > http://www.zip.com.au/~hong |
> > > > > > > Canberra, Australia         |
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Yes, I have tried all the possible settings but without any improvement.
Anyway, thanks for the suggestion.

"Gort" <klaatu@bogus.org> wrote in message
news:##vd1pkfBHA.424@tkmsftngp04...
> "Mauro Leibelt" <mleibelt@home.com> wrote in message
> news:OVcroocfBHA.424@tkmsftngp04...
> | Sorry for not being more specific. The problems that most people have:
> | "Driver in infinite loop" (al builds) and "driver overwrite cache
memory"
> | (using 23.10 and 23.11).
>
> Did you up the AGP setting in BIOS?  tHE SUGGESTED SETTING IS 256m.  |
> |
> | "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> | news:zlbP7.1246$m5.276432@news11-gui.server.ntli.net...
> | >
> | > "Mauro Leibelt [436991]" <mleibelt@home.com> wrote in message
> | > news:OjUZ81PfBHA.2120@tkmsftngp07...
> | > > I have an intel MB and I still have to find a working XPdriver for
my
> | > > GForce2.
> | >
> | >
> | > I'm not suprised you are not getting much help.  Perhaps someone may
be
> | able
> | > to help, if you said what the problem was (other than "I still have to
> | find
> | > a working XPdriver").
> | >
> | > What problems do you have?
> | >
> | >
> |
> |
>

On Thu, 6 Dec 2001 08:04:44 +1300, "lurch" <lurchnz@xtra.co.nz> wrote:

>After working for over a year with VIA chipsets and 6 odd years before that
>on Intel mainboards. I'll stick with Intel, specially if one was to use it
>for a server and needed a reliable hardware setup they could depend on.
>
>VIA just seems to have too many problems, especially with USB devices.

Strangely enough if there's one thing my AMD 761/Via 686b mobo has never
had problems with, it's USB. Detonator drivers yes, but not USB.


--
Hong Ooi                    | "You are inundated with SQUARES!"
hong.ooi@maths.anu.edu.au   |    -- JEM
http://www.zip.com.au/~hong |
Canberra, Australia         |

Instead of jumping on XP or the board manufacturers would think the problem
lies with nVidia. Try swapping in a different card say ATI or ? and see if
the problem comes back. If yes then it may be XP but if no then some e-mail
to nVidia might be in order.
"Mauro Leibelt" <mleibelt@home.com> wrote in message
news:OVcroocfBHA.424@tkmsftngp04...
> Sorry for not being more specific. The problems that most people have:
> "Driver in infinite loop" (al builds) and "driver overwrite cache memory"
> (using 23.10 and 23.11).
>
>
> "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> news:zlbP7.1246$m5.276432@news11-gui.server.ntli.net...
> >
> > "Mauro Leibelt [436991]" <mleibelt@home.com> wrote in message
> > news:OjUZ81PfBHA.2120@tkmsftngp07...
> > > I have an intel MB and I still have to find a working XPdriver for my
> > > GForce2.
> >
> >
> > I'm not suprised you are not getting much help.  Perhaps someone may be
> able
> > to help, if you said what the problem was (other than "I still have to
> find
> > a working XPdriver").
> >
> > What problems do you have?
> >
> >
>
>
>

For the final user it is quite difficult to find out where the problem
actually is. Microsoft certifies that the drivers are XP compliant so, if
they say the drivers are ok, the problem must be XP. On the other hand, if
the Microsoft certification exists just to put smoke in user's eyes, the
problem can well be the driver. In both cases Microsoft has its share of
responsibility even because they have known of the problem for about 9
months and done nothing to solve it. Anyway, I wouldn't blame the MB since
the BSOD has been reported on Intel, VIA,... and on different versions of
the chipsets.


"Gary" <crc_1@hotmail.com> wrote in message
news:4iuR7.3442$5K4.391231@newsread1.prod.itd.earthlink.net...
> Instead of jumping on XP or the board manufacturers would think the
problem
> lies with nVidia. Try swapping in a different card say ATI or ? and see if
> the problem comes back. If yes then it may be XP but if no then some
e-mail
> to nVidia might be in order.
> "Mauro Leibelt" <mleibelt@home.com> wrote in message
> news:OVcroocfBHA.424@tkmsftngp04...
> > Sorry for not being more specific. The problems that most people have:
> > "Driver in infinite loop" (al builds) and "driver overwrite cache
memory"
> > (using 23.10 and 23.11).
> >
> >
> > "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> > news:zlbP7.1246$m5.276432@news11-gui.server.ntli.net...
> > >
> > > "Mauro Leibelt [436991]" <mleibelt@home.com> wrote in message
> > > news:OjUZ81PfBHA.2120@tkmsftngp07...
> > > > I have an intel MB and I still have to find a working XPdriver for
my
> > > > GForce2.
> > >
> > >
> > > I'm not suprised you are not getting much help.  Perhaps someone may
be
> > able
> > > to help, if you said what the problem was (other than "I still have to
> > find
> > > a working XPdriver").
> > >
> > > What problems do you have?
> > >
> > >
> >
> >
> >
>
>

Lucky you. I am using certified drivers and they do not work as well.

"Stephen Naylor" <Stephen.Naylor@ntlworld.com> wrote in message
news:#rJS1v9gBHA.2464@tkmsftngp03...
> The Version 23.11 drivers are not Microsoft certified. You are told this
> when you install them.
>
> I installed them ignoring the onscreen advice not to install them and had
no
> end of problems. I used the rollback feature in device manger to go back
to
> my previous driver and things have been fine since.
>
> Regards
>
> Stephen Naylor
>
> "Mauro Leibelt" <mleibelt@u.washington.edu> wrote in message
> news:uRrVWHzgBHA.1684@tkmsftngp03...
> > For the final user it is quite difficult to find out where the problem
> > actually is. Microsoft certifies that the drivers are XP compliant so,
if
> > they say the drivers are ok, the problem must be XP. On the other hand,
if
> > the Microsoft certification exists just to put smoke in user's eyes, the
> > problem can well be the driver. In both cases Microsoft has its share of
> > responsibility even because they have known of the problem for about 9
> > months and done nothing to solve it. Anyway, I wouldn't blame the MB
since
> > the BSOD has been reported on Intel, VIA,... and on different versions
of
> > the chipsets.
> >
> >
> > "Gary" <crc_1@hotmail.com> wrote in message
> > news:4iuR7.3442$5K4.391231@newsread1.prod.itd.earthlink.net...
> > > Instead of jumping on XP or the board manufacturers would think the
> > problem
> > > lies with nVidia. Try swapping in a different card say ATI or ? and
see
> if
> > > the problem comes back. If yes then it may be XP but if no then some
> > e-mail
> > > to nVidia might be in order.
> > > "Mauro Leibelt" <mleibelt@home.com> wrote in message
> > > news:OVcroocfBHA.424@tkmsftngp04...
> > > > Sorry for not being more specific. The problems that most people
have:
> > > > "Driver in infinite loop" (al builds) and "driver overwrite cache
> > memory"
> > > > (using 23.10 and 23.11).
> > > >
> > > >
> > > > "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> > > > news:zlbP7.1246$m5.276432@news11-gui.server.ntli.net...
> > > > >
> > > > > "Mauro Leibelt [436991]" <mleibelt@home.com> wrote in message
> > > > > news:OjUZ81PfBHA.2120@tkmsftngp07...
> > > > > > I have an intel MB and I still have to find a working XPdriver
for
> > my
> > > > > > GForce2.
> > > > >
> > > > >
> > > > > I'm not suprised you are not getting much help.  Perhaps someone
may
> > be
> > > > able
> > > > > to help, if you said what the problem was (other than "I still
have
> to
> > > > find
> > > > > a working XPdriver").
> > > > >
> > > > > What problems do you have?
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

The Version 23.11 drivers are not Microsoft certified. You are told this
when you install them.

I installed them ignoring the onscreen advice not to install them and had no
end of problems. I used the rollback feature in device manger to go back to
my previous driver and things have been fine since.

Regards

Stephen Naylor

"Mauro Leibelt" <mleibelt@u.washington.edu> wrote in message
news:uRrVWHzgBHA.1684@tkmsftngp03...
> For the final user it is quite difficult to find out where the problem
> actually is. Microsoft certifies that the drivers are XP compliant so, if
> they say the drivers are ok, the problem must be XP. On the other hand, if
> the Microsoft certification exists just to put smoke in user's eyes, the
> problem can well be the driver. In both cases Microsoft has its share of
> responsibility even because they have known of the problem for about 9
> months and done nothing to solve it. Anyway, I wouldn't blame the MB since
> the BSOD has been reported on Intel, VIA,... and on different versions of
> the chipsets.
>
>
> "Gary" <crc_1@hotmail.com> wrote in message
> news:4iuR7.3442$5K4.391231@newsread1.prod.itd.earthlink.net...
> > Instead of jumping on XP or the board manufacturers would think the
> problem
> > lies with nVidia. Try swapping in a different card say ATI or ? and see
if
> > the problem comes back. If yes then it may be XP but if no then some
> e-mail
> > to nVidia might be in order.
> > "Mauro Leibelt" <mleibelt@home.com> wrote in message
> > news:OVcroocfBHA.424@tkmsftngp04...
> > > Sorry for not being more specific. The problems that most people have:
> > > "Driver in infinite loop" (al builds) and "driver overwrite cache
> memory"
> > > (using 23.10 and 23.11).
> > >
> > >
> > > "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> > > news:zlbP7.1246$m5.276432@news11-gui.server.ntli.net...
> > > >
> > > > "Mauro Leibelt [436991]" <mleibelt@home.com> wrote in message
> > > > news:OjUZ81PfBHA.2120@tkmsftngp07...
> > > > > I have an intel MB and I still have to find a working XPdriver for
> my
> > > > > GForce2.
> > > >
> > > >
> > > > I'm not suprised you are not getting much help.  Perhaps someone may
> be
> > > able
> > > > to help, if you said what the problem was (other than "I still have
to
> > > find
> > > > a working XPdriver").
> > > >
> > > > What problems do you have?
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>
>

I have the same problems, and after going through the config for directx,
and trying what they suggested....it still didn't work...I have an Nvidia
gforce 2 mx 400, and have tried everything

the only thing that has worked so far is when I took the card out, and put
in Matrox g400 millenium....as far as I am concerned, the problem lies with
nvidia

"Stephen Naylor" <Stephen.Naylor@ntlworld.com> wrote in message
news:#rJS1v9gBHA.2464@tkmsftngp03...
> The Version 23.11 drivers are not Microsoft certified. You are told this
> when you install them.
>
> I installed them ignoring the onscreen advice not to install them and had
no
> end of problems. I used the rollback feature in device manger to go back
to
> my previous driver and things have been fine since.
>
> Regards
>
> Stephen Naylor
>
> "Mauro Leibelt" <mleibelt@u.washington.edu> wrote in message
> news:uRrVWHzgBHA.1684@tkmsftngp03...
> > For the final user it is quite difficult to find out where the problem
> > actually is. Microsoft certifies that the drivers are XP compliant so,
if
> > they say the drivers are ok, the problem must be XP. On the other hand,
if
> > the Microsoft certification exists just to put smoke in user's eyes, the
> > problem can well be the driver. In both cases Microsoft has its share of
> > responsibility even because they have known of the problem for about 9
> > months and done nothing to solve it. Anyway, I wouldn't blame the MB
since
> > the BSOD has been reported on Intel, VIA,... and on different versions
of
> > the chipsets.
> >
> >
> > "Gary" <crc_1@hotmail.com> wrote in message
> > news:4iuR7.3442$5K4.391231@newsread1.prod.itd.earthlink.net...
> > > Instead of jumping on XP or the board manufacturers would think the
> > problem
> > > lies with nVidia. Try swapping in a different card say ATI or ? and
see
> if
> > > the problem comes back. If yes then it may be XP but if no then some
> > e-mail
> > > to nVidia might be in order.
> > > "Mauro Leibelt" <mleibelt@home.com> wrote in message
> > > news:OVcroocfBHA.424@tkmsftngp04...
> > > > Sorry for not being more specific. The problems that most people
have:
> > > > "Driver in infinite loop" (al builds) and "driver overwrite cache
> > memory"
> > > > (using 23.10 and 23.11).
> > > >
> > > >
> > > > "Mark Gillespie" <mark.gillespie@SPAMTRAPemail.com> wrote in message
> > > > news:zlbP7.1246$m5.276432@news11-gui.server.ntli.net...
> > > > >
> > > > > "Mauro Leibelt [436991]" <mleibelt@home.com> wrote in message
> > > > > news:OjUZ81PfBHA.2120@tkmsftngp07...
> > > > > > I have an intel MB and I still have to find a working XPdriver
for
> > my
> > > > > > GForce2.
> > > > >
> > > > >
> > > > > I'm not suprised you are not getting much help.  Perhaps someone
may
> > be
> > > > able
> > > > > to help, if you said what the problem was (other than "I still
have
> to
> > > > find
> > > > > a working XPdriver").
> > > > >
> > > > > What problems do you have?
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>