white screen with new patch..

[Krusty]

I've never had this with any other version of AH since I can remember... It has only happened with the new patch 8...

2 sessions in a row.. I'm on for an hour and a half, maybe less than 2 hours. Locks up full white screen ("do you want to report this?" useless box pops up). Both times while transmitting vox, but was using vox before it the entire time, then blammo, I'm at the desktop with a white screen error.

[Krusty]

"Good news, ev'rybody!" </Dr.Nick>

I was rolling film the first time it happened. Film cut off at that point, but still have it. Would that help you (HTC) see anything that might have caused the crash?

[Krusty]

Haven't had time to play again for over a week. Come back and 2x in a row I get white-screened to death, both in mid-sortie, both after an hour/hour-and-half, both when vox was coming through or going out.

I reiterate I have NEVER had white screen errors in AH for probably 3-5 years, and with patch 8 all of a sudden it's all I get.

[lyric1]

Similar issues my self since last patch except my screen locks up & then after many minutes an all black screen. Have to switch the PC off to restart every thing. It happens a few times a week happens while sitting in the tower or in flight.

[AAIbyteu]

Same problem.
Downloaded entire game again, no go. Happens at least twice everytime I'm on. 
The game downloaded a new map, started to go into the arena. bang - WSOD!  (white screen of death)
Never had it until the last 2 patches. 
Posted DXDiag before but have not heard anything.  Getting really frustrating.
I have tried almost everything anyone has posted and still no luck.

[AAIbyteu]

Latest update:
My son talked to Skuzzy about the problem and they looked at my system.  This is what was found:
I am running a GForce 9400 with 1 gig of memory.  To save money GForce used a cheaper 512 M memory chip along with a faster chip.  When the processor calls for a lot of transfer of data and it resides in the slower chip it can't keep up and poof - WSOD.  Some tech savy guys out there may know what this all means but the bottom line is this:
Either turn down the shadow texture size to 512 and it might fix it or get a new card.  He recommend a GForce 9600 with 512 meg memory.  I got one on the way for about 70.00 after rebate from Tigerdirect.  Should have it by tomorrow and will see if it does the trick.  I will post back later.
 

[AAIbyteu]

Sad to say 70.00 bucks down the drain   Put in new card.  First couple of hours I tried it, everything fine.  Next day, after about 1 hour - WSOD!! 
happened twice in the same session, having to re-boot system each time.
So, it's not the video card that is the problem. 
I am running XP prof 64bit edition.  Maybe this? 
Very disappointed

[Krusty]

It's not the shadows because my card has minimal settings. "Detail" off, "detail water" on, no shadows, and bump mapping on.

No rhyme or reason why, almost always when vox is coming thru or going out. I get the repeated stuttering sound loop and then wait forever for it to blank white then give me a windows "report error" dialog.

I wonder if MS ever sends these repots to HTC?

[715]

Just got a B(lack)SOD.  E8400 w 512M Radeon HD4850.  Never got crashes with old version, only with 2.14 and now 2.15.  Got more with previous patches, but did just get one with 2.15.1.  They are very infrequent in either case.

Are the error logs of any use at all?  I suspect not, but:
Event Type:   Error
Event Source:   Application Error
Event Category:   None
Event ID:   1000
Description: Faulting application aceshigh.exe, version 0.0.0.0, faulting module aceshigh.exe, version 0.0.0.0, fault address 0x00010088.

[lyric1]

So far with new patch have not had any more crashes. Prior to this patch it happened a few times a day.

[Krusty]

I haven't been flying as much, often not longer than an hour or so, if I can, so I hadn't run into this too much, but it's still there.

Tried to run scenario practice frame today. Right about the 2 hour 15 minute mark (I checked the clock) I white-screened out when somebody used vox.

WHat's up with this?

Does the game crash after "X" seconds of vox are received? What's causing this?


I also have film of this recent crash, as well as previous crash or two, but again don't know if they would record anything that might help.

Before the terrain update, this was not an issue. It never came up. Could it be problems with how the new terrain, or the bump mapping, are stored in memory over long periods of time?


(not sure what it is)

[Krusty]

Aaaaand another... right around 2 hour mark or so (but not exactly).

I hope to god you're all getting some sort of report from Microsoft when we report these errors... Because you'll be finding DOZENS FROM ME!

Need to fix this. As it stands I can't even participate in events because they last longer than Aces High's executable does!


There was NO issue until the recent patch [EDIT: Not the P47M patch, one before that]. I didn't even crash with the new terrain. It was the supposed "fix" that helped others that started screwing me and a bunch of others over, crash-wise. Fixed one crash and introduced an entirely NEW one to a bunch of unaffected players.

[yb11]

me too every time i get hit with bombs in gv or from gv white screen with Application Error report

[df_swans_84]

lots of feedback for you here krusty im impressed *ends sarcasm*

hope it gets sorted for you guys though, thankfully i dont get this, i just got a crap ISP that im trying to cancel before the scenario so i can get back to my old ISP which were great

[Krusty]

going back to my earlier thoughts:

"I never got this with previous versions."

"It was something HTC added that caused this."

With those 2 ideas in mind, the only thing HTC really tweaked was the terrain. I was flying with detail OFF, bump map ON, and water ON, but all other stuff off (shadows/reflections/etc). So, much as I regret to fly this way, I turned off bump mapping and water.


Problem solved. Was able to fly a few long sessions in the MA as well as a scenario frame without crashing.


Looks like arse, though, and I run the risk of ramming water or land any time I dive. I should put water back on and see if I crash again. That would eliminate one or the other as the root of the crashing.