BSOD in Windows 7 - Unified Remote cause?

[JeeveStobs]

I started receiving random BSODs two weeks ago after cold-booting (off overnight) my computer so I enabled Driver Verifier to track down the cause.

I immediately got the following BSOD when booting into Windows:

On Sun 4/3/2016 8:42:07 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\040316-7566-01.dmp This was probably caused by the following module: wdf01000.sys (Wdf01000+0x47C0) Bugcheck code: 0xC9 (0x22E, 0xFFFFF88000E2D7C0, 0xFFFFF98006092D30, 0x0) Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION file path: C:\Windows\system32\drivers\wdf01000.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Kernel Mode Driver Framework Runtime Bug check description: This is the bug check code for all Driver Verifier This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Sun 4/3/2016 8:42:07 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: uvhid.sys (uvhid+0x1585) Bugcheck code: 0xC9 (0x22E, 0xFFFFF88000E2D7C0, 0xFFFFF98006092D30, 0x0) Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION file path: C:\Windows\system32\drivers\uvhid.sys product: Windows ® Win 7 DDK driver company: Windows ® Win 7 DDK provider description: HID mini driver for Unified Virtual HID Bug check description: This is the bug check code for all Driver Verifier This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: uvhid.sys (HID mini driver for Unified Virtual HID, Windows ® Win 7 DDK provider). Google query: uvhid.sys Windows ® Win 7 DDK provider DRIVER_VERIFIER_IOMANAGER_VIOLATION

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.19160.amd64fre.win7sp1_gdr.160211-0600 Machine Name: Kernel base = 0xfffff80003a5c000 PsLoadedModuleList = 0xfffff80003ca3730 Debug session time: Sun Apr 3 04:42:07.815 2016 (UTC - 4:00) System Uptime: 0 days 0:00:11.549

---

• *
• Bugcheck Analysis *
• *

  ---

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 000000000000022e, The caller has completed a successful IRP_MJ_PNP instead of passing it down. Arg2: fffff88000e2d7c0, The address in the driver's code where the error was detected. Arg3: fffff98006092d30, IRP address. Arg4: 0000000000000000

Debugging Details:

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0xc9_22e

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 22e

FAULTING_IP: Wdf01000!FxDevice::DispatchWithLock+0 fffff880`00e2d7c0 48895c2408 mov qword ptr [rsp+8],rbx

FOLLOWUP_IP: uvhid+1585 fffff880`04bbd585 ?? ???

IRP_ADDRESS: fffff98006092d30

DEVICE_OBJECT: fffffa801c688780

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80003f654ec to fffff80003ad0080

STACK_TEXT: fffff880033a8e48 fffff80003f654ec : 00000000000000c9 000000000000022e fffff88000e2d7c0 fffff98006092d30 : nt!KeBugCheckEx fffff880033a8e50 fffff80003f6f5aa : fffff80003f63b00 fffff88000e2d7c0 fffff98006092d30 0000000000000000 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880033a8e90 fffff80003f705b3 : 000000000000022e fffff98006092d30 fffff98006092d30 00000000ffffffff : nt!ViErrorFinishReport+0xda fffff880033a8ee0 fffff80003f7bff2 : fffffa80166fe000 0000000000000000 0820000700000365 fffff80003ad3002 : nt!VfErrorReport1+0x63 fffff880033a8f80 fffff80003f6515e : fffffa801d606240 0000000000000001 0000000000000000 0000000000000000 : nt!VfPnpVerifyIrpStackUpward+0xb2 fffff880033a8fe0 fffff80003f71c5d : fffffa801bf2fd70 fffffa801d606010 fffff98006092d30 fffff98006092d30 : nt!VfMajorVerifyIrpStackUpward+0x6e fffff880033a9020 fffff80003f8363d : fffff98006092ed8 fffff880033a9210 0000000000000000 fffff98006092ed8 : nt!IovpCompleteRequest2+0xad fffff880033a9090 fffff80003ad3ad1 : fffff98006092edb 0000000000000000 0000000000000013 fffff80003b960b3 : nt!IovpLocalCompletionRoutine+0x9d fffff880033a90f0 fffff80003f7aeef : fffff98006092d30 0000000000000000 fffff98006092d00 0000000000000000 : nt!IopfCompleteRequest+0x341 fffff880033a91e0 fffff88004bbd585 : fffffa801c6dd080 fffff98006092ed8 0000000000000000 fffff98006092d30 : nt!IovCompleteRequest+0x19f fffff880033a92b0 fffffa801c6dd080 : fffff98006092ed8 0000000000000000 fffff98006092d30 fffffa801bf14d10 : uvhid+0x1585 fffff880033a92b8 fffff98006092ed8 : 0000000000000000 fffff98006092d30 fffffa801bf14d10 fffff88000e2d706 : 0xfffffa801c6dd080 fffff880033a92c0 0000000000000000 : fffff98006092d30 fffffa801bf14d10 fffff88000e2d706 000000000000001b : 0xfffff98006092ed8

STACK_COMMAND: kb

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: uvhid+1585

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: uvhid

IMAGE_NAME: uvhid.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 560d0254

FAILURE_BUCKET_ID: X64_0xc9_22e_VRF_uvhid+1585

BUCKET_ID: X64_0xc9_22e_VRF_uvhid+1585

Followup: MachineOwner

[JeeveStobs]

Opened ticket in Zendesk #5223

Dump file attached in ticket.

[jonatino]

@orion4444 did you ever fix this issue?

[JeeveStobs]

Yeah, the underlying issue appeared to be caused by my RAM and not Unified Remote. Once I swapped that out, the BSODs stopped.