Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
PC Drivers & Software
- AMD Community
- Support Forums
- PC Drivers & Software
- Ryzen 5700G BSOD VIDEO_MEMORY_MANAGEMENT_INTERNAL ...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2023
11:29 AM
Ryzen 5700G BSOD VIDEO_MEMORY_MANAGEMENT_INTERNAL when trying machine learning
When trying to run Stable Diffusion via the https://github.com/lshqqytiger/stable-diffusion-webui-directml repository, I get a BSOD once I start the txt2img image generation.
Here are the some issues on Github:
https://github.com/lshqqytiger/stable-diffusion-webui-directml/issues/6
https://github.com/microsoft/DirectML/issues/379
Steps to reproduce (on my PC anyway):
1. Follow installation instructions here: https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Install-and-Run-on-AMD-GPUs
2. Try to generate image.
System: Win 10 Pro 64 bit
Driver: Adrenalin Edition 22.11.2
Details about the crash copied from opening the crash dump in Windbg and doing an analyze and then a .symfix and .reload and another analyze (not sure if I did it right):
Loading Dump File [032223-16359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`29800000 PsLoadedModuleList = 0xfffff803`2a42a310
Debug session time: Wed Mar 22 20:08:34.050 2023 (UTC + 1:00)
System Uptime: 0 days 0:17:04.643
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
......
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for watchdog.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {36, ffffbe88c1c104a0, ffff968c95c44048, ffff968c8430ec10}
*** WARNING: Unable to verify timestamp for dxgmms2.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms2.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : dxgmms2.sys ( dxgmms2+9ba59 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000036, The subtype of the bugcheck:
Arg2: ffffbe88c1c104a0
Arg3: ffff968c95c44048
Arg4: ffff968c8430ec10
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: dxgmms2
FAULTING_MODULE: fffff80329800000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUGCHECK_STR: 0x10e_36
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff80338843ad0 to fffff80329bfa110
STACK_TEXT:
ffff8008`11677978 fffff803`38843ad0 : 00000000`0000010e 00000000`00000036 ffffbe88`c1c104a0 ffff968c`95c44048 : nt+0x3fa110
ffff8008`11677980 00000000`0000010e : 00000000`00000036 ffffbe88`c1c104a0 ffff968c`95c44048 ffff968c`8430ec10 : watchdog+0x3ad0
ffff8008`11677988 00000000`00000036 : ffffbe88`c1c104a0 ffff968c`95c44048 ffff968c`8430ec10 ffff968c`7f5415b0 : 0x10e
ffff8008`11677990 ffffbe88`c1c104a0 : ffff968c`95c44048 ffff968c`8430ec10 ffff968c`7f5415b0 00000000`00000002 : 0x36
ffff8008`11677998 ffff968c`95c44048 : ffff968c`8430ec10 ffff968c`7f5415b0 00000000`00000002 fffff803`5e60ba59 : 0xffffbe88`c1c104a0
ffff8008`116779a0 ffff968c`8430ec10 : ffff968c`7f5415b0 00000000`00000002 fffff803`5e60ba59 fffff803`5e5b43c8 : 0xffff968c`95c44048
ffff8008`116779a8 ffff968c`7f5415b0 : 00000000`00000002 fffff803`5e60ba59 fffff803`5e5b43c8 00000000`00000000 : 0xffff968c`8430ec10
ffff8008`116779b0 00000000`00000002 : fffff803`5e60ba59 fffff803`5e5b43c8 00000000`00000000 ffff968c`8430ec40 : 0xffff968c`7f5415b0
ffff8008`116779b8 fffff803`5e60ba59 : fffff803`5e5b43c8 00000000`00000000 ffff968c`8430ec40 00000000`00000002 : 0x2
ffff8008`116779c0 fffff803`5e5b43c8 : 00000000`00000000 ffff968c`8430ec40 00000000`00000002 00000000`fffff662 : dxgmms2+0x9ba59
ffff8008`116779c8 00000000`00000000 : ffff968c`8430ec40 00000000`00000002 00000000`fffff662 ffffbe88`c15712a0 : dxgmms2+0x443c8
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms2+9ba59
fffff803`5e60ba59 4c8b15a8fcfbff mov r10,qword ptr [dxgmms2+0x5b708 (fffff803`5e5cb708)]
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: dxgmms2+9ba59
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: dxgmms2.sys
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols
FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner
---------
1: kd> .symfix
1: kd> .reload
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
......
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000036, The subtype of the bugcheck:
Arg2: ffffbe88c1c104a0
Arg3: ffff968c95c44048
Arg4: ffff968c8430ec10
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
BUGCHECK_STR: 0x10e_36
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff80338843ad0 to fffff80329bfa110
STACK_TEXT:
ffff8008`11677978 fffff803`38843ad0 : 00000000`0000010e 00000000`00000036 ffffbe88`c1c104a0 ffff968c`95c44048 : nt!KeBugCheckEx
ffff8008`11677980 fffff803`5e60ba59 : fffff803`5e5b43c8 00000000`00000000 ffff968c`8430ec40 00000000`00000002 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff8008`116779c0 fffff803`5e606839 : ffff968c`7f5414e0 ffffbe88`b70d4301 00000000`00000000 00000000`0a0e9501 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x10229
ffff8008`11677ba0 fffff803`29a55485 : ffffbe88`b70d43c0 fffff803`5e606830 ffff968c`7f5414e0 000fe067`b4bbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffff8008`11677bd0 fffff803`29c02d48 : ffffe480`6a300180 ffffbe88`b70d43c0 fffff803`29a55430 00040602`700bf212 : nt!PspSystemThreadStartup+0x55
ffff8008`11677c20 00000000`00000000 : ffff8008`11678000 ffff8008`11671000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80329b99f3e-fffff80329b99f41 4 bytes - nt!MiFreeUltraMapping+32
[ a0 7d fb f6:20 62 c4 88 ]
4 errors : !nt (fffff80329b99f3e-fffff80329b99f41)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_large
FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
Followup: memory_corruption
---------
0 Replies
