W
wesleywynn
Guest
Hello,
I just recently got an old pc second hand and have been encountering a recurring BSOD error "DRIVER_IRQL_NOT_LESS_OR_EQUAL what failed: netr28x.sys". I am in no way an expert, but I have been researching and trying to fix this error with everything I can try. I have run memory diagnostic tests (everything came back good), I have uninstalled and reinstalled my 802.11 wireless driver (many times), I've tried reinstalling other drivers on my computer, and I've run driver verifier (I posted the results of that dmp file below). I will also include a link to the minidump files that are currently on my computer from these crashes. There doesn't seem to be any one particular trigger of this crash, it has happened as often as in 30 minute increments while using google meets, to randomly getting triggered while using microsoft word and spotify. Any help would be greatly appreciated
Minidump files (This is my first time using onedrive, let me know if that does not work)
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: ffffbb0e735c7f38, name of the driver having the issue.
Arg3: ffffbb0e7351abb0, verifier internal structure with driver information.
Arg4: 0000000000000001, total # of (paged+nonpaged) allocations that weren't freed.
Type !verifier 3 drivername.sys for info on the allocations
that were leaked that caused the bugcheck.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5921
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on JFOLETTO-PC
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 9465
Key : Analysis.Memory.CommitPeak.Mb
Value: 72
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: c4
BUGCHECK_P1: 62
BUGCHECK_P2: ffffbb0e735c7f38
BUGCHECK_P3: ffffbb0e7351abb0
BUGCHECK_P4: 1
IMAGE_NAME: vgk.sys
MODULE_NAME: vgk
FAULTING_MODULE: fffff8061e600000 vgk
VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY ffffbb0e7351abb0
Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found.
BLACKBOXNTFS: 1 (!blackboxntfs)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffd80`3a006658 fffff803`0f1dae34 : 00000000`000000c4 00000000`00000062 ffffbb0e`735c7f38 ffffbb0e`7351abb0 : nt!KeBugCheckEx
fffffd80`3a006660 fffff803`0f1ea119 : ffffbb0e`7351abb0 fffffd80`3a006750 ffffbb0e`735c7d40 ffffbb0e`735f7e20 : nt!VerifierBugCheckIfAppropriate+0xe0
fffffd80`3a0066a0 fffff803`0ec84cfc : ffffbb0e`7351abb0 ffffbb0e`735c7de0 00000000`00000001 ffffbb0e`735f7e00 : nt!VfPoolCheckForLeaks+0x49
fffffd80`3a0066e0 fffff803`0f1cc502 : 00000000`00583000 ffffbb0e`735c7d40 fffff803`0f429d70 fffff803`0f429d70 : nt!VfTargetDriversRemove+0x108640
fffffd80`3a006760 fffff803`0eefc633 : ffffbb0e`735c7d40 fffffd80`3a006890 00000000`00000001 00000000`ffffffff : nt!VfDriverUnloadImage+0x3e
fffffd80`3a006790 fffff803`0ef69e01 : 00000000`00000000 fffff803`ffffffff ffff6ef8`00000001 ffff8e06`7bd7f4c0 : nt!MiUnloadSystemImage+0x2eb
fffffd80`3a006930 fffff803`0ef69d2e : ffffbb0e`735acdf0 fffffd80`3a006b80 00000000`00000000 00000000`00000000 : nt!MmUnloadSystemImage+0x41
fffffd80`3a006960 fffff803`0ee07ef0 : ffffbb0e`735acdf0 fffffd80`3a006b80 ffffbb0e`735acdf0 fffff803`0ee977bf : nt!IopDeleteDriver+0x4e
fffffd80`3a0069b0 fffff803`0ea6e277 : 00000000`00000000 00000000`00000000 fffffd80`3a006b80 ffffbb0e`735ace20 : nt!ObpRemoveObjectRoutine+0x80
fffffd80`3a006a10 fffff803`0ea6e19e : 00000000`00000008 00000000`00000000 ffffbb0e`735acdf0 00000000`c0000365 : nt!ObfDereferenceObjectWithTag+0xc7
fffffd80`3a006a50 fffff803`0ef32eb2 : 00000000`00000008 00000000`00000008 00000000`c0000365 00000000`00001000 : nt!HalPutDmaAdapter+0xe
fffffd80`3a006a80 fffff803`0f26389f : ffffbb0e`6e1f0310 ffffbb0e`6e1f0310 fffffd80`3a006cc0 00000000`00000000 : nt!IopLoadDriver+0x76a
fffffd80`3a006c50 fffff803`0f26c3fa : ffffffff`c0000365 ffff8e06`7ea3efc0 00000000`00000000 fffff803`0ca781e0 : nt!IopInitializeSystemDrivers+0x157
fffffd80`3a006cf0 fffff803`0efa7e2b : fffff803`0ca781e0 fffff803`0f453f68 fffff803`0efa7df0 fffff803`0ca781e0 : nt!IoInitSystem+0x2e
fffffd80`3a006d20 fffff803`0eb24e25 : ffffbb0e`6e0ca040 fffff803`0efa7df0 fffff803`0ca781e0 00000000`00000000 : nt!Phase1Initialization+0x3b
fffffd80`3a006d50 fffff803`0ec09dd8 : fffff803`0e277180 ffffbb0e`6e0ca040 fffff803`0eb24dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffd80`3a006da0 00000000`00000000 : fffffd80`3a007000 fffffd80`3a001000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0xc4_62_VRF_LEAKED_POOL_IMAGE_vgk.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {6b48ad5e-de65-9e28-3555-0011c454018a}
Followup: MachineOwner
---------
Continue reading...
I just recently got an old pc second hand and have been encountering a recurring BSOD error "DRIVER_IRQL_NOT_LESS_OR_EQUAL what failed: netr28x.sys". I am in no way an expert, but I have been researching and trying to fix this error with everything I can try. I have run memory diagnostic tests (everything came back good), I have uninstalled and reinstalled my 802.11 wireless driver (many times), I've tried reinstalling other drivers on my computer, and I've run driver verifier (I posted the results of that dmp file below). I will also include a link to the minidump files that are currently on my computer from these crashes. There doesn't seem to be any one particular trigger of this crash, it has happened as often as in 30 minute increments while using google meets, to randomly getting triggered while using microsoft word and spotify. Any help would be greatly appreciated
Minidump files (This is my first time using onedrive, let me know if that does not work)
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: ffffbb0e735c7f38, name of the driver having the issue.
Arg3: ffffbb0e7351abb0, verifier internal structure with driver information.
Arg4: 0000000000000001, total # of (paged+nonpaged) allocations that weren't freed.
Type !verifier 3 drivername.sys for info on the allocations
that were leaked that caused the bugcheck.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5921
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on JFOLETTO-PC
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 9465
Key : Analysis.Memory.CommitPeak.Mb
Value: 72
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: c4
BUGCHECK_P1: 62
BUGCHECK_P2: ffffbb0e735c7f38
BUGCHECK_P3: ffffbb0e7351abb0
BUGCHECK_P4: 1
IMAGE_NAME: vgk.sys
MODULE_NAME: vgk
FAULTING_MODULE: fffff8061e600000 vgk
VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY ffffbb0e7351abb0
Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found.
BLACKBOXNTFS: 1 (!blackboxntfs)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffd80`3a006658 fffff803`0f1dae34 : 00000000`000000c4 00000000`00000062 ffffbb0e`735c7f38 ffffbb0e`7351abb0 : nt!KeBugCheckEx
fffffd80`3a006660 fffff803`0f1ea119 : ffffbb0e`7351abb0 fffffd80`3a006750 ffffbb0e`735c7d40 ffffbb0e`735f7e20 : nt!VerifierBugCheckIfAppropriate+0xe0
fffffd80`3a0066a0 fffff803`0ec84cfc : ffffbb0e`7351abb0 ffffbb0e`735c7de0 00000000`00000001 ffffbb0e`735f7e00 : nt!VfPoolCheckForLeaks+0x49
fffffd80`3a0066e0 fffff803`0f1cc502 : 00000000`00583000 ffffbb0e`735c7d40 fffff803`0f429d70 fffff803`0f429d70 : nt!VfTargetDriversRemove+0x108640
fffffd80`3a006760 fffff803`0eefc633 : ffffbb0e`735c7d40 fffffd80`3a006890 00000000`00000001 00000000`ffffffff : nt!VfDriverUnloadImage+0x3e
fffffd80`3a006790 fffff803`0ef69e01 : 00000000`00000000 fffff803`ffffffff ffff6ef8`00000001 ffff8e06`7bd7f4c0 : nt!MiUnloadSystemImage+0x2eb
fffffd80`3a006930 fffff803`0ef69d2e : ffffbb0e`735acdf0 fffffd80`3a006b80 00000000`00000000 00000000`00000000 : nt!MmUnloadSystemImage+0x41
fffffd80`3a006960 fffff803`0ee07ef0 : ffffbb0e`735acdf0 fffffd80`3a006b80 ffffbb0e`735acdf0 fffff803`0ee977bf : nt!IopDeleteDriver+0x4e
fffffd80`3a0069b0 fffff803`0ea6e277 : 00000000`00000000 00000000`00000000 fffffd80`3a006b80 ffffbb0e`735ace20 : nt!ObpRemoveObjectRoutine+0x80
fffffd80`3a006a10 fffff803`0ea6e19e : 00000000`00000008 00000000`00000000 ffffbb0e`735acdf0 00000000`c0000365 : nt!ObfDereferenceObjectWithTag+0xc7
fffffd80`3a006a50 fffff803`0ef32eb2 : 00000000`00000008 00000000`00000008 00000000`c0000365 00000000`00001000 : nt!HalPutDmaAdapter+0xe
fffffd80`3a006a80 fffff803`0f26389f : ffffbb0e`6e1f0310 ffffbb0e`6e1f0310 fffffd80`3a006cc0 00000000`00000000 : nt!IopLoadDriver+0x76a
fffffd80`3a006c50 fffff803`0f26c3fa : ffffffff`c0000365 ffff8e06`7ea3efc0 00000000`00000000 fffff803`0ca781e0 : nt!IopInitializeSystemDrivers+0x157
fffffd80`3a006cf0 fffff803`0efa7e2b : fffff803`0ca781e0 fffff803`0f453f68 fffff803`0efa7df0 fffff803`0ca781e0 : nt!IoInitSystem+0x2e
fffffd80`3a006d20 fffff803`0eb24e25 : ffffbb0e`6e0ca040 fffff803`0efa7df0 fffff803`0ca781e0 00000000`00000000 : nt!Phase1Initialization+0x3b
fffffd80`3a006d50 fffff803`0ec09dd8 : fffff803`0e277180 ffffbb0e`6e0ca040 fffff803`0eb24dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffd80`3a006da0 00000000`00000000 : fffffd80`3a007000 fffffd80`3a001000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0xc4_62_VRF_LEAKED_POOL_IMAGE_vgk.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {6b48ad5e-de65-9e28-3555-0011c454018a}
Followup: MachineOwner
---------
Continue reading...