Just happened again. Win32.sys is the cause of the error. ...I'm guessing there's not much I can do about that. :/ I guess it's just overheating. The position its in right now means it can't really get much air flow and I can't really change it. Oh well, things should start cooling down before long...
Now its really starting to act weird. Booted up my computer and switching to different Windows was slow or took multiple clicks. Restarted and it worked fine, until I got hit with a BSOD again. Same thing as before started happening. Restarted again and its working fine now...
Funny that you guys mention BSOD incidents. Ever since I applied a registry hack to Windows 7 so I could enable AHCI mode for my SSD without having to reinstall my OS, I get the BSOD whenever I boot my system. A memory dump is performed, and then the system is automatically rebooted. I never crash attempting to reboot, and I monitored the CPU and GPU temperatures, but nothing has ever overheated. I can only think of one surefire way to fix it- reinstall Windows 7, but what are the odds I'll ever get around to backing up everything and going through the trouble? No harm is being done, so why bother? I guess what I'm trying to ask is, could anything bad happen to my computer if I leave things the way they are? My error is also in Win32.sys if that helps. Also, this is my last trial post, and I wanted to post something in the "terrible Sonic jokes" topic, but I just have to share mine with all my chums here. "What did Robotnik say before he turned up his treadmill? TIME FOR A CHANGE OF PACE!" "What does Sonic say when he wants to buy steroids? "Gotta juice!"" "Did you hear about Robotnik's new Tex-Mex joint? He calls it the "Mean Bean Machine!"" "What did Sonic say after he ate there? "GOTTA GO FAST!""
Well, another YouTube video started and another BSOD. This time with atikmdag.sys being the error. Seems I was right about it maybe being connected to my Graphics Card as it seems just by searching for atikmdag.sys it's connected with BSODs and its a thing that happens with AMD graphics. Followed some instructions and messed with some System32 files!!! :DDDDDDDD Hope things work out. Rebooted and everything seems fine thus far.
