home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!matt.ksu.ksu.edu!news
- From: brettw@matt.ksu.ksu.edu (Brett D. Watson)
- Newsgroups: comp.os.ms-windows.misc
- Subject: Re: Memory parity error detected. SYSTEM HALTED.
- Date: 10 Sep 1992 09:25:42 -0500
- Organization: Kansas State University
- Lines: 23
- Message-ID: <18nlt6INN3at@matt.ksu.ksu.edu>
- References: <1992Sep10.133717.21198@funet.fi>
- NNTP-Posting-Host: matt.ksu.ksu.edu
- Keywords: WINDOWS 3.1, CRASH
-
- 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.
-
- > Should I install 3.0 first and then upgrade it again to 3.1 ?
- >
- Normally, at least in my experience, this message is due to a bad
- SIMM, or simply a SIMM that needs to be "reseated". Try pulling your
- SIMMs first and putting them back in. If you still get the message I
- would assume you have a bad one. There may be other reasons for this
- message.
-
- -=- Brett
- --
- Brett Watson, 915 Calflin Rd. Manhattan, KS 66502, (913) 776-5951
- ==================================================================
- brettw@matt.ksu.ksu.edu | brettw@holonet.net
-