FredBell

And here we go again, Exception just happened again, Message is: RenderingPipeline.cpp(186): Error #272032750 "An internal rendering error has occurred and the program will terminate: Device Removed" 01/04/2023 04:20:48 PM Build: 24.3.0.84 Windows 64-bit I seem to get that exception when I leave the camera open for a few minutes and then get back to that view. Here is another code change you could try if you catch the exception at the right place in the code: - catch the exception and do the error reporting discussed in previous message. - kill that camera view - cleanup the state of the graphic card (free memory, etc..) - then reopen a new camera view with the same parameters - this would make it much less troublesome to the user. There would be a delay but that is it. Other piece of info you might find useful. I have this error with both graphic cards, the basic card "Intel UHD 630", and the "NVIDIA GeForce GTX 1050Ti with MaxQ Design". And the frequency of the error is similar, the better graphic card, the GTX 1050 crashes more often than the basic "intel 630". I just don't think it is a card issue, maybe a driver issue perhaps. The GTX 1050 can run games that are for more demanding than a design rendering software will ever be, which is a good thing. I also turned off the rendering for "Show Shadows" reflections, etc... Also did not make a difference thus far. Last piece of info, I find that around 50% of the time, after your software crashes, then windows 11 will also crash within a few minutes, you know "blue screen of death" style. It is pretty brutal. I am guessing here, but it looks like the process did not clean the graphic card state properly. All Home Designer 2022 error log show the following: AppName Home Designer Suite 2022.exe AppVersion 23.4.1.8 ModuleName ucrtbase.dll ModuleVersion 10.0.22621.608 ModuleTimeStamp f5fc15a3 ExceptionCode c0000409 FaultingOffset 000000000007f61e AppPath C:\Program Files\Chief Architect\Home Designer Suite 2022\Home Designer Suite 2022.exe ModulePath C:\WINDOWS\System32\ucrtbase.dll All Home Designer 2023 error log show the following: AppName Home Designer Suite 2023.exe AppVersion 24.3.0.84 ModuleName ucrtbase.dll ModuleVersion 10.0.22621.608 ModuleTimeStamp f5fc15a3 ExceptionCode c0000409 FaultingOffset 000000000007f61e ProcessId 0x56ac ProcessCreationTime 0x1d92061a1e919a4 AppPath C:\Program Files\Chief Architect\Home Designer Suite 2023\Home Designer Suite 2023.exe ModulePath C:\WINDOWS\System32\ucrtbase.dll and rarely the error for 2023 is for module nvoglv64.dll located C:\WINDOWS\System32\DriverStore\FileRepository\nvdm.inf_amd64_727392c7e446e087\nvoglv64.dll Hope this helps, Fred

This issue is still not resolved. I am using 24.3.0.84 on win 11 64bit Having same issue as everyone else. Also only happen when I want to see 3D camera view. Just for CA team benefit, just know this issue happens multiple times a day (around once per hour on average). So when you say you cannot replicate it easily... I am wondering how hard you have really tried... What I can see happen is an exception is raised - by your cpp class, probably due to an error code returned by the driver. I am telling you this because I am software developer myself, and write c++ fat client app all the time, and this crash is your fault 100%, here is why, your code gets the error code return and decide to throw the exception, or you did not catch the exception and handled that exception correctly the way your code is supposed to. When this exception is caught - your code, like all other piece of software in the world, is supposed to take a "stack dump" and send it back to you for further analysis. Add a little popup box asking the user for their permission before sending the error report file and you are good to go. Then you would know what causes the issue and have a good chance of fixing it. This is basic software design knowledge. Come on... Or maybe this is not how the world works in "Coeur d'Alene, ID" which by the way is a really cool name for a town. I have experienced this issue for many weeks now, once you use a complex plan then the issue starts to happen more frequently. I did not know or think about reporting it until now. I just did a google search and found tons of folks complaining which led me here. Now that I know you have this forum, I'll come back here with more info if I find anything useful moving forward. Fred