Computing.Net > Forums > Windows 95/98 > ntkern/mmdevldr.vxd error wSoundMAX

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

ntkern/mmdevldr.vxd error wSoundMAX

Reply to Message Icon

Name: cudak888
Date: June 29, 2007 at 15:44:08 Pacific
OS: 98SE
CPU/Ram: Celeron/256mb
Product: Intel D815EEA
Comment:

Yep, I know this one has been asked many times before, but I have yet to find an answer.

I have an Intel D815EEA board here with a built-in SoundMAX (not the Creative) sound card. I recently built it into a box running Windows 98SE on it.

So far, all the drivers for the onboard hardware has loaded fine - except for the SoundMax 2.0 drivers. Without fail, they will appear in the Device Manager with the dreaded yellow exclamation mark, stating the following:

"The ntkern.vxd, mmdevldr.vxd device loader(s) for this device could not load the device driver. (Code 2)"

Removing the driver from Device Manger completely and rebooting has not solved the problem, neither has re-installing the SoundMax 2.0 drivers and software (EA_SM2_A.exe w/the Windows 242937USA8 update) resulted in any joy either. Same results for an attempt to install the SoundMAX driver after installing the Windows 98SE Unofficial Update 2.1 package, and after a re-installing 98SE. No luck. Tried coping the two offending files out of the Windows 98SE .cab files, and pasting them into Windows\System and Windows\System\vcm, no-go on that as well.

I also tried dumping ALL the sound-related items in the Device Manager and re-detecting them, needless to say, that didn't work either.

So far, I believe I have covered just about all bases that I've found through Googling previous discussions about this problem (I probably forgot to list a few as well), and I must honestly say I am stumped.

One thing that does catch my attention though is that the "MPU-301 Compatible" Roland MIDI controller has an IRQ of 05 - shouldn't this IRQ setting be for the SoundMAX card, not the MIDI controller?

Any input and help will be greatly appreciated. So far, I've never run into a problem that I haven't ultimately fixed, and if possible, I'd like to beat this one too (although it is giving me a nice run for the money).

Take care,

-Kurt



Sponsored Link
Ads by Google

Response Number 1
Name: Derek
Date: June 29, 2007 at 16:18:55 Pacific
Reply:

Wow, you've covered some ground there (which leaves little for me to suggest at any rate).

The one place I would have tried putting ntkern.vxd (not the other file) would have been c:\windows\system\vmm32

You probably already know that ntkern.vxd is contained within the compressed file vmm32.vxd but if you put ntkern.vxd in the location given (vmm32) it will pick it up from there rather than the compressed file. I would be inclined to temporarily remove it from the other locations to force it to look in vmm32

I have nothing against it being inside vmm32.vxd it's just that for some quirky reason it might find it more readily as a stand alone file.

If that doesn't help then keeping the file in vmm32, remove the CP entry as before, reboot and see if that helps.

If this makes no difference then I haven't a clue what else to suggest, although I might glare at this post again longing for some inspiration.

DerekW


0

Response Number 2
Name: cudak888
Date: June 29, 2007 at 17:21:33 Pacific
Reply:

Hello Derek,

Thanks for the reply. Turns out I had NTKERN.VXD in c:\windows\system\vmm32 as well - just forgot about it. I also found that I had a copy in c:\windows\system, so I dumped that one, and tried dumping and re-detecting the driver again. Once again, no luck.

By the way, here's something to throw into the mix: I just remembered that I did have this card working once - only once. Once, in the midst of these VXD errors, I DID get it to work.

I celebrated by enjoying Flight Sim '98 (what better on 98SE?) for an hour afterwards, spent 15 minutes looking about at the SoundMAX control panel, went to sleep, woke up the next morning to find no sound to greet me that morning.

P.S.: Here is the current list of drivers being used by the card:

c:\windows\system\smwdm.sys
c:\windows\system\vmm32\ntkern.vxd
c:\windows\system\mmdevldr.vxd
c:\windows\system32\drivers\smwdm.sys

Take care,

-Kurt


0

Response Number 3
Name: Derek
Date: June 29, 2007 at 17:42:02 Pacific
Reply:

Nah, I'm stumped too. I did wonder about hardware (as you managed to get it to work once) but with onboard sound that doesn't help much.

RAM can cause some weird effects, especially those darned edge connectors but it's hard to see why this should single out sound. Could try the clean rubber pencil eraser trick on them I suppose but I will understand if you think that is too off beam to even bother trying.

Clutching at all straws, have you checked for newer sound drivers? Even if the ones you have are OK reloading newer ones might kick it into submission.

Maybe someone else will have some ideas.

DerekW


0

Response Number 4
Name: DAVEINCAPS
Date: June 29, 2007 at 17:50:45 Pacific
Reply:

Are there any older soundmax drivers available on the intel site? Also I think there may be AC97 drivers that will work but I wouldn't know where to direct you for that.

Did you install the motherboard/chipset drivers?


0

Response Number 5
Name: cudak888
Date: June 29, 2007 at 18:06:12 Pacific
Reply:

Derek: Well, I can give the SoundMAX 3.0 drivers a whack, but the only ones I've found online, so far, are for a BCM mobo.

DAVE: Only drivers available at the Intel site are the SoundMAX 2.0's under EA_SM2_A.exe, and the Creative drivers for the boards using the Creative chip (which I've already determined is not the case with mine). All of the Intel drivers are installed.

Take care,

-Kurt


0

Related Posts

See More



Response Number 6
Name: cudak888
Date: June 29, 2007 at 18:32:44 Pacific
Reply:

Just tried the SoundMAX 3.0 drivers for the heck of it. No luck.

Take care,

-Kurt


0

Response Number 7
Name: cudak888
Date: June 29, 2007 at 18:41:48 Pacific
Reply:

David: I just gave Driverguide a quick search for the AC97 drivers. Curiously, are the AC97s a VIA chip?

Seems to be anyway, as I seem to be pulling up nothing but VIA drivers (I gather that this is a VIA CHIP, not something written exclusively for a VIA board - don't want to screw things up more then they already are), although there is one codec that specifies itself as being suitable for an Intel 810/E.

Take care,

-Kurt


0

Response Number 8
Name: DAVEINCAPS
Date: June 29, 2007 at 21:18:28 Pacific
Reply:

VIA drivers aren't going to work.

It looks like that board comes with either the creative 1373 chip or the ADI 1885 AC97 audio codec. You indicate you have the latter. SoundMax is one of the systems that can use that hardware. There's some info here:

http://www.soundmax.com/products/fa...

There are VIA AC97 audio codec chips. But you don't have one of those.

Drivers meant to work with the ADI 1885 should be enough to get the audio going. SoundMax I guess is just a little bit fancier setup.

I found this download page for another Intel board:

http://downloadcenter.intel.com/fil...

It's got a basic ADI driver download and one specifically for the 1885 chip. Either one might work with yours.

Also, you need to make sure you uninstall any previous drivers before installing new ones.



0

Response Number 9
Name: cudak888
Date: June 30, 2007 at 09:55:00 Pacific
Reply:

Hello Dave,

Thank you for those links. Just tried both with the typical resut.

For the record, both were essentially SoundMAX installations - the basic version included the 1.0 (?) drivers, the other is v3.0.

One thing I did notice is that the SoundMAX MIDI controls will open - in the previous installations, the SoundMAX Control Panel would blink open for a second, then vanish. Further attempts to open the SoundMAX controls would only result in a quick blink of the hourglass, and no further action (except for the one time it did install correctly, in which case, the controls did open).

Considering that I've completely nuked every single driver install before installing the following driver, could there be a possibility that this problem relates to a system file that is not installed by the SoundMAX installation setup, and is not affected by a re-installation of Windows?

The only other thing I can think of is if the SoundMAX installation program is not installing all the files sufficiently, although this would not explain why I had the sound working once.

Let me know what you fellows think.

Take care,

-Kurt


0

Response Number 10
Name: DAVEINCAPS
Date: June 30, 2007 at 12:31:41 Pacific
Reply:

I suppose there could be a hardware problem with the sound. You may want to make sure all the audio stuff is enabled in cmos/bios setup. It might also be a resource conflict. The explanation given by 98 in device manager doesn't necessarily tell you everything you need to know. Also have you upgraded DirectX?

Was your windows reinstall an over-the-top or a fresh installation on a newly formatted drive? If it was a fresh installation you may want to try it again. Install windows, then the chipset drivers, then upgrade DirectX. Install the Windows Installer:

http://www.microsoft.com/downloads/...

Don't worry about any of the other updates, at least not yet. Try the soundMax again. You can try temporarily removing unneeded cards like NIC or modem until you get the sound set up, in case there's a resource conflict.


0

Response Number 11
Name: cudak888
Date: June 30, 2007 at 13:23:15 Pacific
Reply:

Hello Dave,

I'll check the BIOS, although I believe the sound-related settings were all enabled the last time I looked. Won't hurt to poke my nose in it again though.

I upgraded to DirectX 9.0 on this machine - 9.0b if I recall right, but I do not recall definitely (don't know why I didn't bother to remember this detail) - have to check.

My install was an over-the-top. The unit has an installation of MS Office '97 on it, and I'd like to keep it there - if possible - for I do not have a replacement CD for it.

There are no add-on cards installed in the unit. Other then the usual, the only other built-in hardware on it is an Ethernet port, VGA port, and a serial game port.

I'll give the BIOS check a try, along with the Windows Installer - certainly sounds like a good utility to check the installation of the SoundMAX drivers and software.

Take care,

-Kurt


0

Response Number 12
Name: cudak888
Date: July 1, 2007 at 10:46:28 Pacific
Reply:

Howdy Dave,

BIOS checked out fine - sound is enabled, and all other related settings are fine as well.

Following that, I tried installing the Windows Installer utility, only for it to refuse to install - the error upon opening the .exe ran something to the extent that the package had already been installed.

I checked this out on a few sites, and found which files caused THAT problem. It took care of the initial error I received, but I can't find any evidence of the Installer actually having been installed on the system - no shortcuts, nothing in the Control Panel, and same for the Add/Remove Programs list.

Curiously, would the Windows Installer give us enough information about the sound card installation that it is worth the effort to try and get it to install properly? I personally have never used the utility before, hence why I ask.

Take care,

-Kurt


0

Response Number 13
Name: DAVEINCAPS
Date: July 1, 2007 at 12:26:59 Pacific
Reply:

It's possible the installer was installed (gotta use a thesaurus) by another piece of software that needed it, or one of the updates. It's just not something that comes on the 98 cd so it needs to be installed from another source. So if you're getting the message it's already installed then it probably is.

As far as I know the windows installer comes up automatically when installing new software. I don't think it's any sort of diagnostic software. But then I haven't really looked that closely at it either.

Assuming the audio hardware is OK I think it's a resource problem--soundmax can't find places to load the files it needs--and of course that's just a guess. Sometimes you can manually change settings for other hardware in device manager but that can cause more problems.

Check in bios setup again. If there's an option for PnP OS, enable it. Or if it's already enabled, disable it. Enabling PnP OS gives windows more leeway in setting up the hardware. You could also try temporarily disabling the on-board NIC and then see if you can set up soundmax.

If all else fails, and not having a replacement office 97 cd is the only thing keeping you from reformatting, I can send you one.


0

Response Number 14
Name: cudak888
Date: July 1, 2007 at 17:05:05 Pacific
Reply:

Hello Dave,

I'd put a guess that the 98SE Unofficial Service Pack put the Installer on the system, but I have yet to see evidence of it by means of it popping up during installations.

PnP BIOS is enabled.

One thing: I finally got a look at the DirectX version I have, and was quite surprised to find v8.1 sitting in my system. More so, I came across one reference to this problem having been a culprit of a DirectX 8.1 installation, ultimately cured by DirectX v9.0c.

Needless to say, in the meantime, I've been trying to install DirectX 9.0c, which is proving to be its own Pandora's Box. You'd think MS can't keep something SIMPLE for a change, eh?

-Kurt


0

Response Number 15
Name: cudak888
Date: July 1, 2007 at 17:09:28 Pacific
Reply:

P.S.: Those DirectX 9.0c problems are mainly that of an illegal operation error during unpacking of the .exe (I downloaded the full package).

Incidentally, thank you VERY much for the offer on the CD. I might take you up on it.

Take care,

-Kurt


0

Response Number 16
Name: DAVEINCAPS
Date: July 1, 2007 at 18:30:54 Pacific
Reply:

I don't know if 'PnP bios' is the same as 'PnP OS' but if there's not separate option for that then I guess don't worry about it.

I think I've got 9.0a on mine and it's what I've been putting on the machines I put together. I think it was a developer's version and I've heard they're sometimes easier to install.


0

Response Number 17
Name: cudak888
Date: July 1, 2007 at 19:10:27 Pacific
Reply:

Hello Dave,

"PnP O/S in the BIOS is enabled" is what I meant to say. Guess I was typing faster then I was thinking.

I should note that I realized DirectX, although detecting itself as v8.1 according to dxdiag, was utilizing a hodgepodge of files from versions 4.x and 6.x - don't even recall seeing any 8.1 files about there.

Taking this into account, I tried one of the DirectX removers out there, then tried installing the v5.0 packaged in FS98 - if nothing else, I hoped that it would give the 9.0c edition something to "bite" on when installing - that, or the possibility that the v5.0 might actually clear up the problem. Neither did anything of the kind.

Although I did finally get around the 9.0c illegal operation error, the dxsetup.exe installation executable insists that "DirectX could not find a file necessary for installation."

Ah, I love a verbose program - now to run a Google search to figure out what the hell that could mean. After all, the entire package DID download in its entirety. Additionally, I tried unzipping the main .exe via WinZip as opposed to running the built-in unzip program.

Is there any location out there that still offers the DirectX 9.0 version you use?

Take care,

-Kurt


0

Response Number 18
Name: DAVEINCAPS
Date: July 1, 2007 at 20:33:47 Pacific
Reply:

It might be on Intel's site. Many of their download pages will offer a link to previous versions. I don't think I even know the file name as I've extracted it and burnt it to a cd.

A lot of those directX uninstallers don't seem to work. A fellow posted one in this previous thread:

http://computing.net/windows95/wwwb...

and as I noted there, an over-the-top reinstallation of 98 will revert it back to the version on the 98 cd.


0

Response Number 19
Name: cudak888
Date: July 3, 2007 at 19:46:51 Pacific
Reply:

Hello Dave,

While I was not able to locate a copy of DirectX 9.0, I was able to hunt up a copy of genuine DirectX 9.0b at one site that installed without issue.

It will probably come as no surprise that it did absolutely nothing to clear up the problem.

The straw finally broke the camel's back at this point, so I once and for all gave in...I wiped the partition and started over.

In the process of re-installing the drivers, I made sure to install the SoundMAX drivers before the others, excepting the Intel-specific chipset drivers - just to see if any of the drivers to be installed later would cause the same conflict.

I am quite pleased to say that no conflicts of any kind happened, and the sound drivers have been operating well for over 10 re-boots as of present. Now to see if it will just hold up until next morning (!)

P.S.: When installing, I believe the SoundMAX driver installed it's own version of mmdevldr.vxd. It flashed by on the screen quite quickly, but I am pretty sure that that was the case. Would this by any chance have any relations to the .vxd problem I had earlier? Was DirectX preventing the SoundMAX version from installing?

Just wild guesses on my part - but heck, no harm in it, eh?

Take care,

-Kurt


0

Response Number 20
Name: DAVEINCAPS
Date: July 3, 2007 at 20:46:04 Pacific
Reply:

I don't know if mmdevldr.vxd would have been the problem. I doubt it was directX as the soundmax installation should have reminded you it needed a newer version. But it was something to check off anyway.

Computer audio hardware and software is getting more and more sophisticated and demanding access to specific resources, ports and IRQ's. That's why it's usually best to install the sound stuff first so it can grab what it needs before it's allocated somewhere else.

I'm glad it seems to be working OK now. If you need the office97 just send a private message.


0

Response Number 21
Name: cudak888
Date: August 7, 2007 at 07:31:56 Pacific
Reply:

PM sent, Dave.

-Kurt


0

Sponsored Link
Ads by Google
Reply to Message Icon

Downgrade Win 98 SE to Wi... smilies for Outlook Expre...



Post Locked

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


Go to Windows 95/98 Forum Home


Sponsored links

Ads by Google


Results for: ntkern/mmdevldr.vxd error wSoundMAX

mmdevldr.vxd error (code2) and (code8) www.computing.net/answers/windows-95/mmdevldrvxd-error-code2-and-code8/86467.html

NTkern.vxd and mmdevldr.vxd - USB and Yamaha AC-XG www.computing.net/answers/windows-95/ntkernvxd-and-mmdevldrvxd-usb-and-yamaha-acxg/53158.html

mmdevldr.vxd (code 8) error still www.computing.net/answers/windows-95/mmdevldrvxd-code-8-error-still/86518.html