I suggest reasonable actions to take and get called Ignorant, alright then Carl.
I have no idea what you hope to accomplish by minimizing this problem or by arguing with me over this but I’ll bite this one time.
I know how software works, you have no idea what I know or don’t know. Quite frankly that was uncalled for but if you want to take this personally be my guest.
Regarding the set of hardware, thats what our error reports is supposed to establish. There is a clear pattern and its RTX cards and Windows 10.
Also the fact you think I haven’t tried a complete OS reset is quite cute, I’ve done that. It made no difference. Someones even RMA’d their card and got a new one with the same problem. People with Older cards don’t have the less of the problem too.
I’d done a lot of things, i’m just not going to post a huge post every single time. I kind of expect you to not just be a jerk about it and make assumptions.
NVIDIA can get the problem to happen, they’ve already dismissed it as being a software fault. They added it to their list or known problems and took it down after less than a day when they could also get it to occur on competing hardware.
Even though this is the case RTX owners seem to be the main sufferers of it.
IOI should be able to get it to happen on their side as well.
With the exception of the memory overload almost all crashes crashes to desktop with the exact same code: 0x80000003
This is exactly why I said that IOI should have made a better error catcher, in order to get more detailed information I’ve had to run the game with a debugger. For hours. Repeating it again and again.
Here is one such error I got as a result.
(42dc.2d30): Break instruction exception - code 80000003 (first chance)
00000001`411561cd cc int 3
Every crash I’ve had, the function MixOneInNChannels is the reason why. I can reduce how often this happens by disabling all but one audio device but it still happens occassionally. Not every 5 minutes like it did before.
Had you bothered to read my post you’d have understood that I already understand that an error code like 80000003 does not help by itself.
How on earth you expect me to be able to get more specific with debugging this when I don’t have access to the source code is another thing.
I am literally criticising how vauge their error system is and you reply that I don’t know or can’t provide enough information. Nice one sherlock :D. Thats my point. They NEED a better ERROR handler. It couldn’t hurt to log more detailed information could it? We wouldn’t be in this situation if the info wasn’t so limited.
If you can identify the function at fault (and I did at least one) you can alter it and see what happens, hence suggestion number 2. Optional Beta builds.
Never the less if you think catching most errors with a single code 0x80000003 is helpful to debugging I don’t know what to say.
I’m not arguing with you past this point. I really don’t see the point, if you want to white knight IOI go ahead but I don’t see what you get out of it.
End of the day I’m just a consumer of a product and I am well within my right to be disgruntled about it, I paid for a product I cannot even use properly. That is all that matters to me, not this petty arguing over what I know or not.
I honestly couldn’t care less if you think i’m ignorant, you showed plenty of ignorance in the way you addressed me. Good day to you sir