Solved Every night I set computer to sleep...every morning, BSOD

[mcplums]

As title says. The comp doesn't go BSOD immediately when I press sleep, it just goes to sleep and the display goes off as usual. It must come on and BSOD itself a few hours later when I'm asleep.

I havn't had a single BSOD during normal computer use.

Any ideas?!

 

[Gator]

Hello mcplums, please follow the instructions below and post the required information.

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[mcplums]

Ah many apologies, I did not see this requirement. Uploaded.

 

[mcplums]

I'd like to add that I've just had my first BSOD during normal use. It's a bit worrying. This is a new build so I can't pin it on any single piece of hardware if indeed it is hardware related.

 

[Gator]

I'd like to add that I've just had my first BSOD during normal use. It's a bit worrying. This is a new build so I can't pin it on any single piece of hardware if indeed it is hardware related.

Ok mcplums, I will start to analyze your BSOD now. In the meantime, go through the steps below. Sometimes this can find and/or fix the problem.

http://www.sevenforums.com/tutorials/220165-troubleshooting-steps-windows-7-a.html

 

[mcplums]

Thanks a lot buddy.

That is an extensive list! I have decided to start off by swapping out the RAM that I have from another pc and also checking all the cables. After doing so I noticed...that there are noises in the title sequences of Far Cry 4 that weren't there before?!?!? It is possible that they patched it very recently, but perhaps this could indicate some problem with the old RAM!? Apologies if this is completely irrelevant.

Anyway, I had three BSODs during normal operation today (from zero over the previous week- i.e. the problem is quickly getting worse) so I should be able to tell pretty soon if the new RAM is making a difference.

Thanks again for your help. If you don't mind me asking, what do you get out of helping strangers on the internet? I am glad that people like you exist, but I must admit I'm not sure why you spend your free time doing this! Maybe I'm just a selfish dick! Regardless, it is much appreciated!

 

[Gator]

Thanks a lot buddy.

That is an extensive list! I have decided to start off by swapping out the RAM that I have from another pc and also checking all the cables. After doing so I noticed...that there are noises in the title sequences of Far Cry 4 that weren't there before?!?!? It is possible that they patched it very recently, but perhaps this could indicate some problem with the old RAM!? Apologies if this is completely irrelevant.

Anyway, I had three BSODs during normal operation today (from zero over the previous week- i.e. the problem is quickly getting worse) so I should be able to tell pretty soon if the new RAM is making a difference.

Thanks again for your help. If you don't mind me asking, what do you get out of helping strangers on the internet? I am glad that people like you exist, but I must admit I'm not sure why you spend your free time doing this! Maybe I'm just a selfish dick! Regardless, it is much appreciated!

Most of us are nerds so we enjoy doing this stuff anyway. Aside from that, its great experience and believe it or not, for someone with little real world experience, it helps to add this on a resume for community service. Im still analyzing your dumps and will upload a fix soon.

They all point to hardware though and possibly your CPU overheating. Pay close attention to the part of the tutorial that references checking your temps. If you overclock, I'd advise stopping immediately, at least for the time being.

 

[mcplums]

Interesting stuff! Thanks for replying!

Anyway- I think it's unlikely to be a CPU issue since this originally arose only after the computer sleeping when the computer was idle- and the three most recent BSODs this evening were also when the comp was idle. And no, I don't overclock! After half an hour of Far Cry 4 max temp reached is 67C. (83 on graphics card though... but again, BSODs have all been when idle).

No more BSODs since switching the RAM...my fingers are crossed....

 

[Gator]

Interesting stuff! Thanks for replying!

Anyway- I think it's unlikely to be a CPU issue since this originally arose only after the computer sleeping when the computer was idle- and the three most recent BSODs this evening were also when the comp was idle. And no, I don't overclock! After half an hour of Far Cry 4 max temp reached is 67C. (83 on graphics card though... but again, BSODs have all been when idle).

No more BSODs since switching the RAM...my fingers are crossed....

Alright good to know, let us know how it works out. The dumps you provided don't point to any specific cause other than hardware and some processor errors. This doesn't always mean the CPU is at fault, but its always a possibility. If you continue to have problems, I'll go ahead and get some other more knowledgeable BSOD analysts to look at it.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80094ab028, bf800000, 200401}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

3: kd> !thread
GetPointerFromAddress: unable to read from fffff80003312000
THREAD fffffa800d7a3b50  Cid 0744.1830  Teb: 000000007ef89000 Win32Thread: fffff900c1b88ab0 RUNNING on processor 3
Not impersonating
GetUlongFromAddress: unable to read from fffff80003251ba8
Owning Process            fffffa800b000b30       Image:         <Unknown>
Attached Process          fffffa800a0a55c0       Image:         [COLOR="Red"][B]ubssrv_oc_only[/B][/COLOR]
fffff78000000000: Unable to get shared data
Wait Start TickCount      620774       
Context Switch Count      1516           IdealProcessor: 0                 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00000000557fddfb
Stack Init fffff880095dec70 Current fffff880095dd880
Base fffff880095df000 Limit fffff880095d7000 Call 0

This seems to be another case of shit software supplied by Gigabyte - there has been a slew of these causing 0x124 BSOD's over the last month or two.

ubssrv_oc_only.exe is the Gigabyte CloudStation RemoteOC application

The solution is to uninstall all Gigabyte utility software, after resetting any auto-overclocks if you enabled them. Reboot and you should be BSOD free.

 

[mcplums]

Thanks for your input buddy. The thing is that since I switched out the RAM and double checked cables, I havn't had a BSOD. If it returns I will certainly try your suggestion.

Could you please help me decode the bug report? Is it stating that the cause of the BSOD was that something couldnt be read from the RAM- while it was working on the ubssrv_oc_only process? Is that what it means?

Thanks!

 

[Golden]

No, it means that one or more of the Gigabyte applications are interfering with the way that RAM is being addressed and written from/to.

The only solution is to uninstall all Gigabyte applications.

 

[mcplums]

Ok will do.

I actually just had another BSOD so clearly my previous fix wasn't the solution. It seems to almost exclusively happen when I'm away from my computer- like Gigabyte launches something during idle time that is causing the issue. Anyway I will uninstall all of it- there are about ten gigabyte apps.

I know this is off topic, but any chance you know why Windows can't prevent a BSOD caused by a program? It seems to me like this should never happen?

 

[Golden]

I know this is off topic, but any chance you know why Windows can't prevent a BSOD caused by a program? It seems to me like this should never happen?

Most BSOD's are caused by 3rd party drivers clashing with the Windows system drivers - Windows cannot prevent that from happening.

 

[mcplums]

Btw your solution of getting rid of all gigabyte apps has completely solved the problem. Thanks very much!

 

[Golden]