Repeated freezes at Starting Windows screen, "Startup Repair" no good

Page 1 of 2 12 LastLast

  1. Posts : 24
    Windows 7 Pro 64 SP1
       #1

    Repeated freezes at Starting Windows screen, "Startup Repair" no good


    I've been working on this problem with people on the BleepingComputer forum for over two months, and while all of their advice has seemed slightly sensible at the time, after replacing EVERY SINGLE PART OF THE COMPUTER save the Seagate-tested, Seagate-passed Seagate hard drive, the CPU, and two of four RAM sticks (which have passed over 80 hours of Memcheck testing)...

    ...I'm beginning to wonder if the problem isn't at least in part with the advice I've been getting over there.

    So, Seven Forums, here's the deal: constant freezing of the "Starting Windows" screen on a relatively fresh install of Windows 7 Pro x64, SP1. "Relatively" fresh in that I've installed all the Windows updates, the newest driver for my graphics card, Chrome, Sublime Text II, Speccy, Dropbox and Keepass.

    The BIOS for my motherboard (brand new!) is updated to the latest version.

    I have unplugged my Delta 44 sound card on the off chance it is the problem child, but the problem persists, so I'm guessing not.

    Here's Speccy:

    http://speccy.piriform.com/results/z...tIGFNkAulcqUFt

    I used to have hobbies. I'd go for walks with my wife, try to learn to play the banjo, cook stuff. Make small batches of wine.

    Now, all I do is work on this infernal box of stinking misery. All I do is run Memtest, run Seagate drive diagnostics, reinstall Windows and occasionally think about taking a sledgehammer to this ******* son of a thousand PETs and just buy a Mac.

    So: new forum. Computer from hell. Any advice?
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    PantsMasterson


    Please check Event viewer to see what is logged there relating to the problem.

    Usually freezing is either hardware (ram, etc.) Which you seem to have eliminated or software conflicts.

    If you have a BSOD (i know it just freezes) please upload at least one because we can examine the drivers that were loaded leading up to the freezes, et
    c.

    There are several ways to find what the problem is. The best is to go into event viewer (type eventvwr in search). Event viewer (local) >>> look for errors listed in the last day, week, etc. Then go to the windows log>application tab. Finally the windows Logs>system tabs.

    You want to look for all errors (they have red in the left column ).

    When you find them you want to look for errors that say app hang, app crash, or anything that relates to the problem.

    When you find them please note the event ID, and the source codes and tell us what they are.



      My Computer


  3. Posts : 24
    Windows 7 Pro 64 SP1
    Thread Starter
       #3

    No BSODs, at least according to BlueScreenViewer.

    I can't find any errors called "App hang" or "App crash" -- there are a LOT of Kernel-EventTracing errors (Event ID 3), and quite a few Kernel-Power and EventLog errors.

    The EventTracing errors all have the following message:
    Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D

    The Kernel-Power errors (Event ID 41) are about rebooting the system without shutting down properly, and I'd guess stem from having to reset when the system freezes at the Starting Windows screen.

    The Legacy Uninstall error (all Event ID 0) reads: The description for Event ID 0 from source LegacyUninstaller cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    Legacy uninstall did not succeed.


    There are very rare errors in the Windows Logs/Application and Windows Log/System sections:

    Application:
    - LegacyUpdate error
    - SidebySide error (EventID 72, Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.)
    - .NET Runtime error (Event ID 1101, .NET Runtime Optimization Service (clr_optimization_v4.0.30319_32) - Failed to compile: System.Data.Entity, Version=3.5.0.0, Culture=Neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil . Error code = 0x80131516 )
    - SidebySide error (see above)

    System:
    More Kernel-Power errors related to unexpected reboots.

    If it helps, I can attach the events for November 14. This system doesn't allow .evtx files, though.
      My Computer


  4. Posts : 24
    Windows 7 Pro 64 SP1
    Thread Starter
       #4

    Another freeze this morning; this time past the password screen, on the desktop, as the spinning blue circle told me programs were loading.

    No BSOD.

    Event Viewer, Administrative Events, three errors from today:
    Eventlog (Event ID 1101): Audit events have been dropped by the transport. 0
    Kernel-EventTracing (Event ID 3): Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D
    Kernel-Power (from the reset button when the computer froze).


    No errors under Windows/Application logs.
    One error (Kernel-Power, from my reboot) under Windows/System logs.
      My Computer


  5. Posts : 24
    Windows 7 Pro 64 SP1
    Thread Starter
       #5

    Same old, same old today: freezes on Windows Starting Up. No BSODs.

    Errors:

    Kernel-EventTracing (EventID 3): Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D
    volmgr (EventID 46): Crash dump initialization failed!
    SideBySide (EventID 33): Activation context generation failed for "c:\program files (x86)\Steam\steamapps\common\dawn of war 2\WorldBuilder.exe". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="8.0.50727.762" could not be found. Please use sxstrace.exe for detailed diagnosis.
    SideBySide (EventID 72): Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.
    Kernel-EventTracing (EventID 3): Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D


    Any ideas? Anybody?
      My Computer


  6. Posts : 24
    Windows 7 Pro 64 SP1
    Thread Starter
       #6

    I have found in a few forums a recommendation to delete MSSEOOBE.etl.

    According to this forum, it isn't even a permanent fix.

    But the point is moot, because I don't have that file, or even its hypothetical folder, anywhere on my system.
      My Computer


  7. Posts : 2
    windos 7 ultimate
       #7

    one thing i would try is getting a second hard drive (borrow one0 and just test a fresh install on that. even though a hard drive may pass a test for bad sectors the drive may not be functioning physically .
    thats what i would try next.
      My Computer


  8. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #8
      My Computer


  9. Posts : 24
    Windows 7 Pro 64 SP1
    Thread Starter
       #9

    Another freeze on "Starting Windows" this morning; this time, no BSOD or events at all (no events in the Event Viewer dated today).

    This is the latest iteration in a series of problems that has led me to replace memory sticks, my graphics card, power supply, and motherboard. Now, apparently, it's a faulty hard drive that somehow escapes all diagnostics with flying colours? It's a little frustrating.
      My Computer


  10. Posts : 24
    Windows 7 Pro 64 SP1
    Thread Starter
       #10

    More freezes on "Starting Windows" this morning, still no BSODs or errors in the Event Viewer.

    Startup Repair does not work.

    On the off chance that it is a bad hard drive, I've ordered a 500GB so I can start again, clean, and see what happens.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 23:33.
Find Us