Windows 10: BSOD only after waking computer from sleep 0x000000be

Are You sure they are on Gsata ports 0 and 1. The specs for your board state that the Chipset ports are sata3 ports 0 and 1, and sata II ports 2,3,4,5,. The Marvell ports, which you don't want to use, are designated as Gsata ports 6,7,8. In the System Specs below, you want the SSD and hard drive on the #1 under Chipset. Ports 0 and 1, not on the Marvell ports, which are listed as Gsata ports 6,7,8.

Attachment 35396

 

They are showing up in the marvell ATA controller config and not the ATA port information page. The DVD drive is in port 3 now though.

Figured it out. It was plugged into the GSATA ports. It was a tight fit in there and I couldnt see the markings on the board that well.

 

Yea, that's typical. They don't mark them for easy reading. Am I correct that you only have problems with sleep?

 

Yes I consistently have been able to recreate the stop message when I put the computer in sleep or it goes to sleep on its own and I try and wake it. At no other time have I had a stop message since installing 10. Some people had suggested turning off auto sleep mode and just putting it into hibernation instead. I have not tried this out yet.

 

Hibernation may be turned off. It does that many time when it detects an SSD. We've seen a lot of people have problems with sleep. I don't use it, so I don't know.

Try this. Right click the start button and select Command Prompt (Admin). copy/paste sfc /scannow and press enter. We want it to say no integrity violations were found. If it says files were found but couldn't be repaired, reboot and run it again. You may have to run it at lease 3 times with reboots in between each time.

 

It states that "Windows Resource Protection did not find any integrity violations."

 

Great. Try going to settings > System > select Power and sleep in the left column > click the link for additional power settings and select Balanced and close the window. See if that makes any difference.

 

Unfortunately it crashed again. Looking with Blue Screen View showed it was caused by hal.dll and the ntoskrnl.

 

ntoskrnl is basically the Windows Kernel. hal.dll is also an integral part of the operating system. Normally, if either of those were corrupted or malfunctioning, you would have more problems than just waking from sleep. Windows won't run without them. The debugger is required to blame something in a crash. They get blamed when it can't find anything else to blame. I'm sure you don't care to know all of that but....

Not all machines can run this, but give it a try. Open the Command Prompt (Administrator) and copy/paste this in it.
Dism /Online /Cleanup-Image /RestoreHealth and press enter. It will seem like it is doing nothing, but it is. It will tell you it ran successfully or give you an error, so just be patient. It can take from 15 minutes to a couple of hours, depending on what errors it needs to repair.

 

Hey sorry I had an early morning shift yesterday and was exhausted. The repair ran and stated that it completed successfully.

However after doing this I put the computer to sleep and it went to the lock screen and I was getting ready to type my password in when it crashed. A dump wasnt saved when I went to look it up.

 

Well, I'm about to run out of ideas other than setting the BIOS to defaults. But first, upload the DM Log collector again and let me see if anything is different.

 

The cause is most likely a bug in windows self.
I have seen others with almost the same problem, only disabling sleep mode works.

 

I agree. I just wanted to try and see if we could find a fix for it, but I have never found one yet. It seems that Windows 10 has an issue with sleep on some computers.

 

Here is the latest dump. I guess the issue is not the end of the world. Could be worse I suppose. So you are suggesting that hibernate might be a better solution that letting it sleep?

 

Try Hibernate and see how it works.