quake2 and opengl problem

[DuRaNgO]

doh!
jim


[This message has been edited by DuRaNgO (edited 08-13-1999).]

[ZokesPro]

Well, it's not my add-on module, I bought it 2 weeks ago and I got the error even before I put the module in. here''s something to think about:

First I reboot my computer then I try out is an OpenGL screen saver I get that memory parity error and if I run everything else that requires OpenGL I get the same error. But if I reboot again and play Quake II in OpenGL then try out the same screen saver suddenly it works and keeps working until I reboot again.

There are no conflicts In my IRQ's they are all where they should be. Video card on IRQ 11, IRQ Holder for PCI steering is on 11 also.

[iNK]

Damn, I went through the entire process of reformatting and reinstalling everything only to find out, I still get the same memory parity error!

Zokespro, so can you even play quake 2 in default opengl mode?

You know, since we do have the same problem, maybe we have similar hardware that is the cause of the problem? Here's my system...

Asus p2b-s motherboard
P2-350 o/c to p2-412
128MB pc100 sdram
Matrox Millenium G200
Canopus Pure 3dII
3Com 10/100 PCI NIC
Sound Blaster 16 ISA
Seagate 9.1GB Hard drive (eide)
Plextor ultraplex cdrom (scsi)
Yamaha 4260 cd recorder (scsi)
Syquest Syjet (scsi)

Anything look familiar?
I noticed that you have an asus motherboard, maybe this is the problem? Have you updated the bios on the motherboard?

[This message has been edited by iNK (edited 08-14-1999).]

[Markisme]

I got the same problem... I used to have a voodoo2 , now I am using a g400. The voodoo2 is properly uninstalled, but games like q3test still can't initialize an opengl driver...even my screensaver doesn't work with opengl....
Even direct3d games tend to crash while adjusting the setting to the primary display.
Tomorrow I'll install windows again...

sigh

[Fifth Horseman]

>I am frustrated with this problem of mine. >Everytime I try to play quake2 in default >opengl mode, my computer blanks out and >shows the following blue screen error:
>System Error
>
>Memory parity error detected
>System halted.
>
>My system is the following:
>Asus p2b-s motherboard
>Matrox millenium g200
>Pure3dII
>p2-350 o/c to p2-412
>128mb pc100 SDRAM

Normally, the only time I have ever seen a machine crash with a parity error is when there was a problem with the system's RAM or a BIOS setting (the latter being somewhat more rare though).

On the software side of things, install Q2 to a new directory and try running it from there to make sure it's just not a screwed up install that's causing your grief. =)

While your at it, try updating your motherboard with the latest BIOS:
http://www.asus.com.tw/Products/Moth...ot1.html#p2b-s

Depending on when you bought your board, you may have a beta BIOS on it (two people I know who bought the P2B-S had beta BIOS's).

In your BIOS settings, I suggest you go into your manually set the settings for your RAM (instead of having it auto-detect it from the EEPROM on the DIMM). If you have more than one RAM DIMM in your machine, and they're from different manufacturers, sometimes the information that's programmed into both of them may be different from each other. Also, (if the BIOS allows you to) change the parity setting for your RAM to NON-ECC. Also, try toning down your AGP Aperature to only 64 for the time being.

If the above doesn't work, then your going to have to start digging into the box. If you have more than one DIMM, take one out and try running the machine/game with only that one DIMM. If that doesn't help, take out that lone DIMM, and replace it with the one you just took out.

If the above doesn't work, try plugging a lone DIMM into a different DIMM slot (other than the DIMM slot you just plugged everything into).


I know the above sounds far-fetched, but I have seen some of the above cause some really strange errors on some PC's.

Regarding my own PC's, on my NT 4.0-SP4 server (P2L97-DS/256MB RAM), when I upgraded the memory from 128MB to 256MB, the machine went totally nuts (random BSOD's on startup, incorrect memory counts, programs refusing to run, etc). After playing around with it, I isolated it to a flakey DIMM slot (slot #2 no less), and incorrect memory timings (two different manufacturers of RAM).


Hope this helps.

FH

[Fifth Horseman]

>I am frustrated with this problem of mine. >Everytime I try to play quake2 in default >opengl mode, my computer blanks out and >shows the following blue screen error:
>System Error
>
>Memory parity error detected
>System halted.
>
>My system is the following:
>Asus p2b-s motherboard
>Matrox millenium g200
>Pure3dII
>p2-350 o/c to p2-412
>128mb pc100 SDRAM

Normally, the only time I have ever seen a machine crash with a parity error is when there was a problem with the system's RAM or a BIOS setting (the latter being somewhat more rare though).

On the software side of things, install Q2 to a new directory and try running it from there to make sure it's just not a screwed up install that's causing your grief. =)

While your at it, try updating your motherboard with the latest BIOS:
http://www.asus.com.tw/Products/Moth...ot1.html#p2b-s

Depending on when you bought your board, you may have a beta BIOS on it (two people I know who bought the P2B-S had beta BIOS's).

In your BIOS settings, I suggest you go into your manually set the settings for your RAM (instead of having it auto-detect it from the EEPROM on the DIMM). If you have more than one RAM DIMM in your machine, and they're from different manufacturers, sometimes the information that's programmed into both of them may be different from each other. Also, (if the BIOS allows you to) change the parity setting for your RAM to NON-ECC. Also, try toning down your AGP Aperature to only 64 for the time being.

If the above doesn't work, then your going to have to start digging into the box. If you have more than one DIMM, take one out and try running the machine/game with only that one DIMM. If that doesn't help, take out that lone DIMM, and replace it with the one you just took out.

If the above doesn't work, try plugging a lone DIMM into a different DIMM slot (other than the DIMM slot you just plugged everything into).


I know the above sounds far-fetched, but I have seen some of the above cause some really strange errors on some PC's.

Regarding my own PC's, on my NT 4.0-SP4 server (P2L97-DS/256MB RAM), when I upgraded the memory from 128MB to 256MB, the machine went totally nuts (random BSOD's on startup, incorrect memory counts, programs refusing to run, etc). After playing around with it, I isolated it to a flakey DIMM slot (slot #2 no less), and incorrect memory timings (two different manufacturers of RAM).


Hope this helps.

FH

[Fifth Horseman]

>I am frustrated with this problem of mine. >Everytime I try to play quake2 in default >opengl mode, my computer blanks out and >shows the following blue screen error:
>System Error
>
>Memory parity error detected
>System halted.
>
>My system is the following:
>Asus p2b-s motherboard
>Matrox millenium g200
>Pure3dII
>p2-350 o/c to p2-412
>128mb pc100 SDRAM

Normally, the only time I have ever seen a machine crash with a parity error is when there was a problem with the system's RAM or a BIOS setting (the latter being somewhat more rare though).

On the software side of things, install Q2 to a new directory and try running it from there to make sure it's just not a screwed up install that's causing your grief. =)

While your at it, try updating your motherboard with the latest BIOS:
http://www.asus.com.tw/Products/Moth...ot1.html#p2b-s

Depending on when you bought your board, you may have a beta BIOS on it (two people I know who bought the P2B-S had beta BIOS's).

In your BIOS settings, I suggest you go into your manually set the settings for your RAM (instead of having it auto-detect it from the EEPROM on the DIMM). If you have more than one RAM DIMM in your machine, and they're from different manufacturers, sometimes the information that's programmed into both of them may be different from each other. Also, (if the BIOS allows you to) change the parity setting for your RAM to NON-ECC. Also, try toning down your AGP Aperature to only 64 for the time being.

If the above doesn't work, then your going to have to start digging into the box. If you have more than one DIMM, take one out and try running the machine/game with only that one DIMM. If that doesn't help, take out that lone DIMM, and replace it with the one you just took out.

If the above doesn't work, try plugging a lone DIMM into a different DIMM slot (other than the DIMM slot you just plugged everything into).


I know the above sounds far-fetched, but I have seen some of the above cause some really strange errors on some PC's.

Regarding my own PC's, on my NT 4.0-SP4 server (P2L97-DS/256MB RAM), when I upgraded the memory from 128MB to 256MB, the machine went totally nuts (random BSOD's on startup, incorrect memory counts, programs refusing to run, etc). After playing around with it, I isolated it to a flakey DIMM slot (slot #2 no less), and incorrect memory timings (two different manufacturers of RAM).


Hope this helps.

FH

[Fifth Horseman]

>I am frustrated with this problem of mine. >Everytime I try to play quake2 in default >opengl mode, my computer blanks out and >shows the following blue screen error:
>System Error
>
>Memory parity error detected
>System halted.
>
>My system is the following:
>Asus p2b-s motherboard
>Matrox millenium g200
>Pure3dII
>p2-350 o/c to p2-412
>128mb pc100 SDRAM

Normally, the only time I have ever seen a machine crash with a parity error is when there was a problem with the system's RAM or a BIOS setting (the latter being somewhat more rare though).

On the software side of things, install Q2 to a new directory and try running it from there to make sure it's just not a screwed up install that's causing your grief. =)

While your at it, try updating your motherboard with the latest BIOS:
http://www.asus.com.tw/Products/Moth...ot1.html#p2b-s

Depending on when you bought your board, you may have a beta BIOS on it (two people I know who bought the P2B-S had beta BIOS's).

In your BIOS settings, I suggest you go into your manually set the settings for your RAM (instead of having it auto-detect it from the EEPROM on the DIMM). If you have more than one RAM DIMM in your machine, and they're from different manufacturers, sometimes the information that's programmed into both of them may be different from each other. Also, (if the BIOS allows you to) change the parity setting for your RAM to NON-ECC. Also, try toning down your AGP Aperature to only 64 for the time being.

If the above doesn't work, then your going to have to start digging into the box. If you have more than one DIMM, take one out and try running the machine/game with only that one DIMM. If that doesn't help, take out that lone DIMM, and replace it with the one you just took out.

If the above doesn't work, try plugging a lone DIMM into a different DIMM slot (other than the DIMM slot you just plugged everything into).


I know the above sounds far-fetched, but I have seen some of the above cause some really strange errors on some PC's.

Regarding my own PC's, on my NT 4.0-SP4 server (P2L97-DS/256MB RAM), when I upgraded the memory from 128MB to 256MB, the machine went totally nuts (random BSOD's on startup, incorrect memory counts, programs refusing to run, etc). After playing around with it, I isolated it to a flakey DIMM slot (slot #2 no less), and incorrect memory timings (two different manufacturers of RAM).


Hope this helps.

FH

[iNK]

Thanks for the input, but after trying all that have been said, I still have the same problems. I just received a reply from Matrox tech support and this is what they say:

>Hello sir,
>
> We are aware of this problem with ECC >enabled with ASUS motherboards. We
>recommend to disable ECC check from the >system Bios. We are still looking in
>to this problem.
>
>Cris Jerez
>Technical Support
>cjerez@matrox.com

I disabled ECC in my BIOS and nothing have changed... I just replied to Matrox regarding this and will post the results as soon as I receive them.