Main Forum > General Computer Support
Error "Windows could not connect to the system to the System Event Notification"
Phillip92:
Well gentlemen after taking it apart cleaning it and double checking all connections it is now running faster. Still getting the same window error at startup and not quite as fast, a little lag. I feel kinda dumb feeling like I should have done that earlier but it seemed like a software error from the get go. I'm going to do all the window updates and go from there. Thank you both once again! I sure learned a lot but shit man my frusturation level was through the roof as I can fix others peoples computer but not my own :-/ I'll update on my status once I get up back up and running.
Julian:
so it ended up being a loose connection or dusty components eh? well that's a good start :D
Boggin:
As you are still getting the error message on start up after the clean out and reconnecting etc. - this is starting to look like a BIOS problem and either looking for a BIOS update or resetting the CMOS would be worth doing.
For info - this is the purpose of the BIOS http://smallbusiness.chron.com/purpose-bios-computer-69278.html
You'll probably need to Google for the Service manual for your machine/motherboard to reset the CMOS, as it isn't always a case of just removing the CMOS battery for a few mins - you normally have to swap a jumper to short the CMOS chip out.
The computer support site if OEM build will have any BIOS updates but if a custom built machine, then you will have to Google the motherboard number and it will probably be worth reinstalling the Chipset drivers after, followed by Video then Audio drivers.
Phillip92:
Sorry haven't responded but been busy. The error came up right after the clean up and reconnections but not anymore for a couple of days. It ran great for a couple days then started slowing up again :( if I power it off for a couple hours it boots up ok but starts again. Believe it might be the be a power supply problem or overheating. Running HWMonitor now to see what it shows. Not exActly sure what to look for on it though. Googling it now.
Shane:
I had this error show up on a few machine and some of them even fresh new installs that I was doing!
I noticed on the new installs it had happened after I installed the IDT audio driver. So I uninstalled the driver and rebooted and the error went away. Turns out it was causing a service to hang for a few before it would start and would cause the error at startup and would be fine after a min or so had pasted.
So as a test, try uninstalling your audio driver and software and see if that does the trick.
Shane
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version