Win 10 PC is not waking up from sleep anymore. BSOD (System_service_exception -ntoskrnl.exe+197680)

Toggle sidebar Toggle sidebar
B

Blarzor

Distinguished
Nov 1, 2011
137
0
18,690
PC:

- Ryzen 7 1700 @ 3.6 Ghz

- 32 GB Ram - G.Skill Ripjaws V F4-3200C16D-32GVK running at 2666 Mhz 14-14-14-34 2T.

- GA-AB350-Gaming 3 Motherboard (bios F23d)

- 512 GB SSD Crucial MX 100

- 2 TB HDD

So strange things have been happening to me for last 2 weeks. First, my PC crashed every time I entered Ebay.co.uk's login page with BSOD bad_pool_caller. I fixed that problem by updating all my PC drivers and installing latest F23d bios from Gigabyte website. I also had to create new Firefox profile though, because with my default one, the Firefox wouldn't even start. That problem was solved.

Now after fixing first problem, I noticed that my PC crashes every time I try to wake it from sleep (I used to put PC to sleep all the time and it woke up normally). I don't even get any blue screen or anything on wake, I just see the HDD light shining still until the PC shuts down after 10 seconds.

Using BlueScreenView, I noticed that the reason for crash is:

- Address in Stack: ntoskrnl.exe+1aa829.

- Caused by Address: ntoskrnl.exe+197680

There used to be FLTMGR.SYS paired together with ntoskrnl.exe as cause of crash in the past but now I can't replicate it and only ntoskrnl.exe shows up as culprit.

Let me know what scans you guys need to diagnose this.

 
Solution
B
TL;DR: If your PC doesn't wake up from sleep after installing later bioses like F22 or F23d (maybe even a few earlier versions). Make sure to set "Global C-State Control" to "Auto".

Longer version:

So I downgraded my Bios to F22 from F23d, however my PC still wasn't waking up from sleep when I set all my overclocks back. I checked Bios a bit more and decided to turn "Global C-State Control" from "Disabled" to "Auto" and voilà! My PC wakes up from sleep once again!

I don't know what changed with later versions of Gigabyte bioses but the older F8 version of bios could wake up the PC with "Global C-State Control" turned OFF.

Thanks to everyone for help. Sohom definitely gave me the idea to try and mess around with C-State setting even...
Sort by date Sort by votes
Can you follow option one on the following link - here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)
 
Upvote 0 Downvote


Thanks! Here is a link to my crash dump. I uploaded it on Mega.nz since I really don't know what websites are good for uploading this kind of things.(so don't get scared by strange link)

https://mega.nz/#!xK5yHJ4Y!a3L6vcoIQ3wVqsc4W1zktExncFdeEEEKtH_cjPQcJQk

 
Upvote 0 Downvote
I'm still looking for assistance.

Meanwhile, I did memtest86 to test the memory stability. I did the stock test that starts autorunning after a few seconds when you load memtest from the usb stick. The test lasted about 7 hours and came up with 0 errors. Everything seems to be ok with RAM.
 
Upvote 0 Downvote
Upvote 0 Downvote
update your webcam drivers, they are from 2009

not sure what this is but its older
Oct 17 2008 - inpoutx64.sys - Kernel level port access driver http://www.highrez.co.uk/
Click to expand...

My own port of the versatile Dynamic Link Library for parallel port interfacing originally written by Logix4U
Click to expand...
thats from above link to highrez

The sleep error could be caused by any driver that doesn't like the new Win 10 power modes, the above 2 could be the cause.
 
Upvote 0 Downvote
I don't like this option but only as it can put you into a boot loop. As such, do one of the next two things before running driver verifer

1. It helps to run system restore before hand to create a system restore point to roll back to if necessary.

2. note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again. Download the Windows 10 media creation tool and use it to make a win 10 installer on USB

try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers. Once it bsod, upload the minidump file and we see what it shows us.

this should show us what is causing the BSOD as the dumps aren't.
 
Upvote 0 Downvote
Hey guys, just an update, I completely forgot to remove my overclocks etc... After setting my bios settings to default, my PC wakes from sleep mode normally. What does this say about the wake problem when my PC is overclocked? My PC was always overclocked with same settings, I just think that something changed probably after bios update? My last bios version jump was big, it was from F8 to F23d so something must have changed right?

My bios on default is not completely bug free though, after 2 or 3 mintues I got the Driver_power_state_failure BSOD which is apparently nothing serious and probably has something to do with mismatch between my power saving settings in windows and bios I'm assuming?

Another thing I noticed @Sohom , Global C-State is disabled in my bios, does that have something to do with my pc not waking from sleep when overclocked? I'm just asking because you mentioned C-state.

I don't remember the exact timing of events. But I think that I updated my Bios to F23d AFTER the Ebay login page bsod's since I thought it would fix the problem (that was not the thing that fixed it I think). Reading on the internet, it seems that lots of people are unhappy with F23d since it causes many problems for them. Should I try downgrading to F10 or F8 to see if wake issue goes away when OC'd?
 
Upvote 0 Downvote

First of all, i would like you to check whether downgrade is possible after updating to a partciular bios(in this regard, the F23d). I always advice people to update bios in sequential order as that helps avoid many unseen issues;
Now, if everything works perfect now, i would advice you to leave everything as it is. If there are issues, try downgrading to the previous bios version you had, if downgrade is possible. And after every bios update, i would advice to clear the cmos or reset the bios.
 
Upvote 0 Downvote
TL;DR: If your PC doesn't wake up from sleep after installing later bioses like F22 or F23d (maybe even a few earlier versions). Make sure to set "Global C-State Control" to "Auto".

Longer version:

So I downgraded my Bios to F22 from F23d, however my PC still wasn't waking up from sleep when I set all my overclocks back. I checked Bios a bit more and decided to turn "Global C-State Control" from "Disabled" to "Auto" and voilà! My PC wakes up from sleep once again!

I don't know what changed with later versions of Gigabyte bioses but the older F8 version of bios could wake up the PC with "Global C-State Control" turned OFF.

Thanks to everyone for help. Sohom definitely gave me the idea to try and mess around with C-State setting even though he didn't mention that setting directly.

Now everything works correctly with all my overclock settings copied from my old F8 bios, except for the "Global C-State Control" of course. I still suggest to everyone NOT TO install F23d BIOS because It's extremely buggy for most people and I had lots of random BSOD's using it. On F22 everything seems fine.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom