Windows 7: Showstopper in 7264 - be careful ...

[NOTE: check the analysis a few posts down!]

Check out my post in the 7264 thread, and make your decision ...

http://www.sevenforums.com/general-d...tml#post151071

"DEFINITE SHOW STOPPER!

OK, I'll stop shouting. My Lenovo didn't implode, but my 7232 workstation did when I started copying a large file to it from the 7264 Lenovo. After about 15% the receiving workstation froze completely. I had to use the reset button, which caused my system RAID 10 to go to recovery mode. I repeated again (I have several backups ) and it seemed OK but about 60% through this time, again the receiving workstation froze.

I'm restoring 7232 to my Lenovo as we speak, while my workstation's RAID 10 heals itself . "

huh?

i guess its not a bug on build 7264
wont be just bcoz its RTM candidate build!!!

you can have (and will have) bugs on any build. The question is this particular bug in 7264 or 7232?, or is it a combination of using both?.

Indeed that is the question . No problem 7232 to 7232. Also no problem between 7232 and 7260. Maybe somebody else will try 7264 to 7264? Call me old-fashioned, but between the warning and this, I'm taking the view that it's a 7264 thing, just MHO.

As always, YMMV .

I've taken some time to do some more testing on this. I've reloaded 7264 x64 as a clean install dual-boot so here's the testbed:

Lenovo X61t tablet notebook:
7232 x64 (upgraded full app complement)
7264 x64 (clean install vanilla)

Core i7 920 workstation:
7232 x64 (clean install full app complement)
7260 x86 (clean install vanilla)
normal and overclocked hardware

I used a 23GB backup image file to copy between systems.

Observed symptom: when copying the file from one system to another over Gigabit LAN the target system completely freezes, requiring hard reset.

Test result: The only time I encountered the freeze (always REPEATABLE, with varying timing) was when copying from the notebook 7264 to the OVERCLOCKED workstation 7232, not if running at normal speeds. All other combos where OK, including overclocked.

Conclusion: this particular problem is in 7260, and is exacerbated by the target being on the ragged edge of execution.

Notice that only the system with a full complement of applications installed and many background processes froze, and then only when overclocked. It just so happened this was my initial 7264 environment configuration since my workstation is overclocked as the norm.

Also of note is that the problem is not an overclocking failure, but a hard system deadlock. The overclocking just seems to egg it out .

BTW, the overclocking configuration can handle over 2 hours of 100% CPU, cache & memory stressing without failure, but obviously there's no networking going on there.

It appears this problem is introducing some kind of system deadlock under certain circumstances which are more likely under system stress. So chances are most people will not encounter this.

good to know, thanks

i dont see us having this build for too long before another appears, my guess would be within 2-3 days lol.

What are the specifics of the system that's locking up? (mobo/ram/etc)

Have you tried moving smaller flies (20/10/5 giggers?)

I rarely move files that large, but I'm constantly moving 1-3 giggers over gigabit, don't wanna walk into that if it's proven.

The original crash happened while copying the ISO for 7264, which is 3GB, and happened about 20% into the copy, but others have taken much longer to crash. But remember that was in an OC'ed system. Because it looks very config specific, I would do a few check runs in your environment with a 5GB between your specific systems before feeling commited .