|
|
 |
|
|
Pages: 1
Problems running D2 in Direct3D
(Click here to view the original thread with full colors/images)
Posted by: phoenix
I have:
Creative RIVA TNT
Pentium II 350, 64 Mb RAM
Windows 98 SE
Updated RIVA TNT graphic card drivers
DirectX 8.0
Diablo II 1.03
When I run D2VidTst.exe it shows several popup windows named "D2VideoTest Exception" with the error "UNHANDLED EXCEPTION ACCESS_VIOLATION(c0000005)" both when testing DirectDraw and Direct3D. If I run Diablo2 with DirectDraw everything works fine but if I run it with Direct3D, Diablo2 shows at startup(only at startup) the same UNHANDLED EXCEPTION error windows, and I if I'm running DiabloII and switch to another application (with ALT-Tab) and return to Diablo2, the Diablo2 screen turns black forever ( the game wont crash though, I can still use the keys to navigate, like ESC).
This happens the same with both the NVIDIA drivers ( W9X-631.zip driver version: 9/20/2000) or the Creative Drivers ( NTAW9X.exe driver version 06/26/2000 ) or the Web Update Creative Drivers (3ddb9xdrv_634.exe driver version 10/20/2000 )
In the attachment is a D2 txt file with the debug information when running Diablo II in Direct3D.
Please help me, I wish to run Diablo2 in Directd3D and be able to ALT-TAB betwen applications.
Bruno Medeiros
Posted by: Canis Lupus
Hello phoenix.
You may want to read the FAQ written up by Ion Silverbolt and see if any of his suggestions can help you:
Unhandled Exception:Access Violation (c0000005) Crash Help
Diablo II has been notorious for not getting along with nVidia drivers, and it is still a long-standing problem that Blizz hasn't totally solved yet.
Try the FAQ and see if you can find anything there that helps you. And I think you forgot to actually attach your D2 debug file to your post.
Post back if you still have problems, and be sure to include the text file...
Posted by: phoenix
 Quote:
Originally posted by Canis Lupus:
Hello phoenix.
You may want to read the FAQ written up by Ion Silverbolt and see if any of his suggestions can help you:
Unhandled Exception:Access Violation (c0000005) Crash Help
Diablo II has been notorious for not getting along with nVidia drivers, and it is still a long-standing problem that Blizz hasn't totally solved yet.
Try the FAQ and see if you can find anything there that helps you. And I think you forgot to actually attach your D2 debug file to your post.
Post back if you still have problems, and be sure to include the text file...
|
Actually I have already read that FAQ, but my problem is not a crash that ocasionaly happens when running Direct3D. Those error messages are displayed only at startup and DiabloII doesnt crash afterwards, it runs normally in Direct3D except for the ALT-TAB problem mentioned before.
If you still think the FAQ solutions might be relevent to this problem I'll try them, but i have the feeling its something else mentioned in the FAQ.
I think the debug file is now correctly attached.
The Phoenix
Posted by: Ion Silverbolt
Diablo II is a very system stressing application. Since you only have 64 megs, it might help to do everything you can to free up available memory. Also, there's some things for video that might help.
[*]Hit CTRL+ALT+DEL and shut down all extra programs in the list except systray, explorer, rnaapp, and point32 if you have it. This will help free up resources and the game should run better.
[*]In your BIOS, disable video shadowing and caching for your video card. This will free up some memory as well and your video card may run more stable.
[*]For your ALT+TAB problem, try setting your display settings to 640X480, 256 colors before playing Diablo II. That should keep the screen from going blank at least.
[*]You have the latest drivers, but what about the latest BIOS? You may want to look in to see if there is a BIOS update for both your video card, and your motherboard. Sometimes BIOS updates take care of various problems with video cards.
[*]You may get better performance with a program called MemTurbo. IT will help free up more RAM for the game and take care of memory leaks.
MemTurbo Memory defragger.
Post back if you need more help. The c0000005 Guide may help you a bit as well.
------------------
©2000 Ionic Computer Services.
Posted by: Ion Silverbolt
debug text file you attached seems to point to the D2CMP.DLL file in the Diablo II folder a lot. If nothing above helps you , you might try copying that file off the Diablo II CD again in case the one in the Diablo II folder is corrupted.
Keep in touch. The c0000005 Guide has some tips in it about memory. I think that may help you some.
------------------
©2000 Ionic Computer Services.
Posted by: phoenix
I did everything you told me except upgrading the BIOS(didnt get the patch yet).
I disabled shadow and caching.
RIVA TNT BIOS is the latest version.
Used CTRL-ALT-DEL to close all aplications
Used the MemTurbo program.
There's no D2CMP.DLL file in the D2 CD's so I reinstalled D2.
It didn't work however, all errors still occur. I somehow don't think this is a memory related problem. Maybe its just a bug in D2 itself.
A sugestion: send me your D2CMP.DLL , perhaps my CD has some error that makes that file corrupt (unlikely tought)
Know this, however: the main problem I want to get fixed is the ALT-TAB problem. I just mentioned the UNHANDLED EXCEPTION errors because I tought they were in the origin of the TABing problem. If they are not, then we can pretty much forget about the errors. Hell, I have plenty of games that show error messages or do ilegal operations on startup.
I tried to run D2 at modes 640x480x256 and 800x600x256, and it worked, I was able to TAB betwen applications. However these modes suck, and I want to use the desktop at a higher resolution and bitdepth( so I can use ICQ, or mIRC, or Roger Wiclo, or whatever) so please help me.
I have attached a debug file created after all of that changes. It also includes debug from D2VideoTest.
The Phoenix
Posted by: Ion Silverbolt
I'm not really qualified to read those text files. BLizzard designed it..hehe I can only make a guess.
I think this is a driver issue all the way. Diablo 2 is not fond of NVidia based cards. A lot of users have better luck with the Detonator 2 drivers for TNT and TNT2 based cards. They also perform better than the newer drivers. The newer drivers are more optimized for GeForce cards. I suggest you try the 5.22 version drivers. You can grab them here.
If that don't help, you might try other things in the c0000005 Guide that are easy to do.
Keep in mind that for some users, there is no definite fix. Blizzard is supposed to address this error more in the 1.04 patch that is due out soon. I hope the 5.22 drivers help you out. A lot of people prefer them as they're one of the most stable of the Detonator drivers NVidia has released.
------------------
©2000 Ionic Computer Services.
Posted by: phoenix
I installed the W9x-522 drivers and (unexpectantly) something changed! Instead of displaying 5 "UNHANDLED EXCEPTION c000005" errors as it allways did, D2 showed 3 "UNHANDLED EXCEPTION c000005" errors and one "ILLEGAL OPERATION c00001d" error . But surprised was I when I quitted Diablo2 and ran it again, and no errors were displayed on this second run. I quit and ran D2 a third and forth time, and there were no errors. More surprised was I when I found I could successfully ALT-TAB between D2 and the desktop, no matter at wich resolution/bitdepth the desktop was.
I then restarted the computer in order to repeat this experiment: Again, the first time I would run Diablo it would display the startup errors and the D2 screen would turn black if I tried to ALT-TAB, but all subsequent runs would work fine - no errors and I could ALT-TAB .
I then tried to install another driver, to find out if this change was indeed caused by the W9x-522 driver. I tried the 3db9xdrv_634 and w9x-631 drivers - Diablo2 displayed the 5 "UNHANDLED EXCEPTION c000005" errors in all runs, and I was unable to ALT-TAB successfully.
Knowing now that the W9x-522 drivers was indeed the cause of these changes, I proceeded to installing them again.
One thing to note though, the W9x-522 drivers had to be installed exactly like described in the readme file, that is, first you change the graphic card drivers to Standart PCI Graphics Adapter(VGA) and reboot and then change the graphic card drivers to those of the W9x-522 drivers and reboot.
If I tried to directly change the graphic card drivers to those of the W9x-522 drivers and reboot, without first changing the graphic card drivers to Standart PCI Graphics Adapter(VGA), Diablo2 would run the following way:
First run: 2 "UNHANDLED EXCEPTION c000005" and 2 "ILLEGAL OPERATION c00001d" errors
Second run: 2 "UNHANDLED EXCEPTION c000005" errors
Third run: Diablo2 crashed the system.
Well, now this problem is fixed, thank you for the help.
The Phoenix
Posted by: Ion Silverbolt
Sounds like a definate driver problem. http://www.opentechsupport.net/forums/smile.gif A lot of users have to use the 5.22 drivers to run Diablo II stable. It's really a shame there are so many problems between Diablo II and NVidia cards. Some say it's NVidias fault and others say Blizzards.
I just with one of them would address the problem with a driver or patch! http://www.opentechsupport.net/forums/smile.gif
Glad you're able to get it running better at least.
------------------
©2000 Ionic Computer Services.
|
|
|
|
|
