PC Pals Forum

Technical Help & Discussion => Windows PCs & Software: Help, News & Discussion => Topic started by: limesy on June 13, 2006, 19:24

Title: Messengers
Post by: limesy on June 13, 2006, 19:24
I just had reinstall windows 2000 on my laptop to get wireless access on my pc. I'm using someone else's network until I can get my own acces and they took certain things of that report to microsoft or something. I haven't a clue, he prefers linux.

Anyway I can't use any messengers on here. I've tried yahoo, msn and gaim. I can send messages but as soon as someone replies the computer screen goes blue and something about a memory dump flashes up breifly before it reboots.

Does anyone have ideas on how I can fix this?
Title: Messengers
Post by: Sandra on June 13, 2006, 19:34
Hi limesy and :welcome:

When the screen goes blue and you get the memory dump there should be a Stop Error message.

It will start with 0x000000 and have 2 more letters or numbers after the last zero, ignore whats in the brackets after that.

If you can let us know the 0x000000?? code we may be able to help, nothing comes to mind at the moment from your symptoms though  :(
Title: Messengers
Post by: Simon on June 13, 2006, 19:36
Hi Limesy, and  :welcome:

Not sure what your problem could be, but hopefully someone will be along to help you in a little while.

A long shot, maybe, but have you tried Trillian?  It's an all in one messenger, and should connect to all your contacts on the various messenger clients, in one window.

www.trillian.cc
Title: Messengers
Post by: limesy on June 13, 2006, 19:47
I haven't tried trillian someone else suggested that but I thought the same thing would happen as when I tried gaim but I'll give it a go.

I'll try and get that number too sometimes it only flashes up briefly before rebooting but I'll do my best
Title: Messengers
Post by: sam on June 13, 2006, 19:54
its  supprising that gaim doesnt work, but it sounds like a system issue possibly related to the network communications, might be useful to ping the machine and see if a similar error occurs.

Oh and you could always use the annoying http://webmessenger.msn.com/