| 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. |
| 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) |
| 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... |
| 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 |
| 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. |
| 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?? |
| 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.. |
| 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. |
| QUOTE (B@se @ May 30 2003, 08:50 AM) | ||
My E drive has 5gb of free space, but it still freezes when my network cable is plugged in |
| 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. |
| 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- |
| 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 |
| 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. |
| 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. |
| QUOTE (Ubergeek @ Jul 25 2003, 03:42 AM) | ||
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 |
nothing can be done about it
| QUOTE |
| sorted out my problem (i think and hope), thought id post just in case it can help anyone else |
| 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 |
| 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? |