Fatal Crash Intercepted When Logging In To Profile Options

[Xplorer4x4]

I have a Slim Trinity RGH. Every time I try to log in to a profile in FSD or NXE it says Fatal Crash Intercepted and restarts NXE or FSD. I am running the latest versions of FSD and Dash Launch. How can I resolve this?

[crazygoldfish]

Delete and re install

[Xplorer4x4]

Delete and re install

Delete what?

FSD? Already deleted and relinstalled a few times just playing with settings and was troubleshooting network issues(turned out to be contpatch)

Dash Launch? Dash Launch has been updated as to the latest version(since stable fsd does not come with up to date dash launch).

[STICKY_BUD]

i would troubleshoot first...
login to your profile from the retail dashboard.
if it fails, you will probably also receive a message which will give you more info to start with.
if it succeeds, try launching FSD from there and see what happens.

[Xplorer4x4]

i would troubleshoot first...
login to your profile from the retail dashboard.
if it fails, you will probably also receive a message which will give you more info to start with.
if it succeeds, try launching FSD from there and see what happens.

hey bud, thanks for a informative response. Like I said, the error persists in NXE, atleast I think it is NXE. I believe I should elaborate because I actually think that may be part of the problem.I bought my console from one of the experienced modders on here. He claimed it came with fsd preinstalled but when I powered on the console originally, the dash looked exactly like NXE which he said fsd looks like nxe. He said fsd did look like nxe so I thought nothing of it but looking in to fsd now I see it had none of the extras of fsd. I tried to install fsd because I was told it was already installed. The install seemed fine, and when I rebooted the dash still looked EXACTLY like NXE and I thought nothing of it untill now because I know 100% sure I have fsd installed. I am thinking maybe my NXE install got messed up when I initially tried to update "fsd?" The problem is trivial because after the dash reboots, I can do anything I wanted but its annoying. The problem only happens on accounts previously used for xbox live. Nonlive profiles do not cause the problem.

[STICKY_BUD]

apologies, did not read the OP very well.

so you were told that NXE was in fact FSD, but really you had a dashlunch that was not configured or launching FSD properly? now that is done properly, but you still cannot login to xbox live profile. do you have the latest dash installed? an update may fix it.

[Xplorer4x4]

apologies, did not read the OP very well.

so you were told that NXE was in fact FSD, but really you had a dashlunch that was not configured or launching FSD properly? now that is done properly, but you still cannot login to xbox live profile. do you have the latest dash installed? an update may fix it.

Thats about right. I thought it was suspicious that FSD looked EXACTLY like NXE but the seller said they looked similar so I thought nothing of it. The dash I believe is NXE allowed me to execute a CD to install XeXMenu, and I could play my GODs fine so I assumed it had to be FSD not NXE as this seemed to me like it was running unsigned code.

Assuming I had FSD I saw mention of an update here on the forums. I was going to update through the dash but couldnt find the settings to do so, so I grabbed the install, and launched it through XeXMenu or XeLL Reloaded. The install screen progress bar filled up to 100% and, if memory serves me right I passed on installing dash launch because it was not mentioned in the post explaining how to update so I assumed it was not important. Immediately after rebooting is when this problem started affecting me in the assumed NXE dash.

As I said, I cant be 100% sure my referenced NXE dash is truly NXE but seeing as I have the latest stable FSD with the latest stable dash launch installed, and this is the dash that is launched if I go to system settings in the guide menu. Also, the dash I assume is NXE has the family settings, the inital set up, vision set up, and so forth, so it has to be NXE right?!?

Sorry for the length of this post but I wanted to try to make it 100% clear what led me to this problem, and confirm my referenced NXE dash is truly NXE. I have not left feedback on my experience in the BST forum yet as I am the type that owns a product for a few months before leaving reviews on products or experiences, and feel it is time to post my experience. I may be an exception in the sellers claimed near spotless record, but the truth is the truth.

[STICKY_BUD]

most of the bst sellers are legit, but they cannot help you if you are unclear about what is happening so my first suggestion is to ask him to read this thread.

he will likely offer to hold your hand since he sold you a misconfigured console, but for the same reason, and the fact that he told you FSD = NXE, he may not be reliable. keep us posted.

[Xplorer4x4]

most of the bst sellers are legit, but they cannot help you if you are unclear about what is happening so my first suggestion is to ask him to read this thread.

he will likely offer to hold your hand since he sold you a misconfigured console, but for the same reason, and the fact that he told you FSD = NXE, he may not be reliable. keep us posted.

Ok well it looks like the mistake was on my end. After reviewing the emails, he had installed freeboot dash not freestyle dash.

As for holding my hand, even if the seller had lied to me, there is little doubt in my mind the seller would offer any help, as the seller got rude with me for asking one to many questions before setting out to start learning things on my own.

So I assume what I thought was NXE is freeboot dash. I guess the best thing to do is try to install freeboot dash to try to fix my problem?

This post has been edited by Xplorer4x4: Mar 23 2012, 04:38 PM

[boflc]

you want to make sure you install dashlaunch as well - just rerun the fsd installer.

[Xplorer4x4]

you want to make sure you install dashlaunch as well - just rerun the fsd installer.

Thanks for the reply, but dashlaunch is already installed and configured as I am set to boot to freestyle dash be default.

[STICKY_BUD]

...
The install screen progress bar filled up to 100% and, if memory serves me right I passed on installing dash launch because it was not mentioned in the post explaining how to update so I assumed it was not important. Immediately after rebooting is when this problem started affecting me in the assumed NXE dash.
...

reinstall both fsd and dashlaunch

[Xplorer4x4]

reinstall both fsd and dashlaunch

STICKY_BUD, as I have stated multiple times, I have already reinstalled fsd and dashlaunch a few times. The part you mention was some time ago and I have since installed fsd and dashlaunch about 2 or 3 times.

This post has been edited by Xplorer4x4: Mar 23 2012, 05:55 PM

[STICKY_BUD]

STICKY_BUD, as I have stated multiple times, I have already reinstalled fsd and dashlaunch a few times. The part you mention was some time ago and I have since installed fsd and dashlaunch about 2 or 3 times.

good luck. you said the same thing about NXE just 4 posts ago and this is your thread. either you read and figure it out yourself, you accept the help offered or fly a kite dude.

[Xplorer4x4]

good luck. you said the same thing about NXE just 4 posts ago and this is your thread. either you read and figure it out yourself, you accept the help offered or fly a kite dude.

I said the same thing about NXE? Not sure what you mean..:s

As for accepting the help, I am truly grateful but here's the problem, you guys say reinstall FSD and dashlaunch again. No I have not tried to reinstall them since opening this thread, but I have tried to reinstall them, and even upgrade dashlaunch once, since the problem first started happening. What good is it going to accomplish to try it again and again when I already have? It's not going to change anything unless of course there is something in particular I should be doing/setting during the install.