In some DOS games, after playing them for a little bit, they cause WinXP to BSoD. Does anyone know what causes this and how to avoid this?
well who knows those games, which you fail to mention, cause some problems with your hardware which you fail to mention.
Currently I'm having trouble with CyberJudas, and my hardware is an Asus V266-A MB, I have 768 MB of DDR RAM, I have an 80 GB SeaGate and a 60 GB Wester Digital. I have a GeForce 3 by VIsion Tek, an SB Audigy, an Ethernet card, I have an ATI TV turner and I believe that is it.
A DOS title bringing the OS to the BSOD? That should almost never happen. If it is, more likely there is a problem with the OS itself.
To be on the safe side, open a Explorer window, click on the "Tools" menu item, click on "Folder Options", click the "View" tab, then scroll to the bottom of the options and make sure "Launch folder windows in a separate process". That at least will provide for another layer of "insulation".
Thanx, I'll see how well that works.😀
No dice
Originally posted by Unregistered Thanx, I'll see how well that works.
Well that wasn't meant as a "fix" to prevent the game from crashing, just to help protect the rest of the OS from being affected when it goes "boom".
If I can find my CD, I'll give it a shot.
I think I found the problem. I disabled Windows File Protection.
Originally posted by Unregistered I disabled Windows File Protection.
If you meant "Read-only" set on the game files, that might make sense, but if you mean Windows File Protection meant to protect system files, it doesn't. It also makes your system more vulnerable to "bad things".
He should test his memory/sound, or his processor.
If it's sound it's likely ACPI compliance.
NTVDM stress sound and memory. So if he's overclockin' or had bad memory then that could be the culprit.
I don't overclock, and the same trouble happened without using NTVDM. And my memory passes the test.
Your memory passes which test? If it is not http://www.memtest86.com/ you tested with, don't be too sure,
Also I had many bluescreens because of bad Soundblaster drivers and/or bad memory. As I read you have an Audigy and those drivers were my problem. So try to get the latest it may improve your stability (or not 😀)
When your Xp bluescreens what does it say? Most of the time it gives some hint on what the problem is. Lookout for mentioning of some .sys file. If one gets mentioned look that sys file up in Windows\system32\drivers\. In the properties you can learn what the driver is for and who made it.
It usually says NTFS.sys or Win32.sys.
Win32.sys? Could be in XP, but I don't see it here in Windows 2000. Are you sure you don't mean, like, KERNEL32.DLL? Also, seeing NTFS.SYS giving BSODs is a bad sign. Like, bad sectors, hard drive is failing, back up your data NOW kind of sign. Unless the specific error comes when you're booting your computer and it is "INVALID_BOOT_DEVICE", in which case it's Windows being stupid.
In any case, I think your problem could be far more serious than it seems. Run a SCANDISK on both your drives.
Yes, it’s my fault.
Clean bill of health on the drives. I think I'll give up, what is displayed in the BSoD isn't usually what caused it, but the end result of bad coding or some king of conflict.
Originally posted by Unregistered ...but the end result of bad coding or some king of conflict.
That might make sense in Win9x, it doesn't for XP. I've deliberately run programs that I knew would crash horribly just to see how resilient the OS was. Maybe two times since I installed it have I seen the kind of thing you described (over a year of constant use).
Something's not right with your OS. Keep an eye out for further "bad behavior".
