Need help to analyse one minidump

StalkeR · 05 Dec 2011

Hello people, I want to help one member at other forum, so he had 0x124 error. I got the dump file, and analysed it.

Code:

0: 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: 856d54dc, 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:  
8a51fcc4 82b1db2d 856d54c0 82bb48c8 82bb48c0 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8a51fce4 82b1e957 82bb48c0 856d54c0 82bb48f0 nt!WheapProcessWorkQueueItem+0x56
8a51fd00 82ac9a6b 82bb48c0 00000000 847f5798 nt!WheapWorkQueueWorkerRoutine+0x1f
8a51fd50 82c54fda 00000001 aa3f3c6a 00000000 nt!ExpWorkerThread+0x10d
8a51fd90 82afd1d9 82ac995e 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_BUS_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

I know that 0x124 is hardware based error, and Windbg also confirm that.

I see VISTA_DRIVER_FAULT, so should I suggest him to do a tests with MemTest, or to use Driver Verifier ?

Or something else, if I'm wrong ?

I also scanned for old drivers:

Code:

kdcom    80bbe000    80bc6000    Tue Jul 14 03:08:58 2009 (4a5bdaaa)    000138b1        kdcom.dll
hal    82a15000    82a4c000    Sat Nov 20 09:37:38 2010 (4ce788d2)    00037fb1    PDB    c:\symcache\halmacpi.pdb\AE605D6C59454802AE1D485E0B089A571\halmacpi.pdb
nt    82a4c000    82e5e000    Thu Jun 23 04:23:05 2011 (4e02a389)    003d3310    PDB    c:\symcache\ntkrpamp.pdb\DF9F0ACF97D44026815CB5CE47A20FA92\ntkrpamp.pdb
mcupdate    88005000    88010000    Tue Jul 14 01:13:13 2009 (4a5bbf89)    0000bd79        mcupdate.dll
PSHED    88010000    88021000    Tue Jul 14 03:09:36 2009 (4a5bdad0)    000108a2    PDB    c:\symcache\pshed.pdb\5ACEAFD8AD3A46FEAD083AFDF675DA391\pshed.pdb
BOOTVID    88021000    88029000    Tue Jul 14 03:04:34 2009 (4a5bd9a2)    00010ff0        BOOTVID.dll
CLFS    88029000    8806b000    Tue Jul 14 01:11:10 2009 (4a5bbf0e)    000461c7        CLFS.SYS
CI    8806b000    88116000    Sat Nov 20 13:05:17 2010 (4ce7b97d)    000adff9        CI.dll
Wdf01000    88116000    88187000    Tue Jul 14 01:11:36 2009 (4a5bbf28)    000717b7        Wdf01000.sys
WDFLDR    88187000    88195000    Tue Jul 14 01:11:25 2009 (4a5bbf1d)    00009df6        WDFLDR.SYS
ACPI    88195000    881dd000    Sat Nov 20 09:37:52 2010 (4ce788e0)    0004f583        ACPI.sys
WMILIB    881dd000    881e6000    Tue Jul 14 01:11:22 2009 (4a5bbf1a)    0000b93d        WMILIB.SYS
msisadrv    881e6000    881ee000    Tue Jul 14 01:11:09 2009 (4a5bbf0d)    0000cd81        msisadrv.sys
pci    8823f000    88269000    Sat Nov 20 09:37:57 2010 (4ce788e5)    0002b72c        pci.sys
vdrvroot    88269000    88274000    Tue Jul 14 01:46:19 2009 (4a5bc74b)    00009326        vdrvroot.sys
partmgr    88274000    88285000    Sat Nov 20 09:38:14 2010 (4ce788f6)    0001bb55        partmgr.sys
volmgr    88285000    88295000    Sat Nov 20 09:38:06 2010 (4ce788ee)    00016e1a        volmgr.sys
volmgrx    88295000    882e0000    Tue Jul 14 01:11:41 2009 (4a5bbf2d)    0004a22a        volmgrx.sys
pciide    882e0000    882e7000    Tue Jul 14 01:11:19 2009 (4a5bbf17)    0000c6dd        pciide.sys
PCIIDEX    882e7000    882f5000    Tue Jul 14 01:11:15 2009 (4a5bbf13)    0000fc04        PCIIDEX.SYS
mountmgr    882f5000    8830b000    Sat Nov 20 09:38:09 2010 (4ce788f1)    00014708        mountmgr.sys
vmbus    8830b000    88334180    Sat Nov 20 10:14:58 2010 (4ce79192)    0002f9e5        vmbus.sys
winhv    88335000    88347000    Sat Nov 20 09:38:15 2010 (4ce788f7)    00010243        winhv.sys
atapi    88347000    88350000    Tue Jul 14 01:11:15 2009 (4a5bbf13)    00014c06        atapi.sys
ataport    88350000    88373000    Sat Nov 20 09:38:00 2010 (4ce788e8)    0002b87f        ataport.SYS
amdxata    88373000    8837c000    Fri Mar 19 17:19:01 2010 (4ba3a3f5)    000147b2        amdxata.sys
fltmgr    8837c000    883b0000    Tue Jul 14 01:11:13 2009 (4a5bbf11)    000382a8        fltmgr.sys
fileinfo    883b0000    883c1000    Tue Jul 14 01:21:51 2009 (4a5bc18f)    0001e423        fileinfo.sys
Ntfs    88408000    88537000    Fri Mar 11 04:21:11 2011 (4d799527)    0012d977        Ntfs.sys
msrpc    88537000    88562000    Tue Jul 14 01:11:59 2009 (4a5bbf3f)    00036b4f        msrpc.sys
ksecdd    88562000    88575000    Sat Nov 20 09:38:54 2010 (4ce7891e)    0001b964        ksecdd.sys
cng    88575000    885d2000    Tue Jul 14 01:32:55 2009 (4a5bc427)    000650c5        cng.sys
pcw    885d2000    885e0000    Tue Jul 14 01:11:10 2009 (4a5bbf0e)    000194cf        pcw.sys
Fs_Rec    885e0000    885e9000    Tue Jul 14 01:11:14 2009 (4a5bbf12)    0000845a        Fs_Rec.sys
ndis    88629000    886e0000    Sat Nov 20 09:39:19 2010 (4ce78937)    000bd48d        ndis.sys
NETIO    886e0000    8871e000    Sat Nov 20 09:40:03 2010 (4ce78963)    0003f253        NETIO.SYS
ksecpkg    8871e000    88743000    Tue Jul 14 01:34:00 2009 (4a5bc468)    00022cb7        ksecpkg.sys
mup    88743000    88753000    Tue Jul 14 01:14:14 2009 (4a5bbfc6)    00014283        mup.sys
hwpolicy    88753000    8875b000    Sat Nov 20 09:37:35 2010 (4ce788cf)    0000b2b9        hwpolicy.sys
fvevol    8875b000    8878d000    Sat Nov 20 09:40:22 2010 (4ce78976)    000390dc        fvevol.sys
disk    8878d000    8879e000    Tue Jul 14 01:11:28 2009 (4a5bbf20)    000152a4        disk.sys
CLASSPNP    8879e000    887c3000    Tue Jul 14 01:11:20 2009 (4a5bbf18)    0002bbfe        CLASSPNP.SYS
crashdmp    887c3000    887d0000    Tue Jul 14 01:45:50 2009 (4a5bc72e)    00010fcb        crashdmp.sys
dump_ataport    887d0000    887db000    Tue Jul 14 01:11:16 2009 (4a5bbf14)    00006f2a        dump_ataport.sys
dump_atapi    887db000    887e4000    Tue Jul 14 01:11:15 2009 (4a5bbf13)    00014c06        dump_atapi.sys
dump_dumpfve    887e4000    887f5000    Tue Jul 14 01:12:47 2009 (4a5bbf6f)    000106ff        dump_dumpfve.sys
rdyboost    88800000    8882d000    Sat Nov 20 10:00:07 2010 (4ce78e17)    000394ea        rdyboost.sys
tcpip    88833000    8897d000    Thu Sep 29 05:22:11 2011 (4e83e463)    0013ea1f        tcpip.sys
fwpkclnt    8897d000    889ae000    Sat Nov 20 09:39:08 2010 (4ce7892c)    0003b983        fwpkclnt.sys
vmstorfl    889ae000    889b6380    Sat Nov 20 10:14:37 2010 (4ce7917d)    000131d0        vmstorfl.sys
volsnap    889b7000    889f6000    Sat Nov 20 09:38:13 2010 (4ce788f5)    0003ca6d        volsnap.sys
spldr    889f6000    889fe000    Mon May 11 18:13:47 2009 (4a084ebb)    0000767d        spldr.sys

And yes, here is that dump file.
Attachment 186977

Thanks.

JMH · 06 Dec 2011

If your friend can.... get him to do these.

1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+

Also this free video stress test: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Next this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

zigzag3143 · 06 Dec 2011

Since the uptime is only 5 seconds it is something very early in the boot. This could be a one off or the beginning of a pattern.

Jan is of course correct in the hardware tests she recommends.

Your friend might also want to run a malwarebytes scan just in case.

StalkeR · 06 Dec 2011

Thanks Jan and Ken. I have already suggested the OP to run a scan with MemTest and SeaTools. I gor feedback, and looks like he have heat problem. The CPU is 70 C, so I'll suggest to clean the pc from dust.
Anyway thanks people. I'll wait to answer again, and I'll post here. :)