PC blue screening when playing Witcher 2

[Fenon]

I've had blue screens frequenty while playing the Witcher 2. I hope this is the right place to put this, sorry if it's not.

I have a GTX 570, 6gb ram, i7 950 over clocked to 4.2ghz and the os is windows 7 64 bit.

I had the 3d vision drivers problem so I uninstalled them, I also installed the beta Nvidia drivers which were supposed to help with the problem of really back performance in buildings, and it did help to some degree, anyway I wasn't really happy with the drivers, didn't feel it was stable so I rolled back to the last driver which was 270.61 I think and uninstalled the 3d vision drivers.

Anyway from the point I started messing around I've been getting blue screens every now and then when playing the game, and once when I had just finished playing the game and all I had up was the launcher.

Anyway I wrote down the I think it was crash info numbers etc (sorry don't know much about this) I didn't count the number of 0's in the long strand:

***STOP: 0x0000000000101


I have had blue screens in Minecraft but not for a long time, other people had the blue screen as well, so I think it was a bug in Minecraft that was fixed and I've had them in Mass Effect but again I've seen reports of blue screens saying that it's because ME doesn't work well with newer drivers. I've not really seen any blue screen reports for the Witcher 2.

[Top-Tier-Tech]

Bad performance and BSODs are common for new PC game releases. That's why I usually just wait to play new games after a certified driver comes out post-game release. More than likely you're just gonna have to deal with it if you choose to play now.

Try disabling extra graphic effects and just stick with basic low settings, might help.

[Fenon]

Someone suggested that it might be because I had the texture size at very large but I reduced it to medium and it was still blue screening.

[Top-Tier-Tech]

Until a new driver set came out post-release of Dragon Age 2 I couldn't enable high-resolution textures on that game nor full DX11 features. Just set every setting as low as possible then start increasing things, if you start BSing again then back off on the settings.

[Fenon]

Problem with that is it's not a regular thing I could be playing for 3 hours and nothing happens, it might be over a day, I usually think that I've fixed it because it's not blue screened for a day and then an hour later it happens.

[Top-Tier-Tech]

Oh, well that's not bad then I'd just be sure to save frequently and call it good. Or wait till a new driver set is released...

[Bolkonsky]

Try forcing lowest setting in the control panel, make sure HDR and AA are not on at the same time, that could be a potential problem. Also, if it happens again, re-write the hex stop error, because I can't find anything on that one.

[Fenon]

Ok thanks I'll wait and see if it blue screens again, then I'll write down the code properly and I'll try turning the AA off.

[Devilmaypoop]

Your OC might be unstable. How long did you test it and what program did you use to do so?

[Crazyeyesreaper]

yea id guess unstable overclock as well

I can run 4.1-4.2ghz and pass LinX, OCCT, Prime 95, IBT, etc etc but soon as i start Battlefield Bad Company 2 my system will hardlock 5 mins in, back the overclock down to 4ghz and all is peachy again,

[Fenon]

I didn't overclock it, I bought it pre-overclocked from Overclockers.co.uk. I know nothing about overclocking and didn't want to even attempt it. I haven't even tried to overclock my graphics card, which to me looks like the easier of the two to overclock.