I'm back. No boot-loop has occurred. Startup was fairly normal, besides the new slowness described earlier.
Edit : Oddly, it seems that after cleaning out the registry with CCleaner and a reboot the system is behaving better again. I'm gonna run a game though, just to give it something more intensive to test. Will let you know if I run into issues.
Another crash. This is the first since removing IOCBIOS.
Also, the program ran normally this time. This should be a more proper file than the last, I think. The last one uploaded so fast it makes me suspicious that much was even in it.
Another BSOD. This time it didn't even display the blue screen. It just froze and looped sound like a BSOD would. No dump was made either. Seems the computer crashed without an actual BSOD this time.
Two more BSODs. Again, they're happening when running games. Here's some more data for you guys. Hope I'm not posting too much.
The only thing I see that's consistent is that it contains "ntoskrnl.exe" or "ntoskrnl.exe+ 74583" in it many times (though not every time). Please note that this has happened no matter how many times I start over with this computer, the error comes back. I have updated my WLAN drivers because that's what my manufacturer told me to do ages ago, but that did not fix the problem.
Happened to you? You mean you get the same problem playing Source games? Same BSOD errors? Just wondering if this is very relevant to what's happening to me O.o
If so, did you ever get them to stop?
Mostly just games in general myself. Not really so much just Source, it happens with other games sometimes too.
I know a lot of people that get random BSODs when playing games though. So annoying. I'm not really sure if there's a way to prevent those.
If there's ever been ONE thing I give console gaming over PC gaming, it's not having big errors like BSODs (though they have other errors, but they don't occur so often).
I'm not sure why, but it does sound like the Intel Tuning Utility was used to make some changes to possibly your fan speed, overclocking and other things, when all of that really should be done in the BIOS. As for the overclocking, you should reset those changes to factory default (if your BIOS gives you to the option to save, do so before changing) since overclocking can cause these kind of issues.
My concern right now is that despite Driver Verifier being on, there has been only one crashdump that has caught a potential suspect, and I'm not sure if it's related to our situation. Regardless, it was some old Logitech Wingman driver causing some problems (date on the driver is April 27, 2010). Try updating it or somethin.
The crashes you're experiencing are strangely consistent in some manner, which would suggest software, but the actual bugcheck types suggest hardware failure. I'm afraid we won't be able to garner the information we need to debug this any further, as it's a very elusive type of bugcheck. Because of that, it looks like we'll need to do some thorough diagnostic testing to kind of brute force an answer out.
My first recommendation outside of resetting your BIOS OC settings to default, is to first start testing with Memtest for about 7+ hours (so overnight). When that is done, you can then proceed to Prime95 for your CPU test. Start with an overnight Torture Test on Blend settings, then follow up with another one overnight with Large FFTs setting, even if the one on Blend happens to fail. Blend will help us discern if this is an issue with crosstalk between CPU and RAM, and Large FFTs will help us determine if it's corruption of CPU internals like registers and L caches. If Blend fails but Large FFT doesn't, it's the crosstalk, and if Blend succeeds but FFT fails it's the CPU internals.
Other misc. yet somewhat related tasks you can do is a CHKDSK to clean up any possible filesystem issues, and follow up with an SFC scan to check if Windows kernel is all clean on the disk end. It's best to do the CHKDSK first so that filesystem problems would be taken care of before dealing with the actual Windows files. Lastly, Seatools is suggested to ensure your drive is ok in the first place. You'll want to run all tests except Advanced.
That's all I can recommend at this point in time. I apologize for going this route, but it's only because there is really no other option I can see at the moment. Well, actually, there is one route, and there's a bit of work involved, but I'm curious about it so I'll take the plunge. I still recommend you start on these as I perform this one final task.
I remember doing CHKDSK a long time ago and that was fine. I'll try memory diagnostics overnight, along with all the other stuff.
As for resetting the OC via BIOS - Sorry to say this, but my BIOS options are very limited and nothing related to overclocking is even in there. It's just very basic stuff like the boot order and some hard drive options. Nothing much related to the CPU is in there.
Hmm... I'm going to remove this Logitech keyboard junk I have. It's the drivers for the G19 keyboard. Every time I install that, more BSODs than usual start coming up. I'm using the latest of the late, but they're still buggy.
What is ntoskrnl.exe anyway?
Quote