Tip & How-To about Computers & Internet

Fix Windows Vista problem with event viewer not working

While there are many different things that might cause the event viewer to stop working (mainly corrupted files which mean windows reinstall *shudder*) one of the things I found that fixed the problem at one of my clients sites happened to be simple enough as reseting the winsock file.

The winsock library is supposed to be the file that never is supposed to fail according to many but on occasion it does. Of course because of this anything that is dependent on it's functions will not work correctly. Because windows vista and higher are so highly dependent on functions that require the winsock, other things will refuse to work like network (internet) connectivity and system services like event viewer.

Here is one of the easier ways to fix it without having to go through the hassle of reinstalling windows.

press start, then press all programs, goto accessories, then look for command prompt.

Don't just left click on it as we have to start it in a different mode I.E. run as administrator.

Right click on command prompt and left click on run as administrator, windows will most likely bring up the warning about if you want to do this, it is safe and of course it should be allowed.

When you see a black window with text open up, this is your command prompt.

in this window just type in the following line:

netsh winsock reset

it may run for a quick moment and could come up with some initialization errors but it will then says winsock is successfully reset and the computer needs to be restarted.

Just restart the computer and check to make sure the program or feature you were trying to use works again :)

Posted by on

Computers & Internet Logo

Related Topics:

Related Questions:

2 Answers

I have an acer that will go to a blue screen after I type in the password then it restarts itself over again the same thing!


Blue screen errors, or blue screen of death (BSOD) errors, are the most severe errors Windows can encounter. Since Windows can not recover from this kernel level error, a blue screen is displayed with the error details. The error details contain a STOP error code, which indicates the type of error.

There are a lot of possible causes for blue screen errors, but most of them relate to the computer hardware. The cause of a BSOD error can be a temperature problem, a timing error, a resource conflict, hardware failure, a corrupt registry, a virus or simply a device incompatibility or driver error.


How to analyze blue screen errors

The first thing to do to analyze a blue screen error is to check the meaning of the STOP error code. You need to stop Windows from rebooting when a STOP error is encountered. Once the blue screen of death is shown, you can check the meaning of the STOP error code. Together with the filename of the driver or module, this will give an indication of the error cause.

Another option to analyze the cause of the blue screen error is to look at the Windows system event log or to debug the memory dump (minidump) that Windows created when the error occurred. The event log can be viewed using the event viewer. Right-click Computer in the Start menu, and then select Manage. In the Computer Management window select Event Viewer. The information in the event log can be of great help to isolate the cause of the blue screen error.

Reading the minidump requires a bit more technical knowledge, but Microsoft has tools to read the minidump.


The most common cause of blue screen errors

In reality, the most common cause of blue screen errors is a device driver problem. Outdated, incorrect or corrupt drivers can cause the system to encounter a STOP error, resulting in the BSOD.

So the easiest way to try and fix a blue screen error is to reinstall and update your system's device drivers. This will ensure that all driver bugs are fixed and that all hardware has the correct driver.

If you know which device caused the error, you can update or reinstall that driver first. The file name in the blue screen of death can help identify the driver. Look for a file with the .SYS extension and search for that file name.

If you do not have the drivers for all devices, or are not comfortable updating your PC's drivers manually, you can use a driver update tool to find, download and update all device drivers for you. Such tools will accurately identify your computer hardware, including any device causing an error, and automatically install the latest drivers for it.

In most cases updating or reinstalling drivers will solve your blue screen errors.



Other causes of blue screen errors

However, if updating device drivers does not fix the blue screen error, there are a number of additional things to try:

Load the default BIOS values - resource conflicts and timing issues can be caused by incorrect BIOS settings.

Update the BIOS - especially after adding new hardware or installing a Windows service pack this can help fix issues.

Update Windows - missing updates, including service packs can be a source of stop errors.

Check your system - run a virus scan and spyware scan after updating your definition files.

Driver rollback - if you have recently updated a driver, you can use the driver rollback to revert back to the previous driver version.


hope it helps, if so rate the solution

Nov 29, 2010 | Acer Aspire 3690-2196 Notebook

1 Answer

I get error rtl100.bpl what must i do


hi
i am techbuddies from fixya group i would like to try and solve your issue .
please try to follow these steps

You probably read web pages written in a language that displays Right To Left
(hence rtl100) There are several reasons why that file might corrupt, an
add-on of some kind being the main suspect. Go to start/run, and type:

iexplore -extoff

to see it that stops the error.
If not, try refreshing all system files with :

sfc /scannow

if is doesnot work then try this

Are any devices malfunctioning? Select Start, All Programs, Accessories,
System Tools, System Information. Open Components under System Summary
and click on Problem Devices. Is anything listed there?

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Does anything turn up in the Event Viewer Logs?

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.
if the same problem comes up please try to get in touch with me on my email or on fixya

thanks
techbuddies

Dec 30, 2009 | Dell Microsoft Windows XP Home Edition

2 Answers

Age of kings stopped working


Uninstall the game and reinstall it. Make sure you backup all your saved games first.

Sep 01, 2009 | Microsoft Age of Empires 2: Age of Kings...

1 Answer

windows dvd maker


What OS are you using? Ultimate, Premium, Basic?
Windows DVD Maker has stopped working Issue : While trying to create DVD in Windows DVD Maker in Vista, or while creating a DVD from Windows Movie Maker, which uses Windows DVD Maker, the burn process stops with error message.

Error message : " Windows DVD Maker has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. "

Cause : Windows DVD maker stops working because of incompatibility with one or more codec files which are outdated or incompatible with the particular project or the DVD Maker software itself.


Resolution :

These Codec files should be located and renamed to resolve the issue.

1. Open Start menu and type Event Viewer in the Start menu search bar. Open Event Viewer from the menu.

2. In the Event Viewer window Click on Windows Logs in the left panel

3. Click on Application Logs under Windows Logs

4. Locate error messages listed in the Central panel of the Event Viewer window and double click the error to check if this is log is related to DVD Maker.

Sample Error Log :

Problem signature

Problem Event Name: APPCRASH
Application Name: DVDMaker.exe
Application Version: 6.0.6000.16386
Application Timestamp: 4549b5b0
Fault Module Name: nevideohd.ax
Fault Module Version: 4.6.15.0
Fault Module Timestamp: 459bb828
Exception Code: c0000005
Exception Offset: 00008b89
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1062


5. Locate Fault Module name, it should be a file with extension .ax.

6. Once the file name is identified, try to locate the file in C:/Windows/System32 folder. ( Please click on Show Contents if the files are not listed Automatically ).

7. If the files are not listed in System32 folder, search for the file, with search containing system files and folders.

8. Locate the file and rename it.

9. Check if the issue persists. If the issue persists and the error message again appears, locate the new .ax file that is causing the issue from the Event Viewer, error log.

These steps will resolve the issue instantly without a restart.


Sep 18, 2008 | Computers & Internet

Not finding what you are looking for?

122 people viewed this tip

Ask a Question

Usually answered in minutes!

Top Computers & Internet Experts

Doctor PC
Doctor PC

Level 3 Expert

7733 Answers

kakima

Level 3 Expert

102366 Answers

David Payne
David Payne

Level 3 Expert

14161 Answers

Are you a Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Loading...