Hallo Liebe Community,
ich schlage mich seit geraumer Zeit mit diversen BSoD herum.
Ich bin nicht wirklich ein Kenner der Materie, habe mich aber bereits wie folgt durchgeschlagen:

Mit einer Software namens BlueScreenView war ich in der Lage, die .dmp-Files unter C:\Windows\Minidump zu öffnen.
Die Fehler weisen durchgängig und ausschließlich auf ntoskrnl.exe hin.
Internet-Recherche brachte mich zu einer Software namens WinDbg.exe, die ebenfalls .dmp-Files auslesen kann,
und das deutlich detaillierter.
Hier entzieht sich meine Kenntnis der Materie.
De-facto treten die Probleme fast ausschließlich bei 3D-Anwendungen auf (zu vielleicht >90%)
Es sind jedoch so gut wie sämtliche Hardware-Komponenten ausgetauscht worden, ohne auch nur einen nennenswerten Erfolg zu erzielen.

Meine Bitte wäre die Ursachenfindung und Problembeseitigung der BSoDs,
da auf diesem System auch bedingt wichtige Daten vorhanden sind
(inzwischen auf einer externen Platte, aber ohne PC kein Zugriff darauf)

Und ich würde mich sehr darüber freuen,
wenn die kommenden Anforderungen an mich leicht verständlich gestellt werden würden.

Vielen Dank bereits im Voraus!

Mein System:
Betriebssystem: Windows 10 Pro (Gratis-Update von Win 7 auf 10)
Motherboard: MSi 770-C45
Prozessor: AMD Phenom(tm) II X6 1090T Processor 3.2 GHz (neu eingebaut)
Grafikkarte: nVidia GeForce GTX 750 Ti (neu eingebaut)
Arbeitsspeicher: G.Skill 4x 2 GB, 1066 MHz
Festplatte: 2 x SATA Samsung á 1 TB, partitioniert

Die detaillierte Beschreibung der .dmp-File aus der WinDbg.exe lautet:

Loading Dump File [C:\Windows\Minidump\092416-18656-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 10586 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.589.amd64fre.th2_release.160906-1759
Machine Name:
Kernel base = 0xfffff801`f8888000 PsLoadedModuleList = 0xfffff801`f8b65cd0
Debug session time: Sat Sep 24 00:00:13.284 2016 (GMT+2)
System Uptime: 0 days 0:30:12.018
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
...............................................
Loading User Symbols
Loading unloaded module list
...........
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff79940000000, 23653, 400023654ffffffe}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** ***********************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Probably caused by : ntoskrnl.exe ( nt+142970 )

Followup: MachineOwner
---------