Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
20721 Discussions

A750: Intant freeze on boot with driver 4314 and crash with error 0x00000116

AlexanderDev
Beginner
5,263 Views

I got new system setup and right away after installing latest drivers 4314 the system would freeze on boot right after the intel arc control panel would start to load.

 

I was able to uninstall the drivers in safe mode and reinstall 4314 without the control panel, however that would cause the system to randomly freeze as soon as windows loads and up to few min after.

 

After searching internet, i have discovered that it could be due to driver 4314, so i have booted in safe mode, used ddu to wipe driver, boot to windows and installed only 4255 driver.

 

That seem to have resolved instant freezing, however then i have noticed that my system started to crash when i would exit hogwarts legacy with error:

 

 

 

 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000116 (0xffffcc02cfbd4460, 0xfffff80163a66850, 0x0000000000000000, 0x000000000000000d). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: b9b814f3-1a03-4b32-9016-66f4788f200c.

 

 

 

 

Upon further investigating, i have discovered that both issues are related to drivers and how drivers access re-bar.

 

I have made sure that my rebar is enabled, technically its only auto option available. Bios on my mainboard is latest one.

 

Any way to resolve the issues I am seeing with driver and system freezing crashing?

 

Build:

  • windows 10
  • intel arc a750
  • r5 5600x
  • gigabyte b550m k
  • 16 ram
  • 500 gig ssd
  • seasonic 500w psu

 

Bios screenshot and system report attached.

 

0 Kudos
20 Replies
Hugo_Intel
Employee
5,217 Views

Hello AlexanderDev


Thank you for posting n the Intel Communities. I am sorry you are experiencing crashes and freezing issues with your Intel® Arc™ A750 Graphics.


  • Please reseat and make sure the GPU is well seated in its PCIE slot, as well as make sure that the cables are properly connected.
  • I also noticed in your post that you are using a 500W PSU, this would not meet the minimum requirement which is 600W, Can you please test another PSU?


In addition, please share with us the following information:


  • Share the crash log files from Windows, they should be located at C:\Windows\minidump. Make sure to gather the log file right after a crash/BSOD occurs.
  • Share a short video showing the issue.


Best Regards,


Hugo O.

Intel Customer Support Technician.


0 Kudos
AlexanderDev
Beginner
5,189 Views
Interesting in regards to 600w PSU requirements, I have already ordered one.

I will post crash dump as soon as I can, and will also reseat GPU.

After the reseating and 600w PSU installation, should I stay on current driver, update current latest or wait for new driver to come out?
0 Kudos
Hugo_Intel
Employee
5,174 Views

Hello AlexanderDev


If the issue is coming from the PSU, you should be able to use any of the drivers, however, I would advise you to update to version 31.0.101.4314, and if there are still issues try again the version 31.0.101.4335. Let us know the results.


Best Regards,


Hugo O.

Intel Customer Support Technician.


0 Kudos
AlexanderDev
Beginner
5,163 Views

Hi Hugo,

 

Here is the update.

 

  1. After re-seating gpu and booting back to windows, intel popped up with the message that re-bar is not enabled.
    1. I have reinstalled the 4225 driver and installed gpu-z, both indicated re-bar was not enabled
    2. After quick search on the internet I have discovered that its common issues with gigabyte motherboards. The recommended solution was to reinstall latest bios update and then re-enable re-bar in the bios.
    3. After bios was reinstalled and re-bar was enabled once more, both intel control panel and gpu-z reported that re-bar is now enabled, YAY.
  2. Core dumps uploaded.
  3. For PSU I am still waiting for it to be delivered.
0 Kudos
Hugo_Intel
Employee
5,093 Views

Hello AlexanderDev


Thank you for the update. We will check the dump file and see if there is more information related to this crash. If you happen to be able to test the new PSU before we post back, feel free to post and let us know.


Best Regards,


Hugo O.

Intel Customer Support Technician.


0 Kudos
AlexanderDev
Beginner
5,072 Views

Hi @Hugo_Intel 

 

I have installed 700w thermaltake smart series 80 plus power supply, and installed latest driver manually ( arc panel indicated 4225 was the latest as well intel driver update tool ). I havent encountered any issues I have described above. Also updated to windows 11, no issues either.

 

I will need to run it for a day or 2 to be 100% sure that the issue has been resolved. However in the summary, the following seems to do the trick:

  1. re-seat gpu
  2. reinstall latest bios update and re-enable re-bar
  3. install 700w psu
0 Kudos
AlexanderDev
Beginner
5,057 Views

After installing driver 4314, i got game Hogwarts legacy to crash within 10 minutes of game play,

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000116 (0xffffb885775ca460, 0xfffff8068e9257e0, 0xffffffffc0000001, 0x0000000000000003). A dump was saved in: C:\WINDOWS\Minidump\051523-6390-01.dmp. Report Id: 690e1af3-2ede-4e57-b39e-99194fc1613e.

 

I have reverted back to driver 4225, which has been stable.

 

minidump is attached.

 

The back to original issue, the problem does not originate from power supply, really seems to be re-bar and 4314 driver.

0 Kudos
Hugo_Intel
Employee
4,996 Views

Hello AlexanderDev


Thank you for letting us know. I would like to get clarification on a couple of things:


  • You reported freezing issues when booting into Windows when driver 31.0.101.4314 is installed, Is this issue completely resolved using either driver 31.0.101.4255 or 31.0.101.4314?
  • As for the crashes you are reporting with Hogwarts Legacy, does the issue only happen with Hogwarts Legacy exclusively? Are you able to replicate it with any other app or game? And does it happen on either driver 31.0.101.4255 or 31.0.101.4314?


Best Regards,


Hugo O.

Intel Customer Support Technician.



0 Kudos
AlexanderDev
Beginner
4,988 Views
- Once re-flashing bios and re- enabling re-bar, I am now able to boot widows with both 4225 and 4314 drivers, on both 500 and 700 watt power supply.

- I only have tried one game for the moment which is Hogwarts legacy.
- it crashes/reboots windows on 4314, or if I downgrade from 4314 to 4225 without clean reinstall using utility like DDU. Happens on both 500 and 700 w PSU and on both windows 10/11
- if I cleanly install driver 4225 after DDU, then I haven't seen this crash so far. I have tested with both 500 and 700 watt PSU.
0 Kudos
Hugo_Intel
Employee
4,937 Views

Hello AlexanderDev


We want to rule out if this is specific to the Hogwarts Legacy game or if the issue might happen with other apps so we can troubleshoot or even do more research as it might be a bug with the game that would need further investigation. Could you please try other free-to-play games like Destiny 2, Fronite, or Apex Legends?


Also, there is a newer driver that was just released version 31.0.101.4369, let's also try to update to this version as it includes new features and improvements.


Best Regards,


Hugo O.

Intel Customer Support Technician.





0 Kudos
Hugo_Intel
Employee
4,817 Views

Hello AlexanderDev

  

I hope you are doing fine. 

  

Were you able to check the previous post? 

Let us know if you still need assistance. 

  

Best regards,  


Hugo O.  

Intel Customer Support Technician. 


0 Kudos
AlexanderDev
Beginner
4,805 Views

Hi @Hugo_Intel ,

 

I have tested out the Overwatch 2 and Hogwarts Legacy with 31.0.101.4369 driver, and its been good so far.

 

Can you tell me what is meaning behind 0x00000116 error?

0 Kudos
Hugo_Intel
Employee
4,779 Views

Hello AlexanderDev


It is good to know the issue is no longer happening. Answering your questions about the bug check 0x00000116 and based on the log files that you shared with us from Windows minidumps we found the following:

  • 050923-6578-01.dmp references fail at BTHport module which is related to the Bluetooth component either hardware or software (driver)
  • 051023-17859-01.dmp does reference to igdkmdnd64.sys which is an Intel Graphics driver component.


Also, based on this article from Microsoft the error is more related to graphics drivers failing so the issue could have been a previous conflicting driver. At the moment what I would advise is to monitor the system for a few more days and if possible to test more games or GPU-intensive applications and verify if the issue happens.


Best Regards,


Hugo O.

Intel Customer Support Technician.


0 Kudos
AlexanderDev
Beginner
4,736 Views

@Hugo_Intel The crash happened again while playing hogwarts legacy.

 

I have used minidump analyser, and once again its display driver related, allso i am not sure why it indicates windows 10, since I am on windows 11?

 

 

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


Loading Dump File [C:\Users\x\Downloads\052523-4796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802`7e600000 PsLoadedModuleList = 0xfffff802`7f2134d0
Debug session time: Thu May 25 00:17:37.185 2023 (UTC - 4:00)
System Uptime: 0 days 3:22:27.775
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`7ea2c0f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffe81`11e6f7e0=0000000000000116
9: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffc10794e31010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff802a0f05980, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.

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

Unable to load image igdkmdnd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmdnd64.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1734

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 4678

    Key  : Analysis.IO.Other.Mb
    Value: 17

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 34

    Key  : Analysis.Init.CPU.mSec
    Value: 234

    Key  : Analysis.Init.Elapsed.mSec
    Value: 82723

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 106

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x116

    Key  : Bugcheck.Code.Register
    Value: 0x116

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  052523-4796-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  116

BUGCHECK_P1: ffffc10794e31010

BUGCHECK_P2: fffff802a0f05980

BUGCHECK_P3: ffffffffc0000001

BUGCHECK_P4: 3

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffc10794e31010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000003

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffffe81`11e6f7d8 fffff802`92e5cf7e     : 00000000`00000116 ffffc107`94e31010 fffff802`a0f05980 ffffffff`c0000001 : nt!KeBugCheckEx
fffffe81`11e6f7e0 fffff802`92e036ba     : fffff802`a0f05980 ffffc107`80d85000 ffffc107`80d850f8 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
fffffe81`11e6f820 fffff802`92e046f6     : ffffc107`00000101 00000000`00000080 ffffc107`80d85000 00000000`00000080 : dxgkrnl!DXGADAPTER::PrepareToReset+0x222
fffffe81`11e6f8a0 fffff802`92e5c6d5     : 00000000`00000100 ffffc107`94e1d040 00000000`00000000 ffffc107`93a582b0 : dxgkrnl!DXGADAPTER::Reset+0x346
fffffe81`11e6f950 fffff802`92e5c832     : 00000000`00000000 ffffc107`8bbcfac0 00000000`00000000 fffff802`7f349ac0 : dxgkrnl!TdrResetFromTimeout+0x15
fffffe81`11e6f980 fffff802`7e8bd625     : ffffc107`94e1d040 ffffc107`7a8a3cb0 fffffe81`00000000 ffffc107`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
fffffe81`11e6f9c0 fffff802`7e8ccfd7     : ffffc107`94e1d040 00000000`0000073a ffffc107`94e1d040 fffff802`7e8bd4d0 : nt!ExpWorkerThread+0x155
fffffe81`11e6fbb0 fffff802`7ea31054     : ffffb100`3fb00180 ffffc107`94e1d040 fffff802`7e8ccf80 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffffe81`11e6fc00 00000000`00000000     : fffffe81`11e70000 fffffe81`11e69000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  igdkmdnd64+15980

MODULE_NAME: igdkmdnd64

IMAGE_NAME:  igdkmdnd64.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_igdkmdnd64.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7eb0cc99-c85b-4092-6430-8f1db059b7c1}

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

 

 

0 Kudos
Hugo_Intel
Employee
4,707 Views

Hello AlexanderDev


In this case, if the issue persists the best next step will be to do a clean installation of the Operating System, please reinstall Windows to make sure the are no conflicting files and check if the same issue happens.


Best Regards,


Hugo O.

Intel Customer Support Technician.


0 Kudos
Hugo_Intel
Employee
4,610 Views

Hello AlexanderDev


Were you able to do a clean installation of your Operating System on your computer? Please let us know if the issue persisted.


Best Regards,


Hugo O.

Intel Customer Support Technician.


0 Kudos
Ethernas
Beginner
4,554 Views

Hi Intel support,

 

 

we are experiencing a similar error on a intel nuc mini pc.

 

TERRA BRIX BEI5-1240 Barebone (4P+8E Cores/16Threads i5-1240P)
• Micro PC Barebone, Silver, 135 x 140 x 45 mm
• Intel Core™ i5-1240P, 1.70 GHz (4.40 GHz Turbo), TDP 28W
• 2 x SO-DIMM DDR4 PC3200, 1.2V, bis zu 64GB
• Intel Iris Xe Graphics, Realtek ALC897 HD Audio
• Intel I225V, 2.5G LAN RJ45, Intel WIFI 6E / Bluetooth 5.2
• 1x PCIe Gen4 x4 /SATA M.2 2280 slot
• Front IO:1x USB 3.2 Gen2 Type C, 3x USB 3.2 Gen2 Type A,
1x head phone jack with MIC
• Rear IO: 1x HDMI(2.1), 1x HDMI(2.0b), 1x mDP (up to 3x Displays),
1x USB 4.0 (Support Intel Thunderbolt 4 with DP mode)*, 2x USB 2.0,
1x RJ45, DC-in, Kensington Lock
• Incl. VESA Mounting Kit, Power Supply, Quick Start Guide

 

We having the same bug check Code and we tried as far replacing the whole nuc and reinstalling the whole os.

We used different hardware drivers of course from intel directly but we still get that error even with a complete new barebone and new Windows Installation .The machine is running on windows 11 22H2 Build Number 22621.1778.

 

I attached a hardware report and the bluescreen as a 7 Zip File.

 

 

0 Kudos
Hugo_Intel
Employee
4,524 Views

Hello Ethernas

 

This is not an Intel® NUC but a Mini-PC manufacturer by Gigabyte we would recommend using the driver listed on their website, the latest graphics driver version they recommend using seems to be 31.0.101.1029. in case the issue persists it would be better to reach Gigabyte directly as this is custom hardware, however, you can also feel free to open a new thread to further take a look at the issue since the thread owner of this one seems unresponsive this thread will no longer be monitored.

 

Best Regards,

 

Hugo O.

Intel Customer Support Technician.

0 Kudos
Hugo_Intel
Employee
4,524 Views

Hello AlexanderDev

  

I hope you are doing fine. 

  

I have not heard back from you. So I will close this thread. If you need any additional information, submit a new question, as this thread will no longer be monitored. 

  

Best Regards, 

 

Hugo O.  

Intel Customer Support Technician. 


0 Kudos
Hugo_Intel
Employee
4,432 Views

Hello AlexanderDev


Before closing the thread we just wanted to let you know that the freezing issue that started with the driver version 31.0.101.4314 was resolved in the latest BETA version 31.0.101.4382, so we would advise that you update to this latest version.


Best Regards,


Hugo O.

Intel Customer Support Technician.


0 Kudos
Reply