Topic: Crashes With Xecuter 2 4976.02? (Read 972 times)

vampire.de · « **Reply #105 on:** June 17, 2003, 12:06:00 PM »

Bad news...
I tried again, a couple of hours later.......and...... it freezed again....
sh..
cu
vampire

Skyron · « **Reply #106 on:** June 22, 2003, 09:48:00 AM »

Fofer · « **Reply #107 on:** June 22, 2003, 12:23:00 PM »

I had a consistent problem with Xecutor Lite once I updated it's BIOS to 4976.02. Every single time I exited a game (whether it be via X2's IGR, or even via the game's own "exit" command) I was unable to use EvoX to launch a 2nd game. It was stable everywhere else. Just on launching a 2nd game would it freeze... and the Xbox had to be turned off to be reset. This only happened when the network cable was plugged in, with it unplugged everything was fine.
I tried static/dynamic, and every version of EvoX, to no avail.

Now, it had worked fine with 4973 BIOS (which came preinstalled) and the problem started when I used FlashX to update it to 4976.02. I only flashed banks 1 & 2 - I left banks 3 & 4 with their factory default.

So I tried to downgrade my BIOS, went back too far, got a bad flash, and took a break.

I got the new Xecutor 2.1 Lite installed last week and flashed the BIOS with the ozxchip CD method to 4976.02 (all banks.) EvoX now works fine on launching a 2nd game, with the network cable plugged in. I tested it extensively this week without any problems. Nothing else has changed at all -- except the chip. I simply replaced my 2.0 Lite with a 2.1 Lite and the problem has gone away. Everything else, including my EvoX version (1.8.3752) has stayed the same.

Of course, AvaLaunch works too. But I'm sticking with EvoX for now since it does everything I need and is configured "just right." I'm looking forward to seeing AvaLaunch, neXgen, and the other dashboards mature.

I hope this helps shed some light for others out there, I know how frustrating it was for me.

Fofer · « **Reply #108 on:** June 22, 2003, 12:29:00 PM »

QUOTE (B@se @ May 30 2003, 08:50 AM)

QUOTE (lenny6998 @ May 30 2003, 07:03 AM)

DIdnt read all the posts but make sure u got atleast 2.5 gigs free on ur e drive.........

My E drive has 5gb of free space, but it still freezes when my network cable is plugged in

And my E: drive only has 607 MB free (I installed Gentoo-X Linux,) yet I no longer freeze (see above.)

Unreal7000 · « **Reply #109 on:** June 23, 2003, 08:50:00 AM »

OK seriously guys lets end this freakin discussion its been going on TOO long.

redrum374 · « **Reply #110 on:** June 24, 2003, 10:15:00 AM »

Question is everyone else here with the network lock ups running XP Professional?

sonik · « **Reply #111 on:** June 25, 2003, 06:00:00 PM »

This game freezes with this bios.
Dead_Or_Alive_Xtreme_Beach_Volleyball_PAL_MULTI6_DVDRIP_XBOX-LIGHT

And works with the old X2 4974.

LateraLex · « **Reply #112 on:** July 06, 2003, 03:11:00 PM »

QUOTE (redrum374 @ Jun 24 2003, 06:54 PM)

Ok we all kinda know that this is a network problem because unplugging the network cable works. But does anyone with any hardcore computer tech/networking skills know what would cause this? I dont understand how it freezes with network cable in it just completely baffles me.

I don't think we know that this is a networking problem, because myself, like many others are getting problems with the network cable disconnected..

Ubergeek · « **Reply #113 on:** July 08, 2003, 06:34:00 AM »

Ubergeek · « **Reply #114 on:** July 08, 2003, 06:37:00 AM »

QUOTE (cYtr0x @ Jun 11 2003, 09:23 PM)

I've been tracking this problem for some time now in search of a solution. I have 2 xb0x here. One b0x is a 1.0 and the other is a 1.1. The 1.0 b0x almost never freezes up at any time. The 1.1 b0x always has and still does lock up randomly . This seems to occur in games, in apps, in evox, after IGR and in the m$ dash. The problem is so inconsistent that it's hard to isolate - sometimes this 1.1 xb0x will run for days at a time without a lockup. At other times, it will lock repeatedly in short periods of time and at yet other times it locks up occasionally after several hours of use. I've been messing with this for months now and still have found no solid answers. Instead I have found a lot of staunchy theories that I feel are shakey at best. So here's what I've been through (and I've given you the abridged version of the story so be thankful)...

Initally, I thought the problem was a result of solder job ... and as confident as I was about the solder job, I reworked it. I removed the pin header completely and cleaned up the board perfectly (with a solder sucker and desolder-braid) and connected the wires directly to the points. Same random lockups.

After this, I read sth on the xecuter forums about it being a install problem and people blaming d0 being not 'solid enough' - so I resoldered d0 a few times to verify that my d0 was not making p00r contact or bridging to a nearby trace. Still - lockups occur.

With more reading throughout various threads and forums, I was told this is the result of IGR. I disabled all IGR - lockups still occur.

Other forum suggestions indicated that I should downgrade evox ... which I did. There were still lockups.

Next, I followed suggestions to use the evox D6 bios image. Also I was told to use a 1mb image on the x2pro instead of 4x256. I did both of these things and the lockups did not go away.

Feeling defeated, I ordered another x2pro to swap the mod out with assuming the mod was defective. The new mod does the exact same thing (at least I have a spare).

Meanwhile I feel it is important to note that my 1.0 xb0x is still working almost flawlessly with the x2pro installed in the exact same manner running all the same bios, dash and game software.

I have several theories:

* The problem seems to only affect 1.1 b0xes. Therefore, I cannot rule out some protection schema that m$ may have incorporated in the model that the x2 hardware and/or bios software does not overcome. Therefore I can't say the bios's and/or evoX are not indirectly responsible for the problem. However, since all the same variables work flawlessly in a 1.0 b0x, it would have to be the result of M$'s revision of the unit.

* I cannot rule out overheating of the mod or the xb0x itself (perhaps as a result of the replacment HD or the lack of the cpu fan in model 1.1 b0xes). It stands to reason that 1.1 b0xes are far more prone to running a bit hotter as a result of the air inside the case not being circulated as well due to that missing fan.

* I cannot rule out electromagnetic interference within the xb0x itself. The x2pro's d0 wire is very small guage wire and may be succeptable to EMI. Flat ribbon cables (like the FCC cable) are succeptable to emi (it would be smarter if the cables were round). Allthough the FCC cable has a shielding, it looks and feels low grade and many people report they are easily damaged. I highly doubt this is the culpret, but I'll keep the idea on the backburner just in case I exhaust all other troubleshooting avenues.

Currently, I am testing the network theory (which I will also give some merit until disproven) as well as the overheating theory. Should any answers present themselves, I will return to report my findings. In the meantime, if anyone uncovers anything please share your info here - thx.

-cYtr0x-

flash it with 2 x different bios

4976.02 and 4977

that will fix it

DuggyUK · « **Reply #115 on:** July 10, 2003, 09:39:00 AM »

QUOTE (Skyron @ Jun 22 2003, 05:48 PM)

My problems seem to have been fixed by switching to avalaunch... so I'm not gonna try and find the exact cause of the crashes until it crashes again

same here!

X-ace · « **Reply #116 on:** July 10, 2003, 09:50:00 AM »

Well here's an interesting one;

I had a completely stable system with NO freezes, until I switched my dash to xbmp. Now some apps won't launch - unless I unplug the network! Funky.

I still use xbmp as my main dash, but launch apps through evox.

Xbox Ver 1.1
X2L
Custom 4976-02
120 GB maxtor
Evox 3752 -> XBMP 2.4 CVS 6/15
Static IP

Win2k on PC
wireless Dlink router

nufan · « **Reply #117 on:** July 13, 2003, 11:49:00 PM »

i swear (at least for my case) its something to do with my network.

My mate has never ever had freezes, then he came to my place in the weekend, plugged in his xbox to my network, and got his first freeze (he didn't even know what was happening, had never had a freeze before)

so all i can narrow it down to his my network (no freezes with no cable)

so i have a nokia m1122 ADSL router, it froze with the inbuilt hub, i now have a switch, still freezes, have 2 other computers connected to it, one with XP professional one with XP home. The only other possibility could be the actual ethernet cable i guess (highly doubtful?)

redrum374 · « **Reply #118 on:** July 14, 2003, 08:11:00 AM »

There is a post that is on here about deleting a file in your saves directory a file that is created everytime xbmp launches. Has anyone tried deleting this it is...
E/tdata/0face007/ on your xbox and delete 'system.bin'
I tried and it worked for me but you have to delete it everytime you get done launching xbmp. Anyone really tampered with this alot?

It currently works for me but we all know how temporary that can be.

nufan · « **Reply #119 on:** July 14, 2003, 12:16:00 PM »

tried it, doesnt last.

its a network problem, like i said my mate with a different version xbox and a different mod chip to me has never ever had freezes until he came here and plugged into my network. Its either the other computers on the network, the type of router/adsl modem/other hardware, or the actual cables. This is also clear from the fact that if you unplug your network cable everything works perfect.

Author Topic: Crashes With Xecuter 2 4976.02? (Read 972 times)