Okay first off thank you both cravavr and easybuy for the tips. Updating the bios did not work afterall.
Yes, I do have a brown power cable, but unfortunately I can't find my manufacturer's code anywhere (I took the sticker off completely to open the box and lost it shortly thereafter). However I did just run across this on the main page of xbox-scene:
| QUOTE |
More Xbox v1.6B Updates: Lockups caused by Hynix RAM and Philips DVD? >> From TeamXecuter.com:
| QUOTE | Some interesting finds.... All v1.6B's that we, and others have found to freeze at dash or during game have Hynix RAM chips and Philips DVD drives. All v1.6B's that we found to work fine have Samsung Ram chips and Samsung DVD drives. Feedback is appreciated to further confirm these findings.....
Also this was posted by XOR, A moderator on the Smartxx forums Quote: How ironic is this... I've just had a 1.6 with a brown Eject lead... Anyway, did everything as per normal, but wouldn't work, locking up on flubber... Anyway in cases where I've seen this happen before I decided to change the HDD for an older one pulled from a 1.1 unit. In it went, formatted it up, installed the software, locked the drive, bingo it worked... Currently testing the HDD now, and it's already showing hundreds of physical errors on the drive (this was new out of the box?), so just re-affirming my initial thought, bad HDDs... If someone gets an equivalent by all means do what you can to fix your own issues, but don't discount that the HDD itself may be bad, regardless of if the XBOX still has it's selaphane on and had never yet been used.
We tested new hard drives on all the machines that lock up and it didnt make any difference - however its another thing for users to check. We have found the bug in FlashBIOS and will hopefully release an update over the weekend. We should also be releasing a new X2 and X3 bios shortly.
|
(November 5 16:27 EST) - (direct link to article) (Posted by:: XanTium)
|
Now some of that really doesn't apply to my situation, I have the Toshiba Samasung DVD drive, but I do have Hynix Ram in my box.
First thing I'm going to try is taking off the blue cable from the chip, which is infact running right over the top of one of the Hynix ram chips. If this works I'll try to re-route it another way like cravavr suggests. I'd really like to keep it since I was also planning on actually adding a permanent port for the USB plug right there next to the Ethernet port.
I have high hopes that this will fix the problem especially since this only happens when I boot up using the mod chip. I have yet to have any problems when booting using the stock bios from MS.
Thanks again.