[xrandr]: gnome-settings-daemon crashed with signal 5 in _XReply()

[Jpphun]

latest version of 13.10 updated every day, installed nvidia-prime, then this started to happen
systeem is on a SSD , Intel® Core™ i7-3630QM CPU @ 2.40GHz × 8 , Intel® Core™ i7-3630QM CPU @ 2.40GHz × 8

i am not sure when this error occurs, usually at start up, the system will jsut lock up and only the power button will shutdown

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-settings-daemon 3.8.5-0ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 29 09:04:08 2013
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationDate: Installed on 2013-04-20 (162 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 gdk_flush () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: [xrandr]: gnome-settings-daemon crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to saucy on 2013-09-22 (7 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1224254, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.