Windows 10: BSOD TDR_VIDEO_FAILURE (0x00000116 ffffe000`6aadd350)

Hi,

Recently after upgrading to Windows 10, my Intel HD 4600 randomly decides to freak out due to the mentioned error.

• The driver is the latest from Intel.
• I have tried numerous other versions (base one from Toshiba from Windows 8, a driver from 2014, and currently the "Windows 10" driver from Intel which all have BSOD'd)
• I switched to Balanced mode for my laptop in case High Performance was causing it for whatever reason (that clearly wasn't it either)

BlueScreenView Info:

Code: The problem seems to be caused by the following file: dxgkrnl.sys Technical Information: *** STOP: 0x00000116 (0xffffe0006aadd350, 0xfffff80191186550, 0x0000000000000000, 0x000000000000000d) *** dxgkrnl.sys - Address 0xfffff8018cff2a8c base at 0xfffff8018ceb0000 DateStamp 0x55bebfed[/quote] This first occurred while I was using Open Broadcaster Source streaming games and the like, which this has never happened before during this either under Windows 8(.1). I'm just so confused as to how to fix this as nothing I've looked at on Google has helped me. I hope you guys can help.

:)

 

How to Analysis the dump,I BsoD tree times In the 6 month

three times Bsod's dump very similarity

My PC

Clevo Gaming notebook

desktop cpu i5-6500，GPU-Nvida 965m， saumsang ddr4 8g，killer netcard 1523

MotherBoard---XMG P7xxDM（-G）

--------------------------------------------------------------------------------------------------

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: ffffe00100c8e004, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffff801497e17dc, address which referenced memory

Debugging Details:

------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPagedPoolEnd

unable to get nt!MmNonPagedPoolStart

unable to get nt!MmSizeOfNonPagedPoolInBytes

ffffe00100c8e004

CURRENT_IRQL: 2

FAULTING_IP:

SynTP+717dc

fffff801`497e17dc 0fb75502 movzx edx,word ptr [rbp+2]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

BAD_PAGES_DETECTED: 12f5b

TRAP_FRAME: fffff800e7381850 -- (.trap 0xfffff800e7381850)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000

rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000

rip=fffff801497e17dc rsp=fffff800e73819e0 rbp=ffffe00100c8e002

r8=fffff801498008f4 r9=0000000000000000 r10=0000000000000011

r11=000000000b6106fd r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na pe nc

SynTP+0x717dc:

fffff801`497e17dc 0fb75502 movzx edx,word ptr [rbp+2] ss:0018:ffffe001`00c8e004=????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800e53595e9 to fffff800e534e9f0

STACK_TEXT:

fffff800`e7381708 fffff800`e53595e9 : 00000000`0000000a ffffe001`00c8e004 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff800`e7381710 fffff800`e5357dc7 : 00000000`00000000 fffff800`e5229ab3 ffffe000`00000000 00001f80`00000201 : nt!KiBugCheckDispatch+0x69

fffff800`e7381850 fffff801`497e17dc : fffff800`e7381a90 00000000`002f9083 fffff800`e73827c8 ffffe000`fb604048 : nt!KiPageFault+0x247

fffff800`e73819e0 fffff800`e7381a90 : 00000000`002f9083 fffff800`e73827c8 ffffe000`fb604048 ffffe000`fb557fc4 : SynTP+0x717dc

fffff800`e73819e8 00000000`002f9083 : fffff800`e73827c8 ffffe000`fb604048 ffffe000`fb557fc4 ffffe000`fb660400 : 0xfffff800`e7381a90

fffff800`e73819f0 fffff800`e73827c8 : ffffe000`fb604048 ffffe000`fb557fc4 ffffe000`fb660400 fffff801`497e1b00 : 0x2f9083

fffff800`e73819f8 ffffe000`fb604048 : ffffe000`fb557fc4 ffffe000`fb660400 fffff801`497e1b00 ffffe000`fb604048 : 0xfffff800`e73827c8

fffff800`e7381a00 ffffe000`fb557fc4 : ffffe000`fb660400 fffff801`497e1b00 ffffe000`fb604048 00000000`00000001 : 0xffffe000`fb604048

fffff800`e7381a08 ffffe000`fb660400 : fffff801`497e1b00 ffffe000`fb604048 00000000`00000001 fffff801`497e1b47 : 0xffffe000`fb557fc4

fffff800`e7381a10 fffff801`497e1b00 : ffffe000`fb604048 00000000`00000001 fffff801`497e1b47 fffff800`e7381a90 : 0xffffe000`fb660400

fffff800`e7381a18 ffffe000`fb604048 : 00000000`00000001 fffff801`497e1b47 fffff800`e7381a90 fffff800`e7381b30 : SynTP+0x71b00

fffff800`e7381a20 00000000`00000001 : fffff801`497e1b47 fffff800`e7381a90 fffff800`e7381b30 00000000`002f9083 : 0xffffe000`fb604048

fffff800`e7381a28 fffff801`497e1b47 : fffff800`e7381a90 fffff800`e7381b30 00000000`002f9083 ffffe000`fb557fd0 : 0x1

fffff800`e7381a30 fffff800`e7381a90 : fffff800`e7381b30 00000000`002f9083 ffffe000`fb557fd0 00000000`00000000 : SynTP+0x71b47

fffff800`e7381a38 fffff800`e7381b30 : 00000000`002f9083 ffffe000`fb557fd0 00000000`00000000 ffffe000`fb557fd0 : 0xfffff800`e7381a90

fffff800`e7381a40 00000000`002f9083 : ffffe000`fb557fd0 00000000`00000000 ffffe000`fb557fd0 ffffe000`fb613828 : 0xfffff800`e7381b30

fffff800`e7381a48 ffffe000`fb557fd0 : 00000000`00000000 ffffe000`fb557fd0 ffffe000`fb613828 fffff801`497c5d98 : 0x2f9083

fffff800`e7381a50 00000000`00000000 : ffffe000`fb557fd0 ffffe000`fb613828 fffff801`497c5d98 00000000`00020000 : 0xffffe000`fb557fd0

STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO

Followup: MachineOwner

---------

what the reason of BsoD?

who can help me. Thank you very much.

***Post moved by the moderator to the appropriate forum category.***

 

Win10 Pro - frequent BSOD - 0x19_20_disk!diskdevicecontrol - Disk.sys

On a new Desktop system with Win10 Pro, a deadly BSOD crash keeps occurring randomly. The crash points to Disk.sys driver by Microsoft. I analysed the crash (see detailed below). It's so bad to see such a crash at such a high rate. Productivity killer!!!

Microsoft - do you have a solution for this?

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

BAD_POOL_HEADER (19)

The pool is already corrupt at the time of the current request.

This may or may not be due to the caller.

The internal pool links must be walked to figure out a possible cause of

the problem, and then special pool applied to the suspect tags or the driver

verifier to a suspect driver.

Arguments:

Arg1: 0000000000000020, a pool block header size is corrupt.

Arg2: ffffe000694e1000, The pool entry we were looking for within the page.

Arg3: ffffe000694e10c0, The next pool entry.

Arg4: 000000000c0c0000, (reserved)

Debugging Details:

------------------

Page 1380 not present in the dump file. Type ".hh dbgerr004" for details

Page 1380 not present in the dump file. Type ".hh dbgerr004" for details

Page 1380 not present in the dump file. Type ".hh dbgerr004" for details

Page 1380 not present in the dump file. Type ".hh dbgerr004" for details

Page 1380 not present in the dump file. Type ".hh dbgerr004" for details

Page 1380 not present in the dump file. Type ".hh dbgerr004" for details

SYSTEM_SKU: 06B9

BIOS_DATE: 01/26/2016

BASEBOARD_PRODUCT: 077RRV

BASEBOARD_VERSION: A00

BUGCHECK_P1: 20

BUGCHECK_P2: ffffe000694e1000

BUGCHECK_P3: ffffe000694e10c0

BUGCHECK_P4: c0c0000

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: ffffe000694e1000 Nonpaged pool

CPU_COUNT: 8

CPU_MHZ: af8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: pcdrrealtime.p

CURRENT_IRQL: 1

ANALYSIS_VERSION: 10.0.10531.520 amd64fre

IRP_ADDRESS: ffffe0006a0ec128

LAST_CONTROL_TRANSFER: from fffff8022eca6de5 to fffff8022ebb7760

STACK_TEXT:

ffffd000`25c70be8 fffff802`2eca6de5 : 00000000`00000019 00000000`00000020 ffffe000`694e1000 ffffe000`694e10c0 : nt!KeBugCheckEx

ffffd000`25c70bf0 fffff802`2eaf04d9 : ffffe000`6a139700 fffff802`2ec83593 fffff802`2ed92180 ffffd000`20206f49 : nt!ExFreePool+0x2c5

ffffd000`25c70cd0 fffff802`2eaeec64 : ffffe000`6a0ec1a0 ffffe000`680e5d28 ffffd000`759d8000 ffffd000`21fff0a0 : nt!IopCompleteRequest+0x79

ffffd000`25c70dc0 fffff802`2ebba953 : 00000000`00000001 ffffe000`763908d0 00000000`00000000 ffffe000`6a0ec1a0 : nt!KiDeliverApc+0x134

ffffd000`25c70e50 fffff800`e2833bb2 : 00000000`00000101 00000000`00000000 00000000`00000000 00000000`00000140 : nt!KiApcInterrupt+0xc3

ffffd000`25c70fe0 fffff800`e283346f : 00000000`00000200 ffffe000`76390900 00000000`00000001 ffffe000`77454103 : storport!RaidStartIoPacket+0x3f2

ffffd000`25c71020 fffff800`e283303a : ffffe000`77454180 ffffe000`694e10a0 ffffe000`6a139400 fffff802`00000096 : storport!RaUnitScsiIrp+0x3ef

ffffd000`25c710c0 fffff800`e2889391 : 00000000`00000103 ffffe000`77454180 ffffe000`763908d0 fffff802`00000096 : storport!RaDriverScsiIrp+0x5a

ffffd000`25c71100 fffff800`e2888cc2 : ffffe000`77add010 fffff800`e286cb0f 00000000`00000000 ffffe000`76af3c60 : storport!PortPassThroughSendAsync+0x1b9

ffffd000`25c711b0 fffff800`e2886e0a : ffffe000`76af3c60 00000000`00000000 00000000`0004d000 ffffe000`6a0ec1a0 : storport!PortPassThroughExSendAsync+0x72

ffffd000`25c71220 fffff800`e2848b7c : ffffe000`76af3c60 00000000`0004d004 ffffe000`6a0ec1a0 00000000`00000005 : storport!RaidAdapterPassThrough+0xa2

ffffd000`25c71270 fffff800`e28344c5 : 00000000`00000000 ffffe000`77add010 ffffe000`76af3c60 fffff800`e2878000 : storport!RaidAdapterDeviceControlIrp+0x142e4

ffffd000`25c712f0 fffff800`e2887e76 : ffffe000`76af3c60 00000000`0004d004 ffffe000`6a0ec1a0 ffffe000`6a139550 : storport!RaDriverDeviceControlIrp+0x95

ffffd000`25c71330 fffff800`e28488d1 : 00000000`00000000 fffff802`2ea89139 ffffe000`76af3c60 ffffe000`6a139550 : storport!RaUnitScsiPassThroughIoctl+0xfa

ffffd000`25c713a0 fffff800`e283448a : ffffe000`767ef080 fffff800`e31842dc 00000000`00000000 fffff800`e2878000 : storport!RaUnitDeviceControlIrp+0x14401

ffffd000`25c71420 fffff800`e3183a6d : 00000000`00000000 ffffd000`25c71560 ffffe000`76af3c60 fffff6fb`7dbed018 : storport!RaDriverDeviceControlIrp+0x5a

ffffd000`25c71460 fffff800`e31616cf : 00000000`00000000 fffff802`2eca5c33 00000000`0004d004 ffffe000`767ef358 : CLASSPNP!ClassDeviceControl+0x52d

ffffd000`25c715d0 fffff800`e3188a73 : 00000000`00000000 00000000`c0000910 ffffe000`6a0931b0 ffffe000`68c89c60 : disk!DiskDeviceControl+0x8f

ffffd000`25c71660 fffff800`e2164925 : ffffe000`76af3c60 ffffe000`68c89c60 00000000`00000001 ffffe000`767ef080 : CLASSPNP!ClassDeviceControlDispatch+0x53

ffffd000`25c71690 fffff800`e2152935 : ffffe000`76af3c00 00000000`00000000 00000000`00000000 ffffe000`76af3c60 : partmgr!PmIoctlRedirect+0x4d

ffffd000`25c71700 fffff802`2ee7fac2 : ffffe000`75dd5090 ffffd000`25c71a80 ffffe000`75dd5090 00000000`00000001 : partmgr!PmFilterDeviceControl+0x2a5

ffffd000`25c71750 fffff802`2ee7e956 : e00076ab`76e0fff5 00000000`001f0003 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x1162

ffffd000`25c71920 fffff802`2ebc1fa3 : 00000000`00000102 00000000`00000001 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56

ffffd000`25c71990 00007ffa`0a6151b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000031`6b5ff968 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`0a6151b4

STACK_COMMAND: kb

FOLLOWUP_IP:

disk!DiskDeviceControl+8f

fffff800`e31616cf 488b4c2450 mov rcx,qword ptr [rsp+50h]

SYMBOL_STACK_INDEX: 11

SYMBOL_NAME: disk!DiskDeviceControl+8f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: disk

IMAGE_NAME: disk.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5632d16e

BUCKET_ID_FUNC_OFFSET: 8f

FAILURE_BUCKET_ID: 0x19_20_disk!DiskDeviceControl

BUCKET_ID: 0x19_20_disk!DiskDeviceControl

PRIMARY_PROBLEM_CLASS: 0x19_20_disk!DiskDeviceControl

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x19_20_disk!diskdevicecontrol

FAILURE_ID_HASH: {d33c16fb-cc5f-e3bb-76ce-3c8db2d9afc0}

Followup: MachineOwner

 

Hello, Turtle. Welcome to the forums. I will try to help you. These errors particularly with a Laptop with switchable graphics are difficult. So, there will be a lot of trial and error to see if we can determine exactly what is happening. You are getting 3 types of errors. The most common one is

Code: BugCheck 116, {ffffe0006aadd350, fffff80191186550, 0, d} Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for igdkmd64.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys Probably caused by : igdkmd64.sys ( igdkmd64+16550 ) A stop code 116 is always a graphics driver/card error. Code: Use !analyze -v to get detailed debugging information. BugCheck 119, {1, 135a45, 135a47, ffffe0015be86010} Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessIsrCompletedPacket+7abb ) Followup: MachineOwner[/quote] Is a Video scheduler Internal error and Code: Use !analyze -v to get detailed debugging information. BugCheck 9F, {4, 12c, ffffe000d3b9a800, ffffd0014c2869b0} Implicit thread is now ffffe000`d3b9a800 Probably caused by : BTHUSB.sys Followup: MachineOwner[/quote] Is a Driver power state Failure. BTHUSB is the Bluetooth miniport Driver. Followup: MachineOwner[/quote] If you would please remove any Bluetooth devices and see if that is where some of your problems are coming from.

Next please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow . If you decide to type it in, please notice the space between the sfc and the /. We want it to say no integrity violations were found. If it says there where corrupt files that could not be repaired, please reboot and run it again. You may have to run it 3 times with reboots in between each time.

 

I will try disconnecting my bluetooth mouse when I get home but I've also already run sfc /scannow and it returned no integrity violations.

 

Ok, in the same elevated command prompt, please see if you can run this command. Dism /Online /Cleanup-Image /RestoreHealth It can take from 20 minutes to a couple of hours, depending on your machine and what it finds. It will start at 20% and act like it is stuck for a while. Just let it run. It will complete or give you an error message. For some strange reason, not everyone can run it.

 

Essenbe,

I ran the above prompt in admin and got an all-clear complete.

Attachment 34422

 

Good job. Not everyone can successfully run that. How often do you get a BSOD? Do you want to wait and see if that fixed the problem or would you like to try something different?

 

Essenbe,

I get this BSOD randomly. I have no control as to when it occurs. The last one was watching my friend on Twitch playing some games. The ones around the weekend of August 21st were while I streamed game development. If you would like to try something just in case that didn't affect anything, we could. If you could also explain what that command I performed does, that would be great.

 

What you did was basically a more in depth sfc /scannow. As I understand it, the command scans your system files against the ISO of the system and is supposed to repair/replace any missing/damaged/corrupted system files. It has helped me a couple of times.

The problem we have with Laptops with switchable graphics is usually, they do not switch in time so the system assumes a graphics failure and crashes. We have only found one solution which will, in most cases, solve it. It is not a very desirable solution. So, I was trying to make sure there were no corrupted system files, causing it. The next thing is to check drivers using Driver Verifier. There is the possibility that a clean install would be necessary, if it does not go right. I feel obligated to tell you that. However, we take every precaution to see to it that does not happen and it has never happened to me. What Driver Verifier does is put stress on all 3rd party drivers in order to make them crash, in hopes that the dump file will catch the offending driver. If you decide you want to do that, please let me know and I will give you some instructions on exactly how to do it and what to do beforehand in case it does not go as planned. If you have any questions, please feel free to ask.

 

Essenbe,

I have heard of the Driver Verification tool and I suppose it would work. In regards to the bluetooth driver, I think that one's from station-drivers.com and is probably 3rd party. I've tried finding the first party driver with no luck which means I'm stuck on the base Windows 8 driver. I also have thought of doing a clean Windows 10 install but if you feel Driver Verifier would be a better idea to try first, I'm all in. I'll be back around 11:30pm EST to read your reply.

 

*YouTube video player

 

It seems that after doing the command, not driver verifier, has fixed the issue. I've not had any problems since running that. Thanks!

 

You are more than welcome. I hope your problem is resolved. If you haven't already, be sure to disable Driver Verifier. If you have any further problems, please come back.

 

Well, after a recent BSOD with this error, I am currently running Driver Verifier. A few questions:

1) Will using dual monitors (laptop display + VGA monitor) cause this error?
2) I am going to try to force the BSOD further by watching people on twitch since that's when it commonly occurs.