Solved BSOD with enabled aero. Without aero pc is rock stable.

[hideki2]

Hello. As stated in the title. I can run games for hours newer having an issue, however if I enable aero in windows. And try playing and 3d game I get a black screen and reboot within max 20 minutes. I tried updating graphics drivers, monitoring GPU temperature (its fine) Tried stress testing GPU using Furmark. No problem.

I would be much obliged if anyone could help me to find a solution.

 

[Boozad]

Welcome to 7F. Before we go any further can you click on the Start button and type linpack into the search bar and see what shows in your Start Menu? Post back the results.

 

[hideki2]

That's an intriguing request.
Linpack32
Linpack64
Readme - Intelburntest
Changelog - Intelburntest

I know the latter two ones have nothing to do with anything but you said "Post back the results"

Thanks for reply BTW

 

[Boozad]

Can you fill me in on what Linpack is please? The reason I'm asking is that your dumps are all 0x116 (video timeout detection and recovery) indicating a problem with your GPU, and 0x124 which are virtually always a hardware error that give no clue as to what it actually is, leading me into thinking your GPU was bad. But virtually all of your 124s are showing linpack.exe, I'm getting various results with my Google-Fu and I can't nail down what it is.

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8008433028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  [COLOR=Red][B]linpack64.exe[/B][/COLOR]

 

[hideki2]

Now I see! Linpack is a part of cpu torturing app called "Intelburntest" used for testing stability. Those Bsods were an effect of me optimizing my CPU settings. However its those 0x116 that I would like to get help with.
Everything is good and dandy and doesn't matter how much meat I throw at the GPU unless I enable Aero.

 

[Boozad]

OK so the 0x124s can be ignored. Good for me to learn about that IntelBurn Test anyway.

As for the 0x116s, have they only started recently after updating your nVidia driver by any chance?

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800a86f4e0, fffff880064732dc, ffffffffc000009a, 4}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+79c2dc )

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

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05cd7000 fffff880`066e2000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR=Red][B]Fri Mar 13 15:39:56 2015[/B][/COLOR] (550304CC)
    CheckSum:         009CE879
    ImageSize:        00A0B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[hideki2]

Glad to hear that I could show something new to a BSOD Jedi. About the drivers Its hard to say as this is a relatively fresh system. I never encountered that issue before, but after noticing it yesterday I updated to the newest driver without any positive effect.

 

[Boozad]

More of a Padawan than a Jedi!

Given that you've tried two of the most recent drivers already can you give this a try.

Download this earlier version from here and follow NVIDIA Drivers - Avoid Problems for the cleanest possible install.

 

[hideki2]

Before downgrading drivers I decided to try to replicate issue, however I could not get it to break toady. That's wired because this happened to me many times in a row yesterday. I will see how it goes for the next couple of days, and come back here for your help or to close the thread.

For now thanks for your help.

Stay away from the dark side!

 

[essenbe]

hideki2, can you explain to me exactly what you mean by 'optimizing my CPU settings'? That normally means overclocking. If you are overclocking, please set everything back to defaults. I am not against overclocking, just against it while trying to get a system stable. Even the 116's can be a result of an unstable overclock.

 

[Boozad]

Now there's a Jedi in the room.

 

[hideki2]

I found that a lose power connector was the culprit. Tanks for help! Problem solved!

 

[essenbe]

Great to hear that. I'm glad you found the culprit.