- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Intel Community and Support Team,
I am writing to report a persistent and long-standing Blue Screen of Death (BSOD) issue I've experienced with Intel Arc graphics drivers. This issue dates back to the launch of the Arc A770 and continues to occur on my current system featuring the recently released Arc B580.
System Configuration:
- CPU: AMD Ryzen 9 7950X (iGPU Disabled in BIOS)
- GPU: Maxsun Intel Arc B580 12G (Triple Fan version) - (Previously experienced the same issue on an Intel Arc A770 16GB Limited Edition)
- Motherboard: Gigabyte B650M AORUS PRO AX
- RAM: KingBank DDR5 Hynix A-die 128GB (4x32GB) @ 5200MT/s
- OS: Windows 11 Pro 26100.3624
- Intel Graphics Driver Version: 32.0.101.6653, download from Intel's site
Bug Description:
The system experiences a BSOD with the Bug Check Code 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA). The crash dump analysis consistently points to the Intel Graphics Kernel Mode Driver, igdkmdnd64.sys, as the faulting module.
- Bug Check Code: 0x50
- Bug Check String: PAGE_FAULT_IN_NONPAGED_AREA
- Faulting Module: igdkmdnd64.sys
- Arguments from recent dump (040625-9125-01.dmp):
- Arg1: ffffd3f20e1ff800 (Memory referenced)
- Arg2: 0000000000000002 (Write operation)
- Arg3: fffff8006e8b6206 (Instruction address in igdkmdnd64.sys)
- Arg4: 0000000000000002
- Process Context: The crash often occurs within the context of dwm.exe.
Steps to Reproduce:
The BSOD occurs with a high probability under the following specific conditions:
- Leave the computer idle until it enters a standby/idle state, the screen is locked, and the monitor(s) have entered sleep mode (black screen).
- From another computer, attempt to connect to this machine using Windows Remote Desktop Connection (RDP).
- A BSOD occurs with high likelihood, either immediately upon the connection attempt or shortly after the remote session tries to initialize.
Impact and Context:
This system is used in a productivity environment, and this recurring BSOD has a severe negative impact on my work.
Importantly, this system was previously perfectly stable with both an NVIDIA GeForce RTX 4070 Super and an AMD Radeon RX 7700 XT installed, experiencing no similar RDP-related crashes. The problem only started after installing the Arc B580.
Furthermore, this is not a new issue isolated to the B580. I experienced the exact same bug (same code, module, RDP trigger) with an Intel Arc A770 16GB Limited Edition on a previous system, dating back approximately 2.5 years to the card's launch timeframe. This strongly indicates a persistent, underlying driver issue across Arc generations in handling RDP connections or related system state transitions.
Troubleshooting Attempted:
- Before installing the Arc B580 and its drivers, I performed a thorough driver removal using DDU in Safe Mode to eliminate potential conflicts.
- I then installed the latest official Arc graphics driver downloaded directly from the Intel website.
- Despite these steps, the BSOD issue persists on the B580, replicating the behavior seen on the A770 years ago.
- Ensured Windows, Motherboard BIOS, and AMD Chipset drivers are all up-to-date.
- Verified system stability otherwise (passes stress tests, memory checks, etc.).
Request:
Could the Intel graphics driver team please prioritize investigating this critical, long-standing issue? The inability to reliably use Remote Desktop severely hinders the usability of Arc GPUs in professional and productivity scenarios. I have attached the most recent minidump file (040625-9125-01.dmp) to this post [Or: I can provide the minidump file upon request].
Thank you for your time and assistance.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.015 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.188 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 43
Microsoft (R) Windows Debugger Version 10.0.27793.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\040625-9125-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 26100 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`97a00000 PsLoadedModuleList = 0xfffff800`988f47a0
Debug session time: Sun Apr 6 01:50:31.102 2025 (UTC + 8:00)
System Uptime: 4 days 11:42:54.465
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
................................................................
...
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000b9`19923018). Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff800`97eb7ce0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc0b`4be0d7f0=0000000000000050
12: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffd3f20e1ff800, memory referenced.
Arg2: 0000000000000002, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8006e8b6206, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for igdkmdnd64.sys
KEY_VALUES_STRING: 1
Key : AV.Type
Value: Write
Key : Analysis.CPU.mSec
Value: 1359
Key : Analysis.Elapsed.mSec
Value: 1462
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 265
Key : Analysis.Init.Elapsed.mSec
Value: 9813
Key : Analysis.Memory.CommitPeak.Mb
Value: 89
Key : Analysis.Version.DbgEng
Value: 10.0.27793.1000
Key : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre
Key : Analysis.Version.Ext
Value: 1.2410.2.2
Key : Bugcheck.Code.LegacyAPI
Value: 0x50
Key : Bugcheck.Code.TargetModel
Value: 0x50
Key : Dump.Attributes.AsUlong
Value: 0x21008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0x0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: AV_W_(null)_igdkmdnd64!unknown_function
Key : Failure.Exception.IP.Address
Value: 0xfffff8006e8b6206
Key : Failure.Exception.IP.Module
Value: igdkmdnd64
Key : Failure.Exception.IP.Offset
Value: 0x306206
Key : Failure.Hash
Value: {edb96eb7-b673-d178-0b8a-baf22f5912b8}
BUGCHECK_CODE: 50
BUGCHECK_P1: ffffd3f20e1ff800
BUGCHECK_P2: 2
BUGCHECK_P3: fffff8006e8b6206
BUGCHECK_P4: 2
FILE_IN_CAB: 040625-9125-01.dmp
DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump
FAULTING_THREAD: ffffab065fbbf040
READ_ADDRESS: fffff800989c34b0: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffd3f20e1ff800
MM_INTERNAL_CODE: 2
IMAGE_NAME: igdkmdnd64.sys
MODULE_NAME: igdkmdnd64
FAULTING_MODULE: fffff8006e5b0000 igdkmdnd64
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: dwm.exe
TRAP_FRAME: fffffc0b4be0da50 -- (.trap 0xfffffc0b4be0da50)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=000000006e706b37 rbx=0000000000000000 rcx=ffffab0632c02000
rdx=fffffc0b4be0dce0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8006e8b6206 rsp=fffffc0b4be0dbe0 rbp=fffffc0b4be0dce0
r8=0000000000000004 r9=00000000fffff800 r10=ffffd3f20e1ff800
r11=fffffc0b4be0dd18 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
igdkmdnd64+0x306206:
fffff800`6e8b6206 418902 mov dword ptr [r10],eax ds:ffffd3f2`0e1ff800=????????
Resetting default scope
STACK_TEXT:
fffffc0b`4be0d7e8 fffff800`97cc9301 : 00000000`00000050 ffffd3f2`0e1ff800 00000000`00000002 fffffc0b`4be0da50 : nt!KeBugCheckEx
fffffc0b`4be0d7f0 fffff800`97c8ebdf : ffffd3f2`0e1ff800 00000000`00001000 00000000`00000002 fffff800`97a00000 : nt!MiSystemFault+0x735
fffffc0b`4be0d8e0 fffff800`980880cb : 00000000`00000000 00000000`00000000 00000000`00000000 fffffc0b`4be0dc60 : nt!MmAccessFault+0x2ff
fffffc0b`4be0da50 fffff800`6e8b6206 : ffffab06`32c02000 fffff800`6e8b610c fffffc0b`4be0dc00 00000000`00000000 : nt!KiPageFault+0x38b
fffffc0b`4be0dbe0 ffffab06`32c02000 : fffff800`6e8b610c fffffc0b`4be0dc00 00000000`00000000 00000000`fffff800 : igdkmdnd64+0x306206
fffffc0b`4be0dbe8 fffff800`6e8b610c : fffffc0b`4be0dc00 00000000`00000000 00000000`fffff800 00000000`00000000 : 0xffffab06`32c02000
fffffc0b`4be0dbf0 fffffc0b`4be0dc00 : 00000000`00000000 00000000`fffff800 00000000`00000000 00000000`00000005 : igdkmdnd64+0x30610c
fffffc0b`4be0dbf8 00000000`00000000 : 00000000`fffff800 00000000`00000000 00000000`00000005 fffffc0b`4be0dc60 : 0xfffffc0b`4be0dc00
SYMBOL_NAME: igdkmdnd64+306206
STACK_COMMAND: .process /r /p 0xffffab06ca8e90c0; .thread 0xffffab065fbbf040 ; kb
BUCKET_ID_FUNC_OFFSET: 306206
FAILURE_BUCKET_ID: AV_W_(null)_igdkmdnd64!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {edb96eb7-b673-d178-0b8a-baf22f5912b8}
Followup: MachineOwner
---------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Patrick_Star_Y ,
Let me look into this concern for you. I will coordinate this matter internally and provide you with an update as soon as there is progress or development. I appreciate your patience and the detailed description of the issue.
Regards,
Randy T.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you need the minidump file from the BSOD? If so, how should I send it to you?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Patrick_Star_Y ,
Yes, please. It would be helpful to include the crash report. Additionally, could you try updating to the latest version of the graphics driver, 32.0.101.6732, and observe if the issue persists? You might also consider updating the motherboard BIOS or loading the default settings in the BIOS configuration. Let me know if there are any changes.
Regards,
Randy T.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is the dump file from when the BSOD occurred.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Patrick_Star_Y ,
Following our previous discussion, you may also check the available resolutions provided here, as this might help resolve the issue and determine the reason behind the error code. Let me know if this helps.
Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA - Windows drivers | Microsoft Learn
Regards,
Randy T.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Patrick_Star_Y ,
Just checking in on my previous message regarding your inquiry. Have you had a chance to review it? If you need more information or have any questions, feel free to reach out. I'm here to help!
Regards,
Randy T.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apologies for the delayed response; I've been quite busy with work recently. Thank you for your previous messages and suggestions.
Since my initial report (where I was using driver 32.0.101.6653), I have had the chance to test two different WHQL driver versions based on your feedback and subsequent releases:
Driver Version 32.0.101.6651: Unfortunately, with this driver, I still experienced driver crashes. However, the symptom changed: instead of a Blue Screen of Death (BSOD), the driver would simply crash without bringing down the system. This still consistently occurred after the PC (with the Arc B580 12G) was accessed via Windows 11 Remote Desktop (RDP) and then left idle for several hours. When the crash happened, the Intel® Graphics Software (Arc Control) would display a notification indicating a driver problem, but no BSOD occurred.
Hypothesis & Latest Test (Driver Version 32.0.101.6734): The behavior with driver .6651 led me to suspect that perhaps the Intel® Arc Control software component (or another related software piece installed alongside the driver) might be contributing to the instability, rather than just the core driver itself. Therefore, yesterday I installed the latest available WHQL driver, 32.0.101.6734. Crucially, this time I performed a driver-only installation, specifically choosing not to install the Intel® Arc Control software or any other optional graphics software components. As of now, the system has been running stably with this driver-only configuration for over 24 hours, including periods of idle time after RDP sessions, without any driver crashes or anomalies observed.
Additional Observation - VRAM Usage:
It's also worth noting that my PC is used for productivity and is almost never shut down. As a result, the graphics card's VRAM (Video Memory) usage tends to increase gradually over extended periods of uptime. Looking back, the driver crashes I experienced (both the original BSODs and the non-BSOD crashes with driver .6651) seemed more likely to occur when the dedicated GPU Memory utilization exceeded approximately 80%. This might be another factor contributing to the issue, potentially exacerbated by RDP state transitions or the Arc Control software.
Summary & Next Steps:
The preliminary results suggest that installing only the core graphics driver (.6734) without the accompanying Intel Arc Control software might mitigate or resolve the RDP-related crash issue. I will continue monitoring the system closely with this driver-only setup.
Regarding your previous request: While I haven't experienced a BSOD since switching to the driver-only installation of .6734, I still have the minidump file (040625-9125-01.dmp) from the original BSOD incident reported with driver .6653. If your team still requires it for analyzing the underlying cause (which might still exist even if Arc Control was the trigger for the crash), please let me know the preferred method for uploading it.
Thank you again for your support and investigation.
Best regards,
Patrick_Star_Y
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Patrick_Star_Y,
Quite interesting findings and a detailed report. Yes, kindly provide the crash dump. You can attach the file here, or if you're not comfortable, you may share it through email. Just let me know so I can send you a separate email. I will coordinate this concern internally and report back to you once I have completed our investigation. We value your feedback and are dedicated to improving our products.
Regards,
Randy T.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am now almost certain that the Intel® Arc Control software or one of its related components is causing the driver instability/anomalies.
As I mentioned previously, this time I installed driver 32.0.101.6734 using a driver-only method, without installing any of the associated software. With this configuration, the driver has been running very stably, and the computer has not experienced any driver-related issues whatsoever.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
https://drive.google.com/file/d/10TFL4RG0Oxx_N-P6QttcpgIFfk_h85kW/view?usp=sharing
Here is the link to the minidump file from the BSOD.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Patrick_Star_Y,
Thank you for sharing this information. I will begin investigating the issue and attempt to replicate it on our end. I'll post an update here or notify you directly once there are any developments. If I need further details, I'll reach out to you here. I appreciate your patience as I work on this matter.
Regards,
Randy T.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Patrick_Star_Y,
Thank you for sharing this information. I will begin investigating the issue. I'll post an update here or notify you directly once there are any developments. If I need further details, I'll reach out to you here. I appreciate your patience as I work on this matter.
Regards,
Randy T.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Patrick_Star_Y,
As we continue to investigate the issue you reported regarding the Intel Graphics Driver, we would like to gather a bit more information to ensure we address your concerns accurately.
Could you please clarify which application you are using for remote desktop support? Specifically, are you utilizing Quick Assist or Remote Desktop Connection? This information will help us better understand the context of the issue.
Additionally, we would like to know whether the computer with the Intel Arc B580 installed is the remote system you are accessing, or if it is the workstation you are using to access a remote desktop. This detail is crucial for our investigation.
Your feedback is invaluable to us, and we are committed to resolving this matter promptly. Thank you for your cooperation and assistance.
Looking forward to your response.
Regards,
Randy T.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page