Over last few days an old friend, the beloved Blue Screen of Death
has come back to stay on my el-crappo-pain-in-the-arse-supposedly-super-PC...
Last time it paid me a visit it was a matter of bad RAM, and after looong
memtest sessions I finally narrowed it down to the second RAM module,
which I fortunately managed to exchange for a working one.

This time, memtest fails almost instantly with both modules in their default
positions (Channel A slot 1, Channel B slot 1). I tested each module
seperately in Channel A 1st slot and then in Channel B 1st slot, and they gave
no errors. If I put them in Channel A slot 2 and Channel B slot 2, memtest
works ok.

Does this mean that Channel B slot 1 has got issues?

For the record, my mobo is an MSI 865PE Neo 2 LS and my
memory consists of 2 Kingston Hyper-X DDR433 CL2 modules...

Some memory slots can be annoyingly difficult - I've had troubles with badly seated memory a couple of times, sometimes resulting in symptoms typical of bad ram (occasional BSODs, games crashing etc.). Both times this has happened I've been able to fix it by reseating the RAM though. Maybe this is the case here as well?

I'd try to put the modules back in the default positions, making sure they're properly in place, before jumping to any conclusions - if it still fails you might have a dodgy slot though.

With the modules in their current positions (A2,B2) my memory passes memtest.
Game crashes have occurred though, even with this set-up...
I'm wondering if playing games through daemontools with kerio personal firewall
enabled has got something to do with it.

With modules in previous positions (A1,B1) memory doesn't pass memtest and
I have GPFs and BSODs aplenty...


Is this grounds for a new mobo?

If anything, it's a reason to RMA your current mobo. First i'd check eveything else though.. like, is there a BIOS update?

There is a new bios version. It promises beter system stability.
Downloaded it but haven't flashed it as yet.

BTW, I noticed that the driver causing the BSODs in one winacusb.sys
Microsoft says the vendor of this driver is Conexant... Never heard of them...

Edit: It appears to be one of my modem drivers...

If it's Conexant, it's almost definitely modem. My obscure-brand (Accton) 56K modem runs on Conexant drivers too (though it doesn't give me headaches like it has given you).