Every game, and I mean EVERY game randomly locks up with
an accompanying sound stutter under xp. I know it isn't
a graphics problem. Could this be a memory issue?

The event viewer doesn't show any warnings or event
errors.


>-----Original Message-----
>Ben, go into Control Panel/Administrative Tools/Event
Viewer and click on
>Application in the left panel. It will reveal a listing
of activity in the
>right pane, where you should look for entries with
either a yellow
>exclamation point or red circle with a white X. You can
then right-click
>the listing, select Properties and information about the
error will be
>shown. This would give an indication of where the
problem exists.
>--
>Chris H.
>Microsoft Windows MVP
>Associate Expert
>Expert Zone - www.microsoft.com/windowsxp/expertzone
>
>"Ben Wolf" <(E-Mail Removed)> wrote in message
>news:0c9a01c34c81$170547a0$(E-Mail Removed)...
>>
>> I'm using an SBLive!. It's about four years old. My
>> Processor is an XP 1500 and the memory is 400 MB PC100.
>> Video is now a GeForce 4 MX 440. The motherboard is an
>> ECS k7s5a. Drivers are all current. I'm actually
going
>> to be replacing everything but the video over the next
2
>> months, but I'd love to know what is causing this so I
>> can replace it first. I'm using a clean install of XP.
>> This problem has been happening for the last two to
three
>> months, but it has been happening with even greater
>> frequency since I replaced my GeForce 2 with the
GeForce
>> 4 a few days ago.
>>
>> >-----Original Message-----
>> >Sound stutter? How about your sound card? What do
you
>> have in your system,
>> >and is the driver current?
>> >--
>> >Chris H.
>>
>> >Microsoft Windows MVP
>> >Associate Expert
>> >Expert Zone - www.microsoft.com/windowsxp/expertzone
>> >
>> >"Ben Wolf" <(E-Mail Removed)> wrote in message
>> >news:098501c34c5b$c67a8900$(E-Mail Removed)...
>> >> Every game, and I mean EVERY game randomly locks up
>> with
>> >> an accompanying sound stutter under xp. I know it
>> isn't
>> >> a graphics problem. Could this be a memory issue?
>> >
>> >
>> >.
>> >
>
>
>.
>

If you have performed a clean install then reinstall the motherboard chipset
drivers and the video card manufacturers drivers for Windows XP and then try
again. Ensure that you have reinstalled the soundcard drivers for your
Soundblaster card only from the manufacturer's website.

regards

B
"Chris H." <(E-Mail Removed)> wrote in message
news:%23xLfK%(E-Mail Removed)...
> Sound stutter? How about your sound card? What do you have in your
system,
> and is the driver current?
> --
> Chris H.
> Microsoft Windows MVP
> Associate Expert
> Expert Zone - www.microsoft.com/windowsxp/expertzone
>
> "Ben Wolf" <(E-Mail Removed)> wrote in message
> news:098501c34c5b$c67a8900$(E-Mail Removed)...
> > Every game, and I mean EVERY game randomly locks up with
> > an accompanying sound stutter under xp. I know it isn't
> > a graphics problem. Could this be a memory issue?
>
>

Tried updating the motherboard. Still crashing with a
sound stutter.


>-----Original Message-----
>If you have performed a clean install then reinstall the
motherboard chipset
>drivers and the video card manufacturers drivers for
Windows XP and then try
>again. Ensure that you have reinstalled the soundcard
drivers for your
>Soundblaster card only from the manufacturer's website.
>
>regards
>
>B
>"Chris H." <(E-Mail Removed)> wrote in message
>news:%23xLfK%(E-Mail Removed)...
>> Sound stutter? How about your sound card? What do
you have in your
>system,
>> and is the driver current?
>> --
>> Chris H.
>> Microsoft Windows MVP
>> Associate Expert
>> Expert Zone - www.microsoft.com/windowsxp/expertzone
>>
>> "Ben Wolf" <(E-Mail Removed)> wrote in message
>> news:098501c34c5b$c67a8900$(E-Mail Removed)...
>> > Every game, and I mean EVERY game randomly locks up
with
>> > an accompanying sound stutter under xp. I know it
isn't
>> > a graphics problem. Could this be a memory issue?
>>
>>
>
>
>.
>

>-----Original Message-----
>Every game, and I mean EVERY game randomly locks up with
>an accompanying sound stutter under xp. I know it isn't
>a graphics problem. Could this be a memory issue?
>.
>

I'm having much of the same issue.. But, its just my
computer in general, anything i do causes it to lock up..
Playing MP3s, vid clips, games, sitting there chatting for
hte love of god!

I have a tyan trinity VIA chipset mb, Radeon 8500, AMD XP
1900 running under XP pro...

If I may just interject something....

I haven't seen mention of your BIOS settings yet. I just took a peak on
ECS's site, and it looks like your board uses AMI Bios.
We could compare if you want....

A sure-fire way to get crashes as you describe is to assume that settings
for one card will work on another - even if the 'other' card is a newer one.
Maybe the old card was set to something that doesn't make sense to the new
one, during *demanding* situations such as a game.

I have a Geforce 4 MX440, Jedi Knight II, Unreal II, Unreal Tournament 2003,
and Earthviewer3D NVIDIA, which are all very demanding, but do not have the
lockups. And I am overclocking my CPU (Athlon 1700+ running @ 1900+). I
overclock my video card about 10%.

Video specific:
Burst length?
SDRAM 1T command?
AGP 1x, 2x, 4x?
AGP Aperture setting?
AGP Fast write?

To name just a few...

You might be pleasantly surprised to discover that you solve the problem,
AND get the most of your card and computer, as well.

Good luck,
-Lawrence in Seattle




"Ben Wolf" <(E-Mail Removed)> wrote in message
news:02a301c34c9a$8d3e49d0$(E-Mail Removed)...
> Event Log finally noticed something. I don't know if it
> means anything to you, but here it is:
>
> Faulting application jk2sp.exe, version 0.0.0.0, faulting
> module jk2sp.exe, version 0.0.0.0, fault address
> 0x00039300.
>
> The application is Jedi Knight II. I'd send it to
> Microsoft, but they can take decades to respond to a
> problem.
>
> >-----Original Message-----
> >Strange, Ben. Really strange. Have you tried turning
> down the hardware
> >acceleration on your sound card? Some of the SB Live!
> cards were giving
> >similar problems with full acceleration. You can go
> into Control
> >Panel/Sounds and Audio Devices/Speaker settings at the
> bottom of the first
> >page. Then click the Advanced button and go to the
> Performance tab. In
> >there, use the slider to move one notch left, then try
> the games again. If
> >the problem produces itself, try another notch to the
> left.
> >
> >If that doesn't work, try using Dr. Watson. Yup, he's
> still around.
> >Details on how to set him up in Windows XP are available
> in Help and Support
> >by doing a search for "Dr. Watson" without the quotes.
> He'll trap any error
> >messages.
> >--
> >Chris H.
> >Microsoft Windows MVP
> >Associate Expert
> >Expert Zone - www.microsoft.com/windowsxp/expertzone
> >
> >"Ben Wolf" <(E-Mail Removed)> wrote in message
> >news:01ff01c34c8b$00f75480$(E-Mail Removed)...
> >> The event viewer doesn't show any warnings or event
> >> errors.
> >>
> >>
> >> >-----Original Message-----
> >> >Ben, go into Control Panel/Administrative Tools/Event
> >> Viewer and click on
> >> >Application in the left panel. It will reveal a
> listing
> >> of activity in the
> >> >right pane, where you should look for entries with
> >> either a yellow
> >> >exclamation point or red circle with a white X. You
> can
> >> then right-click
> >> >the listing, select Properties and information about
> the
> >> error will be
> >> >shown. This would give an indication of where the
> >> problem exists.
> >> >--
> >> >Chris H.
> >> >Microsoft Windows MVP
> >> >Associate Expert
> >> >Expert Zone - www.microsoft.com/windowsxp/expertzone
> >> >
> >> >"Ben Wolf" <(E-Mail Removed)> wrote in message
> >> >news:0c9a01c34c81$170547a0$(E-Mail Removed)...
> >> >>
> >> >> I'm using an SBLive!. It's about four years old.
> My
> >> >> Processor is an XP 1500 and the memory is 400 MB
> PC100.
> >> >> Video is now a GeForce 4 MX 440. The motherboard
> is an
> >> >> ECS k7s5a. Drivers are all current. I'm actually
> >> going
> >> >> to be replacing everything but the video over the
> next
> >> 2
> >> >> months, but I'd love to know what is causing this
> so I
> >> >> can replace it first. I'm using a clean install of
> XP.
> >> >> This problem has been happening for the last two to
> >> three
> >> >> months, but it has been happening with even greater
> >> >> frequency since I replaced my GeForce 2 with the
> >> GeForce
> >> >> 4 a few days ago.
> >> >>
> >> >> >-----Original Message-----
> >> >> >Sound stutter? How about your sound card? What do
> >> you
> >> >> have in your system,
> >> >> >and is the driver current?
> >> >> >--
> >> >> >Chris H.
> >> >>
> >> >> >Microsoft Windows MVP
> >> >> >Associate Expert
> >> >> >Expert Zone -
> www.microsoft.com/windowsxp/expertzone
> >> >> >
> >> >> >"Ben Wolf" <(E-Mail Removed)> wrote in message
> >> >> >news:098501c34c5b$c67a8900$(E-Mail Removed)...
> >> >> >> Every game, and I mean EVERY game randomly locks
> up
> >> >> with
> >> >> >> an accompanying sound stutter under xp. I know
> it
> >> >> isn't
> >> >> >> a graphics problem. Could this be a memory
> issue?
> >> >> >
> >> >> >
> >> >> >.
> >> >> >
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

Try removing only the soundcard and run your games without sound just for
troubleshooting purposes and then see if the problem is resolved.

regards

B
"Chris H." <(E-Mail Removed)> wrote in message
news:%23xLfK%(E-Mail Removed)...
> Sound stutter? How about your sound card? What do you have in your
system,
> and is the driver current?
> --
> Chris H.
> Microsoft Windows MVP
> Associate Expert
> Expert Zone - www.microsoft.com/windowsxp/expertzone
>
> "Ben Wolf" <(E-Mail Removed)> wrote in message
> news:098501c34c5b$c67a8900$(E-Mail Removed)...
> > Every game, and I mean EVERY game randomly locks up with
> > an accompanying sound stutter under xp. I know it isn't
> > a graphics problem. Could this be a memory issue?
>
>

I sincerely apologize if I offended you with my remark about reading the
manual. I meant it as a tongue in cheek joke. Honestly.

I would respectfully submit that there is a setting in BIOS ("Fast Command")
that would (theoretically) make my own system faster, except that when I
select it, Windows XP always crashes and gives me the Memory Dump Blue
Screen after barely a minute. So although it *should* provide the best
possible performance - it actually makes performance an impossibility.

A mitigating factor is that I happen to overclock my system. It appears
that by overclocking it, the margin of error for normally productive
settings is much smaller. In my research, however, I determined that the
net gain of overclocking without Fast Command enabled was greater than not
overclocking and enabling it. [Athlon XP 1700+ running happily as a 1900+]

I really was trying to help.

If you want, we could still compare BIOS settings... it's still worth a
shot.

-Lawrence in Seattle


"Ben Wolf" <(E-Mail Removed)> wrote in message
news:01fb01c34e66$d2709490$(E-Mail Removed)...
> I always *read* the manual. The BIOS is and has been
> fully updated. The settings in the BIOS are set for the
> best possible performance. I've even tried loading the
> default configuration setting. I don't use BIOS
> cacheing, and there isnt even an option for shadowing.
>
>
> >-----Original Message-----
> >So, you're saying you've confirmed your BIOS settings, I
> mentioned in my
> >earlier post?
> >
> >I can get every one of my games to crash - and BSODs all
> day long, if I make
> >just and itty bitty change to any of several innocent-
> looking settings in
> >BIOS. Pullout that manual you've set aside, and have a
> look at what your
> >BIOS settings do. You may be pleasantly surprised.
> >
> >Have a good one,
> >-Lawrence in Seattle
> >
> >"Ben Wolf" <(E-Mail Removed)> wrote in message
> >news:04e701c34d13$b2027a10$(E-Mail Removed)...
> >> I've tried everything related to software. It can only
> >> be a hardware issue I think. Starting this month I'm
> >> going to replace most of my components. At least this
> >> gives me an excuse to upgrade.
> >>
> >>
> >> >-----Original Message-----
> >> >
> >> >>-----Original Message-----
> >> >>Every game, and I mean EVERY game randomly locks up
> >> with
> >> >>an accompanying sound stutter under xp. I know it
> >> isn't
> >> >>a graphics problem. Could this be a memory issue?
> >> >>.
> >> >>
> >> >
> >> >I'm having much of the same issue.. But, its just my
> >> >computer in general, anything i do causes it to lock
> >> up..
> >> >Playing MP3s, vid clips, games, sitting there chatting
> >> for
> >> >hte love of god!
> >> >
> >> >I have a tyan trinity VIA chipset mb, Radeon 8500, AMD
> >> XP
> >> >1900 running under XP pro...
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

Over-clocking on Windows XP can produce some results one can never trace.
Windows XP itself runs best of the specs of the hardware, but what it is,
and if you over-clock or even have two memory sticks from different
manufacturers you can have very weird results. Windows XP runs best with
everything "factory." 8-)
--
Chris H.
Microsoft Windows MVP
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone

"Lawrence" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I sincerely apologize if I offended you with my remark about reading the
> manual. I meant it as a tongue in cheek joke. Honestly.
>
> I would respectfully submit that there is a setting in BIOS ("Fast
Command")
> that would (theoretically) make my own system faster, except that when I
> select it, Windows XP always crashes and gives me the Memory Dump Blue
> Screen after barely a minute. So although it *should* provide the best
> possible performance - it actually makes performance an impossibility.
>
> A mitigating factor is that I happen to overclock my system. It appears
> that by overclocking it, the margin of error for normally productive
> settings is much smaller. In my research, however, I determined that the
> net gain of overclocking without Fast Command enabled was greater than not
> overclocking and enabling it. [Athlon XP 1700+ running happily as a
1900+]
>
> I really was trying to help.
>
> If you want, we could still compare BIOS settings... it's still worth a
> shot.
>
> -Lawrence in Seattle

Yes, good discussion is great - and a learning experience. See stuff (-->)
below.

"Lawrence" <(E-Mail Removed)> wrote in message
news:OHc%(E-Mail Removed)...
> Hi Chris,
>
> While I agree with your remarks about potential weirdness, a little decent
> testing, and incremental advances avoids most of that. Besides,
'weirdness'
> is just as capable of cropping up in a 'factory' box as an OCed one.
That's
> partly why this news group exists. If everything integrated perfectly,
> there'd be nothing in here to talk about.
--> Correct, however when Windows XP installs on a system it tracks the
components and what each item does according to the specs set by the
manufacturer. Future operating systems will get even better at it. When
one of the conditions becomes a variable, that's where trouble can come in.
It is like in beta testing programs or games, valid problems in the test
software are only true if the system is not over-clocked. If it can be
reproduced without over-clocking then it is a program bug. If not, guess
where the fault is placed?

> But I pretty much totally disagree that XP *necessarily* runs best with
> everything set to 'factory'. When you consider that CPUs are stamped out
> of one big wafer -and that where the individual chips were in relation to
> the center of that wafer (center chips being more stable at the highest
> speeds, while edge chips tend to be more stable at lower speeds), then the
> entire industry is based upon a spectrum of performance.
--> Granted, some companies produce "over-clock" chips with some point of
leeway, but are we really good enough to know when we've reached that point?
More power, or in this case running a chip beyond the recommended capacity,
isn't necessarily "better." What's gained? Bragging rights, or can one
really detect milliseconds of increased response time? The two major CPU
manufacturers can't even agree on how to describe what is important. 8-)

> So, if you are willing to go slow with your overclocking efforts, and not
> crank the chip right out of the box, you can get some really sweet results
> using tried and true methods that tens of thousands of overclockers
> successfully use, the world over.
--> I agree. But where do you draw the line whether a program is crashing
is the result of a faulty graphics driver or because the card has been
over-clocked. How do you know?

> It's a Bell curve of performance. You just have to look for the sweet
spot.
--> For what, again? Beside the issue of Windows XP recognizing which
chips you're running and tuning itself for the factory specs on that
particular item, what is gained? Shortening the life a CPU, graphics card
or RAM? I've honestly never understood how friends of mine - people who
over-clock everything in sight - can be buying three CPUs a year because
they burn out, for what? I really notice no difference in performance,
except of the individuals as they brag to each other, or complain about
different companies and the products being too fragile.

--> The main difference I've noticed on machines and performance is
increasing the RAM. (And don't try it on Windows XP with mismatched
sticks!). Bumping a system up to 512 from 256 will make a huge difference.

> Thanks for posting your thoughts. I really appreciate kicking these ideas
> around.
--> Glad to have the discussion. I hope you can enlighten me. I never saw
the "advantage" with Windows 95, etc., etc., etc., and still don't. 8-)
--
Chris H.
Microsoft Windows MVP
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone