![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
So, digging deep into the workings of my computer and the internet revealed that I might be able to solve my win32k.sys BSOD errors by changing my memory frequency from AUTO to SYNC. I note, with some concern, that while the motherboard manual lists SYNC as the default and best setting, it also claims I'll have the option to pick from specific settings -- which the actual BIOS doesn't bear out. The only two options in the actual setup are AUTO and SYNC, with AUTO being listed as the best choice. Well, what the hell, now I don't even know what I'm doing. The practical upshot is that my memory frequency has gone from 133 to 200. What THAT means, well, I'm not entirely certain, except that the memory has not yet melted or fried. Yet.
So I test this little tweak by hauling up RO and running it through its paces. Normally I can get about ten, twenty minutes out of the game before I get a win32k.sys BSOD out of it. I pushed it for about twenty today, post-change, and got: an IRQ_NOT_LESS_OR_EQUAL error instead.
Dammit.
Even more bizarrely, though I set Windows to automatically reboot on a stop error, I STILL got the BSOD and had to reboot. Which is okay, I guess, since I learned it was a different error.
Not sure what to make of this, I returned to the collective consciousness of the Internet and determined that this particular problem was frequently observed in more advanced GeForce chipsets (6's and higher, mine is a 440MX) due to the arrival of SP2 and its use of software DEP. Turning off the DEP supposedly resolves the problem. Supposedly the error was fixed in higher driver version for those chipsets -- but I note that my drivers don't actually go that high. My working speculation is that nVidia hasn't actually updated many of the driver functions for its older chipsets, even though they're officially supported, and thus I may be encountering the DEP problem as well. So the simplest thing to do is disable the DEP and see if it helps -- and what problems come out of THAT.
Anyone with actual, useful computer knowledge is free to tell me what the holy hell I did and am doing wrong. And anyone rich is welcome to buy me a graphics card for my birthday. Can I sell my novel now and have a free grand for a top of the line model?
So I test this little tweak by hauling up RO and running it through its paces. Normally I can get about ten, twenty minutes out of the game before I get a win32k.sys BSOD out of it. I pushed it for about twenty today, post-change, and got: an IRQ_NOT_LESS_OR_EQUAL error instead.
Dammit.
Even more bizarrely, though I set Windows to automatically reboot on a stop error, I STILL got the BSOD and had to reboot. Which is okay, I guess, since I learned it was a different error.
Not sure what to make of this, I returned to the collective consciousness of the Internet and determined that this particular problem was frequently observed in more advanced GeForce chipsets (6's and higher, mine is a 440MX) due to the arrival of SP2 and its use of software DEP. Turning off the DEP supposedly resolves the problem. Supposedly the error was fixed in higher driver version for those chipsets -- but I note that my drivers don't actually go that high. My working speculation is that nVidia hasn't actually updated many of the driver functions for its older chipsets, even though they're officially supported, and thus I may be encountering the DEP problem as well. So the simplest thing to do is disable the DEP and see if it helps -- and what problems come out of THAT.
Anyone with actual, useful computer knowledge is free to tell me what the holy hell I did and am doing wrong. And anyone rich is welcome to buy me a graphics card for my birthday. Can I sell my novel now and have a free grand for a top of the line model?
Leave a comment