After reading this, I really believe you already have a good guess where
the problem lies...   best guess at this point...   it is either your motherboard
or your SDram chips.

My first thought would be to check that you have the proper settings for
your ram in the CMOS settings and if you have multiple chips that they
are matched, (if you are using two 16mg chips and they are not matched
it could also create this effect).

The second thought is that either or both your motherboard or your Ram is
bad.   Since you have other computers at home, you could try swapping out
the ram with another computer...  see if the problem persists.   If it does with
different ram, than your failure is in the motherboard.  Make sure all the settings
on your motherboard are correct based on your CPU, from the motherboard
manual, (you did not mention brand or model of your motherboard).   If these
settings are correct...   then you will probably need to have the motherboard
replaced under warranty.

That is my best guess based from the available information...

  Bob Wright


At 03:17 PM 10/9/98 , Ed Richardson wrote:
>Friends on the List,
> I hope you can help one more troubleshooting novice. I recently finished
>assembling my sons computer and am having quite a bit of difficulty getting
>it going. (I have assembled others and not run into to much trouble.. YEAH,
>SO!!! :-) It has run- sound, picture and all but only once for a short
>period and was on the fritz again when started the next morning. I have
>tried formatting and reloading windows and even deleting partitions and
>logical drives and re doing that area of the initial setup. It is the 4th
>computer in the house (or 5th if you count the old 286 in the basement) so
>I was trying to build it economically and it contains some, uhm,
>inexpensive parts but all new and they should work. (hopefully) Some things
>I have noticed is that the RAM count at start up is inconsistent, sometimes
>32768 like it is supposed to be but other times @ 1/2 that amount or around
>20000 etc., just not consistent, also  it says checking NV RAM instead of
>SD like it's supposed to be? What is NV? Anyway, the main problems begin as
>Win. is restarting and checking for installed hardware,(I have installed
>successfully from this W95CD in the past) sometimes it will freeze at this
>point and I will have no choice but to reset,and it wants to run scan disk
>and it finds a varying amount of data on drive c: that may be "one or more
>lost files or directories but are probably just taking up space", but I
>don't think so at this point. Then if I can get it through the first time
>Windows 95 has been run and to the desk top screen quite often the program
>menu is empty etc., it's just not loading correctly. Then the "Blue screens
>of death" start, some examples of the errors are "a fatal exception OE has
>occurred at 0028:c0004a64 in VXD VMM(01)=00003a64, current app will be
>terminated" and another was can't access DLL at 003:00007089 and so on. I
>have disabled the on MO board sound card and have no extras hooked up yet.
>The system consists of Quantum 2.5 Big Foot, 32MEG SDRAM, 200MX Cyrix
>processor, 24x CDROM  and Mitsumi 3 1/2 drive. I appreciate your taking the
>time to read this and send any advice, direction, or hunches you might
>have.    Ed Richardson   Bolivar, Ohio

                                  -----
                PCBUILD mailing list -  http://nospin.com
         Bob Wright:[log in to unmask] - Drew Dunn:[log in to unmask]