First of; Hi!
I love the client, absolutely fantastic when playing on the 120hz servers. Feels so smooth. But is there any chance we'll stop having to restart the client each time we want to join a server with higher or lower tickrate? It isn't the most annoying of things. But it can get annoying considering my problem.
I've been experiencing plenty of crashes whilst using the client; in the menu, at startup, when switching to the 60/120hz client, in game and so forth. Is it a Windows 10 stability problem? I've tested all sorts of compatibility modes with no success.
Crashes in total; around 15 to 20.
System specifications (as listed):
Processor; Intel I5-750 2.6ghz (standard clock)
Graphics card; 1x MSI GeForce GTX-970 SSC ACX2.0+ (factory clocked - no SLI)
OS; Windows 10 Pro x64, version 1511, build 10586.36 <--- I've yet to try the client on Windows 7; will do as fast as possible (later today).
RAM; 3x4 GB of Corsair Vengeance DDR3 (1600mhz) ; of which are usable = ~10GB (10147mb)
MOBO; AsRock P55 Deluxe3
PCU; Corsair RM850 (effect=850W)
SSD; 2x Samsung (can't remember if it's the 840 or 850 series, I'll have to check later today) 120GB in RAID (one of which functions as my system drive)
HDD; 2x Western Digital (cannot remember what exact model) 1000GB; 7200rpm.
I didn't think the crashes caused any logs but they did.
I get the exception code of 0x4000001f, which by my experience with Windows is caused by the x86 subsystem. So I guess I reached some sort of a breakpoint. Is there any debugging mode present in the Beta build? The fault offset was 0x00025956.
Faulting application name: vu.exe, version: 188.8.131.52, time stamp: 0x511c9356
Faulting module name: vu.exe, version: 184.108.40.206, time stamp: 0x511c9356
Exception code: 0x4000001f
Fault offset: 0x00025956
Faulting process id: 0xc60
Faulting application start time: 0x01d13e91c9c02198
Faulting application path: D:\Program Files (x86)\Origin Games\Battlefield 3\vu.exe
Faulting module path: D:\Program Files (x86)\Origin Games\Battlefield 3\vu.exe
Report Id: 00ff6ebb-6b77-4f99-bbf1-07adb0b9db60
Faulting package full name:
Faulting package-relative application ID: