BSoD, Help.

#1
Well, I can not figure this out for the life on me. I got this computer built for me for Christmas. And this has been happening some-what since I got it.

Code:
Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7600.2.0.0.256.1
  Locale ID:	1033


Additional information about the problem:
  BCCode:	124
  BCP1:	0000000000000000
  BCP2:	FFFFFA8004D34038
  BCP3:	0000000000000000
  BCP4:	0000000000000000
  OS Version:	6_1_7600
  Service Pack:	0_0
  Product:	256_1


Files that help describe the problem:
  C:\Windows\Minidump\031512-24148-01.dmp
  C:\Users\Thomas LeGodais\AppData\Local\Temp\WER-39515-0.sysdata.xml


Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409


If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
 


Trouble

Noob Whisperer
#2
Hello and welcome to the forums.
First make sure your machine is configured properly to facilitate the collection of .dmp files.
Go to Start and type in sysdm.cpl and press Enter
Click on 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
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Then:
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area http://windows7forums.com/windows-7...you-filling-your-system-specs.html#post235529 .
Good luck
Randy
 


Trouble

Noob Whisperer
#4
There are no screen shots from CPUz nor is there an HTML report RAMMon. Please include these and for future reference you can attach them within your posts on this forum by clicking reply then go advanced and then using the paperclip icon. Make sure you zip them up first. That way we don't have to go to some other site to get your attachments
With only a single dump file and that being the dreaded;
Code:
[COLOR=#ff0000][U][B]BugCheck 124[/B][/U][/COLOR], {0, fffffa8004d34038, 0, 0}

[U][B]Probably caused by : hardware[/B][/U]
[U][B]WHEA_UNCORRECTABLE_ERROR (124)[/B][/U]
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: fffffa8004d34038, 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.
BUGCHECK_STR:  0x124_GenuineIntel
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`02fd26f0 fffff800`02b1ca89 : fffffa80`04d34010 fffffa80`03a02680 00000000`00000011 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fd2c10 fffff800`029fe547 : fffffa80`04d34010 fffff800`02a775f8 fffffa80`03a02680 00000000`00000286 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fd2c40 fffff800`02966b95 : fffff800`02ad9360 fffffa80`049042e8 fffffa80`049042e0 fffffa80`03a02680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fd2c80 fffff800`028e1161 : fffff880`01193e00 fffff800`02966b70 fffffa80`03a02680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fd2cb0 fffff800`02b77166 : 00000000`00000000 fffffa80`03a02680 00000000`00000080 fffffa80`039ee040 : nt!ExpWorkerThread+0x111
fffff880`02fd2d40 fffff800`028b2486 : fffff880`009ea180 fffffa80`03a02680 fffff880`009f4f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fd2d80 00000000`00000000 : fffff880`02fd3000 fffff880`02fcd000 fffff880`02fd29f0 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
So.....
Stop any and all overclocking and return CPU, GPU and Memory setting to default / auto / normal.
Catch up any and all system drivers to current dates.
Consider upgrading to Service Pack 1.
Might want to also get ready for some hardware diagnotics
here's some suggestions by one of our staff members Hardware Diagnostic | Captain Debugger
and a pretty good explaination of that 124 Stop error. Stop 0x124 - what it means and what to try - Windows 7 Forums
Good luck
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.