[SOLVED] 0x116/7's, possible root cause for some of them?

satrow · May 19, 2012

Not the best area to post this in but I'm unsure as to its' veracity: (no source/verification linked): http://www.techsupportforum.com/for...r-on-for-long-periods-642862.html#post3739196

... is an architectural flaw in the Intel processors that spans multiple generations (core 2 duos - LGA 2011, includes mobile processor line also). The error occurs during intense gaming scenarios and/or high resolution graphics settings.
...
when the error is encountered, the video card and processor attains physical damage. In addition, a damaged video card and processor can and will cause additional damage to other hardware components (motherboard, memory, and even power supplies). If any of these components are transferred to another or new system, the new system may become damaged during intense graphical applications.
...

Wrench97 · May 19, 2012

That's news to me, I would think if true it would have been all over the tech sites.
If a known issue is out and around enough for a 3rd party to come up with a software fix I'm sure we would have heard of it, more likely AMD fan boy's spreading more Anti Intel garbage.

Wrench97 · May 19, 2012

Came from the Nvidia forums Post #47 by The Hun a 3 post member since 2007 > http://forums.nvidia.com/index.php?showtopic=224325&view=findpost&p=1405497

GZ · May 19, 2012

That means it is a reliable source, right? :hysterical:

Wrench97 · May 20, 2012

Absolutely won't believe anyone else:thud:

jcgriff2 · May 21, 2012

.....when the error is encountered, the video card and processor attains physical damage.

I've had a few 0x116 BSODs & several 0x117 Live Kernel Events; updating my NVIDIA 9600M GT driver solved it each time.

To see if you've had any 0x117 Live Kernel Events, check for the existance of "watchdog" dumps -

C:\Windows\LiveKernelReports\WATCHDOG

Mine - W7 x64 installed June 2010 - last 0x117 was 6 months ago -

Code:

WD-20110628-1556.dmp	558056	6/28/2011	15:56:26	A	WD-201~1.DMP
WD-20110629-2342.dmp	596395	6/29/2011	23:42:56	A	WD-201~2.DMP
WD-20111016-2028.dmp	502017	10/16/2011	20:28:26	A	WD-201~3.DMP
WD-20111028-2303.dmp	709189	10/28/2011	23:03:44	A	WD-201~4.DMP
WD-20111106-1051.dmp	557321	11/6/2011	11:51:45	A	WD9815~1.DMP
WD-20111113-1122.dmp	562416	11/13/2011	12:22:30	A	WD2E35~1.DMP

zigzag3143 · May 21, 2012

Happens in win 8 as well. Mine started with an Nvidia update in march. Alternate 117s, and 141's.

usasma · May 22, 2012

@ Ken - can you upload one of the STOP 0x141's please? I need it's output for my BSOD Index page.
Thanks!

Search

Search

[SOLVED] 0x116/7's, possible root cause for some of them?

satrow

Moderator, BSOD Kernel Dump Senior Analyst

Wrench97

Administrator, Hardware Expert

Wrench97

Administrator, Hardware Expert

GZ

Visiting Expert

Wrench97

Administrator, Hardware Expert

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

zigzag3143

Contributor, Sysnative Staff Emeritus

usasma

Retired Admin

[SOLVED] 0x116/7's, possible root cause for some of them?

Moderator, BSOD Kernel Dump Senior Analyst

Administrator, Hardware Expert

Administrator, Hardware Expert

Visiting Expert

Administrator, Hardware Expert

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Contributor, Sysnative Staff Emeritus

Retired Admin

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)