- Gygabyte GA-MA74GM-S2H (rev. 2.0)
- AMD Athlon II X2 245e Boxed
- 2 x 1GB
- 5 x 1,5TB (ik dacht 3xWD en 2xSamsung = alleemaal Greens)
- TBS 6922 dvb-s2 kaartje
- TVSource 4.5.2
Op dit moment ben ik memtest aan het draaien.
Het vage is dat ik dit probleem sinds kort heb zonder dat ik iets aan hardware heb veranderd. TVSource 4.5.2 heb ik al verwijderd en opnieuw geinstalleeerd om te kijken of het niet toevallig daaraan lag.... (Dit voornamelijk vanwege "PROCESS_NAME: tvs_plugin_host").
In welke richting zouden jullie zoeken? Graag meer tips?
Minidump van net heb ik uitgelezen:
- AMD Athlon II X2 245e Boxed
- 2 x 1GB
- 5 x 1,5TB (ik dacht 3xWD en 2xSamsung = alleemaal Greens)
- TBS 6922 dvb-s2 kaartje
- TVSource 4.5.2
Op dit moment ben ik memtest aan het draaien.
Het vage is dat ik dit probleem sinds kort heb zonder dat ik iets aan hardware heb veranderd. TVSource 4.5.2 heb ik al verwijderd en opnieuw geinstalleeerd om te kijken of het niet toevallig daaraan lag.... (Dit voornamelijk vanwege "PROCESS_NAME: tvs_plugin_host").
In welke richting zouden jullie zoeken? Graag meer tips?
Minidump van net heb ik uitgelezen:
code:
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
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
| [b]Datum: 14 March 2013, 13:04:07[/b]
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini031413-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
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: Server, suite: SmallBusiness TerminalServer SmallBusinessRestricted SingleUserTS WHServer
Built by: 3790.srv03_sp2_gdr.130106-1434
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Thu Mar 14 13:00:56.109 2013 (UTC + 1:00)
System Uptime: 0 days 23:50:32.781
Loading Kernel Symbols
...............................................................
................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {0, f772d2c0, b6004000, 15000135}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000000
Arg2: f772d2c0
Arg3: b6004000
Arg4: 15000135
Debugging Details:
------------------
NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.
This error is documented in the following publication:
- Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
Bit Mask:
MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011011000000000010000000000000000010101000000000000000100110101
VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.
UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.
EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.
ADDRV - IA32_MCi_ADDR register valid
Indicates that the IA32_MCi_ADDR register contains the address where
the error occurred.
PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.
MEMHIRERR - Memory Hierarchy Error {TT}CACHE{LL}_{RRRR}_ERR
These errors match the format 0000 0001 RRRR TTLL
Concatenated Error Code:
--------------------------
_VAL_UC_EN_ADDRV_PCC_MEMHIRERR_35
This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.
BUGCHECK_STR: 0x9C_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
PROCESS_NAME: tvs_plugin_host
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 80a64154 to 80827cb3
STACK_TEXT:
f772d290 80a64154 0000009c 00000000 f772d2c0 nt!KeBugCheckEx+0x1b
f772d3c4 80a5b86f f7727fe0 00000000 00000000 hal!HalpMcaExceptionHandler+0x11e
f772d3c4 00000000 f7727fe0 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x9C_AuthenticAMD_ANALYSIS_INCONCLUSIVE
BUCKET_ID: 0x9C_AuthenticAMD_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
--------- |
:strip_icc():strip_exif()/u/146731/crop562615a0aa64c.jpeg?f=community)
En dan niet een kwartiertje ofzo, maar minstens een hele nacht bijvoorbeeld. Verder temperaturen en voltages even checken.
/u/456650/crop5669de30e11d2_cropped.png?f=community)