[darkzone]

Hi Guys,

Lately I have had the problem that XBMC will freeze on the startup screen "XBMC v11.0 eden" and this freezes up the whole computer so I have to kill it and start up again.

Weird thing is that it used to work, then started to freeze sometimes on startup and now it happens every time.

Here is the log:
http://pastebin.com/L5g9vyBw

Often in these occasions Nvidia will come up and yes I do have an Nvidia card, a pretty new one, the GeForce GT 520M, using Windows 7 64bit.

This problem seems to occur every so often on the forum but haven't found a working solution. Have tried the XBMC.exe download that was posted in another thread.

Thanks,

Darkzone

[jhsrennie]

Hmm, there's a similar problem at http://forum.xbmc.org/showthread.php?tid=125338 and I've seen a previous report of this, though the link escapes me at the moment. I note that both you and Hajric are using the Intel GPU. I wonder if we have a problem with that chipset.

You could try deleting or renaming the guisettings.xml. This won't affect your library, though you will have to recreate your display preferences. If you want to do this press Windows-R and in the Run dialog type:

Code:

"%appdata%\XBMC\userdata"

and click OK and an Explorer window will open. In that window you'll see a file called guisettings.xml.

JR

[darkzone]

jhsrennie: I tried to rename the guisettings.xml to guisettings.xml.old and start up, a new file was created but the same thing happened.

The log now indicates some problem with the user profile.

http://pastebin.com/DkGKH3qh

Here is my profiles.xml

http://pastebin.com/VztMmF3H

Not sure what is suppose to be in that file. I have one profile without password. Need to log the profile in to use XBMC.

I think my computer auto chooses if it should use the Graphics card or the CPU graphics (I might be completely out of line here), which could explain why it sometimes works and sometimes not. Will try to set it to always use the CPU and see what happens.

---

Here is a turn.

I first set it to always run with the CPU in the Nvidia control panel. It didn't work.
I then changed it to always run on the GPU and it worked.

Here is the log in case you guys can find something useful from there.

http://pastebin.com/rxNqy3Yf

Will try to reproduce the problem and if I succeed post more specifically the actions I took.

[darkzone]

Ok, so don't think that was the problem.
It still works when I changed it back again. But all view settings are gone so I would say the deleted guisettings.xml was the key it just took a couple of restarts until it got working if that make sense.

So for other people having the same problem I would recommend this.

Also my user profile was gone...

Thank you jhsrennie for the help!

Tell me if you need any other information to understand the problem here. For me it looks like my problem is solved.

[darkzone]

Alright, I have to bump this thread because there is something weird going on.
I got it to work and was once again setting up all my GUI that I lost somehow.

Restarted, bam, same problem, freeze on startup. Did all sorts of stuff but mainly I managed to get the debugger on by changing the xml file:

http://pastebin.com/xCTtQNLk

It is failing to connect to something and tries every 5 seconds.
Now I did the same things again, took away the guisettings, nothing. Added it back again, nothing. Changed the Nvidia Physx setting to GPU instead of CPU, Restarted again and now, success... Still not sure if it was the Nvidia settings or the removing and adding the xml files that made it.
So here is the log when it worked:

http://pastebin.com/1qrx9ARn

This time the connect remote doesn't fail...

Maybe someone can make some sense out of this, I want to keep this thread open to help the XBMC figure this (bug?) out.

[jmarshall]

The remote thing is a red herring - it will do that regardless and is present in both your logs.

IMO it's almost a certainty that it's your GPU stuff.

[fuzzybeer]

I had the same problem. Seemed i had the windows DVD in the drive that was causing this. I ejected the disc and XBMC started to work instantly

[darkzone]

I have struggled with this but I might have finally solved it.

Another post about a similar problem suggested to update the "Intel rapid storage technology driver" found here.

This seems to have worked for me since I haven't had a crash since I updated that driver. And I'm not the only one with this success it seems like. Maybe someone much smarter than me can explain why this happens and maybe even get a fix for it in the next release of XBMC.

Help me spread the word since there seems to be a lot of similar problems out there.

Cheers