Xbox gets "Fatal crash intercepted" when starting xbox360 games. XBLA games works.
Hi
Hope someone has some experience in what is going on here wrt. my issue.
Setup:
I have two Trinity Xbox's: One with 4GB MU + 120GB int. HDD <-- hereafter xbox1.
and
One with a 120GB int. HDD. <-- hereafter xbox2.
Both are RGH'ed (with a CR3 Lite and with a RGX.. But I don't believe that makes a difference), and both are on dashboard 2.0.16203.0.
I have installed the newest Freestyle Dash (Freestyle Dash rev. 58) and corresponding DashLaunch 3.07.
Problem:
The xbox2 runs every game fine, both XBLA and Xbox 360 games.
The xbox1 runs _every_ XBLA game fine, but gets a "fatal crash intercepted" error or "disc unreadable" error (it varies which exception is thrown), whenever I try to run _any_ Xbox 360 rip/game on it. The exact same rips and re-rips works on the xbox2, but not on the xbox1.
What I have tried to do (this is basically a long list of things I have - mostly unrelatedly - tried to do... If it gets too long to read (which I understand, I have listed many experiments I have tried doing), you can skip the rest. They are for the most part not related. Even if you skip, then thank you for having wanted to read some of it and having shown interest. Having said that, here goes:
The first thing that came to my mind was that my xbox1 needed the kinect+avatar update to stop "fatal crash interrupted" exceptions. I have installed the avatars update (using BL4K3Y's guide in here), and verified that it was installed, but the crashes still occur. An interesting fact here is that the xbox2 which runs 360 games just fine do not have the avatars update.
I re-installed both DashLaunch and Freestyle Dash 3, which did not help. I also tried to install lower versions of DashLaunch instead, but could not since only DashLaunch 3.07 supports dashboard 2.0.16203.0.
I flashed a new image unto the xbox, where I chose not to include DashLaunch' launch.ini in J-Runner. That did not help either.
I tried running the xbox 360 rips both directly through DashLaunch and from FSD; both gives me the prior mentioned errors. Trying to run it from FSD without having DashLaunch installed did not yield any positive results either, as the xbox just crashes now (since DashLaunch is no longer there to intercept the fatal crashes and recover/restart the system).
I tried to remove the 4GB IntMU from the troublesome xbox1, since it might have been corrupt/faulty (although it gives me the same exception, regardless of whether my users are stored on the IntMU, or if it is not used at all) - after all, the 4GB intMU is the only difference physically between xbox1 and xbox2 since they are both Trinity's. Sadly it didn't help (afterwards I plugged it back in. No reason not to use those 4GB).
I tried first to remove the DVD present in the DVD-drive, and afterwards I tried to disconnect the complete DVD-drive from the xbox. In both cases the errors still occured. Interestingly, it also still gave the disc unreadable error at times.
I tried to run my rips from an external HDD connected to Xbox1; the same exceptions still occured though. So I have both tried to FTP the rip to Xbox1's internal HDD, and to transfer it directly from my computer to an external HDD. That combined with the amount of times I have tried, rules out (in my eyes atleast, sorry if I am wrong) the possilibity of a bad transfer of the game.
To test the HDD of xbox1, I tried inserting it into my working xbox2. I could play the games from the HDD just fine there, which rules out a defect HDD I suppose. Just to cross-test, I tried to take the HDD present in xbox2 (which works fine in xbox2, tested it before I took the HDD out). I got the same exceptions with xbox2's HDD inserted into xbox1, when trying to run xbox 360 backups. I could run the XBLA games from that HDD just fine though.
I tried fiddling around with the settings in DashLaunch. I found no settings that worked The settings that worked in xbox2 did not work in xbox1 either. If you know what the problem is, and if it can be solved by DashLaunch settings... Then stop reading now. Write the DashLaunch options that should work immediately! I tried most options on/off (I'd like to think that myself atleast, I probably didn't try that many, since I could not run games from FSD without DashLaunch installed either).
I tried to get DashLaunch to write the crashdump to a file, so I could inspect it.... Unfortunately (yet also understandable I suppose ), DashLaunch only allows non-fatal exceptions to be written to the crashdump. The only dumps FSD does is a debug dump when it boots up, which did not seem to contain a lot of info that would help... I have linked it at the end of this post anyway, just in case.
Lastly, I tried swapping the HDMI cable, TV and power adapter, just in case it was something with the peripherals that caused the problem. Unfortunately it was not. I also tried to change the display resolution on the xbox, alas with much the same results as the above test-case scenarios..
What I am thinking now:
I can fortunately outrule the HDD and rips' as being the issue, as they work on the other xbox. I can also outrule the peripherals such as TV and cables.
The only difference between the xbox's, the 4GB MU could also be outruled, as removing it did not do the trick. Same goes with the DVD-drive as removing that did not help either.
The fact that the rips' did not work with or without FSD installed, and with or without DashLaunch installed, also moves my focus away from those applications as being the cause of the problem here. Besides, they are used to thousands, if not hundred of thousands of people with success, so it would be odd if they were the problem.
In my eyes (I might have missed a few things), this leaves me with the NAND/flash as being the culprit. It's the only thing that can store data on the xbox without the HDD, now that swapping HDD's between xbox1 and xbox2 and removing the 4GB IntMU didn't work. The content of the flash also makes the two xbox's different, so it might be possible.
I tried booting up XeLL (which just as XBLA, FSD and DashLaunch works fine) and I downloaded a new dump of my NAND through XeLL's WebUI. I selected the NAND in J-Runner, and it didn't report any bad blocks in the Bad Blocks tab... I don't know what else to check for though :/ ... Or what else that can be done with the NAND dump. Some people in here seems to be beasts with building new NAND dumps from the KV only and advises people to sometimes use the "write fusion" options and what not... I must admit, I don't know about that part of the game, which is why.. I guess, I write here. Hoping to learn in the progress too.
Anyway,
My question is now:
What do you think about what I am thinking after having done the tests I have. Do you think I am right about the NAND being the culprit somehow? Do you know what can be done? Also, do you have any suspicions of what is going on? Or even a solution for how to remedy it?
Thanks alot in advance. Hope the post was understanding, else just ask for deepening info.
I have linked a few files below.
My DashLaunch launch.ini file:
https://dl.dropbox.com/u/13685979/Upload%20til%20TX%20regarding%204GB%20Xbox/launch.ini
FSD's boot/debug log... I don't think that there is anything useful in it, but uploading it cannot hurt (please note when this debug.log was made, I had my DVD Drive disconnected from the xbox, which is why it fails mounting it):
https://dl.dropbox.com/u/13685979/Upload til TX regarding 4GB Xbox/debug.log
The NAND dump retrieved today through XeLL:
https://dl.dropbox.com/u/13685979/Upload til TX regarding 4GB Xbox/flashdmp.bin
By the way, if you think you know what can be done with the NAND or have an idea.. or if you think if a donor NAND will help... or if you can think of anything, where you will need my CPU key to help. Just ask for it, and I'll PM it to you.
Last notes:
Also, if its of any use to you.. If you want something for helping, I'll more than gladly let you use and keep my CPU key afterwards. It's the least I can do. I am of the understanding that they are of a certain value, since they can be used for unbanning an xbox by changing the KV I will not mind at all. I can reveal that the reason I have two xbox's (and TV's), is because I use them for System Link. System Link - it's simply the best. (Sorry if I got you thinking of Tina Turner here.... :|)
Ofc, not to be rude, but I can only give/allow the key to the one whose help works... After all, I cannot give it to multiple people, and still expect it to be unbanned for the one that solved my problem, even though everyone helped. Rough prioritization I guess... Anyway, I don't want to pay/bribe anyone to help me, or have it be the focus of the thread... Neither do I think it is necessary. People are fantastic at helping here without expecting anything except a "thank you", although a thank you to its defense can be really powerful. I simply want to give back to whomever helps me for investing their time in me, if they want it.
BTW, just tested and played Geometry Wars evolved (for those that did not know: It's an XBLA game) for half an hour without any problems... the temperature of the CPU and GPU in FSD never climbed above 60c either.
Hi
Hope someone has some experience in what is going on here wrt. my issue.Setup:
I have two Trinity Xbox's: One with 4GB MU + 120GB int. HDD <-- hereafter xbox1.
and
One with a 120GB int. HDD. <-- hereafter xbox2.
Both are RGH'ed (with a CR3 Lite and with a RGX.. But I don't believe that makes a difference), and both are on dashboard 2.0.16203.0.
I have installed the newest Freestyle Dash (Freestyle Dash rev. 58) and corresponding DashLaunch 3.07.
Problem:
The xbox2 runs every game fine, both XBLA and Xbox 360 games.
The xbox1 runs _every_ XBLA game fine, but gets a "fatal crash intercepted" error or "disc unreadable" error (it varies which exception is thrown), whenever I try to run _any_ Xbox 360 rip/game on it. The exact same rips and re-rips works on the xbox2, but not on the xbox1.
What I have tried to do (this is basically a long list of things I have - mostly unrelatedly - tried to do... If it gets too long to read (which I understand, I have listed many experiments I have tried doing), you can skip the rest. They are for the most part not related. Even if you skip, then thank you for having wanted to read some of it and having shown interest. Having said that, here goes:
The first thing that came to my mind was that my xbox1 needed the kinect+avatar update to stop "fatal crash interrupted" exceptions. I have installed the avatars update (using BL4K3Y's guide in here), and verified that it was installed, but the crashes still occur. An interesting fact here is that the xbox2 which runs 360 games just fine do not have the avatars update.
I re-installed both DashLaunch and Freestyle Dash 3, which did not help. I also tried to install lower versions of DashLaunch instead, but could not since only DashLaunch 3.07 supports dashboard 2.0.16203.0.
I flashed a new image unto the xbox, where I chose not to include DashLaunch' launch.ini in J-Runner. That did not help either.
I tried running the xbox 360 rips both directly through DashLaunch and from FSD; both gives me the prior mentioned errors. Trying to run it from FSD without having DashLaunch installed did not yield any positive results either, as the xbox just crashes now (since DashLaunch is no longer there to intercept the fatal crashes and recover/restart the system).
I tried to remove the 4GB IntMU from the troublesome xbox1, since it might have been corrupt/faulty (although it gives me the same exception, regardless of whether my users are stored on the IntMU, or if it is not used at all) - after all, the 4GB intMU is the only difference physically between xbox1 and xbox2 since they are both Trinity's. Sadly it didn't help (afterwards I plugged it back in. No reason not to use those 4GB).
I tried first to remove the DVD present in the DVD-drive, and afterwards I tried to disconnect the complete DVD-drive from the xbox. In both cases the errors still occured. Interestingly, it also still gave the disc unreadable error at times.
I tried to run my rips from an external HDD connected to Xbox1; the same exceptions still occured though. So I have both tried to FTP the rip to Xbox1's internal HDD, and to transfer it directly from my computer to an external HDD. That combined with the amount of times I have tried, rules out (in my eyes atleast, sorry if I am wrong) the possilibity of a bad transfer of the game.
To test the HDD of xbox1, I tried inserting it into my working xbox2. I could play the games from the HDD just fine there, which rules out a defect HDD I suppose. Just to cross-test, I tried to take the HDD present in xbox2 (which works fine in xbox2, tested it before I took the HDD out). I got the same exceptions with xbox2's HDD inserted into xbox1, when trying to run xbox 360 backups. I could run the XBLA games from that HDD just fine though.
I tried fiddling around with the settings in DashLaunch. I found no settings that worked
The settings that worked in xbox2 did not work in xbox1 either. If you know what the problem is, and if it can be solved by DashLaunch settings... Then stop reading now. Write the DashLaunch options that should work immediately! I tried most options on/off (I'd like to think that myself atleast, I probably didn't try that many, since I could not run games from FSD without DashLaunch installed either).I tried to get DashLaunch to write the crashdump to a file, so I could inspect it.... Unfortunately (yet also understandable I suppose
), DashLaunch only allows non-fatal exceptions to be written to the crashdump. The only dumps FSD does is a debug dump when it boots up, which did not seem to contain a lot of info that would help... I have linked it at the end of this post anyway, just in case. Lastly, I tried swapping the HDMI cable, TV and power adapter, just in case it was something with the peripherals that caused the problem. Unfortunately it was not. I also tried to change the display resolution on the xbox, alas with much the same results as the above test-case scenarios..
What I am thinking now:
I can fortunately outrule the HDD and rips' as being the issue, as they work on the other xbox. I can also outrule the peripherals such as TV and cables.
The only difference between the xbox's, the 4GB MU could also be outruled, as removing it did not do the trick. Same goes with the DVD-drive as removing that did not help either.
The fact that the rips' did not work with or without FSD installed, and with or without DashLaunch installed, also moves my focus away from those applications as being the cause of the problem here. Besides, they are used to thousands, if not hundred of thousands of people with success, so it would be odd if they were the problem.
In my eyes (I might have missed a few things), this leaves me with the NAND/flash as being the culprit. It's the only thing that can store data on the xbox without the HDD, now that swapping HDD's between xbox1 and xbox2 and removing the 4GB IntMU didn't work. The content of the flash also makes the two xbox's different, so it might be possible.
I tried booting up XeLL (which just as XBLA, FSD and DashLaunch works fine) and I downloaded a new dump of my NAND through XeLL's WebUI. I selected the NAND in J-Runner, and it didn't report any bad blocks in the Bad Blocks tab... I don't know what else to check for though :/ ... Or what else that can be done with the NAND dump. Some people in here seems to be beasts with building new NAND dumps from the KV only and advises people to sometimes use the "write fusion" options and what not... I must admit, I don't know about that part of the game, which is why.. I guess, I write here. Hoping to learn in the progress too.
Anyway,
My question is now:
What do you think about what I am thinking after having done the tests I have. Do you think I am right about the NAND being the culprit somehow? Do you know what can be done? Also, do you have any suspicions of what is going on? Or even a solution for how to remedy it?
Thanks alot in advance.
Hope the post was understanding, else just ask for deepening info.I have linked a few files below.
My DashLaunch launch.ini file:
https://dl.dropbox.com/u/13685979/Upload%20til%20TX%20regarding%204GB%20Xbox/launch.ini
FSD's boot/debug log... I don't think that there is anything useful in it, but uploading it cannot hurt (please note when this debug.log was made, I had my DVD Drive disconnected from the xbox, which is why it fails mounting it):
https://dl.dropbox.com/u/13685979/Upload til TX regarding 4GB Xbox/debug.log
The NAND dump retrieved today through XeLL:
https://dl.dropbox.com/u/13685979/Upload til TX regarding 4GB Xbox/flashdmp.bin
By the way, if you think you know what can be done with the NAND or have an idea.. or if you think if a donor NAND will help... or if you can think of anything, where you will need my CPU key to help. Just ask for it, and I'll PM it to you.
Last notes:
Also, if its of any use to you.. If you want something for helping, I'll more than gladly let you use and keep my CPU key afterwards. It's the least I can do. I am of the understanding that they are of a certain value, since they can be used for unbanning an xbox by changing the KV
I will not mind at all. I can reveal that the reason I have two xbox's (and TV's), is because I use them for System Link. System Link - it's simply the best. (Sorry if I got you thinking of Tina Turner here.... :|)Ofc, not to be rude, but I can only give/allow the key to the one whose help works... After all, I cannot give it to multiple people, and still expect it to be unbanned for the one that solved my problem, even though everyone helped. Rough prioritization I guess... Anyway, I don't want to pay/bribe anyone to help me, or have it be the focus of the thread... Neither do I think it is necessary. People are fantastic at helping here without expecting anything except a "thank you", although a thank you to its defense can be really powerful. I simply want to give back to whomever helps me for investing their time in me, if they want it.
BTW, just tested and played Geometry Wars evolved (for those that did not know: It's an XBLA game) for half an hour without any problems... the temperature of the CPU and GPU in FSD never climbed above 60c either.
Last edited:
