Technical Support (Path of Exile 1) - Bug Check (BSOD) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) - Forum

After implementing new memory manager for Vulkan renderer I've cought several STOP screens (BSODs) with this info https://pastebin.com/4znQWYa8 In short, info from the mini dump analyzed by WinDbg " 7: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff880103ae4bd, fffff88006a94938, fffff88006a94190} Probably caused by : nvlddmkm.sys ( nvlddmkm+d154bd ) ... SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) ... BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff880103ae4bd BUGCHECK_P3: fffff88006a94938 BUGCHECK_P4: fffff88006a94190 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nvlddmkm+d154bd fffff880`103ae4bd 488b01 mov rax,qword ptr [rcx] EXCEPTION_RECORD: fffff88006a94938 -- (.exr 0xfffff88006a94938) ExceptionAddress: fffff880103ae4bd (nvlddmkm+0x0000000000d154bd) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000000 Attempt to read from address 0000000000000000 CONTEXT: fffff88006a94190 -- (.cxr 0xfffff88006a94190) rax=fffffa8011a78000 rbx=fffffa8016025160 rcx=0000000000000000 rdx=000000000000006d rsi=0000000000000000 rdi=0000000000000001 rip=fffff880103ae4bd rsp=fffff88006a94b70 rbp=fffff88006a94c51 r8=fffff88006a94c30 r9=fffff88006a94be0 r10=0000000000000000 r11=fffff88003789180 r12=000000000fa00000 r13=fffffa80146f4240 r14=000000000000006d r15=0000000000000000 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010206 nvlddmkm+0xd154bd: fffff880`103ae4bd 488b01 mov rax,qword ptr [rcx] ds:002b:00000000`00000000=???????????????? nvlddmkm.sys is a kernel mode service of NVIDIA driver package NVIDIA driver pack is 466.27-desktop-win8-win7-64bit-international-whql.exe OS: Win 7 x64 Professional NVIDIA GeForce 970 GTX I am updating right now to 466.47 driver version and I hope NVIDIA fixed it but I think you have to be aware of this BSOD because it's probably directly related to your implementation of new memory manager. Last bumped on Jun 3, 2021, 6:08:44 PM	Posted by cursorTarget#1174 on May 30, 2021, 12:04:36 AM Quote this Post
The problem persists in the NVIDIA driver 466.47. Bug Check appeared after 3-4 hours of playing when I entered the map and first mobs were drawn on the screen. " SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff880103c84e5, The address that the exception occurred at Arg3: fffff88008e05968, Exception Record Address Arg4: fffff88008e051c0, Context Record Address " EXCEPTION_RECORD: fffff88008e05968 -- (.exr 0xfffff88008e05968) ExceptionAddress: fffff880103c84e5 (nvlddmkm+0x0000000000d184e5) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000000 Attempt to read from address 0000000000000000 " EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nvlddmkm+d184e5 fffff880`103c84e5 488b01 mov rax,qword ptr [rcx] Same module, the same instruction (same OPCODE) and the same offset nvlddmkm+d184e5. I have switched to D3D because it's very critical for me to keep the game stable because I play only Hardcore. Prior to patch 3.14.2 the game was stable. Moreover i had only 2 crashes (non-BSODs) from the league start playing 8-12 hours every day (lol). I know GGG it is not your direct fault but mostly NVIDIA's because you're not responsive for the BSOD's caused by the kernel mode services even if your user-mode code has some issues. But at least we could have workaround for it? I guess I have to report to NVIDIA. Last edited by cursorTarget#1174 on Jun 1, 2021, 1:37:59 AM	Posted by cursorTarget#1174 on Jun 1, 2021, 1:36:39 AM Quote this Post
After playing two days in Direct3D mode I didn't get a single Bug Check screen. I even tried to cause BSOD manually by dragging Delve Map quickly from left to right and vice versa. In Vulkan it causes the BSOD with very high probability after 4-7 hours of playing. D3D was ok. It causes the freezes but at least stable. I still want to play Vulkan because the framrate is significantly higher in the dense and it causes way less freezes (lag spikes) than D3D. I'm gonna report to NVIDIA right now and asking you to help with fixing their driver by communicating their Dev Support (I believe you communicate them in some way). One of the streamer (arenammorpg) had the same issue on completely different configuration (Win 10 based). Reported to NVIDIA https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/456089/bug-check-screen-while-playing-path-of-exile/ Last edited by cursorTarget#1174 on Jun 3, 2021, 5:03:06 PM	Posted by cursorTarget#1174 on Jun 3, 2021, 4:21:58 PM Quote this Post
Make sure you did a full clean install of your nvidia Driver with a Software called "DDU" (Displaydriver Uninstaller by Wagnardsoft) in safemode. also run a " DISM.exe /Online /Cleanup-image /Restorehealth followed by a " sfc /scannow https://docs.microsoft.com/en-us/windows/client-management/troubleshoot-stop-errors Last edited by Zonk88#1202 on Jun 3, 2021, 4:43:06 PM	Posted by Zonk88#1202 on Jun 3, 2021, 4:38:36 PM Quote this Post
" /Restorehealth Is not available for my OS. Windows 7 x64 Build 7601. sfc /scannow didn't find any integrity violations. Gonna reinstall the driver completely after DDU.	Posted by cursorTarget#1174 on Jun 3, 2021, 5:35:26 PM Quote this Post
you need to run CMD as Admin, DISM got implemented in Vista. It will work in Win7 + just fine tho " DISM.exe /Online /Cleanup-image /Restorehealth Start_CMD_as_Admin Way 1 " Click the Start icon and click in the Search box. Type cmd into the search box. You will see the cmd (Command Prompt) in the search window. Hover the mouse over the cmd program and right-click. Select "Run as administrator". Way 2 " push Winkey+r; type runas /user:Administrator cmd Last edited by Zonk88#1202 on Jun 3, 2021, 5:54:53 PM	Posted by Zonk88#1202 on Jun 3, 2021, 5:53:50 PM Quote this Post
" Zonk88 wrote: you need to run CMD as Admin, DISM got implemented in Vista. It will work in Win7 + just fine tho " DISM.exe /Online /Cleanup-image /Restorehealth Start_CMD_as_Admin Way 1 " Click the Start icon and click in the Search box. Type cmd into the search box. You will see the cmd (Command Prompt) in the search window. Hover the mouse over the cmd program and right-click. Select "Run as administrator". Way 2 " push Winkey+r; type runas /user:Administrator cmd DISM has limited options for Vista and Win 7, they never introduced /Restorehealth for the /Cleanup-image. The only way to use that key is somehow to transfer DISM from Win 8.1 to Win 7 " C:\Windows\System32>dism /Online /Cleanup-image /Restorehealth Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.18489 Error: 87 The restorehealth option is not recognized in this context. For more information, refer to the help. The DISM log file can be found at C:\Windows\Logs\DISM\dism.lo C:\Windows\System32> " C:\Windows\System32>dism /Online /Cleanup-image /? Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.18489 /Cleanup-Image /RevertPendingActions WARNING! This operation will revert pending actions from previous servicing operations. It should be used for recovery operations only. This command is not supported against an online image. Example: DISM.exe /Image:C:\test\offline /Cleanup-Image /RevertPendingActions /Cleanup-Image /spsuperseded [/hidesp] WARNING! The service pack can't be uninstalled after this operation is completed. This operation will remove backup files created during service pack installation. Use /hidesp switch to hide the service pack from Installed Updates. Example: DISM.exe /Image:C:\test\offline /Cleanup-Image /spsuperseded /hidesp /Cleanup-Image /scanhealth Use /ScanHealth to scan the image for component store corruption. Example: DISM.exe /online /Cleanup-Image /scanhealth C:\Windows\System32> Technet " you need to run CMD as Admin PS Current user is already has admin rights. There are no users with "user" rights on this PC, only admins. There is no point to run something with Admin rights when you logged in as Admin. PPS Reinstalled the driver package after using of DDU. Need some time to gather new info regarding the stability. Last edited by cursorTarget#1174 on Jun 3, 2021, 6:19:02 PM	Posted by cursorTarget#1174 on Jun 3, 2021, 6:08:44 PM Quote this Post