xboxscene.org forums

OG Xbox Forums => Software Forums => Xbox Bioses => Topic started by: redrum374 on May 12, 2003, 07:23:00 PM

Title: Crashes With Xecuter 2 4976.02?
Post by: redrum374 on May 12, 2003, 07:23:00 PM
I have the xecuter 2 version 4976.02 and I keep getting system lock ups. I have heard that this doesnt have to do with the bios but deals with evox. I totally disagree I have had the x2 4974 and never had a problem or lock up at all. Is anyone else experiencing this and know how to fix it. It is getting real annoying.
Title: Crashes With Xecuter 2 4976.02?
Post by: razorrifh on May 12, 2003, 07:29:00 PM
what are you doing for the crashes to happen? ive never had a crash with that bios and ive been using it since the day it came out.

if its that annoyingy you can always change it  tongue.gif
Title: Crashes With Xecuter 2 4976.02?
Post by: redrum374 on May 12, 2003, 07:39:00 PM
It happens always when a game is loading or in halo when it is searching for a game in system link. It locks up on me in return to castle wolfenstein at load screens which is the main reason I got the bios. I have the newest evox version.  
Title: Crashes With Xecuter 2 4976.02?
Post by: shanafan on May 12, 2003, 07:40:00 PM
QUOTE (redrum374 @ May 12 2003, 11:16 PM)
I have the xecuter 2 version 4976.02 and I keep getting system lock ups. I have heard that this doesnt have to do with the bios but deals with evox. I totally disagree I have had the x2 4974 and never had a problem or lock up at all. Is anyone else experiencing this and know how to fix it. It is getting real annoying.

What modchip do you have?
Title: Crashes With Xecuter 2 4976.02?
Post by: razorrifh on May 12, 2003, 07:40:00 PM
it freezes on retail games or backups? backups on dvd or hard drive?
Title: Crashes With Xecuter 2 4976.02?
Post by: redrum374 on May 12, 2003, 07:49:00 PM
freezes on backups on the hard drive. And I have a Matrix chip.
Title: Crashes With Xecuter 2 4976.02?
Post by: redrum374 on May 12, 2003, 08:13:00 PM
Do you think it could be a bad flash?? Should I reflash?
Title: Crashes With Xecuter 2 4976.02?
Post by: ChrisF on May 12, 2003, 09:53:00 PM
Ubergeek recommends evox 3285.  He says he there are issues with the newer evox.  Try and see.
Title: Crashes With Xecuter 2 4976.02?
Post by: lion00 on May 13, 2003, 09:47:00 AM
turn off IGR in evo x if you're running games off the harddrive and see if it still freezes with 4976.02
Title: Crashes With Xecuter 2 4976.02?
Post by: razorrifh on May 13, 2003, 06:54:00 PM
also, try reripping your games, because they might of have been errors when you copied them.
Title: Crashes With Xecuter 2 4976.02?
Post by: Dirkbox on May 14, 2003, 03:34:00 AM
well I have never had so many frezes with since using the bios.  It pretty much always when a program crashes.

Trying soethings on Avalaunch last night, i crashed the xbox a few times.  Switching off and on, it get to the xbox & x2logo then no further.  Turning off & on again solves it but, it happened 4 times in a row.  But rebooting using the eject button all is fine.

I'm using evox 3285.

Also using an X2lite, also amazed how many time it switiches banks, but that not important.
Title: Crashes With Xecuter 2 4976.02?
Post by: HBK757 on May 14, 2003, 11:21:00 AM
XBox v1.1 PAL UK
Xecuter 2 Lite (Flashed 4976.02 256K Multi BIOS)
Maxtor 120GB 7200RPM Hard Drive

Have tried Evo-X 3285, 3682, 3752, all give lockups. Have tried disabling IGR (all 3 in Evo-X), no joy. Tried formatting hard drive, reinstalling everything and copying games back over, no joy. Checked solder points, everything is fine. Whatever I do, I get random lockups, mostly on the Evo-X loading screen and just after the loading screen when the screen goes black and is about to begin loading the game. I've also had lockups in Halo and NBA Street Volume 2.

The point is - nobody knows why this happens, and I've tried everything possible to fix it. It cannot be fixed at this time. Maybe a new Evo-X release or X2 Lite BIOS will change that.
Title: Crashes With Xecuter 2 4976.02?
Post by: B@se on May 14, 2003, 12:53:00 PM
I seem to have the same problem, I've also tried a hundred things....

BUT I've noticed that removing the network cable solves the problem, but I would really like my xbox to work properly WITH network cable. I can't find the problem though, really frustrating!

Specs
Xbox v1.0
Xecuter2 lite
Bios: Xecuter2 (tried all the recent bioses, using 4794 at the moment)
Dashboard: Evolution-x 3752( also tried multiple versions without succes)

This post has been edited by B@se: May 14 2003, 07:56 PM
Title: Crashes With Xecuter 2 4976.02?
Post by: redrum374 on May 14, 2003, 07:22:00 PM
Nope still gives me a problem hopefully a new version bios will fix this. Tried reburning game, tried multiple evox dashboard versions, tried reflashing. Nothing works. Ohh well will just wait for new version and hope it works.
Title: Crashes With Xecuter 2 4976.02?
Post by: nebur on May 15, 2003, 08:49:00 PM
skip it fixed it by reloading evo d6 and it still happened. problem cleared after reseting my router. my apologies to the x2 crew.
nebur

This post has been edited by nebur: May 16 2003, 06:04 AM
Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on May 16, 2003, 10:52:00 AM

Didn't see this suggested, so i thought I'd throw it in;
Did you try the X2 IGR disable by putting the file on E?
Title: Crashes With Xecuter 2 4976.02?
Post by: gundamhr on May 16, 2003, 11:45:00 AM
this happens to me all the time too. Previously though, I was using my original bios that came with my chip and it worked perfect. I just flashed with 4976.02, and i get random lockups. Also, in bank 1 I flashed it with the regular 4976.02, however in bank 2 I put a modified 4976.02 with blue x logo, and it worked perfect at first, but no it doesn't work at all. I'm assuming all this has something to do with the bios, because I had no problems with my old bios and EvoX 3572.
Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on May 16, 2003, 12:42:00 PM
Can you reflash back to the old bios, and will it work then?
Title: Crashes With Xecuter 2 4976.02?
Post by: Suckdogg on May 17, 2003, 12:08:00 AM
QUOTE (B@se @ May 14 2003, 09:46 PM)
I seem to have the same problem, I've also tried a hundred things....

BUT I've noticed that removing the network cable solves the problem, but I would really like my xbox to work properly WITH network cable. I can't find the problem though, really frustrating!

Specs
Xbox v1.0
Xecuter2 lite
Bios: Xecuter2 (tried all the recent bioses, using 4794 at the moment)
Dashboard: Evolution-x 3752( also tried multiple versions without succes)

Same thing here, my xbox would lock up after playing 5 minutes or so of certain harddrive games.  Even sometimes while sitting on the menu.  Then I unhooked the cable and it works fine.  
Why is this?
Kind of a pain in the ass to unplug it whenever I play a game, but I guess I'll have to.
Title: Crashes With Xecuter 2 4976.02?
Post by: Suckdogg on May 17, 2003, 12:22:00 AM
Hey B@se, were you running Relax when this was happening to you?  I had mine on as a service, just shut it off and will see what happens.  Maybe when it pings (or whatever) the xbox, it locks it up during a game.


Nope...Still locks up.  Maybe it's Windows???
Title: Crashes With Xecuter 2 4976.02?
Post by: B@se on May 17, 2003, 12:56:00 AM
wink.gif )
Title: Crashes With Xecuter 2 4976.02?
Post by: mrRobinson on May 17, 2003, 05:28:00 PM
Just to add my story...
I was running D6.ejectfix and playing games off Hdd just fine, no lockups ever.
In an attempt to get Enter the matrix playing i had upgraded to the 4976.02
Now about 80% of boot up it locks after it says Xecuter2 at bottom of screen.  If i eject the drive it'll then load.
Igr is disabled and all game still play fine but that lock at boot is annoying.
Title: Crashes With Xecuter 2 4976.02?
Post by: Majinbuu on May 17, 2003, 06:07:00 PM
Alright, I only get lockups when at LAN parties, i have been in all different climates, good ventilation, bad ventilation ect.... i suppose it was only freezing because it was pluged up to the switch (goddamn wish i had read this before last night). That is the only time i get that, when it is pluged up to a network. My freezes ONLY happen when it is on a network when

The switch we were using had DHCP, and i have also had it happen when using crossover. BTW i have two boxes, BOTH 1.0, i would be interested to know if this is isolated to any one particular generation of consoles.

Buu

Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on May 18, 2003, 10:52:00 AM
could be generation of x-box coupled with mod chip and bios.

why don't all of you with issues list your configs

-xbox ver
-mod chip
-bios
-evox ver

then a short description of when it crashes. Maybe we'll see a pattern.
Title: Crashes With Xecuter 2 4976.02?
Post by: mrRobinson on May 18, 2003, 10:57:00 AM
xbox ver  - 1.0 (in first shipment)
-mod chip - xecuter pro
-bios - 4976.02 (IGR disabled in evox.ini and with file on E:)
-evox ver - 1.8.3285


The bios i had before was D6.ejectfix and never hung.
Title: Crashes With Xecuter 2 4976.02?
Post by: mrRobinson on May 18, 2003, 10:58:00 AM
Oops. and mine will hang 70% of time on boot just when it says Xecuter2 on bottom of screen. If i eject drive it then will continue.
Title: Crashes With Xecuter 2 4976.02?
Post by: redrum374 on May 18, 2003, 04:02:00 PM
My specs

Xbox version-1.0
Modchip- Matrix chip
Evox version-1.83285
Bios- 4976.02 xecuter
Relax is running

Lock ups in games!
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 19, 2003, 01:22:00 AM
yeah so this is the deal
Ver. 1.1
Executor 2 lite plus
4976.02 bios
latest evox

locks up when launching some games..it actually starts the game and in the beginning licencse info / movie it will lockup (wolfenstein, halo) xbmp sometimes...all i gotta do is restart and i'm fine though.
also noticed that is locksup during sytem link shit...not during the games however...
when its looking for a game
i really think it has something to do with the network cable...cuz when i unplug no freezing..it also freezed once during nfl fever and that was also system link...
got a crossover here...dhcp has nothing to do with it and neither does cross over ...cuz when i had my 1.0 box w/ executor 1 it never ever locked up
only since i got this new 1.1/ex2liteplus/4976.02 i've been getting problem...
and to the guy who was to lazy to reply to my private message..fuck you....
have a nice day everyone..and hopefully we can figure out /solve this problem
Title: Crashes With Xecuter 2 4976.02?
Post by: Ubergeek on May 19, 2003, 03:10:00 AM
i'd fix it if I EVER saw a problem

you see - for every person who posts with a problem - i could get 50 who dont have any problems - this a problem in itself

if i can dupl;icate an error on my setup then I can debug it - ive never had a problem (except sometimes with evox 3752 - but i just use 3285 anyway)

Title: Crashes With Xecuter 2 4976.02?
Post by: Ubergeek on May 19, 2003, 03:11:00 AM
QUOTE (ybaig123 @ May 19 2003, 10:22 AM)

i really think it has something to do with the network cable...cuz when i unplug no freezing..it also freezed once during nfl fever and that was also system link...

this has been mentioned as the cuase of problems MANY times before bro

I will investigate
Title: Crashes With Xecuter 2 4976.02?
Post by: Ubergeek on May 19, 2003, 03:13:00 AM
also try a 1MB bios with 4976.02 1MB version original release

Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on May 19, 2003, 03:25:00 AM
a similar problem was fixed by deleting game saves (yeah I know, it sounds improbable).
see this thread; http://64.4.8.250/cg...&...d38&t=56194

although with ubergeek on the case we might hope for a scientific and speedy resolution.
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 19, 2003, 12:20:00 PM
i dont think pinging has anything to do with it but i dunno...cuz i have the same setup on my pc and network shit as i did with my last xbox..only change is xbox/chip/bios....and now i get problems
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 19, 2003, 03:30:00 PM
well i didnt think this would change a damn thing but i changed my dashboard back to 3285 static......and it has not freezes once since....keepin the figerz crossed here...hopefully this does the job ...
Title: Crashes With Xecuter 2 4976.02?
Post by: mrRobinson on May 19, 2003, 03:52:00 PM
I don't know.  My issue seems straightforward... I had D6.ejectfix, never an issue then put 4976.02 and it'll hang before getting to the evox dash (but if i eject drive then boot).  The only other thing that changed on my setup during that time is that i added the patched ETM to my F: drive, and to do that i took it off my WET11 (dhcp) to xover to my laptop (static) then back to the WET11 (dhcp).

I'll try the 1mb bios but i'm away on business this week so it'll have to wait till next mon.
Title: Crashes With Xecuter 2 4976.02?
Post by: richie579 on May 19, 2003, 03:58:00 PM
Ver. 1.1
Xecuter 2 lite plus
Bios 4976.02
Evox 1.8.3752
120GB Maxtor(the one with 8MB cache)locked and unlock doesn't matter
Samsung DVD Drive(let's me read all CDRs and RWs)

Games off HD work all the time, the only lock up I got was with the Japanese Ver. of Capcom Vs SNK 2. XBMP(off Slayer's 2.1 up until the latest build) almost always locks upon first boot, reset the machine and everything is fine, tried without net cable, loaded on first boot once, then did the regular, what I just described. I have Evox set to auto load DVD movies and I use xboxdash to play them, again locks up on first boot, reset and everything's fine. FTP almost never works on first boot, again reset, you know the drill, but I do use a mac to connect so that could be it, either way I reset and I'm fine. So basically, I start something that'll lock the machine, reset and I should be fine for the rest of my XBOX session. It would be nice to fix it though.
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 19, 2003, 06:01:00 PM
well fuck....the change of dashboard didnt do shit..stopped freezing for a couple hours...now we are back to square one...cuz it still freezes....someone needs to help....or atleast come up with a defniate reason for all this
Title: Crashes With Xecuter 2 4976.02?
Post by: Jabbah on May 20, 2003, 06:49:00 AM
Well, not sure if this was the same problem as I fixed it pretty quick and so didnt find out how much stuff it affected, but I was having problems with random lockups one night and tracked it down to problems with running DHCP on my network. Assigned static IP's to xbox and all PC's and then it worked fine. Might be worth a try for you guys having problems.

Jb
Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on May 20, 2003, 07:03:00 AM
Or try to turn the network off.
Title: Crashes With Xecuter 2 4976.02?
Post by: Ubergeek on May 20, 2003, 10:24:00 AM
QUOTE (Jabbah @ May 20 2003, 03:49 PM)
Well, not sure if this was the same problem as I fixed it pretty quick and so didnt find out how much stuff it affected, but I was having problems with random lockups one night and tracked it down to problems with running DHCP on my network. Assigned static IP's to xbox and all PC's and then it worked fine. Might be worth a try for you guys having problems.

Jb

this is definatley a fix
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 20, 2003, 01:09:00 PM
WOW..i dont belive this bullshit..i went out and bought a new xbox....took the chip /hdd out the old one...(Swapped them) and guess what?!?!?! it still freezes.....now what?
Title: Crashes With Xecuter 2 4976.02?
Post by: mrRobinson on May 20, 2003, 04:21:00 PM
Well I'll take mine off DHCP but with D6.ejectfix it was on dhcp and there was never a problem so i still think its something that can be fixed in the bios.
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 20, 2003, 11:06:00 PM
i'm not sure if dhcp does it...cuz i'm using crossover & my xbox & pc both have static ips in my network...and i still get freezes...someone please help...
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 20, 2003, 11:47:00 PM
ok i'm gonna get into a little detail here....hopefully someone will be able to figure something out.
Here goes
What is causing this xbox freezing problem?

1.  Is the xbox itself the problem? -- dont think so cuz i just bought another today, installed the x2liteplus & my hdd, and it still freezes on the new box.
2.  The bios the problem? -- no (i think) cuz i've tried a few (4976.02, 4975, d6, ) and same freezing.(not a bad flash either, has been relflashed number of times)
3.  The harddrive the problem? -- no cuz i was using the exact same hdd with my older xbox 1.0 w/ executor 1 and it never gave me this problem.
4.  Is the ex2lite modchip the problem?   -- MABYE , this all started when i installed the chip on my new box (1.1)(its been removed and installed a few times so i dont think a bad installation is the problem either)
5.  Is it the xbox version 1.1?  -- MABYE -- cuz when i had a 1.0(w/ older bios & excutor 1) it never froze, also, the new xbox i bought today was also a 1.1 , and it still freezes.
6.  Is it a networking problem  -- MABYE -- cuz it seems that when the network cable is unplugged, it never freezes, although i have not tested it w/ network cable unplugged for long periods of time.  
7.  DHCP / STATIC related?  -- Dont think so, cuz i have the exact same network setup that i used with my old 1.0 box and never had issues.  Despite changed all my setup to static ips, and it still freezes.

8.  Dashboard related?  -  nope, change evox version around a few times, went back , and forth, no difference.

So what can the problem be?  No idea....the weird thing is that it does this with more than one of my xboxes...someone please help......sometimes i think its my pc.....but what the hell i have the same setup as i did w/ my 1.0, and never had a problem...so what can it be?!  
Ever since i first got my new 1.1 box , installed the x2liteplus /4976.02 and hdd, one of the first times i used it after setting it up...it began freezing...i'm so damn lost right now.....

someone please try to make some sense out of this...and help me out...thankyou
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 20, 2003, 11:56:00 PM
forgot a couple things....

Cant be IGR cuz they are all disable..

and games/apps it has frozen with.....  Wolfenstein...freezes at the first screen(liscense info) before reaching the "ESRB Notice" game experience may change online...." also during system link when looking for a game

Nfl fever, during system link setup,  

Halo, during main menu, once during the intro movie, during system link game search

XBMP - not often...but sometimes

UNreal tournament - once after loading bar was full, it just froze

All of these game/apps use the system link in some way or another...just why didnt i get these problems with my old 1.0 box....why did it start with my 1.1 now?
Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on May 21, 2003, 02:51:00 AM
Well, it sounds to me that for testing purposes, I would start by
+ setting static IP

if does not work by itself, try
+ unhooking the network cable

How many people have tried this and with what results?
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 21, 2003, 03:57:00 AM
setting static ip doesnt help for me...unplugging network cable i think does...i just need to have my box running a little longer to know for sure
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 21, 2003, 11:48:00 AM
could it have anything to do with the fact that my c: / e: drives are backups of drives off a 1.0 xbox and i'm using this shit on a 1.1?
Title: Crashes With Xecuter 2 4976.02?
Post by: B@se on May 21, 2003, 01:06:00 PM
yo redrum, if you want the xbox etc. to have static ip's do you you have to set this in the evox.ini or set it up in the router for example?

(I think i had my xbox's ip set to static in the evox.ini in the beginning, but then xbox live wouldn't connect)
Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on May 21, 2003, 01:09:00 PM
it's in the ini
static IP = yes

see earlier in this thread for examples
Title: Crashes With Xecuter 2 4976.02?
Post by: redrum374 on May 21, 2003, 07:40:00 PM
(I think i had my xbox's ip set to static in the evox.ini in the beginning, but then xbox live wouldn't connect) ?
B@SE what do you mean by xbox live?  You cant use xbox live on backed up games or use xbox live from evox. Your msdash takes care of all that. Evox doesnt have anything to do with xbox live settings.
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 21, 2003, 08:20:00 PM
fuck it... i guess i gotta live with this freezing shit...cuz that static ip stuff doesnt make a difference for me
Title: Crashes With Xecuter 2 4976.02?
Post by: Scubix on May 22, 2003, 03:08:00 AM
tongue.gif

My guess its  the bios (4976.02) or the evo-x, or the combination of them as my probs started after flashing the x2lite bios. I havent had enuf time to test older bioses or evo-x versions, but i will soon

ps: i have a v1.1
Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on May 22, 2003, 03:52:00 AM
well,
unplugging the network canle may not be asolution for all, but if that works at least it is an indication of where the problem is.
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 22, 2003, 04:04:00 PM
fuck this...its gotta be the chip....fucking executor...nothing else can explain this...network cable and all......and i doubt system-mods will take returns...so i guess i just got a shitty chip
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 23, 2003, 12:52:00 AM
B@se mine is pretty much exactly as yours
Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on May 23, 2003, 04:54:00 AM
Sounds like the advice is to pull out the network cord when you play games then
(until someone figures this out)
Title: Crashes With Xecuter 2 4976.02?
Post by: bucko on May 23, 2003, 10:53:00 AM
Could be fragmentation. All those needles spinning accroos 120gig drive to find that certain file to load the game might be the cause of the crashes, the games wern't designed to run on such fragmeneted drives.
Title: Crashes With Xecuter 2 4976.02?
Post by: bucko on May 23, 2003, 12:31:00 PM
Na I was trying to Isolate the problem because I don't think it's a network issue.
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 23, 2003, 06:05:00 PM
if someone can solve this problem for me (and give info that fixes it... ie: no more freezing)....i give them a free xbox (unmodded) w/ controller and all
Title: Crashes With Xecuter 2 4976.02?
Post by: JD22 on May 23, 2003, 11:17:00 PM
Anyone having these problems running game off of a backup?
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 26, 2003, 11:55:00 PM
i told you man....static ip has nothing to do with it
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 27, 2003, 05:55:00 PM
wrong again...next?
Title: Crashes With Xecuter 2 4976.02?
Post by: Fofer on May 27, 2003, 11:39:00 PM
Has anybody tried downgrading from 4976 to 4975 or 4974 to see if the problem goes away?

Mine starting freezing when I upgraded to 4976.  In my efforts to troubleshoot I made a bad flash and now am waiting for a X2 programmer so I can start playing again.
Title: Crashes With Xecuter 2 4976.02?
Post by: Skyron on May 28, 2003, 09:23:00 AM
Mine freezes too, haven't looked at the problem in detail yet.

It does seem to be the case that it will freeze within a couple minutes after playing/xbmp, then I shut down and boot it up again and it works for a long time.
Therefor heating doesn't seem to be the problem, as the box should get hotter the longer it runs.
Title: Crashes With Xecuter 2 4976.02?
Post by: d_river23 on May 28, 2003, 10:59:00 AM
I play NHL2K3 with the network cable plugged in and it freezes during gameplay but if I remove the network cable I never get a crash.

I'm running a xbox 1.0 with Xecuter2 Pro 4976.02
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 28, 2003, 11:22:00 AM
yes if ther is no net work cable ===== no crash..so how can it be temp related....i check the temps and they look normal to me..
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 28, 2003, 11:23:00 AM
also changed bios several times to evox, 4975..etc....and it makes no difference...still freezes
Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on May 28, 2003, 01:51:00 PM
What version of XBMP are you all using?
CVS versions or the 2.3 complex release?

I have the complex and have aboslutely no problems with crashing/freezing.
(version 1 box)
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 28, 2003, 10:10:00 PM
gots complex...xbmp doent crash..only some games
Title: Crashes With Xecuter 2 4976.02?
Post by: Unreal7000 on May 29, 2003, 08:03:00 AM
Try unplugging the network cable out of the back of the xbox when playing ripped games. And turning off IGR. Maybe turn off RDTOOLS. I dont even know what it does anyways.
Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on May 29, 2003, 08:21:00 AM
QUOTE (Unreal7000 @ May 29 2003, 04:03 PM)
Try unplugging the network cable out of the back of the xbox when playing ripped games. And turning off IGR. Maybe turn off RDTOOLS. I dont even know what it does anyways.

Ok I think we figured the network thing out a few times in this thread. Now let's try to figure out why the network is acting up.

My bet is currently on a CVS build of XBMP.

anyone?
Title: Crashes With Xecuter 2 4976.02?
Post by: Unreal7000 on May 29, 2003, 09:35:00 AM
sorry i didn't read all the threads before mine. thought i would just throw that in to see if someone else had already said that.
Title: Crashes With Xecuter 2 4976.02?
Post by: dzv on May 29, 2003, 11:34:00 PM
Would you care to expand on that?  I haven't heard this suggestion before.
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on May 30, 2003, 12:02:00 AM
same here... e has 4730 mb free...still freezes
Title: Crashes With Xecuter 2 4976.02?
Post by: Meep on May 30, 2003, 06:25:00 PM
ok. I haven't played with changing bios's for a long time. an hour ago my v1 box had the X2 version 1 bios, on a 29 homebrew. I've never had a single problem with freezing.

I just installed the latest 4976.02 bios. guess what, it's freezing. Definitely a bios problem, nothing else.

No big deal, props to X for constantly trying to improve their bioses. I hope this helps.
Title: Crashes With Xecuter 2 4976.02?
Post by: robg on May 31, 2003, 01:20:00 AM
My specs

Xbox version-1.1
Modchip- Matirix
Evox version-1.83285
Bios- 4976.02 xecuter
Relax is running
Using a static IP.
All IGR's are off and also have the IGR disable file on drive E:.


My setup occasionally crashes under Media Player 2.4 but I have noticed it always crashes everytime when I try to go back to the evox dashboard from the Super Nintendo emulator.  When I unplug the network cable and carry out the same procedure it does not crash.
Title: Crashes With Xecuter 2 4976.02?
Post by: mrRobinson on May 31, 2003, 01:50:00 PM
I've posted earlier in this thread, but my problem is only a lock up during boot where it won't load the dash but then if i eject the drive it'll reset and load.  So i'm creating a new topic Crashes with Xecuter 2 4976.02 (during boot) and will post what i've done so far to debug this (and seems to be fixed) **for now**
Title: Crashes With Xecuter 2 4976.02?
Post by: Baal on June 01, 2003, 02:14:00 AM
Ok dunno if this thread is good but my problem is quite the same.

my config first.
Xbox v1
Executer2+pogopin
Bios: ...tried many x2 bios.
Nothing on HD


Ok by some weeks i'm experiencing strange hangs on of xbox...it occurs at boot, during loading the game, while playing and load a part of game and so on.
If i press the eject button it will Boot 2 times and FRAG!!!!!
If i disable the chip it will boot normally with MS bios.
Well i was forced to reflash bios and all goes well...but sometimes (just now) also if i -newly - flesh the bios (now i'm trying 4974) i get boot 2 times and FRAG.

Can be the UDF format the cause of those strange problems (also before i used menux and now i'm using craxtion)? (a DVD with Splinter cell and Outlawgolf gives  me this problem 2 time in 2 days).....
But how can the bios be fucked by these loock ups?

- Pogo pin is not misallined.......i chechek the first time when got this problem and reallined it, but when the 2nd time got that problem, with refleshing of bios all went good -


EDIT - rofl.....now i tried to flash the bios the 2nd time and it says " no x2 found!" 1 min before i was able to flash it :|
Title: Crashes With Xecuter 2 4976.02?
Post by: ybaig123 on June 01, 2003, 10:38:00 AM
seems like your problem is way outta this league man
Title: Crashes With Xecuter 2 4976.02?
Post by: mrRobinson on June 02, 2003, 06:04:00 AM
kapkorn you have 4976.02?  my problem was just a hang during boot but when i loaded a color bios it seems to have fixed it (or with network unplugged).  can you try a color bios just so we can differentiate between a problem during boot and problem during game? Unplugging network cable fixes both but wondering if color bios will fix yours.
Title: Crashes With Xecuter 2 4976.02?
Post by: mrRobinson on June 02, 2003, 09:56:00 AM
ok this worked:
4976.02_Red_Noani_256k.bin

whereas this did NOT:
Xecuter2_4976.02_MultiVer_256k.bin
Title: Crashes With Xecuter 2 4976.02?
Post by: mrRobinson on June 02, 2003, 04:26:00 PM
QUOTE
Few questions: (possibly for Ubergeek):
Does the noani change or affect in any way the way the xbox loads its networking stack? It seems like if the network can come "up" before or during the logo screen it will then load the dash, otherwise it just sits there (waiting for the net to initialize?).

The other thing i was going to try is to take my 3285 exox to the 3752. In the 3752 evox.ini there were two extra lines in the network section that i don't have in my .ini with 3285 and they are


SkipIfNoLink = No
SetupDelay = 10


I was thinking if these values were messed with it would get it to work. But right now my problem is resolved with the red noani bios so i don't want to go messing with the dash just yet (and i read about bugs with it anyway)

I know MsSplitch had same issue so if can confirm same fix??
Title: Crashes With Xecuter 2 4976.02?
Post by: micleeso on June 04, 2003, 07:03:00 PM
After reading this thread from the beginning to the end, and working with my own analysis using logic and isolation. By method of elimination I have concluded my research with the following results.

Everyone has the same issue "network communications - crashes the Xbox".  And I have been experiencing the same phenomena. We need to isolate which part of network portion is broken? TCP/IP stack, bios or dashboard? Is it part of the new copy protection circumvents?  Who, what, where, when, and how is this going to be resolved? Simply following a method and coming to a definite conclusion is the only direction a logic answer will follow..
Title: Crashes With Xecuter 2 4976.02?
Post by: micleeso on June 04, 2003, 07:10:00 PM
My current experiment

Many people point to outside network issue such as DHCP. It's proven not related to outside services due to method of elimination.

I have tried the older dashboard from evox and not one crash. Load up the new one and it crashes. So I updated my bios with new evox dashboard, it crashes. Back up to older dashboard it is stable.

I add a direction to my logic, network communications with in evox.

My specs for review (Variables)

Xbox ver. 1.0
120 WD 7200 8MB Cache
Bios x2 4976.02 512k
evox dash 1.8.3752
XBMP build 13 May 2003 20:30
with linksys BEFW11S4 router using wire with wireless module enabled. DHCP disabled.

Evox dash settings
network: static
setup network: yes
no DNS entered
setup delay:
skip setp if No link: yes
xbox hardware info: 00000003 A3 B2
Kernel Version: 1.00.4976.02
FTP: No
Telnet:no
RDTools:No
Clock: Jump to MS Dash:No
Jump if No link: Yes
24Hour: No
SwapDate: Yes
SNTP:216.244.192.3
misc:
Dash ver. 1.8.3753
fahrenheit:No
Auto Launch Games:No
Auto Launch DVD:No
Auto Launch Audio:No
Use F Drive:Yes
In Game Reset:Yes
Use Items.txt:No
Screen Saver:5
Shade Level:95
Title: Crashes With Xecuter 2 4976.02?
Post by: micleeso on June 04, 2003, 07:33:00 PM
Since my direction has pointed to evox I am posting on evox board as well for your info.

http://www.valholl.org/forums/ under EvolutionX Forum Index -> Support -> Lock-up Issues.
Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on June 05, 2003, 10:38:00 AM
Some people have reported success by setting the IP Settings in XBMP to STATIC.

try this and see if it works.

(or try using XBMP as a dash.)
Title: Crashes With Xecuter 2 4976.02?
Post by: LiquidFusion on June 05, 2003, 12:48:00 PM
UPDATE:  over a crossover cable only freezes too.

EDIT:  ok here's another weird thing.  x1.1 doesn't even have to be looking for clients to join.  It can just be in the start menu.  

EDIT2:  OK WHAT THE FUCK!?!??!?

ok i finally fixed it.

so we had an idea about trying to join a game while x1.1 was in a game that doesn't have system link.  So we tryed it with blinx.  I was in the menu and he tried to join a brute force game, nothing happened to mine.  So i did a IGR reset and booted up wolfenstien, a system link game.  Was in the main menu and he tried to join and nothing happened.  So i tried to host a system link game and then he tried to join and again no freezing.  I did another IGR and booted up brute force, and we're currently playing squad deathmatch.  I'm afraid to turn off my xbox for fear that i can't play brute force mp again.
Title: Crashes With Xecuter 2 4976.02?
Post by: mrRobinson on June 05, 2003, 02:08:00 PM
QUOTE (micleeso @ Jun 4 2003, 11:03 PM)
After reading this thread from the beginning to the end, and working with my own analysis using logic and isolation. By method of elimination I have concluded my research with the following results.

Everyone has the same issue "network communications - crashes the Xbox".  And I have been experiencing the same phenomena. We need to isolate which part of network portion is broken? TCP/IP stack, bios or dashboard? Is it part of the new copy protection circumvents?  Who, what, where, when, and how is this going to be resolved? Simply following a method and coming to a definite conclusion is the only direction a logic answer will follow..

Well kapkorn and I both fixed it by loading a 4976 noani bios as opposed to the normal one.  It seems to me whether or not it is a "bios problem" it is definatley something that can be fixed in the bios.  Especially since i never had the problem when i was running D6.ejectfix.  But I posted all this before...
Title: Crashes With Xecuter 2 4976.02?
Post by: chong on June 06, 2003, 04:52:00 PM
which pins do u keep and remove from the xecuter 2? i cant flash, it says flash not wrtiable.
Title: Crashes With Xecuter 2 4976.02?
Post by: zbuffer on June 07, 2003, 05:59:00 PM
I'm having the issue where I used the patch through Craxtion, for my Brute Force HD Backup, and it always freezes during the loading screen... same spot everytime..
Is the conclusion that there is nothing to fix this??
Title: Crashes With Xecuter 2 4976.02?
Post by: psxweb on June 08, 2003, 12:18:00 AM
i've seen that you are a lot to have this prob
i'm mounting modchip every day and i've seen that all these network software are freesing on a cold boot
with evox but if you put avalaunch or nexgen you'll don't have the prob

I'ts not an hardware prob but a simple bug in the evox network i 'think
Title: Crashes With Xecuter 2 4976.02?
Post by: cyberbadboy on June 08, 2003, 04:29:00 AM
Had some trouble like that, all i did was unplug my connections inside the xbox (yellow power cable for the cd rom) hooked everything back up and (No more freezing) it works fine, so my statement is to make sure ur everything is put back the way you found it.
Title: Crashes With Xecuter 2 4976.02?
Post by: slidellsimba2 on June 09, 2003, 10:16:00 AM
i deleted any xbox dashes i want using including the original one and i dont get lockups anymore

just some advice maybe it was something minor that i changed too but i doubt it
Title: Crashes With Xecuter 2 4976.02?
Post by: 007_xbox on June 11, 2003, 02:17:00 PM
cYtr0x, i know exactly what your talking about, both me and my brother own an XBOX, 1.1 and get the same lockups. As you said, its entirely random the lockups. My mate however recently purchased a 1.2, and belive it or not, no lockups!! We havn't once seen it lockup yet after 2 weeks a playing games/XBMP and evox. As i said in my previous post, when this happens, deleting the E/tdata/0face007/system.bin file seems to temporarly fix this problem. I spoke to a couple of people about this problem before, and they said this problem only arose when the x2 bios became multi (1.0 and 1.1). Any one with any advancements, please post!!
Title: Crashes With Xecuter 2 4976.02?
Post by: cYtr0x on June 11, 2003, 11:54:00 PM
Thx for the response.

Interesting that the 1.2 units don't display the same symptoms as the 1.1 units (this reinforces the belief that the x2pro hardware itself is not to blame). I will agree with you that perhaps the problem relates to the bios itself ... but if that's the case, I have to question the EvoXd6 bios too.  Perhaps multiversion bios's really aren't completely finished for the 1.1 xb0x ... however, for the timebeing this remains (in my mind) unproven.  As for the file you suggested deleting, it is not present on this 1.1 xb0x - so it would seem to not be an issue.  As such, I have continued testing...

Overheating theory:
As stated before, indeed the 1.1 box does probably have more uncirculated air that the 1.0 model due to the unpresent heatsink fan.  The addition of a larger drive seeking over more area would also introduce some additional heat. I decided that venting some of that heat could easily be accomplished by removing the cover (I did this last night before a syslink halo match between the two boxes).  After doing so the xb0x worked flawlessly all night and today... until...

Networking buggyness:
Wakeboarding Extreme and UFC Tapout and Halo all ran fine on the 1.1 xb0x today throughout quite a bit of testing.  No lockups booting games, after IGR (I have it re-enabled via the x2 bios since disabling it was not a solution), during gameplay or within EvoX.  As s00n as I turned on the 1.0 xb0x (which had been off all day), halo locked up on the 1.1 xb0x.  Subsequent attempts to begin a system link game between the two boxes resulted in repeated lockups of the 1.1 b0x.  This does NOT occur in the same place each time - sometimes it's in Evox, other times its occurs in game after boot and yet other times this occurs when trying to begin a system link game (again very inconsistent and non-reproducable at times) Immediately following this observation, I was able to play other non-systemlink games on the 1.1 xb0x without any lockups whatsoever.  Also bear in mind that Halo worked PERFELCTLY last night with NO variables changed from then to now.  At one point, I turned the 1.0 xb0x off and the 1.1 box quit locking in halo - then as s00n as I turned the 1.0 b0x on again, the 1.1 locked IMMEDIATELY.  As you can see, some of the findings are conflicting.  However, I still have some troubleshooting avenues to explore - because IF it works sometimes, then it should be reproducable or isolatable (or so logic dictates).

I find myself asking ... "is it all co-incidence?"  I have spent several years troubleshooting extremely technical and sensitive technology  for a living .. but this issue has had me fooled for quite some time now.  Why did syslink halo work flawlessly last night and lock like mad today when nothing had been changed?  I feel confident in saying it has nothing to do with overheating at this point.  I will continue examining the network setup bugginess theory and possibly try a few other bios images.   I'll check in again s00n...

-cYtr0x-
Title: Crashes With Xecuter 2 4976.02?
Post by: 007_xbox on June 12, 2003, 02:17:00 AM
QUOTE
you know, my friend had problems with his xbox locking up. all he did to fix it was go over his soldering job and move to the alternate d0. problem solved.

Im gonna giv this a go, see if it makes a difference.
Title: Crashes With Xecuter 2 4976.02?
Post by: cYtr0x on June 12, 2003, 03:22:00 PM
Yeah - I saw that, thanks!  It's worth checking out at this point, so  I may give that a go as well...

... Let me know how that works out for you.

-cYtr0x-
Title: Crashes With Xecuter 2 4976.02?
Post by: mrRobinson on June 13, 2003, 05:05:00 PM
i know it makes no sense but my problem was fixed when i went from the 4976.02 normal to the 4976.02_color_noani
its easy to test at least to see if it helps, before you rip your box open again.
Title: Crashes With Xecuter 2 4976.02?
Post by: nufan on June 14, 2003, 05:48:00 PM
sad.gif

we used to play it heaps so im gonna flash my bios back and see if that helps, although if i go back too far i will have to start patching games or something i guess.

at least we have given specs and let people know, the x2 team seems to be ignoring this problem i guess because they dont know how to fix it. At least bringing it to their attention like this may make them try and fix it.

Its an annoying problem and i wish i could fix it cause xbconnect kicks ass and i miss it sad.gif
Title: Crashes With Xecuter 2 4976.02?
Post by: wildcard on June 16, 2003, 01:23:00 AM
does anyone know if bios 4977 fixes this problem?

from mine and my friends experience, it seems like we have isolated this problem the bios.

both of us have used D6 bios prior, never had any freezes.  updated to 4976.02 bios, then all the problems with freezes, especially on XBMP 2.4.  disabled all IGR helped but still freezed with network cable in.  network cable out, i get no freeze.  my friend flashed back to the old 4975 bios and he says he get alot less freezes.  if this new bios does not relieve the freezing problem, im go back to 4975.
Title: Crashes With Xecuter 2 4976.02?
Post by: nufan on June 16, 2003, 01:52:00 AM
sad.gif really frustrating its such a random problem, on occasions IGR + connecting to others using xbconnect will be fine (note: it is 100% whenever network cable is UNPLUGGED) but most of the time IGR + connecting using xbconnect still causes freezing. Sad how x. team cant identify it so they can fix it with a bios sad.gif might have to go back to 4975 myself, although bios's after this have really added nothing anyway except small things such as disabling x2 IGR. (which isnt the problem anyway)
Title: Crashes With Xecuter 2 4976.02?
Post by: nufan on June 16, 2003, 02:48:00 AM
smile.gif BTW im running the older 3285 evoX dash since its meant to be more stable.
Title: Crashes With Xecuter 2 4976.02?
Post by: robg on June 16, 2003, 04:13:00 AM
I have changed to the Avalaunch dashboard and all my lockups have now stopped.  My Xbox would always lock up in XBOX Media Player 2.4 with the Evox dashboard when I tried to access my network share.  Now I am using the Avalaunch dashboard I have no problems at all with the lockups.  Admittedly, Avalaunch is still very much in its beta stages at the moment but appears to be getting updated quite often, unlike the Evox dashboard.  I don't think I will be changing back to Evox, Avalaunch is my dashboard of choice now.
Title: Crashes With Xecuter 2 4976.02?
Post by: vampire.de on June 17, 2003, 07:33:00 AM
sad.gif
I tried and tried... no way, anytime I used the XBMP with ReLaX, the XBOX stopped and crashes.... mad.gif
Without the patchcabel... no problem at all.... uhh.gif
Today I tried another thing...
I changed the IP's for DNS in the network-section of evox.ini and config-xml of XBMP....
Before changing I used the IP of my SMC Router/Gateway for DNS. Now I use the real DNS-IP of my ISP....and -quiet please- no more problems.... everything works.... biggrin.gif

Here my configuration:
Pal-XBOX 1.1
120GB Samsung
Samsung DVD
LPC v3.0
X2 Bios v4976.02 256kb multi
Evox v1.8.3752
XBMP 2.4 06-14-03
ReLaX 0.76 Pre.
static IP

vampire
Title: Crashes With Xecuter 2 4976.02?
Post by: vampire.de 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

Title: Crashes With Xecuter 2 4976.02?
Post by: Skyron on June 22, 2003, 09:48:00 AM
tongue.gif
Title: Crashes With Xecuter 2 4976.02?
Post by: Fofer 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.
Title: Crashes With Xecuter 2 4976.02?
Post by: Fofer 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.)
Title: Crashes With Xecuter 2 4976.02?
Post by: Unreal7000 on June 23, 2003, 08:50:00 AM
OK seriously guys lets end this freakin discussion its been going on TOO long.
Title: Crashes With Xecuter 2 4976.02?
Post by: redrum374 on June 24, 2003, 10:15:00 AM
Question is everyone else here with the network lock ups running XP Professional?
Title: Crashes With Xecuter 2 4976.02?
Post by: sonik 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.
Title: Crashes With Xecuter 2 4976.02?
Post by: LateraLex 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..
Title: Crashes With Xecuter 2 4976.02?
Post by: Ubergeek on July 08, 2003, 06:34:00 AM
tongue.gif
Title: Crashes With Xecuter 2 4976.02?
Post by: Ubergeek 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
Title: Crashes With Xecuter 2 4976.02?
Post by: DuggyUK 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 :P

same here!
Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace 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
Title: Crashes With Xecuter 2 4976.02?
Post by: nufan 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?)
Title: Crashes With Xecuter 2 4976.02?
Post by: redrum374 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.
Title: Crashes With Xecuter 2 4976.02?
Post by: nufan 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.
Title: Crashes With Xecuter 2 4976.02?
Post by: smitty555 on July 15, 2003, 03:24:00 PM
My setup:
v1.1 Xbox
Matrix mod
X2 4976.02
Evox 3752
HD loader 1.1

I agree it is a network/link problem. The only time I get lock up's is when I try to load a game from HD or Original with it plugged into the network. If the cable isnt plugged in they work fine. If I use flashfxp to ftp to my box It works fine.

It is a huge pain in the azz if I want to play on Xlink or XBconnect because it takes like 5-10 minutes of rebooting before the game I want to play will load.
Title: Crashes With Xecuter 2 4976.02?
Post by: smitty555 on July 15, 2003, 03:26:00 PM
Oh yea, forgot. Once I do get it working, I can reboot to change games and it stays working. Its kinda like once it establishes the connection its ok.
Title: Crashes With Xecuter 2 4976.02?
Post by: LateraLex on July 15, 2003, 07:46:00 PM
I had this problem, and was told about an interesting solution.
When creating a bios image, whereas you would normall fill all 256KB banks with one Bios (4977) for example. If you havent done this, or don't know how there is a part on this tutorial.
The trick this time is to flash the first two slots with the 4976.02 and the second two with 4977. I have no idea why it works but it has cleared things up for me.
Title: Crashes With Xecuter 2 4976.02?
Post by: X-ace on July 16, 2003, 03:49:00 AM
QUOTE (LateraLex @ Jul 16 2003, 03:46 AM)
I had this problem, and was told about an interesting solution.
When creating a bios image, whereas you would normall fill all 256KB banks with one Bios (4977) for example. If you havent done this, or don't know how there is a part on this tutorial.
The trick this time is to flash the first two slots with the 4976.02 and the second two with 4977. I have no idea why it works but it has cleared things up for me.

Mods,

Isn't it time to merge this discussion with this one?
http://forums.xbox-s...ST&f=38&t=66706

So far I have assumed everybody has seen it. (If not you would want to.)
Title: Crashes With Xecuter 2 4976.02?
Post by: onthereal on July 19, 2003, 10:44:00 AM
My Setup
Xbox: v1.1
DVD: Philips
Hard Drive: Maxtor 160GB / 8Mb Buffer (Locked)
Mod Chip: X2.1 Pro (Header Pin Install)

I started off with a v1.0 that I bought used.  It FRAGed out of the box, so I returned it to the store and picked up a referb.  I installed my X2.1 Pro and 160GB HD right away. Using the chip's flash bios I reflashed the chip with x2_4977. I then used slayers install cd to format and install the new drive.  Once everything was done I started to HD Loader my games to the hard drive.
The box worked great for the first few days, and then came the lockups.  The first was during Halo after about 2 hours of play.  I just reset the box and began playing again.  The next day I bought my Xbox into work to show off the new dash and huge HD.  This time it locked about 1 minute after EvoX loaded.  Since then it has been up and down with no definitive pattern.  It will lock in game, loading game, booting bios, and just sitting idle at the dash.

Things I have done to try to fix it:
- downgraded EvoX
- disabled X2 & EvoX IGR
- tried all recommended BIOS combinations
- disconnected network
- tried different dash (MS, Avaluanch, MXM, neXgen)

None of these fixed the problem.  Since software didn’t seem to fix it, I started to look for possible hardware problems.  I started by returning the Xbox to a semi normal state, ie. run a retail game from DVD with the chip disabled.  This should remove the both BIOS and dash issues from the equation.  So I boot up Splinter Cell and start playing.  At ran for about 15 minutes and locked.  Thinking it might be a heat issue, I put the retail HD back in, did the 12v fan mod, and replaced the cheap thermal pad on the CPU with some Arctic Silver 3.  I was going to replace the thermal pad on the GPU as well, but I couldn’t get the heat sink off.  I put it all back together and tried again.  With these steps Splinter Cell played for about 1 hour, and then locked up again.  This time I said screw it.  I removed the chip, unsoldered D0 and put it all back together again.  It is now a stock out of the box Xbox.  I loaded Splinter Cell and played for the rest of the night, no lockups.
To my best estimation, I have eliminated software as an issue.  The CPU heat is a respectable 110F (Checked with EvoX).  The Xbox locks even when the chip is disabled, thereby removing hacked BIOS’s as the culprit.  This only leaves 2 things IMHO, my crapy soldering or chip incompatibility.  I will clean & resolder all points on the header block as well as D0.  I will also try the alternate D0 on the back of the MB.  I will also try cleaning the ground point to ensure solid connectivity.

I’ll let you know how it turns out.
Title: Crashes With Xecuter 2 4976.02?
Post by: nufan on July 19, 2003, 05:10:00 PM
thats wierd if taking network cable out didnt solve it, cause for most (if not all i think) here it goes sweet without network cable.

Maybe it is poor soldering or something? i dunno, i got mine done by a pro so yeah ;|
Title: Crashes With Xecuter 2 4976.02?
Post by: ThUgLoVe on July 21, 2003, 05:55:00 AM
Ver1.1 box
Matrix with some red X2 bios(cant get the mode 4's lights to come on)

i to am having this prob,but for me atleast it cant be the bios,overheating,chip,dash or anything like that,i had the xbox up and running with the same chip,bios,and dash for over 7mo's with not one lockup,i had my xbox hardwired to my pc for about 1week b4 XBMP 2.4 with no probs,then i got XBMP 2.4 and the day after i started getting locks and its goting worse ever since..

there has to be some file that XBMP 2.4 does something to or it adds a file that is couseing all of this(bc XBMP cant run in the background like a program on a pc could can it?)
how many ppl had the prob start after installing XBMP 2.4?
Title: Crashes With Xecuter 2 4976.02?
Post by: ThUgLoVe on July 21, 2003, 05:42:00 PM
Great point about the XBMP save i didnt think of that:)

also today my xbox was going crazy locking up left and right so i deleted the xbmp 2.4 folder and the system.bin file in E: TDATA and it still locked up alot so i then looked around in  E: TDATA and found some more files that i dont know what made or used them so i deleted them and i havent had not one lock up since,had a few black screens when coming back from ms dash,boxplorer but i think thats the new 3752 evox bc i never had that happen b4..here are the files(i deleted the folders and all but you might want to check and see whats in yours 1st)

E:-TDATA-4d530017-GlobalSettings
E:-TDATA-080275-adserverlist
E:-TDATA-4d530011-Registry-DefSett.ADR                                 E:-TDATA-4d530011-XDemos
E:-TDATA-4d530001-movielock
E:-TDATA-5553000c-audiovideo.par
E:-TDATA-5553000c-contentimage.xbx
E:-TDATA-fffe0000-music-ST

like i said i dont know what made or used these files/folders all i know is that as of now i havent had not 1 lock up since deleteing these files i even let my xbox set for 3hrs b4 turning it back on just now and it didnt lockup and it always locked up on "COLD" 1st boot..

i think we are getting close as to what is cousein all the lockups,if after you installed XBMP 2.4 that you started getting the lockups try what me and onthereal have tryed and see if it works for you and post back plz
Title: Crashes With Xecuter 2 4976.02?
Post by: onthereal on July 22, 2003, 12:49:00 PM
Part 3:

Ok, after hours of game play I figured what the hell, I'll watch a DivX avi on my now stable xbox.  About 20min into the movie... FREEZE!  DOH!!! NOT AGAIN!!!  I rebooted and loaded Splinter Cell from the HD... FREEZE!  This time I decided to delete everything related to XBMP.  I killed the F:AppsXBMP dir.  I killed the game save dirs on E:.  I even removed the reference line in the C:evox.ini.  I then rebooted the box once more.  BAM!! No more freezing.  I am now a firm believer that XBMP the cause of my particular problem.  I don't know how or why, but XBMP just will not work with my xbox.  For the record, I have tried v2.3, v2.4-Complex, v2.4-cvs-7.19.03.  Again, I will monitor the problem for a week or so and let you guys know if this is indeed "THE FIX".

Also, I was thinking we should compile a list of xbox details for those of us that are experiencing the random lockup problem.  The list should be as detailed as possible, listing all hardware specs and loaded software versions.  I think this will help us figure out what we all have in common that may be causing these freezes.

Example: (My Xbox)

Xbox Version: 1.1
Xbox Network State: Pluged in
Network Connected to: Netgear FS108 10/100 Switch
Hard Drive Make: Maxtor
Hard Drive Model: DiamondMax Plus
Hard Drive Size: 160gb
Hard Drive State: Locked
Mod Chip Make: X-ecuter
Mod Chip Model: X2.1 Pro
Mod Chip Install: Header Pin with Alt. D0
Mod Chip BIOS: X-ecuter 4977
Dashboard Make: Evolution-X
Dashboard Version: 1.8.3752

Additional software:
BiosCheck v2.10
boXplorer v0.96
ConfigMagic-Final
DVDX v2.0
FlashX v1.0
Px HDD Loader v1.2a
XBMP v2.4-Complex
Xpad Alpha 2
xToolBox v0.41
MAMEoX v0.71.2b
Pcsxbox v7.0

Possible Solution: Completely removed XBMP from the HD and game save area. (No Freezing for now)
Title: Crashes With Xecuter 2 4976.02?
Post by: nufan on July 23, 2003, 12:44:00 AM
tongue.gif

Xbox Version: 1.1
Hard Drive Make: Seagate
Hard Drive Model: Barracuda IV
Hard Drive Size: 80gb
Hard Drive State: Locked
Mod Chip Make: X-ecuter
Mod Chip Model: X2 Lite
Mod Chip Install: Wires
Mod Chip BIOS: X-ecuter 4977
Dashboard Make: Evolution-X
Dashboard Version: 1.8.3752

Additional software:
boXplorer v0.96
ConfigMagic-Final
DVDX v2.0
FlashX v1.0
Px HDD Loader v1.2a
XBMP v2.4-Complex
xbox FTP

Also i think its important to state network components etc.. and state that EVERYTHING WORKS 100% FINE WITH NETWORK CABLE UNPLUGGED (either unplugged from my xbox or unplugged at the switch)

Connected to: 5 port switch, in turn connected to ADSL ROUTER

Other Network components = 1 x PC running XP Pro 1 x PC running XP Home

Title: Crashes With Xecuter 2 4976.02?
Post by: onthereal on July 23, 2003, 07:27:00 AM
I adjusted the format to include network info.  I also added a possible solution section for stuff that might fix your particular lockups.
Title: Crashes With Xecuter 2 4976.02?
Post by: stodge64 on July 24, 2003, 07:08:00 AM
biggrin.gif but if it wos on the x2 bios and my network cable wos out it didnt crash. So i recommend using the evox bios if you have a networkcable in. biggrin.gif
Title: Crashes With Xecuter 2 4976.02?
Post by: sck on July 24, 2003, 07:19:00 AM
I think that's the same thing I'm getting. On the very first boot up, if I exit an app/emu it will freeze evox when it returns to the dash (and always at the same exact time, like 3-4 secs when the dash returns). After rebooting, I no longer get freezes. At first I didn't think it was the issue w/ evox and the network cable as I swore I got a freeze upon first boot w/ the network cable out, but I've just been using the system with the network cable removed and no longer get those freezes. So it looks like evox networking code is probably not renewing or releasing the ip properly that causes it to freeze up the xbox in conjunction w/ x2 4977. I'll probably be switching to Avalaunch once the next release is out, so we'll see if that eliminates the freezing issues ad it's annoying to plug/unplug the network cable. I was wondering, have any of you tried adjusting the setup delay for networking options and see if that helps at all?
Title: Crashes With Xecuter 2 4976.02?
Post by: Ubergeek on July 24, 2003, 07:42:00 AM
QUOTE (stodge64 @ Jul 24 2003, 04:08 PM)
the only problem with my xbox locking up wos the X-ecuter 2 4977 bios. switched it to the evox blue bios and hasnt crashed for about a week now. I put both bioses on my x2lite and switched it to x2 bios and crashed then switched it back to evox and hasnt crash yet.  biggrin.gif but if it wos on the x2 bios and my network cable wos out it didnt crash. So i recommend using the evox bios if you have a networkcable in. biggrin.gif

well if you'd read all the posts youd see that ppl have issues with evox bios also

this problem is software related not bios related - the problem is there are different fixes for different setups - there is no set fix

its all down to the fact that so many diff apps are trying to work together at the same time - and a confliction ensues

i still to this day havent seen this problem with my box and boxes ive tested - i wish to god i could see it
Title: Crashes With Xecuter 2 4976.02?
Post by: nufan on July 26, 2003, 03:32:00 PM
QUOTE (Ubergeek @ Jul 25 2003, 03:42 AM)
QUOTE (stodge64 @ Jul 24 2003, 04:08 PM)
the only problem with my xbox locking up wos the X-ecuter 2 4977 bios. switched it to the evox blue bios and hasnt crashed for about a week now. I put both bioses on my x2lite and switched it to x2 bios and crashed then switched it back to evox and hasnt crash yet.  biggrin.gif but if it wos on the x2 bios and my network cable wos out it didnt crash. So i recommend using the evox bios if you have a networkcable in. biggrin.gif

well if you'd read all the posts youd see that ppl have issues with evox bios also

this problem is software related not bios related - the problem is there are different fixes for different setups - there is no set fix

its all down to the fact that so many diff apps are trying to work together at the same time - and a confliction ensues

i still to this day havent seen this problem with my box and boxes ive tested - i wish to god i could see it

yeah i guess this is true.

what confuses me though is that my mates xbox has gone sweet for like a year at his place, will all his apps installed etc.. then he comes to my place, plugs it into my network and gets his first freeze ever.

this is suggesting to me that some xbox's dont like some routers ? or certain cable? i dunno but in my case anyway it seems to be a hardware issue somewhere rather than software or bios.
Title: Crashes With Xecuter 2 4976.02?
Post by: erexx on July 26, 2003, 11:45:00 PM
I have been using 4976.02 without any issues on 3 xbox's worth 3 different hard drives
and 3 different modchips for quite sometime without issue.

I use:
EvolutionX_V1_8_3752
RelaX_v075
Bios: 4976.02
IGR enabled on all three.

3 box’s: PC-Bioxx, X2 Pro and a Matrix

3 Hard drives: 60gig Maxtor, 120gig WD, and 120 gig Maxtor

All over a 100Mbit Static IP Lan

I recommend that you don’t use wireless you only asking for trouble.
(Maybe in the future but I am old I guess)

I could also use DHCP but Avalaunch, when i use it, likes to set its own DHCP address... grrr
.... btw can any help me fix this?

I delete and upload gigabyte avi's and games all the time to each Xbox as I test XBMP
as I fulfill the family’s requests....
(Backup games to HD, I use XBMP 5-7-03 and
xbmp_2.4_cvs_compile_xbins_7-19-03 looks good so far on one Xbox right now)

Network cables are always connected but random(?) remote control pauses exist in every version of XBMP I use after 2.2
(thank god others are admitting to that problem now as well)

I can only think this is a combination of more than few problems:

1) Wireless networks ~ your only asking for trouble
2) Particular network hardware compatibility issues (routers and hubs)
3) XBMP pauses in remote control, doesn’t crash on me and streaming never stutters or pauses.
4) Get and modify the original release of any bios release or risk someone else’s mistake.
5) Bad download of various binaries... don’t assume that what you got is good.

A long post I know... just my $5 dollars worth... ha!....
Title: Crashes With Xecuter 2 4976.02?
Post by: ThUgLoVe on August 05, 2003, 04:06:00 AM
sad.gif..




1.1 NTSC Xbox
Matrix mod  with X2 4977 Custom bios
EVOX 3752
80gig Matrix Hdd
SMC nic card
XP Pro
Title: Crashes With Xecuter 2 4976.02?
Post by: ThUgLoVe on August 06, 2003, 07:08:00 AM
Quote
nothing can be done about it
Title: Crashes With Xecuter 2 4976.02?
Post by: dzv on August 06, 2003, 07:13:00 AM
I don't actually suffer from this problem, but for those of you that do, here's something to try...

Backup your E drive to your PC, then delete everything in the cache, udata, and tdata folders.  Also delete everything in the X, Y, and Z drives.  This is essentially clearing out all the temp and cache files on the Xbox HDD.  It's possible that something left behind by one program may be causing problems.  It might be a long shot, but it's worth a try, is it not?
Title: Crashes With Xecuter 2 4976.02?
Post by: ThUgLoVe on August 06, 2003, 07:21:00 AM
my xyz's are always cleaned out and my e drive was always the same b4 i connected the network and after so i doubt its something like that.also when i come back from a game it locks up around 1-3sec's after the dash shows up on screen,does anyone know what evox it doing around this time?

bc if we could fig out what it is doing at the time of lockup then maybe we could fig out what is locking it up
Title: Crashes With Xecuter 2 4976.02?
Post by: nufan on August 06, 2003, 11:31:00 AM
tongue.gif
Title: Crashes With Xecuter 2 4976.02?
Post by: nufan on August 06, 2003, 09:50:00 PM
tongue.gif

Hope this helps, will report back when i get my new router and let you know if my longggggg lasting problem finally has an end to it.

cheers
Title: Crashes With Xecuter 2 4976.02?
Post by: Tailwind on August 06, 2003, 11:44:00 PM
QUOTE
sorted out my problem (i think and hope), thought id post just in case it can help anyone else


Nufan, buying a new router will NOT solve the issue.

I have a 100 mb switch connected to a pc and my xbox, the uplink is going to my ethernet-router (with buildin 100 mb hub), where another machine is plugged in.

Basiccally my xbox is connected to the switch.

My guess is that OR the xbox sends out broadcast packaged OR any other device on the netwerk (e.g. router, pc, printerswitch etc.)

I use static ip on my xbox. Does your router give DHCP addresses out and is your Xbox configured to use DHCP?

My suggestion is to perform a a network snif to see what the Xbox is sending/or recieving  at time it freezes. Because my problem is fixed, it's no use to do it.

I think it's broadcast related. Because it is random the lockups, it is explainable because a broadcast does not always have the same time. It could also be a dns-resolving issue. Have anyone already tried to remove the dns entries from the xbox? If not, try this and see what happens.

nufan: switch to static ip, use the blue noani, teurn of igr in evox (use igr from bios), use the latest evox version.

If someone knows how to snif, snif the thing (3 logs --> in, out, in/out) I can analyse it.
Title: Crashes With Xecuter 2 4976.02?
Post by: nufan on August 07, 2003, 12:10:00 AM
tongue.gif
Title: Crashes With Xecuter 2 4976.02?
Post by: Scubix on August 10, 2003, 02:00:00 AM
QUOTE (nufan @ Aug 7 2003, 09:10 AM)
i realise all that, i hvae tried all that, blue no ani etc...

since unplugging the router fixes my problem, i cant see how im wrong in assuming the ROUTER is causing the problem. Especially since my mate as a different router (the one im getting) and has no problems till he comes to my place.

....

im not losing any money buyin the new router anyway as im selling the old one and getting this new one. If it doesnt fix it then there really is nothing i can do. But the fact that when i disconnect the router (still leaving everything else on the network connected via the switch) must mean thats the problem. This new one is hopefully gonna fix it, if not well i have a new router tongue.gif

I dont even have a hardware router, and i have the same probs, so i doubt its related to the router itself. I just use a 100 Mbits switch connected to a linux pc (internet conencted to this pc).
I think i has something to do with the network traffic, just dont know what. Probably not DHCP stuff, cause i dont use dhcp, all static here smile.gif
Title: Crashes With Xecuter 2 4976.02?
Post by: ThUgLoVe on August 12, 2003, 05:09:00 AM
yeah it cant be a router or a hub issue bc i have nether,my box is hooked up stright from a nic card in my pc..

is there anyone even working on a fix for this besides us siting here  talking about it?

Title: Crashes With Xecuter 2 4976.02?
Post by: mrRobinson on August 14, 2003, 08:42:00 AM
QUOTE (ThUgLoVe @ Aug 12 2003, 09:09 AM)
yeah it cant be a router or a hub issue bc i have nether,my box is hooked up stright from a nic card in my pc..

is there anyone even working on a fix for this besides us siting here  talking about it?

It can be a router or a hub issue being that when most people disconnect the cable from the xbox problem goes away.  this problem seems to take on many "forms" like a cancer.  if you read every post in this thread you'll see many "fixes" for it that have worked for one or two people but nothing that works for all.  Chances are, somewhere in here is a fix that would work for you.  
Title: Crashes With Xecuter 2 4976.02?
Post by: nufan on August 16, 2003, 02:30:00 AM
smile.gif