Freezing/BSOD Randomly, Different Error Codes

[essenbe]

The case specs show it as being 8.1" wide. The 212 I believe is 6" tall, and should fit (just a guess). But, if you bought a K series CPU and a Z77 board, it appears you intend on overclocking. If that is the case, you will need something much better than the stock cooler. That being said, the stock cooler should be doing a better job than the temps I saw, unless you are overclocked now. Whatever you decide to use, I would also invest in additional case fans. Decent case fans are pretty cheap, and will add fresh, cooler air to whatever cooler you use. But, if the 212 will fit, it is the best cooler you can use in it's price range. There are better coolers, but at a much higher price. And unless you plan on very high overclocks, the 212 will do the job. Most any decent aftermarket cooler will be better and quieter than the stock Intel cooler.

Whichever cooler you choose, make sure it will fit over your ram.

 

[Britton30]

I think the Hyper EVO should fit your case. The cooler is 6.25" tall and subtracting 1" to allow for the space from the side panel and board stand offs you still have about 3/4" to play with. You can measure from the top of your CPU to the side panel to make sure.

If you get the Hyper EVO I would recommend getting 2 PWM fans for it and another 120MM fan for your side panel to bring in cool air if space allows.
Newegg.com - Computer Parts, PC Components, Laptop Computers, LED LCD TV, Digital Cameras and more!

 

[DeathPhage]

Okay I was going between the EVO and this Newegg.com - COOLER MASTER Seidon 120M RL-S12M-24PK-R1 Water Cooler any thoughts on water cooling vs. air?

I have 3 case fans, two in front and one on top. Since my mobo only has 4 fans slots (1 CPU, 3 case fans) I won't be able to attach any more fans unless there's a way to multiple the plugs.

 

[Britton30]

I personally don't think water belongs inside a PC, but many people here use the closed loop systems or have built their own.

Some fans come with an adapter so it will plug into a Molex (large 4 pin) connector. There are splitters to run two fans from one fan header but they may cause too much current draw from it.

 

[DeathPhage]

Newest BSOD Report.

 

[Vir Gnarus]

I'm not sure what you had to go through previously, but from the first crash to the last it does seem to be very consistent, with WHEA errors reported by your CPU that it has suffered an internal timer error. There's the offchance that the BIOS or motherboard software can cause this. Update the BIOS if you haven't already, update all your mobo drivers, and uninstall all software that came with your motherboard. This includes 'enhancement' software, OC/tuning utilities, monitoring utilities, etc. Anything that does not involve getting your components on your mobo to work should be eliminated. You may need Driver Sweeper (a free app) to take care of that completely. Also, your last option is to reset BIOS settings to Safe/Normal defaults to ensure you don't have BIOS settings inadvertently OCing your system.

If none of that appears to work, then you have a bad CPU. Best replace the fella.

Analysts:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800f766028, be000000, 800400}

*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : GenuineIntel

Followup: MachineOwner
---------

1: kd> !errrec fffffa800f766028
===============================================================================
Common Platform Error Record @ fffffa800f766028
-------------------------------------------------------------------------------
Record Id     : 01cdb9e56e7f3463
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 11/4/2012 23:21:51 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800f7660a8
Section       @ fffffa800f766180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : [COLOR=Red]Micro-Architectural Error[/COLOR]
Flags         : 0x00
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800f7660f0
Section       @ fffffa800f766240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : a9 06 03 00 00 08 10 02 - bf e3 9a 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800f766240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800f766138
Section       @ fffffa800f7662c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=Red]Internal timer[/COLOR] (Proc 1 Bank 3)
  Status      : 0xbe00000000800400
  Address     : 0x0000388005069c61
  Misc.       : 0x000000000003ffff

 

[DeathPhage]

I updated my BIOS, it still froze on me. I just uninstalled the software that came with the Mobo so I'll try that and hopefully that works. If not I guess I'll get in touch with intel if you think it's a CPU problem rather than a GPU problem.

 

[Vir Gnarus]

Again, you'll wanna confirm the software is completely uninstalled using Driver Sweeper. Mobo software uninstallers are often broken and leave behind the actual drivers, which ends up still getting loaded at Windows startup and still bugging things out. You can also confirm they're gone by eyeballing the drivers that load at startup with Autoruns. Unchecking an entry will disable that entry, and deleting it will, well, delete it. Check drivers and services list.

 

[DeathPhage]

Okay Driver Sweeper shows that there are no Drivers installed and I got rid of all of the Autoruns on my motherboard.

 

[Vir Gnarus]

Unless you bought the CPU straight from Intel, btw, I'm not sure they'll be able to help you as you are an end user. You may have better chances getting a replacement via the vendor that you used to purchase it. Has the system been unstable since you removed the mobo software?

 

[DeathPhage]

Well it's hard to tell since the sytem freezes randomly so it could happen an hour from now or as long as 3 days from now. That's the thing that makes fixing this so tough is that it can't really be replicated.

 

[Vir Gnarus]

Mmk, it's best to wait a bit to be certain if removing the mobo stuff fixed things up. We'll see how that goes, and if it goes unstable again, it's time to whip out the warranty (if it still is active).

 

[DeathPhage]

After uninstalling the Mobo software my computer has run for over 2 days two different times! So I'm guessing this bascially means that I can't use my Mobo software correct? or is there a way to remedy this?

Thanks for the help in solving the problem!

 

[DeathPhage]

And a couple hours after I post that it freezes. I'm hoping that one was just a fluke.

 

[Vir Gnarus]

I'm feeling that it may not be, and that we really do have a hardware issue (though I wouldn't doubt the mobo software helped make it worse!). If you wish you can wait it out if it happens again. But it sounds like you may need to get ready to start swappin hardware. I'd pick the mobo first, then the CPU. The PSU can also be potential cause, so don't neglect that.

And yes, it's never good to have software that comes with mobos installed.

 

[DeathPhage]

Well I just replaced the PSU so I'm hoping that's not the issue. I'll start with the mobo and see if I can get that RMA under warranty and go from there.