Explorer Constantly Crashes

Diagnosing the Crash: What Happens When You Click a Link

When you double‑click a hyperlink in Internet Explorer, Windows Help, or Windows Explorer on a Windows 98 SE machine, the entire browser or help window suddenly closes, and you see an error message that reads something like “error de proteccin general en el mdulo CM8330.DRV de 0006:0000197a.” The situation is peculiar: right‑clicking the link and choosing “Open” from the context menu works fine, and navigating to the same address with the address bar or the “Go” button is also safe. This behavior points to a specific interaction between the graphical user interface and a low‑level system component, rather than a generic Internet Explorer bug.

The first clue lies in the message itself. “CM8330.DRV” is a device driver file belonging to the Sound Blaster 16 series, and the error code “0006:0000197a” is a standard Windows error that indicates a serious protection violation inside that driver. In a typical Windows environment, a crash caused by a driver failure would show a small red window or a blue “Program has stopped working” dialog. On Windows 98, the driver stack is less robust, so the operating system may simply terminate the process that loaded the driver and close the window that was interacting with it.

Because the crash only occurs when the user double‑clicks a link, the event that triggers the failure is likely the attempt to launch the default application for the URL - normally Internet Explorer itself. The double‑click action invokes a shell command that loads Internet Explorer and passes the URL as an argument. If the Sound Blaster driver is corrupted or incompatible with the system’s current configuration, launching Internet Explorer forces the driver to load in the same process space. The driver’s internal checks then detect an illegal memory access or a mismatch between the driver version and the operating system, and Windows kills the process. When you use the context menu, the shell may launch Internet Explorer through a different pathway that avoids the problematic driver load, or the OS may defer loading the driver until after the application starts, allowing the crash to be avoided.

Another layer of evidence is the fact that the error is not limited to Internet Explorer alone. Clicking a link in Windows Explorer or Windows Help produces the same result. Both of those applications use the same URL handling infrastructure: they send a request to the shell to open the link with the default handler. Thus the root cause is in the shared code that handles the link request, not in any one application. This pattern is typical of hardware driver conflicts that surface when a process attempts to use a resource the driver protects.

In older systems such as Windows 98 SE, the Sound Blaster 16 driver is often installed from the CD that comes with the motherboard or from a bundled software package. The driver on that disk is usually for a specific motherboard chipset and may not be fully compatible with every BIOS or CPU configuration. Over time, the driver can become corrupted through improper updates, accidental file deletion, or a bad BIOS setting. A corrupted driver can silently refuse to load, or it can load but crash the process that tries to use it. Because the Sound Blaster driver is loaded by many programs - including Internet Explorer, Windows Help, and even the Windows desktop itself - the failure manifests in a variety of seemingly unrelated ways.

To confirm that the driver is indeed the culprit, you can use the “Device Manager” from the Control Panel. Under “Sound, video and game controllers,” locate the “SB16 Audio Device.” Right‑click and choose “Properties.” In the “Driver” tab, you’ll see the driver version and the date it was installed. If the date matches the original CD or if the version number looks older than the one that shipped with your motherboard, you’re likely dealing with an outdated or mismatched driver. Conversely, if the driver appears to be from a newer third‑party source but still crashes, it might be incompatible with Windows 98 SE’s limited support for newer hardware features.

At this point, you should also consider whether any other audio software or drivers are installed that might interfere with the SB16 driver. Programs like Realtek HD Audio, SoundBlaster Pro, or even generic “audio enhancement” tools can conflict, especially if they load additional DLLs into the process space. Uninstalling these programs temporarily and testing the link click again can help isolate whether the problem is specifically tied to the SB16 driver or to a broader audio stack conflict. In many cases, however, the symptom points directly back to the CM8330.DRV file, and the solution involves updating or reinstalling that driver from the original source or a reliable vendor.

In summary, the crash you’re experiencing is a classic sign of a problematic Sound Blaster 16 driver on a Windows 98 SE system. The double‑click action triggers the Windows shell to launch Internet Explorer, which loads the driver, leading to a protection violation and the abrupt termination of the application. By narrowing the investigation to the driver level and testing alternative launch methods, you can pinpoint the root cause and move toward a definitive fix.

Resolving the Issue: Updating the Sound Driver

Fixing the crash begins with replacing the faulty CM8330.DRV driver with a clean, compatible version from a reputable source. The most reliable option is the latest driver bundle released by CMedia, the company that originally developed the Sound Blaster series. Their website hosts a collection of drivers that include the 16‑bit driver for Windows 98 SE, complete with an installation wizard that guides you through the update process.

First, download the driver package from

Tags