Googled stuff up. Found nothing. Never had issues before installing 4.1
I have a i7-950 @4Ghz, 12 GB RAM. 128GB SSD with 1.5TB Back-up HDD. I have a second set of 12 GB's that I swapped out and both sets had same issue.
Reinstalled.. works fine now (not installed LR4.1 yet... I am too scared): I say fine... but sometimes I will get BSOD's while the system is trying to sleep... which might be a driver issue, but before after 10 minutes of booting regardless of what i was doing, it would BSOD after every 10 minutes of logging into Win 7 Ultimate x64bit.
Again it could be just my system.
What does your event log say - what BSOD do you get? And have you always had this with the O/C CPU? Have you tried with the system running without any O/C - would assume you have since you seem to be able to reproduce the issue fairly consistently.. ? Not saying I can help, but always willing :-)
Thanks. I have run the cpu at 4.3Ghz at 1.26v without issues. It's water cooled.
But at the time of BSOD's, I had it clocked down to 4, then stock 3.06, even tried 2.8 and 2.66Ghz... same issue. Perhaps it could have been a SSD filled up issue... but I doubt it since it showed 40GB free bfore Win 7 reintsall. NOw it is back up at 4Ghz, no problems, re-installed. I guess I will try 4.1 again ... soon :-)
The funny thing is, when it BSoD's, it always did it 10 minutes after boot up, whether I was logged on Windows, active or inactive or even not logged on... it would just BSOD and restart... Every effin 10 minutes.
Disk space is unlikely to cause BSOD, SSD firmware has however been known to cause this esp. on OCZ SSDs. As you say if it does not reappear since the re-install, even with O/C then all is good. The fact that it occurred at login means that it is unlikely to be app related as no user context exists at this stage, so unless the app has installed system-level drivers (e.g. AV, FW), then it is most likely not that causing the issue, again eliminating LR as the culprit
Alas the reinstall also means we can't see inside the eventlog, which is of course where you want to look. If it does re-occur, would be good to know what the BSOD code / event id was as this often helps eliminate / narrow down the causes....
Finally, if it comes back with LR 4.x it would point more towards some issue with your graphics card / drivers, but was not aware of LR doing any system-level hooks - it just talks direct to your Gfx card. Again, eventlog with BSOD code should help confirm this.