Shutting down pc with a problem of debugger

Syntax errors are the most common problem for developers. A single syntax error can cripple even the best applications and websites. You can correct syntax errors easily once you find them. Typical errors include missing commas, semicolons and parenthesis. Debuggers are available in many software development kits to aid you in the location of syntax errors. However, you can find and correct syntax errors manually as well. Learning how to correct syntax errors is an essential part of being a software developer.

Locate the syntax error manually. Step through each section of your code. Most code will be sectioned off into groups or functions. Carefully proof your code. Be sure to pay close attention to how lines are grouped. A common syntax mistake is incorrect grouping.

For instance, if you have an If Else statement embedded in another If Else statement, be sure the embedded statement is surrounded by a separate set of parenthesis or brackets, depending on your language. Double-check notes sections. Notes are only for the developer to see. However, if the syntax isn't correct, the notes may become part of your application, which may not agree with existing code. Ensure the syntax around your notes is correct. Run a debugger if possible. This will make locating errors much easier. A debugger will be found under a menu such as Debug, Run or Tools or as part of your SDK's toolbar. Allow the debugger to run. Errors will be listed at the bottom or right side of your screen. Many debuggers will highlight possible errors in your code as well. A line number, along with the possible error, will be listed in the error message. Locate your syntax error if the debugger isn't correct. Sometimes a debugger will show you where your application stopped working correctly. The syntax error itself may be above or below the line listed in the debugger message. Check all syntax within the surrounding area, especially within the line's function. Run your application after correcting the syntax error. Check every possible function of your application to ensure it works correctly. If you find a problem, double-check the syntax in your code that surrounds the problem area. For instance, if your application has a log-in screen that isn't accepting passwords correctly, check the code for the log-in screen. Remove Syntax Error syntax error typically occurs when the Web page you are loading causes a script error in the browser. This is caused by incorrect code that displays an error message or results in a Web page that does not load correctly. You can remove a syntax error by making a change to the settings of your Web browser. Common Web browsers that can experience this type of error include Internet Explorer, Mozilla Firefox and Safari.
Double-click the "Internet Explorer" icon to open the program. Click the "Tools" drop-down menu and select "Internet Options." This will display the Internet Options window. Go to the "Advanced" tab and scroll down to the "Browsing" section. Remove the check from the box for "Disable script debugging (Internet Explorer)," "Disable script debugging (Other)" and "Display a notification about every script error." Click the "Apply" button to save the changes. Click the "OK" button to close the Internet Options window. Close and restart the Internet Explorer browser for the changes you made to take effect. b> Mozilla Firefox b> Double-click the "Mozilla Firefox" icon to open the program. Type "about:config" into the address bar and press the "Enter" key. Type "dom.max_script_run_time" into the Filter text box and press the "Enter" key. Double-click "dom.max_script_run_time" to display the Enter Integer Value dialog box. Enter a value of "10" or "15" into the text box and click the "OK" button to save the change. Close and then restart the Firefox browser for the change to take effect. b> Safari b> Click the "Safari" icon to open the Web browser. Select the option for "Preferences" from the menu bar. Go to the Advanced tab and click the option for "Show Develop menu in menu bar." Click the option for "Develop" from the menu bar. Click the option for "Disable Runaway JavaScript Timer." Close and re-open the browser for the change to take effect.

b>

b>

Sorry my friend but it seems that you catched a huge virus, I don't remember the name of the virus, but is extremely famous, sorry nothing else to do than reinstall windows.

Try uninstalling a few unnecessary programs
The first cause can be fixed rather easily. Simply run fewer programs or buy additional RAM click start right click on my computer select properties you will see all imformation about your computer including installed ram

or processor upgrades. Your computer is running past its specified limits. But remember that in this case the blue screen of death should happen extremely infrequently. If you see the physical memory dump blue screen much more often then the issue is clearly...!..
click start right click on my computer,properties advanced scroll down to system and recovery open settings write and debugging information the drop down button select none
ideally, it should already be the default debugger for your system.
The Dr. Watson debugger program logs all information related to failed processes to the Drwtsn32.log file. In addition to this, the debugger program can be configured to create memory dump files related to the failed processes. You can refer these dump files to analyze the reason behind a process failure.
Perform the following steps to configure Dr. Watson as the default debugger program to record user-mode program errors:

1. Open Start menu, select Run, type Drwtsn32.exe -I and then press Enter. This command sets Dr. Watson as the default debugger.
2. Next, run the Drwtsn32.exe command.
3. In the Dr. Watson for Windows dialog box, select the following check boxes:
• Append to Existing Log File
• Visual Notification
• Create Crash Dump File
4. Now, when your computer restarts after the STOP 0xC000021A error is generated, run the Dr. Watson command.
5. Here, view the paths to the Dr. Watson and User.dmp logs.
6. Open Windows Explorer, navigate to the log files and then open them.
7. Here, check the cause behind the STOP 0xC000021A error.

also you might download and use this registry cleaner it is totally free to use
http://download.cnet.com/ccleaner/

another one of the possibile reaons is

a bad lead can cause a computer to continue on a cycle or to shutdown or fail to detect your hard drive

Test all leads that attach to your hard drive including electrical extensions,IDE,SATA

the leads from your ((motherboard to your hard drive)) make sure they have a secure connection and are not faulty or just replace them there probably old and faulty
make sure all leads that are attached to your drives dvd\cd 3 1/2 inch floppy have secure connections and are not faulty even the electic extensions or just replace them they are probably faulty a computer needs its connections to finish its cycle and have an end so any faulty leads will end up with a computer error
click start control panel administrive tools,computer management ,disk management right click on your drive select properties click tools you should see click check now click start two boxes automatically fix files and scan for and attempt recovery of bad sectors place then a tick in both boxes then select check now,start should schedule this task when restart
do not do anything while the chkdsk utility is in progress any input will damage your computer
hope this helps

The first cause can be fixed rather easily. Simply run fewer programs or buy additional RAM or processor upgrades. Your computer is running past its specified limits. But remember that in this case the blue screen of death should happen extremely infrequently. If you see the physical memory dump blue screen much more often then the issue is clearly...!..
The first cause can be fixed rather easily. Simply run fewer programs or buy additional RAM or processor upgrades. Your computer is running past its specified limits. But remember that in this case the blue screen of death should happen extremely infrequently. If you see the physical memory dump blue screen much more often then the issue is clearly...!..
click start right click on my computer,properties advanced scroll down to system and recovery open settings write and debugging information the drop down button select none
ideally, it should already be the default debugger for your system.
The Dr. Watson debugger program logs all information related to failed processes to the Drwtsn32.log file. In addition to this, the debugger program can be configured to create memory dump files related to the failed processes. You can refer these dump files to analyze the reason behind a process failure.
Perform the following steps to configure Dr. Watson as the default debugger program to record user-mode program errors:

1. Open Start menu, select Run, type Drwtsn32.exe -I and then press Enter. This command sets Dr. Watson as the default debugger.
2. Next, run the Drwtsn32.exe command.
3. In the Dr. Watson for Windows dialog box, select the following check boxes:
• Append to Existing Log File
• Visual Notification
• Create Crash Dump File
4. Now, when your computer restarts after the STOP 0xC000021A error is generated, run the Dr. Watson command.
5. Here, view the paths to the Dr. Watson and User.dmp logs.
6. Open Windows Explorer, navigate to the log files and then open them.
7. Here, check the cause behind the STOP 0xC000021A error.

also you might download and use this registry cleaner it is totally free to use
http://download.cnet.com/ccleaner/

another one of the possibile reaons is

One bad lead can cause a computer to continue on a cycle or to shutdown or fail to detect your hard drive

Test all leads that attach to your hard drive including electrical extensions,IDE,SATA

the leads from your ((motherboard to your hard drive)) make sure they have a secure connection and are not faulty or just replace them there probably old and faulty
make sure all leads that are attached to your drives dvd\cd 3 1/2 inch floppy have secure connections and are not faulty even the electic extensions or just replace them they are probably faulty a computer needs its connections to have an end so any faulty leads will end up with a computer error
click start control panel administrive tools,computer management ,disk management right click on your drive select properties click tools you should see click check now click start two boxes automatically fix files and scan for and attempt recovery of bad sectors place then a tick in both boxes then select check now,start should schedule this task when restart
do not do anything while the chkdsk utility is in progress any input will damage your computer

hope this helps

The first cause can be fixed rather easily. Simply run fewer programs or buy additional RAM or processor upgrades. Your computer is running past its specified limits. But remember that in this case the blue screen of death should happen extremely infrequently. If you see the physical memory dump blue screen much more often then the issue is clearly...!..
The first cause can be fixed rather easily. Simply run fewer programs or buy additional RAM or processor upgrades. Your computer is running past its specified limits. But remember that in this case the blue screen of death should happen extremely infrequently. If you see the physical memory dump blue screen much more often then the issue is clearly...!..
click start right click on my computer,properties advanced scroll down to system and recovery open settings write and debugging information the drop down button select none
ideally, it should already be the default debugger for your system.
The Dr. Watson debugger program logs all information related to failed processes to the Drwtsn32.log file. In addition to this, the debugger program can be configured to create memory dump files related to the failed processes. You can refer these dump files to analyze the reason behind a process failure.
Perform the following steps to configure Dr. Watson as the default debugger program to record user-mode program errors:

1. Open Start menu, select Run, type Drwtsn32.exe -I and then press Enter. This command sets Dr. Watson as the default debugger.
2. Next, run the Drwtsn32.exe command.
3. In the Dr. Watson for Windows dialog box, select the following check boxes:
• Append to Existing Log File
• Visual Notification
• Create Crash Dump File
4. Now, when your computer restarts after the STOP 0xC000021A error is generated, run the Dr. Watson command.
5. Here, view the paths to the Dr. Watson and User.dmp logs.
6. Open Windows Explorer, navigate to the log files and then open them.
7. Here, check the cause behind the STOP 0xC000021A error.

also you might download and use this registry cleaner it is totally free to use
http://download.cnet.com/ccleaner/
hope this helps
don

this problem only can fix by reinstall your computer operating system (windows)

:) For what purpose you need a debugger when you can not fix your own mess :) ?!?

Which debugger have you installed? It must be a ring 0 i guess if auto loading drivers (SoftIce, Syser or RR0D .. WinDBG will not crash your OS )

Just go SafeMode and remove all autorun entries for the debugger ( drivers included ), use autoruns from M$ Technet ( SysInternals ), or just System Restore to previous point where you were not trying things that are out of your league ;)

A piece of advice :
For debugging use dedicated machine or virtual one

Hi!

This is what DrWatson is:
http://en.wikipedia.org/wiki/Dr._Watson_(debugger)

And this is how to disable it:
http://support.microsoft.com/kb/188296


Follow the steps fro n the link above and you will be fine

Good Luck
Nic

If you re-formatted, it's probably just a coincidence about I tunes.
I would suspect an overheating problem. Open the side cover and check all the fans for dust, especially yhe CPU fan. You can blow the dust out with a can of compressed air. Try re-seating the RAM while you have the cover off. Good luck!

It could be under warranty have the motherboard checked and or the processor. Something is wrong it shouldnt freeze up like that.