Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Windows won't boot - stalls before login/welcome screen

16 Dec 2012   #1
InvalidError

Win7 Pro x64
 
 
Windows won't boot - stalls before login/welcome screen

A short intro (skip if you like):

Hi everyone, this system has been running close to 24/7 since roughly two years ago. A custom RT7Lite disc was used and a lot of tweaking has been done, so the system is well in need of a fresh format. Unfortunately, this was planned for after the holidays, and as I was unprepared for this crash, it could take me longer to figure out what I need to transfer to a new install then it would to fix the current one. Any suggestions will be greatly appreciated!

System specs:

OS: Win7 Pro x64
CPU: Intel Q9550
Motherboard: Gigabyte EP45-DS4P
Memory: 8GB PC2-8000
Graphics Card: ATI HD4870 (PCIe/512MB)
System Drive: 2x Intel x25-V SSDs in RAID0 (via mainboard's ICH10R)
Network: Intel Gigabit CT PCIe card
Firewall: Outpost Pro

The current problem:

System passes POST, bootloader, "Windows is Starting" animation. USB devices initialize, and the mouse pointer appears. The screen remains black (no background, login dialog, accessibility/power buttons, etc.) indefinitely. The mouse still moves and NumLock can be toggled, so the system has not halted - it just doesn't get any further than that. After 15 minutes power-saving kicks in and the display goes to sleep - Moving the mouse or pressing a key turns it back on again as though everything is normal, but it's still stuck at the black screen.

Events leading up to this:

I have been using a PCIe JMicron-based SATA card with a broken eSATA port, and I recently got an ASM1061-based SATA 6Gbps card to replace it. This new card is PCIe 2.0 and my motherboard only has two 2.0 slots - the x16 and x8 slots meant for video - so I was testing what difference it made running my gfx card in x8 mode. I decided running it this way was OK, so I started tweaking the SATA card. I had seen reports that using the generic Microsoft driver with this chipset was hugely detrimental to write performance, so naturally I tried to install the newest ASM one. This didn't work, as Windows told me "this location does not contain information about your hardware". I resorted to using the driver's installer program, which ran perfectly - but Windows kept using its own driver anyway.

Finally, I decided to try the older version of the ASM driver. This installed properly and the device was no longer listed as a generic ATA controller. On a hunch, I tried updating the driver again (without rebooting) to the newest driver, and Windows accepted it with no complaint this time. However, my firewall (Outpost) asked me whether I wanted to allow direct disk access to an uncertified/??? driver. I affirmed this as it was intended. It's worth mentioning that Outpost was being a nuisance when I was testing PCIe slots, as it wiped its configuration file each time I moved my NIC. This meant it lost all the rules regarding which system components were allowed to do what, and had me confirm each one.

I then rebooted to MS-DOS on a USB stick to update the SATA card's firmware. I restarted into Windows several times without issue, but the SATA card didn't show during POST or in the Device Manager. Turns out the uploader mislabelled a BIOS OROM module as the add-on card's firmware. Back in DOS, I flashed the correct/original file, but the card still didn't seem to work (no BIOS info page, still absent in Windows) so I went back and flashed it a third time. After that theBIOS splash screen re-appeared and it seemed like everything would be fine.

However, upon booting into Windows, I was now getting a consistent BSOD: STOP 0x00000024 0x0000000000190494 (I only have the first two numbers, which I googled on my phone out of curiosity). I rebooted to safe mode and the same BSOD came up after CLASSPNP.SYS was listed. At this point I inserted my Windows DVD and ran the Startup Repair function, which took a while but completed successfully. I checked the log after it was done and the only reported issue was that the 100MB System Reserved partition was "corrupt". After restarting, the BSOD is gone but I now have this black screen/no login issue.

Things I have tried:

-Pretended the login screen was there (entered password and pressed Enter) in case it was a graphical glitch.

-System restore is disabled so I can't use that to revert whatever caused this.

-Tried booting in each of Windows' alternate modes (VGA, Safe, Safe w/LAN, Safe w/CMD, Last Known Good, etc.), problem persists.

-Unplugged secondary display in case it was drawing stuff on the wrong monitor.

-Shuffled the expansion cards back to where they were when the problem started, tried alternate locations, booted with all cards removed.

-Opened a command line window from the Win7 DVD and ran SFC and scandisk. SFC reported there were several errors that could not be repaired, however this was also the case several weeks ago when I used SFC to troubleshoot an application. I'm fairly certain this can be blamed on the RT7lite'd install source.

-Booted into an old install of Vista x64 Ultimate on another drive, and replaced all instances of the ASM drivers with the older version. No change. Went back into Vista and renamed the driver files - no change.

Brainstorming:

-Non-destructive "Upgrade" install over existing version Has to be done from within Windows 7. Tried initializing this from Vista, but it seems it can only be installed over the currently active partition (and can't be done anyway because Ultimate trumps Professional.)

-This xbootmgr tutorial helped me narrow the timing of the problem down, it seems to be happening in the SMSSInit phase of MainPathBoot... Knowing this hasn't really helped me so far and it appears xbootmgr has to be initialized from the OS being traced, so I'm not sure if I can even use this tool.

-The automatic Startup Repair script (on the installation disc) reports that the system booted successfully. Running SFC without the /offwindir and /offbootdir switches reports that a system repair is pending. The bootloader lists the OS as "Windows 7 (recovered)"


My System SpecsSystem Spec
.
16 Dec 2012   #2
gregrocker

 

There is absolutely no reason to run a Lite version of WIn7, which is featherlight and always instantaneous when you have a perfect install on adequate hardware. How is it activated?

So you are not going to get support here where we know Win7 best, except to advise that you to Clean Reinstall your licensed version following the steps given (same for retail) to get it perfect.

This should solve all the problems, which are characteristic of trying to run a modded version of an OS that already has every service possible set to Manual on fast triggers, the very genius which has made it the most popular OS ever. Experiments we did during Beta proved that any such trims were always met with unintended consequences.

If not then after your reinstall post back any issues and we will help you resolve them as always.
My System SpecsSystem Spec
17 Dec 2012   #3
InvalidError

Win7 Pro x64
 
 

Quote   Quote: Originally Posted by gregrocker View Post
There is absolutely no reason to run a Lite version of WIn7, which is featherlight and always instantaneous when you have a perfect install on adequate hardware. How is it activated?
My system partition is <25GB, which means Windows' default installation would eat >80% of it. That is certainly ample reason to prevent it from installing applications that will go unused (Movie Maker, Games, and many others.) The main purpose however, was to tweak the settings for SSDs - such as disabling indexing and defrag on the system drive. I'm well aware that 7 "can" do this on its own, but I am not one to let it make its own decisions unless necessary. I'm also aware that this can all be done post-install, but why would anyone bother when it can be done from a single locus. I'm not sure what you mean by "How is it activated", but if you're suggesting I'm using an illegitimate license I can assure you that's not the case.

Quote   Quote: Originally Posted by gregrocker View Post
So you are not going to get support here where we know Win7 best, except to advise that you to [do that thing you're trying to avoid doing].
I'm sorry, but if you don't have a constructive suggestion and are unwilling to help, why did you bother to post all this?
My System SpecsSystem Spec
.

17 Dec 2012   #4
gregrocker

 

Because we offer the Best Practices here for the OS, and feel obligated to comment when we see clearly Worst Practices being done. Not only is the Lite version immediately suspect as is any modded Win7, but compound tweaking leads most inevitably to unbootable Win7 as we've seen here countless thousands of times.

In the past Lite versions were considered warez and might result in outright ban from the Forums.

However for awhile it became apparent they were thought useful for extremely tiny netbook drives and so a cautious tolerance developed.

My best advice to you given the circumstances is to clear the boot sector of code with Diskpart Clean Command then reinstall genuine Windows 7. The fact that you've legally activated it doesn't make it geniune.

Short of that you can Mark Active the System Reserved (if you have it) or C partition then run Startup Repair - Run up to 3 Separate Times . It should automate SFC but if not run SFC /SCANNOW Run in Command Prompt at Boot then from the same command line Disk Check. Everything else that can be done is in Troubleshooting Windows 7 Failure to Start
My System SpecsSystem Spec
Reply

 Windows won't boot - stalls before login/welcome screen




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Windows won't boot to login screen
Earlier today, my laptop (a Dell Inspiron 1545) was lagging hard, so I force shut it down in hopes that it would clear up and run smoothly. However, after restarting the computer and prompting Windows to start normally, I was taken to the default windows 7 login background (the blue one with the...
BSOD Help and Support
Windows Boot stalls when adding additional Sata Drives
I've recently reinstalled Win7 64bit to my Mushkin enhanced Deluxe 240gb SSD. This drive had a missing MBR. I was finally able to reformat it and install Windows after changing the boot to Legacy Only in the Gigabyte BIOS. After installing all the updated drivers and video drivers in the new...
Hardware & Devices
No login screen on boot, Windows 7 Home Premium
When I turn on the computer, I get a blue, wispy screen and a pointer. I have read all the posts regarding this problem. I don't think anyone figured it out without formatting their hard drive. I have created a recovery disc (which is now stuck in the DVD drive b/c I can't eject). Booting...
General Discussion
Windows stalls at the welcome screen
Hello. I have tried startup repairs, I have tried booting in safe modes (it failed to boot safe modes) and running chkdsk + sfc commands via the disk I have. None of these have fixed the problem.
General Discussion
Very slow boot, stalls at starting windows
Hi there, I recently upgraded my windows 7 from the release candidate to an oem version that was supplied with a new computer, I completely wiped the old win 7 os and installed on a clean partition, dual boot with xp, install was great, went fast and no errors, but now it takes up to 20 min to...
Performance & Maintenance


Our Sites

Site Links

About Us

Find 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:26.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App