All games crash

[Darkandlight]

Hey all,
I have recently built a new PC, which went smooth, and have installed my initial lineup of games. I am running a Sapphire Radeon 9000 pro and have upgraded to the latest drivers (catalyst 3.2 or whatnot). I am running Win XP home. UT2003, Unreal Tournament (original), Neverwinter Nights, and Freelancer all experience spontaneous crashes back to Windows. Some show an error spouting a "General Protection Fault". While others no erro message is displayed. I am running DirectX 9.0. Does anyone have any ideas about this? Thanks

[Force Flow]

Are you sure you're running DX9 and not DX9a?

Are there any conflicts in your device manager?

[ktkendall]

What sound card do U have. In my limited experience symptoms such as yours where games seem to be the 1 thing having trouble running smoothly, it has either been video or sound related. You video sure looks to be up to date, so I would wonder about the sound. when it gives you the General Protection Fault, does it name any files or modules that are causing it??

[Darkandlight]

This is the error screen:


UT2003 Build UT2003_Build_[2003-02-13_18.53]

OS: Windows XP 5.1 (Build: 2600)
CPU: AuthenticAMD PentiumPro-class processor @ 1702 MHz with 511MB RAM
Video: SAPPHIRE RADEON 9000 ATLANTIS PRO (6200)

General protection fault!

History: FMallocWindows::Realloc <- 29FB4200 3120 FArray <- FArray::Realloc <- 78*40 <- UShadowBitmapMaterial::Get <- FD3DRenderInterface::SetProjectorMaterial <- FD3DRenderInterface::SetMaterial <- RenderStaticMesh <- FDynamicActor::Render <- RenderLevel <- FLevelSceneNode::Render <- FPlayerSceneNode::Render <- UGameEngine:raw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- UpdateWorld <- MainLoop

[Force Flow]

Lol, I wonder how many people can actually read the gobbledy-gook.

What sound card do you have? (or is it onboard?) What's your motherboard?

[pam123]

Typing " History:... etc. "into the Knowledge Base didn't get an answer.
Can you open the event viewer thing and see what else is there?
You want the stuff that starts : Stop: 0x000.... and so forth.
The M$ Knowledge Base can then pinpoint the error when the code is typed in.
If it's always happening in the same place, a memory module for instance, you may have a hardware problem.
If it's drifting around it's probably software.