Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!
Results 1 to 10 of 10

Thread: loading windows drivers causes windows protection error




  1. #1
    Join Date
    Jan 2002
    Posts
    25

    Default

    Just tried clocking back to 100MHz fsb and the Det 23.12 drivers, but still get the win prot error when try to boot after installing DX8.1.



    about two weeks ago I started having problems geting past
    the boot after installing DX8.1.
    Using diagnostic boot I have narrowed the problem to where
    the windows drivers are loaded. While in safe mode I can,
    using diagnostic boot get back to safe mode in all
    combinations Except where the line ' Load all windows
    drivers' (no completes the diagnostic boot and continues
    back to safe mode, yes goes through the sequence finishing
    at msmouse.vxd where yes or no always results in lockup
    and the Windows protection error [even select no on all
    the next drivers still gets to msmouse.vxd whereafter it
    halts]- 'You need to restart your computer' [forced boot into
    safe mode then, with a change in the system.ini
    adding ;Rem TShoot: mouse=*vmouse and adding a line
    EMMExclude=C000-CFFF {each time i try to boot again it
    adds another C000-CFFF.}])
    Using an Elsa GF2 GTS 32MB vid card with either the elsa
    Gloria CD drivers (4.13.1.1241) or the Nvidia 27.50 or 30.82 drivers the
    PIII 700e W98.2 system will boot up to DX8.0 (from the
    DX6.1a that is with the w98.2 OS reinstall [the only way so far
    to get past that Windows protection error.])
    Enclosed is a copy of the DX8.0 successful DxDiag.exe test,
    System Information
    ------------------
    Time of this report: 8/21/2002, 00:26:35
    Machine name: ********
    Operating System: Microsoft Windows 98 (4.10, Build 2222) A
    Language: English (Regional Setting: English)
    System Manufacturer:
    System Model: Viewsonic GS815 monitor, Elsa Gladiac GF2 GTS, Aopen AX34 Pro II mobo (via vt 82c694b apollo pro 133 chipset)
    BIOS: Award Software International, Inc. 6.00 PG
    Processor: Intel Pentium III, 700MHz (o/c 806MHz), (o/c 115MHz fsb)
    Memory: 638MB RAM (256MB X2, 128MB PC-150 sdram)
    Page File: 41MB used, 1367MB available
    DirectX Version: DirectX 8.0 (4.08.00.0400)
    DX Setup Parameters: /PackageInstall
    DxDiag Version: 4.08.00.0400

    ------------
    DxDiag Notes
    ------------
    DirectX Files Tab: No problems found.
    Display Tab 1: The file nvdisp.drv is uncertified, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs. You may be able to get a certified driver from the manufacturer of the hardware device.
    DirectDraw test results: All tests were successful.
    Direct3D test results: All tests were successful.
    AGP texturing test results: All tests were successful.
    Sound Tab 1: The file smwdm.sys is uncertified, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs. You may be able to get a certified driver from the manufacturer of the hardware device.
    DirectSound test results: All tests were successful.
    Music Tab: DirectMusic test results: All tests were successful.
    Input Tab: No input devices detected.
    No problems found.
    Network Tab: No problems found.



    ---------------
    Display Devices
    ---------------
    Card name: ELSA GLADIAC GeForce2 GTS
    Manufacturer: ELSA
    Chip type: NVIDIA GeForce2 GTS Rev A
    DAC type: Internal
    Device ID: Enum\PCI\VEN_10DE&DEV_0150&SUBSYS_0C501048 &REV_A3\000800
    Display Memory: 31.5 MB
    Current Mode: 640 x 480 (8 bit)(optimal refresh rate)
    Monitor: ViewSonic GS815
    Monitor Max Res: 1920,1440
    Driver Name: nvdisp.drv
    Driver Version: 4.13.01.1241 (English)
    DDI Version: 8 (or higher)
    Driver Attributes: Final Retail
    Driver Date/Size: 6/6/2001 22:15:46, 105888 bytes
    Driver Certified: No
    WHQL Date Stamp: n/a
    VDD: *vdd
    Mini VDD: nvmini.vxd
    Mini VDD Date: , 0 bytes
    Device Identifier: {D7B71E3E-4210-11CF-2177-512C01C2C935}
    Vendor ID: 0x10DE
    Device ID: 0x0150
    SubSys ID: 0x0C501048
    Revision ID: 0x00A3
    Registry: OK
    DDraw Status: Enabled
    D3D Status: Enabled
    AGP Status: Enabled
    DDraw Test Result: All tests were successful.
    D3D Test Result: All tests were successful.
    AGP Test Result: All tests were successful.

    -------------
    Sound Devices
    -------------
    Description: SoundMAX Digital Audio
    Device ID: PCI\VEN_1106&DEV_3058&SUBSYS_30581106& REV_50\BUS_00&DEV_07&FUNC_05
    Manufacturer ID: 1
    Product ID: 100
    Type: WDM
    Driver Name: smwdm.sys
    Driver Version: 5.12.01.2509 (English)
    Driver Attributes: Final Retail
    Driver Certified: No
    Date and Size: 6/29/2000 10:51:52, 269432 bytes
    Other Files: smwdm.sys
    Driver Provider: Analog Devices
    HW Accel Level: Full
    Registry: OK
    Sound Test Result: All tests were successful.

    -----------
    DirectMusic
    -----------
    DLS Path: C:\WINDOWS\system32\drivers\gm.dls
    Version: 1.00.16.0002
    Ports:
    Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port
    SoundMAX Digital Audio, Software (Kernel Mode), Output, DLS, Internal
    MIDI Mapper, Hardware (Not Kernel Mode), Output, No DLS, Internal
    Microsoft GS Wavetable SW Synth, Hardware (Not Kernel Mode), Output, No DLS, Internal
    Roland MPU-401, Hardware (Not Kernel Mode), Output, No DLS, External
    Roland MPU-401, Hardware (Not Kernel Mode), Input, No DLS, External
    Registry: OK
    Music Test Result: All tests were successful.

    -------------
    Input Devices
    -------------
    Poll w/ Interrupt: Yes
    Registry: OK

    -------------

    Input Drivers
    -------------
    Registry Key: msjstick.drv<0014>
    Active: No
    DeviceID: VIAUDIO\*PNPB02F\0001PCI&VEN_1106&DEV_3058 &SUBSYS_30581106&REV_50&BUS_00&DEV _07&FUNC_05
    Matching DevID: PCI\VEN_1106&DEV_3058&SUBSYS_30581106
    16-bit Driver: msjstick.drv
    32-bit Driver: viaudio.vxd

    Registry Key: msjstick.drv<0015>
    Active: Yes
    DeviceID: VIAUDIO\*PNPB02F\0001PCI&VEN_1106&DEV_3058 &SUBSYS_30581106&REV_50&BUS_00&DEV _07&FUNC_05
    Matching DevID: PCI\VEN_1106&DEV_3058&SUBSYS_30581106
    16-bit Driver: msjstick.drv
    32-bit Driver: viaudio.SYS

    Registry Key: msjstick.drv<0023>
    Active: Yes
    DeviceID: VIAUDIO\*PNPB02F\0001PCI&VEN_1106&DEV_3058 &SUBSYS_30581106&REV_50&BUS_00&DEV _07&FUNC_05
    Matching DevID: *PNPB02F
    16-bit Driver: msjstick.drv
    32-bit Driver: vjoyd.vxd


    ----------------------------
    DirectPlay Service Providers
    ----------------------------
    Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (4.08.00.0400)
    Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (4.08.00.0400)
    Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (4.08.00.0400)
    IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (4.08.00.0400)
    DirectPlay8 IPX Service Provider - Registry: OK, File: dpnwsock.dll (4.08.00.0400)
    DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnwsock.dll (4.08.00.0400)
    DirectPlay8 Modem Service Provider - Registry: OK, File: dpnmodem.dll (4.08.00.0400)
    DirectPlay8 Serial Service Provider - Registry: OK, File: dpnmodem.dll (4.08.00.0400)
    DirectPlay Test Result:

    -------------------------
    DirectPlay Lobbyable Apps
    -------------------------

    ------------------------------------
    Inactive Display Entries in Registry
    ------------------------------------
    Card name: ELSA GLADIAC
    Driver: ELSAGDAD.DRV
    Card name:
    Card name:
    Card name:
    Card name:
    Card name:
    Card name:
    Card name:
    Card name:
    Card name: NVIDIA GeForce2 GTS/GeForce2 Pro
    Driver: nvdisp.drv

    ----------------------------------
    Inactive Sound Entries in Registry
    ----------------------------------
    Card name: VIA PCI Audio controller
    Driver: viawave.drv
    Card name: VIA AC'97 Audio Controller (WDM)
    Driver: wdmaud.drv
    Card name: VIA AC'97 Audio Controller (WDM)
    Driver: wdmaud.drv

  2. #2
    Join Date
    Nov 2001
    Posts
    4,723

    Default

    I've been doing some searching and pondering this a bit.
    In all honesty I haven't found anything concrete as to either a cause or a fix for this.

    I'm wondering if perhaps you got a DX8.1 with a corrupt file or maybe a file was corrupted during the install???

    You could try reinstalling the package from another source and see what happens???

    As DirectX8.1 is so hardwired as to be all but un-installable (at least I do remember there are claims of software that uninstalls it - but am not sure how well it works). The only other option I could offer is the ol' reformat and reinstall.

    Hopefully, this will put your post back to the top and someone will know more on this than I.
    The reason a diamond shines so brightly is because it has many facets which reflect light.

  3. #3
    Join Date
    Nov 2001
    Location
    Texas, USA
    Posts
    4,825

    Default

    Is it possible that this DirectX installation is just the straw that broke the camels back? Here's what I mean:

    Memory: 638MB RAM (256MB X2, 128MB PC-150 sdram)
    On a Windows9x system, anything over 256MB of memory tends to play havoc on the setup. It simply is not designed to effectively handle any more than this. I will say right up front that it says a lot about your fine tuning abilities to have kept the system running with 638MB. But maybe it has finally met it's match?

    Just thinking out loud here.
    Old age and treachery will overcome youth and skill
    My Toys

  4. #4
    Join Date
    Jan 2002
    Posts
    25

    Default

    :cool:
    tried option #2 on the boot screen (bootlog.txt) and tried booting again, with the usual halt and the windows protection error black screen.
    Booting back into safe mode, went into the C drive to review the bootlog.txt file. The last line was mention of a joystick, so, went into device manager/sound, video and game controllers then removed the entry gameport joystick then booted computer.
    This time in the boot process it pops up installing new hardware and the window asking for a file on the w98.2 CD, did that and the boot continued into normal display screen. Checked device manager and the gameport joystick had been reinstalled.
    Aparently trying the MS sidewinder briefly 2 yeqars ago left remnant drivers that within the last 3 weeks became corrupted and installing the DX8.1 again finally caused a w prot error.
    But now the system boots ok with DX8.1b + Det 23.12drivers (the 23.12 seem to have beter #s than 30.82.)
    Btw, in my researching I noticed the Det 30.82 are whql so likely not good on o/c systems.
    Fixing computers is sooo easy once u know what is messed up!
    I was about two more boots with that black screen and w prot error from reformating my hd for a try at a total fresh install! And was convinced MS was sabatoging my w98.2 OS since it now refuses to have anything to do with it other than recomend buying the $300 wxp pro. I will buy a GF4 Ti4400 & PIV 2.5GHz before I will buy wxp. Although I really want to see a comparison of the 9700 & the nv30.

  5. #5
    Join Date
    Jul 2002
    Posts
    0

    Default

    :D Good news bug. Be persistent. Those left over drivers are a pain in the backside.

  6. #6
    Join Date
    Jan 2002
    Posts
    25

    Default

    fixing w98.2 to accept < 1GB memory is easy.
    Just edit system.ini [vcache] to MaxFileCache=524288 and minfilecache=32768 and chuncksize=2048
    Reference to these edits:
    http://www.aumha.org/a/memmgmt.php
    http://support.microsoft.com/support.../q253/9/12.asp

    for uninstalling DX on w98.2 system I use dxuninstaller ver 12 from http://www2.driverguide.com/uploads/uploads9/31675.html be sure to read it's read-me file for usage instructions.

    Detonator destroyer ( http://guru3d.com/detonator-destroyer/ )
    nv cleaner ( www.geforcefaq.com/files/cleaninstall.zip )
    are both good for purging older det versions (and thereby avoiding version conflicts with newer same named files.)

  7. #7
    Join Date
    Jul 2002
    Posts
    0

    Default

    Great links there bug. Thanks.

  8. #8
    Join Date
    Nov 2001
    Posts
    4,723

    Default

    bug you have remarkable detecting skills and quite the stick-to-it attitude. Glad to hear you got it working.

    I have to wonder though if indeed it might be time for that format and clean install - 2 year old drivers won't be a problem then and surely it would put a bit of pep back into that system.
    The reason a diamond shines so brightly is because it has many facets which reflect light.

  9. #9
    Join Date
    Nov 2001
    Location
    New England Highlands, Australia
    Posts
    21,907

    Default

    Yes there are ways to trick 98 into using large amounts of memory it the system will boot (a lot won't though once you pass 512MB though).

    The DX removers usually cause more trouble than they're worth, now and again they will be successful but not often.

    Detonator Destroyer is very popular around here though. :D


  10. #10
    Join Date
    Nov 2001
    Posts
    4,723

    Default

    Quote Originally Posted by bug
    fixing w98.2 to accept < 1GB memory is easy.
    Getting the OS to properly utilize amounts in excess of 256Mb is another matter entirely.
    The reason a diamond shines so brightly is because it has many facets which reflect light.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •