Share via

BSOD

Anonymous
2018-03-09T13:34:18+00:00

Hello Community:

Dell Precision 7510

32 GB RAM

Win 7 SP1

--Fully Patched-- To the best of my knowledge

I have been constantly having a BSOD and my search's on the web have not really pointed to anything. I am almost thinking it's an Nvidia problem. Here is the DUMP output as well as the initial error:

Error:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000001 (0x000000007783991a, 0x0000000000000000, 0x000000000000ffff, 0xfffff8800de38b60). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 030918-12027-01.

Second Error:

I am also running a chkdsk for the following as well and not sure if this is in relation:

The description for Event ID 0 from source aksfridge cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

error file fchkdsk.c line 1535 status 0

Debug:

Microsoft (R) Windows Debugger Version 10.0.17074.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\chill\Desktop\030818-11544-02.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.24024.amd64fre.win7sp1_ldr.180112-0600
Machine Name:
Kernel base = 0xfffff800`0320b000 PsLoadedModuleList = 0xfffff800`0344aa90
Debug session time: Thu Mar  8 15:35:20.146 2018 (UTC - 5:00)
System Uptime: 0 days 4:45:26.301
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {7783991a, 0, ffff, fffff88024c5cb60}

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

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

nt!KeBugCheckEx:
fffff800`032b12a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff880`24c5c930=0000000000000001
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: 000000007783991a, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff88024c5cb60, 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.24024.amd64fre.win7sp1_ldr.180112-0600

SYSTEM_MANUFACTURER:  Dell Inc.

SYSTEM_PRODUCT_NAME:  Precision 7510

SYSTEM_SKU:  06D9

BIOS_VENDOR:  Dell Inc.

BIOS_VERSION:  1.15.4

BIOS_DATE:  12/08/2017

BASEBOARD_MANUFACTURER:  Dell Inc.

BASEBOARD_PRODUCT:  0M91XC

BASEBOARD_VERSION:  A00

DUMP_TYPE:  2

BUGCHECK_P1: 7783991a

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: fffff88024c5cb60

FAULTING_IP: 
+0
00000000`7783991a ??              ???

CPU_COUNT: 4

CPU_MHZ: a98

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: C2'00000000 (cache) C2'00000000 (init)

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x1

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  AX-LT08

ANALYSIS_SESSION_TIME:  03-09-2018 08:19:56.0929

ANALYSIS_VERSION: 10.0.17074.1002 amd64fre

LAST_CONTROL_TRANSFER:  from fffff800032c1529 to fffff800032b12a0

STACK_TEXT:  
fffff880`24c5c928 fffff800`032c1529 : 00000000`00000001 00000000`7783991a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`24c5c930 fffff800`032c1435 : fffffa80`27fa2b50 00000000`01fee0d8 fffff880`24c5ca88 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`24c5ca70 00000000`7783991a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x2aa
00000000`01fee0a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7783991a

THREAD_SHA1_HASH_MOD_FUNC:  713a38487ff3d82058f51d9870e0b3de39cbf964

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  8a4816d71fc5737e3871923fa5e27863b4ba4379

THREAD_SHA1_HASH_MOD:  2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

FOLLOWUP_IP: 
nt!KiSystemServiceExit+2aa
fffff800`032c1435 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:  5a58dc54

IMAGE_VERSION:  6.1.7601.24024

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-03-08T20:35:20.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-01-12 11:03:32

BUILDDATESTAMP_STR:  180112-0600

BUILDLAB_STR:  win7sp1_ldr

BUILDOSVER_STR:  6.1.7601.24024.amd64fre.win7sp1_ldr.180112-0600

ANALYSIS_SESSION_ELAPSED_TIME:  365

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
---------
Windows for home | Previous Windows versions | Devices and drivers

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 No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2018-03-09T14:38:07+00:00

    Not sure if its the realtek, intel, or nvidia audio.

    All have the latest version per Dell's site.

    Was this answer helpful?

    0 comments No comments