EVGA

Hot!Bug check 133 in CCVI.sys acquiring spin lock

Author
ddeaver
New Member
  • Total Posts : 5
  • Reward points : 0
  • Joined: 2020/11/20 02:40:04
  • Status: offline
  • Ribbons : 0
2020/11/20 02:49:01 (permalink)
This happens several times a week.  New system with CLC 360 cooler.  I have saved a few kernel dumps if anyone in support is listening.  I was attempting to file a support ticket, but have tossed the original box and cannot get the serial number, which is required to register the product and then file the support ticket.  My bad on tossing the box, but wasn't expecting this.   Anyone else having this problem and found a WAR besides just buying a new cooler?  Anyone in support seeing this? Again, I'm happy to communicate more details and pass along a kernel dump to a support person
 
11: 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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8075e4fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------

KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 0
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DDEAVER-DT1
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 37
Key : Analysis.Memory.CommitPeak.Mb
Value: 169
Key : Analysis.System
Value: CreateObject

BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8075e4fb320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT: 
ffff9e00`4b930e18 fffff807`5dc87a98 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`5e4fb320 : nt!KeBugCheckEx [minkernel\ntos\ke\amd64\procstat.asm @ 140]
ffff9e00`4b930e20 fffff807`5db26993 : 00005982`78c2c4f2 ffff9e00`4b917180 00000000`00000000 ffff9e00`4b917180 : nt!KeAccumulateTicks+0x15dda8 [minkernel\ntos\ke\runtime.c @ 625]
ffff9e00`4b930e80 fffff807`5db2647a : ffffc18d`d8ec9040 ffffbe80`834d15c0 00000000`00000000 ffffc18d`e5086010 : nt!KeClockInterruptNotify+0x453 [minkernel\ntos\ke\clocktick.c @ 1714]
ffff9e00`4b930f30 fffff807`5da2ecd5 : ffffc18d`d8ec9040 fffff807`5da9fa77 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a [minkernel\hals\lib\timers\common\timerint.c @ 857]
ffff9e00`4b930f60 fffff807`5dbf604a : ffffbe80`834d15c0 ffffc18d`d8ec9040 ffffffff`c0000120 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 [minkernel\ntos\ke\intrcmn.c @ 1716]
ffff9e00`4b930fb0 fffff807`5dbf65b7 : 00000000`e83045d2 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa [minkernel\ntos\ke\amd64\intsup.asm @ 572]
ffffbe80`834d1540 fffff807`5db302ff : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc18d`e4e2ade0 : nt!KiInterruptDispatchNoLockNoEtw+0x37 [minkernel\ntos\ke\amd64\intsup.asm @ 693]
ffffbe80`834d16d0 fffff807`5db302c8 : ffffc18d`e504e8c0 ffff9e00`4b917180 ffffc18d`e4e2ade0 fffff807`5e1b1019 : nt!KxWaitForSpinLockAndAcquire+0x2f [minkernel\ntos\ke\spinlock.c @ 95]
ffffbe80`834d1700 fffff807`6d711211 : 00000000`00000000 ffffc18d`e5086010 00000000`00000000 fffff807`5daa1c2f : nt!KeAcquireSpinLockRaiseToDpc+0x88 [minkernel\ntos\ke\spinlock.c @ 526]
ffffbe80`834d1730 fffff807`5dac310e : ffffc18d`e5086010 ffffbe80`834d1809 ffffbe80`834d1809 ffffc18d`e50865ab : CCVI+0x1211
ffffbe80`834d1780 fffff807`5dac2fd7 : 00000000`00000000 00000000`00000000 ffffc18d`e2c625f0 00000000`00000002 : nt!IopfCompleteRequest+0x11e [minkernel\ntos\io\iomgr\iosubs.c @ 4806]
ffffbe80`834d1870 fffff807`609b811a : 00000000`c0000120 ffffc18d`e2c35dd0 ffffc18d`e5086010 00000000`00000000 : nt!IofCompleteRequest+0x17 [minkernel\ntos\io\iomgr\iosubs.c @ 4546]
ffffbe80`834d18a0 fffff807`609f924e : ffffbe80`834d1a02 ffffc18d`da702988 ffffc18d`e5086010 ffffc18d`e2c3a310 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
ffffbe80`834d1930 fffff807`60a252b6 : ffffc18d`e2a379c0 ffffc18d`e2c35dd0 ffffc18d`e2c62502 00000000`00000000 : Wdf01000!FxRequest::Complete+0x8a [minkernel\wdf\framework\shared\inc\private\common\FxRequest.hpp @ 806]
ffffbe80`834d1990 fffff807`60a26b18 : ffffc18d`e2a37a38 ffffc18d`e5086010 ffffc18d`e5086002 ffffc18d`e2c625f0 : Wdf01000!FxIoQueue::CancelForQueue+0x162 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 4435]
ffffbe80`834d19e0 fffff807`609c84b7 : ffffc18d`e2c626b0 ffffc18d`da7029a0 ffffc18d`e5086010 ffffbe80`834d1aa9 : Wdf01000!FxIoQueue::_IrpCancelForQueue+0x48 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 4495]
ffffbe80`834d1a20 fffff807`5da95acf : ffffc18d`e5086010 ffffc18d`e504ea02 ffffc18d`e5086010 ffffc18d`e504ea02 : Wdf01000!FxIrpQueue::_WdmCancelRoutineInternal+0x87 [minkernel\wdf\framework\shared\core\fxirpqueue.cpp @ 905]
ffffbe80`834d1a70 fffff807`6d71147e : ffffc18d`e504e6b0 ffffc18d`e504ea10 ffffbe80`834d1c10 00000000`00000000 : nt!IoCancelIrp+0x6f [minkernel\ntos\io\iomgr\iosubs.c @ 3287]
ffffbe80`834d1ab0 fffff807`6d722c3e : ffffc18d`e7188638 00000000`00000103 ffffc18d`e504ea10 ffffc18d`da7029a0 : CCVI+0x147e
ffffbe80`834d1ae0 fffff807`6d721ece : ffffc18d`da7029a0 ffffbe80`834d1bf0 ffffc18d`e504ea10 ffffc18d`00000000 : SiLib+0x2c3e
ffffbe80`834d1b40 fffff807`5db9b8b9 : ffffc18d`eb890040 ffffc18d`e7188010 ffffc18d`00000000 ffffc18d`00000000 : SiLib+0x1ece
ffffbe80`834d1b70 fffff807`5daa2ae5 : ffffffff`fa0a1f00 fffff807`5db9b6e0 ffffc18d`ec676470 00000000`000000c3 : nt!PopIrpWorker+0x1d9 [minkernel\ntos\po\irpwork.c @ 608]
ffffbe80`834d1c10 fffff807`5dbfbbf8 : ffff9e00`4b917180 ffffc18d`eb890040 fffff807`5daa2a90 00000000`00000246 : nt!PspSystemThreadStartup+0x55 [minkernel\ntos\ps\psexec.c @ 9688]
ffffbe80`834d1c60 00000000`00000000 : ffffbe80`834d2000 ffffbe80`834cc000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 [minkernel\ntos\ke\amd64\threadbg.asm @ 83]

RETRACER_ANALYSIS_TAG_STATUS: DEBUG_FLR_FAULTING_IP is not found
SYMBOL_NAME: CCVI+1211
MODULE_NAME: CCVI
IMAGE_NAME: CCVI.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1211
FAILURE_BUCKET_ID: 0x133_ISR_CCVI!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {66616394-979c-9535-d6e9-a93b38983eb7}
Followup: MachineOwner
#1

11 Replies Related Threads

    Sajin
    EVGA Forum Moderator
    • Total Posts : 46119
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: offline
    • Ribbons : 198
    Re: Bug check 133 in CCVI.sys acquiring spin lock 2020/11/20 07:43:53 (permalink)
    You're running the latest version of flow control?

    Want to save 5 to 10% on your next EVGA purchase? Just click on the associates banner to save, or enter the associates code at checkout on your next purchase. If you choose to use my code I want to personally say "Thank You" for using it.
     

     
    #2
    ddeaver
    New Member
    • Total Posts : 5
    • Reward points : 0
    • Joined: 2020/11/20 02:40:04
    • Status: offline
    • Ribbons : 0
    Re: Bug check 133 in CCVI.sys acquiring spin lock 2020/11/20 08:39:45 (permalink)
    Sajin
    You're running the latest version of flow control?




    This morning I installed v2.0.10 (EVGA_Flow_Control_Setup_v2.0.10), and *think* I had 2.0.9 before.  Will see if it re-occurs with 2.0.10.  The system is ~ 1 month old, so the version I installed on top of (that exhibited bug check) was whatever was available 1 month ago.
    #3
    ddeaver
    New Member
    • Total Posts : 5
    • Reward points : 0
    • Joined: 2020/11/20 02:40:04
    • Status: offline
    • Ribbons : 0
    Re: Bug check 133 in CCVI.sys acquiring spin lock 2020/12/10 16:49:00 (permalink)
    This still reproduces with 2.0.10.  Same as before, I have a kernel dump I can share if that can help resolve it.
    #4
    Ehkoh
    New Member
    • Total Posts : 1
    • Reward points : 0
    • Joined: 2021/05/18 14:45:46
    • Status: offline
    • Ribbons : 0
    Re: Bug check 133 in CCVI.sys acquiring spin lock 2021/05/18 15:14:27 (permalink)
    Please update this thread with any info you can get, I have a problem thats almost completely identical. CCVI.sys is the driver I suspect is causing semi-frequent crashes with DPC_Watchdog_Violation. I have a new install of windows, almost nothing installed, and still getting crashes that lead to that driver.
     
    Also, don't feel bad about the box, I'm in the same boat currently.. :(
    #5
    Mister E...
    SSC Member
    • Total Posts : 569
    • Reward points : 0
    • Joined: 2005/05/12 18:10:06
    • Status: offline
    • Ribbons : 2
    Re: Bug check 133 in CCVI.sys acquiring spin lock 2021/05/23 15:53:21 (permalink)
    Just seeing this thread - serial number can usually be found on a label on the rad as well - right by the hose connections.

    Software is also at v.2.0.11 if that helps with the issue.
    #6
    ddeaver
    New Member
    • Total Posts : 5
    • Reward points : 0
    • Joined: 2020/11/20 02:40:04
    • Status: offline
    • Ribbons : 0
    Re: Bug check 133 in CCVI.sys acquiring spin lock 2021/07/07 08:08:41 (permalink)
    I am still seeing this problem.  Software version is v2.10.0.0 .  Crash most recently on 7/2/2021 and 7/7/2021.  Any clues on this?
    #7
    ddeaver
    New Member
    • Total Posts : 5
    • Reward points : 0
    • Joined: 2020/11/20 02:40:04
    • Status: offline
    • Ribbons : 0
    Re: Bug check 133 in CCVI.sys acquiring spin lock 2021/07/07 08:19:03 (permalink)
    More details on latest failure from 7/7/2021:
     
    3: kd> kn
    # Child-SP          RetAddr               Call Site
    00 ffff9100`9b36fe18 fffff803`5cc1edb6     nt!KeBugCheckEx
    01 ffff9100`9b36fe20 fffff803`5ca16ac3     nt!KeAccumulateTicks+0x205a96
    02 ffff9100`9b36fe80 fffff803`5ca165aa     nt!KeClockInterruptNotify+0x453
    03 ffff9100`9b36ff30 fffff803`5ca7e795     nt!HalpTimerClockIpiRoutine+0x1a
    04 ffff9100`9b36ff60 fffff803`5cbf86ca     nt!KiCallInterruptServiceRoutine+0xa5
    05 ffff9100`9b36ffb0 fffff803`5cbf8c37     nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
    06 ffffbb04`00c11540 fffff803`5cb604fc     nt!KiInterruptDispatchNoLockNoEtw+0x37
    07 ffffbb04`00c116d0 fffff803`5cb604c8     nt!KxWaitForSpinLockAndAcquire+0x2c
    08 ffffbb04`00c11700 fffff803`787e1211     nt!KeAcquireSpinLockRaiseToDpc+0x88
    09 ffffbb04`00c11730 fffff803`5cb0dede     CCVI+0x1211
    0a ffffbb04`00c11780 fffff803`5cb0dda7     nt!IopfCompleteRequest+0x11e
    0b ffffbb04`00c11870 fffff803`61bb811a     nt!IofCompleteRequest+0x17
    0c (Inline Function) --------`--------     Wdf01000!FxIrp::CompleteRequest+0x13 [minkernel\wdf\framework\shared\inc\private\km\FxIrpKm.hpp @ 75]
    0d ffffbb04`00c118a0 fffff803`61bf9b1e     Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
    0e ffffbb04`00c11930 fffff803`61c25b96     Wdf01000!FxRequest::Complete+0x8a [minkernel\wdf\framework\shared\inc\private\common\FxRequest.hpp @ 806]
    0f (Inline Function) --------`--------     Wdf01000!FxRequest::CompleteWithInformation+0x19 [minkernel\wdf\framework\shared\inc\private\common\FxRequest.hpp @ 820]
    10 ffffbb04`00c11990 fffff803`61c273f8     Wdf01000!FxIoQueue::CancelForQueue+0x162 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 4435]
    11 ffffbb04`00c119e0 fffff803`61bc84b7     Wdf01000!FxIoQueue::_IrpCancelForQueue+0x48 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 4495]
    12 ffffbb04`00c11a20 fffff803`5cae70af     Wdf01000!FxIrpQueue::_WdmCancelRoutineInternal+0x87 [minkernel\wdf\framework\shared\core\fxirpqueue.cpp @ 905]
    13 ffffbb04`00c11a70 fffff803`787e147e     nt!IoCancelIrp+0x6f
    14 ffffbb04`00c11ab0 fffff803`787f2c3e     CCVI+0x147e
    15 ffffbb04`00c11ae0 fffff803`787f1ece     SiLib+0x2c3e
    16 ffffbb04`00c11b40 fffff803`5cb9ce49     SiLib+0x1ece
    17 ffffbb04`00c11b70 fffff803`5caf53b5     nt!PopIrpWorker+0x1d9
    18 ffffbb04`00c11c10 fffff803`5cbfe278     nt!PspSystemThreadStartup+0x55
    19 ffffbb04`00c11c60 00000000`00000000     nt!KiStartSystemThread+0x28
     
    3: kd> !lmi CCVI.sys
    Loaded Module Info: [ccvi.sys]
             Module: CCVI
       Base Address: fffff803787e0000
         Image Name: CCVI.sys
       Machine Type: 34404 (X64)
         Time Stamp: 45c90c16 Tue Feb  6 18:15:34 2007
               Size: a000
           CheckSum: dca3
    Characteristics: 22 
    Debug Data Dirs: Type  Size     VA  Pointer
                 CODEVIEW    8d,  5170,    2d70 RSDS - GUID: {6016D36C-6A8C-408C-B464-72FC1C8BD6BE}
                   Age: 1, Pdb: c:\dev\development\librarypackages\usbxpress\drivers\usbxpress\windows_2k_xp_s2k3\objfre_wlh_amd64\amd64\SIUSBXP.pdb
         Image Type: MEMORY   - Image read successfully from loaded memory.
        Symbol Type: NONE     - PDB not found from symbol server.
        Load Report: no symbols loaded
     
    3: kd> !sysinfo cpuinfo
    [CPU Information]
    ~MHz = REG_DWORD 3893
    Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
    Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
    Identifier = REG_SZ AMD64 Family 23 Model 113 Stepping 0
    ProcessorNameString = REG_SZ AMD Ryzen 7 3800X 8-Core Processor            
    Update Status = REG_DWORD 1
    VendorIdentifier = REG_SZ AuthenticAMD
    #8
    Rockndot
    New Member
    • Total Posts : 1
    • Reward points : 0
    • Joined: 2022/01/11 18:28:34
    • Status: offline
    • Ribbons : 0
    Re: Bug check 133 in CCVI.sys acquiring spin lock 2022/01/11 19:01:01 (permalink)
    I had the same issue where my computer would crash every other time I put it to sleep or turned it off. I had the same exact FAILURE_ID_HASH: {66616394-979c-9535-d6e9-a93b38983eb7}.
     
    For the longest time, I did not know that it was an EVGA driver causing the issue until I clean installed Windows 11 on a new disk and realized that I had no issues until I later installed EVGA Flow Control. The version I installed that caused the crashes on my new Windows 11 machine was v2.0.11. I updated my bios for my ASUS Z390-A thinking it might solve the issue. Still, the same issue persisted. I then uninstalled and reinstalled the newer version of the Flow Control Driver (v2.0.12) (Windows 10 64bit version despite running Windows 11). Now it is working properly and I no longer experience these crashes.
     
    I am unsure if it is the just the update to v2.0.12 that fixed the problem or if it was a combination of that and the bios update.
    I really hope this helps as I know how frustrating it is to have that issue. I was too lazy to fix it for a long time and it was starting to drive me insane.
     
    Here is the stack text of my v2.0.11 crashes within the MEMORY.DMP file:
    PS: I don't know why my OSNAME is listed as Windows 10 still.
     
    STACK_TEXT:  
    ffffd780`a650bdd8 fffff803`5fadb50f : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`60505330 : nt!KeBugCheckEx
    ffffd780`a650bde0 fffff803`5fadb121 : 000000af`38477dc3 ffffd780`a649f180 00000000`00000246 fffff803`5fad68ae : nt!KeAccumulateTicks+0x20f
    ffffd780`a650be50 fffff803`5fad930a : ffffd780`a64a8200 fffffa06`87ea7400 ffffd780`a64a8298 fffff803`5fa13ccb : nt!KiUpdateRunTime+0x61
    ffffd780`a650beb0 fffff803`5fad90f6 : ffffc681`9b12a3e0 ffffc681`9b12a490 00000000`00000000 00000000`00000000 : nt!KeClockInterruptNotify+0x11a
    ffffd780`a650bf40 fffff803`5fa8d6a0 : ffffc681`9b12a3e0 fffff803`5fb3823c 00000000`00000000 7fffffff`00000034 : nt!HalpTimerClockIpiRoutine+0x16
    ffffd780`a650bf70 fffff803`5fc175ca : fffffa06`87ea7480 ffffc681`9b12a3e0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa0
    ffffd780`a650bfb0 fffff803`5fc17b97 : 00000000`e58a8d5f fffff803`5fad59a4 ffffc681`a3c35000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
    fffffa06`87ea7400 fffff803`5fa95d6c : 00000000`00000000 00000000`00000000 ffffc681`a7474de0 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
    fffffa06`87ea7590 fffff803`5fa95d31 : ffffc681`a5e1ba80 ffffd780`a649f180 ffffc681`a7474de0 fffff803`6026b019 : nt!KxWaitForSpinLockAndAcquire+0x2c
    fffffa06`87ea75c0 fffff803`77f11211 : 00000000`00000000 ffffc681`a5e0a820 00000000`00000000 fffff803`5fa475ff : nt!KeAcquireSpinLockRaiseToDpc+0xc1
    fffffa06`87ea75f0 fffff803`5fb34b27 : ffffc681`a5e0a820 fffffa06`87ea76e9 fffffa06`87ea76e9 ffffc681`a5e0ad73 : CCVI+0x1211
    fffffa06`87ea7640 fffff803`5fb349e7 : ffffc681`a5e0a820 00000000`00000000 ffffc681`a620a830 00000000`00000000 : nt!IopfCompleteRequest+0x127
    fffffa06`87ea7750 fffff803`62588ad0 : ffffc681`a5e0a820 00000000`00000000 00000000`00000002 00000000`00000000 : nt!IofCompleteRequest+0x17
    fffffa06`87ea7780 fffff803`625e3c96 : ffffc681`a5e0a820 ffffc681`9ab697e0 ffffc681`a2367ab0 ffffc681`a2471c50 : Wdf01000!FxRequest::CompleteInternal+0x240 [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
    fffffa06`87ea7810 fffff803`625bbe9a : ffffc681`b1db2ab0 ffffc681`a2367ab0 ffffc681`a620a802 00000000`00000000 : Wdf01000!FxRequest::Complete+0x8a [minkernel\wdf\framework\shared\inc\private\common\FxRequest.hpp @ 806]
    fffffa06`87ea7870 fffff803`62601f88 : ffffc681`b1db2b28 ffffc681`a5e0a820 ffffc681`a5e0a802 ffffc681`a620a830 : Wdf01000!FxIoQueue::CancelForQueue+0x2dc62 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 4435]
    fffffa06`87ea78c0 fffff803`6258e808 : ffffc681`a620a8f0 ffffc681`9ab69800 ffffc681`a5e0a820 00000000`00000000 : Wdf01000!FxIoQueue::_IrpCancelForQueue+0x48 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 4495]
    fffffa06`87ea7900 fffff803`5fa229ef : ffffc681`a5e0a820 ffffc681`a5e1bb02 ffffc681`a5e0a820 ffffc681`a5e1bb02 : Wdf01000!FxIrpQueue::_WdmCancelRoutineInternal+0x88 [minkernel\wdf\framework\shared\core\fxirpqueue.cpp @ 928]
    fffffa06`87ea7950 fffff803`77f1147e : ffffc681`a5e1b870 ffffc681`a5e1bbd0 fffffa06`87ea7af0 00000000`00000000 : nt!IoCancelIrp+0x6f
    fffffa06`87ea7990 fffff803`77f22c3e : ffffc681`afe0f5f0 00000000`00000103 ffffc681`a5e1bbd0 ffffc681`9ab69800 : CCVI+0x147e
    fffffa06`87ea79c0 fffff803`77f21ece : ffffc681`9ab69800 fffffa06`87ea7ad0 ffffc681`a5e1bbd0 ffffc681`00000000 : SiLib+0x2c3e
    fffffa06`87ea7a20 fffff803`5fbab717 : ffffc681`bac71040 00000000`00000000 00000000`00000000 fffffa06`87ea7a00 : SiLib+0x1ece
    fffffa06`87ea7a50 fffff803`5fa478f5 : ffffffff`fa0a1f00 fffff803`5fbab510 ffffc681`a7ef8c30 00000000`0000088a : nt!PopIrpWorker+0x207
    fffffa06`87ea7af0 fffff803`5fc19a74 : ffffd780`a63cb180 ffffc681`bac71040 fffff803`5fa478a0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
    fffffa06`87ea7b40 00000000`00000000 : fffffa06`87ea8000 fffffa06`87ea1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


    SYMBOL_NAME: CCVI+1211
    MODULE_NAME: CCVI
    IMAGE_NAME: CCVI.sys
    STACK_COMMAND: .cxr; .ecxr ; kb
    BUCKET_ID_FUNC_OFFSET: 1211
    FAILURE_BUCKET_ID: 0x133_ISR_CCVI!unknown_function
    OS_VERSION: 10.0.22000.1
    BUILDLAB_STR: co_release
    OSPLATFORM_TYPE: x64
    OSNAME: Windows 10
    FAILURE_ID_HASH: {66616394-979c-9535-d6e9-a93b38983eb7}
    Followup: MachineOwner
    #9
    coolmistry
    CLASSIFIED Member
    • Total Posts : 2469
    • Reward points : 0
    • Joined: 2009/04/08 11:13:01
    • Location: Hemel Hempstead , London
    • Status: online
    • Ribbons : 41
    Re: Bug check 133 in CCVI.sys acquiring spin lock 2022/01/13 09:22:15 (permalink)
    I have updated v2.0.12 from V2.0.9. No problem here but I have realise and haven't see this icon under my taskbar... see the photo if that normal but it suppose not safely remove "eject 690CL"
    Oldest version wasn't there....
    Eject 690CL
     

    Windows 11 Home 64bits up to Dated
    i7 8086k @ 4.0Ghz delidded IHS Pure Copper OC 5.3 Ghz || EVGA Z370 Classifieds K || 2 x EVGA GTX 1080 Ti SC Black Edition || 32Gb Dominator Platinum DDR3 3200mhz XMP || 500gb Samsung 970 EVO plus NVMe || 500gb Samsung 870 EVO Sata M.2 (1 x SSD and 1xHHD) || Killer Wireless AC1550 || EVGA CLC 360 Cooler || EVGA Supernova 1000w G2 || EVGA Z10 Keyboard || EVGA TORQ X10 mouse ||EVGA DG 77 case || Acer Predator Z35 35" 200Hz G-Sync v2 Pro || Logitech Z906 5.1 system sounds SPDIF|| Kaspersky Internet Security
    #10
    mvaldess
    New Member
    • Total Posts : 10
    • Reward points : 0
    • Joined: 2019/04/17 19:33:46
    • Status: offline
    • Ribbons : 0
    Re: Bug check 133 in CCVI.sys acquiring spin lock 2022/01/14 14:43:06 (permalink)
    coolmistry
    I have updated v2.0.12 from V2.0.9. No problem here but I have realise and haven't see this icon under my taskbar... see the photo if that normal but it suppose not safely remove "eject 690CL"
    Oldest version wasn't there....

     


    I was trying several version of this software and at some point this 690CL thing appeared in the system tray.
    If you check Device Manager in Control Panel, you'll find an "Asetek USB Device". When uninstalling it I checked "Delete the driver software for this device":
    1. The 690CL thing disappeared.
    2. CCVI appeared in Device Manager.
    3. Everything works fine.

    I'm on v2.0.11 with no problems.
    #11
    rgarvey58
    New Member
    • Total Posts : 64
    • Reward points : 0
    • Joined: 2021/03/11 06:35:53
    • Location: Boston, MA
    • Status: offline
    • Ribbons : 2
    Re: Bug check 133 in CCVI.sys acquiring spin lock 2022/01/16 11:09:45 (permalink)
    Flow Control 2.0.12 includes a 'newer' Asetek driver (6.7.2.0) based on winusb instead of CCVI. The driver is a generic winusb version, which still has the "Safe Removal" flag set which is why '690CL' shows up in the system tray. It doesn't affect the device operation, but as discussed in other threads... EVGA should have removed the safe removal flag with a proper implementation. 
     
    FYI... for anyone using Argus Monitor for fan control... the new driver included with 2.0.12 is not compatible. The CCVI driver is required if you want to control the EVGA CLC. 
    #12
    Jump to:
  • Back to Mobile