home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.misc
- Path: sparky!uunet!cs.utexas.edu!csc.ti.com!tilde.csc.ti.com!mksol!mccall
- From: mccall@mksol.dseg.ti.com (fred j mccall 575-3539)
- Subject: Re: Memory parity error detected. SYSTEM HALTED.
- Message-ID: <1992Sep10.162106.14993@mksol.dseg.ti.com>
- Keywords: WINDOWS 3.1, CRASH
- Organization: Texas Instruments Inc
- References: <1992Sep10.133717.21198@funet.fi>
- Date: Thu, 10 Sep 1992 16:21:06 GMT
- Lines: 32
-
- In <1992Sep10.133717.21198@funet.fi> ms86817@cs.tut.fi (Matti Suokko (OH5MRM)) writes:
-
- > SYSTEM ERROR: Memory parity error detected. System halted.
-
-
- > What will cause the error message above ?
- > When I upgraded WIN 3.0 to WIN 3.1 it worked fine, but then
- > I formatted my HD and installed WIN 3.1 again, and
- > now it crashes 50 times a day.
-
- This is generally caused by either bad memory or having memory with
- different speed ratings (on some motherboards). The reason it worked
- when you did the update and not the full install is that when you just
- do the update, Windows 3.1 install won't update some of the device
- drivers and will use those that are already on the disk from Windows
- 3.0.
-
- > Should I install 3.0 first and then upgrade it again to 3.1 ?
- >
-
- Well, that would be an interim fix, but you really need to figure out
- which of the new Windows drivers is stressing your memory and either
- use a different driver or find the problem with the memory. You lose
- performance by using the older drivers (and it is the higher
- performance of the new drivers that is causing your memory to fail
- where it didn't before).
-
- --
- "Insisting on perfect safety is for people who don't have the balls to live
- in the real world." -- Mary Shafer, NASA Ames Dryden
- ------------------------------------------------------------------------------
- Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.
-