	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

07/08/2009 at 07:16AM PDT, ID: 24553208

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.7

BSOD: WHEA_UNCORRECTABLE_ERROR (124) minidump attached

Asked by jtiernan2008 in Debugging Software for Development, Windows Vista, Assembly Programming Language

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

Thanks a million

View the Solution FREE for 30 Days

         
           
             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:

           
           
             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
---------

           
         

Keywords: BSOD: WHEA_UNCORRECTABLE_E…

	Title
1	bugcheck stop 0x0000001e
2	BLUE SCREEN ERROR
3	bugcheck stop 0x0000000a on …

Loading Advertisement...

20091111-EE-VQP-91 - Hierarchy / EE_QW_4_20070622

1. jcgriff29,800
2. chris_bot...6,000
3. roman24,600
4. abel4,500
5. duncan_roe4,000
5. madprogr...4,000
7. epasquier3,000
8. emoreau2,500
8. meverest2,500
8. jkr2,500
8. ragi00172,500
8. TechSoEasy2,500
8. apresto2,500
8. doades2,500
15. nobus2,400
16. MrClyfar2,000
16. Jbamaral2,000
16. locke_a2,000
16. t0t02,000
16. Sethi2,000
16. rg202,000
16. joinaunion2,000
16. oBdA2,000
16. gtokas2,000
16. McKnife2,000
16. nsr812,000
16. Snarf00012,000
16. mwvisa12,000
16. dericstone2,000
16. TeraByte...2,000
16. p_davis2,000
16. David-Ho...2,000
16. Ray_Pas...2,000
16. EMB012,000
16. Gary_Th...2,000
16. Jones9112,000
16. oklit2,000
16. treeandrew2,000
16. hathehariken2,000
16. pcelba2,000
16. Aleksei_...2,000
16. leakim9712,000

1. jcgriff29,800
2. jkr8,500
3. chris_bot...6,000
4. roman24,600
5. abel4,500
6. Dhaest4,000
6. sunnycoder4,000
6. duncan_roe4,000
6. madprogr...4,000
10. meverest3,500
11. MrClyfar3,000
11. epasquier3,000
13. emoreau2,800
14. ragi00172,500
14. TechSoEasy2,500
14. apresto2,500
14. jgordos2,500
14. doades2,500
19. nobus2,400
20. Qlemo2,150
21. Jbamaral2,000
21. dbrunton2,000
21. locke_a2,000
21. ericpete2,000
21. t0t02,000
21. Sethi2,000
21. rg202,000
21. logudotcom2,000
21. joinaunion2,000
21. oBdA2,000
21. mrGreen2,000
21. twoboats2,000
21. basicinsti...2,000
21. johnb67672,000
21. scrathcyboy2,000
21. gtokas2,000
21. pmascari2,000
21. dampsey2,000
21. McKnife2,000
21. nsr812,000
21. mtz1of42,000
21. vadimrapp12,000
21. Snarf00012,000
21. mwvisa12,000
21. evilrix2,000
21. ororiole2,000
21. dericstone2,000
21. TeraByte...2,000
21. p_davis2,000
21. David-Ho...2,000
21. Ray_Pas...2,000
21. MrHusy2,000
21. pcsmitpra2,000
21. slam692,000
21. EMB012,000
21. Gary_Th...2,000
21. paulsolov2,000
21. Jones9112,000
21. oklit2,000
21. treeandrew2,000
21. hathehariken2,000
21. pcelba2,000
21. Aleksei_...2,000
21. leakim9712,000

BSOD: WHEA_UNCORRECTABLE_ERROR (124) minidump attached

Asked by jtiernan2008 in Debugging Software for Development, Windows Vista, Assembly Programming Language

About this solution