thank you
Launch terminal and tail your /var/log/system.log right after you try to run Console and see if it says why its not running/crashing...
Interesting, as I pulled up terminal and followed your suggestion, console unfroze and I got the following where LCC is the logitech control center I have installed for my keyboard and mouse. I just uninstalled and reinstalled it yesterday too as the USB device was somehow the culprit behind my computer not being able to awake from sleep and firewire devices were no longer being recognized. Its being rather problematic. I would leave it uninstalled if it weren't for the button functionality I would lose on my mouse.
Apr 3 19:44:54 localhost kernel[0]: AppleFWOHCI_AsyncTransmit::waitForDMA - context not going inactive.
Apr 3 19:54:40 localhost kernel[0]: State change timeout, state is 7
Apr 3 19:55:45 localhost LCCDaemon[149]: AZTheatre posted an event which matched global settings but wasn't handled: <AZEvent: mouse ratcheting wheel status [0]>
Apr 3 19:55:45 localhost LCCDaemon[149]: AZTheatre posted an event which matched global or specific settings but wasn't handled by the fallback settings: <AZEvent: mouse ratcheting wheel status [0]>
Apr 3 19:55:47 localhost LCCDaemon[149]: AZTheatre posted an event which matched global settings but wasn't handled: <AZEvent: mouse ratcheting wheel status [0]>
Apr 3 19:55:47 localhost LCCDaemon[149]: AZTheatre posted an event which matched global or specific settings but wasn't handled by the fallback settings: <AZEvent: mouse ratcheting wheel status [0]>
Apr 3 19:59:05 localhost kernel[0]: AppleFWOHCI_AsyncTransmit::waitForDMA - context not going inactive.
Apr 3 20:08:02 localhost kernel[0]: AppleFWOHCI_AsyncTransmit::waitForDMA - context not going inactive.
Apr 3 20:14:41 localhost quicklookd[224]: [QL ERROR] /Library/QuickLook/GBQLGenerator.qlgenerator/ has no identifier: ignoring
Apr 3 20:14:44 localhost login[227]: USER_PROCESS: 227 ttys000
