More great photos. Looks like you two had a wonderful time. Hope to hear from Jeff when he gets back to the brutal heat here in Austin. Warning! At least three out of the next five days (Monday August 9 through Friday August 13, look out!) will feature triple digit temps. Ouch!
--Ed--
Keep up the good work, guys. Sounds like you're having at least as much fun (and the same kind of weather) as we did on our recent trip to Maine. Word of warning: you won't want to come home to the "no relief in sight from triple digit temps" that currently passes as our so-called weather forecast. Ouch!____See ya soon!__--Ed--
You're welcome! Comments about my sanity, troubleshooting skills, and general competence notwithstanding, I really enjoyed--and continue to enjoy--this entire adventure!
--Ed--
Had that system running for 2-plus years before making the 32 to 64 bit switch. HW Monitor reported temperatures of 27-37 Celsius at the cores, and never over 40 Celsius at the socket. Just re-ran HW Monitor on that machine and temps are as follows (wish I could just stick a screenshot in here):
mobo: 24-27
CPU socket: 25-32
CPU core 1: 35-38
CPU core 2: 33-35
CPU core 3: 38-41
CPU core 4: 38-41 (all preceding temps Celsius)
I *seriously* doubt it was thermal. I always watch my temps and that build ran cool for so long in advance of the switchover that I'd be surprised if temps caused my problem. Besides, why would the same cooler/CPU work (and install) Win7 x86 flawlessly but bork on x64. Surely, both would overheat at more or less the same time?
Interesting hypothesis, though.
--Ed--
I did try the original configuration with only the CPU different. Same problem. Thanks for asking,
--Ed--
Thank you. Thank you. Thank you. Nice to hear my own longstanding experience vindicated by somebody else. This is the first "partial CPU failure" I've ever experienced. Numerous dead CPUs over the years (occupational hazard when you're assigned to overclock systems) but none that worked mostly, except for this one little thing...
To me, at least, that's what made this story interesting and why I pitched it to Esther in the first place.
Thanks again,
--Ed--
The original CPU runs 32-bit Win7 fine, but it won't permit me to install Win7 x64 as documented. That's what I know for sure anyway!
--Ed--
I don't know why the part dislays its particular and unique (in my experience, and in my research of available information, forum postings, and so forth). I had hoped to get Intel to dig in and see what was up but they were emphatically not interested. If you have some ideas on how I might go about testing further, I'm certainly game to try.
Thanks for the feedback.
--Ed--
Gee that's pretty much the order I followed myself, except for putting the mobo and PSU ahead of the CPU. As I have now stated in replies to numerous other posts, I'd actually forgotten the chip was an engineering sample, because it had been working without any problems for over two years (in 32-bit mode, however). I thought it was an interesting exercise in troubleshooting nevertheless, and wrote it up as such.
Thanks for adding some cogent and relevant advice to the overall content of the story.
--Ed--
Hey! I used that system for 2-plus years on 32-bit OSes without any problems at all. I started working in IT in 1981/2, possibly before you were born. If the system hadn't worked fine for so long I wouldnt' have been so cavalier about switching from 32- to 64-bit. As I said in a reply to an earlier posting, it had been so long since Intel sent it to me that I'd actually forgotten it was an engineering sample until I popped it out and check the package information. I just thought it was an interesting troubleshooting exercise and wrote it up as such. It's your privilege (and apparent pleasure) to think otherwise.
Thanks for the feedback,
--Ed--
![[Avatar]](/images/avatar26.png){kind=avatar}
Ed Tittel 
Brainchild