Black Screen / Freeze after first reboot

Black Screen / Freeze after first reboot

• Chardiot

  thanks wrote:

  6) While warning...  Administrator account is disabled by default.  Sorry had to say it... Becareful not to shoot yourself here having only one admin account going into upgrade.

   

  Oh geez, in XP64 my only account IS the admin account, could that really be the problem I'll create another XP64 account, and run the upgrade from that.

  Cheers!

  
  

• dn8

  This worked for me as well. I had the exact same issue and never would have run the memory diagnostics if I didn't read your tip but it worked. I guess it is just fm. Thanks.
  

• cb3431

  Do not change the bios settings... Besides notice everyone posting here appeared to do so

   

  You might want to add a couple of other add-ins to help you visualize what is going on.  Here are the three:

  • Security configuration and analysis
  • Security templates
  • Local Computer Policy (if not seen add group policy choose the default to analyze local computer and this will load it)

   

  1. Next, open up security templates in the main window right click on setup security and choose save as and rename it.  You will use the new one created so not to muck up the original (I called it newgame so you can follow the next steps). 

   

  2. Right click on security configuration and analysis and choose Open database can also be used to create database, so just type a name (I called it template) and click open and it will be created in your documents folder under security. 

   

                                                                 i.      Next, import the template newgame (the one you just created)

                                                               ii.      Right clicking on security configuration and choose to analyze computer now.

                                                              iii.      Then its time to play the game of search and destroy errors by opening up the trees and finding on the red x’s or most on them before applying

  3. The database column is your new policies and current is settings now.  The first couple of trees are set in the Local Computer Policy while others such as services can be found in admin tools
  4. Key Notes

                                                                 i.      The new system is out of the box so keep in mind new is actually the original so you might want to change local computer policies instead of the db ones and then run the analyze computer again to sync them up.

                                                               ii.      Differences in users can also be a result of windows updates, possibly installed sql server, etc where other users where added.  This is the box setup remember.  If you see system ids (sids) where a name should be that is most likely from you adding a user and later removing them if you are not in a domain for they take time to fill in the names from the domain controller. So let it sit a second before removing them but after a minute go for it.

                                                              iii.      One other trick to fix file system and registry errors is  Choosing to define the policy and propagating permissions down or replacing them when it will not propagate. Closing the two dialog boxes opening them again upchucking define fix a ton of errors where they are overwhelming.

                                                             iv.      In the beginning it might take for ever between each setup do not worry as errors are removed it will speed up.

                                                               v.      Save dialog usually refers to right clicking on security policy analyzer and choosing save.

                                                             vi.      Do not forget to apply and reanalyze.  Meaning it is iterative so it does not need to be perfect each time before applying.  For conflicts in permissions between the registry and file system might stop otherwise stump you on why the red x will not go away.

  5. Good luck… 

  
  

• Sportsdude

  I stated the admin thing but ideally review the system policies. I am not even saying change anything but it will really help in finding where it lies...

  To do so:

  1) Windowkey+r

  2) Type mmc and hit enter

  3) Review the policies with either:

  a) Resultant set of policies (more for domain-based computer)

  b) Security configuration and analysis (more for workgroup based computer)

  4) If you do not know where to begin been there, and I wish someone would have showed me how instead of learning by trial and error. So I could probably throw a quick-and-dirty how-to video together by tomorrow given you let me know soon you absolutely need it.

  
  

• Razzel

  I tried to follow Ramenkage's directions but whenever I boot from the DVD, it says "Windows is loading files" then it goes to the logo screen with the green progress bar then to the black screen. If I don't boot from the DVD, then a menu comes up that looks like this:
  
  

  Windows Boot Manager
  
  

  Choose an operating system to start, or press TAB to select a tool:
  (Use the arrow keys to highlight your choice, then press ENTER.)
  
  Earlier Version of Windows
  Windows Setup
  
  
  
  
  
  
  Tools:
  
  
  Windows Memory Diagnostic
  
  
  
  
  If I choose to run the Windows Memory Diagnostic, it runs 2 memory tests and then restarts and the same problem happens
  If I choose to run the earlier version of windows, it restores windows XP
  and if I choose to run windows setup, it freezes on the black screen.
  

  
  

• RajeshR

  Thanks thanks!

  I went to the mmc, and loaded the secpol file with all the policy stuff in, not sure what I wa slooking at or whether anything needed changing though... was that the right one to lead

  Cheers!

  
  

• iosys

  I have the same issue as listed above and I just tried to run the memory diagnostics and it didn't work. Could someone clarify the steps involved to do this and have it work I'm not sure I did it right.
  
  

• kevinj

  I'm having the same problem. I haven't tried removing any peripherals yet, but I somehow doubt it will help. One difference: If I boot into Safe Mode, it takes a while but eventually gets past all the files it has to load, then informs me that I can't continue the installation in Safe Mode. Then it hangs again.
  
  My specs are:
  

  • Pentium 4 3.0GHz HT
  • 512MB DDR2 PC4200 SDRAM
  • nVidia GeForce 6600GT
  • Creative SoundBlaster Audigy2ZS Platinum
  • WD Raptor 36GB 10,000RPM SATA-150 (boot drive)
  • WD Caviar 200GB 7,200RPM SATA-150

  Any help would be much appreciated.
  
  

• Voodoo45

  Hello- I have ran into just about every problem listed in this section.  Yes, this was a very unproductive year, but funny for all I can do is laugh thinking about it.  I feel your frustration and like people no to problems are identical, but here are a couple of ways I got back up after being black and blued down...

  1) First can you boot from disk  I have found over the builds that upgrade versions have not while full installation disks do. If so a repair hyperlink is on the first page and the following one has a fix boot issues to try.

  2) Vista changes the disk partition sizes leaving more unclaimed space in the beginning and end.  I have discovered in the past (when routating the order of disks to keep working systems intact) the block in beginning was to large to boot from.  Fix there was formating the drive from the command prompt or from running from an xp disk and just killing the system as soon as it got that far into installation.  Then NOT messing with the vista formatting options from the gui.

  3) Policy settings got me too.  If possible (probably not in work environment scarer if you can)  login as an admin and reset the policies back to factory settings.  Several routes allow for this to occur.  One could be running the policy analyzer snapin.  OR just open and go to admin tools then "Local Security Policy".  Next, open up the trees and right click when your cursor is in the dead middle a setting.  From there you should be able to see default settings. This is not always possible in corporate world.

  4) Worst case scenario get bartpe it is a freeware under the gnu license that will boot the system off of the cd drive allowing you to recover and or fix problems from a simple gui.  OR boot off of a floppy/usb jump stick etc the point is to thinking-out-of-the-box when you are black and blue.

  5) Might have tripped here but worth the warning.  Vista has several locks requiring it to authorize itself before allowing you access to the interent.  So be aware of the catch of needing the nic driver but stuck on how to get it to there.

  6) While warning...  Administrator account is disabled by default.  Sorry had to say it... Becareful not to shoot yourself here having only one admin account going into upgrade.

  7) Bios settings DO NOT SET! Leave the defaults... in the past used to require tweaks at times.  Vista gets around them.  For example, I only plug in a floppy drive in once every few months to update the bios or as a last resort.  However, it is the first device to boot.  A couple of years back I would get errors on this and similar blantent logical errors and not anymore.  They got the processor under check, for in the past I used to reload the bios when I messed the system.  Versus opening the box and reseting the cmos on taking the battery out and causing a short.  Vista will not  allow me to do this anymore either erroring while writing the floppy or during boot, but updating the bios still works.  Vista even speaks, scary (hit the box hard enough and you should get an echo). Leading me to wonder if defaults are best like in ipv4 vs. ipv6   I just tested several of these answers again. And it all boils back to no modification to the bios!  I have no cpu fan, diskette which used to be huge red flags, and when I changed the bios to what it was it worked, but much more problematic, then removed an ide drive and would not boot until I used the defaults.  PS: Same for ipv4 leave defaults if you want much use if any of ipv6 in networking.  The managed code virtualizes most and setting the board bois only interfers with that...

  8) Remember most problems are a bunch of little ones.  So to brake down the scope and eliminate some hypothesis' try this... Reload to some other os (xp or 2003) then download a trial of virtual pc. Then run the install on the virtual pc for vista this will not leave you feeling blue.

  9) Finally, and the thing that has got me several times is a scratched and/or dirty disk.  Little secret: car wax is great for scratched and scuffed cds/dvds.

  
  

• toddhd

  Alright, I fixed it. I started thinking maybe my memory was bad (even though it had been working perfectly with XP). So I found the memory diagnostic tool on the install DVD and ran it. It didn't find any probems, but as soon as it finished, Vista loaded and continued the install. I'm not sure how exactly this fixed it, but it's certainly worth a shot for anyone else with this problem.
  
  

• Mystret

  I had one freshly formatted ntfs partition on each drive.
  
  

• Markus Fritz

  I have the same problem. I am running an Athlon X2 4800 in an Asus A8N-E with 4gb Ram. Only one internal SAT 300gb drive, with a seperate D partition. I instal Vista Business 64 on the D partition, and everything works just dandy, but when it does the first reboot, it hangs with a black screen with a few small coloured squares/pixels in the top 3rd of the screen.

  Please, can someone offer some finite advice on this

  Cheers!

  
  

• DSent

  just a thought, are u using ntfs partitions

  
  
  

• NeederOfVBHelp

  What ended up working for me went something like this:
  

  1. Boot from the Vista DVD and run a fresh install (not an upgrade). The first part of the install runs smoothly, and then the machine reboots.
  2. If it tries to boot from the hard disk (which would be the normal next step), the loading bar animation appears, then disappears. The system hangs on a black screen with the hard drive light on, but no audible hard drive activity.
     
  3. The solution is to boot from the DVD again, and run the repair utility.
     
  4. The repair tool finds nothing wrong, and gives more options. One of these will be the memory diagnostics tool.
  5. Run the memory test. When it finishes, Vista successfully (albeit slowly) boots and completes the install.

  Once again, this is what worked for me, with my machine's unique hardware quirks. It may not (and probably won't) work for everybody. But it's certainly worth a shot.
  
  
• Black Screen / Freeze after first reboot