Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs

User Tag List

dxgkrnl.sys BSOD

This is a discussion on dxgkrnl.sys BSOD within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category. I have a National Instruments PXI 8108 and receiving a dxkrnl.sys BSOD periodically. I have attached the dump files here:


Closed Thread
 
Thread Tools Search this Thread
Old 12-24-2014, 09:48 AM   #1
Registered Member
 
Join Date: Dec 2014
Posts: 2
OS: Windows 7



I have a National Instruments PXI 8108 and receiving a dxkrnl.sys BSOD periodically. I have attached the dump files here:

https://provincialaerospace.sharefil...1b13462b3479cb

and the System NFO and driver section here:

https://provincialaerospace.sharefil...ca3c25f4140269

and bug analysis below

Code:
Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\AMD\121814-6531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\Vistasymbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\Vistasymbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0x8343a000 PsLoadedModuleList = 0x8357a310
Debug session time: Thu Dec 18 12:34:40.332 2014 (UTC - 3:30)
System Uptime: 0 days 0:12:16.003
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000047, 834a70ee, b14f38b8, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkGetPresentHistory+4b9 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000047, The exception code that was not handled
Arg2: 834a70ee, The address that the exception occurred at
Arg3: b14f38b8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

FAULTING_IP: 
nt!KeReleaseSemaphore+a7
834a70ee cc              int     3

TRAP_FRAME:  b14f38b8 -- (.trap 0xffffffffb14f38b8)
ESP EDITED! New esp=b14f3c68
ErrCode = 00000000
eax=00000000 ebx=8355cd20 ecx=85e7ef00 edx=00000000 esi=85e7efb0 edi=000007ff
eip=834a70ee esp=b14f392c ebp=b14f3c78 iopl=0         nv up ei pl zr na pe nc
cs=0000  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000246
nt!KeReleaseSemaphore+0xa7:
834a70ee cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from 945596bf to 834a70ee

STACK_TEXT:  
b14f3c78 945596bf 85e7efb0 00000000 00000001 nt!KeReleaseSemaphore+0xa7
b14f3d18 9719a1f1 007df9fc 00000001 b14f3d34 dxgkrnl!DxgkGetPresentHistory+0x4b9
b14f3d28 8346f856 007df9fc 007dfa10 77b670f4 win32k!NtGdiDdDDIGetPresentHistory+0x15
b14f3d28 77b670f4 007df9fc 007dfa10 77b670f4 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
007dfa10 00000000 00000000 00000000 00000000 0x77b670f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DxgkGetPresentHistory+4b9
945596bf 8d4d9c          lea     ecx,[ebp-64h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!DxgkGetPresentHistory+4b9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e3dcf

IMAGE_VERSION:  6.1.7601.18510

FAILURE_BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x8e_dxgkrnl!dxgkgetpresenthistory+4b9

FAILURE_ID_HASH:  {5c3027d9-1203-6604-4823-6f485530c0a5}

Followup: MachineOwner
---------
Code:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000047, The exception code that was not handled
Arg2: 834a70ee, The address that the exception occurred at
Arg3: b14f38b8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

FAULTING_IP: 
nt!KeReleaseSemaphore+a7
834a70ee cc              int     3

TRAP_FRAME:  b14f38b8 -- (.trap 0xffffffffb14f38b8)
ESP EDITED! New esp=b14f3c68
ErrCode = 00000000
eax=00000000 ebx=8355cd20 ecx=85e7ef00 edx=00000000 esi=85e7efb0 edi=000007ff
eip=834a70ee esp=b14f392c ebp=b14f3c78 iopl=0         nv up ei pl zr na pe nc
cs=0000  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000246
nt!KeReleaseSemaphore+0xa7:
834a70ee cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from 945596bf to 834a70ee

STACK_TEXT:  
b14f3c78 945596bf 85e7efb0 00000000 00000001 nt!KeReleaseSemaphore+0xa7
b14f3d18 9719a1f1 007df9fc 00000001 b14f3d34 dxgkrnl!DxgkGetPresentHistory+0x4b9
b14f3d28 8346f856 007df9fc 007dfa10 77b670f4 win32k!NtGdiDdDDIGetPresentHistory+0x15
b14f3d28 77b670f4 007df9fc 007dfa10 77b670f4 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
007dfa10 00000000 00000000 00000000 00000000 0x77b670f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DxgkGetPresentHistory+4b9
945596bf 8d4d9c          lea     ecx,[ebp-64h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!DxgkGetPresentHistory+4b9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e3dcf

IMAGE_VERSION:  6.1.7601.18510

FAILURE_BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x8e_dxgkrnl!dxgkgetpresenthistory+4b9

FAILURE_ID_HASH:  {5c3027d9-1203-6604-4823-6f485530c0a5}

Followup: MachineOwner
---------
Code:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000047, The exception code that was not handled
Arg2: 834a70ee, The address that the exception occurred at
Arg3: b14f38b8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

FAULTING_IP: 
nt!KeReleaseSemaphore+a7
834a70ee cc              int     3

TRAP_FRAME:  b14f38b8 -- (.trap 0xffffffffb14f38b8)
ESP EDITED! New esp=b14f3c68
ErrCode = 00000000
eax=00000000 ebx=8355cd20 ecx=85e7ef00 edx=00000000 esi=85e7efb0 edi=000007ff
eip=834a70ee esp=b14f392c ebp=b14f3c78 iopl=0         nv up ei pl zr na pe nc
cs=0000  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000246
nt!KeReleaseSemaphore+0xa7:
834a70ee cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from 945596bf to 834a70ee

STACK_TEXT:  
b14f3c78 945596bf 85e7efb0 00000000 00000001 nt!KeReleaseSemaphore+0xa7
b14f3d18 9719a1f1 007df9fc 00000001 b14f3d34 dxgkrnl!DxgkGetPresentHistory+0x4b9
b14f3d28 8346f856 007df9fc 007dfa10 77b670f4 win32k!NtGdiDdDDIGetPresentHistory+0x15
b14f3d28 77b670f4 007df9fc 007dfa10 77b670f4 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
007dfa10 00000000 00000000 00000000 00000000 0x77b670f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DxgkGetPresentHistory+4b9
945596bf 8d4d9c          lea     ecx,[ebp-64h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!DxgkGetPresentHistory+4b9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e3dcf

IMAGE_VERSION:  6.1.7601.18510

FAILURE_BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x8e_dxgkrnl!dxgkgetpresenthistory+4b9

FAILURE_ID_HASH:  {5c3027d9-1203-6604-4823-6f485530c0a5}

Followup: MachineOwner
---------
Code:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000047, The exception code that was not handled
Arg2: 834a70ee, The address that the exception occurred at
Arg3: b14f38b8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

FAULTING_IP: 
nt!KeReleaseSemaphore+a7
834a70ee cc              int     3

TRAP_FRAME:  b14f38b8 -- (.trap 0xffffffffb14f38b8)
ESP EDITED! New esp=b14f3c68
ErrCode = 00000000
eax=00000000 ebx=8355cd20 ecx=85e7ef00 edx=00000000 esi=85e7efb0 edi=000007ff
eip=834a70ee esp=b14f392c ebp=b14f3c78 iopl=0         nv up ei pl zr na pe nc
cs=0000  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000246
nt!KeReleaseSemaphore+0xa7:
834a70ee cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from 945596bf to 834a70ee

STACK_TEXT:  
b14f3c78 945596bf 85e7efb0 00000000 00000001 nt!KeReleaseSemaphore+0xa7
b14f3d18 9719a1f1 007df9fc 00000001 b14f3d34 dxgkrnl!DxgkGetPresentHistory+0x4b9
b14f3d28 8346f856 007df9fc 007dfa10 77b670f4 win32k!NtGdiDdDDIGetPresentHistory+0x15
b14f3d28 77b670f4 007df9fc 007dfa10 77b670f4 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
007dfa10 00000000 00000000 00000000 00000000 0x77b670f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DxgkGetPresentHistory+4b9
945596bf 8d4d9c          lea     ecx,[ebp-64h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!DxgkGetPresentHistory+4b9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e3dcf

IMAGE_VERSION:  6.1.7601.18510

FAILURE_BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x8e_dxgkrnl!dxgkgetpresenthistory+4b9

FAILURE_ID_HASH:  {5c3027d9-1203-6604-4823-6f485530c0a5}

Followup: MachineOwner
---------
Code:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000047, The exception code that was not handled
Arg2: 834a70ee, The address that the exception occurred at
Arg3: b14f38b8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

FAULTING_IP: 
nt!KeReleaseSemaphore+a7
834a70ee cc              int     3

TRAP_FRAME:  b14f38b8 -- (.trap 0xffffffffb14f38b8)
ESP EDITED! New esp=b14f3c68
ErrCode = 00000000
eax=00000000 ebx=8355cd20 ecx=85e7ef00 edx=00000000 esi=85e7efb0 edi=000007ff
eip=834a70ee esp=b14f392c ebp=b14f3c78 iopl=0         nv up ei pl zr na pe nc
cs=0000  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000246
nt!KeReleaseSemaphore+0xa7:
834a70ee cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from 945596bf to 834a70ee

STACK_TEXT:  
b14f3c78 945596bf 85e7efb0 00000000 00000001 nt!KeReleaseSemaphore+0xa7
b14f3d18 9719a1f1 007df9fc 00000001 b14f3d34 dxgkrnl!DxgkGetPresentHistory+0x4b9
b14f3d28 8346f856 007df9fc 007dfa10 77b670f4 win32k!NtGdiDdDDIGetPresentHistory+0x15
b14f3d28 77b670f4 007df9fc 007dfa10 77b670f4 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
007dfa10 00000000 00000000 00000000 00000000 0x77b670f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DxgkGetPresentHistory+4b9
945596bf 8d4d9c          lea     ecx,[ebp-64h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!DxgkGetPresentHistory+4b9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e3dcf

IMAGE_VERSION:  6.1.7601.18510

FAILURE_BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x8e_dxgkrnl!dxgkgetpresenthistory+4b9

FAILURE_ID_HASH:  {5c3027d9-1203-6604-4823-6f485530c0a5}

Followup: MachineOwner
---------
Code:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000047, The exception code that was not handled
Arg2: 834a70ee, The address that the exception occurred at
Arg3: b14f38b8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

FAULTING_IP: 
nt!KeReleaseSemaphore+a7
834a70ee cc              int     3

TRAP_FRAME:  b14f38b8 -- (.trap 0xffffffffb14f38b8)
ESP EDITED! New esp=b14f3c68
ErrCode = 00000000
eax=00000000 ebx=8355cd20 ecx=85e7ef00 edx=00000000 esi=85e7efb0 edi=000007ff
eip=834a70ee esp=b14f392c ebp=b14f3c78 iopl=0         nv up ei pl zr na pe nc
cs=0000  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000246
nt!KeReleaseSemaphore+0xa7:
834a70ee cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from 945596bf to 834a70ee

STACK_TEXT:  
b14f3c78 945596bf 85e7efb0 00000000 00000001 nt!KeReleaseSemaphore+0xa7
b14f3d18 9719a1f1 007df9fc 00000001 b14f3d34 dxgkrnl!DxgkGetPresentHistory+0x4b9
b14f3d28 8346f856 007df9fc 007dfa10 77b670f4 win32k!NtGdiDdDDIGetPresentHistory+0x15
b14f3d28 77b670f4 007df9fc 007dfa10 77b670f4 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
007dfa10 00000000 00000000 00000000 00000000 0x77b670f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DxgkGetPresentHistory+4b9
945596bf 8d4d9c          lea     ecx,[ebp-64h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!DxgkGetPresentHistory+4b9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e3dcf

IMAGE_VERSION:  6.1.7601.18510

FAILURE_BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x8e_dxgkrnl!dxgkgetpresenthistory+4b9

FAILURE_ID_HASH:  {5c3027d9-1203-6604-4823-6f485530c0a5}

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

0: kd>
Code:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000047, The exception code that was not handled
Arg2: 834a70ee, The address that the exception occurred at
Arg3: b14f38b8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

FAULTING_IP: 
nt!KeReleaseSemaphore+a7
834a70ee cc              int     3

TRAP_FRAME:  b14f38b8 -- (.trap 0xffffffffb14f38b8)
ESP EDITED! New esp=b14f3c68
ErrCode = 00000000
eax=00000000 ebx=8355cd20 ecx=85e7ef00 edx=00000000 esi=85e7efb0 edi=000007ff
eip=834a70ee esp=b14f392c ebp=b14f3c78 iopl=0         nv up ei pl zr na pe nc
cs=0000  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000246
nt!KeReleaseSemaphore+0xa7:
834a70ee cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from 945596bf to 834a70ee

STACK_TEXT:  
b14f3c78 945596bf 85e7efb0 00000000 00000001 nt!KeReleaseSemaphore+0xa7
b14f3d18 9719a1f1 007df9fc 00000001 b14f3d34 dxgkrnl!DxgkGetPresentHistory+0x4b9
b14f3d28 8346f856 007df9fc 007dfa10 77b670f4 win32k!NtGdiDdDDIGetPresentHistory+0x15
b14f3d28 77b670f4 007df9fc 007dfa10 77b670f4 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
007dfa10 00000000 00000000 00000000 00000000 0x77b670f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DxgkGetPresentHistory+4b9
945596bf 8d4d9c          lea     ecx,[ebp-64h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!DxgkGetPresentHistory+4b9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e3dcf

IMAGE_VERSION:  6.1.7601.18510

FAILURE_BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

BUCKET_ID:  0x8E_dxgkrnl!DxgkGetPresentHistory+4b9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x8e_dxgkrnl!dxgkgetpresenthistory+4b9

FAILURE_ID_HASH:  {5c3027d9-1203-6604-4823-6f485530c0a5}

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

0: kd> lmvm dxgkrnl
start    end        module name
9453d000 945f5000   dxgkrnl    (pdb symbols)          c:\vistasymbols\dxgkrnl.pdb\07257BE14A5C462F879DD0FE9EDCA16F2\dxgkrnl.pdb
    Loaded symbol image file: dxgkrnl.sys
    Mapped memory image file: c:\vistasymbols\dxgkrnl.sys\539E3DCFb8000\dxgkrnl.sys
    Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
    Image name: dxgkrnl.sys
    Timestamp:        Sun Jun 15 22:13:59 2014 (539E3DCF)
    CheckSum:         000BBCF4
    ImageSize:        000B8000
    File version:     6.1.7601.18510
    Product version:  6.1.7601.18510
    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:     dxgkrnl.sys
    OriginalFilename: dxgkrnl.sys
    ProductVersion:   6.1.7601.18510
    FileVersion:      6.1.7601.18510 (win7sp1_gdr.140615-1511)
    FileDescription:  DirectX Graphics Kernel
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
0: kd> .trap 0xffffffffb14f38b8
ESP EDITED! New esp=b14f3c68
ErrCode = 00000000
eax=00000000 ebx=8355cd20 ecx=85e7ef00 edx=00000000 esi=85e7efb0 edi=000007ff
eip=834a70ee esp=b14f392c ebp=b14f3c78 iopl=0         nv up ei pl zr na pe nc
cs=0000  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000246
nt!KeReleaseSemaphore+0xa7:
834a70ee cc              int     3
jeffn12 is offline  
Sponsored Links
Advertisement
 
Old 12-24-2014, 11:13 AM   #2
Microsoft MVP
Microsoft Team Moderator
Articles Team Manager
Hardware Team Moderator
 
Masterchiefxx17's Avatar
 
Join Date: Feb 2010
Location: Wisconsin, USA
Posts: 39,491
OS: Windows 10 Professional 64bit

My System


I've moved your post to the correct BSOD forum. To get started follow this guide here:

Please read all of the following instructions found here: https://www.techsupportforum.com/foru...ta-452654.html
Masterchiefxx17 is offline  
Old 12-25-2014, 03:19 AM   #3
Registered Member
 
Join Date: Dec 2014
Posts: 2
OS: Windows 7



Thank you
jeffn12 is offline  
Sponsored Links
Advertisement
 
Old 12-27-2014, 03:41 PM   #4
Administrator
Manager, Microsoft Support
Acting Manager, Security
BSOD Kernel Dump Expert
Microsoft Windows Insider MVP
 
jcgriff2's Avatar
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 34,339
OS: Windows 10, 8.1 + Windbg :)



Hi -

All of the dumps have a 0xc47 exception error code in common.
Quote:
EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore
such that its maximum count would have been exceeded.
This has to do with drivers keeping track of access and very well could indicate a rogue driver is at fault.

See if Driver Verifier flags any 3rd party drivers -

https://www.techsupportforum.com/foru...ed-473665.html

Let Driver Verifier run for at least 24 hours in the background.

If a BSOD occurs while Driver Verifier is running, go to \windows\minidump, copy out the most recent dump to Documents or Desktop, zip it up and attach to your next post.

Please be sure to follow instructions by Masterchiefxx17.

Regards. . .

jcgriff2

`
jcgriff2 is offline  
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
0x116 BSOD: dxgkrnl.sys
So I've been getting random BSODs that seem to be coming from my GPU. These often begin with hangs/artifacts in games and then the system will crash and code 43 the GPU, which will then consistently crash upon use. Problem is, this is a brand new GPU that I am 99.9% sure is not...
JG1020 BSOD, App Crashes And Hangs 2 02-08-2014 10:27 PM
BSOD: dxgkrnl.sys when trying to play games.
hello i have nvidia geforece gt540m i get bluescreens when i use the video card for playing games if i used integrated graphic no blue screen blue screen viewer display this as red. i also already got the latest drivers unnistalled and rebooted and let windows install it self did not work...
dishonored BSOD, App Crashes And Hangs 7 01-10-2014 11:16 AM
BSOD Due to dxgkrnl.sys
Hi All, when I play Napoleon total war and some other games after 5 minutes my pc crashed...Please help me....This is the file...TY
Saviljas BSOD, App Crashes And Hangs 6 01-19-2013 08:12 AM
[SOLVED] Bsod dxgkrnl.sys
Hello, i post today because i have some bsod since 2 weeks then my pc have been buy from 1 month. Bsod often appear while i stop pc with dxgkrnl.sys and page fault on non paged area ... Can you help to resolve ? in attachment dump et perfmon log ps: sry for my bad english i am a frenchie...
emileletueur BSOD, App Crashes And Hangs 2 03-04-2012 01:53 AM
BSOD Problems, IQRL_Not_Less_Or_Equal; PFN_List_Corrupt; Ntfs.sys etc.
Over the past 2 months I've been having problems with BSOD's. First I tought it was just a one time thing but after five times I started to think different. I used Ccleaner and Comodo cleaner to clean up the registry but nothing helped. The one thing I did noticed was that the BSOD's were different...
Pytrik BSOD, App Crashes And Hangs 9 02-28-2011 04:41 AM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Post a Question


» Site Navigation
 > FAQ
  > 10.0.0.2
Powered by vBadvanced CMPS v3.2.3


All times are GMT -7. The time now is 10:21 PM.


Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.1.0 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
Copyright 2001 - 2018, Tech Support Forum

Windows 10 - Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts