Notice: Windows Protection Errors really ARE caused by faulty and/or dislodged RAM

[x51out]

I guess the moral of the story is: start with the simplest solution. Sometimes you'd think not to, but then, after a week of head-throbbing agitiation with a windows protection error, ya finally just pull the ficken RAM and then pop it back in and no more error. It wasn't the *.vxd's, or conflicting drivers, or double enties in device manager (although, due to the ever so slightly dislodged RAM, the windows installation was faulty to begin with)... Lesson learned...;) .

[AllGamer]

hmm.... no comments, don't want to spoil your moment :p

what you said is ambigous ;)

[Baddog]

Originally posted by AllGamer
hmm.... no comments, don't want to spoil your moment :p

what you said is ambigous ;)


Well said:t

[x51out]

I did almost write that I felt like the rear end of a donkey after my "discovery" (dumb-stumble-upon-everyone-told-me-so-anyway). Hey, I'm a computer-enthusiast, I'll twist this not-so-bad experience into something positive somehow and if I have to shoud myself in a cloud of ignorance and denial, well then I'll just stay the same person I've always been...:p .

[AllGamer]

there's nothing wrong with what you found/said :)

it just that the opposite can happen too ;)

that's why i said it was an ambiguos statement :p

So in some cases that work, in other cases that doesn't apply, basically it Depends :D