Associate
- Joined
- 29 Sep 2020
- Posts
- 1
I recently bought a new PC from overclockers and since the beginning I've been receiving a lot of BSOD with various error messages. I've updated all my drivers. Run system check and memory tests but I still do not know what is causing it. Here is some of the information from the dump files from the BSOD I've received today:
REFERENCE_BY_POINTER (18)
Arguments:
Arg1: ffffac8c6e2af7a0, Object type of the object whose reference count is being lowered
Arg2: ffffac8c81c9e3e0, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: 0000000000000031, Reserved
The reference count of an object is illegal for the current state of the object.
Each time a driver uses a pointer to an object the driver calls a kernel routine
to increment the reference count of the object. When the driver is done with the
pointer the driver calls another kernel routine to decrement the reference count.
Drivers must match calls to the increment and decrement routines. This bugcheck
can occur because an object's reference count goes to zero while there are still
open handles to the object, in which case the fourth parameter indicates the number
of opened handles. It may also occur when the object's reference count drops below zero
whether or not there are open handles to the object, and in that case the fourth parameter
contains the actual value of the pointer references count.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2858
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-20U48SK
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 5183
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 18
BUGCHECK_P1: ffffac8c6e2af7a0
BUGCHECK_P2: ffffac8c81c9e3e0
BUGCHECK_P3: 1
BUGCHECK_P4: 31
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: nvcontainer.exe
STACK_TEXT:
ffffcf83`a0829908 fffff804`71821564 : 00000000`00000018 ffffac8c`6e2af7a0 ffffac8c`81c9e3e0 00000000`00000001 : nt!KeBugCheckEx
ffffcf83`a0829910 fffff804`71c09037 : 00000000`ffff8001 ffffac8c`81c9e3b0 ffffac8c`81c9e3b0 ffffd186`430f1840 : nt!ObfDereferenceObjectWithTag+0x17eeb4
ffffcf83`a0829950 fffff804`71c0e32e : 00000000`00000d38 000000ef`cfeff300 ffffcf83`00000002 ffffcf83`a0829a00 : nt!ObCloseHandleTableEntry+0x2c7
ffffcf83`a0829a90 fffff804`717d4258 : ffffac8c`77588080 000000ef`cfeff408 ffffcf83`a0829b80 ffffffff`ffb38db0 : nt!NtClose+0xde
ffffcf83`a0829b00 00007ff9`0e9bc254 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000ef`cfeff508 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`0e9bc254
SYMBOL_NAME: nt!ObfDereferenceObjectWithTag+17eeb4
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.1082
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 17eeb4
FAILURE_BUCKET_ID: 0x18_CORRUPT_REF_COUNT_nt!ObfDereferenceObjectWithTag
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fa6b3516-71cb-1e92-b987-b8bebd3458ac}
Followup: MachineOwner
RQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000005dc8, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 000000000000004b, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80747a4b31b, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3405
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-20U48SK
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 7590
Key : Analysis.Memory.CommitPeak.Mb
Value: 108
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: a
BUGCHECK_P1: 5dc8
BUGCHECK_P2: ff
BUGCHECK_P3: 4b
BUGCHECK_P4: fffff80747a4b31b
WRITE_ADDRESS: 0000000000005dc8
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
TRAP_FRAME: ffff9d86bbe7d780 -- (.trap 0xffff9d86bbe7d780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000012e2819e8 rbx=0000000000000000 rcx=0000000000000001
rdx=000000000000028e rsi=0000000000000000 rdi=0000000000000000
rip=fffff80747a4b31b rsp=ffff9d86bbe7d910 rbp=ffff9d86bbe7da10
r8=8000000000000000 r9=ffff9d86bbe7db60 r10=000000012e4eacd9
r11=ffff90f8e9200000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!PpmIdlePrepare+0x16b:
fffff807`47a4b31b 488b86c85d0000 mov rax,qword ptr [rsi+5DC8h] ds:00000000`00005dc8=????????????????
Resetting default scope
STACK_TEXT:
ffff9d86`bbe7d638 fffff807`47bd4829 : 00000000`0000000a 00000000`00005dc8 00000000`000000ff 00000000`0000004b : nt!KeBugCheckEx
ffff9d86`bbe7d640 fffff807`47bd0b69 : 00000000`00000000 00000000`00000000 00000000`00007ebb 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9d86`bbe7d780 fffff807`47a4b31b : 00000000`00108f32 00000000`00989680 ffff8004`29bd0010 00000001`2e4eaa4a : nt!KiPageFault+0x469
ffff9d86`bbe7d910 fffff807`47a4a206 : 00000000`00000003 00000000`00000002 ffff8004`29bd0100 00000000`00000008 : nt!PpmIdlePrepare+0x16b
ffff9d86`bbe7db00 fffff807`47bc6484 : ffffffff`00000000 ffffa100`f0479180 ffff8004`2e2f8080 00000000`00000948 : nt!PoIdle+0x1e6
ffff9d86`bbe7dc60 00000000`00000000 : ffff9d86`bbe7e000 ffff9d86`bbe78000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x44
SYMBOL_NAME: nt!PpmIdlePrepare+16b
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 16b
FAILURE_BUCKET_ID: AV_CODE_AV_nt!PpmIdlePrepare
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {0722116b-c23b-c6c2-0c96-05693152d11a}
Followup: MachineOwner
I really don't know what to do anymore? Anyone any ideas?
REFERENCE_BY_POINTER (18)
Arguments:
Arg1: ffffac8c6e2af7a0, Object type of the object whose reference count is being lowered
Arg2: ffffac8c81c9e3e0, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: 0000000000000031, Reserved
The reference count of an object is illegal for the current state of the object.
Each time a driver uses a pointer to an object the driver calls a kernel routine
to increment the reference count of the object. When the driver is done with the
pointer the driver calls another kernel routine to decrement the reference count.
Drivers must match calls to the increment and decrement routines. This bugcheck
can occur because an object's reference count goes to zero while there are still
open handles to the object, in which case the fourth parameter indicates the number
of opened handles. It may also occur when the object's reference count drops below zero
whether or not there are open handles to the object, and in that case the fourth parameter
contains the actual value of the pointer references count.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2858
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-20U48SK
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 5183
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 18
BUGCHECK_P1: ffffac8c6e2af7a0
BUGCHECK_P2: ffffac8c81c9e3e0
BUGCHECK_P3: 1
BUGCHECK_P4: 31
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: nvcontainer.exe
STACK_TEXT:
ffffcf83`a0829908 fffff804`71821564 : 00000000`00000018 ffffac8c`6e2af7a0 ffffac8c`81c9e3e0 00000000`00000001 : nt!KeBugCheckEx
ffffcf83`a0829910 fffff804`71c09037 : 00000000`ffff8001 ffffac8c`81c9e3b0 ffffac8c`81c9e3b0 ffffd186`430f1840 : nt!ObfDereferenceObjectWithTag+0x17eeb4
ffffcf83`a0829950 fffff804`71c0e32e : 00000000`00000d38 000000ef`cfeff300 ffffcf83`00000002 ffffcf83`a0829a00 : nt!ObCloseHandleTableEntry+0x2c7
ffffcf83`a0829a90 fffff804`717d4258 : ffffac8c`77588080 000000ef`cfeff408 ffffcf83`a0829b80 ffffffff`ffb38db0 : nt!NtClose+0xde
ffffcf83`a0829b00 00007ff9`0e9bc254 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000ef`cfeff508 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`0e9bc254
SYMBOL_NAME: nt!ObfDereferenceObjectWithTag+17eeb4
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.1082
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 17eeb4
FAILURE_BUCKET_ID: 0x18_CORRUPT_REF_COUNT_nt!ObfDereferenceObjectWithTag
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fa6b3516-71cb-1e92-b987-b8bebd3458ac}
Followup: MachineOwner
RQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000005dc8, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 000000000000004b, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80747a4b31b, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3405
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-20U48SK
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 7590
Key : Analysis.Memory.CommitPeak.Mb
Value: 108
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: a
BUGCHECK_P1: 5dc8
BUGCHECK_P2: ff
BUGCHECK_P3: 4b
BUGCHECK_P4: fffff80747a4b31b
WRITE_ADDRESS: 0000000000005dc8
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
TRAP_FRAME: ffff9d86bbe7d780 -- (.trap 0xffff9d86bbe7d780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000012e2819e8 rbx=0000000000000000 rcx=0000000000000001
rdx=000000000000028e rsi=0000000000000000 rdi=0000000000000000
rip=fffff80747a4b31b rsp=ffff9d86bbe7d910 rbp=ffff9d86bbe7da10
r8=8000000000000000 r9=ffff9d86bbe7db60 r10=000000012e4eacd9
r11=ffff90f8e9200000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!PpmIdlePrepare+0x16b:
fffff807`47a4b31b 488b86c85d0000 mov rax,qword ptr [rsi+5DC8h] ds:00000000`00005dc8=????????????????
Resetting default scope
STACK_TEXT:
ffff9d86`bbe7d638 fffff807`47bd4829 : 00000000`0000000a 00000000`00005dc8 00000000`000000ff 00000000`0000004b : nt!KeBugCheckEx
ffff9d86`bbe7d640 fffff807`47bd0b69 : 00000000`00000000 00000000`00000000 00000000`00007ebb 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9d86`bbe7d780 fffff807`47a4b31b : 00000000`00108f32 00000000`00989680 ffff8004`29bd0010 00000001`2e4eaa4a : nt!KiPageFault+0x469
ffff9d86`bbe7d910 fffff807`47a4a206 : 00000000`00000003 00000000`00000002 ffff8004`29bd0100 00000000`00000008 : nt!PpmIdlePrepare+0x16b
ffff9d86`bbe7db00 fffff807`47bc6484 : ffffffff`00000000 ffffa100`f0479180 ffff8004`2e2f8080 00000000`00000948 : nt!PoIdle+0x1e6
ffff9d86`bbe7dc60 00000000`00000000 : ffff9d86`bbe7e000 ffff9d86`bbe78000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x44
SYMBOL_NAME: nt!PpmIdlePrepare+16b
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 16b
FAILURE_BUCKET_ID: AV_CODE_AV_nt!PpmIdlePrepare
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {0722116b-c23b-c6c2-0c96-05693152d11a}
Followup: MachineOwner
I really don't know what to do anymore? Anyone any ideas?
