Sign in with
Sign up | Sign in
Your question

BSOD while gaming

Last response: in Systems
Share
June 6, 2014 8:31:22 AM

Hi,

I'm getting several BSOD after playing Witcher 2 and WatchDogs (which is a mess TBH).

I'll just copy paste the DUMP file here
Use !analyze -v to get detailed debugging information.

BugCheck 113, {19, 2, 10de, 1184}

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Page 208db7 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiFdoDispatchPnp+7c2ee )

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

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

VIDEO_DXGKRNL_FATAL_ERROR (113)
The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.
Arguments:
Arg1: 0000000000000019, The subtype of the bugcheck:
Arg2: 0000000000000002
Arg3: 00000000000010de
Arg4: 0000000000001184

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

Page 208db7 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details
Page 209200 not present in the dump file. Type ".hh dbgerr004" for details

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x113

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER: from fffff8800463655d to fffff803a405b440

STACK_TEXT:
fffff880`031ae4f8 fffff880`0463655d : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx
fffff880`031ae500 fffff880`045dfdf2 : 00000000`c00000bb fffffa80`0a14d990 00000000`c00000bb fffffa80`0a14d990 : watchdog!WdLogEvent5_WdCriticalError+0xcd
fffff880`031ae540 fffff880`0456388a : fffffa80`0a3c7100 00000000`00000017 fffffa80`0a3c7040 00000000`00000008 : dxgkrnl!DpiFdoDispatchPnp+0x7c2ee
fffff880`031ae590 fffff880`055df526 : fffffa80`0a411000 fffffa80`0a14d990 fffffa80`0a411000 fffffa80`0b5be6b0 : dxgkrnl!DpiDispatchPnp+0x92
fffff880`031ae6a0 fffff803`a43ed90f : fffffa80`0a3c7040 fffff880`055df3ba 00000000`c00000bb 00000000`00000000 : nvlddmkm+0x147526
fffff880`031ae750 fffff803`a4509d15 : 00000000`00000017 fffff880`031ae819 fffffa80`06b137f0 fffffa80`06b11880 : nt!IopSynchronousCall+0xc7
fffff880`031ae7c0 fffff803`a450989a : fffff8a0`0244bba0 00000000`00000080 fffffa80`06b11880 00000000`00000000 : nt!IopRemoveDevice+0xd9
fffff880`031ae880 fffff803`a45097ad : fffffa80`06b137f0 00000000`00000000 fffff8a0`01636d01 fffff8a0`01636d10 : nt!PnpSurpriseRemoveLockedDeviceNode+0xaa
fffff880`031ae8d0 fffff803`a4509714 : 00000000`00000000 00000000`00000000 fffff8a0`01636d10 fffffa80`06b137f0 : nt!PnpDeleteLockedDeviceNode+0x5d
fffff880`031ae910 fffff803`a45084c3 : 00000000`00000000 fffff880`031aea70 fffff8a0`048ce0d0 00000000`00000003 : nt!PnpDeleteLockedDeviceNodes+0x98
fffff880`031ae970 fffff803`a4398345 : fffff880`031aeb88 00000000`00000000 fffff8a0`0a6c9700 fffff8a0`00000000 : nt!PnpProcessQueryRemoveAndEject+0x2c3
fffff880`031aeae0 fffff803`a43fb342 : fffff8a0`0244bba0 00000000`00000000 00000000`00000001 00000046`72b0f200 : nt!PnpProcessTargetDeviceEvent+0x9d
fffff880`031aeb20 fffff803`a4099311 : fffffa80`0beaa600 fffff8a0`048ce0d0 fffff803`a43fb058 fffffa80`0c7066f0 : nt!PnpDeviceEventWorker+0x2ea
fffff880`031aeb80 fffff803`a402dff5 : fffffa80`0c6fa420 00000000`00000080 fffff803`a40991d0 fffffa80`0beaa600 : nt!ExpWorkerThread+0x142
fffff880`031aec10 fffff803`a40e2836 : fffff880`00a7b180 fffffa80`0beaa600 fffff880`00a86f40 fffffa80`06715480 : nt!PspSystemThreadStartup+0x59
fffff880`031aec60 00000000`00000000 : fffff880`031af000 fffff880`031a9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgkrnl!DpiFdoDispatchPnp+7c2ee
fffff880`045dfdf2 4439a7d0010000 cmp dword ptr [rdi+1D0h],r12d

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl!DpiFdoDispatchPnp+7c2ee

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 523a6c87

BUCKET_ID_FUNC_OFFSET: 7c2ee

FAILURE_BUCKET_ID: 0x113_dxgkrnl!DpiFdoDispatchPnp

BUCKET_ID: 0x113_dxgkrnl!DpiFdoDispatchPnp

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x113_dxgkrnl!dpifdodispatchpnp

FAILURE_ID_HASH: {b212c09c-a0e6-382b-f346-e87f97dbdd4f}

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

7: kd> lmvm dxgkrnl
start end module name
fffff880`044cb000 fffff880`04634000 dxgkrnl (pdb symbols) c:\windows\symbol_cache\dxgkrnl.pdb\439183C1793F4DBD825AB075FD546B861\dxgkrnl.pdb
Loaded symbol image file: dxgkrnl.sys
Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
Image name: dxgkrnl.sys
Timestamp: Thu Sep 19 05:16:23 2013 (523A6C87)
CheckSum: 0016E3CB
ImageSize: 00169000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

I have very little notions of PC when it comes to diagnostics.

I know it"s something to do with the DirectX that fails (or so).
I've updated all my drivers (GTX 770) and ran Windows updates (Windows 8).

More about : bsod gaming

June 8, 2014 1:34:58 PM

I reinstalled Windows 8, made the upgrade to 8.1 and still have the BSOD.
I downloaded and bluescreenview and this is the new DUMP:

Dump File : 060814-11937-01.dmp
Crash Time : 08/06/2014 22:16:53
Bug Check String :
Bug Check Code : 0x00000113
Parameter 1 : 00000000`00000019
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`000010de
Parameter 4 : 00000000`00001184
Caused By Driver : watchdog.sys
Caused By Address : watchdog.sys+39ca
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\060814-11937-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 302 264
Dump File Time : 08/06/2014 22:17:38



m
0
l
!