Alright, so I decided I'd try out my mobo's (ASRock z68 extreme3 gen3) advanced turbo 50 feature. All was good, it definitely worked, except I have my stock cooler and I knew it wouldn't stay very cool. It started getting too warm (80-90c) so I shutdown and turned it off. Everything should've been back to normal. Nope. After I logged back into windows the bsods came.
They come at any random time from when it says Windows is Starting, and about 1-2 minutes at my desktop after I've logged in. It used to be always before the login screen but now I'm getting to the login screen at least.
Things I've tried:
-Unplugging all non essentials
-Reseating all hardware
-reseated CPU and fan as well
-Safe mode (this seemed to last longest before bsod came)
Anything I try I can't get anywhere due to the bsods. Is it possible my CPU is overheating? I can't get a read on its temps.. The bsods always come before I can run a program. It's showing aboGut 45c in the bios, slowly climbing (.5C/2-3 seconds)
My phone won't let me scroll back up to edit what I wrote but I just got my desktop all the way loaded and coretemp started. It showed all cores at 30-40c. So it can't be overheating. It bsod'ed again just after I saw it.
Anyone have any other ways I could go about testing my issue here? Of could someone possibly have any sort of solution here?
Another update... While I was in safe mode I went to msconfig and changed the startup to "diagnostic startup" and started my computer normally, and everything is working fine with just the bare essentials loaded. So would this mean I have a driver issue somewhere?
It could be a drive issue but what would really help is if you can provide the information from the BSOD. We will need the information from the blue screen and there may even be a crash dump created that would help.
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8008b47028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
Its a driver issue, have you installed any new hardware or updated any drivers recentely?
Go back in to safe mode and disable all start up services. then reboot into normal windows and then add them back in one at a time. restart after adding in every service.
When the PC bluescreens you will then know what is causing the problem as it will be the last service you have re added
While in safe mode you can try disabling some things from start up. Go to run and type msconfig and under start up remove the check mark from items you don't want to load and eventually you may find the driver that's causing the problem.
Thank you very much guys... it appears the problem was coming from 2 intel processes - hkcmd.exe and igfxtray.exe
All appears to be well now! Only I'm having troubles getting my aero themes to work again. They're all grayed out and I can't select them. Is there a process I need to be running to allow them to be selected?
Its because those two processes are the part of the graphics driver package.
Best bet is note the display driver name leave them disabled and then uninstall and remove the display driver via device manager and get the most up to date drivers from Intel's website.
Veyr true, infact you may be able to get away with just going into device manager and right clicking on the display adapter and clicking properties, then in the window that pops up click the driver tab and click roll back driver, enable the startup service and see if that works!
Turns out it wasn't driver issues at all, even though all that seemed to prolong the bsods. gamerk316 was right, it had to deal with OCing. Thing is though, it was being caused by Intel's Turbo Boost, which had been enabled by default since I first got this build about 6 months ago. I guess enabling ASRock's Advanced Turbo 50 goofed something with it, even though I disabled it soon after enabling it.
But all is well, and thanks for all the help! I came that close to wiping my hard drive and doing a fresh install of windows... Good thing I stuck it out!