• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 541
  • Last Modified:

DirectX 9.0b (and Nvidia FX 5200)

I recently re-installed XP because of a problem a problem I was having with Flight and Train Simulators, and subsequently DirectX 9. And I am experiencing exactly the same problem. DXDIAG is locking the computer completely while trying to display the Bouncing White Box in Full Screen Mode.
I have an NVidia FX 5200 with 128Mb of ram, if that's any help. The last time I used one of the simulators was about a month ago, and they were working perfectly up until then. Like DirectX, they also locked-up the computer just after they started.
Does anyone know what might be causing this rather annoying problem?
Thanks in advance.
0
terrymold
Asked:
terrymold
  • 4
  • 2
1 Solution
 
gemartiCommented:
Look in your event viewer for any errors related to your problem. Look in both the application and system log.

START | RUN | EVENTVWR.MSC

Post the SOURCE and EVENT ID for the errors you find.
0
 
terrymoldAuthor Commented:
I ran DXDIAG, which then locked the PC as previously mentioned. I then restarted and ran EVENTVWR.MSC, and this is what I got....

Type      Source      Event

Info      Tcpip      4201
Error      Disk      11
Error      Atapi      11
Error      Disk      11
Error      Disk      11
Error      Disk      11
Error      Disk      11
Error      Disk      11
Error      Disk      11
Error      Atapi      5
Error      Disk      11
Error      Disk      11
Error      Disk      11
Error      Disk      11
Info      Eventlog      6005
Info      Eventlog      6009
Error      Disk      11

Regards
Terry
0
 
gemartiCommented:
Well unfortunately those events don't seem to have anything to do with the DXDIAG tool or the errors it is generating.

Do you have LapLink installed on your system? It is known to cause problems with directX.

You may want to download and run this utility to test your memory:

+++++++++++++++
Windows Memory Diagnostic
http://oca.microsoft.com/en/windiag.asp

Exceprt:
The Windows Memory Diagnostic tests the Random Access Memory (RAM) on your computer for errors. The diagnostic includes a comprehensive set of memory tests. If you are experiencing problems while running Windows, you can use the diagnostic to determine whether the problems are caused by failing hardware, such as RAM or the memory system of your motherboard. Windows Memory Diagnostic is designed to be easy and fast. On most configurations, you can download the diagnostic, read the documentation, run the test and complete the first test pass in less than 30 minutes.


0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
terrymoldAuthor Commented:
I don't have LapLink installed and I have very recently run the Windows Memory Diagnostic program and it showed everything to be fine.
Could the problem be anything to do with the Video card, or it's drivers (I have the very latest driver for it.)?
0
 
terrymoldAuthor Commented:
Hi gemarti
I read somewhere that if you updated an Nvidia driver by installing new over old, it could cause problems.
So I uninstalled the Drive, reverting to a generic VGA driver.
While in that state, I checked DXDIAG and lo and behold, it went through all the tests OK.
I then re-installed the latest Drivers, the "proper" way, set everything up, and re-booted.
Then I ran DXDIAG again. And it LOCKED UP on the second white box test again. I'll explain exactly what happens in case someone recognises the symptoms.
Select Display.
Select Test DirectDraw.
It then displays Black and White Rectangles - OK.
It then displays a Bouncing White Box in a small window - OK.
It then displays a Bouncing White Box in Full Screen Mode - LOCKS UP with a stationary white box on a black screen.
At this point, I have to reset the computer.

Maybe this will help?
Regards
Terry
0
 
terrymoldAuthor Commented:
After lots of fiddling, I have managed to cure the problem. But I don't know EXACTLY what the cause of it was.

My PC is as follows:
AMD 2000+
VIA KT133A
512Mb Ram
Nvidia FX 5200 with 128Mb Ram
200Mb HD space

As mentioned, I updated the Nvidia driver from 56.64 to 56.73.
Last night, in a fit of inspiration, I re-installed the 43.45 driver which came with the PC. And it works again. No problems with DirectX. No problems with the two simulators.
When I have time, I am going to progress up through the driver versions to see which one DirectX plays up with.
So, there must be something about my exact combination that causes this conflict.

I hope this might be of interest to someone out there with a similar problem.
Terry
0
 
Computer101Commented:
PAQed, with points refunded (500)

Computer101
E-E Admin
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now