BSOD στα καλα καθουμενα

[IceFrog]

Το Σαββατο εστησα τον υπολογιστη μου.
Δουλεψε μεχρι σημερα αψογα, χωρις το παραμικρο προβλημα και σημερα με τρελανε στα bsod με τα περισσοτερα να εχουν να κανουν με memory.
Τρεχω το windows memory diagnostic και περναει κανονικα χωρις error. Memtest δεν με αφηνει να τρεξω παιρνω το error could not start cpu 0 (ειναι θεμα που εμφανιζεται σε αρκετους με gigabyte μητρικες)
Ειπα να κανω και ενα τεστ τον ssd μηπως μου δημιυργει αυτος το θεμα, και οταν παω να τρεξω check disk τρωω ξανα bsod. Στο hard disk sentnel μου τον βγαζει μεν με υγεια 100% αλλα γραφει το παρακατω μηνυμα σαν παρατηρηση

Problems occurred between the communication of the disk and the host 6234 times.

In case of sudden system crash, reboot, blue-screen-of-death, inaccessible file(s)/folder(s), it is recommended to verify data and power cables, connections - and if possible try different cables to prevent further problems.

More information: http://www.hdsentinel.com/hard_disk_case_communication_error.php

The TRIM feature of the SSD is supported and enabled for optimal performance.

The health is determined by SSD specific S.M.A.R.T. attribute(s):  #231 SSD Life Left

 

No actions needed.

Τα windows τα περασα ξανα σημερα 

Cpu g4560
Mobo gigabyte 110m ds2
Ram corsair vengeance 2133

Καμια ιδεα γιατι κοντεύω να τρελαθω?
Να επαναλαβω πως απο το Σαββατο μεχρι και χτες δουλευε αψογα.

[BlueBlood7]

Με τα ενσωματωμένα γραφικά λειτουργείς?

 

Τροφοδοτικό ποιο έχεις?

[IceFrog]

Η καρτα γραφικων μου ειναι η rx 460
Το τροφοδοτικο μου ειναι coolermaster 750wat, δεν θυμαμαι ακριβως το μοντελο.

[BlueBlood7]

1) Αν μπορείς βρες μια άλλη μνήμη από κάποιον γνωστό σου να την δοκιμάσεις 1-2 μέρες. Αν σου βγάλει πάλει BSOD κάνεις το 2)

2) Απεγκατέστησε τους drivers της 460 με το DDU σε safe mode, αφαίρεσέ την και μείνε με τα ενσωματωμένα γραφικά. Κάτσε έτσι ένα διάστημα.

 

Καλό είναι να ανεβάσεις τα minidumps.

[IceFrog]

Πριν λιγο διαβασα τα bumps με το whocrashed 
ολα λενε πως το πιο πιθανο ειναι να εχω θεμα driver
Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 7/11/2017 11:56:16 AM your computer crashed
crash dump file: C:\Windows\Minidump\071117-5593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1A (0x61941, 0xFFFFC0011592D933, 0x9, 0xFFFFD00131773740)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (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 Tue 7/11/2017 11:56:16 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ci.dll (CI!Ordinal3+0x71F6)
Bugcheck code: 0x1A (0x61941, 0xFFFFC0011592D933, 0x9, 0xFFFFD00131773740)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ci.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Code Integrity Module
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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 Tue 7/11/2017 10:43:24 AM your computer crashed
crash dump file: C:\Windows\Minidump\071117-5390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1A (0x5012, 0xFFFFF58010804000, 0x16587, 0x1DD49)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (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 Tue 7/11/2017 10:34:47 AM your computer crashed
crash dump file: C:\Windows\Minidump\071117-5687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFECB3968, 0x20000000000, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (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 Tue 7/11/2017 10:11:55 AM your computer crashed
crash dump file: C:\Windows\Minidump\071117-6812-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x11410)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800A3991410, 0xFFFFD0019F9762C8, 0xFFFFD0019F975AE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms2.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.



 

Και μολις ειδα οτι η gigabyte εβγαλε νεο bios update.. το περναω και αυτο μια..

Αποσυνδεσα ολους τους δισκους και αφησα μονο τον ssd με τα windows τον οποιο εβαλα σε αλλη θυρα και με αλλο καλωδιο.
Αφου δεν διρθωθηκε με ουτε με το bios update, αυριο θα κανω δοκιμη τις ραμ σε αλλο μηχανημα...

[m04d18]

Γενικα οι h110 μητρικες χρειαζονται Bios update για να υποστιριξουν Kaby Lake επεξεργαστες οπως ο g4560 .

( Αν και συνηθως δεν κανουν ουτε post πριν το update) .  

 

https://www.gigabyte.com/Motherboard/GA-H110M-S2-rev-10#support-dl

---> Support --> Downloads --> Bios ---> F20

 

[BlueBlood7]

Γενικα οι h110 μητρικες χρειαζονται Bios update για να υποστιριξουν Kaby Lake επεξεργαστες οπως ο g4560 .

( Αν και συνηθως δεν κανουν ουτε post πριν το update) .  

 

https://www.gigabyte.com/Motherboard/GA-H110M-S2-rev-10#support-dl

 

---> Support --> Downloads --> Bios ---> F20

 

 

Γενικλα οπου κολλάει αυτό?