Win 7 32 bit will not start after update
Installed on new hard drive. No problem started right up. Did updates and would not restart. Will start and run in Safe Mode with networking. Disabled all drivers and tried to restart. Still does not restart. It will get to the starting windows screen but after it runs for awhile the screen flickers twice and reboots.If I restore to early point, it works just fine. What can I do next?
January 24th, 2010 6:08am

If you restore to an earlier point, but then you mention a new hard drive. Clearly though the problem seem to point to a driver and you're not getting any error messages at ALL? Not even in the event manager? Was this an upgrade from Vista or a clean install? What machine is this - be specific to make, model and model # so we can best assist you. Did you do a bios upgrade? Have you checked device manager to see if there are any problems with any devices? You can also do a driver verifier testFor more information about Driver Verifier, see Driver Verifier. Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior. Driver Verifier is included in Windows 2000 and later versions of Windows. Driver Verifier works on both the free and checked builds. The following sections explain the operation of Driver Verifier: Driver Verifier Options describes each of the actions of Driver Verifier in detail. Using Driver Verifier explains how to activate Driver Verifier, how to choose which options are active and which drivers will be verified, and how to monitor the behavior of drivers being verified. No Reboot Feature describes the functionality, available in Windows Vista and later versions of the Windows operating system, that helps to eliminate disruptive reboots. With this functionality, you can use Driver Verifier on production servers that cannot afford to reboot. Additionally, you can monitor your driver while you attach and remove devices. <!----> You can run Driver Verifier on multiple drivers simultaneously, or on one driver at a time. It can perform a variety of actions, and most of these can be optionally enabled or disabled. This allows you to put a driver through heavy stresses or through a more streamlined test. Driver Verifier can verify any number of drivers. However, the Special Pool and I/O Verification options will be more effective when used on one driver at a time. Note On Windows Vista and later versions of the Windows operating system, Driver Verifier runs only with elevated privileges. For more information, see The Verifier Utility. The Verifier utility, Verifier.exe, activates and monitors Driver Verifier. This utility is located in the %windir%\system32 directory of Windows. There are two ways to use the Verifier utility. Command line. To use Driver Verifier at the command-line, in a Command Prompt window, type verifier followed by at least one command-line parameter. Driver Verifier Manager. To open the Driver Verifier Manager graphic user interface, in a Command Prompt window, type verifier (with no parameters). On Windows Vista and later versions of Windows, a Windows Security dialog box prompts you for permission to run Driver Verifier Manager. To run it, select Permit. <!----> Note Driver Verifier Manager in Windows XP and later differs slightly from the version of Driver Verifier Manager in Windows 2000. This section includes: <!----> Verifier Command Line Driver Verifier Manager (Windows XP and later) The Windows XP and later version of Driver Verifier Manager begins with a screen which allows you to select one of five tasks. Whichever task you choose, you will be shown a series of screens that can be navigated by using the Back and Next buttons. When this sequence is complete, use the Finish button to save any changes you have made and exit Driver Verifier Manager. If you wish to discard your changes, use the Cancel button. The following tasks can be chosen from the first screen of Driver Verifier Manager: Create standard settingsSelects a standard set of Driver Verifier options, and then allows you to select the drivers to be verified. These settings will take effect after the next boot. See Selecting Driver Verifier Options and Selecting Drivers to be Verified for details.Create custom settingsDisplays all Driver Verifier options and lets you select from among them. Then, it allows you to select the drivers to be verified. These settings will take effect after the next boot. See Selecting Driver Verifier Options and Selecting Drivers to be Verified for details.Delete existing settingsDeactivates all of Driver Verifier Manager options and deletes the list of drivers being verified. This takes effect after the next boot.Display existing settingsDisplay the options that will be activated and the drivers that will be verified after the next boot. It does not include any volatile settings. See Viewing Driver Verifier Settings for details.Display information about the currently-verified driversThis will display statistics related to Driver Verifier's actions. See Monitoring Global Counters and Monitoring Individual Counters for details. It will also allow you to view and alter Driver Verifier's volatile actions. See Using Volatile Settings.Ok so I gave you all that info, here in a nutshell how to do itYou can try using a tool called driver verifier. If this tool finds a problem, your machine will crash again. Hopefully with it enabled, it will allow you to easily identify the bad driver.Enable driver verifier1) Open an elevated command prompt2) Type "verifier /standard /all" (no quotes)3) Reboot your machine4) Use machine again until it crashes After the crash & reboot, go into safe mode. Disable driver verifier1) Open an elevated command prompt2) Type "verifier /reset" (no quotes)3) Reboot your machineAfter it crashes, look in c:\windows\minidumps for a memory dump file. Post that to a public share on http://skydrive.live.com and post the link here.MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
Free Windows Admin Tool Kit Click here and download it now
January 24th, 2010 10:50am

I am doing as requested, about retart number 20, but it still has not failed to start. This was a clean install on a new hard drive. I am puzzled why it runs just fine until the updates are run. If it was a driver issue would it not fail before the updates? Also, I disabled all drivers and it still would not start.Will update if it finally fails.
January 24th, 2010 8:29pm

Not necessarily, it may be a program or new driver installed that could be causing the issue. So you did the driver verifier and you let it run for some time now and it didn't crash? Have you now turned off verifier (after how long did you let it run?) You can't just disable all drivers, going into safe mode will load the minimum set of drivers needed to start. I'm curious how you're disabling ALL drivers when it doesn't start.You choice of words like "will update if it finally fails" doesn't make sense because on one hand you say it doesn't start, but then you say just the opposite in the next sentence. It could be that the updates are installing new drivers for something - look at the updates list and see what it is installing. 1 - So you're saying that Windows 7 IS starting up just fine now right?2 - But it won't start if you get updates - is that what you are saying? 3 - So you did a restore to an earlier point got it to working and it hasn't failed to start since right?4- You have applied updates again - correct? and now its still booting up just fine right?Just clarifying some of these points so we'll know you're functioning. MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
Free Windows Admin Tool Kit Click here and download it now
January 24th, 2010 10:23pm

hi , cdobbs , some of the links dont work and give 404 errorshttp://social.technet.microsoft.com/Error/Error404.aspx?aspxerrorpath=/en-us/library/ms792872.aspxhave a nice fresh new weekScan with OneCare + 50 Windows 7even Tips + Plagued by the Privacy Center? REMOVE IT + Threat Research & Response Blog + Sysinternals Live tools + TRANSLATOR+ Photosynth + Microsoft Security + Microsoft SUPPORT + PIVOT from Live Labs + Microsoft Live Labs + Office 2010 beta + Get Windows LIVE!
January 24th, 2010 10:42pm

Hi, According to the problem description, this issue can be caused by one of the following factors: Ø Certain update was not compatible with the current hardware or software configuration. Ø The previous updates were not installed successfully. However, I still would like to confirm the following questions: 1. What updates are offered to be installed? Please let me know the update KB number. 2. Are there any driver updates? Based on the current situation, I would like to provide the following troubleshooting suggestions: 1. Update the BIOS and the hardware drivers 2. Create a restore point manually 3. Prepare a Clean Boot 4. Install the updates one by one to narrow down the possible cause 5. Hide the problematic update To troubleshoot the system freezing issue, please try the detailed steps below: Step 1: Please refer to the hardware manufacturer’s official websites to update the BIOS and the hardware drivers manually. Step 2: Create a restore point ===================== 1.Open System by clicking the Start button, right-clicking Computer, and then clicking Properties. 2.In the left pane, click System protection. If you're prompted for an administrator password or confirmation, type the password or provide confirmation. 3.Click the System Protection tab, and then click Create. 4.In the System Protection dialog box, type a description, and then click Create. After that, if any unexpected issues are encountered, System Restore can help us revert. Step 3: Prepare a Clean Boot ===================== 1. Log on to the computer by using an account that has administrator rights. 2. Click Start, type msconfig.exe in the Start Search box, and then press ENTER to start the System Configuration Utility. If you are prompted for an administrator password or for confirmation, type your password, or click Continue. 3. On the General tab, click Selective Startup, and then click to clear the Load startup items check box. (The Use Original Boot.ini check box is unavailable.) 4. On the Services tab, click to select the Hide all Microsoft services check box, and then click Disable all. Note: Following this step lets Microsoft services continue to run. These services include Networking, Plug and Play, Event Logging, Error Reporting, and other services. If you disable these services, you may permanently delete all restore points. Do not do this if you want to use the System Restore utility together with existing restore points. 5. Click OK, and then click Restart. For more information about Clean Boot, you may refer to the following knowledge basic article: How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7 Step 4: Please install the updates one by one to narrow down the possible problematic update. If the issue reoccurs, we can run System Restore again and hide the problematic update. If the issue does not reoccur, the updates should be installed successfully. Step 5: Hide the problematic update ===================== 1.Open Windows Update by clicking the Start button. In the search box, type Update, and then, in the list of results, click Windows Update. 2.Do one of the following. •If you have important updates to hide, click the link that tells you important updates are available. •If you have optional updates to hide, click the link that tells you optional updates are available. 3.Select the update that you want to hide, right-click it, and then click Hide update. Do this for each update you want to hide. 4.Click OK. If the issue persists, would you please send me System Information for analyzing. For your convenience, I have created a workspace for you. You can upload the information files to the following link. (Please choose "Send Files to Microsoft") Workspace URL: https://sftasia.one.microsoft.com/choosetransfer.aspx?key=36ff9187-2178-446b-887b-ef028ad9dc05 Password: tixSzs[%SW0BQ Note: Due to differences in text formatting with various email clients, the workspace link above may appear to be broken. Please be sure to include all text between '(' and ')' when typing or copying the workspace link into your browser. Meanwhile, please note that files uploaded for more than 72 hours will be deleted automatically. Please ensure to notify me timely after you have uploaded the files. Thank you for your understanding. WindowsUpdate.log ===================== 1. Press the Windows key and the R key at the same time, type: %windir% and press Enter. 2. Locate a file named WindowsUpdate.log and send it to us. System Information ===================== 1. Click Start, type in msinfo32 in the Search bar and then press Enter. 2. Choose Save from the File menu and save it as an NFO file. 3. Find the file, right-click on this file, click Send To, and click Compressed (zipped) Folder. 4. Send the compressed file to us. Regards,Arthur Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2010 12:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics