Blue screen crash from this MP4 video file in VLC v1.1.11?

[ant]

Hello.

I downloaded 174 MB and tried to play http://media.assembly.org/vod/2006/semi ... 00kbps.mp4. It seems to work in VLC v1.1.11, but will blue screen (rtkhdaud.sys DRIVER_IRQL_NOTLESS_OR_EQUAL) with a stuck audio if I go skip back in its video file. If I using K-Lite Codec Mega Pack v7.20 + v7.28 updates' Media Player Classic Home Cinema v1.5.2.3329 in my updated, old Windows XP Pro. SP3 with the latest onboard RealTek audio driver, then I get no video and gibberish audio. I can easily reproduce this 100% with this pattern. I don't know if it will blue screen for other PCs.

FYI, file properties from MediaInfo:
General
Complete name : E:\dl\asm\59_seminar_linux_4k_coding_h264_400kbps.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom
File size : 174 MiB
Duration : 46mn 21s
Overall bit rate : 526 Kbps

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 46mn 21s
Bit rate : 401 Kbps
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 5:4
Frame rate mode : Constant
Frame rate : 25.000 fps
Standard : PAL
Bits/(Pixel*Frame) : 0.039
Stream size : 133 MiB (76%)

Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Codec ID : 40
Duration : 46mn 21s
Bit rate mode : Variable
Bit rate : 121 Kbps
Channel(s) : 1 channel
Sampling rate : 48.0 KHz
Compression mode : Lossy
Stream size : 40.0 MiB (23%)

Maybe it's a bad encoded MP4 file? I tried another MP4 (not from the same server) with no problems with both players.

Either way, shouldn't VLC reject this video file to prevent the blue screen? FYI from WinDbg on my latest memory.dmp file:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Aug 7 15:58:42.564 2011 (UTC - 7:00)
System Uptime: 0 days 0:05:31.033
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols

Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ab65fa54, 2, 0, ab1edc1a}

*** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
Probably caused by : RtkHDAud.sys ( RtkHDAud+eac1a )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ab65fa54, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: ab1edc1a, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: ab65fa54

CURRENT_IRQL: 2

FAULTING_IP:
RtkHDAud+eac1a
ab1edc1a 0fbf0c4548f960ab movsx ecx,word ptr RtkHDAud+0x50c948 (ab60f948)[eax*2]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

TRAP_FRAME: ba4df900 -- (.trap 0xffffffffba4df900)
ErrCode = 00000000
eax=00028086 ebx=8a9fff30 ecx=00a02183 edx=8a99f928 esi=ff5fde7c edi=ff5fde7c
eip=ab1edc1a esp=ba4df974 ebp=ba4df980 iopl=0 nv up ei pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212
RtkHDAud+0xeac1a:
ab1edc1a 0fbf0c4548f960ab movsx ecx,word ptr RtkHDAud+0x50c948 (ab60f948)[eax*2] ds:0023:ab65fa54=41c7
Resetting default scope

LAST_CONTROL_TRANSFER: from ab1edc1a to 80544758

STACK_TEXT:
ba4df900 ab1edc1a badb0d00 8a99f928 be4d5951 nt!KiTrap0E+0x238
WARNING: Stack unwind information not available. Following frames may be wrong.
ba4df980 ab1ee1fb 8a99f7c0 00000033 8a9fff30 RtkHDAud+0xeac1a
ba4df9a0 ab1897e4 8a99f7c0 8a99f7c0 00000060 RtkHDAud+0xeb1fb
ba4dfa30 ab152c76 8a9ab8b0 ba4dfa8c 8a9ae94c RtkHDAud+0x867e4
ba4dfd00 ab15537c ba4dfd18 8a98b000 8a98b000 RtkHDAud+0x4fc76
ba4dfd28 80545eef 8a9aeee0 8a98b000 891a4ba0 RtkHDAud+0x5237c
ba4dfd50 80545dd4 00000000 0000000e bc2abc2a nt!KiRetireDpcList+0x61
ba4dfd54 00000000 0000000e bc2abc2a 5e775e77 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
RtkHDAud+eac1a
ab1edc1a 0fbf0c4548f960ab movsx ecx,word ptr RtkHDAud+0x50c948 (ab60f948)[eax*2]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: RtkHDAud+eac1a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: RtkHDAud

IMAGE_NAME: RtkHDAud.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e157cc2

FAILURE_BUCKET_ID: 0xD1_RtkHDAud+eac1a

BUCKET_ID: 0xD1_RtkHDAud+eac1a

Followup: MachineOwner
---------

1: kd> lmvm RtkHDAud
start end module name
ab103000 ab754000 RtkHDAud (no symbols)
Loaded symbol image file: RtkHDAud.sys
Image path: \SystemRoot\system32\drivers\RtkHDAud.sys
Image name: RtkHDAud.sys
Timestamp: Thu Jul 07 02:30:42 2011 (4E157CC2)
CheckSum: 00619DCC
ImageSize: 00651000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
1: kd> lmvm RtkHDAud
start end module name
ab103000 ab754000 RtkHDAud (no symbols)
Loaded symbol image file: RtkHDAud.sys
Image path: \SystemRoot\system32\drivers\RtkHDAud.sys
Image name: RtkHDAud.sys
Timestamp: Thu Jul 07 02:30:42 2011 (4E157CC2)
CheckSum: 00619DCC
ImageSize: 00651000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Thank you in advance.

[Jean-Baptiste Kempf]

If you BSOD, then you have a driver issue (audio or video). Try deactivating audio and then video to see which one is the culprit.

[ant]

If you BSOD, then you have a driver issue (audio or video). Try deactivating audio and then video to see which one is the culprit.

I tried disabling audio feature in VLC and was able to reproduce the blue screen so it is audio related as the blue screen said. Now, how to prevent this so I can watch these old MP4s without bluescreening?

Is anyone else able to reproduce this problem?

FYI, mplayer.exe had no problems:
C:\>D:\winstuff\MediaCoder2011\codecs\mplayer.exe G:\videos\UnwatchedDownloadsAndRips\ASM\badBSoDinVLCtoo\59_seminar_linux_4k_coding_h264_400kbps.mp4
MPlayer UNKNOWN-4.5.0 (C) 2000-2011 MPlayer Team
Cannot load bitmap font: Arial

Playing G:\videos\UnwatchedDownloadsAndRips\ASM\badBSoDinVLCtoo\59_seminar_linux
_4k_coding_h264_400kbps.mp4.
libavformat file format detected.
[lavf] stream 0: video (h264), -vid 0
[lavf] stream 1: audio (aac), -aid 0, -alang und
VIDEO: [H264] 720x576 24bpp 25.000 fps 401.0 kbps (49.0 kbyte/s)
Clip info:
major_brand: isom
minor_version: 512
compatible_brands: mp41
creation_time: 1970-01-01 00:00:00
Load subtitles in G:\videos\UnwatchedDownloadsAndRips\ASM\badBSoDinVLCtoo\
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
==========================================================================
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 48000 Hz, 1 ch, s16le, 120.6 kbit/15.70% (ratio: 15073->96000)
Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
==========================================================================
AO: [dsound] 48000Hz 1ch s16le (2 bytes per sample)
Starting playback...
Unsupported PixelFormat 61
Unsupported PixelFormat 53
Movie-Aspect is 1.25:1 - prescaling to correct movie aspect.
VO: [directx] 720x576 => 720x576 Planar YV12

Also, VLC v1.1.0 for Linux on a different PC had no crashes.

[VLC_help]

You can usually avoid BSODs with different video or audio output module. But as JB said, it is a driver issue or a hardware issue
http://wiki.videolan.org/WindowsFAQ-1.1 ... _output.3F
http://wiki.videolan.org/WindowsFAQ-1.1 ... _anomalies

[ant]

You can usually avoid BSODs with different video or audio output module. But as JB said, it is a driver issue or a hardware issue
http://wiki.videolan.org/WindowsFAQ-1.1 ... _output.3F
http://wiki.videolan.org/WindowsFAQ-1.1 ... _anomalies

Ah, ugh. I will have to find time to fiddle with each audio option. Dang, so complicated/complex!

Currently, I am using OpenGL video output because of viewtopic.php?f=14&t=90011
... I am currently using the default audio options in VLC with stereo (2.1). I don't know if that are related.

I will be curious if anyone else can reproduce this on their Windows PCs. I will try this on my office PC's 64-bit W7 HPE with the same portable VLC player and MP4 file. It also has an onboard RealTek audio.

[Lotesdelere]

This file is broken, especially the audio track which claims to be mono in MediaInfo but all tools I've tried detect it as stereo (including VLC) with the exception of YAMB/MP4Box which says it has 0 channel

However when attempting to remux the file with FFmpeg, it detects the audio track as mono but remuxes it as stereo. Even once extracted, most players are experiencing troubles for playing this audio track. Not to mention most players don't even detect the video track.
So there is definitely something fishy with this file.

[ant]

This file is broken, especially the audio track which claims to be mono in MediaInfo but all tools I've tried detect it as stereo (including VLC) with the exception of YAMB/MP4Box which says it has 0 channel

However when attempting to remux the file with FFmpeg, it detects the audio track as mono but remuxes it as stereo. Even once extracted, most players are experiencing troubles for playing this audio track. Not to mention most players don't even detect the video track.
So there is definitely something fishy with this file.

Wow. Interesting and thanks. That was only the only MP4 file. There were many from http://archive.assembly.org/ ... I can get a bunch of URLs with this problem if needed.

Shouldn't VLC block me to play this problematic MP4 file to prevent a blue screen/crashes?

[ant]

... I will try this on my office PC's 64-bit W7 HPE with the same portable VLC player and MP4 file. It also has an onboard RealTek audio.

I couldn't reproduce the blue screen on it with the same exact file and portable VLC player at work. However, lots of popping sounds which make me not watch these bad videos.