Mother Board Monitor Cause Boot Issues w/K7S5A?

Discussion in 'ECS' started by Ralph D., Jul 1, 2004.

  1. Ralph D.

    Ralph D. Guest

    WinXP (sp1 all updates until about 3 or 4 weeks ago) /98SE Dual boot

    ECS K7S5A v 3.1

    Last Sunday I installed Motherboard Monitor... this may be a red herring, as
    it ran OK until today, but that and a lost connection mssg with my HP
    Photosmart 1215 are the only things of any remarkable note.


    Today I rebooted XP and got as far as the splash screen where the green line
    runs across and then the screen went blank and stayed that way.

    Restarted to the Normal Start with same results.

    Start with Last Known Good Configuration did the same.

    Started Safe mode and removed MotherBoard Monitor with no joy.

    Started Safe mode and did a Restore Point to Saturday, when I restarted it
    got to the same spot and died... but when I went back to Safe Mode it said
    'Restore Successful', yet when I tried to restart I still only got to the
    same Splash with green bar and then black and let it wait it out for over 5
    minutes with not so much as a flicker out of the HD light.

    Device Manager shows nothing unusual.

    Win98SE boots and runs fine.


    Could MM5 have some issue with my board's controllers that would not go away
    with an Add/Remove?


    Not sure where I want to go from here, but this is all I can think of with
    only one cup of coffee in me.
     
    Ralph D., Jul 1, 2004
    #1
    1. Advertisements

  2. Ralph D.

    Ralph D. Guest

    Just to be clear... I may be mis-phrasing when I call the black WinXP Home
    screen with the moving green bar a Splash screen... but the idea is that XP
    stops responding at this point in the boot process.
     
    Ralph D., Jul 1, 2004
    #2
    1. Advertisements

  3. Ralph D.

    kirbalo Guest

    I use MBM on both of my K7S5A PRO r.5.0 boards with no problem whatsoever.
    If you did a restore back to a point "before" the problems occurred, then
    you have other problems. Be sure you actually restored to a point "Before"
    the problems occurred.

    Check the capacitors near your RAM, and other parts of the motherboard. My
    r3.1 board went bad because of bad Capacitors. If they look buldged on
    top, and not flat, then you have a problem. I had to replace with a PRO
    v.5.0.

    The reason I bring this up, is some motherboard problems mask themselves as
    software problems. Especially, the ones around the RAM modules. When
    these fail, the voltages are not stable, and it gives the appearance of
    software problems.

    Other than that, MBM works fine. Try to use the very latest version...

    Did MBM install in Win98SE OK?

    --
    Kirbalo...

    K7S5A Pro, Athlon XP 1600+
    1 Gig DDR, 120 GB, nVidia GeForce 4 MX 440
    SuSE Linux 9.0 Pro & XP Pro Dual Boot
    Linux 2.4.21-226-athlon
    10:54am up 10 days 22:57, 4 users, load average: 1.03, 1.13, 1.17
     
    kirbalo, Jul 1, 2004
    #3
  4. Ralph D.

    Ralph D. Guest

    I have not installed the software in the 98 partition, as I do not use it
    that much. I *really* do not want to now as I do not want to risk hosing
    both OS's.

    If it were hardware... why would it boot and run fine to safe mode and run
    alright in 98SE? Not arguing... trying to understand as I don't know what to
    think about the whole situation.

    Thanks for replying.
     
    Ralph D., Jul 1, 2004
    #4
  5. Ralph D.

    kirbalo Guest

    Great questions...and that's what debugging is all about...as you know. It
    was just a suggestion that I wish someone would have made to me about 9
    months before I figured it out after thinking I had a Windows Registry
    problem, etc...

    I suspect that if 98SE runs and continues to run fine, you probably don't
    have a problem...just take a quick look at them for sanity's sake...

    --
    Kirbalo...

    K7S5A Pro, Athlon XP 1600+
    1 Gig DDR, 120 GB, nVidia GeForce 4 MX 440
    SuSE Linux 9.0 Pro & XP Pro Dual Boot
    Linux 2.4.21-226-athlon
    11:26am up 10 days 23:29, 4 users, load average: 1.00, 1.07, 1.08
     
    kirbalo, Jul 1, 2004
    #5
  6. Ralph D.

    alpha_uma Guest

    I would run MEMTEST86 first to make sure that the RAM is not the problem. I
    usually make that my very first step in troubleshooting perplexing software
    crashes including BSOD (blue screens of death).

    If the RAM passes MEMTEST86, I would NOT be inclined to suspect other
    hardware problems--at least not at this point--unless you see leaking or
    bulging capacitors or smell a distinct odor coming from the capacitors.

    Restoring Windows to "last known good configuration" would fail if the
    underlying problem is only intermittant and might not have manifested itself
    earlier. There is still the possibility--albeit small--that your underlying
    problem might have been already there even BEFORE you installed MBM. But,
    just like you, I need to be convinced that MBM is not the problem as
    "accuse-the-nearest-one-intuition" says MBM is the primary suspect. Have you
    tried googling to see if other people runnning WinXP are having similar
    problems with MBM as you are?
     
    alpha_uma, Jul 1, 2004
    #6
  7. Ralph D.

    James J Guest

    FWIW, I've been running MBM 5 with my K7S5A (version 3.1 I think) since I
    got it, over 1.5 years ago. No problems that I'm aware of. I'm running
    Win98. No idea if there might be issues with WinXP, but the general
    combination of MBM 5 and K7S5A doesn't seem to be a problem.

    Good luck.

    James
     
    James J, Jul 7, 2004
    #7
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.