Blue screen codes?

In all NT Kernel Windows versions, BSoD codes can be found in the Event Viewer.
Right-click My Computer > Manage > Event Viewer > This is where things differ |  In WinXP its under System | In Vista and Win7 its under Windows Logs > System

It should say STOP ERROR or something similar and have a white exclamation in a red circle with a priority of critical.

Please post the entire contents of the event.

~Fus

Ok, so I think i found a general set of "errors" in there.  this is what comes up:
Performance power management features on processor 1 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.
the only thing that varies in them is the # in "processor 1" (varies from 0-7 I believe.)
What's the cause of this? Thanks

owcraftsman

Is your memory rated to run at 1300 or above?
have you tried bumping vcore or CPU VTT
That usually fixes BSOD caused by unstable bios settings
IE: stop 0x00000101 or 0x00000124
also check your bios to see if you are close to the below settings
CPU PLL 1.8v
IOH 1.225           
IOH/ICH 1.6                      
ICH 1.15

the memory is rated to 1600 mhz, so that shouldnt be the issue. Ill check those settings as well and post back shortly

Try
1.26875 vcore
+125 VTT
1.8 PLL
CPU PLL 1.8v
IOH 1.225           
IOH/ICH 1.6                      
ICH 1.15

while we wait and see what Fiius has to say

Alright - BSoD code is 0x30 which is SET_OF_INVALID_CONTEXT.

Lets take a look at the BSoD Parameters;
Parameter 1 - New Stack Pointer location - 0xffffffffc0000005 - Hex address of 18,446,744,072,635,809,797 (18 exabytes, the limit of 64bit memory addressing)

Parameter 2 - Old Stack Pointer location - 0x0 - I'm not sure what would be a good value here, since I'm not a programmer, but given that this is the start of memory addresses and the 1st parameter is the end of the memory addresses, its not good.

Parameter 3 - Trap Frame Address - 0x0 - If I understand this correctly. when a processor gets an interrupt, it sticks the current instructions into a trap frame and works on the interrupt.  When its done with the interrupt, it reads the trap frame and starts where it left off at.

Parameter 4 - Reserved (0x0) - 0x0 - Expected value.

Another important key is up top of that BSoD entry -

<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />

  <EventID>41</EventID>

It means that whatever is just before the BSoD entry (~5 or so entry range) could be a contributing factor to why the computer BSoD'd.

Given the hex ranges and the BSoD code itself, you are looking at a driver or bit-flipping in RAM.  Perhaps try loosening the timings on your RAM or lowering the speed down 100MHz.  This, coupled with the slight voltage increase, should rule out or point out if its a RAM problem.
If you are still having problems after adjusting the RAM, we start on drivers next.

As for your general errors regarding performance power management features - it may be showing up if you disabled C1E SpeedStep or whatever Intel calls their power-saving settings in BIOS nowadays.  To make it go away, change your Power Profile from Balanced to Performance.

~Fus

Update: to sort of start off fresh, I set my entire bios configs back to default, so my system is no longer overclocked.  Problem is...my system keeps crashing! It'll say something about win32.sys (or sks I didn't catch it fast enough) and it'll blue screen and restart.  What could it be?

Ok, finally got it to show me the screen!
Here's the read out, word for word:
A problem has been detected and Windows has been shut down to prevent damage to your computer.  
If this is the first time you've seen this stop error screen, restart your computer.  If this screen appears again, follow these steps:
Disable or uninstall any anti-virous, disk defragmentation or backup utilities.  Check your hard drive configuration, and check for any updated drives.  Run chkdsk /F to check for hard drive corruption, and then restart your computer.
 
Technical information:
*** STOP: 0x00000024 (0x00000000001904FB, 0xFFFFF8800E861848, 0XFFFFF8800E8610B0, 0XFFFFF88001424A30)
 
***    ntfs.sys-ADdress FFFFF88001424A30 base at FFFFF880014160000, DateStamp 4a5bc14f
 
did a crash dump blah blah blah
 
What gives?I know my "F:" drive is a daemon tools drive, but i cant figure out what the problem is

So I tried this...Im still getting error codes.  At this point Im ready to just do a clean wipe/install on my computer.  Any other suggestions?

Here is a thought ......  Something to noodle on....
If your speedstep is disabled and the power manamgment kicks wouldn't it also have to manipulate ram speeds as well .   If you had overclocked to the limits of your ram , and power managment tries to kick down cpu and ram might it cause the same Blue screen issues.  
Given some of the stop screen and BSOD errors pointed out.  It may be contributing.  Maybe some one here knows a little bit more on how  power managment changes CPU power and wether it manipulates ram speeds and timmings.   
 
Also I have set my system to max perfomrmance and I can not stop the event log errors  however I am not overclocked.
 
Phil

yep let us know