Vista x86 doesn't boot RRS feed

  • Question

  • For a few days, every time I try to boot Vista x86, the booting process seems to start good but when the "progress bar" appears, it remain a bit longer than normal time, and after some seconds blue screen appears and the system reboots.
    Sometimes I get chkdsk of the active partition before the boot but the problems doesn't resolve.
    I also tried booting system in safe mode and with the other possible options such as "Restoring System to Last Configuraton"  but there's no way to solve, same thing trying to restore after booting from Vista DVD.
    Just thing I noticed it's that a pair of time after I got this problem, after many hours my computer was switched off, I started and Vista booted correctly, but this happened just sometimes.

    Tuesday, June 17, 2008 2:16 PM


  • Hi,


    I would like to share the following information with you:



    What is the blue screen stop?


    Generally speaking, this should actually be a blue screen stop issue or stop error issue. Windows 2000 and later (including Windows Vista) uses separated user mode and kernel mode memory space. The blue screen stop errors are always caused by kernel portion components, such as a device drivers, backup software or anti-virus services (buggy services).


    To be more specific, the system goes to a blue screen because there is some exceptions happened in the kernel (a device drivers, backup software or anti-virus services, etc.), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).


    Windows 2000, Windows XP and Windows Vista act similarly when kernel mode crash problem occurs.


    How to troubleshoot the blue screen stop problem?


    To solid troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump and analyze the related source code if needed. Unfortunately, debugging is beyond what we can do in the forum. I'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. To obtain the phone numbers for specific technology request please take a look at the web site listed below:




    If you are outside the US please see http://support.microsoft.com for regional support phone numbers.


    Having said that, I'd still like to provide the following general troubleshooting steps for your reference. You can try them first before calling Microsoft CSS:


    Note: Please perform a complete system backup first. If any unexpected issue occurs, we can quickly restore the system to the current status.


    1. Scan your system to make sure that the system is virus free. Temporarily disable your anti-virus software to see if this problem is gone.

    2. If you have recently installed any software, hardware or drivers, please remove them. 

    3. Disable all the third party startup programs and services by using the MSConfig.exe utility shipped with system.


    How to take a Clean Boot


    Please take the suggestions in Safe Mode.


    1. Click Start, type "MSCONFIG" (without the quotations) in the Search Bar and Press "Enter" to start the System Configuration Utility.

    2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray).

    3. Click the "Startup" tab, click "Disable All" and click "OK".

    4. Restart the computer and test the issue.


    Note: Clean Boot is a troubleshooting step. If some programs have been disabled, we can re-enable them later. If you see the System Configuration Utility, check the box of "Don't show this message" and then click "OK".


    Please monitor the system in the Clean Boot environment. If the problem does not occur, it indicates that the problem is related to one application or service we have disabled. You may use the MSCONFIG tool again to re-enable the disabled item one by one to find out the culprit.


    4. However, if the issue still persists, please contact Microsoft Customer Support Service (CSS) for further troubleshooting. I hope the problem will be resolved soon.



    Thursday, June 19, 2008 11:05 AM