TechSpot

Bsod computer keeps restarting

By Kraze
Mar 17, 2008
Topic Status:
Not open for further replies.
  1. im getting this error message:

    0x000000c2 (0x00000007, 0x00000cd4, 0x02130001, 0x89280a18)

    this is what i found in the minidump log


    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Mon Mar 17 21:56:00.281 2008 (GMT-5)
    System Uptime: 0 days 0:32:05.041
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    .........................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ............................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck C2, {7, cd4, 2130001, 89280a18}

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

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!PVOID ***
    *** ***
    *************************************************************************
    unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_POOL_HEADER ***
    *** ***
    *************************************************************************
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
    *** ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : ntoskrnl.exe ( nt+22deb )

    Followup: MachineOwner
    ---------
  2. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

    Suugestion
    1. Run memtest (7 Passes)
    2. Reseat the ram
    3. Confirm your Antivirus and firewall up to date (program wise)
    4. Update all drivers from your computer's manufacture

    The invalid entries are not relevant.
    And also please attach (using the paperclip icon) in any new message (any other minidumps)
    But preferably do the above first
  3. raybay

    raybay TS Evangelist Posts: 10,716   +6

    This problem usually indicates a fairly common bug check error.
    The specific cause is most often a driver error, a video graphics hardware error, or a memory module failure. Nevertheless, these errors are very difficult to track down with certainty.
    It is handy to first download the latest video drivers, and the previous video drivers and store them some place that you can later find them. Then disable the current drivers in the Device Manager, and
    Install the newer driver, then reboot. You may also need to step back to the next most recent driver.
    Some of these errors will result from driver downloads in concert with a Windows or Microsoft update.
    You may be able to trouble shoot this problem with a number of standard basic fixes. First, be sure you have enough hard disk space… At an absolute minimum, you should have at least 17% free space… 25% or more is preferred.
    When you can tell that a driver has been posted in the bug check report, be sure you have the new and most recent drivers downloaded and available where you can find them. Then disable the currently installed driver in the device manager… understanding that it is difficult to figger out the driver or function that caused the problem.
    One useful troubleshoot is to temporarily change out video adapters, along with their relevant drivers.
    Another is to disable caching and shadowing in your BIOS memory.
    You could have a hardware incompatibility that was enlarged by a Windows or Microsoft download or updated. Make certain that the hardware you have installed is on the Microsoft Windows Hardware Compatibility List (HCL).
    Often a faulty device driver or system service can be what is causing this error… which results in hardware errors such as IRQ or BIOS conflicts, memory errors and other hard-to-detect problems.,
    Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
    When you have a driver listed by name in the bug check, you must disable or remove that driver, and download a new one from the current or previous list… and of course suspect any recent driver downloads or recent Microsoft Updates. Disable or remove anything you have recently added.
    SAFE MODE. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you should attempt to use SAFE MODE to rename or delete the driver. You may also have to restart your computer from a cold boot by using the Recovery Console to get access to the file.
    Be aware that the cause of this error could be a third-party remote control program, if you use such a thing. If such software is installed, this service, too, can be removed by starting the system using the Recovery Console… then deleting the offending system service file.
    You should check your system log in the Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. As mentioned above, disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, such as the free download of MemTest86 or the especially the memory scanner, supplied by the system manufacturer. Look for these details on the motherboard owners manual.
    The errors that generates these messages may appear after the first restart Windows Setup, or after Setup is finished. One possible cause of the error, as mentioned above, is a lack of disk space for installation. It can also be system BIOS incompatibilities. For lack of disk space, reduce the number of files on the target hard disk. Check for and delete any unneeded temporary files, Internet cache files, application backup files, and .chk files containing saved file fragments from disk scans. You should actually use another hard disk with more free space for the installation, since hard drives are so inexpensive nowadays.
    Many forget that BIOS problems can cause this bug check error, but can be resolved by upgrading the system BIOS version... Be careful, however, as BIOS updates are still risky on some motherboards.
  4. kimsland

    kimsland Ex-TechSpotter Posts: 18,353

    Say what !

    I had to read all that!
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.