Yucky Blue Screen of (semi) Death

  1. #1
    RxMixer is offline Newbie

    Unhappy Yucky Blue Screen of (semi) Death

    Running win98se and about 2 weeks ago one of my kids managed to let a virus in which was quickly rounded up by Norton Anti-Virus (part of System Works). Normally my NAV does a full system scan once a week on auto status, but after the breach, I figured I'd run a full scan at this point. Went to run full a/v and it runs through the "scanning memory" themometer ok but then just hangs at this point and never even starts to click off any of the "scanning master boot record" termometer. Hangs for about 30 seconds then the Blue Screen "WINDOWS FATAL EXCEPTION ERROR 0D ("zero" D) HAS OCCURRED AT F0000:0000E4BE (all zeros here, folks). THE CURRENT APPLICATION WILL BE TERMINATED ..." BLAH BLAH BLAH. Clicking on any key will terminate NAV and return me to my desktop. I reinstalled NAV again but still came up with the exact same error. I can't find this error anywhere and this looks like a friendly forum, so I'm wondering if anybody out there has any suggestions or do I have to reinstall WIN98 again?

    Thanks in advance...

    Terry
    Last edited by RxMixer; 21-08-2004 at 05:22 PM.

  2. #2
    DJNafey is offline UK site moderator
    This Microsoft article will probably be of interest to you:

    http://support.microsoft.com/default...g%2Fkbfe0d.asp

    If that doesn't help, then what I would try next is to uninstall Norton System Works, reboot, run a full Scandisk on the hard drive, then run a Defrag on the hard drive, reboot and install Norton System Works again.

    Let us know how you get on - if it sorts out your problem, we can close this thread. If it doesn't, we can help further

  3. #3
    RxMixer is offline Newbie
    Thanks for the heads up DJ. I thought I looked at all the help screens I could find at MS, but I guess I missed this one. Funny (not) problem I had going back a few months ago was all of the sudden, I couldn't get my system to reboot. Was just getting one long and two short beeps when I started up system ... no video. Award BIOS confirms that signal indicates bad video. Also Soundblaster live also not running. HUH?? Running ABIT KT7A mobo, ATHLON 1200, 2G RAM with Radeon AGP video card. Thought Radeon board was bad , had an old VIRGE S3 PCI video card around so I tossed that in .. it works but still running into no sound from the SB card. Got new Radeon 9200 card ... same prob. Looked really carefull at mobo and I think I got a couple of slightly expanding capacitors and wondering if thats affecting the AGP slot. Temps are all low enough lots of fans and using round cable inside full tower. So I think that the old video drivers may be causing the probs according to MS. I'll try the Norton uninstal yada yad yada and get back. to ya. Thanks again Terry

  4. #4
    DJNafey is offline UK site moderator
    No problem - will look forward to hearing from you again soon

  5. #5
    RxMixer is offline Newbie
    We tried, we really, really tried!! Did the NSW uninstall, Scandisk, reboot, Defrag (took forever), reboot, reinstall NSW, reboot , and ..... I still get blue screen . Tried to run it in safe mode and it still got the blue screen but it happened instantly under safe mode, whereas it took about 20 to 30 seconds to happen in normal Win 98se mode. Went to the MS area you linked to and changed drivers for video as they suggested but still came up blue. Any more ideas floating around out there before I reinstall Windows again?

    Thanks in advance,

    Terry

  6. #6
    DJNafey is offline UK site moderator
    As I've always got lots of memory lying around, I would look to swap out the RAM before going to the effort of formatting and re-installing Windows in case it's a hardware problem. If you don't have any spare RAM, maybe you could borrow some out of someone else's PC?

  7. #7
    RxMixer is offline Newbie
    I have 2 sticks of 512 RAM on board and I'm running MemTest on it as we speak 610 Meg - now at 1784 cycles and 2340% coverage with zero errors. Maybe I'll try to swap out 1 stick at a time and see what happens. Funny though (and we're getting away from the Win98 thread here, I know) I ran a program through eSupport.com which shows various mobo parameters (BIOS, chipset, OS, RAM) and it says mem installed = 1024 MB (correct) but this utility says memory maximum = 512 MB. ABIT KT7A Raid Mobo is capable of 1.5 GB. What the ...???
    BTW I installed AVG Anti-virus and thank goodness it came up empty.
    NEW STUFF: Went back into NSW and found the manual control settings to add or subtact the options for scanning memory, boot records and master boot records in addition to the files. Unclicked all 3 boxes -> no prob. Added memory button -> no prob. Took off memory button and added boot record button -> no prob. Took off boot record button and clicked Master boot records and bada-bing Blue screen of death appears!! What does this mean in light of the fact that I unstalled NSW and reinstalled it and have tested system with AVG with no faults??? Going to find a very sturdy concrete wall and run into it pretty soon.
    Thanks, Terry
    Last edited by RxMixer; 26-08-2004 at 11:44 PM.

  8. #8
    DJNafey is offline UK site moderator
    If you leave off the 'Master Boot Record' (MBR) option and run a full scan on the whole system, does it complete successfully and say there's no problems? If it does, then that does point to the fact that there's some kind of problem in the MBR that it can't cope with.

    Formatting the hard disk won't fix that I don't think - you'll need to run FDISK to re-partition it and re-create the master boot record unless you can find a utility on the Internet that can re-create it. It's rather risky though - make sure you back up any files you want to keep before you try anything with the MBR.

    To use FDISK, you might be able to delete the partition and then re-create the partition at exactly the same size. Without formatting, you could quite possibly find that the system then boots up exactly as before with your Windows install in tact ..... but without the NSW problem.

+ Reply to Thread