jirim100 Posted October 6, 2021 Share Posted October 6, 2021 (edited) Today my PC goes to BSOD (during recording). Source was probably DD card Max M4 (module DDcapture.sys). What means lines in debug log with the following text?: "ParseSI Bad CRC" These lines are before BSOD. BSOD crash happened about 06.10.21 14:33:56. Here is analyzed crash dump by WinDbg: Spoiler Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\100621-7375-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (20 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff803`31000000 PsLoadedModuleList = 0xfffff803`31c2a390 Debug session time: Wed Oct 6 14:34:25.501 2021 (UTC + 2:00) System Uptime: 3 days 4:08:22.609 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............. Loading User Symbols Loading unloaded module list .................................................. For analysis of this file, run !analyze -v 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace. Arg2: 0000000000000501, The DPC time count (in ticks). Arg3: 0000000000000500, The DPC time allotment (in ticks). Arg4: fffff80331cfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding this single DPC timeout Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for DDCapture.sys ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: TickPeriods *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 2 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-B7NHU71 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 10 Key : Analysis.Memory.CommitPeak.Mb Value: 80 Key : Analysis.System Value: CreateObject BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff80331cfb320 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffff9d80`879f4e18 fffff803`3143ac88 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffff9d80`879f4e20 fffff803`3126f9a3 : 0001f0f7`7c67bdb7 ffff9d80`879db180 00000000`00000000 ffff9d80`879db180 : nt!KeAccumulateTicks+0x1c8a88 ffff9d80`879f4e80 fffff803`3126f48a : ffffb205`11ce6480 ffffd70b`62c2f4e0 00000000`00000000 ffff9d80`879f4f20 : nt!KeClockInterruptNotify+0x453 ffff9d80`879f4f30 fffff803`31327ef5 : ffffb205`11ce6480 00000000`00000000 00000000`00000000 ffffc5a2`65b53c69 : nt!HalpTimerClockIpiRoutine+0x1a ffff9d80`879f4f60 fffff803`313f752a : ffffd70b`62c2f4e0 ffffb205`11ce6480 ffffb205`239e3000 ffffb205`22725080 : nt!KiCallInterruptServiceRoutine+0xa5 ffff9d80`879f4fb0 fffff803`313f7a97 : ffffb205`233cc293 fffff803`3124885e ffffb205`233cc010 ffffd70b`62c2f4f9 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffffd70b`62c2f460 fffff803`312e4751 : ffffb205`205edda0 ffff9d80`879db180 00000000`00000000 ffffb205`233cc290 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffffd70b`62c2f5f0 fffff803`4aa13d1b : ffffb205`205edc90 ffffb205`2b4a29e0 00000000`00017800 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x11 ffffd70b`62c2f620 fffff803`4aa148a4 : ffffb205`2b4a2a02 00000000`00017800 00000000`00000001 ffffb205`1b4df180 : ks!CKsQueue::LockStreamPointer+0x7b ffffd70b`62c2f660 fffff803`4aa14945 : 00000000`00000000 ffffb205`1a492a90 ffffb205`2b4a2a40 00000000`00017800 : ks!CKsQueue::GetLeadingStreamPointer+0x44 ffffd70b`62c2f690 fffff803`48d32f86 : ffffb205`25b87050 ffffb205`25b87050 00000000`00017800 00000000`00000282 : ks!KsPinGetLeadingEdgeStreamPointer+0x55 ffffd70b`62c2f6c0 ffffb205`25b87050 : ffffb205`25b87050 00000000`00017800 00000000`00000282 00000000`00000304 : DDCapture+0x2f86 ffffd70b`62c2f6c8 ffffb205`25b87050 : 00000000`00017800 00000000`00000282 00000000`00000304 ffffb205`1b4df180 : 0xffffb205`25b87050 ffffd70b`62c2f6d0 00000000`00017800 : 00000000`00000282 00000000`00000304 ffffb205`1b4df180 00000000`00000000 : 0xffffb205`25b87050 ffffd70b`62c2f6d8 00000000`00000282 : 00000000`00000304 ffffb205`1b4df180 00000000`00000000 0001f0ea`62a5024b : 0x17800 ffffd70b`62c2f6e0 00000000`00000304 : ffffb205`1b4df180 00000000`00000000 0001f0ea`62a5024b 00000000`00000001 : 0x282 ffffd70b`62c2f6e8 ffffb205`1b4df180 : 00000000`00000000 0001f0ea`62a5024b 00000000`00000001 fffff803`4c7e3716 : 0x304 ffffd70b`62c2f6f0 00000000`00000000 : 0001f0ea`62a5024b 00000000`00000001 fffff803`4c7e3716 ffffb205`1b4dfc50 : 0xffffb205`1b4df180 SYMBOL_NAME: ks!CKsQueue::LockStreamPointer+7b MODULE_NAME: ks IMAGE_NAME: ks.sys IMAGE_VERSION: 10.0.19041.1136 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 7b FAILURE_BUCKET_ID: 0x133_DPC_ks!CKsQueue::LockStreamPointer OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {88e5f647-4bca-75c1-f7b1-29de8dc280fc} Followup: MachineOwner --------- Attached Tuner.log is from Digital Devices Control Center. svcdebug.zip TunerLog.txt Edited October 6, 2021 by jirim100 Quote Link to comment
Griga Posted October 6, 2021 Share Posted October 6, 2021 4 hours ago, jirim100 said: What means lines in debug log with the following text?: "ParseSI Bad CRC" SI = broadcasted Service Information. More about it here. The EPG data is part of it. SI data comes with a CRC checksum. If the calculated EPG data checksum doesn't match the broadcasted checksum, the DMS discards the data, assuming that is it corrupted somehow, e.g by reception disturbances. 4 hours ago, jirim100 said: Attached Tuner.log is from Digital Devices Control Center. I would rather forward them to Digital Devices. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.