Print

[Swift1]

No freezing problems here at all

Setup is as follows:

Xbox 1.0
EvoX 1.8.3752
Chameleon flashed with "4977 red noani" using EvoX's bult in chameleon flashing commands.
I use a Static IP with a default Gateway of 192.168.1.1
SwapDate = Yes in EvoX
IGR Disabled in EvoX

I also have no problems using Samba shares in XBMP and all the emu's

The only time i've ever experienced my Xbox locking up is when i've accidently selected to search a Relax share in an Emu. Xbox would immediately freeze, but then again i don't have Relax setup on the PC as i much prefer Samba shares. So the locking up could be down to it looking for something that ain't there causing a crash of the emu.

Also if people are having problems with in game lock up's you have to ask yourself what drive is in your Xbox? If it's a Thompson then most likely that's your problem. I used to think the bios or my chip was at fault until i upgraded to a Samsung drive. Once i installed the Samsung i went back and reupped every game that refused to boot or had locking up problems in game. Now every game works without so much as a hiccup! The Thompson drive is a piece of sh*t! Get rid of it. It can't read files accurately for the life of it and this is off original discs. I can't speak for the Phillips drive, i've yet to test it's ripping capabilities as i have yet to upgrade my second box to a larger HD and mod chip. But i'm guessing it can't be as bad as the Thompson.

Some of the problem games, all PAL btw, off the top of my head for the Thompson were:

Rocky (would lock-up during a fight)
James Bond - Nightfire (freeze on the progress meter upon loading the game)
Moto GP2 (Refused to load at all)
Wolverine's Revenge (Refused to load at all)
Soul Calibur 2 (JAP-NTSC) - (JAP error message on boot up)

There are others and these results have been confirmed with other Thompson drives. Your mileage may vary but the Thompson can not read as accurate as the Samsung.

Hope this info has helped.

[madcake]

This goes to m3talslug ->  In your evoX.ini, is there RDTOOLS enabled? If so, disable it and check if your stuff still freezes when launched from evoX. If it is already disabled .. well, then i'd say good bye to evoX and welcome to Avalaunch and MXMDash :-)

-cake

[Ubergeek]

mmm disabling RDTOOLs

thats a good point - all try that too

this problem is what I excpected all along - not a bios issue

[Devil-Man]

so yeah uber, i would lay $100 bill on it being everyone using evox dash and it NOT being a bios issue.

[GuySmily]

I have been having crashing problems ever since I switched motherboards.  I have gone through 3 1.1 boards..  My first motherboard had InNetISCS writtin on the top, and it never ever crashed without reason.  Since I switched to one that had PulseJack on the side (opposite the port), I started crashing randomly (around 70%) when I returned to EvoX by ANY IGR with the network cable attached.

Hm.. gonna be late for school, I'll finish there.

[sck]

I switched to avalaunch finally and the freezes are gone, but like you m3talslug, I dislike the additional features of the other dashes. Evox is a plain and simple dash which has a stable ftp, and nice bios flasher.  But the only choice it seems to get rid of the freezing is to switch dashes.

[Ubergeek]

you didn't mention if you had tried ANY of the fixes I posted - this is the first thing you should be doing - then posting results

and its nothing to do with "pc-power-conduit"

[mrRobinson]

Ubergeek posted the second thread that was created about this issue and I always found the first one more helpful.
This is it for those who wish to review:
Original Thread

oh, and i could swear there were people who left everything the same and switched dash boards and the problem didn't go away.  and in my case, i never had the problem, changed my bios and had the problem, then eventually fixed it again with a 4976.02 red noani.

I really think its a combination of factors that cause people to notice this not just one buggy piece of software.

[athloni]

I'm SURE I solved the problem !!!!!!!!

Everyone with this problem:

After IGR, the box freezes while trying to launch another game /program.

It is an EVOX BUG in combination with a router !!!!

DISABLE SNTP BIJ CHANGING THIS SETTINGS IN EVOX.INI:

[Clock]

JumpToMsDash   = Yes
JumpIfNoLink   = Yes
Use24      = Yes
SwapDate   = No
SNTP_Server   = 216.244.192.3

Also be sure to flash your BIOS with EVOX. And flash all banks with the SAME BIOS. Flashing the BIOS wit 2 different BIOS versions will also create the same freezing problems.

This solved my problem, and also for 2 frends of mine.
So I'm sure this does the trick !!!!

I'm using:
Xbox version 1.0 PAL
Latest EVOX
xecuter2_4978.3

[GuySmily]

None of the suggested fixes throughout this post and others have worked.  As I said earlier.. My original 1.1 motherboard was completely stable.  I have switched motherboards twice and the problem has stayed with me..

1) Type of hack used (modchip / tsop / exploit)
Originally used matrix, now I have a chameleon

2) Motherboard / MCPX version / dashboard used / bios version
1.1 mobo, MCPX version?.. EvoX 1.8.3752, x2 4977 and evox d6 (many xbtool mods done.. color, boot location, dvd check, etc - no effect)

3) Your windows Network protocol setup
My PC and xbox both have static IPs, subnet 255.255.255.0, gateway 192.168.1.1.  The PC has DNS servers set up, but the xbox is left blank.

4) EXACT description of crash
I usually only crash when leaving or returning to EvoX.  I've been messing with the ms dashboard a lot recently, and I find that I crash very very frequently when I try to run it..  I seem to get 1 successful run, then 1 hang at the loading screen.  Avalaunch didn't fix the problem, and launching from boxplorer also doesn't help much.  I get stuck at the blank screen before the app I'm trying to run would load.  Games never seem to crash though.  Back to the ms dashboard..  If I forget to resign the xbe or make some other mistake, I get to the error screen.  If I crash, I know I did it properly.

As everyone else says, a reboot fixes the problem completely.  And of course I have no problems when I disconnect the ethernet cable.

[Terrorbyte]

I've tried all of the suggestions (including Ubergeek's suggestions FIRST) and have not been able to solve/resolve my freezing issues.  The identical freezing behaviors result when using either the x2_4978.03 OR the x2_4977 (blue Noani, among all the others floating around) BIOS.  I almost always create my own color BIOSes, I don't use any "pre-modified" BIOSes, like the ones found on xbins.  I haven't really used any of the other BIOSes (i.e. Evox D.6, etc.) because they blow balls.  

Here's my particular setup:

- X-Ecuter 2.2 Lite (x2_4978 on first 512k, x2_4977 on the other half of the memory bank)
- 1.3 XBOX, Evox 1.8.3752 (I know it's a shitty dash but I'm used to it and don't want to waste time with the other dashes...yet)
- Linksys BEFSR41 Router, 192.128.1.2-192.168.1.254 IP range used on my network PCs, etc; using STATIC IP (tried dynamic, same problems); no funky network shit or anything else running (like gay ass Norton software firewalls, etc)
- my box (among other 1.3s I've seen with my same similar setup using the network cable) crashes when it FIRST loads a game, namely Tony Hawk 4 (Halo usually crashes, but it takes a bit longer, usually once the game loads it upchucks) or the FCE Ultra emulator (v10).  The crash will generally occur immediately after I load the emulator or game, and then I have to reset my friggin XBOX.  Usually to fix the damn problem I hit the eject button which resets my box, then launch whatever crashed once again, and the crash NEVER happens after that.  When the network cable is unplugged, everything works fine, no crashing, even with IGR enabled.  Disabling/enabling IGR seems to have no effect or bearing in my particular case.  I know this is not an isolated case because several other xboxes (using different modchips, but the same BIOS and dashboard) exhibit the same behavior when plugged into a network.  

I've practically given up troubleshooting this shit because I can work around it, but it's still an annoyance.  Hopefully sooner or later someone will figure out an exact cause.  I'll continue to try out other suggestions as I get time, and if I ever do get success I'll post here.

I suppose if the source of the freeze is rooted in Evox then that's my problem and I'll eventually have to use avalaunch or MXM, or whatever.

[nufan]

terrorbyte, change your ways and get rid of evoX. Im 90% sure it will fix the problem for you. I was used to evoX too but dont you think avalaunch is worth it considering it will FIX YOUR PROBLEM? plus u can do everything u need to in ava, support is excellent, its a great dash. Get avalaunch, put avadash.xbe in your C: Drive and ENJOY NO FREEZING.

Could i put it any more simply ? its not hard dude, its your own fault if you still get freezing.

[m3talslug]

Anyone get a chance to try the new EVOX dashboard to see if it fixes the freezing yet?  I haven't had the time to switch from MXM... but it's a switch I'd gladly make since MXM is just too damned painful to configure.

[sck]

I just tried it, however I had my xbox left off for 10 mins or so after turning it on to upgrade. XBMP did not freeze upon startup, but it now freezes upon exit; non network apps used to have this problem. so it seems that startup freezes are gone, but the return to dash freeze takes its place. I'll test some more from a cold boot tomorrow morning. But since they actually updated evox they will hopefully fix this annoying bug. If MXM and Avalaunch work, this should be an easy fix. It has to be the network init code.

[san9jay]

i can also confirm its evox and not the bios. I switched to using XBMP as my dash and the problems went away.