daily dose of windows registry: error 3


Stop 0x00000024 or NTFS_FILE_SYSTEM

The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.

Possible Resolutions:

• Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or drivers can also adversely affect the system's ability to read and write to disk, causing errors. If using SCSI hard disks, check for cabling and termination problems between the SCSI controller and the disks. Periodically check Event Viewer for error messages related to SCSI or FASTFAT in the System log or Autochk in the Application log.

• Verify that the tools you use to continually monitor your system, such as virus scanners, backup programs, or disk defragmenters are compatible with Windows. Some disks and adapters come packaged with diagnostic software that you can use to run hardware tests.
To test hard disk or volume integrity

Method 1:

1. In the Run dialog box, in the Open box type:
cmd

2. Start the Chkdsk tool, which detects and attempts to resolve file system structural corruption. At the command prompt type:
chkdsk drive: /f

Method 2:

1. Double-click My Computer, and then select the hard disk you want to check.
2. On the File menu, click Properties.
3. Click the Tools tab.
4. In the Error-checking box, click Check Now.
5. In Check disk options, select the Scan for and attempt recovery of bad sectors check box. You can also select the Automatically fix file system errors check box.

If the volume you are checking is in use, a message asks whether you want to delay disk error checking until the next time you restart your computer. After you restart, disk error checking runs and the volume chosen is not available to run other tasks during this process. If you cannot restart the computer due to the error, use safe mode or Recovery Console.

If you are not using the NTFS file system, and the system partition is formatted with the file allocation table (FAT16 or FAT32) file system, long file name (LFN) information can be lost if hard disk tools are started from an MS-DOS command prompt. A command prompt appears when using a startup floppy disk or when using the command prompt startup option on multiple boot systems that use FAT16 or FAT32 partitions with Microsoft® Windows® 95 OEM Service Release 2 (OSR2), Microsoft® Windows® 98, or Microsoft® Windows® Millennium Edition (Me) installed. Do not use tools meant for other operating systems on Windows XP partitions!

• Nonpaged pool memory might be depleted, which can cause the system to stop. You can resolve this situation by adding more RAM, which increases the quantity of nonpaged pool memory available to the kernel.

Daily dose of windows registry: Error 2

Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED

The Stop 0x1E message indicates that the Windows XP kernel detected an illegal or unknown processor instruction. The problems that cause Stop 0x1E messages share similarities with those that generate Stop 0xA errors in that they can be due to invalid memory and access violations. This default Windows XP error handler typically intercepts these problems if error-handling routines are not present in the code itself.

Possible Resolutions:

• Stop 0x1E messages typically occur after installing faulty drivers or system services, or they can indicate hardware problems, such as memory and IRQ conflicts. If a Stop message lists a driver by name, disable, remove, or roll it back to correct the problem. If disabling or removing applications and drivers resolves the issue, contact the hardware manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.

• If the Stop message mentions the file Win32k.sys, the source of the error might be a third-party "remote control" program. If such software is installed, you might be able to disable it by starting the system in safe mode. If not, use Recovery Console to manually delete the system service file that is causing the problem.

• Problems can result from system firmware incompatibilities. Many Advanced Configuration and Power Interface (ACPI) issues can be resolved by updating to the latest firmware.

• Other possible causes include insufficient disk space while installing applications or performing certain functions that require more memory. You can free up space by deleting unneeded files. Use Disk Cleanup to increase available disk space. From Recovery Console, remove temporary files (those with .tmp file extensions), Internet cache files, application backup files, and .tmp files generated by Chkdsk.exe or Autochk.exe. You can also choose to install additional applications to another hard disk with more free space or move data files, paging files, and so on.

• The problem might be due to a memory leak caused by an application or service that is not releasing memory correctly. Poolmon (Poolmon.exe) helps you to isolate the components that are causing kernel memory leaks. For more information about troubleshooting memory leaks, see Microsoft Knowledge base articles Q177415, "How to Use Poolmon to Troubleshoot Kernel Mode Memory Leaks," and Q298102, "Finding Pool Tags Used by Third Party Files Without Using the Debugger."

Beginners Guides: Crash Recovery - Dealing with the Blue Screen Of Death

If you've ever used Windows, chances are you've experienced the lovely shade of blue associated with the famous Windows Stop Error or 'Blue Screen of Death.' This frequent, although less so in newer operating systems, error occurs whenever Windows senses a software, hardware or driver error which will not allow it to continue operating properly. In other words, it happens all the time, for all sorts of reasons.
Often, if you're lucky, the problem will resolve itself with a simple reboot and you may never have to worry about it again. More typically though, the BSOD is a harbinger of trouble and you may find yourself faced with another and another until you throw up your hands... but all is not lost.
In this article PCstats.com will walk you through the BSOD in many of its most familiar incarnations. We will not be exploring and cataloguing what each BSOD means, but rather providing a set of tools for troubleshooting that you can use to get around any Blue Screen Of Death, or constant crash issue. Just another step in PCstats' never-ending quest to save your hard earned cash from going to the computer repair shop

.

What is a Blue Screen of Death?
The Blue Screen of Death, or more properly the 'Windows stop message' occurs when Windows detects a problem or error from which it cannot recover. The operating system halts and diagnostic information is displayed on a blue screen. In newer versions of the operating system, the contents of the PC's memory are dumped to a file for later analysis.

All Windows XP stop errors are numbered according to the circumstances that caused the error, which assists enormously in troubleshooting them. Let's take a moment to look at a BSOD in its natural environment, careful now, we don't want to startle it... Note the eye catching shade of blue intended to warn us of trouble, the detailed list of hexadecimal numbers, and relatively unhelpful 'tip.' This is the BSOD in all its glory, so be very afraid if you ever come face to face with this hideous creature!

 

daily dose of windows registry errors

Error Message:

IRQL_NOT_LESS_OR_EQUAL 


Explanation:
This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access. The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has an incorrect value in it, the program tries to access memory that it should not. When this occurs in a user-mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message. If you encounter this error while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

User Action:
This error usually occurs after the installation of a buggy device driver, system service, or BIOS. To resolve it quickly, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time. If you encounter this error while upgrading from Windows NT 4.0 or earlier, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners prior to upgrading. Contact the software manufacturers to obtain updates of these tools. For additional error messages that might help pinpoint the device or driver that is causing the error, check the System Log in Event Viewer. Disabling memory caching of the BIOS might also resolve this error. You should also run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owners manual for your computer. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows 2000 drivers. Disable sync negotiation in the SCSI BIOS, check the cables and the SCSI IDs of each device, and confirm proper termination. For enhanced integrated device electronics (EIDE) devices, define the onboard EIDE port as Primary only. Also, check each EIDE device for the proper master/slave/stand-alone setting. Remove all EIDE devices except for hard disks. If the message appears during an installation of Windows 2000, make sure that the computer and all installed peripherals are listed on the Microsoft Windows 2000 Hardware Compatibility List (HCL) on http://www.microsoft.com. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support.

Airtel 3G Data Card

Before launching the 3G services , Airtel has launched the new USB 3G data card . The new Airtel 3G Data Card will be currently used for wireless Internet access over Airtel 2G/2.75G GSM services across India.Once Airtel launch their 3G services , the same data card can be used to access the 3G network.
The new Airtel 3G data card is Plug and Play device .It supports EDGE/GPRS and UMTS/HSDPA up to 3.6 Mbps speed and is compatible with Windows / MAC .

Airtel 3G Data Card Prepaid Plan
One  month validity Plans – Rs.349 will get 500MB data transfer,Rs.599 will get  1GB,and Rs.899 will get  2GB .

Airtel 3G Data Card Price

Airtel 3G Data Card is available at price of Rs.3799 for postpaid and prepaid users in India.

* 3.5-inch capacitive Touchscreen HD display with Multi-Touch and Gestures support * 1st phone WITH Symbian^3 OS * 12 Megapixel Camera * HD Ready (720p) Vido Recording at 30 FPS * HDMI Output, Video on Demand Through OVI Store * 3G HSDPA * GPS with AGPS support * Anodized aluminium casing, available in Color o Silver white o Dark grey o Orange o Blue o Green

Nokia N8 specifications :

• Network: WCDMA 850/900/1700/1900/2100 and GSM/EDGE 850/900/1800/1900
• OS: Symbian^3
• Form Factor: Touch screen monoblock
• Dimensions: 113.5 x 59.12 x 12.9 mm (L x W x H)
• Weight: 135g
• Display and user interface
  • Screen size: 3.5-inch
  • Resolution: 16:9 nHD (640 x 360 pixels) AMOLED
  • 16.7 million colours
  • Capacitive touch screen
  • Orientation sensor (Accelerometer)
  • Compass (Magnetometer)
  • Proximity sensor
  • Ambient light detector
• Battery: 1200mAh BL-4D
  • Talk-time : up to 12 hours
  • Standby time : up to 390 hours
• Media Storage/Memory:
  • Internal memory: 16 GB
  • MicroSD memory card slot, hot swappable, up to 32 GB
• Video Playback:
  • Video recording, Performance: encoding
  • 25fps, decoding 30fps, File Formats:
  • H.264, MPEG-4, VC-1, H.263, Real Video
  • 10, ON2 VP6, Flash video
• Music Playback:
  • FM radio, FM transmitter, MP3 player,
  • Supported codecs:MP3,AAC,eAAC,
  • eAAC+,WMA,AMR-WB, DRM support, DRM:
  • OMA DRM 2.0
• Main Camera:
  • Lens: Carl Zeiss optics
  • Image capture: 12 megapixels
  • Video capture: HD 720p
  • Aperture: F2.8
  • Focal length: 5.4
  • Flash: Xenon flash
• Connectivity:
  • Nokia Adapter Cable for HDMI CA-156
  • WLAN IEEE802.11 b/g/n
  • Bluetooth 2.1 with support for stereo headsets
  • Positioning with GPS, A-GPS, WLAN and Cell-ID
  • Micro-USB 2.0 high speed for file transfers and charging
  • USB On-the-Go
  • Nokia AV connector 3.5 mm for audio
  • input/output and TV out