Walker News

How To Fix PowerPoint Slide Show Crash Problem

My PowerPoint 2007 running in Windows Vista Ultimate keeps on hang up whenever I try to open a PowerPoint Slide Show. After couple of attempts, the Problem Reports And Solutions program pop up a temporarily Registry trick for the application hang up problem.

In the Event Viewer, the Application Log recorded the error messages that said [ Faulting application POWERPNT.EXE, version 12.0.4518.1014, time stamp 0x45428035, faulting module ntdll.dll, version 6.0.6000.16386, time stamp 0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9, process id 0x120c, application start time 0x01c7dd01e9f43530 ].
Before committing the temporarily Registry trick, I went to ask Google for similar problems and solutions. The search results seem to suggest that the hang up was likely caused by Voxware MetaSound Audio Codec compatibility issue in Windows Vista.

According to Windows XP Documentation, Voxware MetaSound Audio Codec is one of the common audio codecs supported by Windows (officially). In this case, a third party Voxware audio codec installation might have caused the compatibility problem.

With this codec problem, you’ll likely encounter PowerPoint 2007 hangs up when opening Slide Show with sound effects, Outlook 2007 crash when the Outlook Reminder tool play a sound alert, OneNote close and exit when access to Option menu, etc.

How to temporarily fix or resolve Voxware Audio Codec compatibility issue or the Office 2007 application hang up problem?

As per Windows Vista bundled Problem Reports And Solutions program, the problem was caused by a compatibility problem between earlier version of Microsoft Office and Microsoft Office 2007. But, the Registry trick is obviously to disable the Voxware audio codec from loading in Windows Vista.
  1. Press the Windows shortcut key or click the Vista Orb to bring up Vista Start menu,
  2. Type regedit in the Start Search text box and press ENTER key to bring up Windows Registry Editor,
  3. Double-click HKEY_LOCAL_MACHINE, SOFTWARE, Microsoft, Windows NT, CurrentVersion, Drivers32,
  4. Locate the msacm.voxacm160 Registry key on the right pane (the Vista Problem Reports And Solutions suggest a different Registry key named msacm.voxacm16, which is not exists in my Vista Ultimate version),
  5. Right-click the msacm.voxacm160 Registry key, select Rename option and change it to something else, e.g. no.msacm.voxacm160

Bear in mind that this is only a temporarily Registry trick to resolve the codec compatibility problem. In rare cases, this trick may cause older programs that rely on this audio codec to malfunction! If it happens so, try to revert the Registry change – i.e. rename no.msacm.voxacm160 back to msacm.voxacm160 will do.

So far, this Registry trick works well for my case!

Custom Search

  1. Windows Update VS Windows Error Reporting – Walker News 15-08-07@14:50

    […] Remember the Vista version of Windows Error Reporting (WER) program? Yes, it’s called Problem Reports And Solutions. […]

2018  •  Privacy Policy