Windows 7 64-bit 8GB RAM doesn't start after installing X-Fi drivers
I have Windows 7 64 bit, 8GB RAM for a few months. After inserting an X-Fi Platinum Fatalty Champion Series (S/N MASB046A83R0772D; OP BN 06SB046A00005 Rev A) and installing Creative Sound Blaster X-Fi series driver 2.8.003 dated 26 Jun 09. The sounds plays OK, but after rebooting Windows doesn't start, with a CorruptRegistry error. I have installed Windows from scratch, but it only works until I install the X-Fi driver and reboot. Please help. I have searched the internet and found no solution to my problem besides a Wikipedia article that X-Fi has problem with 64-bit Vista with 4GB RAM or more.
Hi, I am also running windows 7 ultimate 64 with the same sound card and am using the july 5 driver. It works but i cant use the creative control panel as i get a black screen on start-up and when i uninstall the contol panel windows functions normally. I may have to go with the onboard sound to get all 4 speakers to work. I have 6 Gb of ram on a gigabyte X58 Mobo.
Similar Messages
-
DBConsole Service doesn't start after Install OAS F&R-Services Win 10g
Windows DBConsole Service doesn't start after Install OAS F&R-Services
Hello,
we have installed:
WINDOWS Server 2003 with SP 2
Oracle 10.2.0.1
OAS F&R Services 10.1.2.0.2
after Install DBR2 EM / DBConsole did work
after Install OAS F&R-Service
the windows-service for DBConsole
doesn't start, return with an Error Code 2
see below
the file named emdbconsole.nohup from output log
is not to find
the ias_console does work fine
OAS F_R-Services do work too
whats may be wrong ?
regards
Norbert
OracleDBConsoleorclsrvc.log :
EMDROOT=D:\oracle\product\10.2.0\db_1
ORACLE_HOME=D:\oracle\product\10.2.0\db_1
EMDSTATE=D:\oracle\product\10.2.0\db_1\kfin_orcl
CONSOLE_CFG=dbconsole
TRACE_LEVEL=16
TIMEOUT=15
12/14/09 13:13:08 Start pending...
12/14/09 13:13:08 Verifying dbconsole is not started already. Command line "D:\oracle\product\10.2.0\db_1\bin\emctl.bat" istatus dbconsole
12/14/09 13:13:09 dbconsole launch commandline is "D:\oracle\product\10.2.0\db_1\bin\emctl.bat" istart dbconsole
12/14/09 13:13:09 Tracking process launch...
12/14/09 13:13:39 dbconsole exited with retCode 2.
12/14/09 13:13:39 Check D:\oracle\product\10.2.0\db_1\kfin_orcl\sysman\log\emdbconsole.nohup for details
Edited by: astramare on Dec 15, 2009 8:43 AMHi,
1. Stop the DBConsole. (set ORACLE_SID first & ORACLE_HOME)
cd %ORACLE_HOME%\bin
emctl stop dbconsole
2. Update the <ORACLE_HOME>/<hostname_sid>/sysman/config/emd.properties file.
Change line from:
tracelevel.main=WARN
To
tracelevel.main=DEBUG
Decomment this line, so that the line becomes :
EMAGENT_PERL_TRACE_LEVEL=DEBUG
3. Update the <ORACLE__HOME>/<hostname_sid>/sysman/config/emomslogging.properties
Change line from:
log4j.rootCategory=WARN, emlogAppender, emtrcAppender
To
log4j.rootCategory=DEBUG, emlogAppender, emtrcAppender
4. Remove/backup all log files from ORACLE_HOME/<hostname_sid>/sysman/log
5. Start the dbconsole and upload the output of each command
- start the dbconsole: "emctl start dbconsole"
- issue "emctl clearstate"
- status the dbconsole: "emctl status dbconsole"
- check the status of the agent until it comes up: "emctl status agent"
- force an upload: emctl upload
6. Check If you are able to view the dbconsole Page & login
check below logs may be you can see the close error messages to solve the issue.
<ORACLE_HOME>/<hostname_sid>/sysman/log directory
<ORACLE_HOME>/<hostname_sid>/sysman/config/emoms.properties
Otherwise re-create the DBconsole using the metalink doc 278100.1 : How To Drop, Create And Recreate DB Control In A 10g Database. (Please check the steps from Recreate/ReConfig DB Control, if you want to re-create)
Thanks. -
HTTP Server Doesn't Start after install
I just completed an install of the 10.1.3.1 Oracle App Server. It indicated that the install was successful. I can see in the log the BPEL Manager deploying in the default domain, but I do not see any reference to the HTTP server. Also, when I do a *./opmnctl startall* there is no HTTP_Server~1.log created.
Is there a step I need to complete to enable the Apache server to start? I must be missing something - the Apache folder is there in the install folder.
The *./opmnctl status* reports:
Processes in Instance: AS02.ssg-st-bpel-build0-dev.vzbi.com
---------------------------------+--------------------+---------+---------
ias-component | process-type | pid | status
---------------------------------+--------------------+---------+---------
OC4JGroup:default_group | OC4J:home | 18970 | Alive
ASG | ASG | N/A | DownI found the following in the installActions log:
Install type for "Oracle HTTP Server 10.1.3.0.0 " is "Typical".
# Not all the dependencies for the component Oracle HTTP Server 10.1.3.0.0 could be found. Missing component oracle.bc4j 10.1.2.0.0.
# Not all the dependencies for the component Oracle HTTP Server 10.1.3.0.0 could be found. Missing component oracle.bc4j.oem 10.1.2.0.0.
# Not all the dependencies for the component Oracle HTTP Server 10.1.3.0.0 could be found. Missing component oracle.soap.srv 2.2.0.0.2a.
# Not all the dependencies for the component Oracle HTTP Server 10.1.3.0.0 could be found. Missing component oracle.apache.ejb 9.0.1.0.1.
# Not all the dependencies for the component Oracle HTTP Server 10.1.3.0.0 could be found. Missing component oracle.apache.ojsp 10.1.2.0.0.
Conflict while setting install type of "Oracle Process Management Notification 10.1.3.1.0 " to "Typical (Typical)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
# Not all the dependencies for the component Oracle HTTP Server 10.1.3.0.0 could be found. Missing component oracle.dcm 10.1.2.0.0.
# Not all the dependencies for the component Oracle HTTP Server 10.1.3.0.0 could be found. Missing component oracle.sysman.emd 10.0.2.0.0.
# Not all the dependencies for the component Oracle HTTP Server 10.1.3.0.0 could be found. Missing component oracle.java.j2ee.iascfg 10.1.2.0.0.
# Not all the dependencies for the component Oracle HTTP Server 10.1.3.0.0 could be found. Missing component oracle.logloader 10.1.2.0.0.
# Not all the dependencies for the component Oracle HTTP Server 10.1.3.0.0 could be found. Missing component oracle.webdb.monitor 10.1.2.0.0.
What am I missing? Is there a package I need to install before installing the App Server?
Edited by: BCurtis on Sep 24, 2010 3:22 PM
Edited by: BCurtis on Sep 24, 2010 3:25 PMI now know I'm missing the <ias-component id="HTTP_Server"> in the opmn.xml file. The following is from an older install of a few years ago.
<ias-component id="HTTP_Server">
<process-type id="HTTP_Server" module-id="OHS">
<module-data>
<category id="start-parameters">
<data id="start-mode" value="ssl-enabled"/>
</category>
</module-data>
<process-set id="HTTP_Server" numprocs="1"/>
</process-type>
</ias-component>This explains why the startall doesn't start the HTTP Server, but why would the install not include the HTTP Server in the configuration? -
Report service doesn't start after installing 9iAS
Forms are fine after installing 9iAS, but report server doesn't
start, and is not listed in Control Panel, Services.
If I try start it as RWMTS60.exe -install oracledev2 tcpip I got
the error "Please consult the installation guides for how to set
up and run this program", if I start it as RWMTS60.exe -listen
oracledev2 I got the error "Rep 0001:Unable to find the report
builder message file. Please verify your installation". Attempt
to run any Reports product (Runtime, for instance) causes
Dr.Watson on RWRUN60.exe. The registry parameter RW60 points to
the ORACLE_HOME/report60 for the Reports Server that is failing.
What do I do to start Reports ?
Thank you,
KateHi,
1. Stop the DBConsole. (set ORACLE_SID first & ORACLE_HOME)
cd %ORACLE_HOME%\bin
emctl stop dbconsole
2. Update the <ORACLE_HOME>/<hostname_sid>/sysman/config/emd.properties file.
Change line from:
tracelevel.main=WARN
To
tracelevel.main=DEBUG
Decomment this line, so that the line becomes :
EMAGENT_PERL_TRACE_LEVEL=DEBUG
3. Update the <ORACLE__HOME>/<hostname_sid>/sysman/config/emomslogging.properties
Change line from:
log4j.rootCategory=WARN, emlogAppender, emtrcAppender
To
log4j.rootCategory=DEBUG, emlogAppender, emtrcAppender
4. Remove/backup all log files from ORACLE_HOME/<hostname_sid>/sysman/log
5. Start the dbconsole and upload the output of each command
- start the dbconsole: "emctl start dbconsole"
- issue "emctl clearstate"
- status the dbconsole: "emctl status dbconsole"
- check the status of the agent until it comes up: "emctl status agent"
- force an upload: emctl upload
6. Check If you are able to view the dbconsole Page & login
check below logs may be you can see the close error messages to solve the issue.
<ORACLE_HOME>/<hostname_sid>/sysman/log directory
<ORACLE_HOME>/<hostname_sid>/sysman/config/emoms.properties
Otherwise re-create the DBconsole using the metalink doc 278100.1 : How To Drop, Create And Recreate DB Control In A 10g Database. (Please check the steps from Recreate/ReConfig DB Control, if you want to re-create)
Thanks. -
IMac 24" doesn't start after installing Mavericks.
After installing Mavericks (10.9.2) the machine started having hiccups... rebooting at random times on it's own. After upgrading to 10.9.3, it only got worse. Reboots were more frequent (as little as 1 minute between each reboot). Then it took the final step and went into a state where it remains with black screen, the startup jingle may begin, but is killed within half a second or less... goes into a reboot loop. The DVD sounds, then it tries to reboot again, DVD sounds... sometimes the jingle starts... but is cut off by a reboot. Trying to get ANYTHING done with different key press combinations (option+command+R+P, D, T, Command, Option... pretty much every single combination one can find online for accessing safe boot or recovery or whatever... does not work. The machine seems to have been killed by Mavericks. I have come across a LOT of posts by other people who have experienced the same thing (rebooting after installing Mavericks) going back to October last year, and a few have experienced the same dead computer issue as I am having... all the while there is no fix or explanation from APPLE regarding this issue. I have even opened the machine up and checked all cable connections, tested the HDD on another computer (was ok), cleaned the memory module connectors etc. Before the total crash I had installed a temperature monitoring program with ventilator control, due to the DVD ventilator running at high RPM after installing Maverics. All the temp sensors were reporting modest temps (ranging from 39 - 79 Celsius (only the power supply was above 50 Celsius).
The computer is as useful as a brick by this point. Since it went dead, it has successfully started up 3 times (out of 500+ attempts), but rebooted within a couple of minutes, into it's cycle of dead reboots.
One way of getting it to boot and prepare for re-installation, is to keep the power button pressed until it sounds 3 times long, 3 times short and 3 times long beeps... it would only start making the first beep... then it rebooted in to death again.
Could it be that Mavericks is destroying the firmware, or even killing the hardware? I also have Mavericks on MBA and MBP, where the MBA has no problems, while the MBP freezes up every 2 days or so... requiring a forced reboot.
Anyone with a usable advice on what to do in order to get the machine working again? How many years does it normally take APPLE support staff to fix serious issues like this one? It's already been over 7 months since the first people began experiencing these issues with Mavericks, but nothing has been done about it on APPLE's end ... as far as I can tell.
Looking forward to some solutions.Just wanted to write the conclusion of this issue here, and make things as clear as possible.
I took the iMac to a support center, and they confirmed that several components on the power supply board were fried and other parts had been overheated. It took a few weeks for them to get the needed parts (much cheaper than replacing the entire unit). I brought the iMac back home and started it up, and it did work... but it was getting very hot very quickly. I was thinking that maybe I should install Mountain Lion on it, and get away from Mavericks... just in case.... the computer had been turned on for around 1 hour at that point, and then it rebooted.... and stayed dead for 10 minutes or so... until it could start up again. Was on for a few minutes... then dead again.
Clearly the cause of the problem was still present, and fixing the symptom did not prove to be a lasting solution.
The machine would not stay turned on long enough (when it DID turn on) for even formatting the disk, so I removed the SDD from it, formatted it with my MBA (connected through USB), and inserted it in the iMac again. Starting it up resulted in a few minutes being turned on, overheating and crashing. Having downloaded ML and created a USB installer for it, it was now a case of trying one's patience ... hoping for the machine to stay turned on long enough to make it all the way through the installation process.... it managed to do the first part of the installation after several hours of crashing and overheating.... and it came to a point where I simply turned it off and gave up... thinking that the problem simply was physical in nature, and not caused by Mavericks as I had assumed from the start. Next day I had renewed energy, turned the puter on and it behaved in the same way... turning off, then starting by itself trying to get through the installation.... it would fail again and again... I left the house, with it turned on, hoping that it would at least manage to finish at some point in time... so that I could write off my "BAD Mavericks" suspicion. When I returned several hours later, the installation was complete and the machine was purring quietly and the back of the computer was NOT hot like a steam iron.
Now it has been working for several days without any problems at all.
The final conclusion is this:
Mavericks IS at fault, and will physically DESTROY computers that are "somehow" not compatible with it. I would have thought that Apple had enough capable engineers to prevent the operating system to mess up the hardware in this way, but clearly I was wrong on that account. I can only WARN other people to even attempt installing Mavericks on puters of this type:
Hardware Overview:
Model Name: iMac
Model Identifier: iMac7,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: IM71.007A.B03
SMC Version (system): 1.21f4
Serial Number (system): W8*******X89
Hardware UUID: 00000000-0000-1000-8000-001B639688F7
Anyone claiming that Mavericks is not at fault, is plain and simple WRONG, in DENIAL or LYING. There is absolutely NO doubt in my mind any longer, that the problem was indeed Mavericks getting installed on the machine and messing with the hardware on a level where it should never happen. If someone working at Apple would like to purchase/replace my iMac in order to test it and figure out that this is a REAL problem, they are welcome to do so. I think it is more than guaranteed that the damage caused by this Mavericks nightmare installation will never be recovered, nor will the time and work lost ever be compensated, but I would actually like Apple to acknowledge their responsibility and failure to address this issue in a professional and responsible way.
IF Mavericks was NOT at fault, then someone should explain the logic behind the machine physically burning components shortly after the installation of Mavericks, and even when the SDD had been wiped clean with no OS, it was still overheating and shutting off, until it could finally have ML installed... and at that point it was cured and has worked flawlessly ever since. Not a single hiccup, no over heating, no problems.
My offer to sell/replace the iMac stands if Apple is really interested in looking at this SERIOUS issue with Mavericks. This is NOT a minor issue they should expect simply goes away, or will be ignored by people who experience their machines BURNING to pieces.
On my MBA and MBP Mavericks is not causing any problems, so it is not "all bad", but for the iMac it meant total annihilation.
Anyone who has installed Mavericks on their iMac of similar age as mine, having rebooting and overheating problems: REMOVE the Mavericks installation ASAP and get ML on it before it goes up in flames!
Other Mac's have been reported having the rebooting/overheating problems as well, although I have not noted down which builds those were. The problem is REAL and COSTLY for those who experience it.... both time-wise and in terms of lost time/work.
Hopefully this will help others from getting the same terrible experience as I got, and save some computers from burning up.
<Personal Information Edited by Host> -
Hi!
I've got a new 27" iMac (late 2013), and I was going to install Windows 8.1 (64-bit) to be able to play a few games.
Everything went smoothly (installed normally via Boot Camp Assistant), and after the Windows setup, the Boot Camp drivers needed to be installed. After this, the computer rebooted, but crashed at a blue screen with the error called "kernel_security_check_failure".
It rebooted a few times on its own, but after a few times, I got some options, and I chose to "refresh" the Windows 8 install, meaning it would reset the install while keeping my files (even though I didn't have any, as I never got to use it). This took some time, but it worked, and it booted into W8.
The Boot Camp drivers had been removed though, so I had to reinstall them. After they had reinstalled, the computer rebooted and the same blue screen with the same error hit me.
Something tells me that some of the BC drivers are messing things up. I can't find any information on this elsewhere.
Would it be possible to install only selected drivers, to eventually find out which driver is causing the problem?
All help is greatly appreciated!I finally gave up, reloaded everything, this time, using WIn 8.1 Pro, not Enterprise. After I did the updates, patches, Norton 360, shut computer down and connected the external drives, and booted up...and got the BSOD. This time, I went to Microsoft and downloaded the Windows Debugger, and think I may have found the problem...NORTON!
Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
Am conrtacting them, but, here's the Debugger output:
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Dump\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`0f87e000 PsLoadedModuleList = 0xfffff802`0fb482d0
Debug session time: Tue Jun 17 00:48:52.131 2014 (UTC - 6:00)
System Uptime: 0 days 0:03:09.864
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, ffffd0002852d3e0, ffffd0002852d338, 0}
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
Followup: MachineOwner
6: kd> !analyze -v
* Bugcheck Analysis *
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd0002852d3e0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0002852d338, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
TRAP_FRAME: ffffd0002852d3e0 -- (.trap 0xffffd0002852d3e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe00059c129f0 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe0005718d2a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8020f9e8cdb rsp=ffffd0002852d570 rbp=0000000000000000
r8=0000000000005aa0 r9=00000000000007ff r10=ffffd00066cc8000
r11=ffffe00059963040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
nt! ?? ::FNODOBFM::`string'+0x682b:
fffff802`0f9e8cdb cd29 int 29h
Resetting default scope
EXCEPTION_RECORD: ffffd0002852d338 -- (.exr 0xffffd0002852d338)
ExceptionAddress: fffff8020f9e8cdb (nt! ?? ::FNODOBFM::`string'+0x000000000000682b)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT
BUGCHECK_STR: 0x139
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_PARAMETER1: 0000000000000003
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff8020f9ddae9 to fffff8020f9d1fa0
STACK_TEXT:
ffffd000`2852d0b8 fffff802`0f9ddae9 : 00000000`00000139 00000000`00000003 ffffd000`2852d3e0 ffffd000`2852d338 : nt!KeBugCheckEx
ffffd000`2852d0c0 fffff802`0f9dde10 : ffffe000`59c8cc40 00000000`00000000 ffffe000`54b71040 fffff800`1d6d40b6 : nt!KiBugCheckDispatch+0x69
ffffd000`2852d200 fffff802`0f9dd034 : 00000000`00000000 00000000`00000000 ffff6d2d`50094127 fffff802`0f81458f : nt!KiFastFailDispatch+0xd0
ffffd000`2852d3e0 fffff802`0f9e8cdb : ffffc000`061df4e0 ffffc000`061df4e0 ffffc000`061dfbf8 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf4
ffffd000`2852d570 fffff800`1d7a0be6 : ffffe000`59e10120 fffff800`1d794388 ffffe000`54dfe9c8 fffff800`1d735f7c : nt! ?? ::FNODOBFM::`string'+0x682b
ffffd000`2852d5a0 fffff800`1d7a54e2 : ffffc000`061df4e0 ffffc000`061dfbf8 ffffc000`061df550 fffff800`1d7367ea : SYMDS64+0x71be6
ffffd000`2852d5d0 fffff800`1d737f20 : ffffc000`061df378 ffffc000`061dfbf8 00000000`00000000 ffffc000`05a9bf18 : SYMDS64+0x764e2
ffffd000`2852d620 fffff800`1d73e171 : ffffc000`051e6a88 ffffc000`05a9bf18 ffffc000`05a9bf18 ffffe000`5988cb00 : SYMDS64+0x8f20
ffffd000`2852d650 fffff800`1d782027 : ffffc000`061ea018 00000000`00000000 ffffe000`58409008 fffff800`1d794388 : SYMDS64+0xf171
ffffd000`2852d680 fffff800`1d79af21 : ffffc000`061ea018 ffffd000`2852d8c9 ffffe000`58409008 00000000`10000004 : SYMDS64+0x53027
ffffd000`2852d6c0 fffff800`1d9a3bb3 : ffffe000`58409078 fffff800`1d98b3e8 ffffe000`58409008 ffffd000`2852d8c9 : SYMDS64+0x6bf21
ffffd000`2852d6f0 fffff800`1d9a91fa : ffffe000`5840a1a8 ffffe000`58409008 00000000`00000000 ffffe000`00000000 : SYMEFA64+0xe9bb3
ffffd000`2852d720 fffff800`1d9ae015 : 00000000`00000000 00000000`00000000 ffffd000`2852d8c9 ffffe000`58a10e60 : SYMEFA64+0xef1fa
ffffd000`2852d760 fffff800`1d9adf4c : 00000000`01820201 ffffe000`58a10e60 ffffe000`58a10e60 ffffe000`58a10be0 : SYMEFA64+0xf4015
ffffd000`2852d790 fffff800`1d9b294c : ffffe000`59e0a150 ffffe000`58a10e60 ffffe000`5988ca80 ffffe000`58a10e60 : SYMEFA64+0xf3f4c
ffffd000`2852d7c0 fffff800`1d9a2435 : ffffd000`2852d8a0 ffffe000`599a4010 ffffd000`00000000 ffffe000`59e0a010 : SYMEFA64+0xf894c
ffffd000`2852d7f0 fffff800`1d6d528a : 00000000`00000000 ffffe000`59e0a070 ffffe000`5604e300 ffffe000`58a10e60 : SYMEFA64+0xe8435
ffffd000`2852d820 fffff800`1d71bf76 : ffffd000`2852d960 00000000`00000000 ffffe000`5604f900 ffffe000`571dab10 : fltmgr!FltpPerformPreCallbacks+0x31a
ffffd000`2852d930 fffff800`1d6d413a : ffffe000`57170dd0 ffffe000`571dabd0 ffffe000`59cf18c0 fffff802`0fd411a7 : fltmgr!FltpProcessShutdownRequest+0x122
ffffd000`2852d9b0 fffff802`0fbf7518 : ffffe000`57170dd0 00000000`00000001 ffffe000`571dabd0 fffff802`0fb54a90 : fltmgr!FltpDispatch+0x13a
ffffd000`2852da10 fffff802`0fbf7273 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopShutdownBaseFileSystems+0xb8
ffffd000`2852da90 fffff802`0fbfb722 : fffff802`0fbfb4b0 00000000`00000000 ffffe000`59963040 ffffe000`59963040 : nt!IoShutdownSystem+0x127
ffffd000`2852db10 fffff802`0f8d1adb : fffff802`0fbfb4b0 ffffd000`2852dbd0 00000000`00000000 ffffe000`59963040 : nt!PopGracefulShutdown+0x272
ffffd000`2852db50 fffff802`0f94d794 : ffffe000`59965800 ffffe000`59963040 ffffe000`59963040 ffffe000`54b71040 : nt!ExpWorkerThread+0x293
ffffd000`2852dc00 fffff802`0f9d85c6 : ffffd000`66c40180 ffffe000`59963040 ffffe000`59965800 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`2852dc60 00000000`00000000 : ffffd000`2852e000 ffffd000`28528000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
SYMDS64+71be6
fffff800`1d7a0be6 33d2 xor edx,edx
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: SYMDS64+71be6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SYMDS64
IMAGE_NAME: SYMDS64.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 51f84c44
FAILURE_BUCKET_ID: 0x139_3_SYMDS64+71be6
BUCKET_ID: 0x139_3_SYMDS64+71be6
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x139_3_symds64+71be6
FAILURE_ID_HASH: {bf9be68b-5f04-08d4-3152-3d420dc362f6}
Followup: MachineOwner -
Elements 13 doesn`t start after installing
the start windows is here with Organizer and Fotoeditor, but they cant be opened.
Windows updates are successful.
Thank you in advance!
RobertWithout exact system info nobody can tell you anything.
Mylenium -
Últimamente Photoshop CC 2014 se detiene fusionando las capas al hacer panoramas. Primero edito mis fotos Raw en Lightroom luego las paso a Photoshop para hacer panoramas. Photoshop las abre y fusionando las capas se detiene.
Según el administrador de tareas cuando se bloquea tiene ocupado el 81 % de memoria 25% de CPU y 1% del disco.
Mi PC tiene Windows 8.1 de 64 bits y tiene 8 Gb de ram
Lately Photoshop CC 2014 in my PC gets blocked when doing panoramas. First I edit my raw photos in Lightroom, then export to Photoshop for making panoramas. My Pc runs Windows 8.1 64 bits 8Gb RamÚltimamente Photoshop CC 2014 se detiene fusionando las capas al hacer panoramas. Primero edito mis fotos Raw en Lightroom luego las paso a Photoshop para hacer panoramas. Photoshop las abre y fusionando las capas se detiene.
Según el administrador de tareas cuando se bloquea tiene ocupado el 81 % de memoria 25% de CPU y 1% del disco.
Mi PC tiene Windows 8.1 de 64 bits y tiene 8 Gb de ram
Lately Photoshop CC 2014 in my PC gets blocked when doing panoramas. First I edit my raw photos in Lightroom, then export to Photoshop for making panoramas. My Pc runs Windows 8.1 64 bits 8Gb Ram -
I have mac pro i7 , 8GB RAM , 750 HDD , can i install windows 7 ultimate 64 as a parrallals desktop?
i have mac pro i7 , 8GB RAM , 750 HDD , can i install windows 7 ultimate 64 as a parrallals desktop?
Hello and welcome to Apple Support Communities!
Yes, you can install Windows 7 Ultimate 64-bit in your Mac using Parallels for Mac. Just follow the instructions of the virtualization programs during the install. Should you need any assistance with the installation process, I strongly recommend contacting Parallels Tech Support (you must register with Parallels in order to have tech support).
Alternatively, you can always use Apple's BootCamp if you want to run Windows natively in your Mac. Check their support page, Apple has a lot of good links explaining this solution.
Hope this helps! -
Web Start doesn't run after install
Hi all,
I'm wondering wether Web Start doesn't start after successful installation. Only the splash screen is shown a while when starting JWS and the administration screen doesn't pop up.
I've read some mails about similiar problems (proxy?), but didn't resolve the problem yet.
NT 4.0 SP 5, JWS 1.01._01 with RT
also tried: JSDK 1.4 beta3 with JWS included
please help. thank you
regards, thomasHello,
I am not sure, but this does sound like I had the same problem. I got the following reply:
Take a look at:
http://www.geocities.com/vamp201/jwsfaq.html
--> 'Why can't I start Web Start's app manager under Windows? Why does the app manager's preferences dialog fail to appear? '
This might be a proxy issue. Try to turn off your proxy by putting
javaws.cfg.proxy.setting=NONE
in your 'javaws.cfg' file and see if it Web Start's app manager shows up then.
I have added the line mentioned above, and it worked fine. In addition I added the following line:
javaws.cfg.jre.default=0
Check this out and good luck! -
The browser doesn't start after turning off and turning on the computer
The browser doesn't start after turning off and turning on the computer. I tried to delete the program entirely (along with personal preferences), create a new account, install a different browser versions. All this did not help. (I have Windows 7.) Help, please! Every day I have to reinstall Firefox!
Hello Nastena, try a clean re-install, certain Firefox problems can be solved by performing a ''Clean reinstall''. This means you '''remove Firefox program files''' and then reinstall Firefox. Please follow these steps:
'''Note:''' You might want to print these steps or view them in another browser.
#Download the latest Desktop version of Firefox from http://www.mozilla.org and save the setup file to your computer.
#After the download finishes, close all Firefox windows (click Exit from the Firefox or File menu).
#Delete the Firefox installation folder, which is located in one of these locations, by default:
#*'''Windows:'''
#**C:\Program Files\Mozilla Firefox
#**C:\Program Files (x86)\Mozilla Firefox
#*'''Mac:''' Delete Firefox from the Applications folder.
#*'''Linux:''' If you installed Firefox with the distro-based package manager, you should use the same way to uninstall it - see [[Installing Firefox on Linux]]. If you downloaded and installed the binary package from the [http://www.mozilla.org/firefox#desktop Firefox download page], simply remove the folder ''firefox'' in your home directory.
#Now, go ahead and reinstall Firefox:
##Double-click the downloaded installation file and go through the steps of the installation wizard.
##Once the wizard is finished, choose to directly open Firefox after clicking the Finish button.
Please report back to see if this helped you!
* check also if your antivirus or other security software(firewall, antispyware etc) blocks firefox access.
thank you -
[SOLVED] Xorg doesn't start after upgrade to 1.17.1
Archlinux i686
Intel Core 2 Duo 6600
01:00.0 VGA compatible controller: NVIDIA Corporation G71 [GeForce 7900 GT/GTO] (rev a1)
After following upgrades:
[2015-02-26 03:27] [PACMAN] Running 'pacman -S mesa mesa-demos mesa-libgl'
[2015-02-26 03:27] [ALPM] transaction started
[2015-02-26 03:28] [ALPM] upgraded mesa (10.4.2-1 -> 10.4.5-1)
[2015-02-26 03:28] [ALPM] upgraded mesa-libgl (10.4.2-1 -> 10.4.5-1)
[2015-02-26 03:28] [ALPM] upgraded mesa-demos (8.2.0-3 -> 8.2.0-4)
[2015-02-26 03:28] [ALPM] transaction completed
[2015-02-26 03:28] [PACMAN] Running 'pacman -S xorg-server xorg-server-common'
[2015-02-26 03:29] [ALPM] transaction started
[2015-02-26 03:29] [ALPM] removed xf86-video-vesa (2.3.2-5)
[2015-02-26 03:29] [ALPM] removed xf86-video-nouveau (1.0.11-2)
[2015-02-26 03:29] [ALPM] removed xf86-video-modesetting (0.9.0-2)
[2015-02-26 03:29] [ALPM] upgraded xorg-server-common (1.16.3-2 -> 1.17.1-3)
[2015-02-26 03:29] [ALPM] upgraded xorg-server (1.16.3-2 -> 1.17.1-3)
Xorg doesn't start after reboot and I found following kernel message:
kernel: [drm:drm_mmap_locked] *ERROR* Could not find map
and /var/log/Xorg.0.log looks like this:
[ 5.591]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[ 5.591] X Protocol Version 11, Revision 0
[ 5.591] Build Operating System: Linux 3.18.6-1-ARCH i686
[ 5.591] Current Operating System: Linux emeria7 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:59:29 CET 2015 i686
[ 5.591] Kernel command line: root=/dev/disk/by-label/archroot rw
[ 5.591] Build Date: 22 February 2015 12:52:47PM
[ 5.591]
[ 5.592] Current version of pixman: 0.32.6
[ 5.592] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 5.592] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 5.592] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 26 14:58:35 2015
[ 5.597] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 5.597] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 5.598] (==) ServerLayout "ServerLayout0"
[ 5.598] (==) No screen section available. Using defaults.
[ 5.598] (**) |-->Screen "Default Screen Section" (0)
[ 5.598] (**) | |-->Monitor "<default monitor>"
[ 5.599] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 5.599] (**) | |-->Device "Device0"
[ 5.599] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 5.599] (**) Option "BlankTime" "0"
[ 5.599] (**) Option "StandbyTime" "0"
[ 5.599] (**) Option "SuspendTime" "0"
[ 5.599] (**) Option "OffTime" "0"
[ 5.599] (==) Automatically adding devices
[ 5.599] (==) Automatically enabling devices
[ 5.599] (==) Automatically adding GPU devices
[ 5.608] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 5.608] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 5.608] (**) Extension "Composite" is disabled
[ 5.608] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 5.608] (II) Loader magic: 0x829e700
[ 5.608] (II) Module ABI versions:
[ 5.608] X.Org ANSI C Emulation: 0.4
[ 5.608] X.Org Video Driver: 19.0
[ 5.608] X.Org XInput driver : 21.0
[ 5.608] X.Org Server Extension : 9.0
[ 5.611] (EE) systemd-logind: failed to get session: PID 995 does not belong to any known session
[ 5.611] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 5.612] (--) PCI:*(0:1:0:0) 10de:0291:107d:2a62 rev 161, Mem @ 0xfd000000/16777216, 0xc0000000/268435456, 0xfc000000/16777216, I/O @ 0x0000ac00/128, BIOS @ 0x????????/131072
[ 5.612] (II) Open ACPI successful (/var/run/acpid.socket)
[ 5.613] (II) LoadModule: "glx"
[ 5.616] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 5.632] (II) Module glx: vendor="X.Org Foundation"
[ 5.632] compiled for 1.17.1, module version = 1.0.0
[ 5.632] ABI class: X.Org Server Extension, version 9.0
[ 5.632] (==) AIGLX enabled
[ 5.632] (==) Matched nouveau as autoconfigured driver 0
[ 5.632] (==) Matched nv as autoconfigured driver 1
[ 5.632] (==) Matched nouveau as autoconfigured driver 2
[ 5.632] (==) Matched nv as autoconfigured driver 3
[ 5.632] (==) Matched modesetting as autoconfigured driver 4
[ 5.632] (==) Matched fbdev as autoconfigured driver 5
[ 5.632] (==) Matched vesa as autoconfigured driver 6
[ 5.632] (==) Assigned the driver to the xf86ConfigLayout
[ 5.632] (II) LoadModule: "nouveau"
[ 5.632] (WW) Warning, couldn't open module nouveau
[ 5.632] (II) UnloadModule: "nouveau"
[ 5.632] (II) Unloading nouveau
[ 5.632] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 5.633] (II) LoadModule: "nv"
[ 5.633] (WW) Warning, couldn't open module nv
[ 5.633] (II) UnloadModule: "nv"
[ 5.633] (II) Unloading nv
[ 5.633] (EE) Failed to load module "nv" (module does not exist, 0)
[ 5.633] (II) LoadModule: "modesetting"
[ 5.633] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 5.634] (II) Module modesetting: vendor="X.Org Foundation"
[ 5.634] compiled for 1.17.1, module version = 1.17.1
[ 5.634] Module class: X.Org Video Driver
[ 5.634] ABI class: X.Org Video Driver, version 19.0
[ 5.634] (II) LoadModule: "fbdev"
[ 5.634] (WW) Warning, couldn't open module fbdev
[ 5.634] (II) UnloadModule: "fbdev"
[ 5.634] (II) Unloading fbdev
[ 5.634] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 5.634] (II) LoadModule: "vesa"
[ 5.634] (WW) Warning, couldn't open module vesa
[ 5.634] (II) UnloadModule: "vesa"
[ 5.634] (II) Unloading vesa
[ 5.634] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 5.634] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 5.634] (++) using VT number 7
[ 5.635] (II) modeset(0): using drv /dev/dri/card0
[ 5.635] (II) modeset(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 5.636] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[ 5.636] (==) modeset(0): RGB weight 888
[ 5.636] (==) modeset(0): Default visual is TrueColor
[ 5.636] (II) Loading sub module "glamoregl"
[ 5.636] (II) LoadModule: "glamoregl"
[ 5.636] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 5.647] (II) Module glamoregl: vendor="X.Org Foundation"
[ 5.647] compiled for 1.17.1, module version = 1.0.0
[ 5.647] ABI class: X.Org ANSI C Emulation, version 0.4
[ 5.647] (II) glamor: OpenGL accelerated X.org driver based.
[ 5.772] (II) glamor: EGL version 1.4 (DRI2):
[ 5.786] (II) modeset(0): glamor initialized
[ 5.786] (II) Loading sub module "dri2"
[ 5.786] (II) LoadModule: "dri2"
[ 5.786] (II) Module "dri2" already built-in
[ 5.843] (II) modeset(0): Output DVI-0 has no monitor section
[ 5.896] (II) modeset(0): Output DVI-1 has no monitor section
[ 5.950] (II) modeset(0): Output TV-0 has no monitor section
[ 6.006] (II) modeset(0): EDID for output DVI-0
[ 6.006] (II) modeset(0): Manufacturer: SAM Model: 76f Serial#: 1110590261
[ 6.006] (II) modeset(0): Year: 2011 Week: 8
[ 6.006] (II) modeset(0): EDID Version: 1.3
[ 6.006] (II) modeset(0): Digital Display Input
[ 6.006] (II) modeset(0): Max Image Size [cm]: horiz.: 51 vert.: 29
[ 6.006] (II) modeset(0): Gamma: 2.20
[ 6.006] (II) modeset(0): DPMS capabilities: Off
[ 6.006] (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 6.006] (II) modeset(0): First detailed timing is preferred mode
[ 6.006] (II) modeset(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
[ 6.006] (II) modeset(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
[ 6.006] (II) modeset(0): Supported established timings:
[ 6.006] (II) modeset(0): 720x400@70Hz
[ 6.006] (II) modeset(0): 640x480@60Hz
[ 6.006] (II) modeset(0): 640x480@67Hz
[ 6.006] (II) modeset(0): 640x480@72Hz
[ 6.006] (II) modeset(0): 640x480@75Hz
[ 6.006] (II) modeset(0): 800x600@56Hz
[ 6.006] (II) modeset(0): 800x600@60Hz
[ 6.006] (II) modeset(0): 800x600@72Hz
[ 6.006] (II) modeset(0): 800x600@75Hz
[ 6.006] (II) modeset(0): 832x624@75Hz
[ 6.006] (II) modeset(0): 1024x768@60Hz
[ 6.006] (II) modeset(0): 1024x768@70Hz
[ 6.006] (II) modeset(0): 1024x768@75Hz
[ 6.006] (II) modeset(0): 1280x1024@75Hz
[ 6.006] (II) modeset(0): 1152x864@75Hz
[ 6.006] (II) modeset(0): Manufacturer's mask: 0
[ 6.006] (II) modeset(0): Supported standard timings:
[ 6.006] (II) modeset(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 6.006] (II) modeset(0): #1: hsize: 1280 vsize 800 refresh: 60 vid: 129
[ 6.006] (II) modeset(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 6.006] (II) modeset(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 6.006] (II) modeset(0): #4: hsize: 1440 vsize 900 refresh: 60 vid: 149
[ 6.006] (II) modeset(0): #5: hsize: 1440 vsize 900 refresh: 75 vid: 3989
[ 6.007] (II) modeset(0): #6: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
[ 6.007] (II) modeset(0): #7: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 6.007] (II) modeset(0): Supported detailed timing:
[ 6.007] (II) modeset(0): clock: 148.5 MHz Image Size: 509 x 286 mm
[ 6.007] (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 6.007] (II) modeset(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 6.007] (II) modeset(0): Supported detailed timing:
[ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
[ 6.007] (II) modeset(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
[ 6.007] (II) modeset(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 6.007] (II) modeset(0): Ranges: V min: 50 V max: 75 Hz, H min: 31 H max: 81 kHz, PixClock max 175 MHz
[ 6.007] (II) modeset(0): Monitor name: SMBX2331
[ 6.007] (II) modeset(0): Supported detailed timing:
[ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
[ 6.007] (II) modeset(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
[ 6.007] (II) modeset(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
[ 6.007] (II) modeset(0): Supported detailed timing:
[ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
[ 6.007] (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 6.007] (II) modeset(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
[ 6.007] (II) modeset(0): Supported detailed timing:
[ 6.007] (II) modeset(0): clock: 74.2 MHz Image Size: 509 x 286 mm
[ 6.007] (II) modeset(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
[ 6.007] (II) modeset(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 6.007] (II) modeset(0): Supported detailed timing:
[ 6.007] (II) modeset(0): clock: 27.0 MHz Image Size: 509 x 286 mm
[ 6.007] (II) modeset(0): h_active: 720 h_sync: 732 h_sync_end 796 h_blank_end 864 h_border: 0
[ 6.007] (II) modeset(0): v_active: 576 v_sync: 581 v_sync_end 586 v_blanking: 625 v_border: 0
[ 6.007] (II) modeset(0): Supported detailed timing:
[ 6.007] (II) modeset(0): clock: 27.0 MHz Image Size: 509 x 286 mm
[ 6.007] (II) modeset(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
[ 6.007] (II) modeset(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
[ 6.007] (II) modeset(0): Number of EDID sections to follow: 1
[ 6.007] (II) modeset(0): EDID (in hex):
[ 6.007] (II) modeset(0): 00ffffffffffff004c2d6f0735433242
[ 6.007] (II) modeset(0): 0815010380331d782aee91a3544c9926
[ 6.007] (II) modeset(0): 0f5054bfef80714f8100814081809500
[ 6.007] (II) modeset(0): 950fa940b300023a801871382d40582c
[ 6.007] (II) modeset(0): 4500fd1e1100001e011d007251d01e20
[ 6.007] (II) modeset(0): 6e285500fd1e1100001e000000fd0032
[ 6.007] (II) modeset(0): 4b1f5111000a202020202020000000fc
[ 6.007] (II) modeset(0): 00534d4258323333310a2020202001ee
[ 6.007] (II) modeset(0): 02031cf14890041f0514131203230907
[ 6.007] (II) modeset(0): 078301000066030c00100080011d80d0
[ 6.007] (II) modeset(0): 721c1620102c2580fd1e1100009e011d
[ 6.007] (II) modeset(0): 8018711c1620582c2500fd1e1100009e
[ 6.007] (II) modeset(0): 011d00bc52d01e20b8285540fd1e1100
[ 6.007] (II) modeset(0): 001e8c0ad090204031200c405500fd1e
[ 6.007] (II) modeset(0): 110000188c0ad08a20e02d10103e9600
[ 6.007] (II) modeset(0): fd1e110000180000000000000000004c
[ 6.007] (II) modeset(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
[ 6.007] (II) modeset(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
[ 6.007] (II) modeset(0): Printing probed modes for output DVI-0
[ 6.007] (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 6.007] (II) modeset(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[ 6.007] (II) modeset(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[ 6.007] (II) modeset(0): Modeline "1600x1200"x65.0 175.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (81.2 kHz d)
[ 6.007] (II) modeset(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 6.007] (II) modeset(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 6.007] (II) modeset(0): Modeline "1400x1050"x74.8 155.80 1400 1464 1784 1912 1050 1052 1064 1090 +hsync +vsync (81.5 kHz d)
[ 6.007] (II) modeset(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
[ 6.007] (II) modeset(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 6.007] (II) modeset(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 6.007] (II) modeset(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
[ 6.007] (II) modeset(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 6.007] (II) modeset(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 6.007] (II) modeset(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[ 6.007] (II) modeset(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 6.007] (II) modeset(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 6.007] (II) modeset(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
[ 6.007] (II) modeset(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 6.007] (II) modeset(0): Modeline "1024x768"x75.0 170.24 1024 1108 1220 1416 768 768 770 801 doublescan -hsync +vsync (120.2 kHz d)
[ 6.007] (II) modeset(0): Modeline "1024x768"x60.0 133.47 1024 1100 1212 1400 768 768 770 794 doublescan -hsync +vsync (95.3 kHz d)
[ 6.007] (II) modeset(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 6.007] (II) modeset(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz d)
[ 6.007] (II) modeset(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 6.007] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 6.008] (II) modeset(0): Modeline "960x720"x75.0 148.50 960 1032 1144 1320 720 720 722 750 doublescan -hsync +vsync (112.5 kHz d)
[ 6.008] (II) modeset(0): Modeline "960x720"x60.0 117.00 960 1024 1128 1300 720 720 722 750 doublescan -hsync +vsync (90.0 kHz d)
[ 6.008] (II) modeset(0): Modeline "928x696"x75.0 144.00 928 992 1104 1280 696 696 698 750 doublescan -hsync +vsync (112.5 kHz d)
[ 6.008] (II) modeset(0): Modeline "928x696"x60.1 109.15 928 976 1088 1264 696 696 698 719 doublescan -hsync +vsync (86.4 kHz d)
[ 6.008] (II) modeset(0): Modeline "896x672"x75.0 130.50 896 944 1052 1228 672 672 674 708 doublescan -hsync +vsync (106.3 kHz d)
[ 6.008] (II) modeset(0): Modeline "896x672"x60.0 102.40 896 960 1060 1224 672 672 674 697 doublescan -hsync +vsync (83.7 kHz d)
[ 6.008] (II) modeset(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 6.008] (II) modeset(0): Modeline "800x600"x75.0 101.25 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (93.8 kHz d)
[ 6.008] (II) modeset(0): Modeline "800x600"x70.0 94.50 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (87.5 kHz d)
[ 6.008] (II) modeset(0): Modeline "800x600"x65.0 87.75 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (81.2 kHz d)
[ 6.008] (II) modeset(0): Modeline "800x600"x60.0 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (75.0 kHz d)
[ 6.008] (II) modeset(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 6.008] (II) modeset(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 6.008] (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 6.008] (II) modeset(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 6.008] (II) modeset(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
[ 6.008] (II) modeset(0): Modeline "700x525"x74.8 77.90 700 732 892 956 525 526 532 545 doublescan +hsync +vsync (81.5 kHz d)
[ 6.008] (II) modeset(0): Modeline "700x525"x60.0 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (64.9 kHz d)
[ 6.008] (II) modeset(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 6.008] (II) modeset(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 6.008] (II) modeset(0): Modeline "640x512"x75.0 67.50 640 648 720 844 512 512 514 533 doublescan +hsync +vsync (80.0 kHz d)
[ 6.008] (II) modeset(0): Modeline "640x512"x60.0 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (64.0 kHz d)
[ 6.008] (II) modeset(0): Modeline "640x480"x60.0 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (60.0 kHz d)
[ 6.008] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 6.008] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 6.008] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz d)
[ 6.008] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz d)
[ 6.008] (II) modeset(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 6.008] (II) modeset(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 6.008] (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 6.008] (II) modeset(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 6.008] (II) modeset(0): Modeline "576x432"x75.0 54.00 576 608 672 800 432 432 434 450 doublescan +hsync +vsync (67.5 kHz d)
[ 6.008] (II) modeset(0): Modeline "512x384"x75.0 39.38 512 520 568 656 384 384 386 400 doublescan +hsync +vsync (60.0 kHz d)
[ 6.008] (II) modeset(0): Modeline "512x384"x70.1 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync (56.5 kHz d)
[ 6.008] (II) modeset(0): Modeline "512x384"x60.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz d)
[ 6.008] (II) modeset(0): Modeline "416x312"x74.7 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync (49.7 kHz d)
[ 6.008] (II) modeset(0): Modeline "400x300"x72.2 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync (48.1 kHz d)
[ 6.008] (II) modeset(0): Modeline "400x300"x75.1 24.75 400 408 448 528 300 300 302 312 doublescan +hsync +vsync (46.9 kHz d)
[ 6.008] (II) modeset(0): Modeline "400x300"x60.3 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz d)
[ 6.008] (II) modeset(0): Modeline "400x300"x56.3 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz d)
[ 6.008] (II) modeset(0): Modeline "320x240"x72.8 15.75 320 332 352 416 240 244 246 260 doublescan -hsync -vsync (37.9 kHz d)
[ 6.008] (II) modeset(0): Modeline "320x240"x75.0 15.75 320 328 360 420 240 240 242 250 doublescan -hsync -vsync (37.5 kHz d)
[ 6.008] (II) modeset(0): Modeline "320x240"x60.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz d)
[ 6.063] (II) modeset(0): EDID for output DVI-1
[ 6.116] (II) modeset(0): EDID for output TV-0
[ 6.116] (II) modeset(0): Output DVI-0 connected
[ 6.116] (II) modeset(0): Output DVI-1 disconnected
[ 6.116] (II) modeset(0): Output TV-0 disconnected
[ 6.116] (II) modeset(0): Using exact sizes for initial modes
[ 6.116] (II) modeset(0): Output DVI-0 using initial mode 1920x1080
[ 6.116] (II) modeset(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 6.116] (==) modeset(0): DPI set to (96, 96)
[ 6.116] (II) Loading sub module "fb"
[ 6.116] (II) LoadModule: "fb"
[ 6.117] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 6.118] (II) Module fb: vendor="X.Org Foundation"
[ 6.118] compiled for 1.17.1, module version = 1.0.0
[ 6.118] ABI class: X.Org ANSI C Emulation, version 0.4
[ 6.118] (==) Depth 24 pixmap format is 32 bpp
[ 6.462] (==) modeset(0): Backing store disabled
[ 6.462] (==) modeset(0): Silken mouse enabled
[ 6.464] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 6.535] (==) modeset(0): DPMS enabled
[ 6.535] (WW) modeset(0): Option "EXANoComposite" is not used
[ 6.535] (II) modeset(0): [DRI2] Setup complete
[ 6.535] (II) modeset(0): [DRI2] DRI driver: nouveau
[ 6.535] (II) modeset(0): [DRI2] VDPAU driver: nouveau
[ 6.535] (--) RandR disabled
[ 6.551] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 6.551] (II) AIGLX: enabled GLX_ARB_create_context
[ 6.551] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 6.551] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 6.551] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 6.551] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 6.551] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 6.551] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 6.551] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 6.552] (II) AIGLX: Loaded and initialized nouveau
[ 6.552] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 6.559] (II) modeset(0): Setting screen physical size to 507 x 285
[ 6.741] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 6.741] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 6.741] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 6.741] (II) LoadModule: "evdev"
[ 6.741] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 6.744] (II) Module evdev: vendor="X.Org Foundation"
[ 6.744] compiled for 1.16.2, module version = 2.9.1
[ 6.744] Module class: X.Org XInput Driver
[ 6.744] ABI class: X.Org XInput driver, version 21.0
[ 6.744] (II) Using input driver 'evdev' for 'Power Button'
[ 6.744] (**) Power Button: always reports core events
[ 6.744] (**) evdev: Power Button: Device: "/dev/input/event3"
[ 6.744] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 6.744] (--) evdev: Power Button: Found keys
[ 6.744] (II) evdev: Power Button: Configuring as keyboard
[ 6.744] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[ 6.744] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 6.744] (**) Option "xkb_rules" "evdev"
[ 6.744] (**) Option "xkb_model" "pc104"
[ 6.744] (**) Option "xkb_layout" "us"
[ 6.744] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 6.780] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 6.780] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 6.780] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 6.780] (II) Using input driver 'evdev' for 'Power Button'
[ 6.780] (**) Power Button: always reports core events
[ 6.780] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 6.780] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 6.780] (--) evdev: Power Button: Found keys
[ 6.780] (II) evdev: Power Button: Configuring as keyboard
[ 6.780] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2"
[ 6.780] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 6.780] (**) Option "xkb_rules" "evdev"
[ 6.780] (**) Option "xkb_model" "pc104"
[ 6.780] (**) Option "xkb_layout" "us"
[ 6.780] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 6.781] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event4)
[ 6.781] (II) No input driver specified, ignoring this device.
[ 6.781] (II) This device may have been added with another device file.
[ 6.782] (II) config/udev: Adding input device HDA Intel Line Out Side (/dev/input/event10)
[ 6.782] (II) No input driver specified, ignoring this device.
[ 6.782] (II) This device may have been added with another device file.
[ 6.782] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event5)
[ 6.782] (II) No input driver specified, ignoring this device.
[ 6.782] (II) This device may have been added with another device file.
[ 6.782] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event6)
[ 6.782] (II) No input driver specified, ignoring this device.
[ 6.782] (II) This device may have been added with another device file.
[ 6.783] (II) config/udev: Adding input device HDA Intel Line Out Front (/dev/input/event7)
[ 6.783] (II) No input driver specified, ignoring this device.
[ 6.783] (II) This device may have been added with another device file.
[ 6.783] (II) config/udev: Adding input device HDA Intel Line Out Surround (/dev/input/event8)
[ 6.783] (II) No input driver specified, ignoring this device.
[ 6.783] (II) This device may have been added with another device file.
[ 6.783] (II) config/udev: Adding input device HDA Intel Line Out CLFE (/dev/input/event9)
[ 6.783] (II) No input driver specified, ignoring this device.
[ 6.783] (II) This device may have been added with another device file.
[ 6.784] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event1)
[ 6.784] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
[ 6.784] (II) Using input driver 'evdev' for 'Logitech USB-PS/2 Optical Mouse'
[ 6.784] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
[ 6.784] (**) evdev: Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event1"
[ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Vendor 0x46d Product 0xc050
[ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
[ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
[ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found relative axes
[ 6.784] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
[ 6.784] (II) evdev: Logitech USB-PS/2 Optical Mouse: Configuring as mouse
[ 6.784] (II) evdev: Logitech USB-PS/2 Optical Mouse: Adding scrollwheel support
[ 6.784] (**) evdev: Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
[ 6.784] (**) evdev: Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 6.784] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/0003:046D:C050.0001/input/input1/event1"
[ 6.784] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE, id 8)
[ 6.784] (II) evdev: Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
[ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
[ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
[ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
[ 6.784] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
[ 6.785] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
[ 6.785] (II) No input driver specified, ignoring this device.
[ 6.785] (II) This device may have been added with another device file.
[ 6.785] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 6.785] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 6.785] (**) AT Translated Set 2 keyboard: Applying InputClass "Keyboard Defaults"
[ 6.785] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 6.785] (**) AT Translated Set 2 keyboard: always reports core events
[ 6.785] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 6.785] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 6.785] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 6.785] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 6.785] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 6.785] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 6.785] (**) Option "xkb_rules" "evdev"
[ 6.785] (**) Option "xkb_model" "pc104"
[ 6.785] (**) Option "xkb_layout" "us"
[ 6.785] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 6.803] (EE)
[ 6.803] (EE) Backtrace:
[ 6.803] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x132) [0x81df9e2]
[ 6.804] (EE) 1: ? (?+0x132) [0xb7787cc5]
[ 6.804] (EE) 2: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x4cd7) [0xb6e2a1c7]
[ 6.806] (EE) 3: /usr/lib/xorg-server/Xorg (xf86_show_cursors+0x688) [0x80f9008]
[ 6.806] (EE) 4: /usr/lib/xorg-server/Xorg (xf86DestroyCursorInfoRec+0xcf8) [0x8103fc8]
[ 6.806] (EE) 5: /usr/lib/xorg-server/Xorg (RamDacHandleColormaps+0x67b) [0x810218b]
[ 6.807] (EE) 6: /usr/lib/xorg-server/Xorg (miPointerUpdateSprite+0x25d) [0x81c648d]
[ 6.808] (EE) 7: /usr/lib/xorg-server/Xorg (miPointerUpdateSprite+0x4c1) [0x81c6b31]
[ 6.808] (EE) 8: /usr/lib/xorg-server/Xorg (CompositeRegisterImplicitRedirectionException+0x4199) [0x8114399]
[ 6.809] (EE) 9: /usr/lib/xorg-server/Xorg (PanoramiXRenderReset+0x72a) [0x815915a]
[ 6.810] (EE) 10: /usr/lib/xorg-server/Xorg (ConfineToShape+0x9f1) [0x80843b1]
[ 6.810] (EE) 11: /usr/lib/xorg-server/Xorg (WindowHasNewCursor+0x3b) [0x8084f2b]
[ 6.810] (EE) 12: /usr/lib/xorg-server/Xorg (ChangeWindowAttributes+0xb7c) [0x80aa9ec]
[ 6.811] (EE) 13: /usr/lib/xorg-server/Xorg (ProcBadRequest+0x209) [0x8074a49]
[ 6.811] (EE) 14: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x3a6) [0x807abf6]
[ 6.811] (EE) 15: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x42f) [0x807edaf]
[ 6.811] (EE) 16: /usr/lib/xorg-server/Xorg (miPolyFillRect+0x27f) [0x8068ddf]
[ 6.814] (EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xde) [0xb72d864e]
[ 6.814] (EE) 18: /usr/lib/xorg-server/Xorg (_start+0x21) [0x8068bd9]
[ 6.814] (EE)
[ 6.814] (EE) Segmentation fault at address 0x0
[ 6.814] (EE)
Fatal server error:
[ 6.814] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 6.814] (EE)
[ 6.814] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 6.814] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 6.814] (EE)
[ 6.815] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 6.817] (EE) Server terminated with error (1). Closing log file.
Note the segfault in modesetting_drv.so!
Any help?
I tried to reinstall dependencies of xorg-server and mesa. And then I even went through with the whole system update which I postponed for a few weeks because of the KDE changes. Sadly even the whole system update didn't help.
Is it possible that any old config files can cause this?
EDIT:
I tried kernel parameter "nouveau.modeset=0" but it didn't help.
Last edited by cro (2015-02-26 16:33:19)Ok, I guess I solved it by reinstalling xf86-video-nouveau.
Funny business! Why did the upgrade to xorg-server 1.17.1 force me to remove it when it is still needed??
And why does that lead to mysterious error messages and segfault??
I discovered it accidentally when I stumbled upon the fact that the package was still installed on my newer x86-64 Arch installation despite being on xorg-server 1.17.1. -
FF doesn't start after update to version 27.0.1
FF doesn't start after update to version 27.0.1
Crash ID: bp-2bc18734-d643-4843-a10f-fd6102140214Firefox 27.0.1 is too new for me to know what unique issues it might have. I will message you a link to download the installer for Firefox 27.0 to see whether that reverses the problem.
-
Teamviewer doesn't start after resume from hibernation
Teamviewer doesn't start after resume from hibernation, what can I do to make it work?
I issued command "teamviewer --daemon start" but no success.Quote from: BOSSKILLER on 07-July-08, 00:03:29
That's probably BIOS bug, have a ask MSI here: http://ocss.msi.com.tw/ They can send you a new BIOS to try.
I supposed that this issue is caused by BIOS bug, and this speculation was confirmed. MSI Support has sent to me link with BIOS version 132, which solves the problem
Under this link you can find this BIOS: http://rapidshare.com/files/127845890/a7395ims.132.zip.html
Regards. -
My macbook air doesn't start after being for 2 months off? What can i do?
Plug it in and leave it on the charger for about 5 minutes then try to turn it on. If that doesnt work, contact apple and have it sent out for repair or take it to your local apple store. they will probably cover it for free if no physical damage has been done.
Maybe you are looking for
-
Lightroom 3.6 64bit on windows 7 sp1 error: the application was unable to start correctly 0xc000007
Hi, I've uninstalled, reinstalled (3.6 and later the original 3), but still nothing. I've been using LR for years without any problem but yesterday I suddenly got this message and now, whatever I try, it won't start again. This sucks big time! Any he
-
Carriage return in central text
Hi, I'd like to know how to add a carriage return character in a central text of an order document. I use SAVE_TEXT BAPI to add central text in an order. Thank you for your help.
-
I am a big iMovie fan, but I have just had a problem while attempting to create a video game trailer. I have never experienced this before, and I do not know how to get by it. Ok. So I have 20 seconds of scrolling text, and about 28 lines of text. 24
-
What is "delivery transmission report" checkbox on AS2 receiver adapter?
Hi Gurus, we have an AS2 adapter from seeburger and there is a checkbox on receiver adapter "delivery transmission report". What is this good for? Thank you, Olian
-
How to switch subscription from PC to Mac
I subscribed to Adobe CC on a PC and have since switched hardware to Mac. How do I move my subscription?