Osingen71 Posted Tuesday at 02:43 PM Share Posted Tuesday at 02:43 PM I keep getting whitescreen and crashes non stop. Few things I notice is that most of time the ram usageis raising, and the cpu is going to 44% at vortex usage and it crashes. It started 17th of january, and it messed up my game so it was unplayable. I have a 2nd comp where I have identical setup, and backups of all files and folders with various dates. But no matter what back up I replace it with, I will get the train of unlimited loop of crashes. I replaced most of my computer except my gpu and cpu - did a clean install, and the crashes keep on going. I can use it on my 2nd computer with no problems. The main difference between the two computers is that the 2nd has a slower gen3 nvme and a xeon cpu. The system it crashes repeteadly on is a i9-14900k on a asus dark hero z790 mb, samsung 990 pro nvme disks - wich has high end speed... I did check file systems - and no errors, I did reinstall runtime for vortex - but to no help. I tried block it in firewall, was few lesser crashes at startup - i excluded it from AV, but no difference. Vortex starts with crashing just by launching it, all from 1-10 times, and hitting deploy its a new loop of crashes, even just by dragging files over to it - it started crashing. Vortex worked perfectly fine by me until january 14 to 17 ( did not launch it between thoose days). I dont see how and why it should crash, but the only thing im leaning on is that it dont like the fast disks - unless its something it dont like with the cpu, as rest is new. I can use the other computer to mod the game - then copy it over, and play the game - but thats a time wasting operation 800gb's is slow to copy on external then onto this comp. Network is way slower.... dont have 10g. So for every changes I wanna make, i have to do it on 2nd comp then do the copy over process.... I would really like to find a way to make vortex work again on my main computer. I cancled my subscription as it is until this is solved. Link to comment Share on other sites More sharing options...
ChemBoy1 Posted Tuesday at 04:36 PM Share Posted Tuesday at 04:36 PM Your CPU is almost certainly the problem. Not sure if you read the news, but your 14900k is likely extremely unstable. That's why you have trouble on that specific machine. It's possible 24H2 has made this instability worse somehow. Don't blame Nexus for your hardware problems. Link to comment Share on other sites More sharing options...
Osingen71 Posted Tuesday at 09:18 PM Author Share Posted Tuesday at 09:18 PM (edited) 4 hours ago, ChemBoy1 said: Your CPU is almost certainly the problem. Not sure if you read the news, but your 14900k is likely extremely unstable. That's why you have trouble on that specific machine. It's possible 24H2 has made this instability worse somehow. Don't blame Nexus for your hardware problems. If you keep updated on cpu's - the microcode is fixed for all 13th and 14th gen - just need to update the MB Bios .... Beside, it has worked for me since I installed it about a year ago with no problems.... so i doubtfully think that. I even had a backup I played from end of july - but reverting to that also keeps getting crashes. So - after swapping out most of my computer, the only thing is left is MS updates... and they did some updates 14th and 17th of january - when my problems started. But as it is, the program is crashing just by starting it...sometimes with 10 times in a row... So if you are an official support member, and your response is it is a HW problem - dont blaim nexus, thats a very unfriendly and fast answer. Edited Tuesday at 09:36 PM by Osingen71 Link to comment Share on other sites More sharing options...
vortexposer Posted Tuesday at 11:20 PM Share Posted Tuesday at 11:20 PM (edited) Had similar issues a while back and it ended up being a non-typical .NET error - which redownloading off of official Vortex page enabled me to fix/repair. How you tried that? I had to reinstall and then boot again for it to display the repair option - https://www.nexusmods.com/site/mods/1 Edited Tuesday at 11:22 PM by vortexposer Link to comment Share on other sites More sharing options...
ChemBoy1 Posted Wednesday at 04:48 AM Share Posted Wednesday at 04:48 AM Don't bother vortexposer. It couldn't possibly be an issue with the user's system configuration. Simply impossible. Link to comment Share on other sites More sharing options...
Osingen71 Posted Wednesday at 04:50 PM Author Share Posted Wednesday at 04:50 PM I dont see why you are so hostile? Is it a problem that we seek solutions here? And your answer @ChemBoy1 are quite rude - instead of seeking a solution of try finding a problem, you are pointing fingers and harassing. But - for to try to dig into the problem. I got my event viewer full of yellow and red flags, pointing to .NET and blocking access to Win32k.sys from Vortex. I did try uninstall .Net - reboot and reinstall. I also ran installer over vortex installation. I also have a lot of yellow flags from Vortex trying to access Win32k.sys - as is a module for windows managing. I did install the runtime as is linked to on the web with vortex, but it still crashes like pearls in a neckless... Link to comment Share on other sites More sharing options...
vortexposer Posted Wednesday at 10:24 PM Share Posted Wednesday at 10:24 PM (edited) Is your other PC using a similar custom install path for Vortex? .NET seems to have an issue finding or accessing E:\\ModInstallerIPC.exe Edited Wednesday at 10:32 PM by vortexposer Link to comment Share on other sites More sharing options...
7531Leonidas Posted Wednesday at 10:52 PM Share Posted Wednesday at 10:52 PM Isn't there some kind of file path character length limit? I am not sure that this one is too long, but might be useful to check... Link to comment Share on other sites More sharing options...
vortexposer Posted Wednesday at 11:00 PM Share Posted Wednesday at 11:00 PM Yeah, or possibly the path beginning in a root subfolder. Might not matter but my custom install path is C:\Vortex\\ vs C:\<folder>\Vortex\\ Link to comment Share on other sites More sharing options...
Osingen71 Posted 21 hours ago Author Share Posted 21 hours ago 10 hours ago, vortexposer said: Is your other PC using a similar custom install path for Vortex? .NET seems to have an issue finding or accessing E:\\ModInstallerIPC.exe Both computers have the same path - thats the reason I can back up the folders and copy them between, vortex just checks all files when starting program after a restore/copy of all files (appdata+gamefiles). 10 hours ago, 7531Leonidas said: Isn't there some kind of file path character length limit? I am not sure that this one is too long, but might be useful to check... I had no warnings of copy the whole folder from root of E drive with explorer, so the limit is withing 255 still. Not sure if I can change the path after game is modded without messing it up. Regarding .NET - This is a ASUS Motherborad and its using aura creator - and that is running with no problems, both needing .Net 6.x I did scan system files, gonna try DISM commands and see if its a dismatch in Health records as I suspect its something with winupdt that messed it up. But put in a nutshell - if I sandbox .Net, vortex should work with no problems. And just for to be on safe side, I did a extended test on the cpu with Intel Processor Diagnostic Tool 64bit (refering to 1st answer) - and it was no problems at all. Im also gonna try it on a 2.5 ssd disk I have, that is unused... can never harm to have extra storage - and also to test if it has something to do with fast nvme disks. I had 2 crashes yesterday where it crashed on a javascript inside it - not sure if that matters at all. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now