Windows 7 BSOD a couple of minutes after power up, then stable after BSOD until power down. HELP!

tearz · Aug 14, 2010

Im getting BSOD some time after power up, dont know what to do
When my computer restarts it works fine and are stable.

It started this behavior when I installed a SSD disk. It has been 6 month stable.
With SSD disk the POST prompted HT Transport failure after BSOD and the data on the SSD disk was corrupted.
Changed to WD Raptor disk and I still get BSOD's, but no POST message and filesystem is ok.

My computer specs are:

Asus M4A79-T motherboard
gainward geforce 465
gainward geforce 275
AMD phenom II X4 965 cpu
4X Corsair XMS3 DDR3 1333MHz 2GB CL9
Western Digital Raptor 150gb hd
Cooler Master Silent Pro M700 700W PSU

posting last 5 minidumps aswell.

Please help

TorrentG · Aug 14, 2010

Unfortunately, I have to tell you that all crash dumps are hardware based 0x124 ones. These do not specify the hardware fault.

Code:

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


Loading Dump File [E:\Temp\Rar$DI01.706\081310-21793-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e10000 PsLoadedModuleList = 0xfffff800`0304de50
Debug session time: Fri Aug 13 12:30:18.130 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:07.846
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, fffffa8007cf88f8, 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: 0000000000000000, Machine Check Exception
Arg2: fffffa8007cf88f8, 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_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031c46f0 fffff800`030caa89 : fffffa80`07cf88d0 fffffa80`06d2c040 fffffa80`00000006 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031c4c10 fffff800`02fac667 : fffffa80`07cf88d0 fffff800`030255f8 fffffa80`06d2c040 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031c4c40 fffff800`02f14c45 : fffff800`03087360 fffffa80`07d58828 fffffa80`07d58820 fffffa80`06d2c040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031c4c80 fffff800`02e8d961 : fffff880`00c30e00 fffff800`02f14c20 fffffa80`06d2c040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031c4cb0 fffff800`03124c06 : 00000560`00000000 fffffa80`06d2c040 00000000`00000080 fffffa80`06d1c040 : nt!ExpWorkerThread+0x111
fffff880`031c4d40 fffff800`02e5ec26 : fffff880`02f64180 fffffa80`06d2c040 fffff880`02f6efc0 00000560`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031c4d80 00000000`00000000 : fffff880`031c5000 fffff880`031bf000 fffff880`037c5540 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_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

1: kd> lm t n
start             end                 module name
fffff800`00b9d000 fffff800`00ba7000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff800`02e10000 fffff800`033ec000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff800`033ec000 fffff800`03435000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`00c00000 fffff880`00c4c000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`00c98000 fffff880`00ca5000   mcupdate mcupdate.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`00ca5000 fffff880`00cb9000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`00cb9000 fffff880`00d17000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00d17000 fffff880`00dd7000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`00e5c000 fffff880`00e6c000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`00e6c000 fffff880`00e86000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00e86000 fffff880`00e8f000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e8f000 fffff880`00eb9000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00eb9000 fffff880`00ec4000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00ec4000 fffff880`00ed8000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00edc000 fffff880`00f80000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f80000 fffff880`00f8f000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f8f000 fffff880`00fc2000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`01000000 fffff880`01009000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`01009000 fffff880`01038000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`01038000 fffff880`0108f000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`0108f000 fffff880`01099000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01099000 fffff880`010a6000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`010a6000 fffff880`010bb000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`010bb000 fffff880`010d0000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`010d0000 fffff880`010d7000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`010d8000 fffff880`011fe000   spcz     spcz.sys     Sun Oct 11 16:55:14 2009 (4AD24632)
fffff880`01200000 fffff880`01230000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`0123c000 fffff880`013df000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`013df000 fffff880`013f2000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`01400000 fffff880`0144c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`0144c000 fffff880`01486000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01486000 fffff880`014c0000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`014c0000 fffff880`014d6000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`014d6000 fffff880`014e4000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`014e4000 fffff880`014ed000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`014ee000 fffff880`0154c000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`0154c000 fffff880`01566000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01566000 fffff880`015d9000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`015d9000 fffff880`015ea000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`015ea000 fffff880`015f4000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`015f4000 fffff880`01600000   dump_ataport dump_ataport.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01600000 fffff880`01612000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01612000 fffff880`0161b000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`0161d000 fffff880`0170f000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0170f000 fffff880`0176f000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`0176f000 fffff880`0179a000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`0179a000 fffff880`017e4000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`017e4000 fffff880`017f4000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`017f4000 fffff880`017fc000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01801000 fffff880`019fe000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
Mini Kernel Dump does not contain unloaded driver list

I suggest updating the bios or firmware for all drives and motherboard involved.

These crashes you've had are so bad that I can't even see more than about 15% of your installed drivers.

This thread should be followed as it is one of the best resources to be found about 0x124 stops:

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

Good luck and please post new crashes as they become available.

You might also try scanning the system with Malwarebytes and letting it remove anything it finds. Spwl.sys might be malware.

Also recommend to uninstall whichever current antivirus you have (in safe mode) as the least stuff installed is going to be helpful to you here until the issue is resolved:

AV Uninstallers - Windows 7 Forums

If you have Daemon Tools installed, uninstall it in the normal method. Then use the installer/uninstaller found here to remove sptd.sys:

Link Removed (Don't use if you don't have Daemon Tools already installed.)

Search

Navigation section

Windows 7 BSOD a couple of minutes after power up, then stable after BSOD until power down. HELP!

tearz

New Member

Attachments

TorrentG

TorrentG

Banned