wangelibgl
Cadet 4th Year
- Registriert
- Juli 2013
- Beiträge
- 117
Hallo Leute, Ich habe vor kurzem einen gebrauchten i7-4790K gekauft und ihn gegen meinen i5-4670K ersetzt. Seit dem habe ich das Problem, dass mein PC crasht (machmal Standbild oder Blackscreen und manchmal Bluescreen) mit einem brutalen Sound. Habe BIOS resetet, Windows neu installiert und auch Ram mehrmals umgesteckt, hat alles nichts gebracht. Es ist also ziemlich sicher, dass die CPU das Problem ist und defekt ist?. Treiber habe ich auch bereits aktualisiert und auch Driver Booster laufen lassen. Anbei ist auch noch die Dump Datei. Hoffe ihr könnt mir helfen!
Zu meinem System:
Und hier noch die Fehlermeldung von WhoCrashed:
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Tue 13.02.2018 00:45:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021318-5671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8006797DE26, 0xFFFFE506E708AE80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 13.02.2018 00:45:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x9549)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8006797DE26, 0xFFFFE506E708AE80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
Zu meinem System:
- i7-4790K
- MSI GTX 1070 Quicksilver (Baugleich Gaming X)
- ASUS Z87-Pro (C2)
- 16GB G.Skill Sniper DDR3-1866 DIMM CL9
- 120GB Samsung 840 Evo
- 2TB Seagate HDD
- 530 Watt be quiet!
- Bitfenix Shinobi USB 3.0 Midi Tower
- 27" Full HD Monitor (1080p)
- Mugen 5 CPU Kühler
Und hier noch die Fehlermeldung von WhoCrashed:
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Tue 13.02.2018 00:45:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021318-5671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8006797DE26, 0xFFFFE506E708AE80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 13.02.2018 00:45:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x9549)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8006797DE26, 0xFFFFE506E708AE80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.