Fatal Crash Intercepted When Logging In To Profile Options

[crazygoldfish]

Step back & try again & your posts are confusing.

To be honest sounds like your doing something wrong.

[Xplorer4x4]

Ok let's forget everything else in this thread and start with fresh details.


I bought a pre-RGHed slim trinity in the bst section.

It came with freeBOOT installed(which I thought the seller said was fsd, when i double checked the emails, he said freeBOOT not fsd)

I tried to install FSD, but when I installed it, I did not configure/install dash launch.

After installing fsd, I rebooted, and when using NXE I got the fatal crash intercepted error when I tried to log in to a former XBox Live account. Thats was a few weeks or so ago. I been dealing with the error since then.

About 2 days ago, I installed FSD AND dashlaunch. I played with it a bit, and was having trouble due to problems with contpatch in dash launch. So I tried reinstalling dashlaunch and fsd a few times, but kept having trouble with not pulling covers or loading GODS. So I decided to reinstall BOTH once or twice more. The problem with the fatal crash was not resolved.

Then I updated to the latest stable/last version of dashlaunch since the version that comes with fsd installer is out dated.

After updating and reconfiguring dashlaunch, it still gives me the fatal crash when I try to sign in to a profile formerly for xbox live.

I can try to install FSD and dashlaunch again, but what good could it possible do that has not been done from the previous reinstalls plus dashlaunch update?

[deilzfcjk]

Honestly, it's something to do with the peripherals connected to the console. If you have an external SATA connected it may be the problem. I know I have encountered Fatal Exception Intercepted a a few times wiht my 20gb MS hdd. I think in the process of setting up the FSD and dashlaunch's launch.ini file and running the dashlaunch installer. The hacked dash, ie Freeboot with dashlaunch extenstions is looking for config files from the SATA harddrive. When you have it defined somewhere else, like the nand or another harddrive? USB?

To get rid of the problem i just disconnect the SATA hdd. and run games off my external usb. Im sure others here have experienced the same exact problem as you.

But, as I recall you won't have use of your profiles, anymore. Who cares, you're not taking a RGH/Jtag on live anyways.

[Xplorer4x4]

I can see where your coming from, but I dont think perihials are the problem..I had an offical ms hdd i converted to an internal hdd. Thats when my first attempt at fsd took place. Now I am using a seagate 750gb internal hdd converted to a usb hdd.

From what I gather fsd and/or dashlaunch look on usb first which is where I have my installation at right now. It happened on the internal sata to so I dont think thats a factor.

As for profiles, well i dont care about the xbox live stuff but you have to log in to a profile to play games. I have xbl blocked using the family settings in nxe. and live dns block on dashlaunch.

[Xplorer4x4]

I turned my usb hdd off and rebooted. It launches straight to NXE and when I log in to a profile, it still has a fatal crash.

For what it's worth I did notice there is a launch.ini configured in the flash partition, and was just installed by fsd yesterday.

I also tried launching my fsd cd and using the remove function in the installer to remove fsd from my usb hdd. It sits there saying waiting for input after I push start.

I also used the installer to look for an fsd install on flash(by having the usb hdd off) but it did not find anything.

Not sure if it is safe to simply delete the FSD folder from the USB HDD so I will try installing FSD with FSD still installed as I have before.

EDIT!!

Ok so I fixed it for a moment...

So I checked the remove current install(or whatever it says) in fsd installer, then selected to install fsd and dashlaunch.

Installed FSD but skipped dash launch.

Reboot and came up to NXE if memory serves me right. Tested. Crash. Reboot.

Tried NXE and was able to switch profiles with out a crash. So I reinstalled fsd and dashlaunch.

Configured dashlaunch, reboot to fsd and crash is back.

This post has been edited by Xplorer4x4: Mar 24 2012, 01:56 AM

[crazygoldfish]

Is this a 4gb slim?

Other thing you try is removing dash & fsd and try installing to a USB hd

[deilzfcjk]

this happens. So, I used to not be able to play any games off hdd. because once i load games, it will ask to login to profile then it would go all crazy with fatal crash intercepted and reboot. Then once I removed the offending root cause of the problem its fine. So, look I telling you it's something to do with the launch.ini or fsd installer app you run. I don't remember all this as i did it in 2010-11.

I could test my slim rgh out if you want me to but I have to finish some of my other work first.

[Xplorer4x4]

Is this a 4gb slim?

Other thing you try is removing dash & fsd and try installing to a USB hd

Yes 4GB slim.

Removing nxe? FSD is installed on my external. The internal hdd has been removed as I have no use for it with the external.

this happens. So, I used to not be able to play any games off hdd. because once i load games, it will ask to login to profile then it would go all crazy with fatal crash intercepted and reboot. Then once I removed the offending root cause of the problem its fine. So, look I telling you it's something to do with the launch.ini or fsd installer app you run. I don't remember all this as i did it in 2010-11.

I could test my slim rgh out if you want me to but I have to finish some of my other work first.

I can play games of the external through fsd. I havent tried the external with NXE. I get the crash but its justa nuisance. It is not hindering my ability to play games because after the crash I am logged in to my profile and ready to go.

I am not arguing that fsd is the culprit. I KNOW it is the culprit. I was saying that I have tried to reinstall several times with no luck. Then, out of pure luck, I found a combination that fixed it. Then I reinstalled fsd and dash launch properly and it came back again. I tried the steps I outlined, but I vaugley recalled what I did to fix it. No such luck this time.

If you can try to troubleshoot it again on your slim I would be incredibly grateful.

[crazygoldfish]

There was issues with the 4gb slims, pretty sure you had to configure them slightly differently to work.

[Xplorer4x4]

There was issues with the 4gb slims, pretty sure you had to configure them slightly differently to work.

Any details would be great. I found alot of reports of this on the fsd forums but no real fix.

Quick question, my external is recognize as Usb0 so should the ini read:
Default = usb:\FreeStyle\default.xex
or
Default = usb0:\FreeStyle\default.xex
From what I gather the 0 is not needed.

[Xplorer4x4]

I have liveblock set to true, livestrong set to false and contpatch set to false. The xbox shows the proper static ip and I can conect via ftp, although it does not like to connect at times. How come I cant connect to check for fsd updates or even weather data?

[Xplorer4x4]

Well here is a fix that might work for others. My name servers(in NXE network settings) were set to automatic. Once I changed the primary DNS server to 192.168.1.1 it has gotten internet connection for about 5 successful boots in a row with network access.


EDIT2: So I can go into my game library and update covers manually, but it does not seem to download them automaticly despite my scan frequency set to 5 min, and waiting 5 mins for covers to slowly start showing up.


This post has been edited by Xplorer4x4: Mar 26 2012, 06:30 AM