pilo7, Well pilo...those codes you've listed are memory addresses and normally the cause of the blue screens are a result of an application wanting to access a specific address that may be already occupied therefore causing the blue screen. The thing that strikes me as odd is the fact that it is happening on an XP system, which manages memory much more efficently, so it may very well be a bad address on the RAM. Let's see what others say before we make the assumption that you have a bad stick of RAM