BSOD (DRIVER_IRQL_NOT_LESS_OR_EQUAL igdkmd64.sys)

Hi, I am currently facing the problem of BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL igdkmd64.sys on my laptop (HP ENVY 15-j126tx)
OS: Windows 8.1
Intel HD Graphics 4600 with driver version 10.18.10.3277
I have try updating the driver but the problem don't seem to be solve. I had also try rollback the driver but after rollback I was unable to adjust my screen resolution and brightness (I not sure it still get BSOD anot).
What should I do to solve this problem?
I hope it was able to solve this problem with the screen resolution and brightness able to adjust.
Thank you.
This question was solved.
View Solution.

I have try to update the driver but the problem didn't solve yet, and also try getting old version driver. After I install old driver, most of my program stop working. I really need help in solving this problem.

Similar Messages

VIDEO_TDR_FAILURE (igdkmd64.sys) crashing my NEW laptop and BSOD while gaming Windows 10

Recently I bought a new laptop, Lenovo Y50, and had no issues with it. I started playing a game called "Path of Exile" and while in the middle of the game it would freeze and then cause my laptop to crash into BSOD and give me the error message VIDEO_TDR_FAILURE (igdkmd64.sys) which looked like this:
Link to image
https://communities.intel.com/servlet/JiveServlet/showImage/2-255820-239358/bsod2.jpg
I have searched through for assistance but found no resolution in the attempts I made. The most recent attempt was uninstalling the Intel Driver but that just lowered my FPS entirely. So I reinstalled and the problem came up again and then I foolishly shut my laptop off before it hit the BSOD and when I booted it back up then screen was all black and not changing. Scared of ruining my new computer, I hard shut down the laptop once again and then it booted up normally, only that it was much slower. Have I damaged my laptop? If so, what steps do I need to take? And yes, I have insurance.
Specs:
Processor 4th Generation Intel Core i7-4720HQ Processor (2.60GHz 1600MHz 6MB)
Operating system Windows 8.1 64 originally but updated to windows 10
Display 15.6" FHD IPS LED Backlight (1920x1080)
Graphics NVIDIA GeForce GTX 860M 4GB
Memory 16.0GB PC3-12800 DDR3L SDRAM 1600 MHz
Hard Drive Hybrid 1TB 5400 RPM+8GB SSHD
Network Card Intel® Dual Band Wireless-AC 3160
I have posted for assistance on the following websites: Microsoft, Lenovo, Intel, and Yahoo. Thank you for your assistance.
Moderator note: large image(s) converted to link(s): About Posting Pictures In The Forums

I have the same issue with my Y50 laptop after updating to windows 10. For me there is one more problem in the chrome browser: image shaking on videos and gifs..I also tried to clean install windows 10, remove and reinstall drivers for intel and nvidia with no result.Maybe intell will update the drivers soon...

T61 Windows 7 64bit BSOD igdkmd64.sys with 965 when on batteries

As long as I'm plugged in, I don't get the BSOD.
Most of the time, when I'm running on batteries, and waking up from sleep, I get the BSOD with the igdkmd64.sys.
I have a Lenovo T61, Windows 7 64 bit, 4GB ram,
device manager says I have: Intel 965 Express chipset for the display.
I just recently installed windows7 64 bit on a new hard drive.
The drivers I have installed are: 15.12.75.4.64.1930 (or 8.15.10.1930 from device manager)

Hi, lumangoy
I did some research on the issue and found this forum from Microsoft. The consensus on the forum is that it is a driver issue. I looked at the driver matrix on Lenovo Support and found a newer version of the chipset driver than what you specified in your post. Your current verison is 8.15.10.1930 and the latest from Lenovo's site is 9.3.0.1021. So I would try updating to that first, and that can be found here. Upon getting to this page, select the approriate operating system and driver category from the dropdown menus to filter the search results.
Another suggestion from a moderator on the Microsoft forum is to use Intel's site to make sure the drivers are up to date. The link provided in the forum can be found here. This will take you to a site where Intel will scan the hardware of the computer and make sure that the latest drivers are installed.
Good luck, and let me know how it goes,
Adam
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution!" This will help the rest of the community with similar issues identify the verified solution and benefit from it.

Lenovo thinkpad W540 BSOD igdkmd64.sys

Hi,
several times a day the system has a blue screen igdkmd64.sys for intel graphics driver , I could not update the driver for intel updater gives me error, I tried to find if lenovo have any update for this driver and I find nothing.
please help, and sorry for my bad English.

Download the latest Intel driver. The latest available one can be found here:
http://www.station-drivers.com/index.php/downloads/Drivers/Intel/HD--and--Iris-Graphics/Serie-15.36....
Unpack this somewhere.
Force the driver install using Device Manager:
1. Device Manager
2. Right-click the Intel graphics card, update driver.
3. Browse my computer for driver software
4. Let me pick from a list of device drivers on my computer
5. Have Disk
6. Point this at the Graphics folder inside where you unpacked the above file.
7. You should see the list populate with the name of your graphics card.
8. Continue the driver install.
This bypasses the "computer does not meet requirements" issue the setup file usually complains about.
Note: Your brightness levels might change with this driver compared to the Lenovo driver.
W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

Yoga 13 Graphics driver problem -BSOD

I am having a problem getting this frequent "graphic driver stopped responding..." message and a "video_scheduler.." BSOD after that. Something like this:
Steps I did:
Did OKR. Clean driver. Lenovo driver. Windows update intel Driver. Latest Intel HD 4000 from their site. The BIOS version is upto date but I reinstalled again.NO luck. .I tried both Win 8 and 8.1 here. .. I tried all these possibilities..
Did clean windows install from a non-lenovo windows 8 image. Wiped SSD. Windows was fresh, clean and no bloatware. No Luck. Updatet to 8.1 .. did all possibilities again.. no luck.
I called Lenovo Tech. They remote to the laptop and what he did is uninstall all graphics driver and use windows generic driver. He stopped auto windows update (since windows updates the driver). There's no error, but the laptop performance is horribly slow. Scrolling long PDF and websites is wavy and the HDMI port is useless.
Lenovos solution is unacceptable. The laptop is bassically useless.
Are you guys experiencing the same thing too? Do you guys know a solution. I really like the laptop but it is unusable.
BTW, I bought this laptop ~3 weeks as scratch and dent at their lenovo website. I wonder if there is a hardware problem for this.
Also, the wifi sucks.. sigh

Here's the analysis:
System Information (local)
computer name: JCXLENOVO
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: 20175, LENOVO, INVALID
CPU: GenuineIntel Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4171603968 total
VM: 2147352576, free: 1873526784
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 3/20/2014 4:55:37 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031914-6000-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
Bugcheck code: 0x119 (0x1, 0x0, 0xA60, 0xFFFFE000023D7010)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 3/20/2014 4:55:37 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64!hybDriverEntry+0xB861A)
Bugcheck code: 0x119 (0x1, 0x0, 0xA60, 0xFFFFE000023D7010)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\igdkmd64.sys
product: Intel HD Graphics Drivers for Windows 8(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation VIDEO_SCHEDULER_INTERNAL_ERROR
On Thu 3/20/2014 4:51:59 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031914-5593-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
Bugcheck code: 0x119 (0x1, 0x0, 0x45F5, 0xFFFFE000023043C0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 3/19/2014 4:46:45 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031814-3859-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
Bugcheck code: 0x119 (0x1, 0x0, 0x1A4F, 0xFFFFE00000225010)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 3/19/2014 4:36:24 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031814-4218-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
Bugcheck code: 0x119 (0x1, 0x0, 0x2BCA, 0xFFFFE000023F5010)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 3/19/2014 4:28:45 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031814-3921-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
Bugcheck code: 0x119 (0x1, 0x0, 0x1D35, 0xFFFFE00002255540)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 3/19/2014 3:25:52 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031814-4234-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
Bugcheck code: 0x119 (0x1, 0x0, 0x1A96, 0xFFFFE00002380010)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 3/18/2014 7:00:40 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031814-4046-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
Bugcheck code: 0x119 (0x1, 0x2E17, 0x29E, 0xFFFFE00000255010)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 3/6/2014 9:07:27 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030614-3906-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x39CA)
Bugcheck code: 0x119 (0x1, 0x0, 0x2B6B, 0xFFFFE00001C90010)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 3/6/2014 7:21:39 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030514-8468-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF8001F9D9CA0)
Bugcheck code: 0x119 (0x1, 0x0, 0x448, 0xFFFFE00001C2D2A0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
Bug check description: This indicates that the video scheduler has detected a fatal violation.
A third party driver was identified as the probable root cause of this system error.
Google query: VIDEO_SCHEDULER_INTERNAL_ERROR
Conclusion
16 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

Win 8.1 Encountering PFN_List_Corrupt BSOD while shutting down

Hi there, starting last month my computer began experiencing PFN_List_Corrupt BSODs occasionally while shutting down. I am running Win 8.1. I tried memory search but the system says no error was found. Could someone help me with this? The DMP Files are here: http://1drv.ms/1A7pv3k
Thanks!

Hi,
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {9a, 218e0c, 6, 2}
*** 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+1c992 )
Followup: MachineOwner
4: kd> !analyze -v
* Bugcheck Analysis *
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000009a,
Arg2: 0000000000218e0c
Arg3: 0000000000000006
Arg4: 0000000000000002
Debugging Details:
BUGCHECK_STR: 0x4E_9a
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff80333a17527 to fffff8033396a1a0
STACK_TEXT:
ffffd000`b29a5548 fffff803`33a17527 : 00000000`0000004e 00000000`0000009a 00000000`00218e0c
00000000`00000006 : nt!KeBugCheckEx
ffffd000`b29a5550 fffff803`338691b2 : 00000002`146d2863 00000000`00000020 fffff6f0`00e56998
00000000`00002000 : nt!MiBadRefCount+0x4f
ffffd000`b29a5590 fffff803`33868ea1 : 00000000`00000000 00000000`00000001 00000000`00000010
00000000`00000001 : nt!MiInsertNonPagedPoolOnSlist+0x2e2
ffffd000`b29a55f0 fffff803`33abb3d7 : 00000000`00000000 ffffc000`c13de510 ffffc000`c22e14d0
fffff800`6d4d6956 : nt!MiFreePoolPages+0x5d
ffffd000`b29a5620 fffff803`33abbd0f : ffffe001`c9c61010 ffffe001`ce7027c0 00000000`00000000
00000000`00000002 : nt!ExDeferredFreePool+0x3c7
ffffd000`b29a56a0 fffff800`77301992 : 00000000`00000000 00000000`00000000 ffffe001`ce0d0000
00000000`324d4740 : nt!ExFreePoolWithTag+0x84f
ffffd000`b29a5790 00000000`00000000 : 00000000`00000000 ffffe001`ce0d0000 00000000`324d4740
ffffe001`ce279bb0 : igdkmd64+0x1c992
STACK_COMMAND: kb
FOLLOWUP_IP:
igdkmd64+1c992
fffff800`77301992 ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: igdkmd64+1c992
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME: igdkmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52379d96
FAILURE_BUCKET_ID: 0x4E_9a_igdkmd64+1c992
BUCKET_ID: 0x4E_9a_igdkmd64+1c992
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x4e_9a_igdkmd64+1c992
The dump shows that the BSOD is probably caused by : igdkmd64.sys
It is known as Intel Graphic Kernel Mode Driver or belongs to software intel Graphic Accelerator Drivers for Windows.
I suggest you keep the latest version of the driver or software, or reinstall as a test.
Yolanda Zhu
TechNet Community Support

Random BSOD after installing port replicator drivers.

Hi, my boss just got a new laptop (TP T400s running Windows 7) and after configuring it, it was working fine. But then I installed the drivers for the USB port replicator with digital video and after rebooting, right after the login screen, it BSOD, complaining about igdkmd64.sys. Rebooted again, it didn't crashed upon login this time, just a little while later when clicking on the start menu. After more test, the replicator seemed to work, but not the digital video port. The DVI connector didn't worked correctly, just the mouse pointer was being displayed. Trying to set resolution didn't do anything and switching output source via Win-P provoked a strange flickering for a minute or so and then the machine automatically rebooted. Tried the driver found on the CD (1.0) and also those available through Lenovo website (1.5.6.8), always the same thing. Now I've uninstalled the drivers and the random BSOD keep reappearing.
Is this issue common? Is the port replicator faulty or is it the ThinkPad? Is the windows installation screwed, can it be repaired? What is Lenovo return policy?
I've also seen lots of complaints on this forum about random shutdown, this would be as unacceptable for us than the current BSOD we're experiencing. Is that situation widespread?
P.S.: We're trying to get work done, not beta test Lenovo products!
Thanks
Solved!
Go to Solution.

nbuduroi wrote:
Hi, my boss just got a new laptop (TP T400s running Windows 7) and after configuring it, it was working fine. But then I installed the drivers for the USB port replicator with digital video and after rebooting, right after the login screen, it BSOD, complaining about igdkmd64.sys. Rebooted again, it didn't crashed upon login this time, just a little while later when clicking on the start menu. After more test, the replicator seemed to work, but not the digital video port. The DVI connector didn't worked correctly, just the mouse pointer was being displayed. Trying to set resolution didn't do anything and switching output source via Win-P provoked a strange flickering for a minute or so and then the machine automatically rebooted. Tried the driver found on the CD (1.0) and also those available through Lenovo website (1.5.6.8), always the same thing. Now I've uninstalled the drivers and the random BSOD keep reappearing.
Is this issue common? Is the port replicator faulty or is it the ThinkPad? Is the windows installation screwed, can it be repaired? What is Lenovo return policy?
I've also seen lots of complaints on this forum about random shutdown, this would be as unacceptable for us than the current BSOD we're experiencing. Is that situation widespread?
P.S.: We're trying to get work done, not beta test Lenovo products!
Thanks
The win7 driver for the usb port replicator with digital output is not out yet. So, you cannot get it work under win7. I recall seeing an official flyer of the product, in which there is a line stating that a win7 driver will be out in December.

BSOD VIDEO_DXGKRNL_FATAL_ERROR after sleep/hibernate on windows 8.1 HP Zbook 14

I have a new HP ZBook Mobile 14 workstation that I have upgraded to windows 8.1.
Unfortunately after it has gone to sleep/hibernate the machine will always BSOD referencing VIDEO_DXGKRNL_FATAL_ERROR when I try to wake it up. I have tried uninstalling and re-installing all the drivers but am not having any joy. I have also disabled
fast start up and hibernate from the power options but that has not improved the situation.
I have put the mini dumps on OneDrive: MiniDumps
Any help would be greatly appreciated!
Cheers, James

James
Ouch 21 crashes in a week. These were related to your video driver (igdkmd64.sys) causing DirectX to fail. There is a known problem with the March 2014 drivers (yours) and the July 2014 drivers. As a first step I would remove the current
driver and revert back to a driver that is at least 6 months older at least until they release a less buggy driver. This is one of those times when a newer driver isnt better.
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\New folder\083014-10375-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`d8607000 PsLoadedModuleList = 0xfffff802`d88d12d0
Debug session time: Sat Aug 30 09:42:27.923 2014 (UTC - 4:00)
System Uptime: 0 days 0:43:20.664
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 113, {17, ffffe000b97f5010, 0, 0}
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44 )
Followup: MachineOwner
1: 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: 0000000000000017, The subtype of the bugcheck:
Arg2: ffffe000b97f5010
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
CUSTOMER_CRASH_COUNT: 1
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 fffff8001d99c9ca to fffff802d875afa0
STACK_TEXT:
ffffd000`20945a18 fffff800`1d99c9ca : 00000000`00000113 00000000`00000017 ffffe000`b97f5010 00000000`00000000 : nt!KeBugCheckEx
ffffd000`20945a20 fffff800`1d82e990 : ffffe000`b97f5010 ffffe000`badcf880 ffffd000`20945a88 00000000`00000018 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffd000`20945a60 fffff800`1f096e8c : ffffe000`b99f9000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+0x44
ffffd000`20945a90 ffffe000`b99f9000 : 00000000`00000001 00000000`00000000 00000000`00000000 ffffe000`c0a918e0 : igdkmd64+0x3be8c
ffffd000`20945a98 00000000`00000001 : 00000000`00000000 00000000`00000000 ffffe000`c0a918e0 fffff800`1f093c22 : 0xffffe000`b99f9000
ffffd000`20945aa0 00000000`00000000 : 00000000`00000000 ffffe000`c0a918e0 fffff800`1f093c22 ffffe000`c0689880 : 0x1
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44
fffff800`1d82e990 4869cf08020000 imul rcx,rdi,208h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 539a2a6c
IMAGE_VERSION: 6.3.9600.17210
BUCKET_ID_FUNC_OFFSET: 44
FAILURE_BUCKET_ID: 0x113_dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB
BUCKET_ID: 0x113_dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x113_dxgkrnl!dxgadapter::setpowercomponentactivecb
FAILURE_ID_HASH: {e8253e80-8827-02a0-2ed9-269d46938eb3}
Followup: MachineOwner
1: 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: 0000000000000017, The subtype of the bugcheck:
Arg2: ffffe000b97f5010
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
CUSTOMER_CRASH_COUNT: 1
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 fffff8001d99c9ca to fffff802d875afa0
STACK_TEXT:
ffffd000`20945a18 fffff800`1d99c9ca : 00000000`00000113 00000000`00000017 ffffe000`b97f5010 00000000`00000000 : nt!KeBugCheckEx
ffffd000`20945a20 fffff800`1d82e990 : ffffe000`b97f5010 ffffe000`badcf880 ffffd000`20945a88 00000000`00000018 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffd000`20945a60 fffff800`1f096e8c : ffffe000`b99f9000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+0x44
ffffd000`20945a90 ffffe000`b99f9000 : 00000000`00000001 00000000`00000000 00000000`00000000 ffffe000`c0a918e0 : igdkmd64+0x3be8c
ffffd000`20945a98 00000000`00000001 : 00000000`00000000 00000000`00000000 ffffe000`c0a918e0 fffff800`1f093c22 : 0xffffe000`b99f9000
ffffd000`20945aa0 00000000`00000000 : 00000000`00000000 ffffe000`c0a918e0 fffff800`1f093c22 ffffe000`c0689880 : 0x1
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44
fffff800`1d82e990 4869cf08020000 imul rcx,rdi,208h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 539a2a6c
IMAGE_VERSION: 6.3.9600.17210
BUCKET_ID_FUNC_OFFSET: 44
FAILURE_BUCKET_ID: 0x113_dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB
BUCKET_ID: 0x113_dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x113_dxgkrnl!dxgadapter::setpowercomponentactivecb
FAILURE_ID_HASH: {e8253e80-8827-02a0-2ed9-269d46938eb3}
Followup: MachineOwner
1: kd> lmvm dxgkrnl
start end module name
fffff800`1d818000 fffff800`1d999000 dxgkrnl (pdb symbols) c:\symbols\dxgkrnl.pdb\9D44B2A5938E41528DA86348D6D1F5C21\dxgkrnl.pdb
Loaded symbol image file: dxgkrnl.sys
Mapped memory image file: c:\symbols\dxgkrnl.sys\539A2A6C181000\dxgkrnl.sys
Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
Image name: dxgkrnl.sys
Timestamp: Thu Jun 12 18:32:12 2014 (539A2A6C)
CheckSum: 00185C7C
ImageSize: 00181000
File version: 6.3.9600.17210
Product version: 6.3.9600.17210
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.3.9600.17210
FileVersion: 6.3.9600.17210 (winblue_gdr.140612-1509)
FileDescription: DirectX Graphics Kernel
LegalCopyright: © Microsoft Corporation. All rights reserved.
Wanikiya and Dyami--Team Zigzag

INTERNAL_POWER_ERROR and VIDEO_TDR_FALIURE BSODs on Windows 10

Hi there, I upgraded to Windows 10 4 days ago and ever since I am trying to fix this issue. The thing is that at first I could not open Catalyst Control Center as it would result into an INTERNAL_POWER_ERROR BSOD. I found a way to fix that (but not permanently). If I manually update my AMD drivers every time after I reboot, I am able to use my AMD Radeon HD8750M but a reboot or putting the laptop in sleep mode will cause the same BSOD over and over again. Sometimes when I try to hibernate the laptop I get a different BSOD of VIDEO_TDR_FAILURE which is cause by the Intel HD4600 driver. So my question is, what is going on with both drivers. I tried analyzing the crash dumps and they really are causing the issues. Did anyone find any permanent fix for that? For now I have tried installing the official AMD drivers, the drivers from the HP page and nothing works. Basically now I can only work straight away with my laptop but I cannot use hibernation and everytime I shut down I have to "fix it" again and again. For 4 days I was trying to find a solution on my own but I guess I cannot so now I decided to ask here. Thanks in advance!

Hi @vignesh310 ,
Thank you for your query, I will try my best to help!
I see you are getting this error " VIDEO_TDR_FALIURE (igdkmd64.sys)" This can be caused by out of date drivers.
You stated that if you uninstall the display driver then it works.
Have you ran the HP Support Assistant to aid with HP updates?
Here is a link to the recommended drivers for your system. HP Pavilion g6-2005tx Notebook PC Drivers
Please verify that you have the latest drives installed.
Here is a link to Computer Does not Start (Windows 7, Vista, XP) that may also help.
If you think it may be a hardware failure here is a link to assist you with the testing.
Testing for Hardware Failures (Windows 7, Vista)
I hope this is helpful!
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

Igdkmd64.sys blue screen

How exactly do I trouble shoot what is causing this random blue screen igdkmd64.sys? Thanks!

Hi,
Since Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a third-party device drivers, backup software or anti-virus services (buggy services).
The system goes to a BSOD because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case
some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).
To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that
a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a look at the web site listed below:
Microsoft - Help and Support
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see Microsoft Worldwide Home for regional support phone numbers.
http://www.microsoft.com/worldwide/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

W530 Frequent BSODs

NOTE: These are NOT BSODs when plugging/unplugging A/C power. This is a different issue.
On my nice new W530, I'm getting frequent (3/day) bluescreens.
They don't seem to occur in any pattern, or in any application specifically. I do not believe it to be a heat issue. (At least, the laptop feels cool to the touch.) I've gotten them playing games (graphically intensive, and not so graphically intensive), watching movies on netflix, and even casual use.
Specs:
i7-3160QM (2.30GHz)
8gb RAM
Windows 7 Home Premium 64-bit
nvidia Quadro K2000m
All the latest drivers (from Lenovo) installed.
There seem to be a few cuplrits in my dump files (from most to least common):
dxgmms1.sys (Appears most)
igdkmd64.sys (Appears twice)
nvlddmkm.sys (These two appear only once)
nvkflt.sys
These sound like graphics driver issues, but updating to the latest nVidia drivers (not Lenovo distributed) caused some other issues. Any help here would be appreciated.

'evening...
i did a little searching and a number of hits point to problems with DirectX, which makes sense based on the 1st file you mention: dxgmms1.sys.
a post from june, here: http://windows7bugs.wordpress.com/2012/06/26/windows-7-bsod-windows-7-x64-nvlddmkm-sys-dxgkrnl-sys-d... talks a bit about it and may be worth your further research. checking your version of DirectX and seeing if there is any available update, might clear things up for you.
regards.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
PM requests for individual support are not answered. If a post solves your issue, please mark it so.
X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
I am not a Lenovo employee.

BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL

Hello,
on my laptop i was playing GTA IV, i was driving around and i got this BSOD.
Bluescreenview says 033115-41093-01.dmp 31/03/2015 19:57:04 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`01d61a17 igdkmd64.sys igdkmd64.sys+62a17 x64 ntoskrnl.exe+14dca0 C:\WINDOWS\Minidump\033115-41093-01.dmp 2 15 9600 285,968 31/03/2015 20:00:18
i have searched this issue online and people say to update graphics drivers.
i have a clean install of 8.1 as my hard drive died a while ago.
so i installed hp support assistant and checked for updates. i try to install them but it just gets stuck on "Downloading" and at the top it says "Completed" and i click next but the updates are still there. so i tried reinstalling hp support assistant and rebooted after every step.
stil getting the issue.
anyone know a solution?
also, this may be the last laptop i will get.

The card I am using is a Condor Engineering CEI-520, recently acquired by GE. ( http://www.gefanucembedded.com/products/1025 ) It is a 16 channel digital serial card for testing avionics. This particular model is a PCI board. The card comes with a driver and DLL that you can program from user mode to do most things. However, for our particular application, I needed to hook interrupts. So I worked with Condor to write a driver to do that under WIN98. That driver has been functioning for 4 or 5 years now. This version I am working on now runs on Win2K and is completely redesigned. It has been running smoothly for about a year. This error only happens when we run a test that really taxes the system. We've got 3 channels of the PCI 6602 DMAing stuff while my card is busily servicing interrupts as well. We have previously ran this test successfully under WIN98 on this very machine. So my suspicion is that there is a synchronization issue in the WIN2K driver for the 6602 that gets uncovered by this scenario. Like I said in my original post, I have a Kernal Dump I can provide to the NI developer if they want to look into it. They can load that into windbg and see what led up to the crash. I can't really learn anything from it because I don't have the driver source for the 6602. If I had that and a symbol file, I could probably debug it myself.
I have an identical system that I am going to run this test on today for comparison.

GT70-2OD BSOD after BIOS /EC update

Hello all,
I was having wireless disconnect issues with the Killer N1202. I had changed a couple of my wireless router's settings and updated to the latest Killer drivers / network manager and turned off the application monitoring. I still had the disconnect issue.
In my zeal to fix the problem, I decided to flash the BIOS and EC firmware. The notebook is the GT70-2OD (1763) RAID, full color backlit keyboard, Windows 8 64-bit so these are the files I used to flash:
BIOS - w8_E1763IMS.70E.zip - flashed with EFI_Boot process
EC firmware - w8_1763EMS1.505.zip - used winflash in Windows 8 - made sure i closed as many apps as I could beforehand.
Followed the flashing instructions to the letter. After each flash, disconnected the AC and removed the battery for no less than 5 minutes.
When I booted the notebook back up, I got the BSOD - VIDEO_TDR_FAILURE (igdkmd64.sys) when I tried to log in to Windows. At that point, had to go into safe mode and disable the Intel graphics driver. This allowed me to log in. I then tried updating the Intel graphics driver to the latest Win8-64 version. Still got the same BSOD at login.
With even more zeal, decided to rebuild to the factory Windows installation with the MSI recovery. It pulls up the initial config screens in Windows, but still the same BSOD. Can't even get to safe mode now or get past the configuration screens. Safe mode isn't an option either. Windows throws an error that it cannot enter safe mode because setup has not completed. So much for zeal.
Just looking for some suggestions.
Is there a way to roll back the EC and BIOS? If I can, and if it's even advisable at this point, where would I find the older versions? The product and download sites only list the most recent.
Thanks for any help on this.

I haven't tried any different drivers other than the ones I mentioned in my post. I will try a fresh install of the OS and go from there. Ran the memtest86+ util for three passes and the memory looks good. Unfortunately, I didn't record what versions of the previous EC and BIOS.
I will post the results of the fresh OS install soon.
Thanks
George

Tecra M9-136 - BSOD during Vista SP2 update

Tecra M9-136 asked this morning to update to Vista SP2 and during the process the BSOD 0x0000007E arrived. Restarted in Safe Mode and the installer continued and then finally reported that the update had failed - and reverted to SP1. This took most of the morning.
It will start in Safe Mode but on a normal boot-up, Vista SP1 gets through the fingerprint recognition and then fails with the same BSOD (it doesn't get as far as displaying the desktop).
The laptop has BIOS level 1.80. I've tried in Safe mode to install 1.90 but it tells me that the battery has insufficient charge and the power adapter isn't attached. Both untrue.
Stuck - need advice. Could this be a hard fault? Can't see how I can update anything if it's a soft fault.
thanks

The message with the BSOD mentioned checking BIOS and driver versions. Anyway, no change made to that.,
I tried System Restore but the only available restore point was the SP2 installation. I thought Vista was supposed to save a restore point every 24 hours even if nothing new had been installed.
I've now found in System Information / Windows Error Reporting several messages like this:
28/09/2009 12:08 Windows Error Reporting Fault bucket 0x7E_NULL_IP_DRVNDDM+57bd, type 0
Event Name: BlueScreen
Response: None
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\Mini0928 09-04.dmp
C:\Users\me\AppData\Local\Te mp\WER-75660-0.sysdata.xml
C:\Users\me\AppData\L ocal\Temp\WER7D78.tmp.version.txt
& #x000d;
These files may be available here:
C:\Users\me\AppData\Local\Mic rosoft\Windows\WER\ReportArchive\Report06d1c4b5

Pavilion Elite e9180f freezes, crashes, BSOD

I am one of the many unhappy customers who bought this piece of junk (Pavilion Elite e9180f) and waited too long to return it because in my naivete, I thought it was some kind of simple software issue. Nope! It's definitely something wrong with the hardware, because the freezes and crashes have been happening since day 1, right when I took the thing out of the box.
Yeah, the system is fast and runs Windows Vista great, when it's actually WORKING, which is usually only guaranteed for about the first 5 minutes after you power the system on and boot windows. After that, it's just buying time before it crashes again. Forget trying to get anything done on this computer. Forget about asking this PC to play a video or music file without the files "stuttering" during playback. Even my 7 year old Sony Vaio which is running XP can handle playing an MP3 file without stuttering and crashing!
Like everyone else, the freezes and crashes happen either one of two ways:
1) The machine begins to "stutter", stutter more, then freeze/crash. When I say stutter, I mean I move the mouse, the pointer graphic will hesitate on the screen and lag behind. If you start to play a video or music file, this manifests in an audible "stutter". The stuttering gets worse and worse as minutes pass until eventually it freezes for good, blasting that 1/50th second moment of audio into infinity. You have to reboot immediately if you don't want to go deaf or be driven mad.
2) I will be doing nothing at the time (example, I close all programs out and leave Windows sitting on the main desktop screen), I'll walk out of the room for a minute, then come back and find I can't move the mouse. This system will often lock-up without any warning!
Sometimes I'll get a BSOD or error screen, sometimes I won't (in which case your only option is to do a cold re-boot.) When I do get the BSOD, the error is ALWAYS the "did not get a response from the secondary processor" yada yada. I wish HP would just admit they shipped this model out with a bad processor/motherboard/whatever and do an official recall. I have owned PCs for the last 13 years and this is the worst and most consistently disappointing experience I have ever had.
What is the hardware issue? Which part is the lemon part? The motherboard? The processor? The BSODs seem to indicate a bad processor. I do have the Pegatron Truckee version 1.03 motherboard. Is that the problem?
P.S. I have contacted HP on many occasions about this, literally stayed on the phone for hours with "customer support" (according to one HP rep, 80% of their customer service reps are based outside of the United States...good luck getting any "technical" help from them) to no avail. I did talk to one nice tech support guy in Canada who said "it sounds like your unit has a bad processor", so he had HP send me a box to ship my unit to their repair center so they can replace the processor. However, I have also had HP reps tell me it could be anything from the memory to the hard drive. Multiple HP reps claimed to me that they have "received no complaints" about this system. One guy told me he "thought he got an email last week" regarding "something" about the system, but couldn't remember what it was and he put me on hold while he searched for the email. He never found it. What a joke.
EDIT: Just to clarify, the crashing issue has been happening since day one, but initially I thought it was an issue with Vista. I had never owned or used Vista before, so I thought maybe Vista was just unstable. Nope. I know several people who own Vista and have never experienced these issues. I have downloaded every update from Microsoft/Windows Update. I have upgraded to Vista SP2 with all the latest drivers and software for all of my hardware. No luck. It is definitely a hardware issue. Thank god HP's warranty is good for 1 year (I bought my Elite in July).
Message Edited by Doonyman on 09-24-2009 02:58 AM

Unfortunately I have to add my disastrous encounter with HP's E9180F a true lemon HP is selling. I must take some responsibility for not carefully researching this model before I purchased, but I trusted the HP name and got stung- big time.
The scoundrel :
HP and its Pavilion Elite e9180f
Windows 7 64bit
motherboard - Pegatron Truckee ver 1.03
BIOS ver 5.22Intel Core i7 920 @ 2.67GHz
Memory 9206 MB Ram
As so many others have reported my HP E9180f started locking up and going to BSOD right out of the box. My first freeze-up came when I was doing the Windows update process. At first I didn't think much about it but I started getting random freezes a couple time a day. At that point I went online to see if others had experienced the same problem and perhaps had a fix. What I found was very troubling; I found extensive documentation describing my exact problems and what was really horrifying was the reports of how ridiculous HP's help services were treating people with the problem. At first I didn't totally believe what I was reading on HP's own customer forum; I do now.
·         I've went through the total recovery process three times now, HP techs have spent hours remotely running my computer, (yes it did lock up on them to)
·         I had to upgraded the BIOS. (HP tech tried, said he had, but he hadn't)
·         I was directed to clear the BIOS (luckily for me I had the tools
·         Updated all drivers again and again.
·         Next I was asked to remove the video card, memory, and motherboard power cable and reseat them. I declined because I didn't want to give HP any reason to void my HP 2 year House Call Care Pack which covers this unit. When I invited HP to send a service tech out to perform these tasks, they said that house call only covers part replacement, we weren't replacing a part. I couldn't believe what I was told. Are you feeling my frustration?
Keep in mind that each time HP requests that I make changes, they then ask me to test the system, which I did and each time with the same result, BSOD
I'm heading into my fifth week of working with HP to fix this problem. and I still haven't even been able to get my case moved up to a senior case manager, what a joke HP's help process is.
One conversation I loved was;
HP tech: "I'll have a senior case manager call you within 24 hours."
Skeptical me: "What should I do if I don't get a call?"
Silence, no response.
Me again: "What should I do if I don't get a call?"
HP tech: "That's an impossibility."
Guess what? The impossibility became reality (I bet you guessed) .
HP's last stall tactic was to have me fax them my proof of purchase and invoice and call back in 24 hours. Where have I heard that before? Apparently nothing can go forward until they receive it. So I faxed them the stuff within 10 minutes, and when I called back 24 hours later, guess what, you're right it wasn't on their system yet. I asked couldn't I be escalated to a senior case manager (it's apparent that only a senior case manager can do anything). "No," was the tech's reply, "call back again later".
Please if anyone out there knows the secrete to getting a senior case manager, or an HP tech support number here in the U.S. so I can get this thing fixed I'd love to know it.
Fast becoming HP never again.

BSOD (DRIVER_IR​QL_NOT_LES​S_OR_EQUAL igdkmd64.s​ys)

Similar Messages

Maybe you are looking for

BSOD (DRIVER_IRQL_NOT_LESS_OR_EQUAL igdkmd64.sys)