Windows 10 Loading Crash -
SugarD-x - 02.06.2015
There seems to be an issue with SA:MP 0.3.7 crashing in Windows 10 builds. Obviously these are not yet released, however the operating system is due to be out July 29th, so I figured I would bring this up now since others have also mentioned the issue to me.
Requested Information:
1) SA-MP version: 0.3.7
2) Windows version: Windows 10 Insider Preview, Build 10130 (Latest public build. Previous builds are also affected)
3) Video card type: Nvidia 8800GT
4) IP:Port (if any) of the server you are trying to play on: 46.105.234.125:7777
5) If you are crashing, paste the crash report in your post and say when the crash occurs:
Code:
SA-MP 0.3.7
Exception At Address: 0x005B8E75
Base: 0x044C0000
Registers:
EAX: 0x0FC41284 EBX: 0x00000000 ECX: 0x0EDB4800 EDX: 0x00000000
ESI: 0xFFFFFFFF EDI: 0x58472DA0 EBP: 0x00000000 ESP: 0x0029FD10
EFLAGS: 0x00210206
Stack:
+0000: 0xFFFF002B 0x00002EE0 0x00BCE000 0x00000800
+0010: 0x00000000 0x04AA8440 0x00B71848 0x0CB21A38
+0020: 0x0029FF70 0x0083D53B 0xFFFFFFFF 0x005B9282
+0030: 0x00869AF8 0x00869B08 0x00869B20 0x00000000
+0040: 0x00869B30 0x00000001 0x00863B10 0x76F70CE0
+0050: 0x00000000 0x58472DA0 0x41544144 0x50414D5C
+0060: 0x4E4F5A2E 0x00880020 0xFFFFFFFF 0x0082421E
+0070: 0x0082423B 0x00001800 0x00824266 0x00001800
+0080: 0x00000000 0x008211B7 0x00001800 0x49742400
+0090: 0x005B3206 0x00001800 0x0053BCA0 0x00863B10
+00A0: 0x00863A90 0x00863B10 0x0000000A 0x0053E593
+00B0: 0x00863B10 0x00748D00 0x750B95C0 0x00000000
+00C0: 0x0029FF80 0x7FFDE000 0x016C0000 0x00000008
+00D0: 0x016C39C0 0x00000008 0x00000100 0x00000008
+00E0: 0x00000102 0x44520000 0x44034000 0x00000000
+00F0: 0x00000000 0x00000690 0x0000041A 0x00000000
+0100: 0x0029FE4C 0x00080E76 0x00000200 0x00000000
+0110: 0x0210037C 0x04605D6A 0x0000037C 0x00000210
+0120: 0x0000002C 0x0029FE24 0x00825EA4 0x77AE56F7
+0130: 0x00825EA4 0x00000000 0x7FFDE000 0x00821D17
+0140: 0x00835342 0xA3DACA4E 0x0029FF80 0x008246F1
+0150: 0x00400000 0x00000000 0x017E2ABD 0x0000000A
+0160: 0x00000094 0x00000006 0x00000002 0x000023F0
+0170: 0x00000002 0x00000000 0x00000000 0x00000000
+0180: 0x00000000 0x00000000 0x00000000 0x00000000
+0190: 0x00000000 0x00000000 0x00000000 0x00000000
+01A0: 0x00000000 0x00000000 0x00000000 0x00000000
+01B0: 0x00000000 0x00000000 0x00000000 0x00000000
+01C0: 0x00000000 0x00000000 0x00000000 0x00000000
+01D0: 0x00000000 0x00000000 0x00000000 0x00000000
+01E0: 0x00000000 0x00000000 0x00000000 0x00000000
+01F0: 0x00824588 0x00824570 0x00824570 0x7FFDE000
+0200: 0xC0000005 0x00000000 0x017E2ABD 0x00000044
+0210: 0x017F94E8 0x017E8890 0x017F7678 0x00000000
+0220: 0x00000000 0x00000000 0x00000000 0x00000000
+0230: 0x00000000 0x00000000 0x00000000 0x00000000
+0240: 0x00000000 0xFFFFFFFF 0xFFFFFFFF 0xFFFFFFFF
+0250: 0x00000000 0x00000000 0x0029FE70 0x0029F8CC
+0260: 0x0029FFCC 0x00825EA4 0x00888078 0x00000000
+0270: 0x0029FF94 0x750B3224 0x7FFDE000 0x750B3200
SCM Op: 0x0, lDbg: 0 LastRendObj: 0
Game Version: US 1.0
6) If you are crashing loading SA-MP, please say whether GTA:SA single player works (test it): Single-player loads fine. SA:MP crashes about half-way into loading after displaying the splash/loading screen.
7) Do you have any other GTA:SA mods installed? e.g. new vehicles: None.
It is also worth noting that the issue is completely consistent every time. Compatibility and "Run As Administrator" settings do not resolve the issue, just as Windows' own compatibility troubleshooter doesn't. I have since reported the issue to Microsoft using their application crash reporter and Windows Feedback systems, however I figured I'd pass this along here too.
As added information, Windows 10 had to activate/install the DirectPlay feature before the game would launch. From what I've read, this is the version seen in Windows 8.1 and earlier, but I cannot confirm this to be correct. (I'm not sure if this is related to the crash or not).
This particular installation also worked fine in Windows 8.1 and earlier, however other users have stated that their fresh installations into Windows 10 itself were not working either. Earlier versions of SA:MP are also likely affected.
Re: Windows 10 Loading Crash -
perfectboy - 04.06.2015
Right click on ur game gta_sa.exe and go to properties and compatiblity tab change it to run in windows 7 mode. Do the same for samp.exe if it works please rep me.
Re: Windows 10 Loading Crash -
SugarD-x - 04.06.2015
That does not work, as previously stated:
Quote:
Originally Posted by SugarD-x
Compatibility and "Run As Administrator" settings do not resolve the issue, just as Windows' own compatibility troubleshooter doesn't.
|
Re: Windows 10 Loading Crash -
SugarD-x - 13.06.2015
I hate to bump this, but has anyone found any solutions yet? This is rendering the multiplayer modification completely unusable on Windows 10, with no workarounds available.
Re: Windows 10 Loading Crash -
Tomboeg - 14.06.2015
You're probably not the only one with this problem.
I myself know no solution, however i believe the SA-MP developer(s) is likely to work on Windows 10 compatibility since everyone is most likely going to upgrade to Windows 10.
Re: Windows 10 Loading Crash -
Alex Magaсa - 14.06.2015
SA-MP client has nothing to do with Windows 10. They are not responsibility for having issues with windows 10.
On Tech: I know you got the Windows 10 Demo(Preview). Some Tech-Computers(Tech-Supporters) said that Windows 10 have alot of bugs cause it's a demo(preview). it's not the final release of Microsoft.
So wait till Microsoft give the whole final package and re-test the game.
Re: Windows 10 Loading Crash -
dugi - 15.06.2015
I've been playing in sa-mp on Windows 10 preview for past 4 months, no issues whatsoever.
Solution posted here
http://forum.ls-rp.com/viewtopic.php...55634#p5742411 seems to work.
Re: Windows 10 Loading Crash -
GWMPT - 17.06.2015
Quote:
Originally Posted by Alex Magaсa
SA-MP client has nothing to do with Windows 10. They are not responsibility for having issues with windows 10.
|
If the GTA SA single player DOES NOT CRASH, that means the modification(in this case, SA:MP) is injecting code to GTA SA which doesn't work, so SA:MP has everything to do with the crash on the windows 10 OS.
Anyways, Windows 10 is still being done, let's wait for the final release, and hopefully the crashes being caused actually will be resolved.
If not, what Kalcor has to do is to build SA:MP client for windows 10, simple as that.
Re: Windows 10 Loading Crash -
J0sh... - 17.06.2015
Quote:
Originally Posted by GWMPT
If the GTA SA single player DOES NOT CRASH, that means the modification(in this case, SA:MP) is injecting code to GTA SA which doesn't work, so SA:MP has everything to do with the crash on the windows 10 OS.
Anyways, Windows 10 is still being done, let's wait for the final release, and hopefully the crashes being caused actually will be resolved.
If not, what Kalcor has to do is to build SA:MP client for windows 10, simple as that.
|
I think Jay has been using windows 10 since it reached public testing. He's having no trouble.
Re: Windows 10 Loading Crash -
SugarD-x - 27.06.2015
Quote:
Originally Posted by Jamester
I think Jay has been using windows 10 since it reached public testing. He's having no trouble.
|
He may have gotten lucky and had something from an older version carried over, (which so far seems to be a recurring issue in some of the builds). I can say that as of Build 10130, I still cannot run it. GTA:SA works fine, SA:MP's client loads fine, however when it comes to running GTA:SA with SA:MP's memory changes loaded, still getting the same crash.
Re: Windows 10 Loading Crash -
SugarD-x - 30.06.2015
Sorry to bump this, but the issue is still present in Build 10158.
Re: Windows 10 Loading Crash -
][Noname][ - 30.06.2015
crash on 0x5B8E75
mov NumberOfVehicleTypes, 16h
samp change this parameter
there is nothing to crash lol
Re: Windows 10 Loading Crash -
eider - 30.06.2015
Crashlog you've posted is reffering to function related to
CStreaming. To be more precise it's function responsible for starting streaming engine in GTA. Further analysis let's us see that precise offset crashlog provided is
5B8E75 which is located near
StreamingMemoryLimit stuff.
Please make sure you don't have any memoryfix plugins or mods (mainly .asi) and that your vorbisFile is clean of ASI hooks. This is not in any case problem related to Windows 10 as I was succesfull in running SA-MP in VM with newest build from Windows Insider. It is however caused by changes SA-MP made in 0.3.7 (which is basically implemented memoryfix itself inside SA-MP for everyone to benefit from it, sadly it breaks stuff if user already have 3rdparty memoryfix installed - in that case he needs to remove it first).
Re: Windows 10 Loading Crash -
][Noname][ - 30.06.2015
too many users use memoryfix, but memory fix as I know doesn't change this address
Re: Windows 10 Loading Crash -
SugarD-x - 30.06.2015
It didn't cause this crash in Windows 8.1, however upon removing it, I still receive another crash at about 90% loading. Again, only Windows 10 is affected:
Код:
SA-MP 0.3.7
Exception At Address: 0x0040FB80
Base: 0x04280000
Registers:
EAX: 0x00000EA0 EBX: 0x008D6264 ECX: 0x00000000 EDX: 0x0055B855
ESI: 0x008E48AC EDI: 0x008E48AC EBP: 0x00000000 ESP: 0x0029FC3C
EFLAGS: 0x00210212
Stack:
+0000: 0x0041B207 0x00000030 0x008E48AC 0x00C8E0C8
+0010: 0x00000EA0 0x0FCB0420 0x008E48AC 0x0029FF70
+0020: 0x0083723B 0xFFFFFFFF 0x00808A7A 0x008E48AC
+0030: 0x00000EA0 0x0FCB0420 0x00000040 0x00000000
+0040: 0x008E48AC 0x0FCB0420 0x00000027 0x00000EAC
+0050: 0x00036003 0xFFFFFFFF 0x008241AF 0x0074BB74
+0060: 0x008D6264 0x00000EA0 0x0253F2FA 0x0029FCDC
+0070: 0x008E48AC 0x00B44874 0x00000254 0x00002E01
+0080: 0x00036003 0x00036003 0x00036003 0x0000000C
+0090: 0x00000004 0x0029FCE8 0x00000000 0x00000027
+00A0: 0x0FB2C6A8 0x00000041 0x00B44874 0x00000010
+00B0: 0x00036003 0x00002E90 0x00000027 0x00000000
+00C0: 0x00000000 0x005373AB 0x00000027 0x008E48AC
+00D0: 0x00000254 0x00B44874 0x00002E90 0x0040C814
+00E0: 0x008E48AC 0x00B44874 0x00002E90 0x00000254
+00F0: 0x00000000 0x008E4A60 0x00000000 0x0EAD8800
+0100: 0x00B54800 0x008E7B50 0x0029FF70 0x76498710
+0110: 0x391EE0EF 0xFFFFFFFE 0x0040E2CA 0x0EAD8800
+0120: 0xFFFFFFFF 0x00000000 0x0000000A 0x00000000
+0130: 0x76C91290 0x00000000 0x00000000 0x000016A9
+0140: 0x0040EAC8 0x00000000 0x00000001 0x00000000
+0150: 0x00863B10 0x005BA263 0x00000000 0x00863A6C
+0160: 0x0086A578 0x00000000 0x0053BCAB 0x00863B10
+0170: 0x00863B10 0x00863A90 0x00863B10 0x0000000A
+0180: 0x0053E593 0x00863B10 0x00748D00 0x76A19710
+0190: 0x00000000 0x0029FF80 0x7FFDE000 0x01600000
+01A0: 0x00000008 0x01603A30 0x00000008 0x00000100
+01B0: 0x00000008 0x00000102 0x44520000 0x44034000
+01C0: 0x00000000 0x00000000 0x00000690 0x0000041A
+01D0: 0x00000000 0x0029FE4C 0x000602B0 0x00000200
+01E0: 0x00000000 0x028F030D 0x00555C5B 0x0000030D
+01F0: 0x0000028F 0x0000002C 0x0029FE24 0x00825EA4
+0200: 0x76467607 0x00825EA4 0x00000000 0x7FFDE000
+0210: 0x00821D17 0x00835342 0x4F78E40F 0x0029FF80
+0220: 0x008246F1 0x00400000 0x00000000 0x01892B95
+0230: 0x0000000A 0x00000094 0x00000006 0x00000002
+0240: 0x000023F0 0x00000002 0x00000000 0x00000000
+0250: 0x00000000 0x00000000 0x00000000 0x00000000
+0260: 0x00000000 0x00000000 0x00000000 0x00000000
+0270: 0x00000000 0x00000000 0x00000000 0x00000000
SCM Op: 0x0, lDbg: 0 LastRendObj: 0
Game Version: US 1.0
Edit: It seems the base address keeps changing every time I attempt to launch it, however the address where the exception occurs is still the same.
Re: Windows 10 Loading Crash -
Matt - 30.06.2015
I tested SA-MP on Windows 10 and it worked completely fine
Re: Windows 10 Loading Crash -
][Noname][ - 30.06.2015
Quote:
Exception At Address: 0x0040FB80
|
this is gta bug, not samp
(byte)0x6F7440=C3 will fix 0x0040FB80 crash but you will warning near train
problem of this - 0xB71670 filenameBuffer is bugged sometimes and caused to clear collision pointer, I don't have idea what is reason
0x006F5636 crash - same
Re: Windows 10 Loading Crash -
SugarD-x - 30.06.2015
Quote:
Originally Posted by SPAWN_METAL
this is gta bug, not samp
(byte)0x6F7440=C3 will fix 0x0040FB80 crash but you will warning near train
problem of this - 0xB71670 filenameBuffer is bugged sometimes and caused to clear collision pointer, I don't have idea what is reason
0x006F5636 crash - same
|
This is happens when the game is loaded around 90% through SA:MP. GTA:SA works fine.
Re: Windows 10 Loading Crash -
Konverse - 30.06.2015
Does the GTA-SA and SA-MP are compatible with windows 10 yet? just asking because I tried it also but it crashed for no reason at all.
Re: Windows 10 Loading Crash -
SugarD-x - 30.06.2015
Quote:
Originally Posted by Konverse
Does the GTA-SA and SA-MP are compatible with windows 10 yet? just asking because I tried it also but it crashed for no reason at all.
|
GTA:SA itself should be fine. Are you getting the same crashes I described?