New
#1
Different Bug Check codes in ntoskrnl.exe only after wakeup from sleep
Disclaimer: I'm starting this crosspost to the microsoft forums since there where only 16 views in 5 days and only one reply and I've come to some conclusion. I'm curios if thats reasonably and maybe here is someone around with more Windows debugging experience than me who can pin point it some more.
____________________________________________________________________________________________________ __________
Post:
The system is a new build (2 weeks) for gaming mostly and i commonly run into a system that won't wake up after putting it into the sleep mode. It's not always the case, but maybe 1 out of 3 times, it won't wake up properly. After trying it to wake up per keyboard/mouse, the power LEDs lid up for maybe 1-2 secs and then the system shuts down. When i press a random key on the keyboard, the num lock LED still turns on.
Besides the mini dumps, i also get "Event 41 - Kernel Power" entries in the system log. Bug Check Codes: 0xd1, 0x1e, 0xef.
- The system is new, so maybe hardware related?
- The Stop Codes only happen after sleep during wake up so far.
- I am sure that i had the same problem with the one week i was running Windows 8.1 before i updated to Windows 10. So it's maybe not Windows 10 related.
- I did run a sfc /scannnow, it passed without errors.
- memtest86 run for 8h without any error.
- I already removed a gigabyte driver gdrv.sys, after I tired to solve the problem and thought it is driver related. I ran verifier.exe on non microsoft drivers turning on everything except Force IRQL Checking and Low Resource Simulation and in the one day i way running it, that driver caused some shutdowns.
- I already updated all drivers and the bios (F8)
- SMART long tests without errors
- chkdsk /F /R C: is also clean
- I almost uninstalled all software with drivers (.sys) except those for (well known) Hardware. Not that much was installed yet, but ..
So, my main question, can it even be a hardware problem, even though it happens only during wake up after a sleep, otherwise the system is just fine (run for 3 days without problems)?!
The mcupdate_GenuineIntel.dll in the stack trace makes me think it's either a Windows software fault (unlikely) or a hardware issue with my Gigabyte Mainboard and/or the Intel CPU. Is that reasonable, or any other thing i could test before RMA? Maybe run a linux and see if i can sleep/suspend there? But than i again, i'm not sure what that would prove at all..
Thanks in advance for any hints, Johannes.
Last edited by johanneszab; 18 Aug 2015 at 14:07.