BSOD at various times, Dump .zip file attached

The new MEMORY.DMP file: Dropbox - MEMORY.DMP

Thank you again.

I'm pretty certain the problem has something to do with the IDrive program you are running for backups.

These 0x101 bugchecks are caused by a secondary processor being hung and not handling the clock interrupts. In the two kernel dumps I have looked at, the hung processor thread has been associated with an IDrive process.

Code:

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: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffad01b2714180, The PRCB address of the hung processor.
Arg4: 0000000000000009, The index of the hung processor.

0: kd> !prcb 9
PRCB for Processor 9 at ffffad01b2714180:
Current IRQL -- 0
Threads--  Current ffff8480774f5700 Next 0000000000000000 Idle ffffad01b2724300
Processor Index 9 Number (0, 9) GroupSetMember 200
Interrupt Count -- 027c792d
Times -- Dpc    000000ad Interrupt 0000049e 
         Kernel 0019e630 User      00009ae7 
0: kd> !thread ffff8480774f5700
THREAD ffff8480774f5700  Cid 06c8.4db4  Teb: 0000000000232000 Win32Thread: 0000000000000000 RUNNING on processor 9
IRP List:
    ffff848080f15010: (0006,04c0) Flags: 00000884  Mdl: 00000000
Not impersonating
DeviceMap                 ffffc4863ae18c00
Owning Process            ffff84807ac18580       Image:         id_service.exe
Attached Process          N/A            Image:         N/A
Wait Start TickCount      1736999        Ticks: 716 (0:00:00:11.187)
Context Switch Count      14600956       IdealProcessor: 9             
UserTime                  00:01:09.015
KernelTime                00:06:03.703
Win32 Start Address 0x00007ffb495403d0
Stack Init ffffa88b65c30c90 Current ffffa88b65c2f440
Base ffffa88b65c31000 Limit ffffa88b65c2b000 Call 0000000000000000
Priority 9 BasePriority 8 PriorityDecrement 0 IoPriority 2 PagePriority 5

Code:

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: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffc5000529f180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.



8: kd> !prcb 2
PRCB for Processor 2 at ffffc5000529f180:
Current IRQL -- 0
Threads--  Current ffff9b0fdef7c080 Next 0000000000000000 Idle ffffc500052af300
Processor Index 2 Number (0, 2) GroupSetMember 4
Interrupt Count -- 0658eaa0
Times -- Dpc    00000071 Interrupt 000008f8 
         Kernel 001d743c User      0004c1e0 
8: kd> !thread ffff9b0fdef7c080
THREAD ffff9b0fdef7c080  Cid 2894.3d08  Teb: 0000000000402000 Win32Thread: 0000000000000000 RUNNING on processor 2
IRP List:
    ffff9b0fe48b91b0: (0006,04c0) Flags: 00000884  Mdl: 00000000
Not impersonating
DeviceMap                 ffffaf0de70c01d0
Owning Process            ffff9b0fde1f8580       Image:         id_bglaunch.exe
Attached Process          N/A            Image:         N/A
Wait Start TickCount      4112701        Ticks: 528 (0:00:00:08.250)
Context Switch Count      670114         IdealProcessor: 4             
UserTime                  00:00:14.656
KernelTime                00:01:49.437
Win32 Start Address 0x00007ffcfa9503d0
Stack Init ffffad813033ac90 Current ffffad813033a000
Base ffffad813033b000 Limit ffffad8130335000 Call 0000000000000000
Priority 9 BasePriority 8 PriorityDecrement 0 IoPriority 2 PagePriority 5

Thank you for the update. I will close iDrive for now and let you know if I have any further crashes.

Thank you very much,
Eric

50/50 chance that its iDrive or NordVPN