Risuban

This is the kind of worse case scenario this bug can imply, since I'm guessing you have only 1 disk, I was lucky to have more than one and have wf installed in a different one from the OS

I get it but then again the disk where warframe is installed is my better quality disk out of all 4 of them, and the fact that this update is really buggy still and the fact that immediately after the crash my disk was no longer appearing in the disk manager, but was detected by bios and somehow it changed its own boot order. I ran a few diagnosis and the disk is healthy logically speaking and the PCB (of both MOBO and M.2 drive) is clean as new, no signs of a short circuit, damaged components or burn marks. It maybe have just been a case of Windows being Windows -I'm running windows 11- but then again, I have never encountered something like this before and the fact that I was able to fix the issue does not mean someone who's less technologically inclined than me can fix it, they'll probably get a bad scare or think their PCs are bricked. What I'm trying to say is that it probably wasn't a matter of warframe taking control over something it should have control over, but the fact that this CAN happen may indicate that something warframe is doing or how it's handle of memory allocations changed in this update may cause this.

Well, the title pretty much sums it up, i was farming in freeroam duviri for a whole hour, got a lot of decrees and i think it was too much for the game to handle so it crashed, which lead to one of my drives not being registered by my os and i had to change the boot order in my bios (had to go through a lot of troubleshooting before realizing that was the problem, even had to reinstall the game). I´d like something for the inconvenients I went through. Hopefully this was an isolated incident and other people don't have to go through what i went through.