New
#1
BS after converting a video
So I was attempting to skrink a video down and BSOD came up. I would post it but it is 1.5 gigs in size. THis is the best I could do.
A little about my machine. I just recently formatted and started over a week ago, something I do once a year. All Windows updates applied, very little software installed at the moment. I would like to start this process over again but not if it is going to BS againCode:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 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:\cache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Machine Name: Kernel base = 0xfffff800`03a05000 PsLoadedModuleList = 0xfffff800`03c486d0 Debug session time: Thu Dec 26 14:00:37.353 2013 (UTC - 6:00) System Uptime: 0 days 20:08:23.150 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details Loading unloaded module list ................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {19, 0, fffff880009cf180, 4} *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009cf180, The PRCB address of the hung processor. Arg4: 0000000000000004, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: DivXEngine.exe CURRENT_IRQL: d STACK_TEXT: fffff800`05457958 fffff800`03ad1a4a : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009cf180 : nt!KeBugCheckEx fffff800`05457960 fffff800`03a846f7 : 00000000`00000000 fffff800`00000004 00000000`00002710 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e fffff800`054579f0 fffff800`03ff4895 : fffff800`0401a460 fffff800`05457ba0 fffff800`0401a460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377 fffff800`05457af0 fffff800`03a77113 : 00000000`630db28d fffff800`05457b01 fffffa80`0cd5ef00 fffff800`05457ec0 : hal!HalpHpetClockInterrupt+0x8d fffff800`05457b20 fffff800`03aab634 : fffff800`03bf5e80 fffff800`03a7f2e0 fffffa80`17eef8b0 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163 fffff800`05457cb0 fffff800`03a83f4d : fffff800`05457e00 00000000`00000000 fffffa80`16db3c58 fffffa80`16db3050 : nt!KxWaitForLockOwnerShip+0x28 fffff800`05457ce0 fffff880`017885b8 : 00000000`00000000 fffff800`05457ec0 fffffa80`0d3dd350 fffffa80`16db3c58 : nt!KeAcquireInStackQueuedSpinLock+0x8d fffff800`05457d30 fffff880`0178ae35 : fffffa80`17fb2110 00000000`00000000 00000000`00000000 fffffa80`1654f250 : storport!RaidAdapterAcquireStartIoLock+0x28 fffff800`05457d60 fffff880`0177e33b : 00000000`00000000 fffffa80`18088950 fffffa80`00000000 fffffa80`17fb2110 : storport!StorAcquireSpinLock+0x35 fffff800`05457d90 fffff880`0152f36b : fffffa80`1720d2f0 fffffa80`0d3db608 00000000`00000002 00000000`00000000 : storport! ?? ::FNODOBFM::`string'+0xa02 fffff800`05457e10 fffff880`014ceb83 : fffffa80`0cd33e80 fffff880`05006c57 fffffa80`0cd33e80 fffff880`05006614 : iaStorA+0x6b36b fffff800`05457e50 fffff880`0153c1a4 : fffffa80`16bad000 00000000`75542450 00000000`00000022 00000000`00000002 : iaStorA+0xab83 fffff800`05457e80 fffff800`03a8530c : fffff800`03bf5e80 fffffa80`0d3de008 fffffa80`0d3dd350 00000000`00000000 : iaStorA+0x781a4 fffff800`05457f00 fffff800`03a7dd15 : 00000000`00000000 fffffa80`19e039b0 00000000`00000000 fffff880`0153057c : nt!KiRetireDpcList+0x1bc fffff800`05457fb0 fffff800`03a7db2c : 00000000`2311f170 fffff880`014c70ce 00000000`00000000 fffff880`0b893b60 : nt!KyRetireDpcList+0x5 fffff880`0b893aa0 fffff800`03ac5b53 : fffff800`03a76a56 fffff800`03a76ac2 00000000`00000000 00000000`00002001 : nt!KiDispatchInterruptContinue fffff880`0b893ad0 fffff800`03a76ac2 : 00000000`00000000 00000000`00002001 fffffa80`0cd5eb40 fffffa80`1904e990 : nt!KiDpcInterruptBypass+0x13 fffff880`0b893ae0 00000000`66b67d9f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0x212 00000000`2321eed4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x66b67d9f STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner ---------
Quote