[BUG] Windows 10 Explorer Crashes Doing Metadata Lookups on Some WAV Files

Windows 10 explorer.exe crashes (and then restarts) when browsing folders containing .wav files. 

The issue seems to be in the PropertySystem lookup when trying to extract metadata.

Affected System: Windows 10 Professional 1607 (v10.0.15063).

The parameters do not change.

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Explorer.EXE
P2: 10.0.15063.332
P3: 2bdd7016
P4: mfsrcsnk.dll
P5: 10.0.15063.0
P6: 5398e597
P7: c0000005
P8: 0000000000032fc7
P9:
P10:

(I have not done extensive research to figure out exactly what in the WAV files it's not happy with.)

It's not the file association mapping itself, I've tried changing that and there's no effect.

It's the property system's lookup.

If someone at Microsoft would like a sample .wav file that definately causes this issue, please contact me.

(I should note, Windows 7 browsing a folder with the same .wav file does not crash.)

Was this discussion helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this discussion?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this discussion?

Thanks for your feedback.

I can confirm this bug happens on the latest Windows 10 Build 15063.483

This WAV header is ok in Windows Explorer:

00000000  52 49 46 46 04 66 07 00  57 41 56 45 66 6d 74 20  |RIFF.f..WAVEfmt |
00000010  10 00 00 00 01 00 01 00                           |........|
00000018

This WAV header produces a crash


00000000  52 49 46 46 b8 93 02 00  57 41 56 45 66 6d 74 20  |RIFF....WAVEfmt |
00000010  10 00 00 00 01 00 01 00                           |........|
00000018

  <Data />
  <Data>0</Data>
  <Data>APPCRASH</Data>
  <Data>Not available</Data>
  <Data>0</Data>
  <Data>explorer.exe</Data>
  <Data>10.0.15063.447</Data>
  <Data>951324bb</Data>
  <Data>mfsrcsnk.dll</Data>
  <Data>10.0.15063.0</Data>
  <Data>5398e597</Data>
  <Data>c0000005</Data>
  <Data>0000000000032fc7</Data>

 <Data />

Here is the debug. Looks like the issue is with CWAVFileParser::ParseWAVFormat

7 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Happens here as well, for a 20-bit file !

Here's the diff against the 24-bit source file that has been saved to 20-bit:

> fc /b sample_20.wav.q sample_24.wav
Comparing files sample_20.wav.q and SAMPLE_24.WAV
00000022: 14 18

4 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Discussion Info


Last updated November 12, 2020 Views 540 Applies to: