CPU Core Voltage Too Low -> Crash? [Archive]

Don Cohen

February 21st 04, 09:43 PM

Hi,

This is a fresh thread based on what was learned in a separate thread
(Desperately Need Help - System Reboot/Crashes).

The tentative conclusion in the other thread is that my crashes are being
caused by hardware, and not software. In that regard, I have installed and
run AIDA32 Enterprise System Information. Here is the relevant information:

My primary problem is random, sporadic crashes to a BSOD, starting after
almost 2 years of relatively glitch-free running, and *not* following any
significant hardware or software changes:

PAGE_FAULT_IN_NONPAGED_AREA
****STOP: 0x00000050 (0xB7874E5E, 0x00000000, 0xB7874E5E, 0x00000000)

Full details on this problem and prior trouble-shooting can be found in the
other thread.

Gateway 700XL, approximately 2 years old, XP Home, 1024 mb RAM
Intel Pentium 4A, 2.2 GHz (5.5x400), Northwood A80532 CPU chip
Intel D850MV (Maryville) Motherboard, i850 Chipset
Brand new Antec 430W TruPower PSU (replacing the prior Gateway 250W PSU, but
not fixing the crashes)

AIDA32 shows the actual CPU Core Voltage for my system varying between 1.43
and 1.45 Volts.
AIDA32 also has a section showing the CPU Physical Properties. Here it
indicates:
--Core Voltage 1.475V - 1.55V--

Someone experiencing similar (but not identical) crashes as me found his CPU
Core Voltage to be the source of his problem, indicating his opinion that
voltage differences as small as 0.025V can be quite significant. If true,
then my CPU Core Voltage is out of the normal range.

My questions:

1. Is the difference between the apparent optimal range for Core Voltage and
my actual Core Voltage enough to explain these very random crashes? (I can
go a few minutes, a few hours, a few days between crashes).

2. Is there any way to adjust this voltage? I have not yet found any BIOS
or motherboard jumper settings that might do this.

3. If this is the source of the problem, do I replace the motherboard, or
the CPU? In other words, which hardware component is causing the low CPU
Core Voltage?

Anybody that can offer some knowledgeable advice here? It will be very
greatly appreciated. I have been fighting this problem for several weeks
now, and consumed untold hours trouble-shooting.

Thanks!

Don

Edward J. Neth

February 21st 04, 10:04 PM

"Don Cohen" > wrote in message
...

> 1. Is the difference between the apparent optimal range for Core Voltage
and
> my actual Core Voltage enough to explain these very random crashes? (I can
> go a few minutes, a few hours, a few days between crashes).

It's unlikely. Do the crashes occur when you run in Safe Mode? I'd bet on
a software issue
before you start troubleshooting hardware. Anything abnormal in the event
logs?

>
> 2. Is there any way to adjust this voltage? I have not yet found any BIOS
> or motherboard jumper settings that might do this.

No.

>
> 3. If this is the source of the problem, do I replace the motherboard, or
> the CPU? In other words, which hardware component is causing the low CPU
> Core Voltage?
>

Most likely the power supply, if it turns out to be hardware in origin.

Don Cohen

February 21st 04, 10:22 PM

Hi Edward,

Thanks for the reply.

> > 1. Is the difference between the apparent optimal range for Core Voltage
> and
> > my actual Core Voltage enough to explain these very random crashes? (I
can
> > go a few minutes, a few hours, a few days between crashes).
>
> It's unlikely. Do the crashes occur when you run in Safe Mode? I'd bet
on
> a software issue
> before you start troubleshooting hardware. Anything abnormal in the event
> logs?

You can check the other thread for the long, gory details (this has been a
long, tortous process), but what is highly suggestive that it's hardware is:

-the reboots *have* occurred in safe mode
-they also occurred when I booted directly from the XP CD in order to access
the Windows Recovery Console. I got to the point where it lets you choose
the Windows partition (in my case, the only choice present is c:\winnt), and
when I hit enter, it rebooted.

To me, and the others more knowledgeable than me, this was a fairly
definitive indication that it's a hardware issue, since no programs,
drivers, etc., from the OS on the hard drive were even loaded or running.

If you think otherwise, please let me know what your reasoning is.

> > 3. If this is the source of the problem, do I replace the motherboard,
or
> > the CPU? In other words, which hardware component is causing the low
CPU
> > Core Voltage?
> >
>
> Most likely the power supply, if it turns out to be hardware in origin.

My initial suspicion when this whole thing started, based on the specific
stop message, was a bad PSU. I replaced the 250W original PSU that came
with the system, with an Antec 430W TruPower PSU. It ran fine for almost 3
days after I did this, but then the identical crash recurred.

So at this point, I strongly suspect motherboard and/or CPU. But I really
don't know anything for sure at this point.

Any additional thoughts greatly appreciated.

Don

Jack

February 21st 04, 10:22 PM

Hi Don, this is really a long shot, but it recently happened to me on a
three year old system(non-Gateway).
I was getting random re-boots and corruptions. Even when trying to get to
the Recovery Console.
It turned out it was a faulty cd/dvd rom(Pioneer dvd-116). My only
indication of this was that CD's were getting hot when being used.
hth, Jack

"Don Cohen" > wrote in message
...
> Hi,
>
> This is a fresh thread based on what was learned in a separate thread
> (Desperately Need Help - System Reboot/Crashes).
>
> The tentative conclusion in the other thread is that my crashes are being
> caused by hardware, and not software. In that regard, I have installed
and
> run AIDA32 Enterprise System Information. Here is the relevant
information:
>
> My primary problem is random, sporadic crashes to a BSOD, starting after
> almost 2 years of relatively glitch-free running, and *not* following any
> significant hardware or software changes:
>
> PAGE_FAULT_IN_NONPAGED_AREA
> ****STOP: 0x00000050 (0xB7874E5E, 0x00000000, 0xB7874E5E, 0x00000000)
>
> Full details on this problem and prior trouble-shooting can be found in
the
> other thread.
>
> Gateway 700XL, approximately 2 years old, XP Home, 1024 mb RAM
> Intel Pentium 4A, 2.2 GHz (5.5x400), Northwood A80532 CPU chip
> Intel D850MV (Maryville) Motherboard, i850 Chipset
> Brand new Antec 430W TruPower PSU (replacing the prior Gateway 250W PSU,
but
> not fixing the crashes)
>
> AIDA32 shows the actual CPU Core Voltage for my system varying between
1.43
> and 1.45 Volts.
> AIDA32 also has a section showing the CPU Physical Properties. Here it
> indicates:
> --Core Voltage 1.475V - 1.55V--
>
> Someone experiencing similar (but not identical) crashes as me found his
CPU
> Core Voltage to be the source of his problem, indicating his opinion that
> voltage differences as small as 0.025V can be quite significant. If true,
> then my CPU Core Voltage is out of the normal range.
>
> My questions:
>
> 1. Is the difference between the apparent optimal range for Core Voltage
and
> my actual Core Voltage enough to explain these very random crashes? (I can
> go a few minutes, a few hours, a few days between crashes).
>
> 2. Is there any way to adjust this voltage? I have not yet found any BIOS
> or motherboard jumper settings that might do this.
>
> 3. If this is the source of the problem, do I replace the motherboard, or
> the CPU? In other words, which hardware component is causing the low CPU
> Core Voltage?
>
> Anybody that can offer some knowledgeable advice here? It will be very
> greatly appreciated. I have been fighting this problem for several weeks
> now, and consumed untold hours trouble-shooting.
>
> Thanks!
>
> Don
>
>

Cunning Linguist

February 21st 04, 10:41 PM

Don Cohen wrote in microsoft.public.windowsxp.help_and_support:

> Hi,
>
> This is a fresh thread based on what was learned in a separate thread
> (Desperately Need Help - System Reboot/Crashes).
>
> The tentative conclusion in the other thread is that my crashes are
> being caused by hardware, and not software. In that regard, I have
> installed and run AIDA32 Enterprise System Information. Here is the
> relevant information:
>
> My primary problem is random, sporadic crashes to a BSOD, starting after
> almost 2 years of relatively glitch-free running, and *not* following
> any significant hardware or software changes:
>
> PAGE_FAULT_IN_NONPAGED_AREA
> ****STOP: 0x00000050 (0xB7874E5E, 0x00000000, 0xB7874E5E, 0x00000000)
>
> Full details on this problem and prior trouble-shooting can be found in
> the other thread.
>
> Gateway 700XL, approximately 2 years old, XP Home, 1024 mb RAM
> Intel Pentium 4A, 2.2 GHz (5.5x400), Northwood A80532 CPU chip
> Intel D850MV (Maryville) Motherboard, i850 Chipset
> Brand new Antec 430W TruPower PSU (replacing the prior Gateway 250W PSU,
> but not fixing the crashes)
>
> AIDA32 shows the actual CPU Core Voltage for my system varying between
> 1.43 and 1.45 Volts.
> AIDA32 also has a section showing the CPU Physical Properties. Here it
> indicates:
> --Core Voltage 1.475V - 1.55V--
>
> Someone experiencing similar (but not identical) crashes as me found his
> CPU Core Voltage to be the source of his problem, indicating his opinion
> that voltage differences as small as 0.025V can be quite significant.
> If true, then my CPU Core Voltage is out of the normal range.
>
> My questions:
>
> 1. Is the difference between the apparent optimal range for Core Voltage
> and my actual Core Voltage enough to explain these very random crashes?
> (I can go a few minutes, a few hours, a few days between crashes).
>
> 2. Is there any way to adjust this voltage? I have not yet found any
> BIOS or motherboard jumper settings that might do this.
>
> 3. If this is the source of the problem, do I replace the motherboard,
> or the CPU? In other words, which hardware component is causing the low
> CPU Core Voltage?
>
> Anybody that can offer some knowledgeable advice here? It will be very
> greatly appreciated. I have been fighting this problem for several
> weeks now, and consumed untold hours trouble-shooting.
>
> Thanks!
>
> Don
>
>

Don, I'll bet dollars to doughnuts that you have a corrupted driver. Make sure you have all
updated drivers for your motherboard, sound card, video card and, if you have on installed,
56K modem. I had the same peoblem with crashes and blue screens. I upgraded my
motherboard drivers and all the others that I mentioned and I've been running BSOD free
for the last 9 months. Hope that healps.

Curley

February 21st 04, 10:41 PM

Another long shot Don. Your mention of nonpaged area rang a bell. I had problems on two new machines after reinstalling all my software. Numerous crashes and event log said nonpaged pool was empty. Turned out the culprit was Roxio GO Back. Comes with Nort
on systemworks, and IS NOT compatable with XP. It will load just fine then crash the system randomly. If you try to reinstall XP with GO BACK already installed XP will tell you during installation that it is not compatable.

Don Cohen

February 21st 04, 10:41 PM

Hi Jack,

> Hi Don, this is really a long shot, but it recently happened to me on a
> three year old system(non-Gateway).
> I was getting random re-boots and corruptions. Even when trying to get to
> the Recovery Console.
> It turned out it was a faulty cd/dvd rom(Pioneer dvd-116). My only
> indication of this was that CD's were getting hot when being used.

Interesting. At this point, anything's possible. I just wish there were
some specific hardware diagnostics that could be used to actually make a
diagnosis, rather than having to do a tedious and time-consuming trial and
error replacement.

Actually, I have been referred to a program called Tuff-Test-Pro, that is
supposed to do just this.

Does anybody here have any experience with this program?

Thanks

Don

Don Cohen

February 21st 04, 10:42 PM

> Don, I'll bet dollars to doughnuts that you have a corrupted driver. Make
sure you have all
> updated drivers for your motherboard, sound card, video card and, if you
have on installed,
> 56K modem. I had the same peoblem with crashes and blue screens. I
upgraded my
> motherboard drivers and all the others that I mentioned and I've been
running BSOD free
> for the last 9 months. Hope that healps.

Thanks for the post and suggestions.

Ordiniarily, I would agree with you. But what makes this situation
different, and apparently much more suggestive of a hardware source is the
following:

--these crashes occurred from within Safe Mode
--they have also occurred when booting directly from the XP Boot CD, going
into Windows Recovery Console. Afaik, no hard drive based drivers or files
are in use in that circumstance.

If you think otherwise, I'm definitely interested in your thinking.

Thanks!

Don

P.S. How does one update one's motherboard drivers?

Don Cohen

February 21st 04, 10:42 PM

Hi Curley,

> Another long shot Don. Your mention of nonpaged area rang a bell. I had
problems on two new machines after reinstalling all my software. Numerous
crashes and event log said nonpaged pool was empty. Turned out the culprit
was Roxio GO Back. Comes with Norton systemworks, and IS NOT compatable with
XP. It will load just fine then crash the system randomly. If you try to
reinstall XP with GO BACK already installed XP will tell you during
installation that it is not compatable.

Thanks for the reply.

I've found there are a wide variety of applications that will cause similar
appearing crashes: Lexar Card drivers, Roxio GO Back, also Roxio CD Creator
as well, if I recall correctly. In my case, GO Back is not installed on my
system.

The things that argue against a software cause for these crashes:

--these crashes occurred from within Safe Mode
--they have also occurred when booting directly from the XP Boot CD, going
into Windows Recovery Console. Afaik, no hard drive based drivers or files
are in use in that circumstance.

But until I actually solve it, I really don't know anything for sure.

Best regards,

Don

Unknown

February 21st 04, 11:02 PM

Do not overlook a static problem. In winter indoors with dry air almost
anythig will generate static.
"Don Cohen" > wrote in message
...
> > Don, I'll bet dollars to doughnuts that you have a corrupted driver. Make
> sure you have all
> > updated drivers for your motherboard, sound card, video card and, if you
> have on installed,
> > 56K modem. I had the same peoblem with crashes and blue screens. I
> upgraded my
> > motherboard drivers and all the others that I mentioned and I've been
> running BSOD free
> > for the last 9 months. Hope that healps.
>
> Thanks for the post and suggestions.
>
> Ordiniarily, I would agree with you. But what makes this situation
> different, and apparently much more suggestive of a hardware source is the
> following:
>
> --these crashes occurred from within Safe Mode
> --they have also occurred when booting directly from the XP Boot CD, going
> into Windows Recovery Console. Afaik, no hard drive based drivers or files
> are in use in that circumstance.
>
> If you think otherwise, I'm definitely interested in your thinking.
>
> Thanks!
>
> Don
>
> P.S. How does one update one's motherboard drivers?
>
>

dmac

February 21st 04, 11:21 PM

not for nothing, but it could be a hard drive issue. rec console accesses
the c drive I believe.

--

David MacLeod
Etna, Maine USA
P4 2.8 OC to 3.13
1 GB DDR 466
Radeon 9800 Pro 256 MB
2 Seagate 120 RAID 0

"Don Cohen" > wrote in message
...
> Hi Jack,
>
> > Hi Don, this is really a long shot, but it recently happened to me on a
> > three year old system(non-Gateway).
> > I was getting random re-boots and corruptions. Even when trying to get
to
> > the Recovery Console.
> > It turned out it was a faulty cd/dvd rom(Pioneer dvd-116). My only
> > indication of this was that CD's were getting hot when being used.
>
> Interesting. At this point, anything's possible. I just wish there were
> some specific hardware diagnostics that could be used to actually make a
> diagnosis, rather than having to do a tedious and time-consuming trial and
> error replacement.
>
> Actually, I have been referred to a program called Tuff-Test-Pro, that is
> supposed to do just this.
>
> Does anybody here have any experience with this program?
>
> Thanks
>
> Don
>
>
>

Don Cohen

February 21st 04, 11:21 PM

> not for nothing, but it could be a hard drive issue. rec console accesses
> the c drive I believe.

This occurred to me as well. I may have to buy and try out that
Tuff-Test-Pro and see if it can find a specific hardware problem.

Thanks

Don

Don Cohen

February 21st 04, 11:21 PM

> Do not overlook a static problem. In winter indoors with dry air almost
> anythig will generate static.

True. But more often than not it occurs when I'm just sitting at the
keyboard, typing or mousing around, and bam! there it goes.

Don

Unknown

February 21st 04, 11:21 PM

Yes but simple movements such as casters on a chair, or the mouse on a plastic
surface will generate static. My brother had the same problem. We tried a
humidifier and presto, no more problems. I keep the humidity in my house on
the high side----have an automatic one in my furnace.
"Don Cohen" > wrote in message
...
> > Do not overlook a static problem. In winter indoors with dry air almost
> > anythig will generate static.
>
> True. But more often than not it occurs when I'm just sitting at the
> keyboard, typing or mousing around, and bam! there it goes.
>
> Don
>
>
>
>

February 22nd 04, 12:03 AM

On Sat, 21 Feb 2004 17:11:04 -0500, "Don Cohen"
> wrote:

>> Do not overlook a static problem. In winter indoors with dry air almost
>> anythig will generate static.
>
>True. But more often than not it occurs when I'm just sitting at the
>keyboard, typing or mousing around, and bam! there it goes.
>
>Don

Hi Don:

Nothing like going crazy trying to track something like this down....

From reading your posts and replies and what you've already done to
trouble shoot the problem, I believe it is very definitely a hardware
issue.

I would suggest you not spend any more money on diagnostic programs or
the like. Of course a free one is always great to have. I'm not
sure I really trust AIDA32 to accurately monitor CPU voltages. The
best free application that I know of to do that is called "Motherboard
Monitor". You might wish to download and give it a try. Also, go to
the CPU makers web site and get the specs for your CPU. Both Intel
and AMD have spec sheets available which give the voltage and
temperature ranges for the CPUs they manufacture.

You may indeed have a bad motherboard or at least an intermittent
failing component on the board. It may even be memory related. I
don't recall you saying you swapped out the memory modules? Also, go
into your CMOS setup program and make sure all the settings for memory
are within specs. (CAS, RAS, etc)

Good luck.

dmac

February 22nd 04, 12:43 AM

forgot to mention I had boot and crashes when my WD120 started dying. even
in safe mode. drives are pretty cheap, even if it doesn't fix the problem
might be good idea to keep an extra around.

--

David MacLeod
Etna, Maine USA
P4 2.8 OC to 3.13
1 GB DDR 466
Radeon 9800 Pro 256 MB
2 Seagate 120 RAID 0

"Don Cohen" > wrote in message
...
> > not for nothing, but it could be a hard drive issue. rec console
accesses
> > the c drive I believe.
>
> This occurred to me as well. I may have to buy and try out that
> Tuff-Test-Pro and see if it can find a specific hardware problem.
>
> Thanks
>
> Don
>
>
>

dmac

February 22nd 04, 12:43 AM

also forgot to say clean out all temp folders. ones under documents/settings
and windows. might be an errored temp file.

--

David MacLeod
Etna, Maine USA
P4 2.8 OC to 3.13
1 GB DDR 466
Radeon 9800 Pro 256 MB
2 Seagate 120 RAID 0

"Don Cohen" > wrote in message
...
> > not for nothing, but it could be a hard drive issue. rec console
accesses
> > the c drive I believe.
>
> This occurred to me as well. I may have to buy and try out that
> Tuff-Test-Pro and see if it can find a specific hardware problem.
>
> Thanks
>
> Don
>
>
>

Don Cohen

February 22nd 04, 01:21 AM

> Nothing like going crazy trying to track something like this down....

Boy, is that the truth. It has consumed an incredible amount of time and
mental energy.

> From reading your posts and replies and what you've already done to
> trouble shoot the problem, I believe it is very definitely a hardware
> issue.

I appreciate the confirmation. That seems like the only logical conclusion,
but we all know how strange the truth can be at times...

> I would suggest you not spend any more money on diagnostic programs or
> the like. Of course a free one is always great to have. I'm not
> sure I really trust AIDA32 to accurately monitor CPU voltages. The
> best free application that I know of to do that is called "Motherboard
> Monitor". You might wish to download and give it a try. Also, go to
> the CPU makers web site and get the specs for your CPU. Both Intel
> and AMD have spec sheets available which give the voltage and
> temperature ranges for the CPUs they manufacture.

OK, I've downloaded and installed Motherboard Monitor. Definitely more
complex than AIDA32 to setup. But I think I have it now.

It shows Core Temp for CPU varying between 1.46V and 1.49V. I checked
Intel's site, found my chip (SL66S) and it shows the spec for Core Voltage
as 1.500V. So according to MbMonitor my core voltage is still on the low
side, but how significant this 0.1 to 0.4 volts is, I don't know.

Regarding additional diagnostic programs - I'd rather not buy more as well,
but at this point, I still don't have an answer as to what hardware is
faulty, and what to replace...

> You may indeed have a bad motherboard or at least an intermittent
> failing component on the board. It may even be memory related. I
> don't recall you saying you swapped out the memory modules? Also, go
> into your CMOS setup program and make sure all the settings for memory
> are within specs. (CAS, RAS, etc)

I haven't done anything yet with the actual (4) memory modules. Memtest86
ran for over 13 hours/7passes, with no errors detected.

So bottom line - where do I go from here????

Thanks much for the help.

Don

February 22nd 04, 02:03 AM

On Sat, 21 Feb 2004 19:11:11 -0500, "Don Cohen"
> wrote:

>> Nothing like going crazy trying to track something like this down....
>
>Boy, is that the truth. It has consumed an incredible amount of time and
>mental energy.
>
>> From reading your posts and replies and what you've already done to
>> trouble shoot the problem, I believe it is very definitely a hardware
>> issue.
>
>I appreciate the confirmation. That seems like the only logical conclusion,
>but we all know how strange the truth can be at times...
>
>> I would suggest you not spend any more money on diagnostic programs or
>> the like. Of course a free one is always great to have. I'm not
>> sure I really trust AIDA32 to accurately monitor CPU voltages. The
>> best free application that I know of to do that is called "Motherboard
>> Monitor". You might wish to download and give it a try. Also, go to
>> the CPU makers web site and get the specs for your CPU. Both Intel
>> and AMD have spec sheets available which give the voltage and
>> temperature ranges for the CPUs they manufacture.
>
>OK, I've downloaded and installed Motherboard Monitor. Definitely more
>complex than AIDA32 to setup. But I think I have it now.
>
>It shows Core Temp for CPU varying between 1.46V and 1.49V. I checked
>Intel's site, found my chip (SL66S) and it shows the spec for Core Voltage
>as 1.500V. So according to MbMonitor my core voltage is still on the low
>side, but how significant this 0.1 to 0.4 volts is, I don't know.
>
>Regarding additional diagnostic programs - I'd rather not buy more as well,
>but at this point, I still don't have an answer as to what hardware is
>faulty, and what to replace...
>
>> You may indeed have a bad motherboard or at least an intermittent
>> failing component on the board. It may even be memory related. I
>> don't recall you saying you swapped out the memory modules? Also, go
>> into your CMOS setup program and make sure all the settings for memory
>> are within specs. (CAS, RAS, etc)
>
>I haven't done anything yet with the actual (4) memory modules. Memtest86
>ran for over 13 hours/7passes, with no errors detected.
>
>
>So bottom line - where do I go from here????
>
>Thanks much for the help.
>
>Don

Hi Don:

I don't believe the low core voltage is the problem. If anything, a
lower core voltage will usually result in the CPU running a bit
cooler. It's when the core voltage begins to exceed specs that the
CPU may overheat and shut down.

Where you go from here depends a lot on whether or not the unexpected
shutdowns are tolerable. If they're not, (they wouldn't be for me)
you may want to think about swapping out the memory modules for known
good ones. Since memory is currently inexpensive you might want to
pull all four modules and replace two of them and try running the
machine for awhile with less memory to see if that cures the problem.
Memtest86 is a good in house memory tester but not as good as
substitution.

Another remedy might be to replace the motherboard. But if you're
going to do that, you may want to shop around for an upgraded board.
Of course that means a large expenditure but if you're thinking about
upgrading your system, now might be a good time to do it.

Fry's electronics (if there's one in your area) generally has very
good purchases on motherboard kits. Their kits come with CPU and
memory. Of course the price varies depending on the board, CPU,
amount of memory, etc. Something to think about.

I wish you well with your trouble shooting.

Regards.

Don Cohen

February 22nd 04, 02:22 AM

> Hi Don:
>
> I don't believe the low core voltage is the problem. If anything, a
> lower core voltage will usually result in the CPU running a bit
> cooler. It's when the core voltage begins to exceed specs that the
> CPU may overheat and shut down.

Oh well....thought I was on to something....

> Where you go from here depends a lot on whether or not the unexpected
> shutdowns are tolerable.

Completely intolerable. I can't work on a system that could go down without
warning, corrupting and losing data, etc.

> If they're not, (they wouldn't be for me)
> you may want to think about swapping out the memory modules for known
> good ones. Since memory is currently inexpensive you might want to
> pull all four modules and replace two of them and try running the
> machine for awhile with less memory to see if that cures the problem.
> Memtest86 is a good in house memory tester but not as good as
> substitution.

Well, this is do-able. Or I could just take out one at a time, and run
until it crashes or doesn't. Should run ok for most things with 768 mb.

> Another remedy might be to replace the motherboard. But if you're
> going to do that, you may want to shop around for an upgraded board.
> Of course that means a large expenditure but if you're thinking about
> upgrading your system, now might be a good time to do it.
>
> Fry's electronics (if there's one in your area) generally has very
> good purchases on motherboard kits. Their kits come with CPU and
> memory. Of course the price varies depending on the board, CPU,
> amount of memory, etc. Something to think about.

I'm willing to do this, but I worry - could it be the hard drives or optical
drives? If so, I could spend a lot of money and still not fix the problem.

That's why a program like Tuff-Test-Pro (if, in fact it really works, which
I have no data on) seems worth trying. I'm a physician, and would really
like to make a definite diagnosis, and not just keep operating until the
patient gets better (or dies!). Your thoughts on this???

Isn't there some reasonable way to identify the culprit????

> I wish you well with your trouble shooting.

Clearly, I'm going to need it.

(I promise - this is my last set of questions to you).

Don

Doug Knox MS-MVP

February 22nd 04, 03:03 AM

Don,

The voltages for the various components (RAM, CPU and etc.) are =
controlled by voltage regulators on the motherboard. Granted, it could =
be a different component that is having issues, and causing a voltage =
drop across the entire system. It could also simply be the voltage =
regulator that supplies the CPU Core Voltage failing due to age. =20

Try removing all add-on cards, and anything but your primary hard disk =
(you will need to leave the video card in) and retest the system. If =
the voltage is normal, then add the hardware back one piece at a time =
until you see the voltage drop. If you still get the voltage =
difference, even with all extra hardware removed, then you're most =
likely looking at a motherboard replacement.

--=20
Doug Knox, MS-MVP Windows XP/ Windows Smart Display
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.
=20
"Don Cohen" > wrote in message =
...
> Hi,
>=20
> This is a fresh thread based on what was learned in a separate thread
> (Desperately Need Help - System Reboot/Crashes).
>=20
> The tentative conclusion in the other thread is that my crashes are =
being
> caused by hardware, and not software. In that regard, I have =
installed and
> run AIDA32 Enterprise System Information. Here is the relevant =
information:
>=20
> My primary problem is random, sporadic crashes to a BSOD, starting =
after
> almost 2 years of relatively glitch-free running, and *not* following =
any
> significant hardware or software changes:
>=20
> PAGE_FAULT_IN_NONPAGED_AREA
> ****STOP: 0x00000050 (0xB7874E5E, 0x00000000, 0xB7874E5E, 0x00000000)
>=20
> Full details on this problem and prior trouble-shooting can be found =
in the
> other thread.
>=20
> Gateway 700XL, approximately 2 years old, XP Home, 1024 mb RAM
> Intel Pentium 4A, 2.2 GHz (5.5x400), Northwood A80532 CPU chip
> Intel D850MV (Maryville) Motherboard, i850 Chipset
> Brand new Antec 430W TruPower PSU (replacing the prior Gateway 250W =
PSU, but
> not fixing the crashes)
>=20
> AIDA32 shows the actual CPU Core Voltage for my system varying between =
1.43
> and 1.45 Volts.
> AIDA32 also has a section showing the CPU Physical Properties. Here =
it
> indicates:
> --Core Voltage 1.475V - 1.55V--
>=20
> Someone experiencing similar (but not identical) crashes as me found =
his CPU
> Core Voltage to be the source of his problem, indicating his opinion =
that
> voltage differences as small as 0.025V can be quite significant. If =
true,
> then my CPU Core Voltage is out of the normal range.
>=20
> My questions:
>=20
> 1. Is the difference between the apparent optimal range for Core =
Voltage and
> my actual Core Voltage enough to explain these very random crashes? (I =
can
> go a few minutes, a few hours, a few days between crashes).
>=20
> 2. Is there any way to adjust this voltage? I have not yet found any =
BIOS
> or motherboard jumper settings that might do this.
>=20
> 3. If this is the source of the problem, do I replace the motherboard, =
or
> the CPU? In other words, which hardware component is causing the low =
CPU
> Core Voltage?
>=20
> Anybody that can offer some knowledgeable advice here? It will be =
very
> greatly appreciated. I have been fighting this problem for several =
weeks
> now, and consumed untold hours trouble-shooting.
>=20
> Thanks!
>=20
> Don
>=20
>

PWY

February 22nd 04, 03:03 AM

"Don Cohen" > wrote in message
...
> > Hi Don:
> >
> > I don't believe the low core voltage is the problem. If anything, a
> > lower core voltage will usually result in the CPU running a bit
> > cooler. It's when the core voltage begins to exceed specs that the
> > CPU may overheat and shut down.
>
> Oh well....thought I was on to something....
>
> > Where you go from here depends a lot on whether or not the unexpected
> > shutdowns are tolerable.
>
> Completely intolerable. I can't work on a system that could go down
without
> warning, corrupting and losing data, etc.
>
> > If they're not, (they wouldn't be for me)
> > you may want to think about swapping out the memory modules for known
> > good ones. Since memory is currently inexpensive you might want to
> > pull all four modules and replace two of them and try running the
> > machine for awhile with less memory to see if that cures the problem.
> > Memtest86 is a good in house memory tester but not as good as
> > substitution.
>
> Well, this is do-able. Or I could just take out one at a time, and run
> until it crashes or doesn't. Should run ok for most things with 768 mb.
>
> > Another remedy might be to replace the motherboard. But if you're
> > going to do that, you may want to shop around for an upgraded board.
> > Of course that means a large expenditure but if you're thinking about
> > upgrading your system, now might be a good time to do it.
> >
> > Fry's electronics (if there's one in your area) generally has very
> > good purchases on motherboard kits. Their kits come with CPU and
> > memory. Of course the price varies depending on the board, CPU,
> > amount of memory, etc. Something to think about.
>
> I'm willing to do this, but I worry - could it be the hard drives or
optical
> drives? If so, I could spend a lot of money and still not fix the
problem.
>
> That's why a program like Tuff-Test-Pro (if, in fact it really works,
which
> I have no data on) seems worth trying. I'm a physician, and would really
> like to make a definite diagnosis, and not just keep operating until the
> patient gets better (or dies!). Your thoughts on this???
>
> Isn't there some reasonable way to identify the culprit????
>
> > I wish you well with your trouble shooting.
>
> Clearly, I'm going to need it.
>
> (I promise - this is my last set of questions to you).
>
> Don

Don:

Sorry to but in on this fishing expedition but it seems to me the only thing
common to all your events is the CD Rom you were using with the Windows
disk. Try unplugging it and see if problems continue. A long shot I know but
cheap to try.

Pwy

Bob Dietz

February 22nd 04, 03:24 AM

CS wrote:
> On Sat, 21 Feb 2004 19:11:11 -0500, "Don Cohen"
> > wrote:
>
>
>>>Nothing like going crazy trying to track something like this down....
>>
>>Boy, is that the truth. It has consumed an incredible amount of time and
>>mental energy.
>>
>>
>>>From reading your posts and replies and what you've already done to
>>>trouble shoot the problem, I believe it is very definitely a hardware
>>>issue.
>>
>>I appreciate the confirmation. That seems like the only logical conclusion,
>>but we all know how strange the truth can be at times...
>>
>>
>>>I would suggest you not spend any more money on diagnostic programs or
>>>the like. Of course a free one is always great to have. I'm not
>>>sure I really trust AIDA32 to accurately monitor CPU voltages. The
>>>best free application that I know of to do that is called "Motherboard
>>>Monitor". You might wish to download and give it a try. Also, go to
>>>the CPU makers web site and get the specs for your CPU. Both Intel
>>>and AMD have spec sheets available which give the voltage and
>>>temperature ranges for the CPUs they manufacture.
>>
>>OK, I've downloaded and installed Motherboard Monitor. Definitely more
>>complex than AIDA32 to setup. But I think I have it now.
>>
>>It shows Core Temp for CPU varying between 1.46V and 1.49V. I checked
>>Intel's site, found my chip (SL66S) and it shows the spec for Core Voltage
>>as 1.500V. So according to MbMonitor my core voltage is still on the low
>>side, but how significant this 0.1 to 0.4 volts is, I don't know.

NOT 0.1 - 0.4 volts, but 0.01 - 0.04 volts. And the DA converters that
MbMontior and AIDA32 are reading generally don't have that degree of accuracy.
Accuracy would something like 1.46V to 1.49V plus or minus 0.1V at best.

If you want some what accurate measurements, test with a digital multi-meter
at the ATX power connector. You cannot test the core voltage directly at that
connector, but the core voltage is derived from the +3.3 volt line. You'd need
special ($$$) equipment to accurately measure core voltage.

>>
>>Regarding additional diagnostic programs - I'd rather not buy more as well,
>>but at this point, I still don't have an answer as to what hardware is
>>faulty, and what to replace...
>>
>>
>>>You may indeed have a bad motherboard or at least an intermittent
>>>failing component on the board. It may even be memory related. I
>>>don't recall you saying you swapped out the memory modules? Also, go
>>>into your CMOS setup program and make sure all the settings for memory
>>>are within specs. (CAS, RAS, etc)

His Gateway motherboard is somewhat lacking in the bios configuration department.

>>
>>I haven't done anything yet with the actual (4) memory modules. Memtest86
>>ran for over 13 hours/7passes, with no errors detected.

Your MB uses RDRAM which is used in pairs.
Call the modules A1,A2 and B1,B2.
Call the slots they are in 1,2,3 and 4.
Swap A1,A2 from slots 1,2 to slots 3,4
and B1,B2 from slots 3,4 to slots 1,2.

While you're swapping the sticks (especially if you or someone in your
household is a smoker!), use SOFT (not for #1 pencil or ink) eraser to
clean the contacts.

Re-run Memtest86. If Memtest finds an error, replace the appropriate ram
module(s). If no errors are found, run the computer normally to see if
cleaning the contacts has fixed the intermitant spontaneous reboots.

Bob

Don Cohen

February 22nd 04, 03:50 AM

Hi Doug,

Thanks for the reply and advice.

I presume that you feel the voltage measurements are sufficiently accurate
with "Motherboard Monitor" and/or AIDA32 to conclude that the VCore is
genuinely lower than it should be?

And if so, you also feel this small but significant difference could be
creating the system instability?

I will go ahead and give your plan a try tomorrow, and report back.

Thanks much!

Best regards,

Don

"Doug Knox MS-MVP" > wrote in message
...
Don,

The voltages for the various components (RAM, CPU and etc.) are controlled
by voltage regulators on the motherboard. Granted, it could be a different
component that is having issues, and causing a voltage drop across the
entire system. It could also simply be the voltage regulator that supplies
the CPU Core Voltage failing due to age.

Try removing all add-on cards, and anything but your primary hard disk (you
will need to leave the video card in) and retest the system. If the voltage
is normal, then add the hardware back one piece at a time until you see the
voltage drop. If you still get the voltage difference, even with all extra
hardware removed, then you're most likely looking at a motherboard
replacement.

--
Doug Knox, MS-MVP Windows XP/ Windows Smart Display
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.

"Don Cohen" > wrote in message
...
> Hi,
>
> This is a fresh thread based on what was learned in a separate thread
> (Desperately Need Help - System Reboot/Crashes).
>
> The tentative conclusion in the other thread is that my crashes are being
> caused by hardware, and not software. In that regard, I have installed
and
> run AIDA32 Enterprise System Information. Here is the relevant
information:
>
> My primary problem is random, sporadic crashes to a BSOD, starting after
> almost 2 years of relatively glitch-free running, and *not* following any
> significant hardware or software changes:
>
> PAGE_FAULT_IN_NONPAGED_AREA
> ****STOP: 0x00000050 (0xB7874E5E, 0x00000000, 0xB7874E5E, 0x00000000)
>
> Full details on this problem and prior trouble-shooting can be found in
the
> other thread.
>
> Gateway 700XL, approximately 2 years old, XP Home, 1024 mb RAM
> Intel Pentium 4A, 2.2 GHz (5.5x400), Northwood A80532 CPU chip
> Intel D850MV (Maryville) Motherboard, i850 Chipset
> Brand new Antec 430W TruPower PSU (replacing the prior Gateway 250W PSU,
but
> not fixing the crashes)
>
> AIDA32 shows the actual CPU Core Voltage for my system varying between
1.43
> and 1.45 Volts.
> AIDA32 also has a section showing the CPU Physical Properties. Here it
> indicates:
> --Core Voltage 1.475V - 1.55V--
>
> Someone experiencing similar (but not identical) crashes as me found his
CPU
> Core Voltage to be the source of his problem, indicating his opinion that
> voltage differences as small as 0.025V can be quite significant. If true,
> then my CPU Core Voltage is out of the normal range.
>
> My questions:
>
> 1. Is the difference between the apparent optimal range for Core Voltage
and
> my actual Core Voltage enough to explain these very random crashes? (I can
> go a few minutes, a few hours, a few days between crashes).
>
> 2. Is there any way to adjust this voltage? I have not yet found any BIOS
> or motherboard jumper settings that might do this.
>
> 3. If this is the source of the problem, do I replace the motherboard, or
> the CPU? In other words, which hardware component is causing the low CPU
> Core Voltage?
>
> Anybody that can offer some knowledgeable advice here? It will be very
> greatly appreciated. I have been fighting this problem for several weeks
> now, and consumed untold hours trouble-shooting.
>
> Thanks!
>
> Don
>
>

Don Cohen

February 22nd 04, 03:50 AM

Hi Bob,

> NOT 0.1 - 0.4 volts, but 0.01 - 0.04 volts. And the DA converters that
> MbMontior and AIDA32 are reading generally don't have that degree of
accuracy.
> Accuracy would something like 1.46V to 1.49V plus or minus 0.1V at best.
>
> If you want some what accurate measurements, test with a digital
multi-meter
> at the ATX power connector. You cannot test the core voltage directly at
that
> connector, but the core voltage is derived from the +3.3 volt line. You'd
need
> special ($$$) equipment to accurately measure core voltage.

A bit beyond my capabilities at the moment ;-)

> His Gateway motherboard is somewhat lacking in the bios configuration
department.

So I've found...

> Your MB uses RDRAM which is used in pairs.
> Call the modules A1,A2 and B1,B2.
> Call the slots they are in 1,2,3 and 4.
> Swap A1,A2 from slots 1,2 to slots 3,4
> and B1,B2 from slots 3,4 to slots 1,2.
>
> While you're swapping the sticks (especially if you or someone in your
> household is a smoker!), use SOFT (not for #1 pencil or ink) eraser to
> clean the contacts.
>
> Re-run Memtest86. If Memtest finds an error, replace the appropriate ram
> module(s). If no errors are found, run the computer normally to see if
> cleaning the contacts has fixed the intermitant spontaneous reboots.

Will do.

Thanks!

Don

Don Cohen

February 22nd 04, 04:03 AM

> Sorry to but in on this fishing expedition but it seems to me the only
thing
> common to all your events is the CD Rom you were using with the Windows
> disk. Try unplugging it and see if problems continue. A long shot I know
but
> cheap to try.

No problem - join the party!

I'll add this to the list of things to try tomorrow.

Hopefully I'll come up with the answer sooner or later!

Don

Doug Knox MS-MVP

February 22nd 04, 04:41 AM

Its possible, Don. Its also possible that the monitoring circuit is =
what's flaky, but that shouldn't cause a reboot, unless your BIOS would =
support turning off the computer to prevent damage, but then it should =
shut down. When you're dealing with voltages that low, there's not a =
lot of room for error.

--=20
Doug Knox, MS-MVP Windows XP/ Windows Smart Display
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.
=20
"Don Cohen" > wrote in message =
...
> Hi Doug,
>=20
> Thanks for the reply and advice.
>=20
> I presume that you feel the voltage measurements are sufficiently =
accurate
> with "Motherboard Monitor" and/or AIDA32 to conclude that the VCore is
> genuinely lower than it should be?
>=20
> And if so, you also feel this small but significant difference could =
be
> creating the system instability?
>=20
> I will go ahead and give your plan a try tomorrow, and report back.
>=20
> Thanks much!
>=20
> Best regards,
>=20
> Don
>=20
> "Doug Knox MS-MVP" > wrote in message
> ...
> Don,
>=20
> The voltages for the various components (RAM, CPU and etc.) are =
controlled
> by voltage regulators on the motherboard. Granted, it could be a =
different
> component that is having issues, and causing a voltage drop across the
> entire system. It could also simply be the voltage regulator that =
supplies
> the CPU Core Voltage failing due to age.
>=20
> Try removing all add-on cards, and anything but your primary hard disk =
(you
> will need to leave the video card in) and retest the system. If the =
voltage
> is normal, then add the hardware back one piece at a time until you =
see the
> voltage drop. If you still get the voltage difference, even with all =
extra
> hardware removed, then you're most likely looking at a motherboard
> replacement.
>=20
> --=20
> Doug Knox, MS-MVP Windows XP/ Windows Smart Display
> Win 95/98/Me/XP Tweaks and Fixes
> http://www.dougknox.com
> --------------------------------
> Per user Group Policy Restrictions for XP Home and XP Pro
> http://www.dougknox.com/xp/utils/xp_securityconsole.htm
> --------------------------------
> Please reply only to the newsgroup so all may benefit.
> Unsolicited e-mail is not answered.
>=20
> "Don Cohen" > wrote in message
> ...
> > Hi,
> >
> > This is a fresh thread based on what was learned in a separate =
thread
> > (Desperately Need Help - System Reboot/Crashes).
> >
> > The tentative conclusion in the other thread is that my crashes are =
being
> > caused by hardware, and not software. In that regard, I have =
installed
> and
> > run AIDA32 Enterprise System Information. Here is the relevant
> information:
> >
> > My primary problem is random, sporadic crashes to a BSOD, starting =
after
> > almost 2 years of relatively glitch-free running, and *not* =
following any
> > significant hardware or software changes:
> >
> > PAGE_FAULT_IN_NONPAGED_AREA
> > ****STOP: 0x00000050 (0xB7874E5E, 0x00000000, 0xB7874E5E, =
0x00000000)
> >
> > Full details on this problem and prior trouble-shooting can be found =
in
> the
> > other thread.
> >
> > Gateway 700XL, approximately 2 years old, XP Home, 1024 mb RAM
> > Intel Pentium 4A, 2.2 GHz (5.5x400), Northwood A80532 CPU chip
> > Intel D850MV (Maryville) Motherboard, i850 Chipset
> > Brand new Antec 430W TruPower PSU (replacing the prior Gateway 250W =
PSU,
> but
> > not fixing the crashes)
> >
> > AIDA32 shows the actual CPU Core Voltage for my system varying =
between
> 1.43
> > and 1.45 Volts.
> > AIDA32 also has a section showing the CPU Physical Properties. Here =
it
> > indicates:
> > --Core Voltage 1.475V - 1.55V--
> >
> > Someone experiencing similar (but not identical) crashes as me found =
his
> CPU
> > Core Voltage to be the source of his problem, indicating his opinion =
that
> > voltage differences as small as 0.025V can be quite significant. If =
true,
> > then my CPU Core Voltage is out of the normal range.
> >
> > My questions:
> >
> > 1. Is the difference between the apparent optimal range for Core =
Voltage
> and
> > my actual Core Voltage enough to explain these very random crashes? =
(I can
> > go a few minutes, a few hours, a few days between crashes).
> >
> > 2. Is there any way to adjust this voltage? I have not yet found =
any BIOS
> > or motherboard jumper settings that might do this.
> >
> > 3. If this is the source of the problem, do I replace the =
motherboard, or
> > the CPU? In other words, which hardware component is causing the =
low CPU
> > Core Voltage?
> >
> > Anybody that can offer some knowledgeable advice here? It will be =
very
> > greatly appreciated. I have been fighting this problem for several =
weeks
> > now, and consumed untold hours trouble-shooting.
> >
> > Thanks!
> >
> > Don
> >
> >
>=20
>

Don Cohen

February 22nd 04, 05:31 AM

Thanks, Doug.

I'll report back tomorrow on what happens with the experiment you suggest.

I went ahead and switched the RAM modules as one of the other posters
suggested, and will run memtest86 again overnight.

Somehow, I have to fix this darn thing!

All the best,

Don

"Doug Knox MS-MVP" > wrote in message
...
Its possible, Don. Its also possible that the monitoring circuit is what's
flaky, but that shouldn't cause a reboot, unless your BIOS would support
turning off the computer to prevent damage, but then it should shut down.
When you're dealing with voltages that low, there's not a lot of room for
error.

Jym

February 22nd 04, 05:31 AM

Your voltages seem to be right where they are suppose to be with the
processor that you have ,and well within the working variance of the
specifications. Researching your stop error seem to point toward system
ram , taking into account the problems that you have posted . Although this
common stop error could be masked by underlying causes. Try one stick at a
time , then replacing more with successful operation. I too believe the best
way to troubleshoot is to pull out all the nonessential hardware and
software and replace one at a time. Good Luck . Jym

"Don Cohen" > wrote in message
...
> Hi Doug,
>
> Thanks for the reply and advice.
>
> I presume that you feel the voltage measurements are sufficiently accurate
> with "Motherboard Monitor" and/or AIDA32 to conclude that the VCore is
> genuinely lower than it should be?
>
> And if so, you also feel this small but significant difference could be
> creating the system instability?
>
> I will go ahead and give your plan a try tomorrow, and report back.
>
> Thanks much!
>
> Best regards,
>
> Don
>
> "Doug Knox MS-MVP" > wrote in message
> ...
> Don,
>
> The voltages for the various components (RAM, CPU and etc.) are controlled
> by voltage regulators on the motherboard. Granted, it could be a
different
> component that is having issues, and causing a voltage drop across the
> entire system. It could also simply be the voltage regulator that
supplies
> the CPU Core Voltage failing due to age.
>
> Try removing all add-on cards, and anything but your primary hard disk
(you
> will need to leave the video card in) and retest the system. If the
voltage
> is normal, then add the hardware back one piece at a time until you see
the
> voltage drop. If you still get the voltage difference, even with all
extra
> hardware removed, then you're most likely looking at a motherboard
> replacement.
>
> --
> Doug Knox, MS-MVP Windows XP/ Windows Smart Display
> Win 95/98/Me/XP Tweaks and Fixes
> http://www.dougknox.com
> --------------------------------
> Per user Group Policy Restrictions for XP Home and XP Pro
> http://www.dougknox.com/xp/utils/xp_securityconsole.htm
> --------------------------------
> Please reply only to the newsgroup so all may benefit.
> Unsolicited e-mail is not answered.
>
> "Don Cohen" > wrote in message
> ...
> > Hi,
> >
> > This is a fresh thread based on what was learned in a separate thread
> > (Desperately Need Help - System Reboot/Crashes).
> >
> > The tentative conclusion in the other thread is that my crashes are
being
> > caused by hardware, and not software. In that regard, I have installed
> and
> > run AIDA32 Enterprise System Information. Here is the relevant
> information:
> >
> > My primary problem is random, sporadic crashes to a BSOD, starting after
> > almost 2 years of relatively glitch-free running, and *not* following
any
> > significant hardware or software changes:
> >
> > PAGE_FAULT_IN_NONPAGED_AREA
> > ****STOP: 0x00000050 (0xB7874E5E, 0x00000000, 0xB7874E5E, 0x00000000)
> >
> > Full details on this problem and prior trouble-shooting can be found in
> the
> > other thread.
> >
> > Gateway 700XL, approximately 2 years old, XP Home, 1024 mb RAM
> > Intel Pentium 4A, 2.2 GHz (5.5x400), Northwood A80532 CPU chip
> > Intel D850MV (Maryville) Motherboard, i850 Chipset
> > Brand new Antec 430W TruPower PSU (replacing the prior Gateway 250W PSU,
> but
> > not fixing the crashes)
> >
> > AIDA32 shows the actual CPU Core Voltage for my system varying between
> 1.43
> > and 1.45 Volts.
> > AIDA32 also has a section showing the CPU Physical Properties. Here it
> > indicates:
> > --Core Voltage 1.475V - 1.55V--
> >
> > Someone experiencing similar (but not identical) crashes as me found his
> CPU
> > Core Voltage to be the source of his problem, indicating his opinion
that
> > voltage differences as small as 0.025V can be quite significant. If
true,
> > then my CPU Core Voltage is out of the normal range.
> >
> > My questions:
> >
> > 1. Is the difference between the apparent optimal range for Core Voltage
> and
> > my actual Core Voltage enough to explain these very random crashes? (I
can
> > go a few minutes, a few hours, a few days between crashes).
> >
> > 2. Is there any way to adjust this voltage? I have not yet found any
BIOS
> > or motherboard jumper settings that might do this.
> >
> > 3. If this is the source of the problem, do I replace the motherboard,
or
> > the CPU? In other words, which hardware component is causing the low
CPU
> > Core Voltage?
> >
> > Anybody that can offer some knowledgeable advice here? It will be very
> > greatly appreciated. I have been fighting this problem for several
weeks
> > now, and consumed untold hours trouble-shooting.
> >
> > Thanks!
> >
> > Don
> >
> >
>
>