Showstopper in 7264 - be careful ...

[DJG]

[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-discussion/14827-windows-7-7264-leak-74.html#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 . "

 

[Zoulpain]

huh?

 

[raj11650]

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

http://www.sevenforums.com/general-discussion/14827-windows-7-7264-leak-74.html#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 . "

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

 

[YupYup]

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

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?.

 

[DJG]

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 .

 

[DJG]

7264 Showstopper Extended Analysis

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.

 

[or not]

good to know, thanks

 

[misterck]

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

 

[copernicus]

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.

 

[DJG]

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 .

 

[Jon55]

So what is the most recommended version at this time? 7260?


I currently have 7127 but am wondering if it's worth upgrading to 7260.

 

[grouchpunk08]

If you don't want the newest leak with the showstopper, then and I see you have x64, the recommended would be 7232. I'm sure most others that tried the x64 7260 would agree that 7232 is better.

 

[SIW2]

I did hear a rumour MS abandoned 7264/ removed it from consideration as it was too buggy.

 

[spliff]

Reckon I'll stay put w/ 7100x64 until there's a good OEM cracked file out. Why bother when it's running fast and smooth w/ my two screens and sound card.

 

[Jon55]

If you don't want the newest leak with the showstopper, then and I see you have x64, the recommended would be 7232. I'm sure most others that tried the x64 7260 would agree that 7232 is better.

Can anyone else verify this?


And yes, I'd be running the x64 version.

 

[K3VL4R]

Can anyone else verify this?


And yes, I'd be running the x64 version.

+1 for 7232 over 7260 in X64 flavors.

I also just heard about a CPU heat issue with 7264 when Overclocking. Not sure how many of you OC here but I have my Q6600 OC'ed from 2.4 to 3.6 and I noticed 5*C to 10*C higher temps at idle, so I will probably go back to 7232. GPU seems normal so far.

Anyway if you OC or if you want to check your temps out even if you do not I recommend Realtemp because it will show temps on all cores and the cpu load. If you do not know your CPU's rated temp, just Google Overclocking "your processor" because I don't think I can link to another forum.

 

[LarryLaser]

The Showstopper's Issues.

I have been Debugging many Issues in many Ways and on a few different Computers and found the main and same issues for Freezing, Crashing and just plain corruption and file loss.

My main system I test on is a (My Build) Gigabyte Mobo 965P-DS3, Intel Q6600 (2.4Ghz), 8Gig QCZ (800) mem, 2-nVid based Sparkler 9400GT (1 PCI-e and 1 PCI) graphics cards, 4 monitors (2-19" wide {1440x900}, 1-19" St 1280x1024 and a 17" St @1280x1024) and 8 HDD's at a total of 6TBts.
The onboard net is a Marvell Yucon 88E8053 PCI-e Gigabit EC. I have 18 fans in my system including dual and triple fans for my HDD's (mostly 10mm's and some 40mm's), My Rear and Side fans are 120mm's and a 80mm's. I am currently building an AC cooling system for my CP's, this will keep them down to 30ºC or lower.

In most of the bug issues are always related to the VISTA_DRIVER_ID #'s and and compatibility problems related with hardware drivers not properly functional.

The Issue I have found with the problem yáll have talked about on this thread is mainly related to Overclocking problems that are because of over heating/BIOS controllers.

If you Overclock more than 10% in CPU sets and BUS sets then you cause Over Voltage and Over Heat issues, The BIOS then runs a speed reset process (mostly is Automatic, some can disable or manually control it), when this happens the OS's (Win XP, Vista and Win7) hits DPC(Deferred Procedure Calls) and Hardware Interrupts heavily, in net transfers, this can cause the freeze and corrupt any of the files being transferred, in graphics operations this will cause jitterbugging and vid failures.
This is not just happening in Win7, it also happens in WinXP and Vista.

If the Temp jumps above 50º C then your BIOS begins some steps in controll changes, by the time it reaches 55º C the system begins the CPU turndown process.

I never recommend the Overclocking, but if you do I do not suggest you go above 10% increase. And maintain a reasonable cooling set.