Random BSOD - error 1E

Sounds great. I hope your luck continues. If you would, let us know when you feel like the problem is resolved.

Are you overclocking your system? Are there any settings in bios that affect hibernate? I'm noy familiar with Gigabyte bios, but I know there are sone settings in an Asus bios which will affect hibernation. The debugger won't tell us a lot, but I noticed a side comment about trying to unlock the CMOS lock. It's blamed on not being able to wake up the CPU.

Code:

nt!PopHandleNextState+12a
fffff800`01ec2cb9 8be8            mov     ebp,eax
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  nt!PopHandleNextState+12a
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb
IMAGE_VERSION:  6.1.7601.18409
FAILURE_BUCKET_ID:  X64_0x5C_HAL_FAILED_TO_RESTART_PROCESSOR_AFTER_SLEEP_nt!PopHandleNextState+12a
BUCKET_ID:  X64_0x5C_HAL_FAILED_TO_RESTART_PROCESSOR_AFTER_SLEEP_nt!PopHandleNextState+12a
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x5c_hal_failed_to_restart_processor_after_sleep_nt!pophandlenextstate+12a
FAILURE_ID_HASH:  {a3f9a84b-3b7e-1e59-ab8e-459ed3091bc2}
Followup: MachineOwner

What the dump technicallt blames is IaStor, but I doubt that is correct

Code:

hiber_iaStorA
start             end                 module name
fffff880`1b41e000 fffff880`1b6e1000   hiber_iaStorA T (no symbols)           
    Loaded symbol image file: hiber_iaStorA.sys
    Image path: \SystemRoot\System32\Drivers\hiber_iaStorA.sys
    Image name: hiber_iaStorA.sys
    Timestamp:        Thu Apr 03 18:00:05 2014 (533DE7F5)
    CheckSum:         000ABC34
    ImageSize:        002C3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver created to provide disk access during crash dump file generation. I suspect that these are generated for crashes that occur during hibernation/sleep transitions

If your bios has a setting, Asus calls it Internal PLL overvoltage, enabled will disable sleep and hibernate. Whether Gigabyte has that or calls it something different, I don't know.

Another thing to try, if you use hibernate, which you shouldn't need with an SSD, open an elevated command prompt (click start, type cmd in the search box, Right click the entry that appears and select run as administrator) in the command prompt copy/paste this and see powercfg -h on

OK, just look at your CPU settings and make sure your S states are enabled.

Check your SSD and make sure your Firmware is up to date also run Seatools for DOS (SeaTools for DOS | Seagate) on your other hard drives. Please make sure your Windows Updates are Current. Look at installed updates and see if there have been any Failures.