Outlook 2007's automatic reminder feature causes Outlook to automatically close the resolution

Problem Description
Test environment: windows vista home premium
microsoft outlook 2007
Storm video 6.10.00
Phenomenon: Open outlook2007, no to a minute, shut down automatically after an error prompted

error reads as follows:
"problem signature:
problem event name: APPCRASH
application name: OUTLOOK.EXE
Application Version: 12.0.4518.1014
Application Timestamp: 4542840f
Fault Module Name: StackHash_5979
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bdc9
Exception Code: c0000374
Abnormal offset: 000af1c9
OS version: 6.0.6000.2.0.0.768.3
Locale ID: 2052
Other information 1: 5979
Other information 2: 9f381d44f193688b8ae97ee951fae7e7
Others Information 3: 95d8
Other Information 4: 429451768577 6ef911bc323d4b4d0578
Read the privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0804 "

Process: After communicating with the user is the most recent After the storm video software was installed, this fault occurred, so the storm video was uninstalled, but the fault remained. So after reinstalling Outlook2007, it is normal. But after two days, the customer also called the fault to reappear, so he asked the customer again. The customer said that he usually not only uses Outlook to send and receive mail, but also often uses its own automatic reminder function. So entering Outlook quickly (before auto-shutdown) deletes all reminders and is normal.

Analysis
through to find information, found to play a sound when Outlook reminder out of the box, while the sound plays will call Voxware Audio Codec to decode, since the decoder and Vista operating systems do not Compatible, causing Outlook 2007 to automatically shut down. The Voxware Audio Codec decoder is not a decoder that comes with Vista. It may be installed automatically by users when installing Storm Video or other third-party media playback software. By modifying the registry key, disabling Outlook from calling the Voxware Audio Codec decoder can completely solve this problem.

Solutions
find the following in the registry: HKEY_LOCAL_MACHINE - & gt; SOFTWARE-Microsoft - & gt; Windows NT - & gt; CurrentVersion - & gt; Drivers32, renamed "msacm .voxacm160" is "no.msacm.voxacm160".