xboxscene.org forums

Pages: 1 ... 7 8 [9] 10

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

smitty555

  • Archived User
  • Newbie
  • *
  • Posts: 38
Crashes With Xecuter 2 4976.02?
« Reply #120 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.
Logged

smitty555

  • Archived User
  • Newbie
  • *
  • Posts: 38
Crashes With Xecuter 2 4976.02?
« Reply #121 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.
Logged

LateraLex

  • Archived User
  • Jr. Member
  • *
  • Posts: 78
Crashes With Xecuter 2 4976.02?
« Reply #122 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.
Logged

X-ace

  • Archived User
  • Sr. Member
  • *
  • Posts: 283
Crashes With Xecuter 2 4976.02?
« Reply #123 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.)
Logged

onthereal

  • Archived User
  • Newbie
  • *
  • Posts: 16
Crashes With Xecuter 2 4976.02?
« Reply #124 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.
Logged

nufan

  • Archived User
  • Full Member
  • *
  • Posts: 105
Crashes With Xecuter 2 4976.02?
« Reply #125 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 ;|
Logged

ThUgLoVe

  • Archived User
  • Full Member
  • *
  • Posts: 138
Crashes With Xecuter 2 4976.02?
« Reply #126 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?
Logged

ThUgLoVe

  • Archived User
  • Full Member
  • *
  • Posts: 138
Crashes With Xecuter 2 4976.02?
« Reply #127 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
Logged

onthereal

  • Archived User
  • Newbie
  • *
  • Posts: 16
Crashes With Xecuter 2 4976.02?
« Reply #128 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)
Logged

nufan

  • Archived User
  • Full Member
  • *
  • Posts: 105
Crashes With Xecuter 2 4976.02?
« Reply #129 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

Logged

onthereal

  • Archived User
  • Newbie
  • *
  • Posts: 16
Crashes With Xecuter 2 4976.02?
« Reply #130 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.
Logged

stodge64

  • Archived User
  • Newbie
  • *
  • Posts: 31
Crashes With Xecuter 2 4976.02?
« Reply #131 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
Logged

sck

  • Archived User
  • Newbie
  • *
  • Posts: 37
Crashes With Xecuter 2 4976.02?
« Reply #132 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?
Logged

Ubergeek

  • Archived User
  • Hero Member
  • *
  • Posts: 686
Crashes With Xecuter 2 4976.02?
« Reply #133 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
Logged

nufan

  • Archived User
  • Full Member
  • *
  • Posts: 105
Crashes With Xecuter 2 4976.02?
« Reply #134 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.
Logged
Pages: 1 ... 7 8 [9] 10