Unsolved
This post is more than 5 years old
1 Message
3
23494
E7470 BSOD when removed from Docking station
Hi,
Pretty much what the title says..... When I remove the Latitude E7470 from
the docking station (E-Port Plus II Model PRO2X)
it Blue Screens with a APC_INDEX_MISMATCH.
Can anyone help with what I pasted.
Thanks
Microsoft (R) Windows Debugger Version 10.0.17030.1002 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [Z:\121117-9063-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600 Machine Name: Kernel base = 0xfffff800`03813000 PsLoadedModuleList = 0xfffff800`03a55750 Debug session time: Mon Dec 11 14:39:52.555 2017 (UTC - 5:00) System Uptime: 0 days 0:02:57.467 Loading Kernel Symbols ............................................................... ................................................................ ................................................ Loading User Symbols Loading unloaded module list ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1, {76fcbdaa, 0, ffff, fffff88007c46b60} Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 ) Followup: MachineOwner --------- nt!KeBugCheckEx: fffff800`03883e00 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`07c46930=0000000000000001
******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 0000000076fcbdaa, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff88007c46b60, Call type (0 - system call, 1 - worker routine)
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
SYSTEM_MANUFACTURER: Dell Inc.
SYSTEM_PRODUCT_NAME: Latitude E7470
SYSTEM_SKU: 06DC
BIOS_VENDOR: Dell Inc.
BIOS_VERSION: 1.17.5
BIOS_DATE: 07/11/2017
BASEBOARD_MANUFACTURER: Dell Inc.
BASEBOARD_PRODUCT: 0T6HHJ
BASEBOARD_VERSION: A00
DUMP_TYPE: 2
BUGCHECK_P1: 76fcbdaa
BUGCHECK_P2: 0
BUGCHECK_P3: ffff
BUGCHECK_P4: fffff88007c46b60
FAULTING_IP:
+0
00000000`76fcbdaa ?? ???
CPU_COUNT: 4
CPU_MHZ: 9c0
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 4e
CPU_STEPPING: 3
CPU_MICROCODE: 6,4e,3,0 (F,M,S,R) SIG: BA'00000000 (cache) BA'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x1
PROCESS_NAME: audiodg.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: WORK-COMPUTER
ANALYSIS_SESSION_TIME: 12-12-2017 12:08:32.0695
ANALYSIS_VERSION: 10.0.17030.1002 amd64fre
LAST_CONTROL_TRANSFER: from fffff800038833a9 to fffff80003883e00
STACK_TEXT:
fffff880`07c46928 fffff800`038833a9 : 00000000`00000001 00000000`76fcbdaa 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`07c46930 fffff800`038832e0 : fffffa80`204e8b50 00000000`0311e3b8 fffff880`07c46a88 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`07c46a70 00000000`76fcbdaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`0311e388 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fcbdaa
THREAD_SHA1_HASH_MOD_FUNC: 713a38487ff3d82058f51d9870e0b3de39cbf964
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 561f1421a866d36916a994b3bd23a42b1aea0bb5
THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b
FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`038832e0 4883ec50 sub rsp,50h
FAULT_INSTR_CODE: 50ec8348
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiSystemServiceExit+245
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 59b946d1
IMAGE_VERSION: 6.1.7601.23915
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
BUCKET_ID: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
PRIMARY_PROBLEM_CLASS: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
TARGET_TIME: 2017-12-11T19:39:52.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
lfudala
5 Posts
1
December 12th, 2017 13:00
Have 3 7470s getting BSOD since updating to BIOS 1.17.5. The other almost 20 on older version are fine. 1 crashes on every undock. The other 2 are crashing while docked.
ieee488
4 Operator
4 Operator
•
11.1K Posts
1
December 12th, 2017 13:00
Google on APC_INDEX_MISMATCH
ToeKnee600
5 Posts
1
December 14th, 2017 13:00
I too have bluescreens with very similar dump files on Dell E7470 bios version 1.17.5.
(twice when plugging an HDMI external display and once just opening an application)
My other E7470 are not at same bios have not seen this issue either.
I have just downgraded my bios to 1.16.4 and see if the problem goes away.
Thanks -TC
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\TonyStuff\MyDocuments\DebugDiag\Reports\121217-5912-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
************* Symbol Path validation summary **************
Response Time (ms) Location
OK C:\symbols
Symbol search path is: C:\symbols;SRV*C:\symbolscache*msdl.microsoft.com/.../symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
Machine Name:
Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`0324e750
Debug session time: Tue Dec 12 11:20:41.125 2017 (UTC - 6:00)
System Uptime: 0 days 0:50:24.299
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1, {7722bdaa, 0, ffff, fffff8800e09eb60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 000000007722bdaa, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff8800e09eb60, Call type (0 - system call, 1 - worker routine)
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
SYSTEM_MANUFACTURER: Dell Inc.
SYSTEM_PRODUCT_NAME: Latitude E7470
SYSTEM_SKU: 06DC
BIOS_VENDOR: Dell Inc.
BIOS_VERSION: 1.17.5
BIOS_DATE: 07/11/2017
BASEBOARD_MANUFACTURER: Dell Inc.
BASEBOARD_PRODUCT: 0T6HHJ
BASEBOARD_VERSION: A00
DUMP_TYPE: 2
BUGCHECK_P1: 7722bdaa
BUGCHECK_P2: 0
BUGCHECK_P3: ffff
BUGCHECK_P4: fffff8800e09eb60
FAULTING_IP:
+0
00000000`7722bdaa ?? ???
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: BA'00000000 (cache) BA'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x1
PROCESS_NAME: audiodg.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: 4X6SKC2
ANALYSIS_SESSION_TIME: 12-12-2017 14:26:55.0419
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff8000307c3a9 to fffff8000307ce00
STACK_TEXT:
fffff880`0e09e928 fffff800`0307c3a9 : 00000000`00000001 00000000`7722bdaa 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0e09e930 fffff800`0307c2e0 : fffffa80`296ee410 00000000`00d0dee8 fffff880`0e09ea88 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`0e09ea70 00000000`7722bdaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`00d0deb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7722bdaa
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 713a38487ff3d82058f51d9870e0b3de39cbf964
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 561f1421a866d36916a994b3bd23a42b1aea0bb5
THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b
FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`0307c2e0 4883ec50 sub rsp,50h
FAULT_INSTR_CODE: 50ec8348
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiSystemServiceExit+245
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 59b946d1
IMAGE_VERSION: 6.1.7601.23915
FAILURE_BUCKET_ID: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
BUCKET_ID: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
PRIMARY_PROBLEM_CLASS: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
TARGET_TIME: 2017-12-12T17:20:41.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-09-13 09:55:13
BUILDDATESTAMP_STR: 170913-0600
BUILDLAB_STR: win7sp1_ldr
BUILDOSVER_STR: 6.1.7601.23915.amd64fre.win7sp1_ldr.170913-0600
ANALYSIS_SESSION_ELAPSED_TIME: 46d
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x1_syscallnum_4_nt!kisystemserviceexit+245
FAILURE_ID_HASH: {e506ede0-d282-2e4c-5056-6cb373197a73}
Followup: MachineOwner
ToeKnee600
5 Posts
1
December 14th, 2017 13:00
I too have a Dell E7470 running windows 7, I got the same BSOD, 3 times , (Twice pluging an HDMI monitor in, and other just starting an application), APC_INDEX_MISMATCH (1), all pointing to process: audiodg.exe when I upgraded to Bios 1.17.5 also.
I am testing down grading the bios to 1.16.4 to see if the these go away. I am not seeing this on my other E7470 but they were not on this version of bios of 1.17.5.
Here is a sample of my debug when plugging an HDMI monitor.
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\TonyStuff\MyDocuments\DebugDiag\Reports\121217-5912-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
************* Symbol Path validation summary **************
Response Time (ms) Location
OK C:\symbols
Symbol search path is: C:\symbols;SRV*C:\symbolscache*msdl.microsoft.com/.../symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
Machine Name:
Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`0324e750
Debug session time: Tue Dec 12 11:20:41.125 2017 (UTC - 6:00)
System Uptime: 0 days 0:50:24.299
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1, {7722bdaa, 0, ffff, fffff8800e09eb60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 000000007722bdaa, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff8800e09eb60, Call type (0 - system call, 1 - worker routine)
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
SYSTEM_MANUFACTURER: Dell Inc.
SYSTEM_PRODUCT_NAME: Latitude E7470
SYSTEM_SKU: 06DC
BIOS_VENDOR: Dell Inc.
BIOS_VERSION: 1.17.5
BIOS_DATE: 07/11/2017
BASEBOARD_MANUFACTURER: Dell Inc.
BASEBOARD_PRODUCT: 0T6HHJ
BASEBOARD_VERSION: A00
DUMP_TYPE: 2
BUGCHECK_P1: 7722bdaa
BUGCHECK_P2: 0
BUGCHECK_P3: ffff
BUGCHECK_P4: fffff8800e09eb60
FAULTING_IP:
+0
00000000`7722bdaa ?? ???
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: BA'00000000 (cache) BA'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x1
PROCESS_NAME: audiodg.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: 4X6SKC2
ANALYSIS_SESSION_TIME: 12-12-2017 14:26:55.0419
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff8000307c3a9 to fffff8000307ce00
STACK_TEXT:
fffff880`0e09e928 fffff800`0307c3a9 : 00000000`00000001 00000000`7722bdaa 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0e09e930 fffff800`0307c2e0 : fffffa80`296ee410 00000000`00d0dee8 fffff880`0e09ea88 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`0e09ea70 00000000`7722bdaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`00d0deb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7722bdaa
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 713a38487ff3d82058f51d9870e0b3de39cbf964
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 561f1421a866d36916a994b3bd23a42b1aea0bb5
THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b
FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`0307c2e0 4883ec50 sub rsp,50h
FAULT_INSTR_CODE: 50ec8348
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiSystemServiceExit+245
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 59b946d1
IMAGE_VERSION: 6.1.7601.23915
FAILURE_BUCKET_ID: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
BUCKET_ID: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
PRIMARY_PROBLEM_CLASS: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245
TARGET_TIME: 2017-12-12T17:20:41.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-09-13 09:55:13
BUILDDATESTAMP_STR: 170913-0600
BUILDLAB_STR: win7sp1_ldr
BUILDOSVER_STR: 6.1.7601.23915.amd64fre.win7sp1_ldr.170913-0600
ANALYSIS_SESSION_ELAPSED_TIME: 46d
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x1_syscallnum_4_nt!kisystemserviceexit+245
FAILURE_ID_HASH: {e506ede0-d282-2e4c-5056-6cb373197a73}
Followup: MachineOwner
ToeKnee600
5 Posts
0
December 14th, 2017 13:00
I too have the same debug analysis pointing to audiodg.exe but when plugging in HDMI external monitor and once just opening an application. I am testing a downgraded bios version 1.16.4.
I was at 1.17.5 running a Dell E7470 with Windows 7.
Nny117
1 Message
0
December 15th, 2017 12:00
I am also receiving the same error, but slightly different. This is confirmed on 3 different E7470s while either on a dock or removed from a docking station.
==================================================
Dump File : 120517-10623-01.dmp
Crash Time : 12/5/2017 12:17:13 PM
Bug Check String : APC_INDEX_MISMATCH
Bug Check Code : 0x00000001
Parameter 1 : 00000000`77c1bdaa
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`0000ffff
Parameter 4 : fffff880`2a644b60
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70e00
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70e00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : F:\Documents\BSOD\janneth\120517-10623-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 598,224
Dump File Time : 12/5/2017 1:34:02 PM
==================================================
Peppo1
3 Posts
0
December 18th, 2017 03:00
Hi,
we have the same issue with 2 of our 7470s. The laptops crashed frequently when docked, but also in meeting rooms without docking. We got rid of the problem on one laptop by reinstalling it completely. On the other we still have the same issue. Drivers and BIOS have been updated with DELL command Update. We have a support case open, but so far we were only asked to try previous version of the audio driver. Unfortunately we are still getting the BSODs and the user is getting annoyed.
lfudala
5 Posts
2
December 20th, 2017 07:00
The downgrade in the Intel Driver, to 21.20.16.4627, appears to have stopped the issue here as well. 4727 seems to the only other immediately identifiable commonality in my systems since BSODs started.
Peppo1
3 Posts
4
December 20th, 2017 07:00
I have used Dell command update to update all drivers on the affected 7470s.
After some more bluescreens I removed the Realtek audio driver and the Intel video (including display audio) and installed previous versions:
Realtek-High-Definition-Audio-Driver_331N1_WIN_6.0.1.6122_A08
Intel-HD-Graphics-500-P500-600-P600-series-Driver_C2N7T_WIN_21.20.16.4627_A02
There have been no BSODs for 2 days now. I am keeping my fingers crossed it keeps that way and this is finally solved!
Brian42
10 Posts
0
December 20th, 2017 07:00
The folks that tried the BIOS version 1.16.4,1, how has that worked out for you?
Unfortunately, rolling back the BIOS to 1.16.4.1 on an affected machine did not stop the blue screens.
Also... Speaking of the BIOS... In the details for BIOS 1.17.5, what does "Fixed system black screen issue if exit BIOS setup after attached external display device on docking" even mean?!? Does the issue occur if a user attaches/connects an external monitor while in the BIOS? Does the issue occur if the user has an external monitor attached prior to entering the BIOS?
Brian42
10 Posts
0
December 20th, 2017 11:00
Downgrading the Realtek audio driver wasn't needed?
lfudala
5 Posts
0
December 20th, 2017 12:00
I have not went back up on any of them with the Realtek driver. When I tried multiple earlier versions of it, they all crashed, still. Only after downgrading the Display Audio driver did they stop crashing.