BluesScreen on Win2k and WinXP with G400

[xortam]

Svenneman ... there are some things you can try if you're interested in tracking down the problem. Go through the referenced troubleshooting procedures. Try testing your memory modules individually and swapping in other memory. The G400 may be just a scapegoat for other problems in your system. Matrox will replace your card if you really do have a HW problem with the G400 (questionable since you have no problem in Win98).

[Svenneman]

I have 1 new 256mb memory module (Compitable with Athlon)

I replaced my memory 1 year ago because my old module was crap, it made my computer hang itself in win98, this one works fine though, are there any program out there were you test your RAM memory? I could try it if there is one...

[bvh]

I had the same problem with my G400 (BSOD during boot) under Win2K and WinXP. It was strange because I had to remove one memory stick (Value Ram Kingston) to get it working. So try another memory if you can.

[Svenneman]

I can't afford buying a new memory stick

[dZeus]

but you can determine wether it's the RAM stick causing the problems.

https://www.memtest86.com

[Svenneman]

thx I will try it

[Wombat]

It's worth running the test. Unfortunately, bad memory CAN pass those tests sometimes. Just a caveat.

[MK]

My sys is still running fine, but I will give memtest a try ...

MK

[MK]

O.K. now I got my Blue Screen. It reads as follows:

----------------------------------------------------------------------------------------------------
xxx STOP: 0x0000001E (0x0000005, 0xBFB65227, 0x00000000, 0x01000003)

KMODE_EXCEPTION_NOT_HANDLED

xxx Address BFB6522 base at BFAEC00, DateStamp 00000000 - G400DHD.dll
-----------------------------------------------------------------------------------------------------

I have already tried memtest and it reports 0 errors after 14 h with 18 test runs.

Ideas ? Any advice would be appreciated !

MK

[xortam]

"Any advice?"

Have you gone through all of the troubleshooting steps that MSFT documented?

[MK]

xortam - yes I checked everything. I will try the new drivers (5.71) when the final version is out.

Any other ideas ?

MK

P.S: It really looks like the G400 being the culprit, isn`t it ?

[xortam]

Don't have time to review this right now but if you suspect a piece of HW, e.g. the G400, simply swap it for a different piece. You sometimes have to experiment to see what effects your symptoms and hope that leads to determining what the actual problem is.

[MK]

Never change a running system

xortam - I don`t have any other graphics card lying around and the system is absolutely stable besides that. Therefore I am not going to mess around with that.

But thanks for you help.

MK

[Greebe]

ON the MSI-6167 DO NOT place any memory module in the third mem slot if you have (closest to the cpu).

There is a known bug with the mem controller on the 751 northbridge chip.


note: One of the reasons I buy Crucial memory is because they were the ones that enlightened me to this fact when I found this very problem back in March of 2000. The 6167 is the only MB I would use in those days to ensure proper functionality of the Athlons I mod'd.

[desired]

I have the same problem. Same BSOD because of the G400*.dll. It happend in Win2K Proffesional and now in WinXP. Win98 is working perfect. And it's not very driver related; I guess. I used every Win2k drivers since W2K_551 (final, beta and WHQL) and the problem remains. Although It happens rarely, I may say once every 2 weeks, it's annoying... There are no logs in event viewer, and I couldn't find any relation between the BSOD and any programs that were running when it happens....

My system specs: Asus K7M mobo, Thunderbird 750 slot (previously Athlon 500, same problems), G400DH 32Mb AGP2, 1 256Mb DIMM (previously 128Mb DIMM, same problem), Sb. Live Value, Seagate Barracuda IV and IBM DJNA HDDs, ISA winmodem, no network adapter, etc.

Aren't there any sollutions for this problem??
dOOMY