problem with games freezing

[timelesspa 0]

annoyingly my xbox has started freezing while playing games, the first time it happened was while playing bullet witch, prior to the freeze my wired controller kept disconnecting the game glitched when l died and upon trying to return to the dash it froze and the controller lights went out. l dont believe there is a break in the while tho as the controller was recently replaced due to just that issue however the controller does seem pretty loose in the port tho it was the first time it happened, however l started playing the new metal gear solid game went past the cut scenes and played about 5mins into the game tho while l didnt get any controller disconnections the game suddenly froze the controller lights went off and l had to restart the xbox.

lve no clue why the last 2 games caused this issue as to my knowledge heatwise the console never left the never went beyond above approximately 45c, the games are all extracted to the xbox hard drive and the only difference between the games is one asked me to install (the second one to mentioned) which l accepted stupidly so there might be another version of it installed likely in god format which l will have to check.

the one other thing l can tell you is that recently l upgraded the dash which required me to update to the latest dashlaunch so l could use the update method over lan which to my knowledge went fine as l updated to play Thief which required the latest dashboard and l played the game from start to finish with no issue whatsoever after the update, castelevanias only issue was one that allegedly is pretty common where l kept on getting an undefined error  (l played that after the update as well according to google). the dash update method l used was posted elsewhere using xebuild which contained the update files which required me to run a *.bat file however from what l see it only runs the command to update the xbox that would normally have been used for going through the command line (l was just being lazy as l couldnt get jrunner to work on my OS (kept on bitching that it was a 16bit program trying to run on an incompatible 64bit OS (Win7).

this issue is confusing me, lm wondering if its controller related if its disconnecting so fast the console is picking it up as a problem. l dont think its a RROD issue tho l couldnt tell if it was due to the LEDs being modded (ld ask the original modder but lve not seen him round for a few weeks, and lve been playing on it fine for the last six months) temps always seem reasonable, the only other thing l can say is l have been using retrobyte trainers for inf ammo cheats and the required TU updates.

on a final note of interest, lve no clue about the wiring and while lm easily able to flash phat consoles l dislike opening up to take pictures of the wiring however l can tell you that the board is a Jasper (512mb version l believe) and that l believe the heatsink was taken off the falcon that died that l originally had as it was a better heatsink than the stock one. any help or information would be greatly appreciated.

[Swizzy 2084]

Your problem could be related to a write error on the nand (highly unlikely), RROD problems, HDD Problems, or simply game problems... Could you post your dashlaunch settings here? They may give us a clue as to what's going on...

RROD Problems ussually effect most/all modern games (meaning, the ones that are kinda recent) as they tend to push the console more then older ones...

HDD Problems could cause all kinds of wonky things, mostly it causes data corruption which in turn could case a fatal crash, which dashlaunch tries to handle if that option is enabled, and normally the console freeze on such errors which can't be handled...

[timelesspa 0]

lm assuming you want my launch.ini

strangely it has very little in it compared to what l usually see posted unless it has something to do with the update tho l did see 2 *.ini files with launch in their title so l will post both.

 

heres what the launch.ini contains

 

[QuickLaunchButtons]
Default = hdd:\FreeStyle\default.xex
[settings]
nxemini = true
pingpatch = true

 

and heres what the other file titled info_launch.ini

 

 

; launch.xex V3.0 config file
; parsed by simpleIni http://code.jellycan.com/simpleini/
; currently supported devices and paths:
; internal hard disk    Hdd:\
; usb memory stick      Usb:\
; memory unit           Mu:\
; USB memory unit       UsbMu:\
; big block NAND mu     FlashMu:\
; internal slim 4G mu    IntMu:\
; internal corona 4g mu MmcMu:\
; CD/DVD                Dvd:\     (not recommended to use this one)
; buttons can point to any xex, or any CON with default.xex in it on any of the above devices
; note that Right Bumper is ALWAYS default to return NXE
; if you want to assign an additional one, use the path Sfc:\dash.xex ie:
; BUT_A = Sfc:\dash.xex

; all comments and fields in this file are optional, you can remove anything you don't need
; sorry for any double negatives
; njoy, cOz

; example entry
; Default = Hdd:\FreeStyle\default.xex
[Paths]
BUT_A =
BUT_B =
BUT_X =
BUT_Y =
Start =
Back  =
LBump =
RThumb=
LThumb=
; Default is what loads when you hold no buttons
; leave this blank if you want NXE as default
Default =

; at boot time, default can be overridden based on how the console is turned on
; if you start with wired/wireless/IR guide button, this item if existing will be used instead of default
; note that the Guide item is ALWAYS overridden by option: remotenxe = true
Guide =
; if you power on with the button on the front of the console (or the power button on a remote if remotenxe is not set to true)
; this item will be used instead of default
Power =

; if set, going to system settings from HUD will run this app, override with Right Bumper
Configapp =

; if set, this will be run as a title before any other option occurs, does not get circumvented by held buttons or default
; guide/power opts are processed after this; intended for a short video player to allow replacing bootanim
Fakeanim =

; by default this only dumps to UART, setting a file here will cause unhandled exception info to be dumped
; as text to a file. Same path restraints as the quick launch buttons.
; if exchandler is set to false, this option does nothing.
; note that this uses the first drive of the class found, so if you use usb: and have more than one usb device
; it may wind up on any of the usb devices depending on which was enumerated first. The path for the file is only
; checked on boot, so the device must be present at power on and at crash time for this to be effective
; ie: dumpfile = Usb:\crashlog.txt
Dumpfile =

; example plugin entry
; plugin1 = Usb:\plugin\aplugin.xex
[Plugins]
plugin1 =
plugin2 =
plugin3 =
plugin4 =
plugin5 =


; these options are never used directly by dash launch but serve to give the configuration program
; a place to keep these values; note that things like ftp and udp servers are only running while installer is running
[Externals]
; if true, the configuration application will start a FTP server (user/pass: xbox)
; if not present default is FALSE
ftpserv = false

; if ftpserv is true, this is the port that will be used by the FTP server
; if not present default is 21
ftpport = 21

; if true, the configuration application will start the xebuild update server
; if not present default is FALSE
updserv = false

; if true, the configuration application will start in launch mode instead of options mode
; if not present default is FALSE
calaunch = false

; if true, temps in installer and in guide (shuttemps option) will be shown in fahrenheit instead of celsius
; if not present default is FALSE
fahrenheit = false


[settings]
; if true, brining up miniblade in NXE and then pressing Y will cause launch.xex to relaunch for you
; note you must release Y button then press desired QuickLaunchButtons after or use default item
; if not present default is TRUE
nxemini = true

; if true ping limit will be removed for system link play (thanks FBDev!)
; if not present default is FALSE
pingpatch = false

; if true (most) xbla will no longer need yaris patching (thanks mojobojo!)
; if not present default is FALSE
contpatch = false

; Normally when a fatal error occurs the xbox will just freeze, setting this to false will cause a reboot or powerdown
; setting to TRUE will also disable the unhandled exception filter which tries to intercept recoverable unhandled exceptions with exit to dash
; if not present default is FALSE
fatalfreeze = false

; when fatalfreeze is set to false, setting this to true will cause the box to reboot, setting it to false will instead have the box shut down
; note that this option does NOTHING when fatalfreeze is set to true
; if not present default is FALSE
fatalreboot = false

; setting this to true will cause the box to reboot (soft reboot) the way it was intended to
; on jtag ONLY set this to true if using blackaddr's reboot fix for SMC, else on reboot you will get E71 and corrupted dash/video/etc settings
; if not present default is TRUE
safereboot = true

; when set to true, it is possible to hold RB when launching a game to have the region that the game gets from xam spoofed
; if not present this is set to FALSE
regionspoof = false

; when regionspoof is true, you set your region here in hex preceding the value with 0x, for example devkit would be region = 0x7fff
; if not present but regionspoof is set to true, this is set to 0x7FFF
region = 0x7FFF

; when set to false, ejecting a dvd video or game returns you to your default item, set to true to auto exit to NXE
; if not present this is set to FALSE
dvdexitdash = false

; when set to false, using the exit item in an XBLA game returns you to your default item, set to true to exit to NXE arcade menu
; if not present this is set to FALSE
xblaexitdash = false

; when set to true, using miniblades system setting options will not exit to NXE
; if not present this is set to FALSE
nosysexit = false

; when set to true, miniblades will not appear... ever (requested as child saftey measure)
; note that using this option overrides everything in dash launch that relies on miniblade exits to function
; if not present this is set to FALSE
nohud = false

; when set to false, xbox will be capable of finding system updaters
; if not present this is set to TRUE
noupdater = true

; when set to true,  dash launch will put all debug strings out to uart
; if not present this is set to FALSE
debugout = false

; when set to false, dash launch will not attempt to handle last chance unhandled exceptions
; if set to false, exceptions will also not be dumped to the dumpfile
; if not present this is set to TRUE
exchandler = true

; if set to true, this will block the console from resolving LIVE related dns
; if not set this value will be TRUE
liveblock = true

; if liveblock is set to true, this will block the console from resolving all MS related dns
; setting this to TRUE will also block apps like freestyle from accessing things like cover images
; *** note that if NO INI is present for launch.xex, this is set to TRUE
; if not set this value will be FALSE
livestrong = false

; when set to TRUE the X (guide) and power button on IR remotes will cause the xbox to boot to NXE instead of default item
; note that powering on with the windows/start button automatically goes to NXE's media center now regardless of how this is set
; if not set this value will be FALSE
remotenxe = false

; when set to TRUE all USB drives will be polled at hddtimer intervals for the file "alive.txt" in their root
; if the file exists, it will be recreated and 16 random bytes written to it on each poll which should keep drives from spinning down
; if not set this value will be FALSE
hddalive = false

; in seconds, the interval between when USB devices will be polled for "alive.txt" file
; if not set and hddalive is set to TRUE this value will be 210
hddtimer = 210

; attempts to disable popups related to signing in, like "live is blocked" and similar
; !! WARNING OTHER THINGS DO USE THIS DIALOG AND DETECTING THAT IT'S A LOGIN DIALOG MAY NOT BE PERFECT !!
; !! to sign into live profiles other than auto signing on boot you MUST accept the 'check live for updates' dialog BEFORE enabling this option !!
; if not set this value will be FALSE
signnotice = false

; when you hold guide button to shut down xbox, normally the 'cancel' option is selected
; setting this to TRUE will cause the shutdown option to be auto selected instead
; !! WARNING OTHER THINGS DO USE THIS DIALOG AND DETECTING THAT IT'S SHUTDOWN DIALOG MAY NOT BE PERFECT !!
; if not set this value will be FALSE
autoshut = false

; when you hold guide button to shut down xbox, normally a dialog comes up
; setting this to TRUE will cause the console to shutdown instead of show a dialog
; !! WARNING OTHER THINGS DO USE THIS DIALOG AND DETECTING THAT IT'S SHUTDOWN DIALOG MAY NOT BE PERFECT !!
; if not set this value will be FALSE
autooff = false

; 14699+ has native http functions, but you are forced to be logged into use them
; this patch removes that restriction, set to false to disable it if you have any problems
; if not set this value will be TRUE
xhttp = true

; when tempbcast is set to TRUE the raw temp data from smc will be broadcast over UDP at temptime second
; intervals on port tempport
; if not set this value will be FALSE
tempbcast = false
; if not set this value will be 10
temptime = 10
; if not set this value will be 7030
tempport = 7030

; when set to TRUE all titles will have the insecure socket privilege
; if not set this value will be FALSE
sockpatch = false

; when set to TRUE dash launch will not erase launchdata before launching a quick launch item
; if not set this value will be FALSE
passlaunch = false

; when set to TRUE various functions will be spoofed to make firmware think it's connected to LIVE
; this does not compensate for the fact that it cannot contact LIVE servers
; setting this to TRUE forces liveblock to TRUE
; if not set this value will be FALSE
fakelive = false

; when set to TRUE network/cloud storage options should not show up in disk dialogs
; if not set this value will be TRUE
nonetstore = true

; when set to TRUE a snapshot of the console temperature data will be displayed in the console shutdown dialog (displayed when guide button is held)
; !! WARNING OTHER THINGS DO USE THIS DIALOG AND DETECTING THAT IT'S SHUTDOWN DIALOG MAY NOT BE PERFECT !!
; enabling this option disables autooff
; if not set this value will be FALSE
shuttemps = false

; when true, any devkit profiles on the console will not appear as corrupt and can be used
; any changes such as saving games or getting achievements will resign the profile with the current/retail keyvault
; this seems not to affect glitch/jtag dev crossflash, but could affect these profiles on true devkits
; if not set this value will be FALSE
devprof = false

; when true, system link data will be encrypted for communication with devkits
; if not set this value will be FALSE
devlink = false

; when true dash launch will perform automatic disk swapping
; WARNING!! do not enable if you use FSD or swap.xex for this !!
; if not set this value will be FALSE
autoswap = false

; when true, disables kinect health pseudo video at game launch
; if not set this value will be TRUE
nohealth = true

; when true, disables dash locale setup screens when settings already exist
; if not set this value will be TRUE
nooobe = true

; when true dash launch will automatically enable fakelive functionality only during official dash and indie play sessions
; if not set this value will be FALSE
autofake = false

tho l will note if the second file is just an example (l wasnt sure) then where else could dashlaunch information be saved. reason l ask is that all prior settings l made still seemed to be saved from the previous version for example l turned on the live block function.

[Swizzy 2084]

lm assuming you want my launch.ini

strangely it has very little in it compared to what l usually see posted unless it has something to do with the update tho l did see 2 *.ini files with launch in their title so l will post both.

 

heres what the launch.ini contains

 

and heres what the other file titled info_launch.ini

 

tho l will note if the second file is just an example (l wasnt sure) then where else could dashlaunch information be saved. reason l ask is that all prior settings l made still seemed to be saved from the previous version for example l turned on the live block function.

The first ini is the one we're interested in...

The fact that it contains less lines isn't a big problem, it's quite ok that it contains less information then the info one, because it means that the other settings are set to their defaults...

You should check that you don't have a launch.ini in your usb devices, and put the launch.ini you want to use in hdd1

Your settings should be ok tho as it uses mostly defaults...

If possible, connect your HDD to your computer and check the S.M.A.R.T status of it... my guess is that it may be acting up... or it's a write error, in which case i'd recommend trying out http://tinyurl.com/s360nf14b, dump your nand with it then write it back again (rename flashdmp.bin to updflash.bin), once you've done that post the log here (or send it to me) and i can check if there's a write problem or not... [NOTE: Remove your cpukey from the log output!]

I'd also like to know what model of machine you've got, as some models will have issues like yours when there's corruption in a specific area of the nand...

[timelesspa 0]

l'll see what l can do, tho l do have a nand dump prior to the update which l made. tho what confuses me the most if the fact that l had no issues with Thief or Castlevania 2 (the error l got on castlevania didnt freeze the xbox but seemed a common issue on both the xbox and playstation versions of the game which allegedly has something to do with save file corruption so waiting on TU to fix that issue).

is there any way to test extracted games for consistency? l managed to get the hard drive accessible to scan with seatools via my usb to sata adapter ran both quick tests and found no issues lm assuming it tested the smart as well either way it passed both tests.

heres the make and model numbers etc (the ones l could find at least)

MFR date: 2009-9-25

product ID: 01592621227269793905

with regards to the nand would extracting the nand using your method then putting it back cause any issues cause problems? as l dont want to mess things up even more if its a problem related to nand if there are other ways to test things as lm not extremely knowledgeable about it at the moment. and dont wish to mess things up (at least until l know the original modder is about again if the problem is traceable via other means)

Edited March 18, 2014 by Swizzy
Removed console serial

[Swizzy 2084]

It shouldn't cause any issues, another thing you could do is dump the current nand (so you have something to get back to) then flash the dump you made previously (do this with the new version i gave you) then test if it have the same issues, if it does... well... then i don't really know what's wrong other then possibly game data corruption, but that shouldn't happen just like that...

Anyways, There is no way to check the game data except for extracting it an checking the hashes of each file against the second extracted set... (if they're a match, then the data should be fine)

[timelesspa 0]

so do a full dump then reinsert and post log? not at home at the moment, not sure when l'll have time to do it. however did those serial numbers help?

[Swizzy 2084]

so do a full dump then reinsert and post log? not at home at the moment, not sure when l'll have time to do it. however did those serial numbers help?

Yes, do a full dump and write back your last dump (the one you know should be working)

Those serials don't tell me much because i never really took the time to figure out a pattern with them... they also don't tell me if it's a machine with a built-in memory unit (is that one that you have?) all it really tell me is that it's probably a Phat console with a Jasper Motherboard, but... it could just as well be a repaired console that has any other motherboard...

[timelesspa 0]

yes it does have a built in 512 memory unit.

[timelesspa 0]

dumped and reinserted the nand as asked in the original post.

============= Console information: =============

Current Dashboard: 2.0.16547.0
Current DashLaunch version: 3.11 (541)
Your CPUKey is:

================================================

 * Looking for simpleflasher.cmd for automatic features...
game:\simpleflasher.cmd NOT Found!
 * Entering Manual mode!

Press A if you want to flash your nand with Rawflash v5
Press B if you want to safeflash your nand with Rawflash v5 (Dump + Write)
Press X if you want to dump your nand with Rawdump v1
If you press anything else the application will close...
Press Start to flash your nand or press anything else to exit!

Simple 360 NAND Flasher by Swizzy v1.4b (BETA)

 * Detecting NAND Type...
 * Detected RAW NAND device!
 * Entering NAND Mode...

 * Attempting to grab CPUKey...
 * CPUKey sucessfully saved to: game:\cpukey.txt

============= Console information: =============

Current Dashboard: 2.0.16547.0
Current DashLaunch version: 3.11 (541)
Your CPUKey is:

================================================

 * Looking for simpleflasher.cmd for automatic features...
game:\simpleflasher.cmd NOT Found!
 * Entering Manual mode!

Press A if you want to flash your nand with Rawflash v5
Press B if you want to safeflash your nand with Rawflash v5 (Dump + Write)
Press X if you want to dump your nand with Rawdump v1
If you press anything else the application will close...
Press A to Dump System Partition only (64MB, Recommended!)
Press B to Dump Full NAND (256MB/512MB, this may take a while...)
Press Back to abort dump process...
   config register     = AA3064
   sfc:page_sz         = 200
   sfc:meta_sz         = 10
   sfc:page_sz_phys    = 210
   sfc:pages_in_block  = 100
   sfc:block_sz        = 20000
   sfc:block_sz_phys   = 21000
   sfc:size_mb         = 512MB
   sfc:size_bytes      = 20000000
   sfc:size_bytes_phys = 21000000
   sfc:size_pages      = 100000
   sfc:size_blocks     = 1000

 * rawdump v1 started (by Swizzy)
game:\recovery.bin opened OK, attempting to read 0x21000000 bytes from flash...



NAND Dumped!
Completed after 396.00 seconds
Press Start to flash your nand or press anything else to exit!

WARNING! DO NOT TOUCH YOUR CONSOLE OR CONTROLLER DURING THE FLASH PROCESS!!
The console will reboot when it's done!

Checking game:\updflash.bin for spare data... Spare data detected!
   config register     = AA3064
   sfc:page_sz         = 200
   sfc:meta_sz         = 10
   sfc:page_sz_phys    = 210
   sfc:pages_in_block  = 100
   sfc:block_sz        = 20000
   sfc:block_sz_phys   = 21000
   sfc:size_mb         = 512MB
   sfc:size_bytes      = 20000000
   sfc:size_bytes_phys = 21000000
   sfc:size_pages      = 100000
   sfc:size_blocks     = 1000



 * rawflash v5 started (by cOz, modified By Swizzy)
game:\updflash.bin opened OK, attempting to write 0x4200000 bytes to flash...



image written
Completed after 73.00 seconds
Rebooting in 5....4....3....2....1....BYE!

 

[Swizzy 2084]

Hmm, there's no bad blocks detected anywhere... that's not very common for Jasper BB's

Anyways, this is both good and bad news, the good news is that you don't appear to have a write error... the bad news is that we still don't know what's causing the issue...

Could you try writing back your previous dump to see if the error stays? (if it goes away, it's a image issue)

[timelesspa 0]

l couldnt test the games l had issues with on the old nand due to needing the latest dash, but the flashing part both reverted and current firmware seems to be no issue.

if it is a game error are there any better softwares to extract the game with as l use xbox backup creator image tool to extract, l like it because it tells me what the size of the extract will be as well has dir/file numbers are so l can match the sizes.

like l said tho it confuses me because Thief plays fine but the two others seem to cause the console to freeze.

[Swizzy 2084]

http://tinyurl.com/xisoextractorb65

try this one

[timelesspa 0]

not sure when l will be able to test it, as lm pretty busy over the next week or two.

however, just curious and a random thought but l had been using trainers (l tend to find them for most games mainly for ammo type cheats) could they cause issues? and maybe it might be worth looking into dashlaunch settings.. l cant remember but wasnt there settings in there that handled errors? maybe if l turned it on it might handle problems differently to give an indication on where possible issues are occurring.

(tho thinking about the first time l experienced a freeze it happened when trying to return to the dash, the second one was while playing a game tho like l said could trainers also be a factor as l believe l was using one. which was a retrobyte one l believe).

[Swizzy 2084]

not sure when l will be able to test it, as lm pretty busy over the next week or two.

however, just curious and a random thought but l had been using trainers (l tend to find them for most games mainly for ammo type cheats) could they cause issues? and maybe it might be worth looking into dashlaunch settings.. l cant remember but wasnt there settings in there that handled errors? maybe if l turned it on it might handle problems differently to give an indication on where possible issues are occurring.

(tho thinking about the first time l experienced a freeze it happened when trying to return to the dash, the second one was while playing a game tho like l said could trainers also be a factor as l believe l was using one. which was a retrobyte one l believe).

Yes, trainers can also cause issues, after all... they are modifying the game! (if you modify the wrong part of the game it can cause all kinds of funky errors, such as freezing and what not)

; when set to false, dash launch will not attempt to handle last chance unhandled exceptions

; if set to false, exceptions will also not be dumped to the dumpfile

; if not present this is set to TRUE

exchandler = true

This is the setting you're looking for, it's enabled by default, and as your configuration doesn't have "exechandler=false" it's enabled...

Try to disable everything that isn't part of the standard system to check if it is the cause of the problem, of course you'll have to keep the hacked dashboard and it's recommended that you leave dashlaunch running (it's rare that it causes errors, and when it does it's ussually effecting ALL games or EVERYONE xD)

[timelesspa 0]

ok, l did test the new extractor, seemed much faster l'll be using it from now on thats for sure.

anywho, l came upon something interesting. l booted up the xbox as l was going to copy the newly extracted games and reupload them to see if there were any differences, essentially l wanted to see if any files were corrupted by running them though an sfv shecker (as l hashed all the files l extracted from the iso to reupload, so essentially l was going to download and reupload).

but anywho thats not the point, when l flashed the console l restarted and booted a few times following your instructions. however first chance lve had to check after a day and l encountered an E79 error before l got to FSD l dont even think it tried to sign in, could it still be a hard drive issue?

[Swizzy 2084]

ok, l did test the new extractor, seemed much faster l'll be using it from now on thats for sure.

anywho, l came upon something interesting. l booted up the xbox as l was going to copy the newly extracted games and reupload them to see if there were any differences, essentially l wanted to see if any files were corrupted by running them though an sfv shecker (as l hashed all the files l extracted from the iso to reupload, so essentially l was going to download and reupload).

but anywho thats not the point, when l flashed the console l restarted and booted a few times following your instructions. however first chance lve had to check after a day and l encountered an E79 error before l got to FSD l dont even think it tried to sign in, could it still be a hard drive issue?

E79 isn't uncommon with JTAG/R-JTAG, however it's not common etheir... randomly that'll happen...

Things that cause E79 are:

1. Bad Southbridge (may also be causing the freezing for you as it may lose connection with the hdd and such)

2. Bad Blocks in nand (that haven't been dealt with properly, this isn't your problem tho, and this ussually ALWAYS happens and ussually right after flashing the nand)

3. Bad write for essential blocks (kinda like above)

4. Bad JTAG wiring/wrong JTAG wiring (very rare to happen out of the blue, ussually happens during a update when you select wrong smc hack or when you're installing jtag for the first time)

[timelesspa 0]

to be honest, l doubt its wiring. mainly because lve had this RGH1 console since mid-summer last year and. now admittedly lm not much of a gamer but when l get into a game l play it from start to finish. prior to the update ld played the last two Assassins Creed games likely spending a good 4 days on each play time (likely in 6 hour sessions).

after the dash update l did a couple of weeks back because l wanted to play a newer game called Thief l played for maybe 2/3 days in similar length sessions as above with no problems (before the dash update l kept on getting sent to the dashboard every time l tried to play however l didnt have problems playing after the update).

with regards to the E79 error like l said it didnt happen after the nand reflashes l did upon your recommendation.. in fact like l said l was going to test the differences between the files to see if there could be a correlation. l rebooted the console after experiencing it and it when to the dash normally as it usually does.. l rebooted 3 times and couldnt produce it. so my guess is it could be the hard drive going by what lve seen, l must admit it is noisier than ld expect it and admittedly it was an ebay purchase, was contemplating getting a 500gb 2.5" then running a full diagnostic on it once replaced, tho lm wondering if there is a way to clone the drive tho l can live with copying everything back since l have all the backed up iso's. (fyi l disconnect the power of my xbox when not in use as l lost my falcon at the end of last summer when it got stormy my guess was power surge so l dont suppose disconnecting could cause and issue as it always starts from cold).

[timelesspa 0]

just want to add an update.

 

lve found that booting from cold (as l disconnect the power when not in use, as stated in my previous post) l get E79 errors once booted and rebooting the console doesnt seem to produce any further errors. lm assuming the issue is hard drive related so lm planning on purchasing a 500gb 2.5" and replace the one currently inside the xbox 360 enclosure then reinstall the dash. one thing l did notice tho was it was installed upside down, tho l can remedy that by reworking the cable a little.

in any case its going to be maybe 2/3 weeks till l can sort out anything so just wanted to see what others thoughts on my course of action are.. else if that doesnt fix it lm going to need to find a trustworthy modder, hopefully tho l can get hold of the one that originally did mine tho lm not looking forward to the prospect of it being a hardware problem this would be the second xbox lve had a problem with (first one was taken out by a storm or a surge of some type.. but most likely down to the storm at the end of last summer).

either way, apart from the games already on the current hard drive lve backed up all my saves and profiles onto a memory unit l had spare, all thats left is to change the drive, that being said is there a way to transfer the drives content from one drive to another with my computer? no biggie if there isnt as l have all the ISOs backed up but it would have saved time.

[Swizzy 2084]

if it is hdd related it should boot just fine everytime without the HDD

The dashboard isn't installed to the harddrive, it's in the motherboard...

everytime you start your console something will change in the nand, so dumping twice (rebooting in between) will cause the dumps to NOT be a match...

What do you mean by "installed upside down"? what is upside down?? he harddrive? that's normal...

Yes, you can connect the old harddrive to your computer, use something like horizon, xport360 etc. etc. (something that can read XTAF) then you can extract the contents and put your new drive in and putting the files on the harddrive =)

[timelesspa 0]

l forgot about that one, was thinking about copying the entire content of the drive (after formatting it with the xbox of course to set it up to spec) theoretically l shouldnt have to set up FSD if l just copy everything over.

l decided to also boot my xbox once a day when l have a chance, the last two times l booted the xbox from cold (when it was disconnected between use) l received E79 errors so so today l decided to do exactly the same thing but without the hard drive connected, l will do the same tomorrow but so far without the drive connected it hasnt (at this second at least) produced an E79, given that it twice in the row had such an error from a cold boot my guess is there is a likelihood its the drive but l guess l wont know until l replace the drive and run more in depth tests on the old drive once its been replaced.