Fr4nk3nst41n

first a little story:

2 and 1\2 monts ago i bought my HD2400 PRO, the drivers that came with it where unstable as nytroglycerin on a paint mixer(randon freezing, *reboots, etc..in less than 3 minutes o use),tried the omega´s 8.10: still unstable,(gfx glitches,0x00000050 BSOD and ati3duag.dll BSOD) but, WAY better than the one before. Then i used the gecube´s 8.10: more stable, less glitches(and still getting the 2 kinds of BSODs). And now im using the visiontek´s 8.11: this is the more stable drivrer as of yet(i can leave the computer turned on for days now) only one problem persists. the 0x00000050 win32k.sys page fault BSOD.

im no expert in programing/memory adresses, but, 15 years of building and fixing computers for living i think have enought knolege to make an educaded guess.


with that, lets get to the point:

the win32k BSOD normally occurs when for some reason the system changes resolution(booting a game,leavig a game,enable a 2nd monitor, and so on...)
and the error message aways states the same memory adress: BF8B525F
i googled for it and the only response i got was on some russian forum
writen in cyrilic(no way i can read that. the only lenguages i know is portuguese and english ) i nedded someone/somewhere to corfirm the hunch i got:

i dont know much about image buffers or how windows handles them, but i think that it hapens somewhere during the process of storing/reading the image buffer, it might be a faulty video ram(i dont think so) or a error from win32k.sys making incorrect calls.

with this in my mind i looked in the micro$oft suppot i have foud this:

Windows crashes and you receive a 0x50 Stop error message when you copy an image to the clipboard in Windows Server 2003 or Windows XP

its not the EXACT problem but its close enough.

i think that the only thing left now it to figure in wich end the problem is:

ati o micro$oft?