it could be just about anything
bad memory
overheating
bad card, incorrectly seated
damaged software
bad software
Its impossible to help you without getting sheer luck in guessing whats causing it, if you do the "submit info to MS" does it give you any clues?
also if you get the full dump of the error, that'd help more (possibly not much though ) usually it shows you in the "what is contained in this message)
Also if you do have a debugger (usually vc or .net) let it go in and just see what the call trace is..
If its nearly always the same address, its quite unlikely to be overheating or memory problems, thats usually bad software..
Try a spyware / virus scan too. some stuff hooks in badly
|