My Dell Laptop is getting blue screen

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

neeraji

Thread Starter
Joined
May 9, 2018
Messages
2
Sometimes, when I undock my computer, I get a blue screen that reboots. It has been able to restart, but I have received the blue screen at least 4 times this month.

Windows debugger says that it is Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+2aa )
Test report
---------------------------
Loading User Symbols
Loading unloaded module list
.............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {77b9991a, 0, ffff, fffff880059edb60}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+2aa )

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

0: 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: 0000000077b9991a, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff880059edb60, Call type (0 - system call, 1 - worker routine)

Debugging Details:
------------------


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 7601.24094.amd64fre.win7sp1_ldr_escrow.180330-1600

SYSTEM_MANUFACTURER: Dell Inc.

SYSTEM_PRODUCT_NAME: Latitude E7470

SYSTEM_SKU: 06DC

BIOS_VENDOR: Dell Inc.

BIOS_VERSION: 1.18.5

BIOS_DATE: 12/11/2017

BASEBOARD_MANUFACTURER: Dell Inc.

BASEBOARD_PRODUCT: 0T6HHJ

BASEBOARD_VERSION: A00

DUMP_TYPE: 2

BUGCHECK_P1: 77b9991a

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: fffff880059edb60

FAULTING_IP:
+0
00000000`77b9991a ?? ???

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: C2'00000000 (cache) C2'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: DL-BSS4T72

ANALYSIS_SESSION_TIME: 05-09-2018 20:53:47.0696

ANALYSIS_VERSION: 10.0.17134.12 amd64fre

LAST_CONTROL_TRANSFER: from fffff800038d2729 to fffff800038c24a0

STACK_TEXT:
fffff880`059ed928 fffff800`038d2729 : 00000000`00000001 00000000`77b9991a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`059ed930 fffff800`038d2635 : fffffa80`22d25b50 00000000`00a4def8 fffff880`059eda88 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`059eda70 00000000`77b9991a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x2aa
00000000`00a4dec8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b9991a


THREAD_SHA1_HASH_MOD_FUNC: 713a38487ff3d82058f51d9870e0b3de39cbf964

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8a4816d71fc5737e3871923fa5e27863b4ba4379

THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

FOLLOWUP_IP:
nt!KiSystemServiceExit+2aa
fffff800`038d2635 4883ec50 sub rsp,50h

FAULT_INSTR_CODE: 50ec8348

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiSystemServiceExit+2aa

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5abedd8c

IMAGE_VERSION: 6.1.7601.24094

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+2aa

BUCKET_ID: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+2aa

PRIMARY_PROBLEM_CLASS: X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+2aa

TARGET_TIME: 2018-05-04T00:21: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: 2018-03-31 06:29:56

BUILDDATESTAMP_STR: 180330-1600

BUILDLAB_STR: win7sp1_ldr_escrow

BUILDOSVER_STR: 6.1.7601.24094.amd64fre.win7sp1_ldr_escrow.180330-1600

ANALYSIS_SESSION_ELAPSED_TIME: 3e4

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x1_syscallnum_4_nt!kisystemserviceexit+2aa

FAILURE_ID_HASH: {b31de09c-628b-efe2-bb42-b343f7030974}

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

Attachments

Joined
Jan 7, 2014
Messages
2,681
My personal preference is to shut down before undocking. One of the guys here at work kept losing his monitor settings until he started shutting down before undocking.
 

neeraji

Thread Starter
Joined
May 9, 2018
Messages
2
That's right, even I preferred to do the same way. but when there is a meeting and need to undock and walk to the conference room. can't just shut down and open application all over again. Looking for the permanent fix.

wanted to know what is the driver is causing this or maybe the windows?
 

blues_harp28

Moderator
Joined
Jan 9, 2005
Messages
19,449
Hi,
Probably caused by : ntkrnlmp.exe
Is a generic term and not telling us much.
However,
PROCESS_NAME: audiodg.exe
Update your audio drivers. Always go to the manufacturers website to update drivers.
http://www.dell.com/support/home/uk...port/product/latitude-e7470-ultrabook/drivers
======
Also run System File Checker.
Click on Start - Search - Type cmd
Right click on cmd.exe - select Run as Administrator.
At the Command Prompt window - Type
sfc /scannow
Press Enter.
Let it run to completion - but do not close the cmd window.
To save the log file.
Copy and Paste the following in Command Prompt.
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop
\sfcdetails.txt

Press Enter
On your desktop you will see a text file called sfcdetails.txt
It can take 2-3 runs of system file checker for all files to be repaired or replaced.
======
Check and post the following.
TSG System Information Utility - found here.
http://static.techguy.org/download/SysInfo.exe
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Staff online

Top