Error encountered during Nvidia GPU activation, SDXGKRNL and Video Memory issues.
Error encountered during Nvidia GPU activation, SDXGKRNL and Video Memory issues.
Custom Alienware design for laptops, Intel chipset.
CPU: Intel Core i7-10870H with 8 cores.
GPU: Nvidia GeForce RTC 3070 for laptops.
RAM: 32GB DDR4 at 2933MHz.
Power supply: 240W adapter.
Battery: 68Whr lithium-ion.
Storage: 1TB PCIe NVMe SSD (dual drives in RAID).
Operating system: Windows 11 24H2 (previously had BSOD issues earlier).
BIOS: 1.26.0 (latest version from Dell’s website).
I began experiencing BSOD after exiting a game (Dave the diver) on December 31st. Automatic driver updates were enabled, but I couldn’t confirm any installations during that period. I entered a BSOD restart loop, which occurred three times, displaying errors such as:
VIDEO_MEMORY_MANAGEMENT_INTERNAL
AND sometimes VIDEO_DXGKRNL_FATAL_ERROR.
After several loops, the Nvidia GPU would stop being detected, and the charging icon on my laptop would vanish even though the battery was charging. Restarting didn’t resolve the issue, but booting from shutdown helped occasionally. No specific warnings or conflict symbols appeared in Device Manager for drivers.
My troubleshooting steps included:
- Running a system file scan and DISM (all clear).
- Updating Windows and disabling automatic driver updates.
- Disabling background services like gaming input services and Dell support tools.
- Updating Intel drivers to the latest versions via Device Manager and Dell’s website.
- Reinstalling BIOS and resetting default settings.
- Performing a full malware scan with Windows Defender and Kaspersky (no threats found).
I also tried uninstalling Nvidia graphics drivers in safe mode, installing newer driver versions from both Nvidia and Dell websites, and using the latest studio and second-latest drivers. I reinstalled BIOS and set default configurations.
A full malware scan came back clean, though I scanned for Malware using Windows Defender and Kaspersky (no issues detected).
I disabled power settings to balanced performance, which worsened the problem and triggered a different BSOD error: DRIVER_POWER_STATE_FAILURE. I switched back to high performance after that. Virtual memory was disabled, so I enabled it to help detection.
I reconnected the battery using the power button for 20–30 seconds during shutdowns, which sometimes allowed the PC to detect the Nvidia GPU again.
I managed to restore the charging indicator with new drivers, but I took screenshots of GPU statistics via GPU-Z before BSOD occurred. Links are available here:
https://imgur.com/a/gpu
View: https://imgur.com/a/gpu-z-stats-on-intel-nvidia-gpu-sA
I can still use my PC with the new Nvidia driver, but only when disabled in Device Manager; enabling it causes a BSOD shortly afterward. When using balanced power settings, I encountered bug codes 9f (driver ntoskrnl.exe) and 10e/113 (battery on performance).
I found a link to a zip with minidump files from the original errors (excluding power-related ones):
https://www.mediafire.com/folder/zcb8n69...rror_Stuff
Some error logs I recommend reviewing: 010225-9687-01.dmp and 010225-14796-01.dmp.
I’m unsure what to do next—consider rolling back to Windows 11 23H2, trying DDU again with new drivers, or performing a cloud reset. I worry about the GPU but don’t think it’s faulty based on current info. I’m not confident opening it myself due to hardware unfamiliarity. I might need to take it to a repair shop to test if possible. There’s a possibility of driver updates arriving soon, but I’m hesitant since I rely on the Nvidia GPU for ML tasks. Is resetting the PC worth it? Should I opt for a cloud reset or a local one?
What do you think is happening—corrupted files or a hardware issue? What steps should I take next?
unusual cpu performance: present speed
begin by obtaining Microsoft autoruns64.exe from the provided link:
https://learn.microsoft.com/en-us/sysint...s/autoruns
execute it with administrative privileges, locate the relevant driver and turn it off:
iocbios2 Fri Jun 16 15:05:53 2023
restart your system and verify whether the issue persists without the overclock driver.
reminder: the valid kernel address is located outside a file that triggers GPU-related power functions. It seems a service communicates with BIOS via iocbios2.sys. Disabling this unusual clocking may resolve the problem. Your CPU details:
Intel® Core™ i7-10870H at 2.20GHz
previously experienced underclocking, which could point to overheating or a mismatch between the driver and BIOS version.
alternatively, updating the NVGA graphics driver without updating the GPU sound driver might be the cause—this often occurs when users neglect to refresh the GPU audio driver alongside a graphics update.
Sorry, it took me a while, unfortunately. In your response, I installed autoruns and observed four drivers highlighted in red (which might indicate unverified correctness):
1) DDDriver DDDriver: (Not Verified) C:\WINDOWS\System32\drivers\dddriver64Dcsa.sys Oct 26 09:26:22 2020
2) NvModuleTracker NvModuleTracker: Process and module monitoring driver (Not Verified) C:\WINDOWS\System32\drivers\NvModuleTracker.sys Mar 5 06:54:38 2020
3) nvvad_WaveExtensible NVIDIA Virtual Audio Device (Wave Extensible) (WDM): (Not Verified) C:\WINDOWS\system32\drivers\nvvad64v.sys Mar 7 04:03:32 2020
4) nvvhci NVVHCI Enumerator Service: (Not Verified) C:\WINDOWS\System32\drivers\nvvhci.sys Mar 12 14:26:38 2020
Additionally, during DDU checks I ensured a clean install and verified the device manager. I confirmed the presence of NVIDIA High Definition Audio with an updated driver.
Following your advice about nvidia drivers and unverified ones, I disabled driver signature enforcement using the command in cmd: bcdedit.exe /set nointegritychecks.
Although the crash wasn't immediate, I still experienced the same BSOD. I managed to capture more GPU readings via GPU-Z (see links).
In autoruns, I couldn't locate iocbios2.sys and renamed it to iocbios22.sys before rebooting, but the issue persisted. Later, renaming it to iocbios243ffd.sys helped, with new readings available.
I opened the Control Panel, switched between GPUs, and selected only the NVIDIA GPU in cmd, which showed stable readings. I also ran nvidia-smi in cmd for additional details. Some NA values appeared.
After a long wait, I closed all apps, then when I ended GPU-Z, my screen went blank and triggered a BSOD with error: DRIVER_POWER_STATE_FAILURE.
The three minidumps are available here: [link].
A small update: I reset my PC, which left me stuck on 24H2 (unfortunately). Since I did this, I noticed three drivers now listed as unknown in the Device Manager (possibly matching the red drivers from autoruns?).
1) Unknown Driver 1
Device settings for ROOT\UNNAMED_DEVICE\0000 were moved from a previous OS.
Last Device Instance ID: ROOT\UNNAMED_DEVICE\0000
Class GUID: {4d36e96c-e325-11ce-bfc1-08002be10318}
2) Unknown Driver 2
Device settings for ROOT\UNNAMED_DEVICE\0001 were moved from a previous OS.
Last Device Instance ID: ROOT\UNNAMED_DEVICE\0001
Class GUID: {aa018edf-4915-415e-9c17-d7ebec8917d2}
3) Unknown Driver 3
Device settings for ROOT\UNNAMED_DEVICE\0002 were moved from a previous OS.
Last Device Instance ID: ROOT\UNNAMED_DEVICE\0002
Class GUID: {4d36e97d-e325-11ce-bfc1-08002be10318}
Considering this, it seems there might be a hardware problem or at least some hope remains.
it seems the bio was modified but not all drivers were updated. Please visit the link provided: https://www.dell.com/support/home/en-ie/...op/drivers, then choose find drivers and perform the updates. Many of the special intel drivers come from an older build and haven’t been updated. For instance:
iaLPSS2_GPIO2_CNL.sys Tue May 12 00:32:17 2020
iaLPSS2_I2C_CNL.sys Tue May 12 00:31:46 2020
iaStorAC.sys Fri Nov 25 02:32:36 2022
dptf_acpi.sys Fri Mar 12 15:40:08 2021
dptf_cpu.sys Fri Mar 12 15:40:10 2021
HID_PCI.sys Sun Jul 25 22:45:34 2021
not clear what this driver does:
ISH_BusDriver.sys Sun Jul 25 22:45:31 2021
this appears to be an outdated driver:
RTKVHD64.sys Tue Aug 9 03:15:32 2022
SteamStreamingMicrophone.sys Fri Jul 28 08:33:15 2017
017 (597B593B)
SteamStreamingSpeakers.sys Thu Jul 20 17:56:15 2017
TbtBusDrv.sys Mon Jun 27 03:36:05 2022
the bug I found was in the nvidia driver; it took too long to respond to a power request. I’d just update the other intel chipset drivers and re-test.
note: when examining the Dell driver, make sure to select expand all drivers and on the second page you’ll see the additional intel drivers for intel HID, Intel Rapid Storage Driver, and Intel sensor drivers.
I'm not completely certain what it was, but it seems like it might have been resolved. I downloaded the drivers you recommended and also installed whatever else I could find. There were three updates from Windows Update that I applied:
1) Intel Corporation - Extension 27.20.100.9664
2) Intel Corporation - Extension 27.20.100.9168
3) Intel Corporation - Extension 31.0.101.2127
Now my system feels stable again. I played a game to check for stuttering and confirmed the GPU is working properly—everything looks good!
Thanks a lot for your help. I was close to giving up, but you reassured me. People on other threads suggested it might be a hardware problem because the DDU in the NVIDIA drivers didn’t work.
Feel free to ignore my request, but if it’s not too much trouble, could you point me toward some resources for diagnosing these kinds of issues? Did you review the crash reports? What did you think when you were troubleshooting?
I’m really pleased to hear everything is running smoothly now! It seems those updates and drivers have resolved the problem, and it’s impressive that you went through the effort to address all aspects.
When it comes to figuring out these kinds of problems, I can offer some guidance. My approach typically begins with reviewing crash reports or event logs (in Windows, you can use the Event Viewer). These often point to specific issues, such as a faulty driver or hardware part.
I also focus on isolating potential causes by testing one thing at a time. For instance, if DDU wasn’t working, I’d move on to other drivers or even check BIOS/firmware updates. It’s also wise to look for Windows updates regularly, as they sometimes include compatibility fixes.
Discussions in forums and support threads can be useful, but keep in mind that advice should be considered carefully—like the assumption about hardware in your situation. It’s great you tried various software solutions before giving up.
If you’d like more detailed help, there are excellent resources available, such as Tom’s Hardware forums, Reddit’s r/techsupport, and YouTube tutorials.
Let me know if you need more targeted suggestions.