Random Freezes give BSOD notifications after reset

ACIM · 03 Oct 2010

Windows freezes without any warning signs, have to reset the system from there. Then I'm getting the message that Windows didn't shut down correctly. After normal start-up the pop up screen appears telling that an unexpected error occured (something like that), clicking on it shows the BSOD message.

At the moment 64bit version is installed. Also had a clean install of 32bit but the same problem occured.

It's a pre-installed OEM 7 home premium edition, but did several clean installs (because of the problems) with an original Family Pack 7 disc.

The system is being used as a Digital Audio Workstation in a recording studio so it would be great if someone can help me out with this.

If you need more information please let me know.

cybercore · 03 Oct 2010

Both dumps read:

WHEA_UNCORRECTABLE_ERROR (124)
Hardware fault
X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

Stop 0x124 - what it means and what to try

CPU stress test:

Prime95 - Wikipedia, the free encyclopedia
Free Software - GIMPS
Prime95 64-bit now available - Overclockers Forums

Code:

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


Loading Dump File [F:\a\Minidump\100310-23790-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01e01000 PsLoadedModuleList = 0xfffff800`0203ee50
System Uptime: 0 days 0:00:14.930
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, fffffa8008cbf038, 0, 0}

Probably caused by : hardware

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

2: 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: fffffa8008cbf038, 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`021846f0 fffff800`020bba89 : fffffa80`08cbf010 fffffa80`0796e040 fffff8a0`00000005 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02184c10 fffff800`01f9d667 : fffffa80`08cbf010 fffff800`020165f8 fffffa80`0796e040 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02184c40 fffff800`01f05c45 : fffff800`02078360 fffffa80`088b3828 fffffa80`088b3820 fffffa80`0796e040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02184c80 fffff800`01e7e961 : fffff880`010aae00 fffff800`01f05c20 fffffa80`0796e040 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02184cb0 fffff800`02115c06 : 5fac5fac`b7c4b7c4 fffffa80`0796e040 00000000`00000080 fffffa80`0795a890 : nt!ExpWorkerThread+0x111
fffff880`02184d40 fffff800`01e4fc26 : fffff880`020a4180 fffffa80`0796e040 fffff880`020af0c0 0df30df3`2b4c2b4c : nt!PspSystemThreadStartup+0x5a
fffff880`02184d80 00000000`00000000 : fffff880`02185000 fffff880`0217f000 fffff880`0294b540 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_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

















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


Loading Dump File [F:\a\Minidump\092710-13743-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50
System Uptime: 0 days 0:00:07.489
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading 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, fffffa8008dbc038, 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: fffffa8008dbc038, 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`033706f0 fffff800`02d19a89 : fffffa80`08dbc010 fffffa80`0794bb60 fffff880`03370c38 00000000`00000018 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03370c10 fffff800`02bfb667 : fffffa80`08dbc010 fffff800`02c745f8 fffffa80`0794bb60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03370c40 fffff800`02b63c45 : fffff800`02cd6360 fffffa80`08892cd8 fffffa80`08892cd0 fffffa80`0794bb60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03370c80 fffff800`02adc961 : fffff880`010bfe00 fffff800`02b63c20 fffffa80`0794bb60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03370cb0 fffff800`02d73c06 : 00000000`00000000 fffffa80`0794bb60 00000000`00000080 fffffa80`078b7990 : nt!ExpWorkerThread+0x111
fffff880`03370d40 fffff800`02aadc26 : fffff880`03186180 fffffa80`0794bb60 fffff880`031910c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03370d80 00000000`00000000 : fffff880`03371000 fffff880`0336b000 fffff880`03f2d540 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_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

1: kd> lmtn
start             end                 module name
fffff800`00bb9000 fffff800`00bc3000   kdcom    kdcom.dll    Tue Jul 14 04:31:07 2009 (4A5BDFDB)
fffff800`02a16000 fffff800`02a5f000   hal      hal.dll      Tue Jul 14 04:27:36 2009 (4A5BDF08)
fffff800`02a5f000 fffff800`0303b000   nt       ntkrnlmp.exe Sat Jun 19 07:16:41 2010 (4C1C44A9)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Tue Jul 14 04:32:13 2009 (4A5BE01D)
fffff880`00ccd000 fffff880`00d11000   mcupdate mcupdate.dll Tue Jul 14 04:29:10 2009 (4A5BDF66)
fffff880`00d11000 fffff880`00d25000   PSHED    PSHED.dll    Tue Jul 14 04:32:23 2009 (4A5BE027)
fffff880`00d25000 fffff880`00d83000   CLFS     CLFS.SYS     Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`00d83000 fffff880`00ddf000   volmgrx  volmgrx.sys  Tue Jul 14 02:20:33 2009 (4A5BC141)
fffff880`00e1e000 fffff880`00ec2000   Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F)
fffff880`00ec2000 fffff880`00ed1000   WDFLDR   WDFLDR.SYS   Tue Jul 14 02:19:54 2009 (4A5BC11A)
fffff880`00ed1000 fffff880`00f28000   ACPI     ACPI.sys     Tue Jul 14 02:19:34 2009 (4A5BC106)
fffff880`00f28000 fffff880`00f31000   WMILIB   WMILIB.SYS   Tue Jul 14 02:19:51 2009 (4A5BC117)
fffff880`00f31000 fffff880`00f3b000   msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE)
fffff880`00f3b000 fffff880`00f6e000   pci      pci.sys      Tue Jul 14 02:19:51 2009 (4A5BC117)
fffff880`00f6e000 fffff880`00f7b000   vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB)
fffff880`00f7b000 fffff880`00f90000   partmgr  partmgr.sys  Tue Jul 14 02:19:58 2009 (4A5BC11E)
fffff880`00f90000 fffff880`00fa5000   volmgr   volmgr.sys   Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`00fa5000 fffff880`00fac000   pciide   pciide.sys   Tue Jul 14 02:19:49 2009 (4A5BC115)
fffff880`00fac000 fffff880`00fbc000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 02:19:48 2009 (4A5BC114)
fffff880`00fbc000 fffff880`00fd6000   mountmgr mountmgr.sys Tue Jul 14 02:19:54 2009 (4A5BC11A)
fffff880`00fd6000 fffff880`00fdf000   atapi    atapi.sys    Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`01000000 fffff880`0104a000   fwpkclnt fwpkclnt.sys Tue Jul 14 02:21:08 2009 (4A5BC164)
fffff880`0105a000 fffff880`01084000   ataport  ataport.SYS  Tue Jul 14 02:19:52 2009 (4A5BC118)
fffff880`01084000 fffff880`0108f000   amdxata  amdxata.sys  Tue May 19 20:56:59 2009 (4A12F2EB)
fffff880`0108f000 fffff880`010db000   fltmgr   fltmgr.sys   Tue Jul 14 02:19:59 2009 (4A5BC11F)
fffff880`010db000 fffff880`010ef000   fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481)
fffff880`010ef000 fffff880`0114d000   msrpc    msrpc.sys    Tue Jul 14 02:21:32 2009 (4A5BC17C)
fffff880`0114d000 fffff880`011c0000   cng      cng.sys      Tue Jul 14 02:49:40 2009 (4A5BC814)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Tue Jul 14 02:20:54 2009 (4A5BC156)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Tue Jul 14 02:19:27 2009 (4A5BC0FF)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 02:19:45 2009 (4A5BC111)
fffff880`0124e000 fffff880`013f1000   Ntfs     Ntfs.sys     Tue Jul 14 02:20:47 2009 (4A5BC14F)
fffff880`0143f000 fffff880`01531000   ndis     ndis.sys     Tue Jul 14 02:21:40 2009 (4A5BC184)
fffff880`01531000 fffff880`01591000   NETIO    NETIO.SYS    Fri Apr 09 05:43:59 2010 (4BBE946F)
fffff880`01591000 fffff880`015bc000   ksecpkg  ksecpkg.sys  Fri Dec 11 08:03:32 2009 (4B21E0B4)
fffff880`01602000 fffff880`017ff000   tcpip    tcpip.sys    Mon Jun 14 06:39:04 2010 (4C15A458)
fffff880`01863000 fffff880`018af000   volsnap  volsnap.sys  Tue Jul 14 02:20:08 2009 (4A5BC128)
fffff880`018af000 fffff880`018b7000   spldr    spldr.sys    Mon May 11 19:56:27 2009 (4A0858BB)
fffff880`018b7000 fffff880`018f1000   rdyboost rdyboost.sys Tue Jul 14 02:34:34 2009 (4A5BC48A)
fffff880`018f1000 fffff880`01903000   mup      mup.sys      Tue Jul 14 02:23:45 2009 (4A5BC201)
fffff880`01903000 fffff880`0190c000   hwpolicy hwpolicy.sys Tue Jul 14 02:19:22 2009 (4A5BC0FA)
fffff880`0190c000 fffff880`01946000   fvevol   fvevol.sys   Sat Sep 26 05:34:26 2009 (4ABD7DB2)
fffff880`01946000 fffff880`0195c000   disk     disk.sys     Tue Jul 14 02:19:57 2009 (4A5BC11D)
fffff880`0195c000 fffff880`0198c000   CLASSPNP CLASSPNP.SYS Tue Jul 14 02:19:58 2009 (4A5BC11E)
fffff880`0198c000 fffff880`0199a000   crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD)
fffff880`0199a000 fffff880`019a6000   dump_ataport dump_ataport.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`019a6000 fffff880`019af000   dump_atapi dump_atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
fffff880`019af000 fffff880`019c2000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F)
Mini Kernel Dump does not contain unloaded driver list

ACIM · 05 Oct 2010

Thanks for your help so far,

I did a 5 hours memtest with no errors.

Also ran the latest 64bit version of Prime95, this froze my system within about 10 minutes. Will do some more tests with this program later and report it here.

ACIM · 06 Oct 2010

Did some extensive prime95 testing yesterday without any problem.

Got a BSOD a minute ago (.zip included) just browsing the web, clock interrupt was not received on a secondary processor within the allocated time interval.

I really don't have the knowledge to solve this myself. Does anyone have any new insight with the added .zip file?

CarlTR6 · 06 Oct 2010

This is another error code 124.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008d328f8, 0, 0}

Probably caused by : hardware

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

Follow the troubleshooting guide in the link cybercore gave you. Test your temps with Speedfan.

ACIM · 06 Oct 2010

Will do a Vanilla install....

How can I tell the motherboard isn't overclocked?
Is it wise to set bios settings to default?

CarlTR6 · 06 Oct 2010

See if your CPU and RAM are overclocked; you can check this in BIOS.

ACIM · 06 Oct 2010

Ok, I'm back, on a clean install. I also did set the bios back to default settings (I don't think it was overclocked by the way).

Should I start doing tests or just wait and see what will happen?

CarlTR6 · 06 Oct 2010

Just wait and see what happens. You have reinstalled Windows. If the BSOD's start occurring, you will know it is hardware and then start testing.

cybercore · 07 Oct 2010

Yup, those latest 3 all as one say:

BugCheck 124, {0, fffffa8008cbf038, 0, 0}
X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

In theory, your CPU or a memory stick may not be sitting right - you know like a bent pin, but I doubt this is the case. I would try bios upgrade, a chance it'll help. If you go upgrading bios make sure you get the right version for your motherboard. Also, check all CPU settings in bios, even check the memory timings.