Back again! Still BSOD and crashing issues

fuller10e · Jan 31, 2013

I posted about the issue before, but the it hasn't gone away after initially thinking the problem was resolved. So I generated a new report, though the perfmon /report fails to execute everytime, included is the one back in December.

Here are my specs:

IOS: Win7 x86
Processor Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz, 3068 Mhz
JetWay JBI-600-LF LGA 1366 Intel X58 ATX Intel Motherboard
WD 250GB HDD 7200RPM
EVGA GeForce GTX 560 Ti (Fermi) 2GB 256-bit

PSU RAIDMAX HYBRID 2 530W

This is a custom home build, again, the issue started when I upgraded to windows 8, so I went back to 7 and the problem carried over. The graphics card, RAM and HDD have all been replaced after the problem started.

View attachment Windows7_Vista_jcgriff2.zip

GZ · Jan 31, 2013

Hello fuller10e,

Could you provide us with a Speccy report as well?

Speccy - System Information - Free Download

Install the program and run it, then "Publish" the system snapshot, you can paste the URL in your next reply.

Thank you,

GZ

fuller10e · Jan 31, 2013

http://speccy.piriform.com/results/BxdajzqsRoDomn51c2svRcW

There you are

GZ · Jan 31, 2013

Thank you for that.

I have scanned the report (I'm at work, so it will take some time to get through it thoroughly) and only one thing jumps out at me right now... your CPU temp is being reported at 59°, and althought this is in the acceptable range, it is still a little high. Were you playing games or performing a CPU intensive task before taking the system snapshot?

I am adding a link to your previous thread for quick reference.

https://www.sysnative.com/forums/bs...-receieved-secondary-processor.html#post34319

fuller10e · Jan 31, 2013

Yes, I was playing Skyrim at the time it shut down so the heat from the GPU was up there.

However, even though while playing games like that randomly will shut it down or BSOD, at the start of the problem I wasn't doing much gaming and I'll still get BSOD errors when doing almost nothing.

GZ · Jan 31, 2013

I would like you to download HWMonitor (CPUID - System & hardware benchmark, monitoring, reporting) and install it... Just let it run in the background for a little while, while you do normal tasks... After about an hour of monitoring, please take a screenshot and post it in a reply.

If you need help with a screenshot, just ask.

fuller10e · Jan 31, 2013

http://i.imgur.com/DxWTo2u.jpg

GZ · Jan 31, 2013

I can barely make out the values in that screenshot... But your CPU temps look extremely high. High values in the mid 70s.

What is your PC's cooling setup?

fuller10e · Jan 31, 2013

I apologize for that. If you have a scroll wheel on your mouse, hold in control and you can zoom in with it. I've a couple stock fans in my case and the stock heat sink with fan for the CPU, that I've already planned on changing soon with an after market and new paste. Though will that cause a BSOD? Before the message was clock interrupt not received and now its that plus the occasional hardware failure and... I can't remember the next. I've always been under the assumption that overheating would just cause an immediate crash, not BSOD

GZ · Jan 31, 2013

Overheating can cause all sorts of issues. When a CPU gets hot, it will usually clock down, a CPU can malfunction at high temperatures... It's almost like the engine in your car running rough when it overheats... I am not saying that it is the sole issue you have, but I am saying that it is definitely a large contributor. Heat is the number one killer of electronics.

A related question... What is the temperature of the room that your computer is in, and what case (enclosure) are you using?

fuller10e · Jan 31, 2013

It could definitely be a factor, not ruling that out. But the temps are probably higher now since the new GPU, but the issue did start with the original. Though it has been a while since I cleaned out the dust. New thermal paste might help a tiny bit. Win8 killed something and after all the driver updates, something just isn't clicking. When I did think it could have been a hardware issue, I bought a new HDD, RAM and GPU. Next thing I can think of is the CPU or MOBO but I don't think its either? I just can't think of what Win8 did to screw it up.

My room is fairly cool. Gotta say around 70. Probably lower. This is my case.
Newegg.com - Rosewill R519-BK Black ATX Mid Tower Computer Case w/ 500W Power Supply

The power supply detail is inaccurate, I replaced it with the one I stated earlier.

GZ · Jan 31, 2013

That case has only two exhaust fans... The PSU and the 92mm rear fan... I am not a big fan of that, especially running a video card...

The rear fan is oriented to blow out, correct?

Also, is the plastic duct still in place on the side of the case, if so, does it center (give or take) over the CPU?

My wife's PC case employs a similar design... She is running a much hotter (125W TDP) AMD Phenom II CPU, with a Geforce GT260, and her temps never break 50°.

Would you be willing to remove your GPU temporarily and run off the CPU Video for an hour or so to compare CPU temperatures?

And as for Windows 8, I don't see how it could have mucked things up. When you reverted to Windows 7, was it a clean install or a restore from saved image?

fuller10e · Jan 31, 2013

Agreed I'm not a fan of my case either, but it was cheap for my initial build that I've slowly been improving. Case and Heatsinks have been on my to-do list.

Yes, it blows out, the duct is directly centered over the CPU, though I've always thought that it really restricted temp flow.

Yes, I'll be sure to do that starting in the morning though the temp surrounding the card is very cool. Near the processor is where the most noticeable heat source is, obviously.

I didn't understand it either, but as soon as win8 was installed, I've had constant BSOD issues. Before that in the 3 years I've built it everything ran like day 1. Win7 was a clean install, both on the original HDD and the one I replaced it with.

GZ · Jan 31, 2013

fuller10e said:
Agreed I'm not a fan of my case either, but it was cheap for my initial build that I've slowly been improving. Case and Heatsinks have been on my to-do list.
.

To be honest, your case should be fine to keep your CPU cool. Even though you are using a pretty powerful i7 CPU, the TDP (Thermal Design Point) is quite low... Energy efficiency has it's rewards. Your idle temps should be in the 25 to 35 range and you shouldn't see 70s during normal use...

fuller10e said:
Yes, it blows out, the duct is directly centered over the CPU, though I've always thought that it really restricted temp flow.
.

The reason for the duct is so that the CPU fan can draw cool air from outside the case, rather than the warm air inside the case. It has been employed for many years to lower CPU temperatures in compact cases, and usually works quite well.

fuller10e said:
Yes, I'll be sure to do that starting in the morning though the temp surrounding the card is very cool. Near the processor is where the most noticeable heat source is, obviously.
.

Thank You. By removing the GPU, you are taking the biggest heat maker in the case out. This will rule it out as the cause for your high CPU temps.

fuller10e said:
I didn't understand it either, but as soon as win8 was installed, I've had constant BSOD issues. Before that in the 3 years I've built it everything ran like day 1. Win7 was a clean install, both on the original HDD and the one I replaced it with.

This is what mostly makes me think hardware. The OS should not BSOD out of the box (in a fresh install). Every single time I have had this happen, it was due to a hardware issue.

As of right now, I see one major problem that needs to be resolved before we move on, and that is your temperature issue.

fuller10e · Feb 1, 2013

I removed the GPU and heat stayed more or less the same. As I said before, feeling around all parts of the computer, the only change in temperature I can feel is around the CPU. GPU, RAM, HDD and PSU all seem to be pretty cool. There is a noticeable temp difference surrounding the CPU. I won't be able to actually change out my computer's cooling systems until mid this month, tax returns and stuff. I am leaning towards it being a hardware issue, as you said, especially when my BSOD error messages are always either "Unknown Hardware Error" or "Clock interrupt was not received on a secondary processor"

Though I'd like to share that I just got a BSOD, temps were at 40C. I was just watching youtube about the cooling system, error was the secondary processor.

This is what I'm more than likely just going to suck up and buy today. Thoughts?

Newegg.com - CORSAIR Hydro Series H100 (CWCH100) Extreme Performance Liquid CPU Cooler

Newegg.com - Corsair Carbide Series 400R Graphite grey and black Steel / Plastic ATX Mid Tower Gaming Case

jcgriff2 · Feb 1, 2013

Hi -

Windows 7 was installed on 11 November 2012 - the very same day the 1st BSOD occurred.

31 BSOD dumps total; 5 of the 31 were corrupted, i.e., Windows was unable to write the dump file.

The very 1st BSOD had bugcheck = 0x124 = WHEA = Windows Hardware Error Architecture. WHEA is a Machine Check Exception.

The WHEA record does not offer much as it is incomplete/ invalid -

Code:

0: kd> !errrec fffffa80068d7028
===============================================================================
Common Platform Error Record @ fffffa80068d7028
-------------------------------------------------------------------------------
Signature     : *** INVALID ***
Revision      : 0.0
Record Id     : 0000000000000000
Severity      : Recoverable (0)
Length        : 0
Creator       : {00000100-000f-0000-3600-000000000000}
Notify Type   : {00000100-000f-0000-3600-000000000000}
Flags         : 0x00000000

Interestingly, the 2nd BSOD occurred 2 days later and had a bugcheck = 0x9c = Machine Check Exception

0x9c was supposedly retired in XP & replaced by 0x124 in Vista. I have seen 0x9c bugchecks before in Vista and W7. Rare, but not unheard of.

The 0x9c BSOD was hardware failure, but mentioned the Windows processor driver intelppm.sys

Read More:

http://www.sysnative.com/drivers/driver.php?id=intelppm.sys

Another bugcheck that appears = 0x101 = CPU hang

Read More:

Code:


BugCheck 124, {0, fffffa8008142028, b2000000, 5}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa800813f028, b2000000, 5}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa8008201028, b2000000, 4008f}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa800cac1028, b2000000, 5}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa800c9e3028, fa000000, 400405}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 9C, {0, fffff880030ffc70, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa80068ef028, fa000000, 400405}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa800691f038, 0, 0}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa80064f48f8, 0, 0}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880032a4180, 5}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa80069d7028, fa000000, 400405}
Probably caused by : Unknown_Image
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880030a4180, 5}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa80068d2028, be000000, 800136}
Probably caused by : Unknown_Image
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa8006997028, fa000000, 400405}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa80068d6028, ba000000, 400405}
Probably caused by : Unknown_Image
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880009b2180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880030a4180, 5}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa8006955028, fa000000, 400405}
Probably caused by : Unknown_Image
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 101, {18, 0, fffff880030a4180, 5}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 9C, {0, fffff8800318ec70, 0, 0}
Probably caused by : intelppm.sys ( intelppm!MWaitIdle+19 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, fffffa80068d7028, be000000, 800152}
Probably caused by : Unknown_Image
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Unknown_Image should not be found in dumps. It should be a driver name.

You have experienced unknown hardware failure since Windows installation on 11 Nov 12.

Are your 2x4 GB RAM sticks matched?

GZ is the hardware expert here. I sit on the software side of the fence; unfortunately, there is not much more I can offer here outside of running the dumps.

Regards. . .

jcgriff2

BSOD SUMMARY

Code:


Debug session time: Mon Jan 28 11:14:28.338 2013 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\012813-17265-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:49:18.651
Probably caused by : hardware
BugCheck 124, {0, fffffa8008142028, b2000000, 5}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8008142028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000005, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Jan 28 10:24:02.621 2013 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\012813-34296-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:37:41.808
Probably caused by : hardware
BugCheck 124, {0, fffffa800813f028, b2000000, 5}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800813f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000005, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Jan 26 10:48:38.438 2013 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\012613-19718-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 2:56:40.625
Probably caused by : hardware
BugCheck 124, {0, fffffa8008201028, b2000000, 4008f}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8008201028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000004008f, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_MEMORY__UNKNOWN
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Jan 20 11:05:57.568 2013 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\012013-38671-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 14:06:05.833
Probably caused by : hardware
BugCheck 124, {0, fffffa800cac1028, b2000000, 5}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800cac1028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000005, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Jan 18 16:27:38.665 2013 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\011813-38031-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 4:06:32.805
Probably caused by : hardware
BugCheck 124, {0, fffffa800c9e3028, fa000000, 400405}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800c9e3028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Jan 17 17:16:44.641 2013 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\011713-36609-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 3:04:48.829
Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )
BugCheck 9C, {0, fffff880030ffc70, 0, 0}
BugCheck Info: MACHINE_CHECK_EXCEPTION (9c)
Bugcheck code 0000009C
Arguments: 
Arg1: 0000000000000000
Arg2: fffff880030ffc70
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x9C_GenuineIntel
PROCESS_NAME:  TESV.exe
FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Jan  8 12:23:15.984 2013 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\010813-27203-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:19:12.953
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880009b2180, 4}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Jan  2 19:26:04.408 2013 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\010213-36250-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:25:22.486
Probably caused by : hardware
BugCheck 124, {0, fffffa80068ef028, fa000000, 400405}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80068ef028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Dec 23 22:25:07.578 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\122312-33718-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:00:08.531
Probably caused by : hardware
BugCheck 124, {0, fffffa800691f038, 0, 0}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800691f038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Dec 21 22:53:20.203 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\122112-36640-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:00:08.156
Probably caused by : hardware
BugCheck 124, {0, fffffa80064f48f8, 0, 0}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80064f48f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Dec 17 11:37:04.359 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\121712-33109-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 3:33:55.312
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880032a4180, 5}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880032a4180, The PRCB address of the hung processor.
Arg4: 0000000000000005, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Dec 14 15:41:53.984 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\121412-34937-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 5:06:18.937
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880009b2180, 4}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Dec 10 12:35:35.984 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\121012-33109-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:48:54.937
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880009b2180, 4}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Dec  6 15:39:30.060 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\120612-33062-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_fa800792`0f9004c0
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fa800792`0f9004c0
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 1:01:03.013
*** WARNING: Unable to verify timestamp for Unknown_Module_fa800792`0f9004c0
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fa800792`0f9004c0
Probably caused by : Unknown_Image
BugCheck 124, {0, fffffa80069d7028, fa000000, 400405}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80069d7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Dec  3 13:14:39.984 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\120312-16828-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:01:36.937
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880009b2180, 4}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Dec  3 13:11:22.984 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\120312-34687-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 1:47:12.937
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880009b2180, 4}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Nov 30 13:28:26.968 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\113012-24531-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:28:30.062
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880009b2180, 4}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Nov 28 02:34:47.984 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\112812-35687-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:22:24.937
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880009b2180, 4}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Nov 28 00:43:49.984 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\112812-34531-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:18:06.937
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880009b2180, 4}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Nov 28 00:24:11.984 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\112812-38375-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 3:18:18.937
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880009b2180, 4}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  browsemngr.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Nov 26 12:39:26.968 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\112612-15015-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:33:30.937
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880009b2180, 4}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Nov 24 12:37:52.343 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\112412-16421-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 1:33:49.312
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880030a4180, 5}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880030a4180, The PRCB address of the hung processor.
Arg4: 0000000000000005, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Nov 17 14:29:05.100 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111712-15234-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_fffff680`00032728
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffff680`00032728
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:08:55.053
*** WARNING: Unable to verify timestamp for Unknown_Module_fffff680`00032728
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffff680`00032728
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image
BugCheck 124, {0, fffffa80068d2028, be000000, 800136}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80068d2028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800136, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Nov 17 01:21:32.159 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111712-14671-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:33:18.112
Probably caused by : hardware
BugCheck 124, {0, fffffa8006997028, fa000000, 400405}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8006997028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  wmplayer.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Nov 17 00:02:26.445 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111712-33375-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:30:14.398
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image
BugCheck 124, {0, fffffa80068d6028, ba000000, 400405}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80068d6028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Nov 16 23:22:34.984 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111612-19468-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:07:12.937
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880009b2180, 4}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Nov 16 12:32:38.359 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111612-35437-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:02:16.312
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880030a4180, 5}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880030a4180, The PRCB address of the hung processor.
Arg4: 0000000000000005, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Nov 16 12:08:42.353 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111612-34984-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:31:59.306
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image
BugCheck 124, {0, fffffa8006955028, fa000000, 400405}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8006955028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Nov 16 11:35:14.359 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111612-38640-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 12:51:40.328
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, fffff880030a4180, 5}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Bugcheck code 00000101
Arguments: 
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880030a4180, The PRCB address of the hung processor.
Arg4: 0000000000000005, 0.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  wmplayer.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Nov 13 21:58:21.857 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111312-21750-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 6:52:57.810
Probably caused by : intelppm.sys ( intelppm!MWaitIdle+19 )
BugCheck 9C, {0, fffff8800318ec70, 0, 0}
BugCheck Info: MACHINE_CHECK_EXCEPTION (9c)
Bugcheck code 0000009C
Arguments: 
Arg1: 0000000000000000
Arg2: fffff8800318ec70
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x9C_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm!MWaitIdle+19
MaxSpeed:     3070
CurrentSpeed: 3059
BiosVersion = 080015 
BiosReleaseDate = 08/26/2009
SystemManufacturer = Intel
SystemProductName = Thurley
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Nov 11 23:57:17.154 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111112-16421-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:22:21.107
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image
BugCheck 124, {0, fffffa80068d7028, be000000, 800152}
BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80068d7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800152, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

         
       J. C. Griffith, Microsoft MVP (jcgriff2)   
             
           http://mvp.microsoft.com/profiles/Griffithhttps://mvp.support.microsoft.com/profile/Griffith   

           https://www.sysnative.comwww.sysnative.com
             
           http://jcgriff2.comwww.jcgriff2.com 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

fuller10e · Feb 2, 2013

Forgive me for not knowing but what do you mean by 'are your RAM sticks matched?'

Keep in mind, however, all this started when Win8 was installed. The date you are seeing is after reinstalling win7 on the original HDD on which the BSOD first occurred. That date, November 2012, is probably displaying when I installed the new HDD and tried again a fresh Win7 install.

By the way I should mention my appreciation for your efforts with this issue. All suggestions and time spent on helping me with this is invaluable to me. Thanks.

GZ · Feb 3, 2013

Thank you John.

To the issue... As I suspected, the dumps are pointing at hardware.

Since the Windows 7 is a "Clean Install" You can rule out Windows 8 having anything to do with the BSODs you are having in Windows 7.

All the dumps are pointing to the processor, which we know has a heat problem. And since you removed the GPU from the equation, we know it isn't being caused by excess heat from your video card.

Right now, what we need to do is get those temperatures down. Do you know how to properly clean and reapply thermal compound to the heatsink and CPU?

fuller10e · Feb 3, 2013

yes I actually got myself the corsair carbine 400r case with 2 front 120mm fans and 1 rear exhaust 120mm fan. Reapplied the compound, temperatures are rarely every breaking 50 even with games. Tried to get myself a new heatsink but the screws don't show correctly behind the case so I can't do that. Though my case is designed for the h100 water cooling so if need be, there's that.

I heard something interesting though. Even though win7 was a clean install, when you install win8 it encrypts itself in the mobo bios which could be where the issue is coming from? Anyone hear of this?

GZ · Feb 3, 2013

I believe you are thinking about OEM Preinstalled activation. Retail versions of Windows will not make any changes to system firmware. In OEM Preinstallation, the manufacturer is required to include special information in the system firmware. This does not affect retail installations. Could you provide a link to the article or post that you read that contains that information?

Since you installed the system in a new case and your temperatures have dropped, how is your system stability?

Back again! Still BSOD and crashing issues

Member

Visiting Expert

Member

Visiting Expert

Member

Visiting Expert

Member

Visiting Expert

Member

Visiting Expert

Member

Visiting Expert

Member

Visiting Expert

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Visiting Expert

Member

Visiting Expert

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)