Use of a desktop PC along with its internet applications is really something which has made a revolutionary change in the very basic way of living the everyday life and the associated activities in every home all across the globe.

Performing a wide variety of tasks ranging from quite simple to extremely laborious and complicated with equal ease, computers can truly be described as ‘the’ symbol of a modern urban life and its technical and technological dependence. But just like any other technical domestic equipment, even a home PC can really be a cause of trouble for the user at times. Under such circumstances, what happens mostly is that the entire set of applications dependent on the computer has to be suspended for a time period while it remains dysfunctional awaiting professional help. Sometimes, as we’re going to see here, it’s possible to disable applications one by one and stamp out the problem.

One can not deny the fact that it saves an awful lot of time, money and energy if he or she could look in to the problem all by him or herself and solve it and restore the PC to working condition. The basic prerequisite condition to do it is to have a proper understanding of the problem that is causing all the trouble and then it is much easier a job to fix it. For instance, if we consider the case of a Sonic Update Manager problem, it can be observed that it creates one of the most annoying troubles for the PC users.

It is one of the most familiar problems faced by users of PC manufacturers like Dell and basically consists of a message window which is displayed every time a computer is switched on instructing the user to enter the Sonic CD, which in fact is not provided to the users. Thus when he or she decides to click on the cancel button, a number of similar message boxes and pop ups keep on appearing at regular intervals as long as the PC is kept switched on.

The root cause of this truly irritating and infuriating problem lays in the fact that Sonic Update Manager is not actually software but more of a derived application of the actual Sonic RecordNow software.

Now as the users generally will prefer to keep the Sonic RecordNow software installed in their PCs as it comes real handy for creating one’s own CDs and DVDs this associated application also gets installed in the program files keeps on popping time and again. Apart from this, Sonic Update Manager along with the associated applications and services are often checked in to the startup under different names, initials and locations such as update manager, sgtray, isuspm or issch, etc. among various others. Such a thing can cause the Sonic Update Manager problem by flashing those message boxes as they are always getting loaded during the process of rebooting.

Once such causes of the problem are identified, they can be taken care of quite simply without much trouble of any kind. By editing the Windows startup services, it’s possible to disable the processes completely and avoid the usual frustration.

No Comments »

Access Violation problems are generally a result of improper memory usage by the computer through different computer applications. This can actually be compared to the locking of a gate. Files become inaccessible and can not be opened without the fixing up of the access violation error. Access Violation is essentially very common with software malfunction which again usually happens due to poorly written software. Not only with Windows but also with UNIX and other operating systems that one may face the problem of access violation – although it must be said, Windows is a prime offender!

Any attempt to access the source files is nullified by the security layer that is created with the overburdening of the memory module.

Many a times the permission error i.e. access violation error can be resolved by entering a command prompt to change the file attributes. For e.g. a file can be made readable or writable without opening the file but only by the use of a command. A read-only file can not be written upon directly prompting an access violation and therefore the attributes need to be changed. The DOS command prompt is usually quite simple : ATTRIB [+R | -R] [+A|-A] [+H | -H] [[drive:][path]file] [/S] where R means Read-Only; A means Archive attribute; S is System File and H is Hidden File attribute.

In addition to these solutions other kind of access violations need to be dealt with in a different way. If the access violation is caused due to a C++ 2005 application; it may be due to an invalid code generated by the C++ compiler. A corrupted v-table is contained by the application due to the error resulting in an access violation. This can be resolved by a Hotfix available through Microsoft.

A Data Execution Prevention [DEP] was introduced in Windows XP service pack 2. It performs additional checks on memory and thus helps protect the computer against adwares/malwares and the malicious codes generated through them. Applications that violate DEP get the message for access violation. It is always possible to turn off the DEP but this would have to be the last step.

For games and other windows associated applications the access violation is generally resolved by increasing the memory module. Other Windows related access violations can be dealt with by optimization of the computer performance through readily available softwares. The softwares are able to restore processes that were causing problems with the RAM. Also, junk file cleanups and ending unused processes can avoid receiving an access violation.

Windows XP should be equipped to have at least Service Pack 2. It has a number of hotfixes that help in the debugging of related softwares and to avoid access violations. Access violation problems are not incurable. Mostly all kinds of access violations, trough device drivers, RAM, poor written softwares etc can be resolved if proper measures are taken. As a precaution, one can increase the RAM in a computer which performs tedious tasks. The last resort to solve the access violation problems is to call the computer service person or the vendor.

No Comments »

In common computer parlance any memory access violation is termed as an access violation problem or an access violation error. This can happen mainly due to illegal violations that cause the abnormal functioning of the software in question.

A faulty RAM may be at the root of the matter. Many computer users often consider their RAM to perform tasks that are either not supported with the memory allotted or might have internal problems with the memory module.

Device drivers are actually a bridge between higher level computer programs and the devices present inside a computer. It is basically a translator between the devices and the applications or the operating system. Device drivers are an important part for the proper working of the applications. There may be a case where the device working may be in danger due to installation of improper drivers for it. Due to this there may be an access violation.

Softwares are sometimes poorly written or can not be updated properly. These poorly written softwares or bugs as they are generally called can also be a causal agent of the problem. Also, malware and adware are sometimes installed unknowingly over the internet which leads to an overburdening of the memory module and may cause errors in the programs resulting in the access violations. Normally we see that certain games that are installed may have incorrect setup files which after installation show the above error.

Access violation is a reference to a corruption in the terminal services information. Tsprof.exe, Mmc.exe ,Usrmgr.exe etc are examples of Terminal Services administrative utility. When these files are executed, there may be an access violation error and the utility might quit unexpectedly. Again we will see that access violation errors are not bound to the above examples only. There are various programs that use the API functions of WTSSetUserConfig or the WTSQueryUserConfig. This is done for setting or retrieval of any user information. When these programs are run, the utility may show an access violation error and might shut itself off while it still manages certain other accounts. This error is also termed as an 0xC0000005 error.

Microsoft Windows update is another tricky venture which might lead to the access violation error. When one tries to update from Microsoft Update or Windows update, the system might go to a standby position and shows the access violation. When one tries to make a Remote Desktop connection, further trying to log on to it with a certain account, the connection may suddenly close and on restart shows the access violation error.

Access violation is normal with the scans for Microsoft updates using the Windows installer. Svchost.exe, which relates itself with the Automatic Updates Service, may receive an access violation error depending on its method of carrying out a Windows Update. This Windows Update then leads to a memory leak which lengthens the update scan.

This often leads to the malfunction of IE 6, unresponsive to web pages. Access violations are common in computer vocabulary which may result in memory locks.

No Comments »

Print Spooler is the scheduler for a print job. All of the deletion, queuing and restarting of a print job is done with the help of the print spooler. Messages from the computer to the printer or the print server are carried out by the print spooler. Certain problems have been seen to affect the print spooling in a computer. Like the problem of memory or disk space, where the unavailability leads to the stoppage of the print spooler. The sure fire way to solve this problem permanently is by increasing the memory and the hard disk space. An alternative way is to reduce the number of applications that run simultaneously, thereby freeing up some memory and valuable virtual memory.

Print spooler problems might arise from incompatibility to the operating system. One should clarify with the vendor if the printer is compatible with different versions of windows. Recently some printers have been found to give problems with windows vista. And with it the driver CDs should also be supported by the operating system.

A very irritating problem is when a printer can not be added to the computer. This usually occurs due to some third party drivers associated with the printer, which prevents the computer from adding new printers. Some printer services installed before the actual printer is installed may lead to such kind of problems.

A small check and modification of the registry will help solve this problem. Start the computer in safe mode by going to the Windows Advanced Option by pressing the F8 key while the computer starts an then selecting the safe mode option from there. The Microsoft Windows Explorer should then be started and the files in the following folders should be deleted.

C:\Windows\System32\Spool Printers and C:\Windows\System 32
\Spool\Drivers\w32×86.

Then start the registry editor by typing regedit in the Run dialog box. Find HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\
Environments\Windows NT x86.
Check whether there are only two subkeys – Drivers and Print Processors. If anything else is present then click Export on the file menu; type the name that you would like to use in the File Name Box and then click Save.

It should be noted that the print spooling, if not functioning properly, then any addition or removal of printers can not be carried out. The option will not be visible in the control panel. Clanspl.exe is a utility that is found in the Windows Resource Kit tools easily available over the internet. This helps in completing the print spooler jobs and thereby facilitating in the addition or removal of printers to or from the computer.
This program can be used remotely to remove print spooler items on another computer of the network. Lexmark printer services are sometimes installed on the computer which may hinder the addition of a new printer. This can be solved by turning off the LexBce Server Service. For this click Manage after right clicking My Computer. Then follow Services and Applications > Services > LexBce Server(right click) > Properties> General > Startup type > Disabled > Service Status > Stop > OK. Then start the print spooler service if it is stopped.

No Comments »

A print spooler is an application on Microsoft Windows that helps to mange the link between the computer and the printer. This application manages the printing of the papers, and controls whatever demands the user might have for the hardware device. For instance, one can delete print jobs, or pause them and then restart making necessary changes. The print spooler also helps to change priority of certain print jobs and organize the queuing system.

The print spooler organizes by creating a temporary file in the systemroot folder. Once the job has been done the file is then deleted. One of the many events that can cause a print spooler problem is the unavailability of disk space. High quality print jobs if done need large spaces for the printing of high resolution graphics. Easily the workstation configuration can be overtaken by the heavy print jobs.

Print spooler operations create two different files for a single print job. One is the actual file and the other a shadow file. In general, with the crash of a computer, the two files remain in the spool file until the computer or the application is restarted. But there may be times when, due to a problem in the drivers for the printer the files may get accidentally deleted. This might lead to the print job getting aborted. If the spooled files become corrupted they are singled out in the spool folder and that takes up quite an amount of space.

Print spooler can also be termed as the scheduler for print jobs. All the timings and the queuing up of the papers for the print and also maintenance for the order of the print jobs is done by the print spooler. Sometimes due to a large number of print jobs on different printers on a network, the load can become unbearable. Then the print spooler service can stop without any prior notice. The screen might go completely blank and the system restarts or the print spooler service just stops without any warning.

Print spooler problems on a large network of printers might be the result of different types of printers. For example there might be inkjet, DeskJet and dot matrix printers printing together on a network. Since various printers have different necessities, that might turn out to be a hindrance in each other’s way. This can certainly cause a print spooler problem.

Through research, it has been noticed that the print spooler problem is also related with the Internet. After the addition of an internet connection sharing scheme to a network, a problem could occur as the connection sharing uses a class C subnet with a particular address range. This will lead to printing not being done.

Lastly if the printer driver is not compatible with the computer operating system or some problem arose due to improper installation then the print spooler will not perform and nothing would be visible in the Printers and Faxes folder. One should always remember that no printers can be added or removed while any print jobs or the print spooler is in progress.

No Comments »

The problem of the Bad Pool Caller - which occurs during the upgrading of the Microsoft operating system from Windows 2000 to Windows XP - causes the installation process to stop by the display of an error message on the blue screen. This blue screen has been spoken of many times and you’re probably aware of it by now. It’s called the blue screen of death for good reason! If you’re seeing it, something serious has happened to Windows.

In the event of the Bad Pool Cooler error, expect to see a message that reads along the lines of this:

“A problem has been detected and Windows has been shut down to prevent damage to your computer”.

The BAD_POOL_CALLER problem which is displayed as “stop: 0×000000c2” and other similar varieties essentially happens because of certain issues in managing the memory of the computer.

Now if the error message conveying the problem displays the same set of alphanumeric code every time the system reboots itself, the problem can actually be tackled without going for professional technical help. To begin with, the user must verify the RAM and the hardware of the computer and reboot the operating system once more with the help of a setup disk or maybe by using a boot setup having a GUI similar to that of BartPE.

Try booting in to Safe mode using F8 at the relevant screen. This will try to load Windows using the absolute most basic of files. If you still can’t access the Operating System, you’re going to need the setup disk.

If you’ve bothered to make copies of the key Windows files on a floppy disk, they’re about to become extremely useful and you can use these to regain entry to the core Windows system by replacing just these. You will need to set your BIOS to give preference to the floppy disk drive when booting the system.
Once you regain access to Windows, this is to be followed by running a memory test using a RunScanner and subsequently selecting one single account. In case all the accounts open up, the problem should lie in the system registry hive which is to be renamed and not deleted. From the available backup, another hive is to be created and harvesting of any replacement hive must be avoided in any case.

Apart from this relatively lengthy and somewhat complicated method, there are a couple of quite gimmick like tricks which sometimes solve this problem. One of them is to have the operating system installed once again. This will of course reset Windows to its factory set state, saving a large amount of trouble. But it comes at the price of all your saved files that will not be recovered in the reinstallation. Think long and hard before agreeing to reinstall Windows – it should be the last resort.

Another such trick is to switch off the computer for an extended period of time and then switch it back on once more. It sounds like a ridiculous solution but there are many unexplainable scenarios where such an action can have a good effect.

Get a Free Online Diagnostic Scan with RegCure PC Optimizer (Download Takes 2 Mins)

No Comments »

The bad pool caller problem is much documented and can occur at any time on a system that is suffering from memory problems or a hardware configuration issue. The error can be either fatal or recoverable. You’re likely to see it when loading up your Windows operating system during the boot process.

A standard bad pool caller error will read as below:

BAD_POOL_CALLER. stop: 0×000000c2 (0×000000043, 0xc2528000, 0×00000000, 0×00000000) ”

You will also be greeted with an ominous message stating:

“A problem has been detected and Windows has been shut down to prevent damage to your computer”.

The blame for this – in most cases - will fall on the hardware that you have installed on your system and the integrity of the memory. Check your RAM for problems, if this is within your knowledge. Has the problem started occurring following the installation of a new hardware device? In that case, you may want to disconnect it completely and remove it from the boot start-up list. Bad references in the Windows registry can completely decimate your Operating System, and these are often caused by hardware installations gone wrong.

Speaking on a technical note, it can be said that this particular bad pool caller problem may arise in a situation where the system has already got a Winnov Videum AVI video capture adapter along with the Videum software of the 2.9.2 version installed in the computer.

The problem is most annoyingly realized during the process of installing the operating system. Typically, an option appears for getting updated setup files and recommending the download of those files. However, clicking on either of the options such as ‘Yes, download the updated setup files’ or ‘Details’ results in the appearance of messages informing that the items are not compatible with the OS Windows XP and these problems must be resolved before attempting to run the setup once more.

Thus, if the user decides to go for the remaining option of ‘No, skip this step and continue installing Windows’ the blue screen appears carrying an error message saying that “STOP 0xC2 BAD_POOL_CALLER”.

Anybody who’s dealt with Windows for any meaningful period of time will be aware of the problems that come with the infamous blue screen of death. You can find yourself locked out of Windows completely, depending on the nature of the pool caller error.

You may have also noticed that the bad pool caller error arises shortly after installing a font on certain versions of Microsoft Windows. Well, in this case, it’s the font that’s causing the problem. Windows will respond stubbornly and thrown the blue screen error if it detects a bad font, although you shouldn’t suffer from repeated bad pool caller errors. And if you do, it’s likely another factor at work.

The system registry hive is another checking point for bad pool callers. If your registry hive fails or becomes corrupted, you can expect to see a whole lot more of the blue screen errors. In most cases, an error of this magnitude will result in being locked out of the computer completely.

Get a Free Online Diagnostic Scan with RegCure PC Optimizer (Download 2 Mins)

No Comments »

Most of us have encountered a runtime error at some point. These errors are the kind which can hamper smooth working of applications on Microsoft Windows. You can tell a runtime error quite easily from the others – and they will nearly always come with a pop-up message informing you that there’s been an error. It is possible to debug from here, but to actually fix a runtime error; we have to look a little further.

There are many events which can cause runtime errors. The most popular of these are shown in the list below.

Conflicts with other running programs.
Software issue.
Computer virus.
Memory issue.
Conflicts with other running program.

When more than one application is running on a computer simultaneously, conflicts between applications can occur which lead on subsequently to what is known as deadlock state.

Deadlock state is a serious problem in Windows operating systems in which our application gets locked thanks to a resource which is required by another application. The program may be calling on shared resources that are unavailable at the time. To solve this, you should restart the deadlocked applications – saving any changes before doing so as a matter of priority.

Some software issues can also create run time errors, for example bugs which are mistakenly looked over by designers or developer at the time of the application’s creation. Applications will be working smoothly one minute, and then shutting down completely with runtime errors the next. If the runtime error is triggered by a fault in the application, you should check the relevant website for patch releases and fixes. Most software companies will freely distribute fixes to bugs that customers have found.

Some computer viruses also come through malware, spyware and adware. These can tamper with the usual working routine of an application and lead to runtime errors, particularly in cases as mentioned where resources are required by two applications at a given time. Run a simple spyware removal utility and be sure to keep your computer protected from malicious programs. This will usually wipe out those unwanted runtime popups.

Memory is also an important consideration for the origin of runtime errors. Some computers have less memory which makes it not sufficient for an application to run on properly. The failure to deal with memory allocation can trigger all kinds of problems, and you’re likely to notice that your computer is behaving particularly slow and clunky along the way. Runtime errors may appear randomly and at unexpected intervals.

For fixing such errors one should upgrade memory of computer, and ensure that it’s capable of handling the required application. You should increase the amount of RAM to improve your system’s performance – but also be sure to check on the installation requirements of a product before purchase. This will tell you whether there’s enough memory on your system. If you make the mistake of running an application on a low memory machine, you will likely get runtime errors. There is no way of getting around this, you can either upgrade or stop running the program.

No Comments »

If you’re running on Microsoft Windows, it’s pretty much guaranteed that at some time or another, you’ve encountered a runtime error. These can appear for a variety of reasons – we’re going to look at the most common – but it’s important to remember that runtime errors are not restricted to any one application or program. Not all of them are critical, but they’re certainly unwanted.

That is, of course, unless you’re an application developer who can use the debugging information to fix a problem! Run time errors, as you’ve probably seen, appear in the form of a pop up dialogue box. You will have the chance to run a debug script and most run time errors come with the option to report them to Microsoft or elsewhere.

So what causes them? Arguably the most common reason for a runtime error is a clash of system resources. If Program A wants access to a library of files that are being used by Program B – and the two programs can’t work out their differences in the usual manner – a runtime error can be expected along with a downturn in performance for whichever program is being denied the resources.

You’ve probably noticed that the standard Windows system very rarely gets errors when it’s just been setup after bringing it home for the first time. This is because the system components are nicely organized and the Windows registry is in its default state. The moment you take it upon yourself to start installing new third party applications and hardware devices, you open the door to the possibility of runtime errors and files being misused. It’s pretty unavoidable, but there are things we can do to prevent runtime errors becoming too much of an issue.

If a program is uninstalled, make sure that you remove all of the components related to the program. Having spare parts floating on your computer is like issuing an open invitation to the runtime error prompt.

Another key reason for runtime errors is the presence of viruses on a system. We’ve all heard why viruses are terrible things – and yes, they are – but we don’t always have much of a visual representation of what they’re up to. Well, if you see runtime errors popping up left, right and centre, it may just be a sign that you have a virus at work on your computer.

Viruses are rough cut scripts and generally nasty pieces of work. They will cause programs to operate in ways that perhaps were not intended. This, of course, can lead to collisions on your Windows operating system and files becoming corrupt.

If you think that your computer is safe from malicious third party threats and you’re still getting runtime errors, take a good look at the program you’re trying to work with at the time of the error. Is it newly installed?

Not every application is developed to faultless standards and sometimes, a runtime error can simply be the result of bad programming code.

If all else fails, it may be a question of your computer being a little too old and a little too weak to handle the demands that you’re asking of it. Do you have enough memory? Is there plenty of RAM? A lack of memory will lead to poor performance and yes, you guessed it – runtime errors.

No Comments »

Now if you have ever fallen victim to this error type, you’ll certainly know what I’m talking about but for those who have no idea what this error is all about, well, its better to be prepared than not at all. Error 1706 is something that you may come across when you’re installing any application using the Microsoft Office CD which you might do either for repairing the existing application or install a new one itself. Basically, even when you are installing anything using the Windows Installer, you can encounter such an error type.

However, the error 1706 does have varying messages sometimes like “Error 1706: No valid source could be found for the product.” or “Error 1706: Setup cannot find the required files.” In addition to this error message, the message may also recommend the user by providing him with a path “C:\Program Files\Microsoft Office\Office10\1033\Setup.hlp.” So what exactly could be the reason for such an error message now? Well, there are many reasons for that like sometimes the windows installer is not able to locate the source files that the setup process needs for the installation process. Another cause could be due to the fact that you might have installed the setup file through the network administration and you may not find the file again because the network admin platform must have changed.

In order to counter this error, it is important that have the latest version of InstallShield in your computer. In addition, you also have to make sure that you are logged in as an administrator. If still you are unable to locate the files, you can simply search the name of the file in the windows search option and provide the path for the installation process. The last thing that you can do in this respect is use a registry cleaner in order to repair and take care of that error. Frequent registry scans will help you stay safe from this error thereby ensuring the safety of your computer.

No Comments »