New
#21
It is A100-599.
What I would really need is someone having the same or closely comparable model to install Windows 7 and see if this happens on that machine too. The problem occurs with a clean installation with no additional software too. It didn't exist with RC.
A confirmation that this problem is reproducible on this combination of hardware components would be helpful, but as I said, the guys at Redmond are working on this issue.
Well, my problem is solved.
I turned out that to make it possible for my system to work full speed I needed to
a) reset the BIOS to factory defaults
b) set settings to the same values that were in place before that.
I just want to say this: at this moment all I want is a bullwhip and a couple of hours to get medieval on the asses of those in Phoenix Technologies LTD (and those in Toshiba too) responsible for this agony I (and my computer) went through since I installed RTM.
I'm angry beyond belief. I - no, not I, THEY wasted my time and more importantly the time of those good people in Microsoft that have been helping me with this. Resetting the BIOS to factory settings was the idea one of them came up with. I for some curious reason didn't think of doing that all this time. I mean, who would've thought??? I didn't touch the freakin' BIOS at all during the migration from Vista to 7!!!
All my thanks to the marvellous people in Microsft who I will name if I get permission from them to do so.
Before:
- <WinSAT>
- <ProgramInfo>
<Name>WinSAT</Name>
<Version>V6.1 Build-7100.0</Version>
<WinEIVersion>Windows7-RC-0.91</WinEIVersion>
<Title>Windows System Assessment Tool</Title>
<ModulePath>C:\Windows\system32\winsat.exe</ModulePath>
- <CmdLine>
- <![CDATA[ "C:\Windows\system32\winsat.exe" formal -cancelevent 284f5815-6cb2-4840-a052-0e44456aa69d
]]>
</CmdLine>
- <Note>
- <![CDATA[
]]>
</Note>
</ProgramInfo>
- <SystemEnvironment>
<ExecDateTOD Friendly="Saturday September 12, 2009 7:57:21pm">733662:71841960</ExecDateTOD>
<IsOfficial>1</IsOfficial>
<IsFormal />
<RanOverTs>0</RanOverTs>
<RanOnBatteries>0</RanOnBatteries>
</SystemEnvironment>
- <WinSPR>
<SystemScore>3.2</SystemScore>
<MemoryScore>3.2</MemoryScore>
<CpuScore>3.2</CpuScore>
<CPUSubAggScore>3.8</CPUSubAggScore>
<VideoEncodeScore>4.6</VideoEncodeScore>
<GraphicsScore>4.5</GraphicsScore>
<Dx9SubScore>4.5</Dx9SubScore>
<Dx10SubScore>0</Dx10SubScore>
<GamingScore>4.5</GamingScore>
<StdDefPlaybackScore>TRUE</StdDefPlaybackScore>
<HighDefPlaybackScore>TRUE</HighDefPlaybackScore>
<DiskScore>4.8</DiskScore>
</WinSPR>
- <Metrics>
- <CPUMetrics>
<CompressionMetric units="MB/s">44.70806</CompressionMetric>
<EncryptionMetric units="MB/s">22.44890</EncryptionMetric>
<CPUCompression2Metric units="MB/s">134.42795</CPUCompression2Metric>
<Encryption2Metric units="MB/s">195.90944</Encryption2Metric>
<CompressionMetricUP units="MB/s">22.32255</CompressionMetricUP>
<EncryptionMetricUP units="MB/s">11.22517</EncryptionMetricUP>
<CPUCompression2MetricUP units="MB/s">66.77438</CPUCompression2MetricUP>
<Encryption2MetricUP units="MB/s">98.11741</Encryption2MetricUP>
<DshowEncodeTime units="s">12.68250</DshowEncodeTime>
</CPUMetrics>
- <MemoryMetrics>
<Bandwidth units="MB/s">1378.95642</Bandwidth>
</MemoryMetrics>
After:
Compare the numbers. It's crazy, bizarre, weird!- <WinSAT>
- <ProgramInfo>
<Name>WinSAT</Name>
<Version>V6.1 Build-7600.16385</Version>
<WinEIVersion>Windows7-RC-0.91</WinEIVersion>
<Title>Windows System Assessment Tool</Title>
<ModulePath>C:\Windows\system32\winsat.exe</ModulePath>
- <CmdLine>
- <![CDATA[ "C:\Windows\system32\winsat.exe" formal -cancelevent b1cd15bb-05db-4235-9c77-4a5a6ab9f556
]]>
</CmdLine>
- <Note>
- <![CDATA[
]]>
</Note>
</ProgramInfo>
- <SystemEnvironment>
<ExecDateTOD Friendly="Thursday September 24, 2009 10:14:52pm">733674:80092144</ExecDateTOD>
<IsOfficial>1</IsOfficial>
<IsFormal />
<RanOverTs>0</RanOverTs>
<RanOnBatteries>0</RanOnBatteries>
</SystemEnvironment>
- <WinSPR>
<SystemScore>4.5</SystemScore>
<MemoryScore>5</MemoryScore>
<CpuScore>5</CpuScore>
<CPUSubAggScore>4.8</CPUSubAggScore>
<VideoEncodeScore>5.2</VideoEncodeScore>
<GraphicsScore>4.5</GraphicsScore>
<Dx9SubScore>4.5</Dx9SubScore>
<Dx10SubScore>0</Dx10SubScore>
<GamingScore>4.5</GamingScore>
<StdDefPlaybackScore>TRUE</StdDefPlaybackScore>
<HighDefPlaybackScore>TRUE</HighDefPlaybackScore>
<DiskScore>4.8</DiskScore>
</WinSPR>
- <Metrics>
- <CPUMetrics>
<CompressionMetric units="MB/s">100.79263</CompressionMetric>
<EncryptionMetric units="MB/s">51.72366</EncryptionMetric>
<CPUCompression2Metric units="MB/s">296.58154</CPUCompression2Metric>
<Encryption2Metric units="MB/s">468.24298</Encryption2Metric>
<CompressionMetricUP units="MB/s">50.51501</CompressionMetricUP>
<EncryptionMetricUP units="MB/s">25.81683</EncryptionMetricUP>
<CPUCompression2MetricUP units="MB/s">148.04720</CPUCompression2MetricUP>
<Encryption2MetricUP units="MB/s">234.07881</Encryption2MetricUP>
<DshowEncodeTime units="s">7.29427</DshowEncodeTime>
</CPUMetrics>
- <MemoryMetrics>
<Bandwidth units="MB/s">3015.19897</Bandwidth>
</MemoryMetrics>
Last edited by Teerex; 24 Sep 2009 at 16:02. Reason: typo
Hello
Im having exactly the same problem. I have toshiba satellite A200, something happened and my index score for CPU and RAM went from 4.5 to 2.7! Can you tell me in details how did you reset your BIOS and settings?
Hi,
The WEI base score is determined by lowest subscore (thats what it says under the score). So you may very well have some high scores but the score chosen as the WEI will be the lowest subscore.
Hi,
I'm having the same problem you had. My CPU and RAM scores came down to 3.1 from 4.5 for Toshiba A200-1BP. My current bios version is 5.20. My friend has the identical A200 with v1.30bios and he's NOT having any problems. Did you flash your bios with an older version or just reset to factory settings on current version?
WEI is rigged especially the hard drive index score, WD Black = 5.9; WD VelociRaptor = 5.9? Looks good to get high scores with WEI but it's no real performance benchmarking tool.