BSOD Computer Hardware Issue

[fasm1234]

Pc Specs: 

AMD FX-6300 3.5GHz 6-Core Processor

Gigabyte GA-78LMT-USB3 Micro ATX AM3+ Motherboard

Corsair Vengeance 8GB (2 x 4GB) DDR3-1600 Memory

Gigabyte GeForce GTX 770 2GB WINDFORCE Video Card

EVGA 600B 600W 80+ Bronze Certified ATX Power Supply

Western Digital Caviar Blue 1TB 3.5" 7200RPM Internal Hard Drive

 

 

 

1. Microsoft ® Windows Debugger Version 6.3.9600.17336 AMD64
2. Copyright © Microsoft Corporation. All rights reserved.
3.  
4.  
5. Loading Dump File [C:\Windows\Minidump\052415-14102-01.dmp]
6. Mini Kernel Dump File: Only registers and stack trace are available
7.  
8. Symbol search path is: *** Invalid ***
9. ****************************************************************************
10. * Symbol loading may be unreliable without a symbol search path.           *
11. * Use .symfix to have the debugger choose a symbol path.                   *
12. * After setting your symbol path, use .reload to refresh symbol locations. *
13. ****************************************************************************
14. Executable search path is:
15. *********************************************************************
16. * Symbols can not be loaded because symbol path is not initialized. *
17. *                                                                   *
18. * The Symbol Path can be set by:                                    *
19. *   using the _NT_SYMBOL_PATH environment variable.                 *
20. *   using the -y <symbol_path> argument when starting the debugger. *
21. *   using .sympath and .sympath+                                    *
22. *********************************************************************
23. Unable to load image ntoskrnl.exe, Win32 error 0n2
24. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
25. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
26. Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
27. Product: WinNt, suite: TerminalServer SingleUserTS
28. Machine Name:
29. Kernel base = 0xfffff800`02c63000 PsLoadedModuleList = 0xfffff800`02eaa730
30. Debug session time: Sun May 24 01:01:26.237 2015 (UTC - 4:00)
31. System Uptime: 0 days 0:00:09.392
32. *********************************************************************
33. * Symbols can not be loaded because symbol path is not initialized. *
34. *                                                                   *
35. * The Symbol Path can be set by:                                    *
36. *   using the _NT_SYMBOL_PATH environment variable.                 *
37. *   using the -y <symbol_path> argument when starting the debugger. *
38. *   using .sympath and .sympath+                                    *
39. *********************************************************************
40. Unable to load image ntoskrnl.exe, Win32 error 0n2
41. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
42. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
43. Loading Kernel Symbols
44. .................................................
45. Loading User Symbols
46. Mini Kernel Dump does not contain unloaded driver list
47.  
48. ************* Symbol Loading Error Summary **************
49. Module name            Error
50. ntoskrnl               The system cannot find the file specified
51.  
52. You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
53. You should also verify that your symbol search path (.sympath) is correct.
54. *******************************************************************************
55. *                                                                             *
56. *                        Bugcheck Analysis                                    *
57. *                                                                             *
58. *******************************************************************************
59.  
60. Use !analyze -v to get detailed debugging information.
61.  
62. BugCheck 124, {0, fffffa80085c4788, 0, 0}
63.  
64. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
65.  
66. *************************************************************************
67. ***                                                                   ***
68. ***                                                                   ***
69. ***    Either you specified an unqualified symbol, or your debugger   ***
70. ***    doesn't have full symbol information.  Unqualified symbol      ***
71. ***    resolution is turned off by default. Please either specify a   ***
72. ***    fully qualified symbol module!symbolname, or enable resolution ***
73. ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
74. ***    enabling unqualified symbol resolution with network symbol     ***
75. ***    server shares in the symbol path may cause the debugger to     ***
76. ***    appear to hang for long periods of time when an incorrect      ***
77. ***    symbol name is typed or the network symbol server is down.     ***
78. ***                                                                   ***
79. ***    For some commands to work properly, your symbol path           ***
80. ***    must point to .pdb files that have full type information.      ***
81. ***                                                                   ***
82. ***    Certain .pdb files (such as the public OS symbols) do not      ***
83. ***    contain the required information.  Contact the group that      ***
84. ***    provided you with these symbols if you need this command to    ***
85. ***    work.                                                          ***
86. ***                                                                   ***
87. ***    Type referenced: nt!_WHEA_ERROR_RECORD_HEADER                  ***
88. ***                                                                   ***
89. *************************************************************************
90. *************************************************************************
91. ***                                                                   ***
92. ***                                                                   ***
93. ***    Either you specified an unqualified symbol, or your debugger   ***
94. ***    doesn't have full symbol information.  Unqualified symbol      ***
95. ***    resolution is turned off by default. Please either specify a   ***
96. ***    fully qualified symbol module!symbolname, or enable resolution ***
97. ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
98. ***    enabling unqualified symbol resolution with network symbol     ***
99. ***    server shares in the symbol path may cause the debugger to     ***
100. ***    appear to hang for long periods of time when an incorrect      ***
101. ***    symbol name is typed or the network symbol server is down.     ***
102. ***                                                                   ***
103. ***    For some commands to work properly, your symbol path           ***
104. ***    must point to .pdb files that have full type information.      ***
105. ***                                                                   ***
106. ***    Certain .pdb files (such as the public OS symbols) do not      ***
107. ***    contain the required information.  Contact the group that      ***
108. ***    provided you with these symbols if you need this command to    ***
109. ***    work.                                                          ***
110. ***                                                                   ***
111. ***    Type referenced: nt!_WHEA_ERROR_RECORD_HEADER                  ***
112. ***                                                                   ***
113. *************************************************************************
114. Unable to load image PSHED.dll, Win32 error 0n2
115. *** WARNING: Unable to verify timestamp for PSHED.dll
116. *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
117. *************************************************************************
118. ***                                                                   ***
119. ***                                                                   ***
120. ***    Either you specified an unqualified symbol, or your debugger   ***
121. ***    doesn't have full symbol information.  Unqualified symbol      ***
122. ***    resolution is turned off by default. Please either specify a   ***
123. ***    fully qualified symbol module!symbolname, or enable resolution ***
124. ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
125. ***    enabling unqualified symbol resolution with network symbol     ***
126. ***    server shares in the symbol path may cause the debugger to     ***
127. ***    appear to hang for long periods of time when an incorrect      ***
128. ***    symbol name is typed or the network symbol server is down.     ***
129. ***                                                                   ***
130. ***    For some commands to work properly, your symbol path           ***
131. ***    must point to .pdb files that have full type information.      ***
132. ***                                                                   ***
133. ***    Certain .pdb files (such as the public OS symbols) do not      ***
134. ***    contain the required information.  Contact the group that      ***
135. ***    provided you with these symbols if you need this command to    ***
136. ***    work.                                                          ***
137. ***                                                                   ***
138. ***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
139. ***                                                                   ***
140. *************************************************************************
141. *************************************************************************
142. ***                                                                   ***
143. ***                                                                   ***
144. ***    Either you specified an unqualified symbol, or your debugger   ***
145. ***    doesn't have full symbol information.  Unqualified symbol      ***
146. ***    resolution is turned off by default. Please either specify a   ***
147. ***    fully qualified symbol module!symbolname, or enable resolution ***
148. ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
149. ***    enabling unqualified symbol resolution with network symbol     ***
150. ***    server shares in the symbol path may cause the debugger to     ***
151. ***    appear to hang for long periods of time when an incorrect      ***
152. ***    symbol name is typed or the network symbol server is down.     ***
153. ***                                                                   ***
154. ***    For some commands to work properly, your symbol path           ***
155. ***    must point to .pdb files that have full type information.      ***
156. ***                                                                   ***
157. ***    Certain .pdb files (such as the public OS symbols) do not      ***
158. ***    contain the required information.  Contact the group that      ***
159. ***    provided you with these symbols if you need this command to    ***
160. ***    work.                                                          ***
161. ***                                                                   ***
162. ***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
163. ***                                                                   ***
164. *************************************************************************
165. *************************************************************************
166. ***                                                                   ***
167. ***                                                                   ***
168. ***    Either you specified an unqualified symbol, or your debugger   ***
169. ***    doesn't have full symbol information.  Unqualified symbol      ***
170. ***    resolution is turned off by default. Please either specify a   ***
171. ***    fully qualified symbol module!symbolname, or enable resolution ***
172. ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
173. ***    enabling unqualified symbol resolution with network symbol     ***
174. ***    server shares in the symbol path may cause the debugger to     ***
175. ***    appear to hang for long periods of time when an incorrect      ***
176. ***    symbol name is typed or the network symbol server is down.     ***
177. ***                                                                   ***
178. ***    For some commands to work properly, your symbol path           ***
179. ***    must point to .pdb files that have full type information.      ***
180. ***                                                                   ***
181. ***    Certain .pdb files (such as the public OS symbols) do not      ***
182. ***    contain the required information.  Contact the group that      ***
183. ***    provided you with these symbols if you need this command to    ***
184. ***    work.                                                          ***
185. ***                                                                   ***
186. ***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
187. ***                                                                   ***
188. *************************************************************************
189. *************************************************************************
190. ***                                                                   ***
191. ***                                                                   ***
192. ***    Either you specified an unqualified symbol, or your debugger   ***
193. ***    doesn't have full symbol information.  Unqualified symbol      ***
194. ***    resolution is turned off by default. Please either specify a   ***
195. ***    fully qualified symbol module!symbolname, or enable resolution ***
196. ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
197. ***    enabling unqualified symbol resolution with network symbol     ***
198. ***    server shares in the symbol path may cause the debugger to     ***
199. ***    appear to hang for long periods of time when an incorrect      ***
200. ***    symbol name is typed or the network symbol server is down.     ***
201. ***                                                                   ***
202. ***    For some commands to work properly, your symbol path           ***
203. ***    must point to .pdb files that have full type information.      ***
204. ***                                                                   ***
205. ***    Certain .pdb files (such as the public OS symbols) do not      ***
206. ***    contain the required information.  Contact the group that      ***
207. ***    provided you with these symbols if you need this command to    ***
208. ***    work.                                                          ***
209. ***                                                                   ***
210. ***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
211. ***                                                                   ***
212. *************************************************************************
213. *************************************************************************
214. ***                                                                   ***
215. ***                                                                   ***
216. ***    Either you specified an unqualified symbol, or your debugger   ***
217. ***    doesn't have full symbol information.  Unqualified symbol      ***
218. ***    resolution is turned off by default. Please either specify a   ***
219. ***    fully qualified symbol module!symbolname, or enable resolution ***
220. ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
221. ***    enabling unqualified symbol resolution with network symbol     ***
222. ***    server shares in the symbol path may cause the debugger to     ***
223. ***    appear to hang for long periods of time when an incorrect      ***
224. ***    symbol name is typed or the network symbol server is down.     ***
225. ***                                                                   ***
226. ***    For some commands to work properly, your symbol path           ***
227. ***    must point to .pdb files that have full type information.      ***
228. ***                                                                   ***
229. ***    Certain .pdb files (such as the public OS symbols) do not      ***
230. ***    contain the required information.  Contact the group that      ***
231. ***    provided you with these symbols if you need this command to    ***
232. ***    work.                                                          ***
233. ***                                                                   ***
234. ***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
235. ***                                                                   ***
236. *************************************************************************
237. *************************************************************************
238. ***                                                                   ***
239. ***                                                                   ***
240. ***    Either you specified an unqualified symbol, or your debugger   ***
241. ***    doesn't have full symbol information.  Unqualified symbol      ***
242. ***    resolution is turned off by default. Please either specify a   ***
243. ***    fully qualified symbol module!symbolname, or enable resolution ***
244. ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
245. ***    enabling unqualified symbol resolution with network symbol     ***
246. ***    server shares in the symbol path may cause the debugger to     ***
247. ***    appear to hang for long periods of time when an incorrect      ***
248. ***    symbol name is typed or the network symbol server is down.     ***
249. ***                                                                   ***
250. ***    For some commands to work properly, your symbol path           ***
251. ***    must point to .pdb files that have full type information.      ***
252. ***                                                                   ***
253. ***    Certain .pdb files (such as the public OS symbols) do not      ***
254. ***    contain the required information.  Contact the group that      ***
255. ***    provided you with these symbols if you need this command to    ***
256. ***    work.                                                          ***
257. ***                                                                   ***
258. ***    Type referenced: nt!_KPRCB                                     ***
259. ***                                                                   ***
260. *************************************************************************
261. *************************************************************************
262. ***                                                                   ***
263. ***                                                                   ***
264. ***    Either you specified an unqualified symbol, or your debugger   ***
265. ***    doesn't have full symbol information.  Unqualified symbol      ***
266. ***    resolution is turned off by default. Please either specify a   ***
267. ***    fully qualified symbol module!symbolname, or enable resolution ***
268. ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
269. ***    enabling unqualified symbol resolution with network symbol     ***
270. ***    server shares in the symbol path may cause the debugger to     ***
271. ***    appear to hang for long periods of time when an incorrect      ***
272. ***    symbol name is typed or the network symbol server is down.     ***
273. ***                                                                   ***
274. ***    For some commands to work properly, your symbol path           ***
275. ***    must point to .pdb files that have full type information.      ***
276. ***                                                                   ***
277. ***    Certain .pdb files (such as the public OS symbols) do not      ***
278. ***    contain the required information.  Contact the group that      ***
279. ***    provided you with these symbols if you need this command to    ***
280. ***    work.                                                          ***
281. ***                                                                   ***
282. ***    Type referenced: nt!_KPRCB                                     ***
283. ***                                                                   ***
284. *************************************************************************
285. *************************************************************************
286. ***                                                                   ***
287. ***                                                                   ***
288. ***    Either you specified an unqualified symbol, or your debugger   ***
289. ***    doesn't have full symbol information.  Unqualified symbol      ***
290. ***    resolution is turned off by default. Please either specify a   ***
291. ***    fully qualified symbol module!symbolname, or enable resolution ***
292. ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
293. ***    enabling unqualified symbol resolution with network symbol     ***
294. ***    server shares in the symbol path may cause the debugger to     ***
295. ***    appear to hang for long periods of time when an incorrect      ***
296. ***    symbol name is typed or the network symbol server is down.     ***
297. ***                                                                   ***
298. ***    For some commands to work properly, your symbol path           ***
299. ***    must point to .pdb files that have full type information.      ***
300. ***                                                                   ***
301. ***    Certain .pdb files (such as the public OS symbols) do not      ***
302. ***    contain the required information.  Contact the group that      ***
303. ***    provided you with these symbols if you need this command to    ***
304. ***    work.                                                          ***
305. ***                                                                   ***
306. ***    Type referenced: nt!_KPRCB                                     ***
307. ***                                                                   ***
308. *************************************************************************
309. Probably caused by : AuthenticAMD
310.  
311. Followup: MachineOwner
312. ---------

[Faceman]

Just from looking at your specs, the VRMs on that motherboard can't handle the power hungry FX6.