Well Tony--
I always say this about games causing crashes-- If you google for some GunZ
forums, you're awfully likely to get an answer that is dead on in those
forums because you may not be the only one with the problem.
When you get that error--
That stop error, like many of them, is rather general and can be caused by a
number of situations. It can be from a software or hdw incompatiblity
problem.
You'll love this--It's generated when a kernel mode process or driver
attempts to access a memory location at an interrupt request level (IRQL)
that is to high or tries to access a memory location for which it doesn't
have permission.
Another way to say it is it happens when drivers use improper memory
addresses and (I especially like typing this) the driver you have installed
is "lazy." A lazy driver is a driver that doesn't clean up after itself
before exiting--just think the mess in Iraq.
Here's the practical point of this--if you find out from the Blue Screen
what the problem driver is, I'd look hard at the hardware recently
installed--it's probably a hdw driver although it icould be a software
driver. See if you can determine what driver is the problem and then find
out if there is any alternative driver, newer perhaps or an alternate one
that you can install or reinstall the driver you have.
You're better off if the driver is signed by Microsoft. You also might be
able to roll back the driver by accessing its properties in Device Manager--
type devmgmt.msc in the run box.
Here's the thing though that can be practical for you. ***You can use the
stop error (blue screen message) often to determine which driver is
offending if it is a driver problem.*** Remember, because people often
forget
or don't realize, software has drivers as well as hdw, and sometimes several
drivers are installed for a software program. Put "driververifier" (lose
quotes) in your run box and you'll get that idea.
Good luck,
CH
