Standbild/Bluescreen Ursache unklar...

BlackDesert

Ensign
Registriert
Sep. 2012
Beiträge
229
Hallo CB Community,
seit einiger Zeit bekomme ich beim rändern von videos standbilder.
kann dann nur noch den pc "kalt" runterfahren.

Mein System: müsste noch alles in meinem Profil stehen außer die graka ist nun eine gtx 1060.

Mein WhoCrashed bericht:

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 06.02.2017 03:04:58 your computer crashed
crash dump file: C:\Windows\Minidump\020617-11793-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFF800030BF655)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 06.02.2017 03:04:58 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFF800030BF655)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Fri 20.01.2017 23:59:43 your computer crashed
crash dump file: C:\Windows\Minidump\012117-14648-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800D8CB028, 0xB0800000, 0x40151)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (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.



On Wed 18.01.2017 23:20:08 your computer crashed
crash dump file: C:\Windows\Minidump\011817-14008-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x210C2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880045B00C2, 0xFFFFF88007242558, 0xFFFFF88007241DB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread 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 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.


Kann mir bitte jemand weiterhelfen?

Gruß
BlackDesert
 
"MEMOK" - Taste auf dem MB sofort beim Start des MBs/PC drücken -

Im BIOS

"AMD Turbo Technology" = disabled

"Command Rate" = 2T

TESTEN
 
Wie hast du beim GPU-Tausch die alten Treiber entfernt und wann die neuen installiert?
Ist das wirklich alles an Hardware oder ist sonst noch was verbaut und/oder angeschloßen?
Memtest mal laufen gelassen?

Ansonsten: Besser als diese Textbatzen sind meisten Screenshots von BluescreensView. Da hat man die relevanten Infos viel übersichtlicher beisammen.
 
Erst mal danke an alle die hier geantwortet haben,
den "OC Mode" habe ich vom Bios aus ausgeschaltet.
berichte wieder in einigen tagen.

gruß
BlackDesert
 
Drei verschiedene Bugcheck Codes bei 4 BSOD, da würde ich mal einen RAM Test mit Memtest86 oder Memtest86+ empfehlen, denn Abstürze sind neben korrupte Dateien typische Zeichen für RAM Fehler. Teste alle Riegel so wie sie eingebaut sind, ändere da nichts und lass auch die BIOS Einstellungen so wie sie unter Windows betrieben werden, genau so müssen sie ja auch fehlerfrei laufen. Wenn es keine Fehler gibt, warte 6 PASS ob es so bleibt und wenn es Fehler gibt, teste zuerst mit den Standardeinstellungen neu, sollte übertaktet worden sein und danach teste die Riegel einzeln um zu sehen ob einer defekt ist oder ggf. eine andere Ursache vorliegt warum die möglicherweise auch fehlerfreien Riegel nicht fehlerfrei zusammenarbeiten wollen.
 
Also seit einer Woche ist nun nichts passiert alles läuft wieder wie gewohnt.

Nochmal danke an alle.


Bis zum nächsten mal wenn es heißt: der Blacky hat Probleme mit seinem PC ;):D
 
Hallo da bin ich wieder :rolleyes:
die bluescreens sind nu weg aber beim aufnehmen von videos bekomme ich nach knapp einer stunde ein standbild...zwischendurch sind auch kurze standbilder da...kommt die cpu nicht mit oder warum ist das so?
die kleinen/kurzen standbilder sind ja noch ok aber nicht wenn es garnicht mehr weiter geht.

Gruß
Blacky
 
Hast Du denn das RAM mal getestet? Wenn nicht, mache das mal, es schadet nie zu wissen ob nicht Fehler vorhanden sind, auch wenn Memtest86 nur hard-errors finden kann, also Fehler die bei beistimmten Bitkombinationen auftreten und keine soft-errors, also spontan gekippte Bits.

Bzgl. der Aufnahmen die nach einer Stunden stocken, würde ich mal die Temperaturen überwachen (z.B. HWInfo64, dort Sensors) und die S.M.A.R.T. Werte der Platte auf die ausgenommen wird posten.
 
IMAG0242.jpg

Prime 95 @64bit bericht nach einem 10 min test

[Mar 2 20:50] Worker starting
[Mar 2 20:50] Setting affinity to run worker on logical CPU #5
[Mar 2 20:50] Beginning a continuous self-test on your computer.
[Mar 2 20:50] Please read stress.txt. Choose Test/Stop to end this test.
[Mar 2 20:50] Test 1, 26000 Lucas-Lehmer iterations of M12451841 using AMD K10 type-2 FFT length 640K, Pass1=640, Pass2=1K.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Possible hardware failure, consult readme.txt file, restarting test.
[Mar 2 20:51] ERROR: ILLEGAL SUMOUT
[Mar 2 20:51] Maximum number of warnings exceeded.
[Mar 2 20:51] Torture Test completed 0 tests in 0 minutes - 0 errors, 100 warnings.
[Mar 2 20:51] Worker stopped.
 
Zuletzt bearbeitet:
Zurück
Oben