How do I interpret BSOD in Vista

Discussion in 'Operating Systems' started by Rob94hawk, Oct 29, 2019.

  1. Rob94hawk

    Rob94hawk 2[H]4U

    Messages:
    2,120
    Joined:
    Jul 20, 2002
    Yes Vista. I get BSOD occasionally. It's an old reliable socket 775 system that I built a long time ago that is only used for email/internet so there's no real reason to build new. However I would like to go SSD/Windows 10 but I would like to find the problem and see if it's worth fixing.

    How & where to do I decipher BSOD's? Thanks.
     
  2. cybereality

    cybereality [H]ardness Supreme

    Messages:
    4,779
    Joined:
    Mar 22, 2008
    Well, Vista was pretty bad. Installing Windows 10 on a fresh SSD will probably be your best bet.

    However, in terms of the BSOD, look at the error code and module. It might say something like IRQ_LESS_OR_EQUAL or give you the module that is causing problems.

    For example, if it is nv---.sys it is probably a Nvidia driver issue. Then you have two things to search for, but a lot of info online (especially on MS forums) will be unhelpful.

    But you can sometimes get lucky a find a solution. Most times just updating all drivers can help, if not OS reinstall.
     
  3. DrLobotomy

    DrLobotomy [H]ardness Supreme

    Messages:
    6,408
    Joined:
    May 19, 2016
    Post up a screenshot so we can google it.
     
  4. pendragon1

    pendragon1 [H]ardForum Junkie

    Messages:
    14,213
    Joined:
    Oct 7, 2000
    "old reliable" and "getting bsods"?!
    yeah you take the error code plus the module name and add vista to the end and type it in google. if the code is always different its usually bad ram.
     
    Armenius and GoldenTiger like this.
  5. Rob94hawk

    Rob94hawk 2[H]4U

    Messages:
    2,120
    Joined:
    Jul 20, 2002
    Stupid thing keeps rebooting before I get a chance too. Is there a log file saved anywhere?
     
  6. Rob94hawk

    Rob94hawk 2[H]4U

    Messages:
    2,120
    Joined:
    Jul 20, 2002
    Thanks for the tip. I'm just concerned that it's a motherboard chipset issue. If it comes down to that I might as well just build a new rig. But if it just comes down to a driver issue then I might as well just go the Windows 10/SSD route and be done with it.
     
  7. DrLobotomy

    DrLobotomy [H]ardness Supreme

    Messages:
    6,408
    Joined:
    May 19, 2016
    c:\windows\minidumps
     
  8. Armenius

    Armenius I Drive Myself to the [H]ospital

    Messages:
    18,998
    Joined:
    Jan 28, 2014
  9. pendragon1

    pendragon1 [H]ardForum Junkie

    Messages:
    14,213
    Joined:
    Oct 7, 2000
    google "disable automatic restart" + your windows version.
     
    Armenius and GoldenTiger like this.
  10. Mazzspeed

    Mazzspeed [H]ard|Gawd

    Messages:
    1,915
    Joined:
    Dec 27, 2017
    Boot of live Ubuntu media and see how the system runs. If you find it's coming up with kernel panic's every 5 mins than obviously it's a hardware fault...
     
  11. the wafflator

    the wafflator n00b

    Messages:
    16
    Joined:
    Feb 26, 2019
    TBH most blue screens are hardware faults. And a blue screen caused by a hardware faults gives misleading debug info that will send you on a wild goose chase. Before digging through any logs, make sure you don't have failing hardware.