VIDEO_DXGKRNL_FATAL_ERROR bluetooth drivers

lexinho021

Estimable
Oct 15, 2014
5
0
4,510
I got Lenovo e540 laptop and when I try to update my intel bloetooth driver i get BSOD with VIDEO_DXGKRNL_FATAL_ERROR,also i cannot open bluetooth options in device manager and my bluetooth doesn't work,wifi does. Is that software or hardware problem and can anyone help me? I also updated BIOS and all the other drivers
 

lexinho021

Estimable
Oct 15, 2014
5
0
4,510
I'm using Lenovo system update software and that update is shown there,also I'tried to download bluetooth driver update from Lenovno website and the same thing happens
 

lexinho021

Estimable
Oct 15, 2014
5
0
4,510
ymbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff801`f6474000 PsLoadedModuleList = 0xfffff801`f674a370
Debug session time: Thu Oct 16 09:30:34.573 2014 (UTC + 2:00)
System Uptime: 0 days 9:02:12.378
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
..............

************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for watchdog.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 113, {19, 2, 10de, 1292}

*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : dxgkrnl.sys ( dxgkrnl+11bd6c )

That's dmp file
 

lexinho021

Estimable
Oct 15, 2014
5
0
4,510
and this in MEMORY.dmp

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x113

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER: from fffff801ca3a59ca to fffff801f65c31a0

STACK_TEXT:
ffffd000`55996458 fffff801`ca3a59ca : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx
ffffd000`55996460 fffff801`ca33cd6c : ffffe001`93717340 ffffe001`975b5bd0 ffffe001`93717340 ffffe001`975b5bd0 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffd000`559964a0 fffff801`ca2b7e7b : 00000000`00000000 ffffe001`93717340 ffffe001`937171f0 ffffe001`975b5bd0 : dxgkrnl!TdrUpdateDbgReport+0x1a2a4
ffffd000`559964e0 fffff801`ca2a6961 : 00000000`00000017 ffffd000`559965e9 00000000`00000000 00000000`00000008 : dxgkrnl!TdrHistoryInit+0x14adb
ffffd000`55996530 fffff801`cac3cac4 : ffffe001`937d4000 ffffe001`975b5bd0 ffffe001`937d4000 ffffe001`8ee0d6b0 : dxgkrnl!TdrHistoryInit+0x35c1
ffffd000`55996650 fffff801`f68cae82 : ffffe001`937171f0 fffff801`cac3ca4c 00000000`00000000 ffffd000`559967b0 : nvlddmkm+0x14bac4
ffffd000`55996700 fffff801`f69074e0 : 00000000`00000017 ffffd000`559967c9 ffffe001`8eef1a20 ffffe001`8eee9060 : nt!RtlHashUnicodeString+0x3b1e
ffffd000`55996770 fffff801`f694745b : ffffc000`9dac7ca0 ffffc000`a7fa3800 00000000`00000000 00000000`00000000 : nt!IoGetDeviceInterfaces+0x2ad4
ffffd000`55996830 fffff801`f6906e26 : ffffe001`8eef1a20 00000000`00000000 ffffc000`a7fa3800 ffffc000`a7fa3800 : nt!RtlCheckRegistryKey+0xb6b
ffffd000`55996890 fffff801`f6906d66 : 00000000`00000000 ffffc000`a7fa3800 ffffe001`8eef1a20 fffff801`f6a17162 : nt!IoGetDeviceInterfaces+0x241a
ffffd000`559968d0 fffff801`f6905f44 : ffffe001`8eee9060 ffffd000`00000002 00000000`00000000 00000000`00000000 : nt!IoGetDeviceInterfaces+0x235a
ffffd000`55996950 fffff801`f68e8cd1 : ffffc000`9dac7c00 00000000`00000001 ffffc000`00000003 ffffe001`ffffffff : nt!IoGetDeviceInterfaces+0x1538
ffffd000`55996ab0 fffff801`f68e9297 : ffffc000`9dac7ca0 00000000`00000000 00000000`00000000 fffff801`f68e8fa0 : nt!IoDeleteAllDependencyRelations+0x140d
ffffd000`55996af0 fffff801`f64e35e3 : fffff801`f68e8fa0 ffffc000`aa8ef990 ffffd000`55996bd0 ffffe001`96274700 : nt!IoDeleteAllDependencyRelations+0x19d3
ffffd000`55996b50 fffff801`f6572e70 : 01ce9f4d`8fd93f69 ffffe001`8f380040 ffffe001`8f380040 ffffe001`8ee00040 : nt!ExfAcquirePushLockExclusive+0xde7
ffffd000`55996c00 fffff801`f65c97c6 : ffffd000`3a54d180 ffffe001`8f380040 ffffd000`3a5593c0 00490043`ffffffc0 : nt!RtlDecompressFragment+0x3a0
ffffd000`55996c60 00000000`00000000 : ffffd000`55997000 ffffd000`55991000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x59d6


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgkrnl!TdrUpdateDbgReport+1a2a4
fffff801`ca33cd6c 83bfd001000000 cmp dword ptr [rdi+1D0h],0

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl!TdrUpdateDbgReport+1a2a4

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: dxgkrnl.sys

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

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