Jump to content
Sign in to follow this  
Yapab

Consistent crashing since 58899

Recommended Posts

Hello,

On a friend PC the latest 58899 beta has started to crash consistently within less than 30 minutes of play, however its random.

The crash sequence is like so:

1) Error message about some "mipmap" not found, can click "continue"

2) Shortly after (<1min) the game crashes to desktop, quite quickly and without error.

This happens in COOP Campaign AND in the editor.

Error log from ARMA2 follows:

=====================================================================

D:\ArmA 2\beta\arma2.exe

"D:\ArmA 2\beta\arma2.exe" -nosplash -mod=beta =====================================================================

Exe timestamp: 2009/08/29 16:38:02

Current time: 2009/08/30 16:24:51

graphics: D3D9, Device: NVIDIA GeForce 8800 GT , Driver:nv4_disp.dll 6.14.11.9062

resolution: 1680x1050x32

Addons:

CA_Modules_DynO in ca\modules\dyno\, CAAir2_C130J in ca\air2\c130j\

CAAir2_UH1Y in ca\air2\uh1y\, CA_Animals2_Cow in ca\animals2\cow\

CABuildings2 in ca\buildings2\

CAStructures_IndPipe1_todo_delete in ca\buildings2\ind_pipeline\indpipe1\

Ind_SiloVelke in ca\buildings2\ind_cementworks\ind_silovelke\

Chernarus in ca\chernarus\, CA_Dubbing in ca\dubbing\

CASounds_Missions in ca\soundmissions\

CAStructuresHouse_A_Office02 in ca\structures\house\a_office02\

CAStructures_Proxy_BuildingParts in ca\structures\proxy_buildingparts\

CAStructuresHouse_Church_02 in ca\structures\house\church_02\

CAWeapons_2b14_82mm_Mortar in ca\weapons\podnos_2b14_82mm\

CAWheeled2_HMMWV_BASE in ca\wheeled2\hmmwv\

CA_Missions_SecOps in ca\missions\som\

CA_Missions_FirstAidSystem in ca\modules\fa\, CA_Modules_ZoRA in ca\modules\zora\

CA_AIR2_Su25 in ca\air2\su25\, CABuildingParts in ca\buildings2\buildingparts\

pond_test in ca\structures\pond\

CAStructuresLand_Nav_Boathouse in ca\structures\nav_boathouse\

CAStructuresHouse_Church_03 in ca\structures\house\church_03\

CAStructuresHouse_Church_05R in ca\structures\house\church_05r\

CAWater2_LHD in ca\water2\lhd\, CAWheeled2_GAZ39371 in ca\wheeled2\gaz39371\

CAWheeled2_Ikarus in ca\wheeled2\ikarus\

CA_Missions_BattlefieldClearance in ca\modules\bc\

CA_Missions_GarbageCollector in ca\modules\garbage_collector\

CA_Modules_Marta in ca\modules\marta\

CAHouseBlock_A in ca\buildings2\houseblocks\houseblock_a\

Ind_Pec in ca\buildings2\ind_cementworks\ind_pec\

CAStructuresHouse_A_FuelStation in ca\structures\house\a_fuelstation\

CAStructures_Rail in ca\structures\rail\

CAStructuresHouse_A_Hospital in ca\structures\house\a_hospital\

CAWeapons_AmmoBoxes in ca\weapons\ammoboxes\

CAWeapons2_HuntingRifle in ca\weapons2\huntingrifle\

CAWheeled_Pickup in ca\wheeled\datsun_armed\

CAWheeled2_M998A2_Avenger in ca\wheeled2\hmmwv\m998a2_avenger\

CAWheeled2_MTVR in ca\wheeled2\mtvr\

CA_Animals2_Dogs_Pastor in ca\animals2\dogs\pastor\

CAHouseBlock_B in ca\buildings2\houseblocks\houseblock_b\

Farm_WTower in ca\buildings2\farm_wtower\, CARoads2Dam in ca\roads2\dam\

CASounds in ca\sounds\, CAStructures_Proxy_Ruins in ca\structures\proxy_ruins\

CAStructures_Mil in ca\structures\mil\

CAStructuresHouse_HouseV2 in ca\structures\house\housev2\

CAStructuresHouse_Shed_Ind in ca\structures\shed_ind\

Ind_SawMill in ca\structures\ind_sawmill\

CAStructuresLand_Ind_Stack_Big in ca\structures\ind\

CATracked2_T90 in ca\tracked2\t90\, CAWeapons_SPG9 in ca\weapons\spg9\

CAWeapons_VSS_vintorez in ca\weapons\vss_vintorez\

CAWeapons_ZU23 in ca\weapons\zu23\

CAWeapons_Metis_AT_13 in ca\weapons\metis_at_13\

CAWeapons_bizon in ca\weapons\bizon\

CAWeapons_Warfare_weapons in ca\weapons\static\

CAWheeled2_LADA in ca\wheeled2\lada\, CAWheeled2_BTR90 in ca\wheeled2\btr90\

CA_Modules_Coin in ca\modules\coin\, CA_Animals2_Rabbit in ca\animals2\rabbit\

CA_Animals2_Anim_Config in ca\animals2\animconfig\

Rail_House_01 in ca\buildings2\rail_house_01\

CAHouseBlock_C in ca\buildings2\houseblocks\houseblock_c\

Ind_Workshop01 in ca\buildings2\ind_workshop01\, CACharacters2 in ca\characters2\

CARoads2Bridge in ca\roads2\bridge\, CASigns2 in ca\signs2\

CAStructures_A_BuildingWIP in ca\structures\a_buildingwip\

CAStructuresLand_A_MunicipalOffice in ca\structures\a_municipaloffice\

CAStructures_Castle in ca\structures\castle\

CATracked2_2S6M_Tunguska in ca\tracked2\2s6m_tunguska\

CATracked2_T34 in ca\tracked2\t34\, CAWater2_Fregata in ca\water2\fregata\

CAWheeled in ca\wheeled\, CA_Missions_Armory2 in ca\missions\armory\

CA_Missions in ca\missions\, Arma2_Ka52 in ca\air2\ka52\

CAAir2_ChukarTarget in ca\air2\chukar\

CAHouseBlock_D in ca\buildings2\houseblocks\houseblock_d\

Barn_Metal in ca\buildings2\barn_metal\

CAStructures_IndPipe1 in ca\structures\ind_pipeline\indpipe1\

CAStructuresHouse_a_stationhouse in ca\structures\house\a_stationhouse\

CAStructuresInd_Quarry in ca\structures\ind_quarry\

CAweapons_m107 in ca\weapons\m107\, CAWeapons_M1014 in ca\weapons\m1014\

CAWheeled2_LAV25 in ca\wheeled2\lav25\, CAWheeled2_Kamaz in ca\wheeled2\kamaz\

CAWheeled3_TT650 in ca\wheeled3\tt650\

CALanguage_missions in ca\languagemissions\, BI_SRRS in ca\modules\srrs\

CA_Modules_UAV in ca\modules\uav\

CA_Missions_AlternativeInjurySimulation in ca\modules\ais\, CAAir in ca\air\

HALO_Test in ca\air2\halo\, CA_Anims in ca\anims\

Ind_Tank in ca\buildings2\ind_tank\, Farm_Cowshed in ca\buildings2\farm_cowshed\

Shed_wooden in ca\buildings2\shed_wooden\

ind_silomale in ca\buildings2\ind_cementworks\ind_silomale\

Ind_Dopravnik in ca\buildings2\ind_cementworks\ind_dopravnik\

CA_Heads in ca\characters\heads\

CAStructuresHouse_rail_station_big in ca\structures\rail\rail_station_big\

CAStructures in ca\structures\, CATracked2_BMP3 in ca\tracked2\bmp3\

Warfare2 in ca\warfare2\, CAWater2_seafox in ca\water2\seafox\

CAWheeled2_VWGolf in ca\wheeled2\vwgolf\, CAWheeled2_MMT in ca\wheeled2\mmt\

CA_Missions_Templates_SecOps in ca\missions\templates\secops.west\

CA_Modules_Silvie in ca\modules\silvie\, CAUI in ca\ui\, CAAnimals in ca\animals\

CA_Animals2_Dogs_Fin in ca\animals2\dogs\fin\

Misc_WaterStation in ca\buildings2\misc_waterstation\

CATEC in ca\buildings2\buildingparts\signs\tec\

A_GeneralStore_01 in ca\buildings2\a_generalstore_01\, CA_Editor in ca\editor\

CARocks2 in ca\rocks2\, CAStructuresShed_Small in ca\structures\shed\shed_small\

CAStructuresHouse_HouseBT in ca\structures\house\housebt\, Utes in ca\utes\

CAWeapons in ca\weapons\, CAWeapons2 in ca\weapons2\, CAAir2 in ca\air2\

CAAir3_Su34 in ca\air3\su34\, CA_Anims_Wmn in ca\anims\characters\config\wmn\

A_Crane_02 in ca\buildings2\a_crane_02\

CABuildings2_Misc_Cargo in ca\buildings2\misc_cargo\

CACharacters in ca\characters\

CAStructuresHouse_HouseV in ca\structures\house\housev\, CAFonts in ca\uifonts\

CAWheeled2_V3S in ca\wheeled2\v3s\, CAWheeled3_M1030 in ca\wheeled3\m1030\

CA_Modules_clouds in ca\modules\clouds\, CA_Modules_Alice in ca\modules\alice\

CA_Modules_Animals in ca\modules\animals\, CAAir2_MV22 in ca\air2\mv22\

CAAir3 in ca\air3\, CA_Animals2_Chicken in ca\animals2\birds\chicken\

CA_Animals2 in ca\animals2\, CA_Anims_Sdr in ca\anims\characters\config\sdr\

Misc_PowerStation in ca\buildings2\misc_powerstation\

CABuildingParts_Signs in ca\buildings2\buildingparts\signs\

IndPipe2 in ca\buildings2\ind_pipeline\indpipe2\

Ind_Expedice in ca\buildings2\ind_cementworks\ind_expedice\

Ind_Vysypka in ca\buildings2\ind_cementworks\ind_vysypka\, CAMisc in ca\misc\

CAWheeled_Offroad in ca\wheeled\hilux_armed\, CALanguage in ca\language\

CA_Modules_ARTY in ca\modules\arty\, CAAir2_F35B in ca\air2\f35b\

CAAir2_Pchela1T in ca\air2\pchela1t\, CA_Animals2_Sheep in ca\animals2\sheep\

CA_Animals2_Dogs in ca\animals2\dogs\, Ind_Garage01 in ca\buildings2\ind_garage01\

CAData in ca\, CA_Dubbing_Counterattack in ca\dubbing\counterattack\

CARoads2 in ca\roads2\, A_TVTower in ca\structures\a_tvtower\

CAStructuresHouse in ca\structures\house\, CAWater in ca\water\

CAWater2_Destroyer in ca\water2\destroyer\, CAWater2 in ca\water2\

CAWeapons2_SMAW in ca\weapons2\smaw\

CA_Modules_Functions in ca\modules\functions\

CA_Animals2_WildBoar in ca\animals2\wildboar\

CA_Anims_Char in ca\anims\characters\config\

Shed_small in ca\buildings2\shed_small\

CABuildings2_A_Pub in ca\buildings2\a_pub\, WarfareBuildings in ca\misc3\wf\

CAStructuresBarn_W in ca\structures\barn_w\

CAStructures_Wall in ca\structures\wall\

CAStructures_Railway in ca\structures\rail\railway\, CATracked in ca\tracked\

CAWeapons_Saiga12K in ca\weapons\saiga12k\

CAWheeled2_HMMWV_Ambulance in ca\wheeled2\hmmwv\m997a2_ambulance\

CA_HighCommand in ca\modules\hc\, CA_Modules in ca\modules\

CA_Missions_AmbientCombat in ca\modules\ambient_combat\, CAA10 in ca\a10\

CAAir2_MQ9PredatorB in ca\air2\mq9predatorb\, A_statue in ca\buildings2\a_statue\

Ind_Mlyn in ca\buildings2\ind_cementworks\ind_mlyn\

CAData_ParticleEffects in ca\data\particleeffects\, CAMisc2 in ca\misc2\

CAStructures_Nav_pier in ca\structures\nav_pier\

CAStructures_Ruins in ca\structures\ruins\

CATracked2_us_m270mlrs in ca\tracked2\us_m270mlrs\, CATracked2 in ca\tracked2\

CAweapons_ksvk in ca\weapons\ksvk\, CAWeapons2_RPG18 in ca\weapons2\rpg18\

CAWheeled2 in ca\wheeled2\

CAWheeled2_M1114_Armored in ca\wheeled2\hmmwv\m1114_armored\

CAWheeled2_TowingTractor in ca\wheeled2\towingtractor\

CA_HC_Sounds in ca\missions\data\sounds\, Church_01 in ca\buildings2\church_01\

HouseRuins in ca\buildings2\houseruins\, Ind_Shed_01 in ca\buildings2\ind_shed_01\

Ind_MalyKomin in ca\buildings2\ind_cementworks\ind_malykomin\

CAMisc3 in ca\misc3\, CAMusic in ca\music\

CAStructures_Misc_Powerlines in ca\structures\misc_powerlines\

CAStructures_Nav in ca\structures\nav\

CAWater2_fishing_boat in ca\water2\fishing_boat\

CAWeapons_M252_81mm_Mortar in ca\weapons\m252_81mm_mortar\

CAWeapons_Kord in ca\weapons\kord\, CAWeapons_Colt1911 in ca\weapons\colt1911\

CAWheeled3 in ca\wheeled3\, CA_Modules_StratLayer in ca\modules\strat_layer\

CA_CruiseMissile in ca\air2\cruisemissile\, CA_Animals2_Goat in ca\animals2\goat\

CABuildings in ca\buildings\, Ind_Shed_02 in ca\buildings2\ind_shed_02\

CAStructures_A_CraneCon in ca\structures\a_cranecon\

CAStructuresHouse_A_Office01 in ca\structures\house\a_office01\

CATracked2_AAV in ca\tracked2\aav\, CAWater2_smallboat_1 in ca\water2\small_boat\

CAWeapons_DMR in ca\weapons\dmr\, CAWeapons_AK in ca\weapons\ak\

Mods: CA;beta

Distribution: 1465

Exe version: 1.03.58899

Warning Message: No player was selected!

Warning Message: No player was selected!

LZO decompression failed

Unsupported fill format

Warning Message: Cannot load mipmap ca\plants2\clutter\data\c_grasscrooked_ca.paa

Bad DXT2-5 mipmap size

Unsupported fill format

Warning Message: Cannot load mipmap ca\plants2\clutter\data\c_grasscrooked_ca.paa

Bad DXT2-5 mipmap size

Unsupported fill format

Warning Message: Cannot load mipmap ca\structures\house\housev2\data\housev2_04_interier_mc.paa =======================================================

-------------------------------------------------------

Exception code: C00000FD STACK_OVERFLOW at 0057BE33

Share this post


Link to post
Share on other sites

I have a theory but need some more info:

- Which graphics card was used? (specifically need the amount of VRAM)

- What is the VRAM value in the Arma2.cfg?

- What video memory setting was used in the game?

On a side note, please put long error dumps and similar stuff in "spoiler" tags. :)

Share this post


Link to post
Share on other sites
I have a theory but need some more info:

- Which graphics card was used? (specifically need the amount of VRAM)

- What is the VRAM value in the Arma2.cfg?

- What video memory setting was used in the game?

On a side note, please put long error dumps and similar stuff in "spoiler" tags. :)

- 8800GT SLI 1GB

- not sure, its friends PC will have to get this info from him when he is back online

- He used "Very High" setting

I'll use the spoiler tag next time :)

Yapa

Share this post


Link to post
Share on other sites

Also crashing lots still.. though ive had this issue from the very start.

Constant hardlocks of the machine. Generally form 10 to 30mins of play. Only when in SLI mode.

2 x 9800GT cards on a EVGA NForce 790i ultra mobo. 2gig corsair mem. Latest 190.38 drivers.

Game is unplayable in its current state, and i dont see why I should be force to not use SLI when all other games work fine with it.

What other information can i supply to try and get this issue fixed. The crashes are complete system locks so nothing is written to the arma2 rpt files that i can see.

Is there some other log within XP i can check? or some application i can run in the background to try and record exactly what the issue is?

Share this post


Link to post
Share on other sites

Sandzibar, try loading arma 2 with -winxp

Yapab, Try removing the "-mod=beta" from the shorcut. It should still load as long as you load the exe from the beta directory. By using the -mod=beta switch I believe you're attempting to load a mod from a folder called "beta" under the beta directory (IE; D:\arma2\beta\beta\), although I could be wrong but I run without the -mod=beta command and haven't had a problem so it's worth a try.

---------- Post added at 11:06 AM ---------- Previous post was at 11:02 AM ----------

I should add that I believe the CTD was caused by too many errors loading into the stack and windows shut the process down (hence having no error message)

If that doesn't work then it's likely an issue with your game files (or beta file). The errors are basically saying that it either can't find your mipmap (texture) files or that it's compared them and they've been altered in size.

Share this post


Link to post
Share on other sites

Thanks for the reply Bulldogs, I think it is running from the correct directory because the error log points to the Arma2.exe in the Beta folder.

I will be doing further testings at my friends place this weekend as I believe we might have stumbled onto the problem, and I dont think its ARMA2 related but more PC/Hardware related.

Cannot confirm anything yet so will update here on the weekend.

Yapa

Share this post


Link to post
Share on other sites

Yep, it's pointing to the right place but remove the -mod=beta from the end so it just reads "D:\arma2\beta\arma2.exe -nosplash"

Share this post


Link to post
Share on other sites

-mod=beta is required if you want to run the beta patch

Share this post


Link to post
Share on other sites
-mod=beta is required if you want to run the beta patch

Indeed. The beta patch essentially consists of two parts: engine changes in the arma2.exe and data changes in the beta folder. If you load the beta arma2.exe without -mod=beta, some fixes listed in the changelog may not work for you. It could even cause additional problems.

Share this post


Link to post
Share on other sites

Well -winxp doesnt help.. if anything its making the game crash faster for me (though thats merely speculation on my part without enough attempts for decent statistical proof).

Checked XPs Computer Managment > Event Viewer and at the time of the crashes there are always 2 entries. Both refer to the source of the event as 'nv'.

Details on First:

Event ID 14 - Unknown error on CMDre 00000001 00000000 00000000 00000001 00000001

Details on Second:

Event ID 108 - The driver nv4_disp for the display device \Device\Video0 got stuck in an infinite loop. This usually indicates a problem with the device itself or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Fairly sure thats Gfx related. But if arma 2 works ok without SLI... and ALL other games work just fine with SLI.. then doesnt this reaffrim my initial suspicions that its an "arma 2 + SLI = FGHFGfghfghf" issue?

rage.

Edited by sandzibar

Share this post


Link to post
Share on other sites
-mod=beta is required if you want to run the beta patch

Is this really true if you are using the "Launch Arma2 Beta Patch" shortcut that was installed to the main directory by the beta installer? The reason I ask is that I've never had "-mod=beta" in the Beta shortcut and I've never noticed any problems.... yet. I remember using "-mod=beta" for A1 but it slipped my mind until I read kju's post.

Share this post


Link to post
Share on other sites
Is this really true if you are using the "Launch Arma2 Beta Patch" shortcut that was installed to the main directory by the beta installer? The reason I ask is that I've never had "-mod=beta" in the Beta shortcut and I've never noticed any problems.... yet. I remember using "-mod=beta" for A1 but it slipped my mind until I read kju's post.

It's definitely supposed to be there. When I reinstalled the game on a fresh OS I immediately installed the latest beta (at the time) and the shortcut didn't have the -mod=beta added. The most recent beta I've installed did set the shortcut up properly. No idea why it didn't on the first install.

The 'launch beta' shortcut sets the working directory to your main Arma 2 install directory, NOT to the beta\ subdirectory under it. If the WD was set to the beta subdir, the game wouldn't work because 99% of the data would be missing. Thus, -mod=beta is correct: it tells the game to load any addons in ...\arma2\beta\addons, just like you'd expect it would for the beta exe.

Share this post


Link to post
Share on other sites
It's definitely supposed to be there. When I reinstalled the game on a fresh OS I immediately installed the latest beta (at the time) and the shortcut didn't have the -mod=beta added. The most recent beta I've installed did set the shortcut up properly. No idea why it didn't on the first install.

The 'launch beta' shortcut sets the working directory to your main Arma 2 install directory, NOT to the beta\ subdirectory under it. If the WD was set to the beta subdir, the game wouldn't work because 99% of the data would be missing. Thus, -mod=beta is correct: it tells the game to load any addons in ...\arma2\beta\addons, just like you'd expect it would for the beta exe.

Hmmmm. That's quite strange I haven't noticed any problems with any of the beta builds yet with out that in the target line. I added it though just for good measure.

Thanks for the response.

EDIT:

Ahhh I see what happened. I removed it when I pasted the "-mod=" line I used in the v1.03 shortcut. I'm shocked I never had any problems.

Edited by Manzilla

Share this post


Link to post
Share on other sites

Actually now I'm not so sure. This post from the Usage Guidelines thread suggests that the shortcut doesn't include the beta mods folder, only the exe:

If you are using bundled Launch Arma2 Beta Patch.lnk you are essentially playig a hybrid between beta's .exe and the official release's data (config, models, missions).

By using both the .exe and the -beta mod you can try out the tweaks in the data but it can also make your savegames or edited missions unusable for other versions.

I'm not really sure why they wouldn't include the changed data by default - maybe they vary it depending on what they're after feedback on?

Edit: just installed 58946 and the shortcut it creates has -mod=beta, so maybe it was an ommission from earlier beta releases? I'm 99% sure it's supposed to be there, otherwise you wouldn't be testing any changes made to the data.

Edited by some kind of guy

Share this post


Link to post
Share on other sites

Constant hardlocks of the machine. Generally form 10 to 30mins of play. Only when in SLI mode.

Hardlocks are not caused by the game, you need to make sure your hardware is 100% stable (including in SLI mode) before testing a beta patch!

Read this thread for more info http://forums.bistudio.com/showthread.php?t=84156

Share this post


Link to post
Share on other sites

Hmm i have not got any crashes with any of the beta's. Even tested to up the graphics a lot and still i was ok even though i lagged to death.

But i remember before (final's) when i upped the graphics too much i would crash. Beta's works very good for me however on a medium machine.

Share this post


Link to post
Share on other sites

@ Manzilla

The shortcut was fixed in the latest betas.

Share this post


Link to post
Share on other sites

Never used -mod=beta either. I see no difference when i do that and not though?

Applying it anyway to be sure.

Share this post


Link to post
Share on other sites

It is simple. I does not load beta\addons.

Just check whats in there and you see what you miss.

Share this post


Link to post
Share on other sites

Its not that simple - to many. Running the beta shortcut have been enough back in the days, and im guessing a lot of people including myself didnt investigate how it started the game. And the only checks i did was to see that the correct version number was there - wich it was, and i didnt have any problems so i just didnt think about it.

Good to have bright people around to tell us though. :)

Alex

Share this post


Link to post
Share on other sites
Hardlocks are not caused by the game, you need to make sure your hardware is 100% stable (including in SLI mode) before testing a beta patch!

Read this thread for more info http://forums.bistudio.com/showthread.php?t=84156

What does "Event ID 108 - The driver nv4_disp for the display device \Device\Video0 got stuck in an infinite loop." mean with regards to the source of my problems? as thats written to XPs event log at the exact time of each lockup.

Ill look through the thread you suggested. Thanks.

Share this post


Link to post
Share on other sites
What does "Event ID 108 - The driver nv4_disp for the display device \Device\Video0 got stuck in an infinite loop." mean with regards to the source of my problems? as thats written to XPs event log at the exact time of each lockup.

Ill look through the thread you suggested. Thanks.

Thats normally an issue with The GPU hardware or the driver. Its a well known problem with nvidia GPU's and have seen it a few times myself with some of the nvidia boards ive had, a full driver cleanse sorted it for me in most instances but on one board &7600gt) i used rivatuner to change some of the low level behaviour and removed it...but i cant remember what i changed. Type 'nv4_disp infinite loop' in google to be enlightened.

Share this post


Link to post
Share on other sites
Hardlocks are not caused by the game, you need to make sure your hardware is 100% stable (including in SLI mode) before testing a beta patch!

Read this thread for more info http://forums.bistudio.com/showthread.php?t=84156

Thats partially my thread.......I still have Arma 2 being unstable. I can play other games just fine. Bought and tried playing OFP2, but that game isn't worth it. Love Arma 2 just wish it was stable. I have temporarily replaced every component in my PC except for the Processor and Motherboard and Arma 2 still has issues, unless I have a problematic proc or mb, but I don't have the money to try and replace those, couple of hundred for each.

Share this post


Link to post
Share on other sites
Thats partially my thread.......I still have Arma 2 being unstable. I can play other games just fine. Bought and tried playing OFP2, but that game isn't worth it. Love Arma 2 just wish it was stable. I have temporarily replaced every component in my PC except for the Processor and Motherboard and Arma 2 still has issues, unless I have a problematic proc or mb, but I don't have the money to try and replace those, couple of hundred for each.

ArmA II does have issues. It crashes to the desktop, it has various LOD and performance issues. But it doesn't cause your computer to hard lock where the CPU has totally halted, nor will it BSOD. Those would be hardware or driver problems. A game (or any other userland software) is not at a low enough level that it can access hardware directly. It only talks to the videocard/soundcard/etc thru their respective drivers. Drivers, since they need to access the hardware directly, run at the kernel level. (or Ring0) When a driver shits the bed, BSOD. Hard locks on the other hand, in my experience have been hardware related, and they may be triggered by load.

I gave hardware stress testing apps in your thread that can help diagnose your problem. Yes Arma will go tits up and crash to the desktop. It might look all corrupted in game because of its vram issues. But it cannot cause hardware errors! That is a misunderstanding and a big source of FUD.

Share this post


Link to post
Share on other sites

Is it possible for Arma 2 to talk wrong to the video card causing the driver to screw up and cause a BSOD? Thats seems to be the issue.

I have run every benchmark, stress test that I can find and leave it run all night without issues. Only time the crashing is happening is when playing Arma 2. Even overclocked the I have run the stress tests, etc and no issues. Again only when trying to play Arma 2.

Edited by cashxx

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×