Daily BSODs, BCCode 124, Windows 7

phidelt649 · 11 Jul 2011

A few days ago, my computer started shutting down at random intervals. I've run a full Kaspersky Scan and found nothing. I've added nothing new since April (when I installed a new PSU and Wireless PCI card). I'm not sure if it matters or not, but a month ago, my PC wouldn't wake up from hibernation, so I replaced the PSU and turned off the power management system.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8004C362F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\070411-29172-01.dmp
C:\Users\Chad\AppData\Local\Temp\WER-125097-0.sysdata.xml

Still crashing though. Got one today. Has been up and running normal for about five hours now. Updated my video card's drivers and ran four passes of Memtest86. Currently have Firefox, Itunes, Illustrator, Photoshop and Explorer open, so I don't think it is a stress thing. Then I got this:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8004DE0038
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\071011-21481-01.dmp
C:\Users\Chad\AppData\Local\Temp\WER-62650-0.sysdata.xml

Here is what BlueScreenViewer is giving me:

==================================================
Dump File : 071011-21481-01.dmp
Crash Time : 7/10/2011 11:51:34 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04de0038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b18cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor : x64
Crash Address : ntoskrnl.exe+4b18cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071011-21481-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 070711-22448-01.dmp
Crash Time : 7/7/2011 2:06:56 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04ea1038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b18cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor : x64
Crash Address : ntoskrnl.exe+4b18cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070711-22448-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 062411-32931-01.dmp
Crash Time : 6/24/2011 9:49:49 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04d3b8f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b18cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor : x64
Crash Address : ntoskrnl.exe+4b18cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062411-32931-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 052111-20046-01.dmp
Crash Time : 5/21/2011 4:31:35 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04e50038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a5ebc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor : x64
Crash Address : ntoskrnl.exe+4a5ebc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052111-20046-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 262,144
==================================================

Any and all help would be much appreciated, thanks!!

Maguscreed · 11 Jul 2011

Your system has been writing minidumps. These are very useful to us in troubleshooting.
Please go to c:\windows\minidump zip the contents of that folder and attach to your next post.
Screenshots and Files - Upload and Post in Seven Forums

phidelt649 · 11 Jul 2011

Sure, I've attached every minidump I could find.

Maguscreed · 11 Jul 2011

You are getting a hardware level error. One that generally is the result of hardware failure or an unstable overclock on a system component.
Since the drive minidumps are all incomplete it's hard to get very specific at the moment.
Do this for me
To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header
Select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

Hopefully forcing it will give the next minidump created time to store the driver list.

Code:

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: fffffa8004de0038, 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`037e86f0 fffff800`02f0ec59 : fffffa80`04de0010 fffffa80`03acab60 00000000`0000000f 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`037e8c10 fffff800`02deefa7 : fffffa80`04de0010 fffff800`02e692b8 fffffa80`03acab60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`037e8c40 fffff800`02d565c5 : fffff800`02ecaac0 00000000`00000001 fffffa80`04da8e60 fffffa80`03acab60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`037e8c80 fffff800`02cd6021 : fffff880`0108ae00 fffff800`02d565a0 fffffa80`03acab00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`037e8cb0 fffff800`02f6832e : 00000000`00000000 fffffa80`03acab60 00000000`00000080 fffffa80`039efb30 : nt!ExpWorkerThread+0x111
fffff880`037e8d40 fffff800`02cbd666 : fffff880`009e8180 fffffa80`03acab60 fffff880`009f2f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`037e8d80 00000000`00000000 : fffff880`037e9000 fffff880`037e3000 fffff880`03fba540 00000000`00000000 : nt!KiStartSystemThread+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
---------

0: kd> lm t n
start             end                 module name
fffff800`00bab000 fffff800`00bb5000   kdcom    kdcom.dll    Sat Feb 05 10:52:49 2011 (4D4D8061)
fffff800`02c03000 fffff800`02c4c000   hal      hal.dll      Sat Nov 20 07:00:25 2010 (4CE7C669)
fffff800`02c4c000 fffff800`03235000   nt       ntkrnlmp.exe Fri Apr 08 23:15:23 2011 (4D9FDD5B)
fffff880`00c0b000 fffff880`00c18000   mcupdate mcupdate.dll Mon Jul 13 20:29:09 2009 (4A5BDF65)
fffff880`00c18000 fffff880`00c2c000   PSHED    PSHED.dll    Mon Jul 13 20:32:23 2009 (4A5BE027)
fffff880`00c2c000 fffff880`00c8a000   CLFS     CLFS.SYS     Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`00c8a000 fffff880`00d4a000   CI       CI.dll       Sat Nov 20 07:12:36 2010 (4CE7C944)
fffff880`00d4a000 fffff880`00dee000   Wdf01000 Wdf01000.sys Mon Jul 13 18:22:07 2009 (4A5BC19F)
fffff880`00dee000 fffff880`00dfd000   WDFLDR   WDFLDR.SYS   Mon Jul 13 18:19:54 2009 (4A5BC11A)
fffff880`00e10000 fffff880`00e67000   ACPI     ACPI.sys     Sat Nov 20 03:19:16 2010 (4CE79294)
fffff880`00e67000 fffff880`00e70000   WMILIB   WMILIB.SYS   Mon Jul 13 18:19:51 2009 (4A5BC117)
fffff880`00e70000 fffff880`00e7a000   msisadrv msisadrv.sys Mon Jul 13 18:19:26 2009 (4A5BC0FE)
fffff880`00e7a000 fffff880`00ead000   pci      pci.sys      Sat Nov 20 03:19:11 2010 (4CE7928F)
fffff880`00ead000 fffff880`00eba000   vdrvroot vdrvroot.sys Mon Jul 13 19:01:31 2009 (4A5BCADB)
fffff880`00eba000 fffff880`00ecf000   partmgr  partmgr.sys  Sat Nov 20 03:20:00 2010 (4CE792C0)
fffff880`00ecf000 fffff880`00ee4000   volmgr   volmgr.sys   Sat Nov 20 03:19:28 2010 (4CE792A0)
fffff880`00ee4000 fffff880`00f40000   volmgrx  volmgrx.sys  Sat Nov 20 03:20:43 2010 (4CE792EB)
fffff880`00f40000 fffff880`00f47000   pciide   pciide.sys   Mon Jul 13 18:19:49 2009 (4A5BC115)
fffff880`00f47000 fffff880`00f57000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 18:19:48 2009 (4A5BC114)
fffff880`00f57000 fffff880`00f71000   mountmgr mountmgr.sys Sat Nov 20 03:19:21 2010 (4CE79299)
fffff880`00f71000 fffff880`00fad000   vmbus    vmbus.sys    Sat Nov 20 03:57:29 2010 (4CE79B89)
fffff880`00fad000 fffff880`00fc1000   winhv    winhv.sys    Sat Nov 20 03:20:02 2010 (4CE792C2)
fffff880`00fc1000 fffff880`00fca000   atapi    atapi.sys    Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`00fca000 fffff880`00ff4000   ataport  ataport.SYS  Sat Nov 20 03:19:15 2010 (4CE79293)
fffff880`00ff4000 fffff880`00fff000   amdxata  amdxata.sys  Fri Mar 19 11:18:18 2010 (4BA3A3CA)
fffff880`0105a000 fffff880`010a6000   fltmgr   fltmgr.sys   Sat Nov 20 03:19:24 2010 (4CE7929C)
fffff880`010a6000 fffff880`010ba000   fileinfo fileinfo.sys Mon Jul 13 18:34:25 2009 (4A5BC481)
fffff880`010ba000 fffff880`010c5d00   PxHlpa64 PxHlpa64.sys Wed Mar 12 20:58:17 2008 (47D88A39)
fffff880`010c6000 fffff880`01124000   msrpc    msrpc.sys    Sat Nov 20 03:21:56 2010 (4CE79334)
fffff880`01124000 fffff880`01196000   cng      cng.sys      Sat Nov 20 04:08:45 2010 (4CE79E2D)
fffff880`01200000 fffff880`0121b000   ksecdd   ksecdd.sys   Sat Nov 20 03:21:15 2010 (4CE7930B)
fffff880`0121b000 fffff880`0122c000   pcw      pcw.sys      Mon Jul 13 18:19:27 2009 (4A5BC0FF)
fffff880`0122c000 fffff880`01236000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 18:19:45 2009 (4A5BC111)
fffff880`01252000 fffff880`013f5000   Ntfs     Ntfs.sys     Thu Mar 10 21:39:39 2011 (4D79997B)
fffff880`01436000 fffff880`01529000   ndis     ndis.sys     Sat Nov 20 03:23:30 2010 (4CE79392)
fffff880`01529000 fffff880`01589000   NETIO    NETIO.SYS    Sat Nov 20 03:23:13 2010 (4CE79381)
fffff880`01589000 fffff880`015b4000   ksecpkg  ksecpkg.sys  Sat Nov 20 04:10:34 2010 (4CE79E9A)
fffff880`01662000 fffff880`01866000   tcpip    tcpip.sys    Sun Apr 24 21:37:30 2011 (4DB4DE6A)
fffff880`01866000 fffff880`018b0000   fwpkclnt fwpkclnt.sys Sat Nov 20 03:21:37 2010 (4CE79321)
fffff880`018b0000 fffff880`018c0000   vmstorfl vmstorfl.sys Sat Nov 20 03:57:30 2010 (4CE79B8A)
fffff880`018c0000 fffff880`0190c000   volsnap  volsnap.sys  Sat Nov 20 03:20:08 2010 (4CE792C8)
fffff880`0190c000 fffff880`01914000   spldr    spldr.sys    Mon May 11 11:56:27 2009 (4A0858BB)
fffff880`01914000 fffff880`0194e000   rdyboost rdyboost.sys Sat Nov 20 03:43:10 2010 (4CE7982E)
fffff880`0194e000 fffff880`01960000   mup      mup.sys      Mon Jul 13 18:23:45 2009 (4A5BC201)
fffff880`01960000 fffff880`0196c000   dump_ataport dump_ataport.sys Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`0196c000 fffff880`01975000   dump_atapi dump_atapi.sys Mon Jul 13 18:19:47 2009 (4A5BC113)
fffff880`01975000 fffff880`01988000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 18:21:51 2009 (4A5BC18F)
fffff880`01a00000 fffff880`01a16000   disk     disk.sys     Mon Jul 13 18:19:57 2009 (4A5BC11D)
fffff880`01a16000 fffff880`01a46000   CLASSPNP CLASSPNP.SYS Sat Nov 20 03:19:23 2010 (4CE7929B)
fffff880`01a46000 fffff880`01a4e000   AtiPcie  AtiPcie.sys  Tue May 05 10:00:22 2009 (4A005486)
fffff880`01a4e000 fffff880`021ad000   kl1      kl1.sys      Wed Jun 09 08:34:19 2010 (4C0F985B)
fffff880`021ad000 fffff880`021b6000   hwpolicy hwpolicy.sys Sat Nov 20 03:18:54 2010 (4CE7927E)
fffff880`021b6000 fffff880`021f0000   fvevol   fvevol.sys   Sat Nov 20 03:24:06 2010 (4CE793B6)
fffff880`021f0000 fffff880`021fe000   crashdmp crashdmp.sys Mon Jul 13 19:01:01 2009 (4A5BCABD)
Mini Kernel Dump does not contain unloaded driver list

phidelt649 · 12 Jul 2011

Did that...now should I just wait for it to crash again?

Maguscreed · 12 Jul 2011

yeah, it would help if at least one of those above had the complete driver data in them, kind of flying blind in the debugger without it.

Those settings will hopefully assure it writes fully next time.

phidelt649 · 13 Jul 2011

I did what you said, and it just crashed. However, it did automatically restart. The first thing I did was check the sysdmp.cpl settings again and they were still set to what you told me to put them at, so not sure why it automatically restarted?

Anyway, I've attached the dmp in hopes that it might have helped. So so you know, it was up for about 24 hours before it crashed.

EDIT: So far, it has never crashed that close together. Eight minutes after the first crash, it crashed again.

Maguscreed · 13 Jul 2011

Doesn't look to good from the outset.
The error the bug checker popped up is one that only has two real causes.
1 - an unstable overclock
2 - a actual hardware level failure

If your machine is overclocked at all, good news removing the clock should return things to normal.
If you are not, it's probably going to be a pain figuring out which component is failing online.

Code:

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: fffffa8004d258f8, 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`037da6f0 fffff800`02ee0c59 : fffffa80`04d258d0 fffffa80`03a6f040 00000000`0000000e 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`037dac10 fffff800`02dc0fa7 : fffffa80`04d258d0 fffff800`02e3b2b8 fffffa80`03a6f040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`037dac40 fffff800`02d285c5 : fffff800`02e9cac0 00000000`00000206 fffff880`037daca8 00000000`00000018 : nt!WheapProcessWorkQueueItem+0x57
fffff880`037dac80 fffff800`02ca8021 : fffff880`0110be00 fffff800`02d285a0 fffffa80`03a6f000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`037dacb0 fffff800`02f3a32e : 00000000`00000000 fffffa80`03a6f040 00000000`00000080 fffffa80`039efb30 : nt!ExpWorkerThread+0x111
fffff880`037dad40 fffff800`02c8f666 : fffff880`009e8180 fffffa80`03a6f040 fffff880`009f2f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`037dad80 00000000`00000000 : fffff880`037db000 fffff880`037d5000 fffff880`03fe4540 00000000`00000000 : nt!KiStartSystemThread+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
---------

phidelt649 · 13 Jul 2011

I don't have it overclocked as far as I know. Is there anyway to check that? I've never messed with any CPU or RAM settings before.

If it is a hardware issue, how would I go about figuring it out? The only new hardware I've added is the PSU and the WLAN card. Everything else has been there since April of last year.

Maguscreed · 13 Jul 2011

Actually if there was a problem with the new psu and it wasn't sending in enough juice that could be it.
600 watts should be more than enough for a single 9400gt though... good brand too.
I really am more of a software guy. I will see if a more senior member might have some more direct info for you.