Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I an trying to fix a friends Vista laptop. It is stuck in a BSOD/reboot loop. I found the following article on how to repair a similar issue in XP.

Anyone here know if this will work on Vista??

Or, maybe a link to similar repair in Vista?

share|improve this question

closed as too localized by Ivo Flipse Dec 17 '10 at 18:35

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

We're going to need more details to make accurate assumptions as to what's going on.

  • How far do you get in the boot process?
  • Can you enter the BIOS?
  • Can you boot into safe mode/use VESA drivers?

This can be caused by numerous things. Bad drivers and hardware mainly. Whenever I get a problem in Windows a reboot doesn't fix much, you need to fully power down the system to clear the memory modules AFAIK. If you have multiple memory modules you could try booting with only 1 of them (swap between each) to check if ones defective, same goes for multiple hard disks. We'll need more information to be sure though.

share|improve this answer

Sometimes the BSOD screen displays the name of a DLL file. That is a good place to start - often a newly installed program or driver causes the problem. If no DLL name is present, try checking your hardware as John T suggested.

share|improve this answer
BSOD went by too fast to read, and I had no luck with trying to pause it. – CruelSun Nov 3 '09 at 11:56
You can use this too see older BSODs: – alex Nov 3 '09 at 19:46

Thank you, but on further investigation, I found that the HDD was failing, so I replaced it and reloaded windows.

share|improve this answer