Link to home
Start Free TrialLog in
Avatar of c7c4c7
c7c4c7Flag for United States of America

asked on

Constant BSOD

Win 10 Pro 256SSD, single chip 8gig memory, I've reseated the chip.  No external hardware attached

This machine has constant BSOD.  I don't see anything notable in the dumps.  I've
Run Memtest - No Errors
Chkdsk - no errors
Loaded all drivers so that they are current
All windows update have been installed except option updates

I've run out of ideas, I've attached several dmp files060421-9203-01.dmp060421-9656-01.dmp
One thing I've noticed is they occur about every 30 - 34 minutes, but I don't see anything scheduled to run in that time frame

Any help is appreceiated
Avatar of Seth Simmons
Seth Simmons
Flag of United States of America image

what kind of system/components are we dealing with?
are you using integrated graphics or separate?  if separate, take out the graphics card and see if it crashes
would also try a different memory module
the stop code typically indicates a driver though the dump file doesn't really indicate anything outside of the kernel so it's a bit vague
Avatar of c7c4c7

ASKER

Integrated Graphics, it does have a graphics card but not being used,  If it was memory wouldn't memtest find the problem?

My guess is drive as well but everything has been updated
Integrated Graphics, it does have a graphics card but not being used

could try removing it

If it was memory wouldn't memtest find the problem?

not always
Avatar of c7c4c7

ASKER

Removed the card
if it is not solved yet, update all drivers
check also eventviewer and device manager for errors
I ran an analysis using Windbg on the 060421-9203-01.dmp file:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: ffffdb0ab6395050, Object whose reference count is being lowered
Arg3: 0000000000000010, Reserved
Arg4: 0000000000000001, 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:
------------------

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 5

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on PETERS-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 20

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 76

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  18

BUGCHECK_P1: 0

BUGCHECK_P2: ffffdb0ab6395050

BUGCHECK_P3: 10

BUGCHECK_P4: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

LOCK_ADDRESS:  fffff80373c44960 -- (!locks fffff80373c44960)

Resource @ nt!PiEngineLock (0xfffff80373c44960)    Exclusively owned
    Contention Count = 20
     Threads: ffffdb0ac386c040-01<*>
1 total locks

PNP_TRIAGE_DATA:
   Lock address  : 0xfffff80373c44960
   Thread Count  : 1
   Thread address: 0xffffdb0ac386c040
   Thread wait   : 0x1f175

STACK_TEXT:  
ffffef0f`4b2c74e8 fffff803`73414e52 : 00000000`00000018 00000000`00000000 ffffdb0a`b6395050 00000000`00000010 : nt!KeBugCheckEx
ffffef0f`4b2c74f0 fffff803`73271946 : ffffdb0a`b6395050 00000000`69706e50 00000000`00001001 00000000`00000fff : nt!ObfReferenceObjectWithTag+0xf5522
ffffef0f`4b2c7530 fffff803`73639c0b : 00000000`c00000bb ffffef0f`4b2c7600 00000000`0000000c 00000000`00000000 : nt!IoGetAttachedDeviceReferenceWithTag+0x36
ffffef0f`4b2c7560 fffff803`737507c6 : 00000000`c00000bb ffffdb0a`9bb22a20 ffffef0f`4b2c77a8 ffffdb0a`9bb21da0 : nt!IopSynchronousCall+0x3f
ffffef0f`4b2c75d0 fffff803`737506a4 : ffffdb0a`9bb22a20 ffffef0f`4b2c77a8 ffffdb0a`c386c040 fffff803`735d80ce : nt!PnpIrpQueryID+0x56
ffffef0f`4b2c7660 fffff803`7372444d : ffffdb0a`9bb22a20 ffffef0f`4b2c77c0 00000000`00000000 00000000`00000000 : nt!PnpQueryID+0x34
ffffef0f`4b2c76c0 fffff803`73726d10 : ffffdb0a`9bb22a20 ffffdb0a`9bb22a20 00000000`00000001 00000000`00000000 : nt!PiProcessNewDeviceNode+0x11d
ffffef0f`4b2c7890 fffff803`73721586 : ffffdb0a`9bb22a00 ffffdb0a`c44c8901 ffffef0f`4b2c79b0 fffff803`00000000 : nt!PipProcessDevNodeTree+0x380
ffffef0f`4b2c7960 fffff803`7336e04a : 00000001`00000003 ffffdb0a`9bb22a20 00000000`00000000 ffffdb0a`c44c89b0 : nt!PiRestartDevice+0xba
ffffef0f`4b2c79b0 fffff803`73341225 : ffffdb0a`c386c040 ffffdb0a`9bae5b80 fffff803`73c43300 fffff803`00000000 : nt!PnpDeviceActionWorker+0x46a
ffffef0f`4b2c7a70 fffff803`732f53b5 : ffffdb0a`c386c040 00000000`00000080 ffffdb0a`9bac6080 00000000`00000000 : nt!ExpWorkerThread+0x105
ffffef0f`4b2c7b10 fffff803`733fe348 : ffffaa80`85b36180 ffffdb0a`c386c040 fffff803`732f5360 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffef0f`4b2c7b60 00000000`00000000 : ffffef0f`4b2c8000 ffffef0f`4b2c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!ObfReferenceObjectWithTag+f5522

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.985

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  f5522

FAILURE_BUCKET_ID:  0x18_nt!ObfReferenceObjectWithTag

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b6b47bfd-ed1b-fc56-3b01-ddc037f9c59f}

Followup:     MachineOwner


Avatar of c7c4c7

ASKER

all of the driver updates have been installed
Do you see something I missed in windbg?




Avatar of c7c4c7

ASKER

The BSOD are happening every 34 minutes
User generated imageI don’t see anything in the task scheduler that runs in that time frame

User generated image
Where else can I look for programs that run on a set time?
​ 
Do you see something I missed in windbg?

that post is the exact same thing i already looked at last night

Where else can I look for programs that run on a set time?

can you open an elevated command prompt and post the output of tasklist ?

at this point need to start looking at running processes
just because it happens every x minutes does not necessarily indicate a scheduled task
it could be that whatever is causing the fault, it takes that amount of time for it to occur
Avatar of c7c4c7

ASKER

tasklist file included tasklist.txt
Avatar of c7c4c7

ASKER

event viewer system log.evtx
did you happen to also update the bios?
i see nvidia processes running
if you removed the card, can you uninstall the software?  that will rule that out
system log shows another blue screen 0x7e (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) from an hour ago which could point to a driver

also see a stop 0xca (PNP_DETECTED_FATAL_ERROR) which points to a driver
did you update drivers after May 26?  if so, that may have resolved that problem since I don't see that stop code since
ASKER CERTIFIED SOLUTION
Avatar of Seth Simmons
Seth Simmons
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of c7c4c7

ASKER

All drivers were updated yesterday.  That was the first thing I did
Avatar of c7c4c7

ASKER

Dell support assist is gone