Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with AMD processors => Topic started by: paul bristow on February 08, 2019, 02:50:39 pm
-
I am getting persistent blue screen crashes with a variety of stop_code messages like Critical_structure_corruption, that all mean 'something went horribly wrong'
It is a fresh plain Windows 10 1809 installation, fully up-to-date. Just sitting idle except for running windows task manager, and resource manager, the MTBF is about 6 hours.
No overclocking, everything on auto, memory stock speed (and has done a 24 hours memtst86 test OK).
Processor test Passmark OK, and highest temperature of hottest CPU is 50 C (watercooled).
Motherboard BIOS is latest F5, AMD drivers latest too.
Tried two other graphics cards with similar results.
Any suggestions on what else to try?
Anyone with a similar configuration that works OK?
Thanks
Paul
Configuration below:
PerformanceTest Information:
PerformanceTest Version: 9.0 (Build 1030) WIN64
PassMark Rating: (N/A)
System Information:
System Name: HETPD
Model:
Operating System: Windows 10 Professional Edition build 17763 (64-bit)
Motherboard Manufacturer: Gigabyte Technology Co., Ltd.
Motherboard Model: X470 AORUS ULTRA GAMING-CF
Motherboard Version: x.x
BIOS Manufacturer: American Megatrends Inc.
BIOS Version: F5
BIOS Release Date: 2019/01/08
CPU Information:
Manufacturer: AuthenticAMD
Type: AMD Ryzen 7 1800X Eight-Core
Codename: Ryzen
CPUID: Family 17, Model 1, Stepping 1
Socket: AM4
Lithography: 14nm
Number of CPU's: 1
Cores per CPU: 8
Logicals per Core: 2
Clock Frequencies:
Measured Speed: 3286.2 MHz [Turbo: 4107.0 MHz]
Multiplier: 32.8X
Bus Speed: 100.2 MHz
Front Side Bus Speed: (N/A)
Timing Error Ratio: 1.000
Cache per CPU package:
L1 Instruction Cache: 16 x 32 KB
L1 Data Cache: 16 x 64 KB
L2 Cache Size: 16 x 512 KB
L3 Cache: 16 MB
Memory Information:
Total Physical Memory: 16330MB
Available Physical Memory: 13827MB
Memory Devices:
Slot 1: 8GB DDR4 SDRAM PC4-25600
Corsair CMK16GX4M2B3200C16
XMP: 1.35V, Clk: 1600.0MHz, Timings 16-18-18-36
Slot 2: 8GB DDR4 SDRAM PC4-25600
Corsair CMK16GX4M2B3200C16
XMP: 1.35V, Clk: 1600.0MHz, Timings 16-18-18-36
Slot 3:
Slot 4:
Virtual Memory: C:\pagefile.sys (2432MB)
Drive Information:
Physical Drive 0: ST4000DM004-2CV104
Drive Size: 3726GB
Partitions: K:
Interface Type: SATA
Bytes per Sector: 512
RPM: 5425
Drive Serial Number: ZFN0Q771
Physical Drive 1: ADATA SU650
Drive Size: 447GB
Partitions: D: G:
Interface Type: SATA
Bytes per Sector: 512
RPM: Solid State
Drive Serial Number: 2I4320016936
Physical Drive 2: WDC WD10EARS-00Y5B1
Drive Size: 931GB
Partitions:
Interface Type: SATA
Bytes per Sector: 512
RPM: Unknown
Drive Serial Number: WD-WCAV5S078030
Physical Drive 3: Samsung SSD 970 PRO 512GB
Drive Size: 476GB
Partitions: C: I:
Interface Type: NVMe
Bytes per Sector: 512
RPM: Solid State
Drive Serial Number: S463NF0K923655K
Physical Drive 4:
Drive Size:
Partitions:
Interface Type:
Bytes per Sector:
RPM:
Drive Serial Number:
Optical Drive 1: ATAPI iHAS124 F
Volume Information:
Volume 1: C: [Local Drive]
File System: NTFS
Drive Cluster Size: 4KB
Volume Size (Free space): 293.0GB (234.9GB)
Volume 2: D: [Local Drive]
File System: NTFS
Drive Cluster Size: 4KB
Volume Size (Free space): 203.0GB (202.8GB)
Volume 3: G: [Local Drive]
File System: NTFS
Drive Cluster Size: 4KB
Volume Size (Free space): 48.8GB (12.9GB)
Volume 4: I: [Local Drive]
File System: NTFS
Drive Cluster Size: 4KB
Volume Size (Free space): 183.4GB (183.3GB)
Volume 5: K: [Local Drive]
File System: NTFS
Drive Cluster Size: 4KB
Volume Size (Free space): 3726.0GB (3321.2GB)
Volume 6: M: [Optical drive]
File System:
Drive Cluster Size:
Volume Size (Free space):
Volume 7:
File System:
Drive Cluster Size:
Volume Size (Free space):
Video Adapters:
Video Card 1: NVIDIA Quadro P600
SLI/Crossfire Enabled: No
Chip Type: Quadro P600
DAC Type: Integrated RAMDAC
Memory: 2047MB
Video BIOS: Version86.7.3b.0.49
Driver Provider: NVIDIA
Driver Version: 25.21.14.1678
Driver Date: 11-1-2018
Monitor 1: 1920x1080x32 60Hz 96 DPI (Primary monitor)
Monitor 2:
Video Card 2:
SLI/Crossfire Enabled:
Chip Type:
DAC Type:
Memory:
Video BIOS:
Driver Provider:
Driver Version:
Driver Date:
Temperatures:
CPU 0: 33.0C (Maximum: 33.0C)
CPU Core 0:
CPU Core 1:
CPU Core 2:
CPU Core 3:
Hard Disk 0: 32.0C (Maximum: 32.0C)
Hard Disk 1: 22.0C (Maximum: 31.0C)
Hard Disk 2: 30.0C (Maximum: 30.0C)
Hard Disk 3: 37.0C (Maximum: 37.0C)
GPU 0: 40.0C (Maximum: 40.0C)
-
Greetings,
You have way too many connected devices, which will make bench testing or troubleshooting difficult.
I'd try running sfc /scannow from a elevated command prompt to start.
-
The latest bios is F6 - try this one but flush the bios first
-
Sfc /scannow and file system checks, backup and restore and normal Windows oepration are are OK.
Installed F6 (and chipset update with AGESA 1.006).
48 hours memtst86 ran OK
But gigabyte support still claim memory is No 1 suspect.
Memory Information:
Total Physical Memory: 16330MB
Available Physical Memory: 13827MB
Memory Devices:
Slot 1: 8GB DDR4 SDRAM PC4-25600
Corsair CMK16GX4M2B3200C16
XMP: 1.35V, Clk: 1600.0MHz, Timings 16-18-18-36
Slot 2: 8GB DDR4 SDRAM PC4-25600
Corsair CMK16GX4M2B3200C16
XMP: 1.35V, Clk: 1600.0MHz, Timings 16-18-18-36
This is not exactly in compatible memory list, but same specification.
(and I can't find any exact matches for sale - can anyone recommend a supplier of 'known good' memory type 16 Gbyte).
Tried three other graphics cards.
Same BSODs - about once per day.
Other symptom - sometimes POST hangs going round a cycle of LED lit: SYS,DRAM, VGA, SYS, DRAM, VGA ...
but reboots after a 20 second mains poweroff.
Suggestions very welcome.
-
I am running 16GB HyperX Predator 3200 and it's working just fine
https://www.amazon.com/HyperX-Predator-Technology-HX432C16PB3AK2-16/dp/B07GL6CLTT
I would start with xmp 3000 for a week and when all fine then switch to 3200
hope you got a quality psu?
Edit: If you have blue usb3 port problems when moving big files between usb3 devices install the GByte chipset driver just once then overwrite it with the current AMD drivers - this is fixing the issue ;)