«

Every time when I resume my PC from hibernations, I get an error message
saying "Machine Check Error" melding. It looks like a regular messagebox
with a red X, so it's not a BSOD or anything. When clicking OK, the PC
functions normally. In the BIOS, everything is set to default/auto, as far
as overclocking settings are concerned. The problem first occurred
yesterday, when I upgraded my Athlon64 3000+ to an Athlon64 X2 4400+
dualcore CPU.

Configuration is as follows:
- Gigabyte K8N Pro-SLI
- 2x 1GB Crucial DDR400
- Radeon X800 XT
- Athlon64 X2 4400+
- Windows XP Pro x64

In the event log, I always get this message:
http://thany.org/screenshots/Screenshot881.png

And *sometimes* also these:
http://thany.org/screenshots/Screenshot882.png
http://thany.org/screenshots/Screenshot883.png
Although I can't yet pinpoint *when* I get these disturbing-looking erros...

I've seen a lot go wrong with Windowses, but this is kinda new for me. I
don't know where I should look now.

I need help

--
Thanks,

Martijn Saly

If this means, you fitted the new processor on the 'old' motherboard (?) -
first thing that comes to mind is a BIOS update! Also, if you didn't do that
already, I would consider re-installing Windows following such an upgrade.

I cannot make reassurances as to those messages, they are said to indicate
hardware errors, but I wouldn't panic until trying those couple of items
first.


Tony. . .

"Martijn Saly" <> wrote in message
news:%...
> Every time when I resume my PC from hibernations, I get an error message
> saying "Machine Check Error" melding. It looks like a regular messagebox
> with a red X, so it's not a BSOD or anything. When clicking OK, the PC
> functions normally. In the BIOS, everything is set to default/auto, as far
> as overclocking settings are concerned. The problem first occurred
> yesterday, when I upgraded my Athlon64 3000+ to an Athlon64 X2 4400+
> dualcore CPU.
>
> Configuration is as follows:
> - Gigabyte K8N Pro-SLI
> - 2x 1GB Crucial DDR400
> - Radeon X800 XT
> - Athlon64 X2 4400+
> - Windows XP Pro x64
>
> In the event log, I always get this message:
> http://thany.org/screenshots/Screenshot881.png
>
> And *sometimes* also these:
> http://thany.org/screenshots/Screenshot882.png
> http://thany.org/screenshots/Screenshot883.png
> Although I can't yet pinpoint *when* I get these disturbing-looking
> erros...
>
> I've seen a lot go wrong with Windowses, but this is kinda new for me. I
> don't know where I should look now.
>
> I need help
>
> --
> Thanks,
>
> Martijn Saly

Tony Sperling wrote:
> If this means, you fitted the new processor on the 'old' motherboard (?) -
> first thing that comes to mind is a BIOS update! Also, if you didn't do that
> already, I would consider re-installing Windows following such an upgrade.
>
> I cannot make reassurances as to those messages, they are said to indicate
> hardware errors, but I wouldn't panic until trying those couple of items
> first.

I already did a BIOS update. But need I remind you that the mainboard
officially supports dualcore Athlons out-of-the-box. So it had to work
without updates. And surprisingly, hardware-wise it does work. Th CPU is
properly recognized by the BIOS, by Windows, even by memtest86. Oh yeah,
memtest86 reports no errors after a full test cycle...

Anyway, a Windows reinstall. I might try if the problem persists after a
reinstall, but even *if* it works around the problem, I'm not going to
reconfigure the whole box just for one "silly" warning message. I want to
fix the problem, rather than work around it. To me, a reinstall is a "if all
else fails and nothing makes sense no more" kind of thing. It's like buying
a new car just because it has a scratch

--
Thanks,

Martijn Saly

Martijn:

Did you install "AMD AthlonT 64 X2 Dual Core Processor Driver
for Windows XP x64 Edition and Windows Server 2003 x64 Editions Version
(exe) 1.2.2. from
http://www.amd.com/us-en/Processors/..._13118,00.html
after you installed the new processor.





"Martijn Saly" <> wrote in message
news:u3o$tF$...
> Tony Sperling wrote:
>> If this means, you fitted the new processor on the 'old' motherboard
>> (?) - first thing that comes to mind is a BIOS update! Also, if you
>> didn't do that already, I would consider re-installing Windows following
>> such an upgrade.
>>
>> I cannot make reassurances as to those messages, they are said to
>> indicate hardware errors, but I wouldn't panic until trying those couple
>> of items first.
>
> I already did a BIOS update. But need I remind you that the mainboard
> officially supports dualcore Athlons out-of-the-box. So it had to work
> without updates. And surprisingly, hardware-wise it does work. Th CPU is
> properly recognized by the BIOS, by Windows, even by memtest86. Oh yeah,
> memtest86 reports no errors after a full test cycle...
>
> Anyway, a Windows reinstall. I might try if the problem persists after a
> reinstall, but even *if* it works around the problem, I'm not going to
> reconfigure the whole box just for one "silly" warning message. I want to
> fix the problem, rather than work around it. To me, a reinstall is a "if
> all else fails and nothing makes sense no more" kind of thing. It's like
> buying a new car just because it has a scratch
>
> --
> Thanks,
>
> Martijn Saly

Dennis Pack x64, IE7B2 wrote:
> Martijn:
>
> Did you install "AMD AthlonT 64 X2 Dual Core Processor Driver
> for Windows XP x64 Edition and Windows Server 2003 x64 Editions Version
> (exe) 1.2.2. from
> http://www.amd.com/us-en/Processors/..._13118,00.html
> after you installed the new processor.

I sure did, but the problem persists...

I also reinstalled the latest nForce x64 drivers, btw.

--
Thanks,

Martijn Saly

Martijn Saly wrote:
> Every time when I resume my PC from hibernations, I get an error message
> saying "Machine Check Error" melding. It looks like a regular messagebox
> with a red X, so it's not a BSOD or anything. When clicking OK, the PC
> functions normally. In the BIOS, everything is set to default/auto, as
> far as overclocking settings are concerned. The problem first occurred
> yesterday, when I upgraded my Athlon64 3000+ to an Athlon64 X2 4400+
> dualcore CPU.
>
> Configuration is as follows:
> - Gigabyte K8N Pro-SLI
> - 2x 1GB Crucial DDR400
> - Radeon X800 XT
> - Athlon64 X2 4400+
> - Windows XP Pro x64
>
> In the event log, I always get this message:
> http://thany.org/screenshots/Screenshot881.png
>
> And *sometimes* also these:
> http://thany.org/screenshots/Screenshot882.png
> http://thany.org/screenshots/Screenshot883.png
> Although I can't yet pinpoint *when* I get these disturbing-looking
> erros...
>
> I've seen a lot go wrong with Windowses, but this is kinda new for me. I
> don't know where I should look now.
>
> I need help

Now I'm being thrown a BSOD with MACHINE_CHECK_EXCEPTION. According to
Microsoft, either my CPU or my memory is bad. And my memory is perfect.

Could it really be that my CPU is bad? I never thought that could happen...

--
Thanks,

Martijn Saly

Sorry, It's really a serious processor error:

Error Machine_Check_Exception http://support.microsoft.com/kb/329284/en-us
And here:
http://support.microsoft.com/kb/162363/en-us


Ivan

"Martijn Saly" <> escribió en el mensaje news:...
> Martijn Saly wrote:
>> Every time when I resume my PC from hibernations, I get an error message
>> saying "Machine Check Error" melding. It looks like a regular messagebox
>> with a red X, so it's not a BSOD or anything. When clicking OK, the PC
>> functions normally. In the BIOS, everything is set to default/auto, as
>> far as overclocking settings are concerned. The problem first occurred
>> yesterday, when I upgraded my Athlon64 3000+ to an Athlon64 X2 4400+
>> dualcore CPU.
>>
>> Configuration is as follows:
>> - Gigabyte K8N Pro-SLI
>> - 2x 1GB Crucial DDR400
>> - Radeon X800 XT
>> - Athlon64 X2 4400+
>> - Windows XP Pro x64
>>
>> In the event log, I always get this message:
>> http://thany.org/screenshots/Screenshot881.png
>>
>> And *sometimes* also these:
>> http://thany.org/screenshots/Screenshot882.png
>> http://thany.org/screenshots/Screenshot883.png
>> Although I can't yet pinpoint *when* I get these disturbing-looking
>> erros...
>>
>> I've seen a lot go wrong with Windowses, but this is kinda new for me. I
>> don't know where I should look now.
>>
>> I need help
>
> Now I'm being thrown a BSOD with MACHINE_CHECK_EXCEPTION. According to
> Microsoft, either my CPU or my memory is bad. And my memory is perfect.
>
> Could it really be that my CPU is bad? I never thought that could happen...
>
> --
> Thanks,
>
> Martijn Saly

CPUs can go bad but this is rare.
AMD x64 CPUs include the memory controller

If the exception is not reported on a normal boot, there is no reason to
suspect faulty memory or CPU.

What is your PSU? The sudden powerload on resume from hibernation may be
producing a power fluctuation which is interpreted as a system fault with
the new and faster CPU, but would have settled before the old and slower CPU
was ready.


"Martijn Saly" <> wrote in message
news:...
> Martijn Saly wrote:
>> Every time when I resume my PC from hibernations, I get an error message
>> saying "Machine Check Error" melding. It looks like a regular messagebox
>> with a red X, so it's not a BSOD or anything. When clicking OK, the PC
>> functions normally. In the BIOS, everything is set to default/auto, as
>> far as overclocking settings are concerned. The problem first occurred
>> yesterday, when I upgraded my Athlon64 3000+ to an Athlon64 X2 4400+
>> dualcore CPU.
>>
>> Configuration is as follows:
>> - Gigabyte K8N Pro-SLI
>> - 2x 1GB Crucial DDR400
>> - Radeon X800 XT
>> - Athlon64 X2 4400+
>> - Windows XP Pro x64
>>
>> In the event log, I always get this message:
>> http://thany.org/screenshots/Screenshot881.png
>>
>> And *sometimes* also these:
>> http://thany.org/screenshots/Screenshot882.png
>> http://thany.org/screenshots/Screenshot883.png
>> Although I can't yet pinpoint *when* I get these disturbing-looking
>> erros...
>>
>> I've seen a lot go wrong with Windowses, but this is kinda new for me. I
>> don't know where I should look now.
>>
>> I need help
>
> Now I'm being thrown a BSOD with MACHINE_CHECK_EXCEPTION. According to
> Microsoft, either my CPU or my memory is bad. And my memory is perfect.
>
> Could it really be that my CPU is bad? I never thought that could
> happen...
>
> --
> Thanks,
>
> Martijn Saly

Dominic Payer wrote:
> CPUs can go bad but this is rare.
> AMD x64 CPUs include the memory controller
>
> If the exception is not reported on a normal boot, there is no reason to
> suspect faulty memory or CPU.
>
> What is your PSU? The sudden powerload on resume from hibernation may be
> producing a power fluctuation which is interpreted as a system fault with
> the new and faster CPU, but would have settled before the old and slower CPU
> was ready.

PSU is a Super Flower SF-450K-14A. With only two harddrives and a humble
Radeon X800 XT, 450W should be waaay more than enough for my system. I'm not
sure about the detailed specs of the PSU, but I know it can handle a big
load. Because neither playing a modern game, nor stressing both CPU cores to
100% causes any malfunction.

To me, the MACHINE_CHECK_EXCEPTION seems completely at random and completely
out of the blue. the Machine Check Error messagebox is just a reproducable
annoyance with unknown origin...

--
Thanks,

Martijn Saly

Could this be a result of some value in the reg? In the initial stages of
resuming, it may still be looking for 'one' processor?

And yes, I am sorry for using bad language there, when saying 're-install' -
I should have said: repair-install. That at least would have the reg.
updated, I think.

Tony. . .


"Martijn Saly" <> wrote in message
news:...
> Dominic Payer wrote:
>> CPUs can go bad but this is rare.
>> AMD x64 CPUs include the memory controller
>>
>> If the exception is not reported on a normal boot, there is no reason to
>> suspect faulty memory or CPU.
>>
>> What is your PSU? The sudden powerload on resume from hibernation may be
>> producing a power fluctuation which is interpreted as a system fault with
>> the new and faster CPU, but would have settled before the old and slower
>> CPU was ready.
>
> PSU is a Super Flower SF-450K-14A. With only two harddrives and a humble
> Radeon X800 XT, 450W should be waaay more than enough for my system. I'm
> not sure about the detailed specs of the PSU, but I know it can handle a
> big load. Because neither playing a modern game, nor stressing both CPU
> cores to 100% causes any malfunction.
>
> To me, the MACHINE_CHECK_EXCEPTION seems completely at random and
> completely out of the blue. the Machine Check Error messagebox is just a
> reproducable annoyance with unknown origin...
>
> --
> Thanks,
>
> Martijn Saly