Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
In the past whenever ive installed a directx upgrade for windows me(8.0a) the only difference ive noticed is the loss of the animated pregame cinematics in AgeOfEmpires Conquerors Expansion. So i told myself i just wont update it anymore:). I got a new HD and cleanly installed full version of windows me last week. Ive been off work since christmas and i got a little bored so i decided to give 8.1 a shot. I downloaded it and double clicked the exe and heres my story....
I dont have any games installed just yet so i gave the dxdiagnostic a try. I ran it before the update and all the tests were good. After update i receive these errors:------------------
System Information
------------------
Time of this report: 12/29/2001, 08:28:29
Machine name:
Operating System: Microsoft Windows ME (4.90, Build 3000)
Language: English (Regional Setting: English)
System Manufacturer: 00101650 8760C
System Model: 15133500000250
BIOS: Award Medallion BIOS v6.0
Processor: Intel Pentium III, ~731MHz
Memory: 512MB RAM
Page File: 0MB used, 1536MB available
Primary File System: FAT32
DirectX Version: DirectX 8.1 (4.08.01.0881)
DX Setup Parameters: /PackageInstall
DxDiag Version: 4.08.01.0881 32bit------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
DirectDraw test results: Failure at step 7 (User verification of fullscreen bouncing): HRESULT = 0x00000000 (error code)
Direct3D test results: Failure at step 32 (User verification of Direct3D 7 rendering): HRESULT = 0x00000000 (error code)
Sound Tab 1: No problems found.
Music Tab: No problems found.
Input Tab: No input devices detected.
No problems found.
Network Tab: No problems found.
---------------
Display Devices
---------------
Card name: NVIDIA Vanta/Vanta LT
Manufacturer: NVIDIA
Chip type:
DAC type:
Device ID: Enum\PCI\VEN_10DE&DEV_002C&SUBSYS_80181043&REV_15\000800
Display Memory: 15.5 MB
Current Mode: 1024 x 768 (32 bit)(optimal refresh rate)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nvdisp.drv
Driver Version: 4.13.01.2183 (English)
DDI Version: 7
Driver Attributes: Final Retail
Driver Date/Size: 9/14/2001 16:52:00, 106976 bytes
Driver Signed: Yes
WHQL Date Stamp: n/a
VDD: *vdd
Mini VDD: nvmini.vxd
Mini VDD Date: , 0 bytes
Device Identifier: {D7B71E3E-436C-11CF-747B-19A0B7C2C935}
Vendor ID: 0x10DE
Device ID: 0x002C
SubSys ID: 0x80181043
Revision ID: 0x0015
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Failure at step 7 (User verification of fullscreen bouncing): HRESULT = 0x00000000 (error code)
D3D7 Test Result: Failure at step 32 (User verification of Direct3D 7 rendering): HRESULT = 0x00000000 (error code)
D3D8 Test Result: All tests were successful.What happens is when i run the diagnostic i get to the step where it tests full screen direct draw and the screen stays black no bouncing box.
When i attempt to test direct 3d i get the same black screen. I got a bsod once during the direct3d test(spinning cube i think) but didnt write down the error and i havent been able to reproduce it after 5 trys. This is exactly what happened when i attempted 8.0a in the past.Anyone have an idea what to do about this? Another way to install it? If i didnt include some required info let me know. Thanks for any response.

I dug this out of that longwinded nonsense above :)
Errors:DirectDraw test results: Failure at step 7 (User verification of fullscreen bouncing): HRESULT = 0x00000000 (error code)
Direct3D test results: Failure at step 32 (User verification of Direct3D 7 rendering): HRESULT = 0x00000000 (error code)

You can try using the most current drivers 23.11 (the 21.83 drivers were updated some time ago).
Short if that, I couldnt find any hits on betaplace. Try lowering the Hardware Acceleration (Performance Tab in Display in your Display Properties).

Something to consider - There is an item in the nVidia FAQ that relates to a "Black Screen" condition when running 3-D games.
They indicate that the refresh rate should be lowered.
Might try it, see what happens.

I had exactly the same problem when I installed a Creative NVidia GeForce 2 Pro on one system, but it didn't affect the games at all, so I just ignored it and it hasn't caused anything, but if you find a solution, please post back. By the way, I presume your 4 in 1 drivers are the latest. I've often found that to be a problem when upgrading Direct X.

I tried the lowering the refresh rate suggestion. I changed it from optimal to 60hz. The dxdiag tests still produce the same results but i did notice one thing. When i updated directx the text in windows dialogue boxes became slightly blurred. Changing the refresh rate has cleared this up.
I also found drivers for my monitor and installed them rather than using windows default drivers.Still no change.
Next was the via 4in1 drivers 4in1437v(a).zip. Ive never attempted this before because ive never experienced any problems in the past. I read the sites installation information and proceeded to run the "normal" install, unselected turbo agp. And said yes and next till install was complete. When the PC restarted i received this bsod:
"System Haulted device shell cannot find or load required file Krnl386.exe"
After restarting ran the step by step confirmation saying yes until an error occured. This is the bsod that followed:
"While initializing device VCOMM Windows Protection error. You need to restart your computer."
After this i tried it a couple more times and finally entered safe mode and uninstalled the via 4in1 patch.
Pc's back to normal.I know i missed something. Any ideas? Im going to search for the errors after posting this.

I went back to the viaarena site and read the installation instructions again to see if a missed something. I went to maxtor support to verify my hardrive supports dma and it does. I selected dma in device manager and restarted the computer. I receive the same error as before. This time without installing the via drivers. I entered safe mode and found i couldnt unselect dma in device manager as it wasnt an option. I decided to experiment and ran the via setup again choosing to uninstall again and windows is back to normal. I restarted/shutdown a few times to see if i could get the error to occur again but it hasnt. Now im really confused :).
I found an MSKB article about the krnl386.exe error but it says it relates to windows 98. Any thoughts about this before i attempt to troubleshoot with this article. Thanks.

Sorry for not mentioning this the first time because I presumed you would know, but have you checked you actually have VIA, rather than Intel chipset. If it's Intel download an updated ATA storage driver from http://support.intel.com/support/chipsets/driver.htm
You can find out by expanding the + mark beside system devices in device manager and if you have a whole load of VIA stuff at the bottom of the list, then you have VIA.
I have never had any problems with the 4-in-1 update so I can't be of much use there.

:) I do have a via chipset. This one
Click Me
I assumed the via installer checked the system for compatibility after reading this from the installer guide "The 4in1 drivers will automatically detect what drivers you need and will tick or check the boxes corresponding to the necessary drivers".I also read this at the download page "The 4in1 drivers are the same for all VIA chipsets and all Microsoft operating systems" This is why i decided to go ahead and run it.
Should i be using the via update for this chipset? I really have no idea here. One thing i did miss was the "if it an't broke don't fix it" Motto on vias site. I should have payed attention :).Ive decided to leave it be. My last task is Removing DirectX. From what ive read this is impossible. Is it impossible? Would system restore remove directX?
Heres the results of my experiment:
I learned alot about my system, i never knew the model of my monitor till now, i got the info from a tiny little sticker on back SA-986. google took me right to the driversforum. Popular opinion is that my monitor "sux":). My monitor finally has a name EMC.
I updated directx,via chipset,display driver,nvidia and found that things were better before any of it. If it aint broke.... I already knew this but couldnt resist.
Thanks for the help guys.

I don't know many of the details, but I had the same sort of error as I reloaded my system and updated to DirectX 8.1
I am about to re-format, start from scratch, and forget the update! The only other problem I'v had is when I updated the Sound Blaster PCI drivers, I lost my sound!

It's pretty much impossible to completely remove DX (and yes I know many folks have done so with the DX blasters freely available on the net). Microsoft had at one time provided me (after many hours of going back and forth - mostly bitching on my part) with a manual checklist to do so, but warned me that even "they" reformat and reinstall on 9x systems.
I did open a bug report to them. I'll post back what they return.

My Direct3D-Version is still 4.07.00.0700 and the rest is 4.08.01.0881. My new Game wants the DirctX 8, i installed it and there is still no Sound! I've got a Sound Blaster 2.0 and a Diamond Viper V550 (nVidia Riva TNT).
How can i solve the problem? Where can i get the Direct3D 4.08.01.0881? Send me a eMail!

Regarding your DirecctX 8.1 Error,
I also received the following errors:
DirectDraw test results: Failure at step 7 (User verification of fullscreen bouncing): HRESULT = 0x00000000 (error code)
Direct3D test results: Failure at step 32 (User verification of Direct3D 7 rendering): HRESULT = 0x00000000 (error code)After reinstalling drivers and tweaking all setting, it came down to the following solution:
-> set refresh rate to "adapter default" instead of optimal setting ...
Try this out.

Dan (the guy in the post above) hit the nail on the head - setting refresh to Adapter Default totally sorted my problem with Directx 8.1. Cheers Dan - short, simple, sweet solution to a mind boggling problem.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |