Bluescreen Windows 7 64Bit Version!

[myZID]

Hallo Community,

seit gestern habe ich einen neuen Rechner.

Informationen zum Rechner:

Prozessor: AMD A8-3870 APU with Radeon(tm) HD Graphics 3.00 GHz

Arbeitsspeicher: 7,72 GB

Graka (on board): AMD Radeon HD 6550D

und ja ich weiss, der PC ist nicht der beste doch für meine Verhältnisse bzw. meinen Bedarf vollkommen ausreichend!


Wichtig ist zu erwähnen, dass Windows 7 schon vorinstalliert war und ich nur Software installiert habe, die ich benötige. Bis jetzt bekam ich 4 Bluescreens.. 2 x beim patchen von League of Legends, einmal während des spielens von League of Legends und den letzten bei Minecraft während ich auf einem Online Server war.

Folgendes hab ich bisher unternommen:

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 02.02.2014 13:09:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020214-202972-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 02.02.2014 13:09:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 02.02.2014 11:12:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020214-34367-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EC180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 01.02.2014 20:34:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020114-34304-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EC180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 01.02.2014 19:53:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020114-30451-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EC180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Sprich: Ich habe die Dump Datei auswerten lassen und lese daraus, dass es kein Hardware Problem sein kann. Sondern eher ein Treiber/Software Problem. Ich bitte um eure Hilfe und bin euch im vorraus dankbar! Gibt es ein Programm, was veraltete Treiber etc. anzeigt?

P.S. Bin jetzt nicht wirklich ein Fachmann der Plan von dies und jenes hat. Deshalb bitte alles so erklären, dass ich es verstehe .

Danke nochmals im vorraus, grüße

 

[Freak-X]

und ja ich weiss, der PC ist nicht der beste doch für meine Verhältnisse bzw. meinen Bedarf vollkommen ausreichend!

Spielt in diesem Fall doch gar keine Rolle; selbst wenn esein Pentium 3 wäre...

Alle Bluescreens scheinen irgendwie mit den Spielen zusammenzuhängen...

Hast du mal...

- Alle Treiber auf den neuesten Stand gebracht?
- Windows Update so oft durchgeführt, bis nichts mehr gefunden wird?
- Im Gerätemanager nach Ausrufezeichen/Fragezeichen geguckt?
- sfc/scannow ausgeführt? (Win+R und dann "CMD" eingeben; anschließend diesen Befehl)
- chkdsk C: /f laufen lassen? (Win+R und dann "CMD" eingeben; anschließend diesen Befehl)
- Den Autostart mal entrümpelt?
- Irgendwelche Einstellungen im BIOS verändert?

 

[myZID]

-Treiber alle auf dem neusten Stand (alles überprüft eben)
-Hatte acht Windows Updates übersehen/vergessen (aktuell nun auf dem neusten Stand/keine Updates mehr vorhanden)
-Im Gerätemanager sind keine Ausrufe bzw. Fragezeichen vorhanden
-sfc/scannow ausgeführt (Der Windows-Ressourcenschutz hat keine Integritätsverletzungen gefunden)
-chkdsk C: /f (alles inordnung.. soweit ich dies einschätzen kann)
-Autostart war schon entrümpelt. Hab es aber nochmal überprüft!
-IM BIOS hab ich nichts verändert, da ich davon 0 Plan habe. Sprich: Müsste alles auf Werkseinstellung sein.

Grüße und schonmal danke.

P.S. Werde jetzt erstmal ein Auge darauf werfen, ob ich gleich oder später nochmal einen Bluescreen bekomme.

Edit: Bekam grad während ich League of Legends gespielt hab wieder einen Bluescreen.

Hier die Daten

On Sun 02.02.2014 20:34:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020214-20280-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F64180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Problemsignatur:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.1.7601.2.1.0.768.3
Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:
BCCode: 101
BCP1: 0000000000000031
BCP2: 0000000000000000
BCP3: FFFFF88002F64180
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
C:\Windows\Minidump\020214-20280-01.dmp
C:\Users\User\AppData\Local\Temp\WER-76721-0.sysdata.xml

Lesen Sie unsere Datenschutzbestimmungen online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407

Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
C:\Windows\system32\de-DE\erofflps.txt

Hier noch Daten von Debugging Tools for Windows

Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0481e000 PsLoadedModuleList = 0xfffff800`04a616d0
Debug session time: Sun Feb 2 20:34:55.967 2014 (GMT+1)
System Uptime: 0 days 0:40:40.012
*********************************************************************
* 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols

Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002f64180, 2}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll -
***** 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 <symbol_path> 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntkrnlmp.exe

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

 

[Inzersdorfer]

Sowohl für den 0x1E als auch den 0x101 wird empfohlen die Kernspannung zu erhöhen
(increase Vcore/Core Voltage).

 

[myZID]

Gibts da irgendwie ne Anleitung? Habe nämlich Angst etwas falsch zu machen.

Grüße

 

[thompson004]

Du musst das Debuggen mit den richtigen Symbolen machen: http://support.microsoft.com/kb/311503/de
Zur Not kannst du mal Neu aufsetzen.

 

[myZID]

Habe grad durch Google diese Seite hier gefunden http://msdn.microsoft.com/en-us/windows/hardware/gg463028 dort kann man sich die debugging symbols runterladen würde das helfen? Wenn ja welche von den muss ich runterladen da gibt es Windwos 7 Service Pack 1 Windwos 7 RTM etc. und dann gibt es noch in den Unter kategorien Windows x86 etc. Wäre dankbar für Hilfe

Grüße

 

[thompson004]

du musst sie nicht runterladen. einfach das : SRV*Ihr lokaler Symbolordner*http://msdl.microsoft.com/download/symbols
unter "Symbol File Path" eingeben.
"Ihr lokaler Symbolordner" ersetzt du einfach durch einen Pfad wo MS die Symbole speichern soll. Danach machst du "Open Crash Dump" und !analyze -v.

 

[myZID]

Hallo Danke für die Antwort hab jetzt soweit alles gemacht und zwar wie beschrieben. Hier die Crash Dump Analyse

Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:/Symbole*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0481e000 PsLoadedModuleList = 0xfffff800`04a616d0
Debug session time: Sun Feb 2 20:34:55.967 2014 (GMT+1)
System Uptime: 0 days 0:40:40.012
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols

Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002f64180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f64180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:
------------------


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: d

STACK_TEXT:
fffff880`009a9768 fffff800`048eaa4a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx
fffff880`009a9770 fffff800`0489d6f7 : 00000000`00000000 fffff800`00000002 00000000`00002711 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`009a9800 fffff800`04e0d895 : fffff800`04e33460 fffff880`009a99b0 fffff800`04e33460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`009a9900 fffff800`04890113 : 00000000`38c85b6b fffff800`04a0ee80 00000000`00000000 fffff800`048b2ae4 : hal!HalpHpetClockInterrupt+0x8d
fffff880`009a9930 fffff800`048c9469 : fffff800`04a0ee80 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`009a9ac0 fffff800`04898a1c : 00000000`00000000 fffff880`009a9bf8 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x79
fffff880`009a9b00 fffff800`048566e9 : 00000000`00000010 00000000`00000000 fffffa80`03d139d0 00000000`00000010 : nt!KeFlushMultipleRangeTb+0x28c
fffff880`009a9bd0 fffff800`04856f37 : 00000000`00145b00 00000000`0000000f 00000000`00000000 00000000`00000000 : nt!MiZeroPageChain+0x14e
fffff880`009a9c10 fffff800`04b302ea : fffffa80`069d41b0 00000000`00000080 fffffa80`069d4740 fffff800`048848d9 : nt!MmZeroPageThread+0x83a
fffff880`009a9d40 fffff800`048848e6 : fffff800`04a0ee80 fffffa80`069d41b0 fffff800`04a1ccc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KiStartSystemThread+0x16


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

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

 

[thompson004]

Gut analysiert. Ich würde jetzt schon mal mit der Neuinstallation von Windows anfangen.

 

[myZID]

Alles klar, ich werde gleich/später den Rechner neu aufsetzen. Halte euch am laufenden. Aber eine Frage: Sollte ich wieder einen Bluescreen bekommen, dann kann ich von einem Hardware-Schaden ausgehen oder?

Grüße

 

[thompson004]

Ja, ich denke schon. Hast du irgendwelche besonderen Karten/Usb-Geräte noch angeschlossen? Solche können so etwas auch auslösen. Wenn nicht, dann könnten wir bei der Hardware weitersuchen.

 

[myZID]

Einen Drucker von Epson, der Treiber ist aber für Windows 7 64 bit Version und auf dem aktuellen Stand. Sonst keine weiteren USB Geräte bzw. Karten angeschlossen. Bin vor 35 min. mit allem fertig geworden sprich: Windows 7 neu installiert, alle Windows Updates (bis keine mehr kamen) und alle Treiber aktualisiert 2x überprüft! Tja, dann League of Legends ausprobiert und nach ca. 7 min. ingame Bluescreen ...

Hab die Crash Dump Datei auswerten lassen:

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 03.02.2014 17:15:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020314-37315-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EB180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 03.02.2014 17:15:32 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009EB180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


und:

Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02c9f6d0
Debug session time: Mon Feb 3 18:15:32.223 2014 (GMT+1)
System Uptime: 0 days 1:36:24.283
*********************************************************************
* 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols

Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff880009eb180, 1}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for cng.sys -
***** 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 <symbol_path> 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntkrnlmp.exe

Followup: MachineOwner

P.S. Habe einmal mit WhoCrashed auswerten lassen und mit Debugging Tools for Windows. Desweiteren kann ich den Rechner nicht aufschreiben (wegen 3 Jahren Garantie). Habe ihn jetzt 3 Tage und wollte ihn Morgen zurück schicken/umtauschen. Ist wohl das beste ... (dennoch bin ich angepisst irgendwie)

Grüße und danke für eure Hilfe (eventuell hat der ein oder andere noch einen Vorschlag?)

 

[thompson004]

Ok, für die Analyse hättest das ganze Prozedere mit dem Symbol File Path noch machen müssen, aber ist eh egal. Das ist definitiv ein Hardware-Problem, sagt eben auch "hal.dll"-Hardware Abstraction Layer.
ich würde mal alle Ram-Riegel entfernen und nur einen in Slot 1 Stecken und dann wieder Lol spielen.