Windows 10: Help - BSOD IRQL_NOT_LESS_OR_EQUAL caused by usbccgp.sys.

My computer has recently been having several software issues - most recently, I have experienced a BSOD (description in title). Most advice regarding issues like this states that I should replace this driver. How do I do so?

P.S. WinDbg of the BSOD:

Microsoft (R) Windows Debugger Version 10.0.18239.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff800`c741c000 PsLoadedModuleList = 0xfffff800`c77ca290
Debug session time: Mon Oct 22 13:35:22.413 2018 (UTC + 2:00)
System Uptime: 0 days 13:25:30.095
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols

Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8c, 2, 1, fffff805eab918de}

Probably caused by : hardware ( usbccgp!DispatchPdoUrb+ce )

Followup: MachineOwner
---------

nt!KeBugCheckEx:
fffff800`c75c5490 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa301`9b028b80=000000000000000a
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000000000000008c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff805eab918de, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 4011

BIOS_DATE: 04/19/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: ROG STRIX B350-F GAMING

BASEBOARD_VERSION: Rev X.0x

DUMP_TYPE: 1

BUGCHECK_P1: 8c

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff805eab918de

WRITE_ADDRESS: 000000000000008c

CURRENT_IRQL: 2

FAULTING_IP:
usbccgp!DispatchPdoUrb+ce
fffff805`eab918de 004889 add byte ptr [rax-77h],cl

CPU_COUNT: c

CPU_MHZ: ed8

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: MARC-PC

ANALYSIS_SESSION_TIME: 10-22-2018 14:07:22.0811

ANALYSIS_VERSION: 10.0.18239.1000 amd64fre

TRAP_FRAME: ffffa3019b028cc0 -- (.trap 0xffffa3019b028cc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000103 rbx=0000000000000000 rcx=7fa9ab45946d0000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805eab918de rsp=ffffa3019b028e50 rbp=ffffa3019b028f50
r8=fffff805e736c5b8 r9=ffff800781da70e0 r10=ffff9001de000180
r11=ffffa3019b028df0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
usbccgp!DispatchPdoUrb+0xce:
fffff805`eab918de 004889 add byte ptr [rax-77h],cl ds:00000000`0000008c=??
Resetting default scope

MISALIGNED_IP:
usbccgp!DispatchPdoUrb+ce
fffff805`eab918de 004889 add byte ptr [rax-77h],cl

LAST_CONTROL_TRANSFER: from fffff800c75d6069 to fffff800c75c5490

STACK_TEXT:
ffffa301`9b028b78 fffff800`c75d6069 : 00000000`0000000a 00000000`0000008c 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffa301`9b028b80 fffff800`c75d2ce5 : ffff8007`00000000 00001f80`00640248 00000000`000b000b ffff8007`7e964570 : nt!KiBugCheckDispatch+0x69
ffffa301`9b028cc0 fffff805`eab918de : 00000000`0000056b ffffa301`9b028f50 ffff8007`55646948 fffffff6`00000000 : nt!KiPageFault+0x425
ffffa301`9b028e50 00000000`002cc648 : ffff8007`8369fa68 00000000`00000000 ffff9001`de000180 fffff800`c745a11f : usbccgp!DispatchPdoUrb+0xce
ffffa301`9b028f70 ffff8007`8369fa68 : 00000000`00000000 ffff9001`de000180 fffff800`c745a11f ffff8007`86de71f0 : 0x2cc648
ffffa301`9b028f78 00000000`00000000 : ffff9001`de000180 fffff800`c745a11f ffff8007`86de71f0 00000000`00000000 : 0xffff8007`8369fa68


THREAD_SHA1_HASH_MOD_FUNC: 84555248ef219b34181365159b9eb3419b637ce3

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b4bbb39df8761f12d56829b13dee0a8c7bb1b967

THREAD_SHA1_HASH_MOD: f7ae4ccf39b38854447d43e05bc4588bdd7a9a36

FOLLOWUP_IP:
usbccgp!DispatchPdoUrb+ce
fffff805`eab918de 004889 add byte ptr [rax-77h],cl

FAULT_INSTR_CODE: 44894800

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: usbccgp!DispatchPdoUrb+ce

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

PRIMARY_PROBLEM_CLASS: IP_MISALIGNED

TARGET_TIME: 2018-10-22T11:35:22.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-09-20 05:40:30

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 4e5

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:ip_misaligned

FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}

Followup: MachineOwner
---------

:)

 

BSOD caused by avc3.sys

Hi!

I have a Sony Vaio SVE1512I1ESI laptop, Windows 10 Home installed. In the past weeks I got various BSOD, most of the time with FAULTY_HARDWARE_CORRUPTED_PAGE report. I did a driver verification as recommended here in the community. Immediately after the
restart I got another BSOD with IRQL_NOT_LESS_OR_EQUAL message and after that avc3.sys driver error.

Here I upload the latest dmp file:

https://1drv.ms/u/s!At9cDvWNrLp0hIY4kjcT0jAg52SncA

Please help me to fix my laptop.

Thank you!

Attila

 

BSOD irql_not_less_or_equal (bwcW10X64.sys) error


Hi,

Been getting the following blue screen error for a bit now. BSOD irql_not_less_or_equal (bwcW10X64.sys)

I have attached the zip file of my BSOD report. Any help would be greatly appreciated.

Thank you in advance.

Attachment 96009

 

BSOD with error IRQL_NOT_LESS_OR_EQUAL. It also mentioned that the problem was in intelppm,sys.

"I purchased some software called..." 3rd party software is not required (or suggested (by me)).. The Media Creation Tool creates a bootable media.

Does "BSOD with error IRQL_NOT_LESS_OR_EQUAL" happen when you boot the install media?