Windows 7 A fatal hardware error has occurred.

parishpete · Nov 15, 2010

My Hitherto well behaved Win 7 PC keeps coming up with:

A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Unknown Error
Processor ID: 1

The details view of this entry contains further information. (below)

+ System - Provider [ Name] Microsoft-Windows-WHEA-Logger [ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}
EventID 18 Version 0 Level 2 Task 0 Opcode 0 Keywords 0x8000000000000000 - TimeCreated [ SystemTime] 2010-11-15T07:25:27.341000000Z
EventRecordID 299687 - Correlation [ ActivityID] {041B3296-FB8B-4E17-AAC0-FF35AB45BEFC}
- Execution [ ProcessID] 1548 [ ThreadID] 2660
Channel System Computer GWFAC - Security [ UserID] S-1-5-19

- EventData

ErrorSource 3

ApicId 1

MCABank 3

MciStat 0xe20000000000dfcb

MciAddr 0x0

MciMisc 0x0

ErrorType 256

TransactionType 256

Participation 256

RequestType 256

MemorIO 256

MemHierarchyLvl 256

Timeout 256

OperationType 256

Channel 256

Length 864

RawData 435045521002FFFFFFFF0300010000000200000060030000321807000F0B0A140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBA47D132D9684CB0102000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000400000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000058020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000001000000000000000000000000000000000000000000000057010000000000000000000000000000B20F06000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000100000000000000B20F06000008020101200000FFFB8B1700000000000000000000000000000000000000000000000000000000000000000100000002000000C08560309684CB01010000000000000000000000000000000000000003000000CBDF0000000000E2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

It shows four consecutive entries in the event log at each boot up.

Apart from that it seems to make no difference

There are no other entries and no problems with the PC.

I have cleaned out the fans and cooling fins just in case it was a temperature problem but it made no difference.

any thoughts

regards

pete

TorrentG · Nov 15, 2010

Hi.

MCE events mean that there is a hardware issue, perhaps incorrectly set RAM in the bios.

Anyhow, software can sometimes trigger these events. You can post the crash dumps. C:\Windows\Minidump

Copy the files in there to any other folder then zip them and attach the zip to a post.

Also attach a screen shot of CPU-Z spd and memory tabs.

parishpete · Nov 16, 2010

Hi

Minidumps & screenshots are in the W7 zip folder.

I have looked at the BIOS settings for RAM and they are:
Mem config
bank interleaving, channel interleaving, enable clock to all DIMMs - all disabled
Mem hole remapping, power down -enabled
DCT unchanged - always
DRAM timing
all set to auto
EEC config - disabled

The chip in this PC is the good one out of the PC with all the BSOD's. It may not be 100% but the other chip was definitely U/S and a replacement is on the way.

The minidumps are a result of the PC locking up. the disc was spinning, but power down, keyboard & mouse were locked out. All I could do was hit reset.

This might have been due to an unused Nero package that I uninstalled. A related service was left behind and was probably searching for the package and I've since disabled it.

The WHEA errors occur only at first boot, not at restarts and there are always four.

regards

pete

cybercore · Nov 16, 2010

TorrentG is spot on as always, 0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV.

1. Check your current bios settings against those recommended for your CPU.

2. Consider bios upgrade.

3. Could be something not sitting right physically.

(Stop 0x124 - what it means and what to try - Windows 7 Forums)

Old driver to update or to remove it at all:

PxHelp20.sys Mon Apr 25 15:48:02 2005
Px Engine Device Driver for Windows 2000/XP
Sonic Solutions

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\111210-17113-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e55000 PsLoadedModuleList = 0x82f9d810
Debug session time: Fri Nov 12 10:55:28.754 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:08.533
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 8620a5b4, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 8620a5b4, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8af13cc4 82f23fc5 8620a598 82fbcc28 82fbcc20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8af13ce4 82f24def 82fbcc20 8620a598 82fbcc50 nt!WheapProcessWorkQueueItem+0x56
8af13d00 82ec2f3b 82fbcc20 00000000 850d84c0 nt!WheapWorkQueueWorkerRoutine+0x1f
8af13d50 830636d3 00000001 a716c17f 00000000 nt!ExpWorkerThread+0x10d
8af13d90 82f150f9 82ec2e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

Followup: MachineOwner
---------

1: kd> lmsmtn
start    end        module name
839ab000 839f3000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
83b12000 83b1b000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
83ae6000 83aef000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
83aef000 83b12000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
83837000 8383f000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
83881000 8392c000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
89188000 891ad000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
8383f000 83881000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
88f8e000 88feb000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
891ad000 891ba000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
89177000 89188000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
891c5000 891ce000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
891ba000 891c5000   dump_ataport dump_ataport.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
891ce000 891df000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
83b4f000 83b60000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
83b1b000 83b4f000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
88e00000 88e09000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
89145000 89177000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
89350000 89381000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
82e1e000 82e55000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
8913d000 89145000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
80ba7000 80baf000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
88f7b000 88f8e000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
89108000 8912d000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
8381b000 83826000   mcupdate mcupdate.dll Mon Jul 13 19:13:13 2009 (4A5BBF89)
83ad0000 83ae6000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
83800000 83808000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
88f50000 88f7b000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8912d000 8913d000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
89013000 890ca000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
890ca000 89108000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
82e55000 83265000   nt       ntkrpamp.exe Fri Jun 18 23:55:24 2010 (4C1C3FAC)
88e21000 88f50000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
83a4f000 83a60000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
83a1a000 83a44000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
83abb000 83ac2000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
83ac2000 83ad0000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
88feb000 88ff9000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
83826000 83837000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
83b60000 83b64e20   PxHelp20 PxHelp20.sys Mon Apr 25 15:48:02 2005 (426D4972)
893d1000 893fe000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
893c9000 893d1000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
89207000 89350000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
83a44000 83a4f000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
89381000 89389380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
83a60000 83a70000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
83a70000 83abb000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8938a000 893c9000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8392c000 8399d000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
8399d000 839ab000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
839f3000 839fc000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
Mini Kernel Dump does not contain unloaded driver list

parishpete · Nov 16, 2010

Hiya Cybercore

I've never touched the BIOS settings in this PC but I did update to the newest version (501) while I was sorting out the other PC last month.

The current CPU settings are mostly greyed out and unchangeable except for few options. They look right enough though.

I have had the processor cooling block out a couple of times to clean it (last time 2 days ago). If anything was out of place it would have been pushed home. I could take the processor out and inspect the pins but just 1 pin wrong would have upset it big time.

The only thing I've done is pinched the 2 sticks of RAM for the other PC. Whether removing and replacing has upset something I'm not sure.

I'll leave it be until the new stick of RAM arrives for my other PC and put the originals back in this one.

Restarts definitely don't give the hardware error, just the boots from cold.

I've also updated the chipset drivers to the latest for M2N CM DVI M/Bd 630a chipset. I'll worry about the other drivers when the hardware is back in place.

regards

Pete

parishpete · Feb 25, 2011

OK guys,

Back in the saddle!

The bad Win 7 machine has new RAM and is good as gold. Had a small problem with the new external drive which just stayed in use and would't let shutdown happen. By chance I found the problem. I invested in a new gigabit LAN router and the LED's change colour when used in 10/100 which that PC did a couple of times for no reason. Found the cable had a break at the connector. I ran a test and sure enough if the LAN connection was interrupted whilst a backup was taking place across the LAN, the drive lost the plot. New cable, problem solved.

So.. The good PC, subject of this thread. PC now has its original RAM back and continues to behave spot on all day, evey day, except for the WHEA logger event 18. There are still four entries at any boot from cold every day but none at restarts. I've had the processor out and all pins are AOK.
BIOS and MB drivers are up to date. No blue screens, no hangs.

I can't see anything untoward inside the case. Some posts on forums suggest it to be a heat/fan issue, though I can't see that being the case from cold.

I suppose there are two choices; ignore it or ignore it. If there is a problem it must be inside the chip or on the board circuit and it will either work forever or give up. Unless of course you know different...

regards

Pete

cybercore · Feb 25, 2011

http://windows7forums.com/blue-scre...mportant-every-thread-starter-please-see.html

a) CPU-Z memory tab snip
b) RamMon txt report

parishpete · Feb 26, 2011

]Hi Cybercore

Clips and text file attached.

The speed and voltages reported are as per AData specs.

Only one thing sticks out; the date of manufacture of one of the sticks is wrong or not reported

regards

Pete

cybercore · Feb 26, 2011

RAM is slightly underclocked, 774Mhz while you need it 800Mhz. Make the necessary adjustments in the Bios --> Dram.

parishpete · Feb 26, 2011

Interesting..

DRAM has only two configerable settings:

Clock mode, currently set to auto. (manual has 5 settings; 200,266.333,400 & 533)

and DRAM timing mode, currently set to auto. or DCT 0 which has of raft of settings I don't recognise.

Can you give me a clue please?

MB is an ASUS M2N CM DVI

regards

Pete

cybercore · Feb 26, 2011

Pete said:
(manual has 5 settings; 200,266.333,400 & 533)

You need 400. Set, save, reboot, and attach your new CPU-Z memory tab snapshot.

parishpete · Feb 26, 2011

Duly changed. Notice memory speed still shows 387.6. Have re-checked bios and is definitely set manual to 400.

shots attached

regards

Pete

cybercore · Feb 26, 2011

parishpete said:
Duly changed. Notice memory speed still shows 387.6. Have re-checked bios and is definitely set manual to 400.

shots attached

regards

Pete

More than strange, is the voltage 1.8v?

parishpete · Feb 26, 2011

Voltage is 1.8v according to CPU-Z.

Manufacturers spec is 1.8V.

Spec attached

Regards

Pete

cybercore · Feb 26, 2011

Pete said:
Voltage is 1.8v according to CPU-Z.

Manufacturers spec is 1.8V.

Pete, my question is whether the RAM voltage is currently set 1.8v in your bios?

parishpete · Feb 26, 2011

Cybercore,

It's set to auto.

Manual range is only 1.9v to 2.2v

regards

pete

cybercore · Feb 26, 2011

Cybercore,

It's set to auto.

Manual range is only 1.9v to 2.2v

That's the problem, Pete. Your RAM needs 1.8v.

parishpete · Feb 27, 2011

That's ironic!

The PC is "as built" except for fact that 1 stick of RAM came from the other PC and the other is the replacement from AData.

The original RAM is the same spec but under the budget VData label by the same manufacturer. This too is listed as 1.8v. That's in the other PC.

I wonder if the problem lies in a BIOS update.

At the time I was having all the BSOD trouble with the other PC this one was was perfect, no event errors at all. It was only after we cured that one that I updated the BIOS on this one.

I did remove the processor and fins at one point to have a good clean up, but it is definitely seated OK.

I will check out the original user guide and ask the question of ASUS.

regards

Pete

cybercore · Feb 27, 2011

You have 2 A-Data sticks, from different batches. Their rates are identical -- PC 6400 DDR800Mhz 5-5-5-18 1.8v. The sticks should work fine if they are set according to their rated specs.

Two problems:

#1 Right now your RAM frequency is underclocked 774Mhz which is not good.
#2 The sticks need 1.8v,

It's set to auto.

Manual range is only 1.9v to 2.2v

You can reinstall your system and change the hard drives, but it won't help if RAM is set wrong.

Edit:

Reflashing bios might help. Re-attach cpu-z memory and rammon then.

parishpete · Feb 27, 2011

Reflashed bios and checked CPU-Z & Rammon. one small change in CPU-Zfrom 387.6 down to 387.5! no change in Rammon.

Have put a thread on The Asus forum.

Have noticed that original user guide shows voltage choices; 1.90, 1.95, 2.0, 2.05, 2.10, 2.15, 2.2. 2.25.

I have only 1.9, 2.0, 2.1, 2.2. Must be a BIOS change.

will see what ASUS forum comes up with.

Regards

Pete

Windows 7 A fatal hardware error has occurred.

New Member

Banned

New Member

Attachments

New Member

New Member

New Member

New Member

New Member

Attachments

New Member

New Member

New Member

New Member

Attachments

New Member

New Member

Attachments

New Member

New Member

New Member

New Member

New Member

New Member

Similar threads