Argh! Frustrating PC problem, any experts out there?
Just looked through the Event Viewer and found this error, which I think is indicative of the other errors, but I am not 100% certain.
Faulting application ibmmessages.exe, version 1.1.0.3, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00036bd1.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Darn IBM messages!!! That's the first thing I whack on a new IBM/Levono... you don't need it. You mentioned its multiple programs though? Hopefully ntdll.dll is the cause... your looking for any patterns in the error and hopefully something stands out.
Running msconfig(from start-->run) you can test to see if that is the problem.
Click Diagnostic Startup
Under System.ini and win.ini tabs click the button that enables all
Boot.ini should be fine
Under services and startup enable all and then uncheck ibmmessenges and reboot. See if your computer runs fine, if so you can just remove it from the registry or startup menu.
Click Diagnostic Startup
Under System.ini and win.ini tabs click the button that enables all
Boot.ini should be fine
Under services and startup enable all and then uncheck ibmmessenges and reboot. See if your computer runs fine, if so you can just remove it from the registry or startup menu.
I have actually rebooted without ibmmessages.exe running (removed via msconfig) very early on and, while I obviously did not see that particular error, I still did see other errors, including:
I am wondering why none of the EAccessViolation errors are logged in the Event Viewer...
Faulting application firefox.exe, version 1.8.20060.25382, faulting module xpcom_core.dll, version 1.8.20060.25382, fault address 0x0001fbc7.
To add...I reviewed my Firefox history and found this tidbit I searched:
(I think I removed the actual numbers at the end to find more results...)
"Exception EaccessViolation in module unins000"
Originally Posted by dzervit
If you'd like, export your app & system logs out of event viewer and e-mail them to me. Going to be faster than this hit 'n miss stuff we are doing now.
Originally Posted by webmaster
Thanks!!! I will fire them off to your email address on record here...
Keeping current with your SQL service packs may help... you appear to be on SP2 when SP3a is out... MicroSquish says that will help one of your issues (related to the failure of SQLServer starting, not the other errors). Lemme dig around some more...
When SQL Server failed to start (120 day SQL 2000 eval) I think that I removed and reinstalled it (120 SQL 2000 eval) and downloaded the lastest SQL2000 Eval package that included protection against the slammer vulnerability. It worked perfectly prior to this issue, whatever it is. I also tried to apply the fixes on MS's website regarding "EXCEPTION ACCESS VIOLATION" errors and it still refused to start.


