Hey to all,
I keep on getting a weird BSOD issue (124) whenever I'm doing anything with shaders. This issue also extends as far as using CE3, Unity or UDK when creating shaders.
I did a quick google with the ID number, but most of it seemed fluff, so I was wondering if anyone here might have experienced said issue based upon using graphical math tools only, and how did they fix it.
Cheers!
Replies
Cheers.
Laptop video drivers are such piles of shit lol so it just might be that unfortunately.
I hope I'm wrong. Anyway what I would do is change/reinstall the drivers (especially if you changed them before having this issue).
And, my bad for not reading the answers here, so ignore this.
Will try running a couple of tests, although I find it strange that this happens when I'm working specifically 'with' shaders and other nick-nacks, but if I 'play' a game, nothing happens for hours on end.
Cheers.
Yes over clockers use it but it can rule out any cpu & ram issues on standard systems. It can also be software related (people tend to disagree with me on this but one onOne plugin with PS has caused a bsod on a number of occasions) Test your ram with Memtest86+.
Good luck