Is there a newer version of the Intel HD Graphics 630 driver for the HP ENVY All-in-One - 27-b110

Question

Is there a newer version of the Intel HD Graphics 630 driver for the HP ENVY All-in-One - 27-b110

Anonymous

Microsoft told me that the driver for the Intel HD Graphics 630 is causing my crashes. I cannot find a newer version than the 23.20.16.4973 Rev.A. Intel has a newer version, 27.20.100.9079, but Intel says that the driver on the HP ENVY was customized and so I can only get an update from HP.

How do I get a newer driver from HP?

But is that even my problem?

Prior to the Windows 10 May feature update 20H2 this desktop was rock solid.

Since then it has been very unstable.

Initially it was crashing consistently with DPC WATCHDOG violation

Microsoft Support identified my Video drive as the culprit so I updated the NVIDIA GeForce GTX 950M to version 27.21.14.5671

It seemed to be better but was still failing with DPC WATCHDOGs

Another dump identified problems with the network driver.

I updated my Realtek PCIe GbE Family Controller to version 10.45.928.2020 and the Intel(R) Dual Band Wireless-AC 3168 to version 19.51.31.1

Today I had 9 bugchecks as listed below. Everything runs fine as long as both network adapters are disabled. If I enable one or the other the system can work for an hour or more or die in minutes

The HP Support Assistant was no help. I had to get recent device drivers direct from the chip makers.

Below the 9 bugchecks is a partial analysis by WinDbg

Any ideas?

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8005a0fa320, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: c38f84f1-7e3d-4c1b-8a32-0996291fb278.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000005100, 0xffff98c3c081c180, 0x00000000000000d0, 0x0000000000000800). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: cf545719-97c1-4549-a4db-ab351cdb91de.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8004bafa320, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a743e8a1-aa9a-415a-a997-d7d3ff76c5dc.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x000000000000001d, 0xffffa10a3234d740, 0xffffa10a3234d698, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7667fc0b-1203-4bed-bbe3-e530199f419d.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000000, 0x0000000000000501, 0x0000000000000500, 0xfffff80503efa320). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: db3aa191-6e4a-42bd-99cf-0d37e735079f.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff80750afa320, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 1509e613-6ccb-43f2-9d01-d6198059bf00.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff804558fa320, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 35b93463-b30d-44e0-9589-194b84b8d557.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff803229fcb52, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: f319a77a-dd5b-4203-b39d-c41474b0253f.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff80355afa320, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d2dcaf61-e64c-42ce-9ca3-45e17ef53ae7.

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64

Loading Dump File [C:\Windows\MEMORY2021-01-04_20-57.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff80059400000 PsLoadedModuleList = 0xfffff8005a02a2b0

Debug session time: Mon Jan 4 20:57:16.956 2021 (UTC - 5:00)

System Uptime: 0 days 1:17:02.735

Loading Kernel Symbols

...............................................................

.......Page 3c5526 not present in the dump file. Type ".hh dbgerr004" for details

.........................................................

................................................................

.............

Loading User Symbols

PEB is paged out (Peb.Ldr = 000000bb`1df51018). Type ".hh dbgerr001" for details

Loading unloaded module list

..............

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff800597f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd001bafa7e20=0000000000000133

Loading Dump File [C:\WINDOWS\MEMORY.DMP]

Could not open dump file [C:\WINDOWS\MEMORY.DMP], Win32 error 0n2

"The system cannot find the file specified."

2: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000001, The system cumulatively spent an extended period of time at

DISPATCH_LEVEL or above. The offending component can usually be

identified with a stack trace.

Arg2: 0000000000001e00, The watchdog period.

Arg3: fffff8005a0fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

additional information regarding the cumulative timeout

Arg4: 0000000000000000

Debugging Details:

*************************************************************************

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: TickPeriods ***

*** ***

*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec

Value: 3483

Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on BRUCE11

Key : Analysis.DebugData

Value: CreateObject

Key : Analysis.DebugModel

Value: CreateObject

Key : Analysis.Elapsed.mSec

Value: 3546

Key : Analysis.Memory.CommitPeak.Mb

Value: 77

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: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8005a0fa320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffc78100f0ec70 -- (.trap 0xffffc78100f0ec70)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000800 rbx=0000000000000000 rcx=ffffc3bffcf3eb80

rdx=ffffc3e1f0f87000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff800596acd72 rsp=ffffc78100f0ee00 rbp=ffffc3bffcf3eb80

r8=0000000000000000 r9=0000000000000002 r10=0000000000000000

r11=ffffb086d042e0c0 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe cy

nt!MiLockTransitionLeafPage+0x2a:

fffff800`596acd72 488bd8 mov rbx,rax

Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: WerFault.exe

STACK_TEXT:

ffffd001bafa7e18 fffff8005983aa0c : 0000000000000133 0000000000000001 0000000000001e00 fffff8005a0fa320 : nt!KeBugCheckEx

ffffd001bafa7e20 fffff8005966f9a3 : 00000c3a490e193d ffffd001baf55180 0000000000000000 ffffd001baf55180 : nt!KeAccumulateTicks+0x1c880c

ffffd001bafa7e80 fffff8005966f48a : ffffb086be6e40e0 ffffc78100f0ecf0 0000000000000000 ffffc3bffcf3eb80 : nt!KeClockInterruptNotify+0x453

ffffd001bafa7f30 fffff80059727ef5 : ffffb086be6e40e0 fffff800597146b7 0000000000000000 0000000000000000 : nt!HalpTimerClockIpiRoutine+0x1a

ffffd001bafa7f60 fffff800597f722a : ffffc78100f0ecf0 ffffb086be6e40e0 ffffb086d042e740 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5

ffffd001bafa7fb0 fffff800597f7797 : 0000000000000800 0000000000000000 0000000000000000 00001f8000000200 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

ffffc78100f0ec70 fffff800596acd72 : ffffd001baf55180 fffff800596937b0 0000000000000000 0000000000000001 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffffc78100f0ee00 fffff800596ac87f : ffffc3bffcf3eb80 0000000000000000 ffffc78100f0ef80 0000000100000001 : nt!MiLockTransitionLeafPage+0x2a

ffffc78100f0ee50 fffff8005969a37d : 00007ff9e7d20000 ffffc3bffcf3e900 ffffc78100f0f608 ffffc78100f0efe0 : nt!MiTryDeleteTransitionPte+0x1f

ffffc78100f0ee80 fffff8005969ad6e : 0000000000000000 ffffc78100f0f590 ffffc3bffcf3f000 ffffc78100f0f4e0 : nt!MiDeletePteRun+0x157d

ffffc78100f0f090 fffff8005960bedd : 0000000000000000 ffffb086d042e740 ffffc78100f0f4e0 ffffc3bffcf3eff8 : nt!MiDeleteVaTail+0x6e

ffffc78100f0f0c0 fffff8005960bafb : ffffc3e100000000 ffffb086d042e740 ffffc78100000000 ffffc78100f0f530 : nt!MiWalkPageTablesRecursively+0xc6d

ffffc78100f0f160 fffff8005960bafb : ffffc3e1f0efff38 ffffb086d042e740 ffffc78100000001 ffffc78100f0f540 : nt!MiWalkPageTablesRecursively+0x88b

ffffc78100f0f200 fffff8005960bafb : ffffc3e1f0eff000 ffffb086d042e740 ffffc78100000002 ffffc78100f0f550 : nt!MiWalkPageTablesRecursively+0x88b

ffffc78100f0f2a0 fffff8005965de6b : 0000000000000000 ffffb086d042e740 0000000000000003 ffffc78100f0f560 : nt!MiWalkPageTablesRecursively+0x88b

ffffc78100f0f340 fffff8005969b991 : ffffc78100f0f4e0 ffffb08600000000 ffffc3bf00000002 0000000000000000 : nt!MiWalkPageTables+0x36b

ffffc78100f0f440 fffff8005966baf0 : 0000000000000001 ffffc78100000000 ffffb086d042e590 ffffb086c9ddf080 : nt!MiDeletePagablePteRange+0x4f1

ffffc78100f0f750 fffff80059a35c99 : ffffb086d02d7140 0000000000000000 ffffb08600000000 ffffb08600000000 : nt!MiDeleteVad+0x360

ffffc78100f0f860 fffff80059a35330 : ffffb086d02d7140 ffffb086cb196270 ffffb086c9ddf080 0000000000000000 : nt!MiUnmapVad+0x49

ffffc78100f0f890 fffff80059a335ff : ffffb086d02d1a60 ffffb086d02d1a60 ffffb086d02d7140 ffffb086d042e0c0 : nt!MiCleanVad+0x30

ffffc78100f0f8c0 fffff80059a5d6e4 : ffffffff00000000 ffffffffffffffff 0000000000000001 ffffb086d042e0c0 : nt!MmCleanProcessAddressSpace+0x137

ffffc78100f0f940 fffff80059b06596 : ffffb086d042e0c0 ffffe68a1ff71730 ffffc78100f0fb90 0000000000000000 : nt!PspRundownSingleProcess+0x20c

ffffc78100f0f9d0 fffff80059ad22e8 : 00000000c000041d 0000000000000001 0000000000000000 000000bb1df52000 : nt!PspExitThread+0x5f6

ffffc78100f0fad0 fffff80059667fb7 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSchedulerApcTerminate+0x38

ffffc78100f0fb10 fffff800597f9d20 : 00007ff9e7d20000 ffffc78100f0fbc0 ffffc78100f0fd00 ffffc78100000000 : nt!KiDeliverApc+0x487

ffffc78100f0fbc0 fffff800597f62bf : 0000000000000000 0000000000000002 0000000000000000 0000000000000000 : nt!KiInitiateUserApc+0x70

ffffc78100f0fd00 fffff800598071b5 : 00000e8c40000a00 0000000000000000 ffffc78100f0fec0 ffffc78100000000 : nt!NtRaiseException+0x13f

ffffc78100f0fe40 00007ff9e8497d12 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25

000000bb1ddbdc20 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff9`e8497d12

SYMBOL_NAME: nt!KeAccumulateTicks+1c880c

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1c880c

FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup: MachineOwner

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Answer 1

Hi Shreffey,

I am Sumit, an Independent Advisor and a 3 year Windows Insider MVP here to help.

>> but Intel says that the driver on the HP ENVY was customized

and so I can only get an update from HP.

This is correct. OEMs make customizations so if you use a generic Intel driver some things may not work.

If there is no new driver, consider reinstalling the same if you haven't.

Completely remove everything of Graphics driver using DDU and install the newest copy of the driver available.

http://www.guru3d.com/files-details/display-dri...

You can head to either the card manufacturer or device manufacturer to get the newest driver.

Standard 3rd party link disclaimer:

There may be links to non-Microsoft websites that would provide accurate and safe information. Watch out for ads on the websites which are frequently classified as a PUP (Potentially Unwanted Products). There is no need to buy paid products to fix your computers as they do more harm than good sometimes.

Share via

Is there a newer version of the Intel HD Graphics 630 driver for the HP ENVY All-in-One - 27-b110

1 answer