Tip & How-To about Computers & Internet

Blue screen problem

The blue screen problem causes is:

1- bad files in windows (re-install windows )

2- bad data cable ( replac it )

3- bad sector in hard disk ( repair)

4-bbad ram (replace)

5- bad power supply (change)

best regards

Posted by on

Computers & Internet Logo

Related Topics:

Related Questions:

1 Answer

bluescreen problem


the blue screen problem causes is :

bad files in windows (re-install windows )

bad data cable ( replac it )

bad sector in hard disk ( repair)

bad ram (replace)

bad power supply (change)

best regards

if you see that is helpful plz don't forget to vote me




nadereleraki_2.jpg

Apr 01, 2011 | Computers & Internet

1 Answer

PLEASE, I HAVE A DELL D610 LATITUTUDE LAPTOP AND I WAS WORKING WITH BEFORE A BLUE SCREEN APPEARED WITH SOME ERROR MESSAGE, AND NOW THE HARD DISK IS NO LONGER RECOGNIZING, WHEN IT DOES IT ODSN'T ALLOW ME TO FORMAT IT BEFORE IT DISAPPEARS AGAIN, PLEASE HELP ME OUT. I MAKE USE OF WINDOWS XP PROFESSIONAL


Blue screen error may generally appear for three important reasons : 1.If you system is infected with some viruses and your hard drive has bad sectors in it.
2. If your memory card has gone bad or not properly pluged.
3. The OS has gone corupt due to virus attack.....

Resolution: 1. Go ahead and do a complete format on your hard drive and then install the OS, i.e., Win XP.
2.Try replacing your Memory Card in your system.
3. Change your hard drive or conatct Geek Squad @ 1-800-433-5778 for data recovery.

Jul 29, 2010 | Dell Latitude D610 Notebook

1 Answer

Problem: KERNEL_DATA_INPAGE_ERROR Technical information: ***STOP: 0x0000007A (0xC0403638, 0xC0000056, 0x4277F860, 0x806C7913) ***acpi.sys ? Address 806C7913 base at 80692000, DateStamp 49c01a37


The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
Parameters The four parameters that are listed in the message can have three possible meanings. If the first parameter is 1 or 2, or 3 and the third parameter is 0, the parameters have the following definitions.
Parameter Description 1 The lock type that was held (1, 2, or 3) 2 The error status (usually an I/O status code) 3 If Lock Type is 1: the current process

If Lock Type is 2 or 3: 0

4 The virtual address that could not be paged into memory
If the first parameter is 3 (and the third parameter is nonzero) or 4, the parameters have the following definitions.
Parameter Description 1 The lock type that was held (3 or 4) 2 The error status (typically an I/O status code) 3 The address of the InPageSupport structure 4 The faulting address
Otherwise, the parameters have the following definitions.
Parameter Description 1 The address of the page table entry (PTE) 2 The error status (usually an I/O status code) 3 The PTE contents 4 The faulting address

Cause Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following:
  • 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
  • 0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.
  • 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.
  • 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
  • 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.


These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).
Another common cause of this error message is defective hardware or failing RAM.
A virus infection can also cause this bug check.
Resolving the Problem Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.
If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r.
Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.
Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems.
Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer.
Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.
Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error.
Make sure that the latest Windows Service Pack is installed.
If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error.
Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.

Jul 12, 2009 | Microsoft Windows Vista Home Premium with...

3 Answers

CAN'T START UP COMPUTER DETECTS NO MOUSE OR KEYBOARD


The Blue Screen Your Are Talking About Its UNMOUNTABLE BOOT VOLUME and in case of blue screen mouse and keyboard are not detected as WINDOWS are not loading....

There Are 3 Ways To Resolve It But For All 3 Methods We Need The MICROSOFT WINDOWS XP OPERATING SYSTEM DISK...
1st Method Is WINDOWS RE-INSTALLATION. But In This Case All Your Data Would Be Gone..

2nd Method Is WINDOWS PARALLEL RE-INSTALLATION and in this method your data would be saved but you need to install the DRIVER'S SOFTWARE'S and other APPLICATIONS.

3rd Method Is The Easiest And I Prefer Which Is To Repair The Booting Sector.

To repair the volume, follow these steps: (10-15 Minutes)
  1. Start your computer by inserting the Windows startup disks or the MICROSOFT WINDOWS XP OPERATING SYSTEM DISK if your computer can start from the CD drive.
  2. When the Welcome to Setup screen appears, press R to select the repair option.
  3. If you have a dual-boot or multiple-boot computer, select the Windows installation that you want to access from the Recovery Console.
  4. Type the administrator password when you are prompted to do this.

    Note If no administrator password exists, press ENTER.
  5. At the command prompt, on the drive where Windows is installed, type chkdsk /p, and then press ENTER.
  6. It will ask u to overwrite the boot sector so press Y and overwrite the boot sector.
  7. type FIXBOOT and hit enter.
  8. When Everything Is done and new boot sector has been written successfully... type EXIT.
  9. Take Out Windows Disk and Restart Your System..
Some things that you should know before you try this solution loadTOCNode(4, 'resolution');
  • If the file system is damaged, you can use chkdsk /r command to repair the volume. However, if you use the chkdsk /r command, you may lose some data.
  • You will need the Windows startup disks or the Windows installation disk. If you do not have them, contact the computer manufacturer for help in obtaining the disks.
  • You will need the administrator password to complete the steps.
To repair the volume, follow these steps: 40-45 Minutes Complete File Repair
  1. Start your computer by inserting the Windows startup disks or the MICROSOFT WINDOWS XP OPERATING SYSTEM DISK if your computer can start from the CD drive.
  2. When the Welcome to Setup screen appears, press R to select the repair option.
  3. If you have a dual-boot or multiple-boot computer, select the Windows installation that you want to access from the Recovery Console.
  4. Type the administrator password when you are prompted to do this.

    Note If no administrator password exists, press ENTER.
  5. At the command prompt, on the drive where Windows is installed, type chkdsk /r, and then press ENTER.
  6. At the command prompt, type exit, and then press ENTER to restart your computer.
  7. After you repair the volume, check your hardware to isolate the cause of the file system damage.
If this procedure does not work, repeat it, but type fixboot instead of chkdsk /r in step 5.

Rate This Sollution Accordingly.........

May 22, 2009 | Computers & Internet

Not finding what you are looking for?

193 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...