Jump to content

I just recently bought a Ryzen 7 3700x to upgrade from my Ryzen 5 1600x. Since I installed the 3700x, I keep getting a BSOD that says WHEA_UNCORRECTABLE_ERROR. There is no code after that message to help identify the problem. It's been happening at least once every time I use my PC. It has never happened once until I switched CPU's. I finally figured out how to look at the MEMORY.DMP file and all I can get from it is that it's a PCIe error. Specifically "FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_pciexpress_venid_8086_devid_1539_unsupported_request_completion_timeout". I'll attach the full MEMORY.DMP file below. Any help in fixing this would be greatly appreciated.

 

PC Specs

CPU: Ryzen 7 3700x

Cooler: Cryorig H7

GPU: MSI Armor OC GTX 1080Ti

Mobo: Asrock x370 Taichi

RAM: 32gb G.SKILL Trident Z RBG 3200mhz cl14. 4 sticks of 8gb

OS: Windows 10 Pro 64 bit



MEMORY.DMP

Spoiler

 

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`64000000 PsLoadedModuleList = 0xfffff803`644475b0
Debug session time: Fri Sep 20 15:11:01.552 2019 (UTC - 4:00)
System Uptime: 0 days 0:35:23.167
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000003`8ba06018).  Type ".hh dbgerr001" for details
Loading unloaded module list
........
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000004, PCI Express Error
Arg2: ffff8b8d21051038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.

SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  To Be Filled By O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  P5.60

BIOS_DATE:  06/27/2019

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  X370 Taichi

BASEBOARD_VERSION:                        

DUMP_TYPE:  1

BUGCHECK_P1: 4

BUGCHECK_P2: ffff8b8d21051038

BUGCHECK_P3: 0

BUGCHECK_P4: 0

HARDWARE_VENDOR_ID:  8086

HARDWARE_DEVICE_ID:  1539

BUGCHECK_STR:  0x124_AuthenticAMD

CPU_COUNT: 10

CPU_MHZ: e10

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  BlackOps4.exe

CURRENT_IRQL:  7

ANALYSIS_SESSION_HOST:  RHJJ7CB

ANALYSIS_SESSION_TIME:  09-20-2019 15:41:54.0840

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

STACK_TEXT:  
fffff803`69275ce8 fffff803`63fa4fd8 : 00000000`00000124 00000000`00000004 ffff8b8d`21051038 00000000`00000000 : nt!KeBugCheckEx
fffff803`69275cf0 fffff803`677a1920 : ffff8b8d`21060a40 00000000`00000000 ffff8b8d`21051038 00000000`00000000 : hal!HalBugCheckSystem+0xd8
fffff803`69275d30 fffff803`643406d2 : ffff8b8d`21060a40 fffff803`69275db9 00000000`00000000 ffff8b8d`21051038 : PSHED!PshedBugCheckSystem+0x10
fffff803`69275d60 fffff803`67ffe5d4 : 00000000`00000000 00000000`00000000 ffff8b8d`210611b0 ffff8b8d`21050410 : nt!WheaReportHwError+0x382
fffff803`69275e20 fffff803`67ffed52 : ffffe700`80fcbc80 fffff803`69275ec0 ffffe700`80fcbd30 00000707`bad3078c : pci!ExpressRootPortAerInterruptRoutine+0x270
fffff803`69275e80 fffff803`67ffee09 : ffffe700`80fcbc80 00000000`00000000 fffff803`69275fb0 00000000`00000f32 : pci!ExpressRootPortInterruptRoutine+0x22
fffff803`69275ee0 fffff803`641141f1 : 00000000`00000000 ffff8b8d`1b431000 ffffe700`8169b470 fffff803`00000002 : pci!ExpressRootPortMessageRoutine+0x9
fffff803`69275f10 fffff803`640029e5 : fffff803`686ef950 00000000`00008301 fffff803`69275fc0 00000000`00000008 : nt!KiInterruptMessageDispatch+0x11
fffff803`69275f40 fffff803`641c28bf : fffff803`6926ea00 ffffe700`80fcbc80 00000000`00000000 ffffe700`817f58c0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`69275f90 fffff803`641c2b87 : ffffe700`8169b470 00000000`00000000 00000000`00000000 ffff8b8d`21f93030 : nt!KiInterruptSubDispatch+0x11f
fffff803`6926e980 fffff803`686ef14e : fffff803`6926ed40 ffff8b8d`21f936e8 00000000`00000000 fffff803`6c94750c : nt!KiInterruptDispatch+0x37
fffff803`6926eb10 fffff803`6406b065 : fffff803`61843f80 ffff8b8d`1b431000 ffff8b8d`21533a10 fffff803`00000002 : ndis!ndisInterruptDpc+0x1e
fffff803`6926ec40 fffff803`6406a6bf : fffff803`61841180 00000000`00000000 00000000`00000002 00000000`00000005 : nt!KiExecuteAllDpcs+0x305
fffff803`6926ed80 fffff803`641c80e5 : 00000000`00000000 fffff803`61841180 ffffe700`817f58c0 00000146`ed9fad00 : nt!KiRetireDpcList+0x1ef
fffff803`6926efb0 fffff803`641c7ed0 : fffff803`63f766c0 fffff803`63f602ca 00000146`ed9fa378 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffc80f`e5299ac0 fffff803`641c7785 : 00000146`ed9fad00 fffff803`641c2c01 00000000`00080000 ffffc80f`e5299b80 : nt!KiDispatchInterruptContinue
ffffc80f`e5299af0 fffff803`641c2c01 : 00000000`00080000 ffffc80f`e5299b80 ffffe700`817f58c0 ffffc80f`e5299b80 : nt!KiDpcInterruptBypass+0x25
ffffc80f`e5299b00 00007ffb`ca32e987 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0xb1
00000003`8b95fa48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`ca32e987


THREAD_SHA1_HASH_MOD_FUNC:  51db0aed4233f2e8b741902f14e7c65abb3e0b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ad88f4dd472b12dc4c23b0bb075a75471b116d6b

THREAD_SHA1_HASH_MOD:  8d8faa16b10bbba3a8c49adc2db3257dbf7d8245

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PCIEXPRESS_VENID_8086_DEVID_1539_UNSUPPORTED_REQUEST_COMPLETION_TIMEOUT

BUCKET_ID:  0x124_AuthenticAMD_PCIEXPRESS_VENID_8086_DEVID_1539_UNSUPPORTED_REQUEST_COMPLETION_TIMEOUT

PRIMARY_PROBLEM_CLASS:  0x124_AuthenticAMD_PCIEXPRESS_VENID_8086_DEVID_1539_UNSUPPORTED_REQUEST_COMPLETION_TIMEOUT

TARGET_TIME:  2019-09-20T19:11:01.000Z

OSBUILD:  18362

OSSERVICEPACK:  356

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  4d27

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_pciexpress_venid_8086_devid_1539_unsupported_request_completion_timeout

FAILURE_ID_HASH:  {d761fe41-5ac2-5175-49e1-5aa67d406509}

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

 

 

 

 

Link to comment
https://linustechtips.com/topic/1106230-whea-uncorrectable-error/
Share on other sites

Link to post
Share on other sites

Did you try clear CMOS?

CPU: i7-2600K 4751MHz 1.44V (software) --> 1.47V at the back of the socket Motherboard: Asrock Z77 Extreme4 (BCLK: 103.3MHz) CPU Cooler: Noctua NH-D15 RAM: Adata XPG 2x8GB DDR3 (XMP: 2133MHz 10-11-11-30 CR2, custom: 2203MHz 10-11-10-26 CR1 tRFC:230 tREFI:14000) GPU: Asus GTX 1070 Dual (Super Jetstream vbios, +70(2025-2088MHz)/+400(8.8Gbps)) SSD: Samsung 840 Pro 256GB (main boot drive), Transcend SSD370 128GB PSU: Seasonic X-660 80+ Gold Case: Antec P110 Silent, 5 intakes 1 exhaust Monitor: AOC G2460PF 1080p 144Hz (150Hz max w/ DP, 121Hz max w/ HDMI) TN panel Keyboard: Logitech G610 Orion (Cherry MX Blue) with SteelSeries Apex M260 keycaps Mouse: BenQ Zowie FK1

 

Model: HP Omen 17 17-an110ca CPU: i7-8750H (0.125V core & cache, 50mV SA undervolt) GPU: GTX 1060 6GB Mobile (+80/+450, 1650MHz~1750MHz 0.78V~0.85V) RAM: 8+8GB DDR4-2400 18-17-17-39 2T Storage: HP EX920 1TB PCIe x4 M.2 SSD + Crucial MX500 1TB 2.5" SATA SSD, 128GB Toshiba PCIe x2 M.2 SSD (KBG30ZMV128G) gone cooking externally, 1TB Seagate 7200RPM 2.5" HDD (ST1000LM049-2GH172) left outside Monitor: 1080p 126Hz IPS G-sync

 

Desktop benching:

Cinebench R15 Single thread:168 Multi-thread: 833 

SuperPi (v1.5 from Techpowerup, PI value output) 16K: 0.100s 1M: 8.255s 32M: 7m 45.93s

Link to post
Share on other sites

11 minutes ago, GeT_drAWPed said:

I just recently bought a Ryzen 7 3700x to upgrade from my Ryzen 5 1600x. Since I installed the 3700x, I keep getting a BSOD that says WHEA_UNCORRECTABLE_ERROR. There is no code after that message to help identify the problem. It's been happening at least once every time I use my PC. It has never happened once until I switched CPU's. I finally figured out how to look at the MEMORY.DMP file and all I can get from it is that it's a PCIe error. Specifically "FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_pciexpress_venid_8086_devid_1539_unsupported_request_completion_timeout". I'll attach the full MEMORY.DMP file below. Any help in fixing this would be greatly appreciated.

 

PC Specs

CPU: Ryzen 7 3700x

Cooler: Cryorig H7

GPU: MSI Armor OC GTX 1080Ti

Mobo: Asrock x370 Taichi

RAM: 32gb G.SKILL Trident Z RBG 3200mhz cl14. 4 sticks of 8gb

OS: Windows 10 Pro 64 bit



MEMORY.DMP

  Reveal hidden contents

 

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`64000000 PsLoadedModuleList = 0xfffff803`644475b0
Debug session time: Fri Sep 20 15:11:01.552 2019 (UTC - 4:00)
System Uptime: 0 days 0:35:23.167
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000003`8ba06018).  Type ".hh dbgerr001" for details
Loading unloaded module list
........
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000004, PCI Express Error
Arg2: ffff8b8d21051038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.

SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  To Be Filled By O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  P5.60

BIOS_DATE:  06/27/2019

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  X370 Taichi

BASEBOARD_VERSION:                        

DUMP_TYPE:  1

BUGCHECK_P1: 4

BUGCHECK_P2: ffff8b8d21051038

BUGCHECK_P3: 0

BUGCHECK_P4: 0

HARDWARE_VENDOR_ID:  8086

HARDWARE_DEVICE_ID:  1539

BUGCHECK_STR:  0x124_AuthenticAMD

CPU_COUNT: 10

CPU_MHZ: e10

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  BlackOps4.exe

CURRENT_IRQL:  7

ANALYSIS_SESSION_HOST:  RHJJ7CB

ANALYSIS_SESSION_TIME:  09-20-2019 15:41:54.0840

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

STACK_TEXT:  
fffff803`69275ce8 fffff803`63fa4fd8 : 00000000`00000124 00000000`00000004 ffff8b8d`21051038 00000000`00000000 : nt!KeBugCheckEx
fffff803`69275cf0 fffff803`677a1920 : ffff8b8d`21060a40 00000000`00000000 ffff8b8d`21051038 00000000`00000000 : hal!HalBugCheckSystem+0xd8
fffff803`69275d30 fffff803`643406d2 : ffff8b8d`21060a40 fffff803`69275db9 00000000`00000000 ffff8b8d`21051038 : PSHED!PshedBugCheckSystem+0x10
fffff803`69275d60 fffff803`67ffe5d4 : 00000000`00000000 00000000`00000000 ffff8b8d`210611b0 ffff8b8d`21050410 : nt!WheaReportHwError+0x382
fffff803`69275e20 fffff803`67ffed52 : ffffe700`80fcbc80 fffff803`69275ec0 ffffe700`80fcbd30 00000707`bad3078c : pci!ExpressRootPortAerInterruptRoutine+0x270
fffff803`69275e80 fffff803`67ffee09 : ffffe700`80fcbc80 00000000`00000000 fffff803`69275fb0 00000000`00000f32 : pci!ExpressRootPortInterruptRoutine+0x22
fffff803`69275ee0 fffff803`641141f1 : 00000000`00000000 ffff8b8d`1b431000 ffffe700`8169b470 fffff803`00000002 : pci!ExpressRootPortMessageRoutine+0x9
fffff803`69275f10 fffff803`640029e5 : fffff803`686ef950 00000000`00008301 fffff803`69275fc0 00000000`00000008 : nt!KiInterruptMessageDispatch+0x11
fffff803`69275f40 fffff803`641c28bf : fffff803`6926ea00 ffffe700`80fcbc80 00000000`00000000 ffffe700`817f58c0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`69275f90 fffff803`641c2b87 : ffffe700`8169b470 00000000`00000000 00000000`00000000 ffff8b8d`21f93030 : nt!KiInterruptSubDispatch+0x11f
fffff803`6926e980 fffff803`686ef14e : fffff803`6926ed40 ffff8b8d`21f936e8 00000000`00000000 fffff803`6c94750c : nt!KiInterruptDispatch+0x37
fffff803`6926eb10 fffff803`6406b065 : fffff803`61843f80 ffff8b8d`1b431000 ffff8b8d`21533a10 fffff803`00000002 : ndis!ndisInterruptDpc+0x1e
fffff803`6926ec40 fffff803`6406a6bf : fffff803`61841180 00000000`00000000 00000000`00000002 00000000`00000005 : nt!KiExecuteAllDpcs+0x305
fffff803`6926ed80 fffff803`641c80e5 : 00000000`00000000 fffff803`61841180 ffffe700`817f58c0 00000146`ed9fad00 : nt!KiRetireDpcList+0x1ef
fffff803`6926efb0 fffff803`641c7ed0 : fffff803`63f766c0 fffff803`63f602ca 00000146`ed9fa378 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffc80f`e5299ac0 fffff803`641c7785 : 00000146`ed9fad00 fffff803`641c2c01 00000000`00080000 ffffc80f`e5299b80 : nt!KiDispatchInterruptContinue
ffffc80f`e5299af0 fffff803`641c2c01 : 00000000`00080000 ffffc80f`e5299b80 ffffe700`817f58c0 ffffc80f`e5299b80 : nt!KiDpcInterruptBypass+0x25
ffffc80f`e5299b00 00007ffb`ca32e987 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0xb1
00000003`8b95fa48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`ca32e987


THREAD_SHA1_HASH_MOD_FUNC:  51db0aed4233f2e8b741902f14e7c65abb3e0b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ad88f4dd472b12dc4c23b0bb075a75471b116d6b

THREAD_SHA1_HASH_MOD:  8d8faa16b10bbba3a8c49adc2db3257dbf7d8245

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PCIEXPRESS_VENID_8086_DEVID_1539_UNSUPPORTED_REQUEST_COMPLETION_TIMEOUT

BUCKET_ID:  0x124_AuthenticAMD_PCIEXPRESS_VENID_8086_DEVID_1539_UNSUPPORTED_REQUEST_COMPLETION_TIMEOUT

PRIMARY_PROBLEM_CLASS:  0x124_AuthenticAMD_PCIEXPRESS_VENID_8086_DEVID_1539_UNSUPPORTED_REQUEST_COMPLETION_TIMEOUT

TARGET_TIME:  2019-09-20T19:11:01.000Z

OSBUILD:  18362

OSSERVICEPACK:  356

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  4d27

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_pciexpress_venid_8086_devid_1539_unsupported_request_completion_timeout

FAILURE_ID_HASH:  {d761fe41-5ac2-5175-49e1-5aa67d406509}

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

 

 

 

 

1. Clear CMOS after changing the processor

2. Take away any overclocking (CMOS reset will do this)

3. Update your BIOS

I enjoy buying junk and sinking more money than it's worth into it to make it less junk.

Link to post
Share on other sites

5 minutes ago, aisle9 said:

1. Clear CMOS after changing the processor

2. Take away any overclocking (CMOS reset will do this)

3. Update your BIOS

I just cleared CMOS, but I won't really know if that worked for a while. The CPU is not overclocked at all, and I updated the BIOS before installing the new CPU. I just realized that BIOS version 5.80 (I have 5.60) actually does support Matisse, I thought it didn't. I will try updating to 5.80 too.

         
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×