Question

BSOD: WHEA_UNCORRECTABLE_ERROR (124) minidump attached

Asked by: jtiernan2008

Can someone please look at the code below and see why this is happening.

Thanks a million

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: 00000000, Machine Check Exception
Arg2: 862c7d18, Address of the WHEA_ERROR_RECORD structure.
Arg3: f2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.
 
Debugging Details:
------------------
 
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
 
BUGCHECK_STR:  0x124_GenuineIntel
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  a
 
STACK_TEXT:  
820eef84 823a6f1f 00000124 00000000 849ae1b8 nt!KeBugCheckEx+0x1e
820eefa0 820cee6a 849ae1b8 849af890 00000001 hal!HalBugCheckSystem+0x37
820eefc0 823a6ede 849af890 849af9a8 820eeff4 nt!WheaReportHwError+0x10c
820eefd0 823a6fff 00000003 849af890 00000000 hal!HalpReportMachineCheck+0x28
820eeff4 823a389f 8014e000 00000000 00000000 hal!HalpMcaExceptionHandler+0xc3
820eeff4 00000000 8014e000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: hardware
 
IMAGE_NAME:  hardware
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
FAILURE_BUCKET_ID:  0x124_GenuineIntel__UNKNOWN
 
BUCKET_ID:  0x124_GenuineIntel__UNKNOWN
 
Followup: MachineOwner
---------

                                  
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:

Select allOpen in new window

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2009-07-08 at 07:16:49ID24553208
Topics

Debugging Software for Development

,

Windows Vista

,

Assembly Programming Language

Participating Experts
3
Points
500
Comments
10

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. How to analyse XP minidumps
    What processes / applications are available for analysing XP minidump files. Any good references on this would be appreciated.
  2. help with BSOD & minidump
    I recevied a blue screen of death. Here is the error from the event viewer: System error category (102) event 1003 Error code 1000008e, parameter1 c0000047, parameter2 80522363, parameter3 a5f373b4, parameter4 00000000 Does anyone know how to read a minidump? JDF
  3. BSOD - Minidumps
    Trying to diagnose a computer that ocassionally blue screens. Can someone tell me what these minidumps will reveal? http://home.earthlink.net/~asmb/minidumps/
  4. BSOD - help reading minidump/debug log
    Clients computer gets BSOD overnight frequently. Cant figure out what the minidump/debug log is pointing to. Anyone out there can make sense of this one? See code below:
  5. Bsod with no minidump
    Hello my problem is that my computer blue screens once a while but theres no minidump.. am pretty sure i have it enabled and i dont know why i cannot find the minidump file in the system directory.. I have windows xp on service pack 3.. I need the minidump to debug it with wi...
  6. Help with minidump analysis
    When I came to the office this morming my PC had a BSOD. The error on screen was IRQ_NOT_LESS_OR_EQUAL. I rebooted the machine and got a BSOD ntfs.sys 0x00000024. I thought maybe it was a faulty memory module so I removed all modules and rebooted the machine with each stic...

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: awawadaPosted on 2009-07-08 at 07:21:24ID: 24804061

vhange the extension to .txt from .dmp and post the dmp file. all drivers up to date?

 

by: jtiernan2008Posted on 2009-07-08 at 07:34:20ID: 24804214

No problem,

Please note that all generic TS steps have been taken.
I am looking for a debugging solution from someone who understands the code in a similar fashion to the following;
http://www.experts-exchange.com/Software/Development/Management_Debug/Debugging/Q_24490615.html

thanks in advance

 

by: jtiernan2008Posted on 2009-07-08 at 07:35:48ID: 24804229

attached

 

by: awawadaPosted on 2009-07-08 at 07:59:51ID: 24804492

all drivers up to date? Can you test your harddisc ram and cpu for errors with: http://www.ultimatebootcd.com/ ?

Memory Tests with: Memtest86
CPU Tests with: CPU Burn-in, Mersenne Prime Test & StressCPU
Hard Disk Diagnostic with: your Hard Disk Manufacturers tool. (Drive Fitness Test (IBM/Hitachi) works with most)
If evrything passes, I would try removing all of your component down to just the cpu and ram and see if that helps.

 

by: jtiernan2008Posted on 2009-07-08 at 09:24:14ID: 24805472

Hi,

thanks for your help. I appreciate it but all of the above guidelines have been followed and more.
However, I am looking for assistance in explaining the debug information above rather TS steps in the same fashion as the link I provided above.

thanks

 

by: nobusPosted on 2009-07-09 at 00:12:03ID: 24811251

what OS ?  vista 64 ?

here it was nvidia :  http://social.technet.microsoft.com/Forums/en-US/w7itprohardware/thread/c7ca0505-2ae1-40da-94b8-3324f1a3c785

This error relates to the hardware, but does not say what hardware...  The sites below can help :
Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR

BSOD:0x124 issue under Vista SP1

BSOD:0x124 - NVIDIA Forums

 

by: jtiernan2008Posted on 2009-07-09 at 08:39:33ID: 24814843

thanks I saw that website

I have done the TS and researched the error using Google already.
Really looking more for a breakdown of the debug code

 

by: nobusPosted on 2009-07-09 at 11:08:56ID: 24816421

fine with me.

 

by: jtiernan2008Posted on 2009-07-13 at 06:22:36ID: 24839398

thanks for your help though

 

by: jcgriff2Posted on 2009-07-16 at 11:37:36ID: 24872208

.Hi -

I believe the 0x124 bugcheck BSODs are being cause by a mixture of out-dated and more recent drivers colliding with each other on a grand scale.  I think that your BSODs would go away if you would update your system with Vista SP1 - at a minimum.  Viasta SP2 is now out, but SP1 is a prerequisite.

The probable reason for the crashes is that most of your Vista SP0 system drivers (including the DirectX Graphics Kernel) are timestamped Nov 2006.  The NT Kernel and win32k.sys GUI have timestamps = Mar/April 2009.

Your device drivers need to be updated as well.

NVIDIA video    -  nvlddmkm.sys Fri May 11 23:39:48 2007 (46456134)
Conexant Audio -  HSX_CNXT.sys Fri Dec 22 11:48:52 2006 (458C36A4)
Intel wifi             -  NETw4v32.sys Thu Jun 21 04:51:25 2007 (467A663D)
Realtek audio     - RTKVHDA.sys  Mon Jun 11 16:05:26 2007 (466DD536)
Marvell Yukon Ethernet  -     yk60x86.sys  Thu May 24 05:10:49 2007 (465580C9)

Then there is this Sony Electronics Conexant-Ambit SoftK56 Data,Fax Modem Driver from 2000 -
DMICall.sys  Mon Dec 04 23:14:23 2000 (3A2C95CF)

I don't know how Sony justified installing a Win 2000 driver into a Vista system.  If no update is available, I would disable it if the device is not used.

To help you with SP1, here is a link from a post I wrote to help a user install Vista SP1 -

http://www.techsupportforum.com/microsoft-support/windows-vista-windows-7-support/342003-solved-should-i-install-windows-vista-service-pack-1-a.html#post1952419


Regards. . .

jcgriff2
. </A>

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...