Osingen71 Posted 9 hours ago Author Share Posted 9 hours ago Update: I did reinstall my system, just to verify if it was windows that was messing with me - but same problem... did only put in what was needed, drivers, steam, vortex and .net - same problem. I ran updates, and installed my regular programs, - same problem. I swapped my game drive with a normal ssd drive... and after it was finished checking the mod files, i closed and restarted vortex about 10 times, I did add and remove mods deployed and could work with vortex with no problems. So, my 2nd computer got a gen 3 chipset - so it is capped on 3,5 gb read/write, and it works perfect. Read/write speed is around 3gb - running 2 samsung 2gb 970 and 980 pro disks... My main computer has gen 5 chipset, but gen 4 nvme disk drives ( 3 x samsung 990 pro 2gb, 1x WD SN850x 4gb and 1 x WD SX850x 2gb ) - all running at around 6,8gb read/write speed... So - my main conclusion is that something happends within .net and the transfer between vortex, as it either get responce too fast or cus of the fast disk drives it just crashes - and instead of giving a fail and visual msg, it crashes. I searched event viewer for any clues, but it is not much to go on there. I will try and see if I can force one of the drives to go down to gen3 speed - not sure if thats possible. If anyone has any input to me - im happy to try anything. For my system, I did re-run intel cpu diagnostic tool, I did run burnin test on all vital parts for 15 mins, no failure - even temperature on ssd drives didnt go higher than 65 celcius (but they inside asus heat shield). CPU temp was as espected, 76 celcius at high load after 15 min at max stress test. No other failure on system or programs, asus aura creator works flawlessly - as also uses .net 6.x... Link to comment Share on other sites More sharing options...
Osingen71 Posted 9 hours ago Author Share Posted 9 hours ago I just talket to a local developer and he suggested it could be a bug with .net getting responce too quick - so it didnt handle the request in the program. Link to comment Share on other sites More sharing options...
ChemBoy1 Posted 7 hours ago Share Posted 7 hours ago Brother, I use a gen4 SSD on gen5 chipset with similar write speeds. It is not the problem. You are barking up the wrong tree. Link to comment Share on other sites More sharing options...
7531Leonidas Posted 6 hours ago Share Posted 6 hours ago @Osingen71Is your NVME drive formatted as NTFS? Other problems have been caused by non-NTFS drives, just asking. Link to comment Share on other sites More sharing options...
Osingen71 Posted 5 hours ago Author Share Posted 5 hours ago 55 minutes ago, 7531Leonidas said: @Osingen71Is your NVME drive formatted as NTFS? Other problems have been caused by non-NTFS drives, just asking. Yes, I treid them in a raid with 3x the samsungs and single... 1 hour ago, ChemBoy1 said: Brother, I use a gen4 SSD on gen5 chipset with similar write speeds. It is not the problem. You are barking up the wrong tree. Im not sure if im barking the wrong tree, but its the different i got... it works for my computer if i change the disk to the ssd but not to the nvme...But as u as on it - what is your benchmark on your disk drives`? Mine capped all on 6.8-6,9. Im only trying to find a solution, or a reason to why it is so...and reinstalling my system now 5-6 times in 2 weeks only to solve the problem with nexus, i could have reset and used mo2... but I like nexus...is why I try. Link to comment Share on other sites More sharing options...
Osingen71 Posted 5 hours ago Author Share Posted 5 hours ago (edited) According to a scoolmate that is lead programmer in 2K games he says .net is fragile to many things - so it can be different bugs building up. .Net is not built for the next gen speed trasnfer is his words. So im still lending on its something within ms and .net that make it unstable - and it can be that the main script in .net finish after it get respond - so it crashes. He talked programmer language to me, but i didnt understand much.. but mainly he said, if it was a latency and a depend wait recycle responce time - and that script could finish after it had send request and get responce before script finished, it could cause a program error and it would quit insta... But thats programmer language. Edited 5 hours ago by Osingen71 Link to comment Share on other sites More sharing options...
ChemBoy1 Posted 4 hours ago Share Posted 4 hours ago 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