Main Forum > General Computer Support

Error "Windows could not connect to the system to the System Event Notification"

<< < (5/12) > >>

Boggin:
I was considering an overheating problem, but given it works fine in Safe Mode and how long MBAM was running for, other problems could have manifest.

However, download the free version of HWMonitor to see what the temps are like.

http://www.cpuid.com/softwares/hwmonitor.html

The freebie link is down on the left.

EDIT - What about running a chkdsk /f from the Recovery Environment ?

Tap F8 (usually) as you switch on and select Repair your Computer - change/confirm keyboard/currency etc. and navigate to the RE and select Command Prompt.

Enter bcdedit |find "osdevice" and using whichever partition letter, enter chkdsk x: /f where x is the partition letter.

That is the Pipe symbol before find which I usually explain is the uppercase of \

No reboot is required because this is done outside of Windows and it's report will be in the cmd window.

You could also use the green download button to download the trial version of HD Sentinel which will give a written report on the status of your HDD.

http://www.hdsentinel.com/

Phillip92:
Chkdsk once again came back with 0 bad sectors. Running an extended Memory Diagnostic now. Almost complete with no problems detected yet.

Also it does run the same in safe mode. No improvement at all. Now it does run ok with a Live Bootable disk in Linux/Tails which is why I was thinking in was a Windows error. After reinstalling a Clean version of W7 that was not the case.

I checked my fan and overheating stats in Bios and it was fine. Once the memory check comes through I'll try the HWMonitor as I'm running out of ideas. It appears to be a hardware issue but can find the cause.

Would either of you guys suggest taking the case apart and check for damage, loose connections, etc? I haven't done that yet since it appeared to be a software issue at first with all diagnostics coming back ok.

Sorry just saw the previous posts. I'll see if I can find the last log and take a pic. The only thing it stated was an error with the log. Status 50. If not I'll run it again as chkdsk /f.

Boggin:
The status 50 just means that it hasn't created a wininit report in Event Viewer so you don't need to bother with that.

As you have clean installed Win 7 - I assume you haven't installed any other programs yet ?

After the clean install did you need to reinstall any drivers ?

HWMonitor will give the voltages and if you are able to copy a snip of that, it may give a clue.

As it isn't overheating then the PSU could be on its way out or the cables may need reconnecting, but check the pins for cleanliness - you can also do that for the RAM modules.

Phillip92:
No I have not installed anything yet.

The only driver issue I had after the install was 802.11. It was trying to install a driver for my wireless network card which went out months ago. So I just disabled it as I have a Belkin WiFi adapter I was using previously. Haven't even connected that after the reinstall.

I'll check the inside of the computer later on today and also run the HWMonitor as well. Keep you updated. I'll try and take pics of results.

Boggin:
The BIOS may have a Hardware Monitor which will also give you the rail voltages, but they will be at idle rates.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version