All questions for PC/Laptop automatically restarting goes here.

First step on PC restart/restart loop diagnostics is to turn off auto restart when an error occurs.

right click My Computer | Properties | Advanced | Startup and Recovery | Settings | untick Automatically Restart



for BSOD errors please go here for self-diagnostic or post up your minidump files here. If it's not BSOD errors go here.

I run the debugger and found the culprit in the line probably caused by:. I don't know what that file is. what should I do?

Scour the internet to find out. your friend to find out what those errors in mean is:
1. http://support.microsoft.com/search/?adv=1
2. http://www.google.com
3. zip the minidump files and upload it to this thread.

Additional Reading

• Demystifying the 'Blue Screen of Death' from Microsoft Technet
• Windows Debuggers: Part 1: A WinDbg Tutorial from The Code Project
• Generate a memory dump file by using the keyboard
• Overview of memory dump file options
• Windows does not save memory dump file after a crash

This post has been edited by synz: Sep 26 2007, 10:17 PM

Troubleshooting Windows XP install BSODs

Constant Blue screen errors while attempting to install Windows XP are generally caused by hardware or media problems. The most common hardware-related installation issue is faulty memory chips, which can cause havoc to any XP installation. Overheating or a dying or defective hard disk are other common causes. A severely scratched or otherwise faulty XP install CD may also cause stop errors.

First, check your CD and clean or replace it as necessary. Your next step should be to test your system memory for errors with a diagnostic program.

To do this obtain the Windows Memory Diagnostic, Memtest86, or Memtest86+ memory diagnostic programs on floppy or CD we mentioned earlier, and use it to boot your system and test the memory. If either of these programs shows any errors in your memory, you have likely found the source of your troubles.

Chances are you will need to purchase new memory. For more information on faulty memory and memory diagnostics, see PCstats Guide to diagnosing bad memory .

Now it's time to test the hard drive for errors. Visit the website of your hard drive's manufacturer and download their drive diagnostic utility software. Every major hard drive company makes a utility like this freely available. An example is Maxtor's PowerMax software available here . Follow the included instructions to install the software and test your drive(s) for errors.

If no errors were found in memory or with the hard disk, you need to ensure that your processor is not overheating. Make sure the fan on the heatsink is in working order and reboot the computer, pressing DEL repeatedly on startup to go into the BIOS setup screen.

Let your PC run on this screen for an hour or so, checking back to make sure it has not crashed. If a PC crashes on the BIOS screen, it generally means the processor is overheating for one reason or another.

As a final measure, you can remove all unnecessary hardware from your system before attempting to install Windows XP again. Power off the computer, remove the case and remove all hardware except:

Mouse & keyboard
Hard drive
CD-Drive
Video card
Memory
(And obviously the processor and power supply must still be connected also)

Attempt to install XP again. If it works correctly, you can troubleshoot the remaining devices from within Windows.

===================================================


Basic troubleshooting for all BSOD errors

First off, note down all relevant information when you see a BSOD flash across the screen. This includes the error number and friendly name from the 'bugcheck' section of the stop error (see above), and any file names specified in the 'driver information' section.
If the BSOD comes up on the screen for a split-second before the PC restarts and wipes all the useful information away, we need to change some settings within WinXP. In most cases, it should be possible to stop your PC from automatically restarting when it develops a major error, allowing you enough time to jot down the BSOD error message. If you are using WindowsXP, right click on my computer > Properties > Select the 'Advanced' tab > and under 'startup and recovery' click the 'settings' button. This will open a new window, and under the 'System Failure' heading, uncheck 'Automatically restart.'

Continuing on, attempt to restart the computer normally into Windows. If the BSOD occurred while booting Windows, you may be taken to a troubleshooting menu and will have to select 'attempt to start Windows normally.' If your computer starts correctly, continue using it and store the error information for later reference. If the BSOD reoccurs at random or irregular periods, see Section D below on troubleshooting intermittent stop errors.

If your system does not start correctly or the stop message happens again, reboot the system. When the POST (memory checking) screen comes up, press F8 repeatedly. This will bring you to the Windows advanced options menu.

In the Windows advanced options menu choose 'safe mode' to attempt to boot into Windows Safe mode. Safe mode loads Windows XP with a minimal set of drivers and no automatically loaded software. If faulty software or drivers are causing your BSOD problem, safe mode should load correctly. If safe mode loads correctly, refer to Section A below on 'troubleshooting software stop messages.'

If safe mode does not load correctly, and/or you get the same stop message upon attempting safe mode, it's time to try the 'restore last known good configuration' option in the advanced options menu.

Restart your computer, pressing 'F8' again to load the advanced options menu and select 'last known good configuration (your most recent settings that worked).' This uses Windows XP's built in system restore utility to restore the most recent save point, which should be the last time you installed any drivers or other software. If your system boots normally after this operation, hopefully your problem has been fixed.

If you are still receiving a Blue Screen Of Death after the above procedures, or if system restore was disabled on your system, note down any new information on the error and start thinking. Did you install any new hardware or software just before this problem occurred? The driver information section of the BSOD may help with this.

If you did install new hardware or software, and you think you know what it might be that is causing the problem, this gives you a big boost in resolving the situation.

Otherwise, proceed to the advanced troubleshooting sections below. Chances are your error is hardware or system file based and will require more effort to repair.

===================================================
For more information please click here

This post has been edited by synz: May 29 2007, 08:16 PM

Common BSODs in Windows XP

Now that you have a good idea of how to dissect a BSOD and pull out the relevant pieces of information from all the gibberish on the screen, let's look at some of the more common BSODs in Windows XP. I'll only cover just a few of the BSOD conditions, but there are lots of possible Stop errors. For each BSOD I discuss, I'll provide a link to an article on the Microsoft Knowledge Base that covers that particular Stop error. (Since more than one article might address a Stop error, you may want to search the Knowledge Base if you discover that you need more information.)

[b]STOP: 0x0000000A
IRQL_NOT_LESS_OR_EQUAL
This Stop error, which can be caused by either software or hardware, indicates that a kernel-mode process or driver attempted to access a memory location it did not have permission to access or a memory location that exists at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access other only processes that have an IRQL that's equal to or lower than its own.
Troubleshooting a Stop 0x0000000A error in Windows XP

STOP: 0x0000001E
KMODE_EXCEPTION_NOT_HANDLED
This Stop error indicates that indicates that the Windows XP kernel detected an illegal or unknown processor instruction. The problems that cause this Stop error can be either software or hardware related and result from invalid memory and access violations, which are intercepted by Windows' default error handler if error-handling routines are not present in the code itself.
Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors

STOP: 0x00000050
PAGE_FAULT_IN_NONPAGED_AREA
This Stop error indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop error.
Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors

STOP: 0x0000007B
INACCESSIBLE_BOOT_DEVICE
This Stop error indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes this Stop error. This error could also indicate a possible virus infection.
Troubleshooting Stop 0x0000007B or "0x4,0,0,0" Error

STOP: 0x0000007F
UNEXPECTED_KERNEL_MODE_TRAP
This Stop error indicates a hardware problem resulting from mismatched memory, defective memory, a malfunctioning CPU, or a fan failure that's causing overheating.
General causes of "STOP 0x0000007F" errors

STOP: 0x0000009F
DRIVER_POWER_STATE_FAILURE
This Stop error indicates that a driver is in an inconsistent or invalid power state. This Stop error typically occurs during events that involve power state transitions, such as shutting down, or moving in or out of standby or hibernate mode.
Troubleshooting a Stop 0x9F Error in Windows XP

STOP: 0x000000D1
DRIVER_IRQL_NOT_LESS_OR_EQUAL
This Stop error indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by faulty or mismatched RAM or a damaged pagefile.
Error Message with RAM Problems or Damaged Virtual Memory Manager

STOP: 0x000000EA
THREAD_STUCK_IN_DEVICE_DRIVER
This Stop error indicates that a device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter or a faulty video driver.
Error message: STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER

STOP: 0x00000024
NTFS_FILE_SYSTEM
This Stop error indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to drives formatted with the NTFS file system. (A similar Stop message, 0x00000023, exists for the file allocation table [FAT16 or FAT32)] file systems.)
Troubleshooting Stop 0x24 or NTFS_FILE_SYSTEM Error Messages

STOP: 0xC0000218
UNKNOWN_HARD_ERROR
This Stop error indicates that a necessary registry hive file could not be loaded. The file may be corrupt or missing. The registry file may have been corrupted due to hard disk corruption or some other hardware problem. A driver may have corrupted the registry data while loading into memory or the memory where the registry is loading may have a parity error.
How to Troubleshoot a Stop 0xC0000218 Error Message

STOP: 0xC0000221
STATUS_IMAGE_CHECKSUM_MISMATCH
This Stop message indicates driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory hardware can also cause this Stop message to appear.
"STOP: C0000221 unknown hard error" or "STOP: C0000221 STATUS_IMAGE_CHECKSUM_MISMATCH" error message occurs

==============================================================

Reference
More info here

Additional BSODs references
http://www.pcsupportsource.com/xp_stop_messages.htm
http://www.5starsupport.com/info/stop_error.htm
http://www.updatexp.com/stop-messages.html
http://www.computerdr.com.au/technical/stopmsgs.htm

I do not know how to troubleshoot! What should I do?
Please post your minidump files with .ZIP and attach it here.
Minidump files are located in C:\Windows\Minidump
You can go Start > Run > type %systemroot%\minidump > Hit enter

This post has been edited by synz: Sep 26 2007, 09:22 PM

Microsoft ® Windows Debugger Version 6.3.0017.0
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini093006-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Mon Sep 25 20:27:58 2006
System Uptime: 1 days 1:52:56.173
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
.........................................................................................................................
Loading unloaded module list
......................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {468d0002, 2, 1, 804e27e7}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : ntoskrnl.exe ( nt!KeRevertToUserAffinityThread+12e )

Followup: MachineOwner
---------

kd> .reload
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
.........................................................................................................................
Loading unloaded module list
......................................
Loading User Symbols




hi........
aft i run windg,i get this result
can i know wat the problem n how 2 solve???
already face tis bluescrreen problem 4 quite some time

Please attach your minidump files with .ZIP here.

hey..... that day my windows cant boot up it say the 1 file ntfs.sys is missing .... issit same as STOP: 0x00000024
NTFS_FILE_SYSTEM
This Stop error indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to drives formatted with the NTFS file system. (A similar Stop message, 0x00000023, exists for the file allocation table [FAT16 or FAT32)] file systems.)
Troubleshooting Stop 0x24 or NTFS_FILE_SYSTEM Error Messages

this?
btw after i reinstall it a blue screen of death appear when i first rebooted my pc but that screen just flashes for a sec couldnt see whats that then it will reboot again and the page whereby it asked if i wanted to start windows normally or use the last known working configuration..... this also happen when i first installed windows 2 weeks ago..... whats wrong?

^
possible causes for ntfs.sys corruption are a corrupted file ntfs.sys file. (which we can rule out with a fresh installation of Windows from a clean Windows CD and newly partitioned drive) or hardware problems. possible hardware problems include incompatible or failing memory (ie. bad RAMs - very likely), failing hard drive (likely) or failing CD-ROM/damage CD media (not as likely).

on a more specific chance, it could corruption caused by a bad IDE cable or if you are using a RAID / SATA / SCSI setup, the third party drivers you are providing (or not providing for that matter) may not be fully compatible with Windows or damaged. try getting the latest drivers from the manufacturer.


"Missing or corrupt Ntfs.sys" error message when you restart Windows XP after you convert your hard disk to the NTFS file system
http://support.microsoft.com/kb/822800

"Windows could not start because the following file is missing: \system32\drivers\ntfs.sys" error message in Windows XP Service Pack 2
http://support.microsoft.com/kb/887675/en-us

more KB articles
http://support.microsoft.com/search/defaul...=0&y=0&srch=sup

@Darren
are you using another version of winOS to check another version of WinOS dump file? eg. winxp analyzing win2k minidump.

futher places to look for error is in your event log viewer. Right-click My Computer | Manage | expand Event Viewer | check Application, System



This post has been edited by AsenDURE: Oct 9 2006, 11:06 AM

clean cd? newly burn 1 can?
btw after that problem occur i cant even do formating on my harddisk

my pc also having the same problem, it keep on restarting after certain amount of time.. i check with the event viewer n there is so many error, i dunno what is happen..

@rissband

Obviously it was caused by Application Error. If you can attach your minidump files with .ZIP files here would be easier for us to rectify your problem.

Just a question..if error does occurs and since we have unticked the automatic restart button.. then wat will happen?

the pc will display error msg but still can use or what else?

BSoD screen will appear.. that's all.. if the automatic restart has checked then it will restart immediately after half or 1 second when BSoD appear.

What is wrong?

http://www.google.com/search?client=opera&...=utf-8&oe=utf-8

next time crop your image. my eyesight is not as good as it used to be...
you can also double click on the error to see the properties page.


hardware error. looks like the CPU (or RAM?).

bugcheck 9c is a machine check error.

http://support.microsoft.com/?kbid=329284&sd=RMVP

try isolating ...
http://forum.lowyat.net/index.php?showtopic=347156
...and doing stress/heat test.

This post has been edited by AsenDURE: Oct 11 2006, 11:02 AM

here goes my minidump.zip..

Attached File(s)
 Minidump.zip ( 24.23k ) Number of downloads: 104

@rissband



winarp.sys is Routing and Remote Access core service in windows.
http://www.file.net/process/wanarp.sys.html

you can see alot of tcp/ip and winarp problem. you get this BSOD when you try to connect to internet?

try updating your network/modem drivers.