bsod minidump

[bobmane]

hi all

I have no idea why...BSOD...It started about a month ago.

i wiped the HDD clean and restored an image from last known good config...

then after a week it happened again today..


today it was actually spontaneous shutdown and reboot...no BSOD ( i don't know if that is different than normal BSOD)



you can see minidump attachedhttp://pro-tools-training.com/Minidump.zip

 

[richc46]

Welcome

It is a code 124

http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Your report

  Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp6_Minidump[1].zip\Minidump\062110-69654-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03059e50
Debug session time: Mon Jun 21 16:39:40.193 2010 (GMT-4)
System Uptime: 0 days 0:00:18.035
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, fffffa8009623788, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
4: 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: 0000000000000000, Machine Check Exception
Arg2: fffffa8009623788, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
 
BUGCHECK_STR:  0x124_GenuineIntel
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`0337e6f0 fffff800`030d6a79 : fffffa80`09623760 fffffa80`07958040 fffff8a0`0000000e 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0337ec10 fffff800`02fb85a7 : fffffa80`09623760 fffff800`030315f8 fffffa80`07958040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0337ec40 fffff800`02f20b85 : fffff800`03093360 fffffa80`09593548 fffffa80`09593540 fffffa80`07958040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0337ec80 fffff800`02e99861 : fffff880`0113de00 fffff800`02f20b60 fffffa80`07958040 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0337ecb0 fffff800`03131a86 : 00000000`00000000 fffffa80`07958040 00000000`00000080 fffffa80`07943040 : nt!ExpWorkerThread+0x111
fffff880`0337ed40 fffff800`02e6ab06 : fffff880`0316a180 fffffa80`07958040 fffff880`031750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0337ed80 00000000`00000000 : fffff880`0337f000 fffff880`03379000 fffff880`03b1d540 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
4: kd> lmtsmn
start             end                 module name
fffff880`00f1c000 fffff880`00f73000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`01102000 fffff880`0110d000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00d99000 fffff880`00da2000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00da2000 fffff880`00dcc000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00cbf000 fffff880`00d7f000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01944000 fffff880`01974000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c61000 fffff880`00cbf000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01000000 fffff880`01073000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`01974000 fffff880`01982000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`0192e000 fffff880`01944000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0198e000 fffff880`01997000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01982000 fffff880`0198e000   dump_ataport dump_ataport.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01997000 fffff880`019aa000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`01159000 fffff880`0116d000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`0110d000 fffff880`01159000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013d6000 fffff880`013e0000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`018f4000 fffff880`0192e000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01400000 fffff880`0144a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`033f8000 fffff800`03441000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`018eb000 fffff880`018f4000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff800`00bac000 fffff800`00bb6000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`013ab000 fffff880`013c5000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`015ab000 fffff880`015d6000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`00c09000 fffff880`00c4d000   mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`01890000 fffff880`018eb000   MDFSYSNT MDFSYSNT.sys Mon Sep 28 15:02:26 2009 (4AC10842)
fffff880`01883000 fffff880`01890000   MDPMGRNT MDPMGRNT.SYS Wed Sep 23 15:23:04 2009 (4ABA7598)
fffff880`00d7f000 fffff880`00d99000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f7c000 fffff880`00f86000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01179000 fffff880`011d7000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`01871000 fffff880`01883000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`00dcc000 fffff880`00dec000   mvsata   mvsata.sys   Thu Feb 22 15:36:25 2007 (45DDFEC9)
fffff880`01459000 fffff880`0154b000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0154b000 fffff880`015ab000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`02e1c000 fffff800`033f8000   nt       ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB)
fffff880`01208000 fffff880`013ab000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`00fc6000 fffff880`00fdb000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f86000 fffff880`00fb9000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e5c000 fffff880`00e63000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00ff0000 fffff880`01000000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013c5000 fffff880`013d6000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00c4d000 fffff880`00c61000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`0116d000 fffff880`01178ae0   PxHlpa64 PxHlpa64.sys Mon Dec 10 18:49:01 2007 (475DD06D)
fffff880`01837000 fffff880`01871000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`013e0000 fffff880`013fd000   sbp2port sbp2port.sys Mon Jul 13 19:19:53 2009 (4A5BC119)
fffff880`010d3000 fffff880`01102000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`015e6000 fffff880`015ee000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`011d7000 fffff880`011fa000   Tpkd     Tpkd.sys     Wed Dec 23 14:32:16 2009 (4B327040)
fffff880`00fb9000 fffff880`00fc6000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`015d6000 fffff880`015e6000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00fdb000 fffff880`00ff0000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01073000 fffff880`010bf000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`00e69000 fffff880`00f0d000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f0d000 fffff880`00f1c000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f73000 fffff880`00f7c000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
Mini Kernel Dump does not contain unloaded driver list

Outdated drivers in use during dump process

mvsata mvsata.sys Thu Feb 22 15:36:25 2007

PxHlpa64 PxHlpa64.sys Mon Dec 10 18:49:01 2007

Replace the outdated drivers above and read the report included above.

 

[bobmane]

thank you

are you saying

1. it could not be software related?

2. it is hardware related and I have to update...which of these:

mvsata mvsata.sys

PxHlpa64 PxHlpa64.sys

 

[Jonathan_King]

thank you

are you saying

1. it could not be software related?

2. it is hardware related and I have to update...which of these:

mvsata mvsata.sys

PxHlpa64 PxHlpa64.sys

It is most likely hardware related, but there is a chance it is software.

Update the above drivers, just to remove that possibility.

Now for some hardware tests. Be absolutely sure to read this article, and heed its suggestions: http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

 

[richc46]

Read from the link presented at the top of my report. Those old drivers should be replaced regardless of the outcome.

 

[bobmane]

which drivers do you mean?

 

[richc46]

mvsata.sys

PxHlpa64.sys


PxHlpa64.sys is part of sonic solutions sonic.com

Mvsats.sys is Mfg by Mavrell semiconductors.

 

[bobmane]

thanks much..i will give that a shot

 

[richc46]

Old drivers should always be replaced, but in this case there will be a lot more to do to get up and working, again. Read the information about code 124, in my first post.

 

[bobmane]

this site ( pxHelp20.sys programs ) says Mvsats.sys is used by software i dont even have....

and mvsata.sys 2/22/2007 i cant find anywhere online

anyway to just find these and delete them from my system?

 

[CarlTR6]

Rather than delete them, I would rename them to PxHlpa64.bak and mvsata.bak. If you should discover you need one or both you can rename again.

 

[richc46]

Great suggestion Carl

 

[CarlTR6]

Thank you, Richard. That suggestion is one born of experience. One of those I wish I had of's.

 

[bobmane]

can you tell me how to find those and rename them?

 

[ttran]

I guess they are in C-->Windows-->System 32-->drivers. To rename them, right click-->rename

 

[CarlTR6]

1. Unhide systems files and folders.

http://www.sevenforums.com/tutorials/394-hidden-files-folders-show-hide.html

I recommend hiding these again when you are finished.

2. Open Windows Explorer and do a search for each of the files. They are probably in C:\Windows\System32\Drivers

I recommend hiding the system files and folders when you are finished.

Tuan and I were posting at the same time.

 

[ttran]

Thanks Carl, perfect explaination!!!

 

[CarlTR6]

And I thank you!

 

[bobmane]

thanks...i updated mvsata and changed PxHlpa64.sys to PxHlpa64.bak


will see how it goes

 

[richc46]

All that have helped wish you luck. But there were more potential problems than just those two drivers.