Question Gigabyte X399 Aorus 7 gaming rebooting on waking from sleep.

[boing]

I have a problem that just started yesterday, when I put my computer to sleep and try to wake it the system does a full reboot (and obviously dumps all my work) the specs are below, the only major software update was to the latest Win 10 build (1809) a couple of days ago plus Aorus gaming engine and RGB fusion to the latest versions. My Mobo is giving me an A5 error code which seems to be -"Issue reset during SCSI initialization process"

Could anyone point me in the right direction? I'm at a loss.

CPU: Threadripper 1950x
Mobo: Gigabyte X399 Aorus 7 gaming
GPU: Nvidia geforce GTX 1080 TI
RAM: 32gb G-skill F4-3200C14Q-32GFX
OS: Win 10 64 bit 1809 build
PSU: Seasonic Prime gold SSR-750GD

 

[UsandThem]

Tough to say.

Gigabyte has some of the worst apps/programs I've ever dealt with, so they could be the issue. However, Windows 10 updates have also been known to bork a PC or two here.

Does Windows show you the crash cause in the maintenance area (in the control panel, under the security and maintenance section)?

Otherwise, you can download and run this program to see if it can identify the issue:

https://www.nirsoft.net/utils/blue_screen_view.html

 

[boing]

Yes there are a couple of recurring errors, would they mean anything to you?

Problem Event Name: BlueScreen
Code: a0
Parameter 1: 608
Parameter 2: ffff9408e9402058
Parameter 3: 0
Parameter 4: 0

Problem Event Name: LiveKernelEvent
Code: 117
Parameter 1: ffffd90babb36010
Parameter 2: fffff8042ff76b2c
Parameter 3: 0
Parameter 4: 570

 

[boing]

I've updated the MB bios to the latest F11e but it made no difference. I have my RGB's set to be off but when the board resets I notice the MB lights are pulsing on, RGB Fusion was one of the things I updated recently, wonder if that may be an issue?

 

[boing]

Think I got this sussed, traced the problem to ntoskrnl.exe and one of the recommended solutions was to roll back any recently installed drivers, suddenly remembered I'd upgraded my M2 Samsung drivers so I rolled back and the problem is gone!