So, my computer is newish, around 3 months old, sadly store bought but I had no choice in the matter this time, won't go into depth as to why, I'm just throwing it out there because yes, I know, I should build my own. I have done for 16 years now so I am quite capable. regardless, it was from PC world (Evil store) i5-2320 3gig quad core. AMD HD 6670 8GB RAM Windows 7. Clean installation. ALL drivers up to date. Every single one except for the bios (which may or may not be ) No viruses. Norton 360 firewall/AV (Yes yes, they aren't nearly as much of a CPU hog as some years ago. I like it) CCleaner run often. Windows update run 2-3 times per week. Nothing really on the hard drive except for Steam and a steam games (PS2 is Steam bought) Core temps at around 39-41 idle. IIRC around 55 on high load. GPU temp 40 idle. 55-60 full load. tried with GPU CCC panel sliders maxed out, after the blue screens dropped them back down to stock to see. Otherwise, nothing overclocked. Originally only ever had this BSOD in PS2. One time not that long ago had it in some other game. PS2 Seems to kick it off far more than any other though. It would happen once every couple of weeks. Stopped for a week or two, started up again a few weeks ago and now it's done it 3 times in the last few days. Twice today within an hour of each other. It's freezing cold outside and inside, and temps seem pretty stable anyway. Upon checking the stop code, Microsoft put it down to drivers http://answers.microsoft.com/en-us/...00000101/7225385d-515a-e011-8dfc-68b599b31bf5 Most other sites put it down to Vcore. Since it's NOT overclocked, and apparently it can happen more and more over time, and that this is a new computer (might not be good, but it's new!) it's pissing me off. Makes me regret buying it even more, but again, no choice. Nor do I think I can take back a computer for BSOD...so it feels like I am just sitting and waiting. If I do change the Vcore, then that basically screws me over if it goes wrong I think, and they'd blame it on me. Does anyone have any experience with this specific BSOD? Any suggestions other than raising Vcore? Really starting to bug me now.