Issue metadata
Sign in to add a comment
|
Chrome causes a BSOD when opening/loading pages
Reported by
seklan...@gmail.com,
Aug 28 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome 2. Boom -OR- 1. Open new tab 2. Go to any website (even www.google.com) 3. Boom -OR- 1. Hit 'Restore tabs' since it's already crashed 6 times today 2. Boom What is the expected behavior? The browser should not cause a BSOD What went wrong? SYSTEM_SERVICE_EXCEPTION in wdf01000.sys Did this work before? Yes before 22 July 2017 Chrome version: 60.0.3112.113 Channel: stable OS Version: 10.0 Flash Version: This happens like 5 times a day. I have to use other browsers just so my computer won't lose all my work because of Chrome.
,
Aug 29 2017
cb259666-605f-46bb-982e-818736befced
,
Aug 29 2017
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 29 2017
I am investigating further, but the issue may be connected to the Intel Display Driver. This would make sense, as Chrome uses the graphics in a way other browsers do not. As to who is at fault, I do not know if Chrome is behaving inappropriately or there is an issue with the driver, but I am investigating this scenario.
,
Aug 30 2017
seklandja@, Thanks for the reply. We are unable to reproduce the issue on Windows 7,Mac 10.12.6 & Ubuntu 14.04 using latest stable#60.0.3112.113 . Could you please provide us the server is from chrome://crashes for the recent crash you observed as per the attached screenshot.
,
Aug 30 2017
Unfortunately, the problem isn't that Chrome itself is crashing. Chrome is causing the Intel Display Driver to crash, which is why it results in a BSOD. This should only affect Windows. I am using Windows 10 on a Surface Book, with Intel HD Graphics 520.
,
Aug 30 2017
Furthermore, I checked my update history, and there were no updates to any graphics drivers within the last 3 or 4 months.
,
Aug 30 2017
Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 1 2017
It continues to crash. If I completely uninstall the Intel Graphics Driver through the Device Manager, and use the generic Windows VGA-compatible Graphics Driver, or run Chrome on the NVIDIA graphics card, there is no crashing and everything works fine and perfectly. However, being as this is a Surface Book, I am frequently detaching the part of the laptop that has the NVIDIA graphics card, so this is more of a stop-gap solution than anything. I don't know how much it would help, but I have about 40 more minidump files if they could be of any use.
,
Sep 1 2017
More data from Windows event viewer, all of these are from a single crash: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-09-01 17:38:36 Event ID: 1001 Task Category: None Level: Error Keywords: Classic User: N/A Computer: magnesium Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8044e265d2b, 0xffffc100df1205b0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 62bc08b7-3d02-4ef6-b9b3-589351b84b9d. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-09-01T21:38:36.337630300Z" /> <EventRecordID>38354</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>magnesium</Computer> <Security /> </System> <EventData> <Data Name="param1">0x0000003b (0x00000000c0000005, 0xfffff8044e265d2b, 0xffffc100df1205b0, 0x0000000000000000)</Data> <Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data> <Data Name="param3">62bc08b7-3d02-4ef6-b9b3-589351b84b9d</Data> </EventData> </Event> Log Name: Application Source: Windows Error Reporting Date: 2017-09-01 17:38:40 Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: magnesium Description: Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff8044e265d2b P4: ffffc100df1205b0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\090117-14546-01.dmp \\?\C:\Windows\Temp\WER-23125-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AA0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AC0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AD0.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_9b6bb023472bc64e9c96a133197115656d9fe6ac_00000000_035c6acf Analysis symbol: Rechecking for solution: 0 Report Id: 62bc08b7-3d02-4ef6-b9b3-589351b84b9d Report Status: 4 Hashed bucket: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-09-01T21:38:40.607165200Z" /> <EventRecordID>264129</EventRecordID> <Channel>Application</Channel> <Computer>magnesium</Computer> <Security /> </System> <EventData> <Data> </Data> <Data>0</Data> <Data>BlueScreen</Data> <Data>Not available</Data> <Data>0</Data> <Data>3b</Data> <Data>c0000005</Data> <Data>fffff8044e265d2b</Data> <Data>ffffc100df1205b0</Data> <Data>0</Data> <Data>10_0_15063</Data> <Data>0_0</Data> <Data>256_1</Data> <Data> </Data> <Data> </Data> <Data> \\?\C:\WINDOWS\Minidump\090117-14546-01.dmp \\?\C:\Windows\Temp\WER-23125-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AA0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AC0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AD0.tmp.txt</Data> <Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_9b6bb023472bc64e9c96a133197115656d9fe6ac_00000000_035c6acf</Data> <Data> </Data> <Data>0</Data> <Data>62bc08b7-3d02-4ef6-b9b3-589351b84b9d</Data> <Data>4</Data> <Data> </Data> </EventData> </Event> Log Name: Application Source: Windows Error Reporting Date: 2017-09-01 17:38:41 Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: magnesium Description: Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff8044e265d2b P4: ffffc100df1205b0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\090117-14546-01.dmp \\?\C:\Windows\Temp\WER-23125-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AA0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AC0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AD0.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_9b6bb023472bc64e9c96a133197115656d9fe6ac_00000000_cab_1f086d8e Analysis symbol: Rechecking for solution: 0 Report Id: 62bc08b7-3d02-4ef6-b9b3-589351b84b9d Report Status: 2049 Hashed bucket: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-09-01T21:38:41.377587500Z" /> <EventRecordID>264130</EventRecordID> <Channel>Application</Channel> <Computer>magnesium</Computer> <Security /> </System> <EventData> <Data> </Data> <Data>0</Data> <Data>BlueScreen</Data> <Data>Not available</Data> <Data>0</Data> <Data>3b</Data> <Data>c0000005</Data> <Data>fffff8044e265d2b</Data> <Data>ffffc100df1205b0</Data> <Data>0</Data> <Data>10_0_15063</Data> <Data>0_0</Data> <Data>256_1</Data> <Data> </Data> <Data> </Data> <Data> \\?\C:\WINDOWS\Minidump\090117-14546-01.dmp \\?\C:\Windows\Temp\WER-23125-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AA0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AC0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AD0.tmp.txt</Data> <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_9b6bb023472bc64e9c96a133197115656d9fe6ac_00000000_cab_1f086d8e</Data> <Data> </Data> <Data>0</Data> <Data>62bc08b7-3d02-4ef6-b9b3-589351b84b9d</Data> <Data>2049</Data> <Data> </Data> </EventData> </Event>
,
Sep 1 2017
I obtained this data using NirSoft's BlueScreenView. I've only included the ones that were marked as causes for the BSOD. This is from the same crash as the above mentioned data. The minidump file is attached. NTFS.sys NTFS.sys+cfd22 fffff804`4ebd0000 fffff804`4ee13000 0x00243000 0x634a21b1 2022-10-14 22:57:53 Microsoft® Windows® Operating System NT File System Driver 10.0.15063.0 (WinBuild.160101.0800) Microsoft Corporation C:\WINDOWS\system32\drivers\NTFS.sys ntoskrnl.exe ntoskrnl.exe+1778a9 fffff800`39083000 fffff800`3990c000 0x00889000 0x597fd80d 2017-07-31 21:23:25 Microsoft® Windows® Operating System NT Kernel & System 10.0.15063.540 (WinBuild.160101.0800) Microsoft Corporation C:\WINDOWS\system32\ntoskrnl.exe Wdf01000.sys Wdf01000.sys+5d2b fffff804`4e260000 fffff804`4e33e000 0x000de000 0x26eee197 1990-09-12 21:32:07 Microsoft® Windows® Operating System Kernel Mode Driver Framework Runtime 1.21.15063.0 (WinBuild.160101.0800) Microsoft Corporation C:\WINDOWS\system32\drivers\Wdf01000.sys
,
Sep 1 2017
In summary, this is clearly caused by a change in Chrome since 2017-07-22 which causes the Intel Graphics Driver to cause Windows itself to crash. Whether this happens because of a bug in the Intel Graphics Driver itself, I don't have the skills to figure that out, but I know that the driver hasn't changed for many months before these crashes started to happen.
,
Sep 2 2017
WinDbg pieced it all together:
Microsoft (R) Windows Debugger Version 10.0.16270.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Zeklandia\Downloads\090117-14546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff800`39083000 PsLoadedModuleList = 0xfffff800`393cf5c0
Debug session time: Fri Sep 1 17:37:26.278 2017 (UTC - 4:00)
System Uptime: 0 days 0:48:56.048
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
..................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8044e265d2b, ffffc100df1205b0, 0}
Probably caused by : Microsoft.Bluetooth.Legacy.LEEnumerator.sys ( Microsoft_Bluetooth_Legacy_LEEnumerator!Microsoft::Bluetooth::Legacy::LEEnumerator::DeviceFdo::QueueFileRequest+1f8 )
Followup: MachineOwner
---------
nt!KeBugCheckEx:
fffff800`391ef560 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc100`df11fce0=000000000000003b
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8044e265d2b, Address of the instruction which caused the bugcheck
Arg3: ffffc100df1205b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.15063.540 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: Microsoft Corporation
SYSTEM_PRODUCT_NAME: Surface Book
SYSTEM_SKU: Surface_Book
SYSTEM_VERSION: D:0B:09F:1C:03P:38
BIOS_VENDOR: Microsoft Corporation
BIOS_VERSION: 90.1427.768
BIOS_DATE: 12/19/2016
BASEBOARD_MANUFACTURER: Microsoft Corporation
BASEBOARD_PRODUCT: Surface Book
DUMP_TYPE: 2
BUGCHECK_P1: c0000005
BUGCHECK_P2: fffff8044e265d2b
BUGCHECK_P3: ffffc100df1205b0
BUGCHECK_P4: 0
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
FAULTING_IP:
Wdf01000!FxObjectHandleGetPtrQI+3b [minkernel\wdf\framework\shared\object\handleapi.cpp @ 376]
fffff804`4e265d2b 488b4028 mov rax,qword ptr [rax+28h]
CONTEXT: ffffc100df1205b0 -- (.cxr 0xffffc100df1205b0)
rax=0000000000000005 rbx=ffff818dc35a1860 rcx=ffff818dc35a1860
rdx=ffffc100df120ff0 rsi=00007e723ca5e798 rdi=0000000000001028
rip=fffff8044e265d2b rsp=ffffc100df120fa0 rbp=ffffc100df1210d9
r8=00007e723ca5e798 r9=0000000000001028 r10=0000000000000000
r11=ffffc100df121008 r12=fffff8003b886768 r13=ffff818dd4b131a0
r14=00007e7226fe0700 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
Wdf01000!FxObjectHandleGetPtrQI+0x3b:
fffff804`4e265d2b 488b4028 mov rax,qword ptr [rax+28h] ds:002b:00000000`0000002d=????????????????
Resetting default scope
CPU_COUNT: 4
CPU_MHZ: af8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 4e
CPU_STEPPING: 3
CPU_MICROCODE: 6,4e,3,0 (F,M,S,R) SIG: 9E'00000000 (cache) 9E'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: MAGNESIUM
ANALYSIS_SESSION_TIME: 09-01-2017 23:47:04.0912
ANALYSIS_VERSION: 10.0.16270.1000 amd64fre
LAST_CONTROL_TRANSFER: from fffff8044e2a3ed6 to fffff8044e265d2b
STACK_TEXT:
ffffc100`df120fa0 fffff804`4e2a3ed6 : ffffffff`fa0a1f00 00007e72`26fe07d8 ffffffff`ffffffa1 fffff800`3b88f6f2 : Wdf01000!FxObjectHandleGetPtrQI+0x3b [minkernel\wdf\framework\shared\object\handleapi.cpp @ 376]
ffffc100`df121010 fffff800`3b88f6f8 : 00007e72`26fe0700 00000000`00000000 ffff818d`d59fa020 ffff818d`d901f820 : Wdf01000!imp_WdfTimerStart+0x42976 [minkernel\wdf\framework\shared\core\fxtimerapi.cpp @ 235]
ffffc100`df121050 fffff800`3b88e467 : fffff800`00000000 ffff818d`c0000022 00000000`00000000 00007e72`2444e618 : Microsoft_Bluetooth_Legacy_LEEnumerator!Microsoft::Bluetooth::Legacy::LEEnumerator::DeviceFdo::QueueFileRequest+0x1f8
ffffc100`df121140 fffff804`4e268d4c : 00007e72`2a6148e8 ffffc100`df121299 ffff818d`dbbb19e0 00000000`00000000 : Microsoft_Bluetooth_Legacy_LEEnumerator!Microsoft::Bluetooth::Legacy::LEEnumerator::DeviceFdo::DeviceFileCreate+0x167
ffffc100`df1211c0 fffff804`4e26701f : ffff818d`bcc8ec00 ffffc100`df121388 ffff818d`d70a5701 ffff818d`d57b4010 : Wdf01000!FxPkgGeneral::OnCreate+0xa0c [minkernel\wdf\framework\shared\irphandlers\general\fxpkggeneral.cpp @ 1302]
ffffc100`df121300 fffff800`3951a265 : ffff818d`d57a8390 ffffc100`df1216d0 ffff818d`d57a8390 ffff9b82`0f040001 : Wdf01000!FxDevice::DispatchWithLock+0x5df [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]
ffffc100`df1213f0 fffff800`3952561b : fffff800`39519a50 fffff800`39519a50 ffffc100`00000000 ffff818d`d5a5fa90 : nt!IopParseDevice+0x815
ffffc100`df1215d0 fffff800`39529150 : ffff818d`c2da9400 ffffc100`df121838 00000000`00000040 ffff818d`bcc8ec60 : nt!ObpLookupObjectName+0x46b
ffffc100`df1217a0 fffff800`3952d0ca : ffff818d`00000001 ffff818d`dbc6e6c0 000000aa`113fefe8 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1e0
ffffc100`df1218e0 fffff800`3952e159 : 000000aa`113fef70 00000000`00000000 000000aa`113fefe8 000000aa`113fef88 : nt!IopCreateFile+0x3aa
ffffc100`df121980 fffff800`391fa413 : 00000000`00000a18 fffff800`39528e6b 00000000`00000000 fffff800`3953322f : nt!NtCreateFile+0x79
ffffc100`df121a10 00007ffe`4e7b5e44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000aa`113feef8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`4e7b5e44
THREAD_SHA1_HASH_MOD_FUNC: 209c9bfdcfb12567be025c104901fb139fecfa0f
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 08f94d27032c9a02c3f8d1bf9a376d7317b0ef68
THREAD_SHA1_HASH_MOD: f377fca980aa41c961abd1ee7787227144ce9d10
FOLLOWUP_IP:
Microsoft_Bluetooth_Legacy_LEEnumerator!Microsoft::Bluetooth::Legacy::LEEnumerator::DeviceFdo::QueueFileRequest+1f8
fffff800`3b88f6f8 b803010000 mov eax,103h
FAULT_INSTR_CODE: 103b8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: Microsoft_Bluetooth_Legacy_LEEnumerator!Microsoft::Bluetooth::Legacy::LEEnumerator::DeviceFdo::QueueFileRequest+1f8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Microsoft_Bluetooth_Legacy_LEEnumerator
IMAGE_NAME: Microsoft.Bluetooth.Legacy.LEEnumerator.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.15063.496
STACK_COMMAND: .cxr 0xffffc100df1205b0 ; kb
BUCKET_ID_FUNC_OFFSET: 1f8
FAILURE_BUCKET_ID: 0x3B_Microsoft_Bluetooth_Legacy_LEEnumerator!Microsoft::Bluetooth::Legacy::LEEnumerator::DeviceFdo::QueueFileRequest
BUCKET_ID: 0x3B_Microsoft_Bluetooth_Legacy_LEEnumerator!Microsoft::Bluetooth::Legacy::LEEnumerator::DeviceFdo::QueueFileRequest
PRIMARY_PROBLEM_CLASS: 0x3B_Microsoft_Bluetooth_Legacy_LEEnumerator!Microsoft::Bluetooth::Legacy::LEEnumerator::DeviceFdo::QueueFileRequest
TARGET_TIME: 2017-09-01T21:37:26.000Z
OSBUILD: 15063
OSSERVICEPACK: 540
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-07-31 21:23:25
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.15063.540
ANALYSIS_SESSION_ELAPSED_TIME: 4db
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x3b_microsoft_bluetooth_legacy_leenumerator!microsoft::bluetooth::legacy::leenumerator::devicefdo::queuefilerequest
FAILURE_ID_HASH: {64b9bd72-40f1-0823-f343-0ba636dc3635}
Followup: MachineOwner
---------
3: kd> lmvm Microsoft_Bluetooth_Legacy_LEEnumerator
Browse full module list
start end module name
fffff800`3b880000 fffff800`3b89e000 Microsoft_Bluetooth_Legacy_LEEnumerator # (pdb symbols) C:\ProgramData\Dbg\sym\Microsoft.Bluetooth.Legacy.LEEnumerator.pdb\B72E592444A7A15CF27E7486D3949BA31\Microsoft.Bluetooth.Legacy.LEEnumerator.pdb
Loaded symbol image file: Microsoft.Bluetooth.Legacy.LEEnumerator.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\Microsoft.Bluetooth.Legacy.LEEnumerator.sys\D0CDF8481e000\Microsoft.Bluetooth.Legacy.LEEnumerator.sys
Image path: \SystemRoot\System32\drivers\Microsoft.Bluetooth.Legacy.LEEnumerator.sys
Image name: Microsoft.Bluetooth.Legacy.LEEnumerator.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: D0CDF848 (This is a reproducible build file hash, not a timestamp)
CheckSum: 0001F343
ImageSize: 0001E000
File version: 10.0.15063.496
Product version: 10.0.15063.496
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: Microsoft.Bluetooth.Legacy.LEEnumerator.SYS
OriginalFilename: Microsoft.Bluetooth.Legacy.LEEnumerator.SYS
ProductVersion: 10.0.15063.496
FileVersion: 10.0.15063.496 (WinBuild.160101.0800)
FileDescription: Legacy Bluetooth LE Bus Enumerator
LegalCopyright: © Microsoft Corporation. All rights reserved.
,
Sep 2 2017
If anyone can tell me why Chrome causes the Microsoft Legacy Bluetooth LE Bus Enumerator driver to crash while using Intel integrated graphics, by all means, go ahead.
,
Sep 5 2017
I have had to use Opera/Firefox/Vivaldi/Edge in the meantime because none of them cause this problem. Since Opera and Vivaldi are Chromium based, that makes this problem specific to Google Chrome. I would love to test this out by using Chromium, but I don't really have the time for my computer to keep BSODing when I'm doing schoolwork.
,
Sep 6 2017
Based on the comments received from #9, 12, 13, 14, 15, 16, 17, seems to be out of TE's scope. Can someone from Dev team please look into this issue. Adding the label 'TE-NeedsTriageHelp'. Thanks.
,
Oct 23 2017
I am still experiencing this issue, even on Chrome 62 stable. If it helps, I've noticed the issue seems to correlate to Chrome losing or gaining focus/visibility: - switching Windows' virtual desktops - resuming from sleep or suspension (lock screen activating) - minimizing This would make sense, since the issue is also connected to the Intel Graphics Driver. Please tell me what I need to do to get the information needed for someone to fix this, it's been driving me nuts for 4 months.
,
Oct 23 2017
AFAICT it's pretty impossible to guess the reason. Maybe you can find the smallest working/crashing range using Chromium snapshots: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/ v58 is roughly 454000 v60 is roughly 475000
,
Oct 23 2017
Unfortunately, this issue isn't Chrome crashing, it's Chrome crashing Windows. Thus, there are no Chrome crash reports generated, since Chrome did not crash.
,
Oct 23 2017
#22, crash report is not needed. Simply download any snapshot in the range from #21, unpack and run e.g. chrome --user-data-dir=d:\temp If it works, proceed with the subsequent range, otherwise the preceding range. You can automate the process a bit https://www.chromium.org/developers/bisect-builds-py The only inconvenience is that you'll need to write down the currently displayed range.
,
Oct 24
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by brajkumar@chromium.org
, Aug 29 2017Labels: Needs-Triage-M60 Needs-Feedback