PC Specs:
Cpu - i7-3770
Gpu - Gigibyte GTX 780TI OC 3GB
Motherboard - Gigibyte H77m
Ram - Kingstom HyperX 16GB (2x8GB) 1600mhz
SSD - Samsung 850 EVO 250gb
HDD - WD Black 3TB
Psu - FSP Aurum Gold 650w
OS - Windows 10 Pro
Around a month ago I installed windows 10 on a brand new ssd, until around 5 days ago it has been running perfectly. For some reason now when I put my desktop to sleep it wakes up 5-15 min later. I've dealt with this before in Win 8.1, disabling wake timers and network card options did the trick previously, but this time I cant figure it out.
In event manager the error that always shows up at the time of waking is "Event ID 129: Reset to device, \Device\RaidPort0" (source: storeahci)."
I am not running raid, though I am running in ahci mode. I am also using a New 3tb WD Black HDD for storage.
I rolled back using recovery to the 9th of September and it seemed to work initially. It did not wake up until I used my it, but after playing a game and putting it back into sleep mode the problem reared its head again...
Would appreciate any help.
Cpu - i7-3770
Gpu - Gigibyte GTX 780TI OC 3GB
Motherboard - Gigibyte H77m
Ram - Kingstom HyperX 16GB (2x8GB) 1600mhz
SSD - Samsung 850 EVO 250gb
HDD - WD Black 3TB
Psu - FSP Aurum Gold 650w
OS - Windows 10 Pro
Around a month ago I installed windows 10 on a brand new ssd, until around 5 days ago it has been running perfectly. For some reason now when I put my desktop to sleep it wakes up 5-15 min later. I've dealt with this before in Win 8.1, disabling wake timers and network card options did the trick previously, but this time I cant figure it out.
In event manager the error that always shows up at the time of waking is "Event ID 129: Reset to device, \Device\RaidPort0" (source: storeahci)."
I am not running raid, though I am running in ahci mode. I am also using a New 3tb WD Black HDD for storage.
I rolled back using recovery to the 9th of September and it seemed to work initially. It did not wake up until I used my it, but after playing a game and putting it back into sleep mode the problem reared its head again...
Would appreciate any help.