Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Stop 0x124 with dump data

22 Apr 2011   #11
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Thank you for the update and a good job of following suggestions.

I am sorry to hear you are incapacitated by shoulder surgery. I wish you a complete and speedy recover. Post back when you can - and get well!


My System SpecsSystem Spec
.
10 May 2011   #12
Cadx

Windows 7 x64
 
 

Thank you for the get well wishes. I finally managed to switch my e8400 CPU for another one as well as switch RAM. However, I still came across stop error 0x124. I honestly do not know what else to do. I have a spare motherboard I got from my cousin and maybe I could switch that too? Anyway, attached are the recent files from my crash.

Attachment 153807
My System SpecsSystem Spec
10 May 2011   #13
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Cadx View Post
Thank you for the get well wishes. I finally managed to switch my e8400 CPU for another one as well as switch RAM. However, I still came across stop error 0x124. I honestly do not know what else to do. I have a spare motherboard I got from my cousin and maybe I could switch that too? Anyway, attached are the recent files from my crash.

Attachment 153807

Yours is a mix of video (BC116) tdr recovery and hardware. I wouldnt be surprised if the video card is the hardware that is failing. I would first replace the video driver with the newest version using these instructions


When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

Or Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

Let us know if that doesnt help
My System SpecsSystem Spec
.

10 May 2011   #14
Cadx

Windows 7 x64
 
 

Thanks for the fast response zigzag3143. I followed your instructions and still got the 0x124 stop error. Attached is the new crash report.

Attachment 153823
My System SpecsSystem Spec
10 May 2011   #15
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Cadx View Post
Thanks for the fast response zigzag3143. I followed your instructions and still got the 0x124 stop error. Attached is the new crash report.

Attachment 153823

Still pointing to hardware in the newest one. Have you followed all the suggestions in the link?

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051011-27222-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03207000 PsLoadedModuleList = 0xfffff800`03444e50
Debug session time: Tue May 10 16:04:59.272 2011 (GMT-4)
System Uptime: 0 days 0:00:06.910
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, fffffa8002af18f8, 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: fffffa8002af18f8, 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`02fc76f0 fffff800`034c1a99 : fffffa80`02af18d0 fffffa80`018d9b60 fffff8a0`00000005 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fc7c10 fffff800`033a3677 : fffffa80`02af18d0 fffff800`0341c5f8 fffffa80`018d9b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fc7c40 fffff800`0330bc45 : fffff800`0347e360 fffffa80`029fc268 fffffa80`029fc260 fffffa80`018d9b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fc7c80 fffff800`03284961 : fffff880`0106be00 fffff800`0330bc20 fffffa80`018d9b60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fc7cb0 fffff800`0351a7c6 : dee040cb`87233c41 fffffa80`018d9b60 00000000`00000080 fffffa80`018c6040 : nt!ExpWorkerThread+0x111
fffff880`02fc7d40 fffff800`03255c26 : fffff880`009e9180 fffffa80`018d9b60 fffff880`009f3f40 0f4866e2`170d2b17 : nt!PspSystemThreadStartup+0x5a
fffff880`02fc7d80 00000000`00000000 : fffff880`02fc8000 fffff880`02fc2000 fffff880`0376b540 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
---------
My System SpecsSystem Spec
11 May 2011   #16
Cadx

Windows 7 x64
 
 

Hi zigzag3143, yes I did follow the instructions in the link.
My System SpecsSystem Spec
11 May 2011   #17
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Cadx View Post
Hi zigzag3143, yes I did follow the instructions in the link.
Hardware errors are always a problem to resolve. I would start by minimizing the hardware set. remove all external USB (or others) devices that are not essentials.

Run memtest to check your memory (if you havent already)

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Run a CHKDSK to check the HD

A- CHKDSK /R /F:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

Do this for each hard drive on your system.

When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.

It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

See "CHKDSK LogFile" below in order to check the results of the test.


B- Elevated Command Prompt:


Go to Start and type in "cmd.exe" (without the quotes)

At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"


C-CHKDSK LogFile:


Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).

Copy/paste the results into your next post.
My System SpecsSystem Spec
11 May 2011   #18
Cadx

Windows 7 x64
 
 

I will run Memtest86 tonight. Here is the check disk log file for my C drive. I have 3 more drives I will check.

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
347904 file records processed. File verification completed.
575 large file records processed. 0 bad file records processed. 2 EA records processed. 76 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
419270 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
347904 file SDs/SIDs processed. Cleaning up 71 unused index entries from index $SII of file 0x9.
Cleaning up 71 unused index entries from index $SDH of file 0x9.
Cleaning up 71 unused security descriptors.
Security descriptor verification completed.
35684 data files processed. CHKDSK is verifying Usn Journal...
34666168 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0xecd26000 for 0xf000 bytes.
Read failure with status 0xc000009c at offset 0xecd34000 for 0x1000 bytes.
Windows replaced bad clusters in file 57259
of name \Windows\winsxs\wow64_microsoft-windows-eventcollector_31bf3856ad364e35_6.1.7600.16385_none_61573ee0c2c4be2b\wecapi.dll.
Read failure with status 0xc000009c at offset 0xff924000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xff929000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xff92a000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xff92a000 for 0x1000 bytes.
Windows replaced bad clusters in file 150302
of name \Windows\winsxs\AM234D~1.206\usbvideo.sys.
347888 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
11460315 free clusters processed. Free space verification is complete.
Adding 3 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

256003775 KB total disk space.
209569296 KB in 233905 files.
135484 KB in 35685 indexes.
16 KB in bad sectors.
457719 KB in use by the system.
65536 KB occupied by the log file.
45841260 KB available on disk.

4096 bytes in each allocation unit.
64000943 total allocation units on disk.
11460315 allocation units available on disk.

Internal Info:
00 4f 05 00 21 1d 04 00 0f 5b 07 00 00 00 00 00 .O..!....[......
73 93 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 s...L...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
My System SpecsSystem Spec
11 May 2011   #19
Cadx

Windows 7 x64
 
 

D drive was error free.

Chkdsk was executed in read/write mode.

Checking file system on D:
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Volume dismounted. All opened handles to this volume are now invalid.

CHKDSK is verifying files (stage 1 of 5)...
87168 file records processed. File verification completed.
3 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
92250 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
87168 file SDs/SIDs processed. Cleaning up 6 unused index entries from index $SII of file 0x9.
Cleaning up 6 unused index entries from index $SDH of file 0x9.
Cleaning up 6 unused security descriptors.
Security descriptor verification completed.
2542 data files processed. CHKDSK is verifying Usn Journal...
36483000 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
87152 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
1906297 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

232372160 KB total disk space.
224509076 KB in 69308 files.
41824 KB in 2543 indexes.
0 KB in bad sectors.
196072 KB in use by the system.
65536 KB occupied by the log file.
7625188 KB available on disk.

4096 bytes in each allocation unit.
58093040 total allocation units on disk.
1906297 allocation units available on disk.
My System SpecsSystem Spec
Reply

 Stop 0x124 with dump data




Thread Tools




Similar help and support threads
Thread Forum
Stop 0x124 - what it means and what to try
Synopsis: A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of...
Crash and lockup debug 'How To'
Stop 0x124
i need help stopping this problem i recently installed windows ultimate x64 and couple days later this stop error been haunting me since then..can anybody help me stop getting this error
BSOD Help and Support
BSOD stop 0x124
System about 1year old, when bought installed full retail windows 7 prof x64 a few months ago it started blue screening while gaming, its now beginning to irritate me into action
BSOD Help and Support
Win 7 BSOD stop 0x124
Hi, I've recently started experiencing these BSOD's even when the PC is idle. Here is the Who Crashed analysis : On Fri 07/05/2010 10:17:15 your computer crashed This was likely caused by the following module: hardware Bugcheck code: 0x124 (0x0, 0xFFFFFA80076E1028, 0xFE200040, 0x60114A)...
BSOD Help and Support
0x124 STOP Error - Possible nVidia?
Hi everyone, Over the last few days, I have been getting blue screen stop errors, with the 0x124 error. Originally, I thought it was a software issue, so I reinstalled Windows 7 from scratch, but this obviously did not resolve the problem. I had a look at some possible causes, and like usual,...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:03.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App