Re: Windows XP Home Edition SP2 NTFS


"Phil Weldon" <notdiscosed@xxxxxxxxxxx> wrote in message:

I'mi' wrote:
| Not so. Settings in the BIOS (software on a flash memory chip) can be
set
to
| overclock CPU and memory speed to the point of overheating and hardware
| damage. Software programs for graphics cards can do the same thing. The
| utility 'Speedfan' can cause hardware failure if used improperly.
_____

BIOS settings for increasing CPU speed and/or memory speed can not
physically damage the CPU or memory. Intel CPUs since at least the
Pentium
II contain thermal diodes that force a shut-down on overheating, resulting
in no damage. Even that likely never happens because long before that
point
the CPU will produce errors and lock up and cool off because very few
transistors are switching. More recent AMD CPUs also have that
protection.
For overclocked memory, errors will begin to occur and lock up the system
long before any damage is done. Setting CPU core voltage too high can
immediately destroy a CPU, but excessive voltage settings require a manual
selection in the BIOS. 'Manual settings' are NOT a 'software program'.

Phil Weldon

I'll inform the community at alt.comp.hardware.overclocking that Phil Weldon
said the nonfunctioning Intel and AMD cpus they have are not actually dead
but in cooldown mode. Whether manual or automatic it's still a software
interface and it has a direct effect on hardware.


| > "Will Denny" <willdenny@xxxxxxxx> wrote in message:
|
| >> Agreed - no software can physically damage any hardware. However
| >> hardware does deteriorate over time.
|
| >> Will Denny
| >> MS-MVP Windows Shell/User
| >> Please reply to the News Groups



.

Relevant Pages

  • [PATCH] Document Linuxs memory barriers [try #3]
    ... The attached patch documents the Linux kernel's memory barriers. ... I've tried to get rid of the concept of memory accesses appearing on the bus; ... barring implicit enforcement by the CPU. ...
    (Linux-Kernel)
  • Oops in 2.6.28-rc9 and -rc8 -- mtrr issues / e1000e
    ... Bios 1.04beta did show correct memory sizing in dmidecode, ... I hope this is as simple as me doing something glaringly wrong in the kernel ... DMI present. ... CPU: L2 cache: 6144K ...
    (Linux-Kernel)
  • Re: read vs. mmap (or io vs. page faults)
    ... not fit in main memory, and there are overheads related to the heuristics ... But because the CPU is underutilized, ... reasonably sized user buffer). ... You have to measure the actual overhead to see what the actual cost is. ...
    (freebsd-questions)
  • Sun Fire v440 hardware problem (cant get ok>)
    ... 0>Init CPU ... 1>Set JBUS config reg ... 0>Probe and Setup Memory ... Could not read diag-level from NVRAM! ...
    (SunManagers)
  • Re: Windows XP Home Edition SP2 NTFS
    ... Settings in the BIOS (software on a flash memory chip) can be set ... BIOS settings for increasing CPU speed and/or memory speed can not ...
    (microsoft.public.windowsxp.basics)