¿Why my Windows 7 Pro have Kernel-Power error 41?

Question

Hello, good morning, I installed Windows 7 Professional Edition and each time freezes and restarts, I open the event viewer and I see several critical events would like to see if someone can help me. They say "Event 41, Kernel-Power", I occasionally
happen ... especially when browsing internet through a USB modem ZTE MF-193, but I have also occurred trying to play games like Half Life 1 or Warcraft 3. 
My pc specs are as follows. According to the Direct X diagnostics are: 
Time of this report: 4/5/2014, 07:24:38
       Machine name: FAMILY-PC
   Operating System: Windows 7 Professional 64-bit (6.1, Build 7600) (7600.win7_rtm.090713-1255)
           Language: Spanish (Regional Setting: Spanish)
System Manufacturer: Intel
       System Model: DG41WV
               BIOS: BIOS Date: 01/07/09 15:28:41 Ver: 08.00.10
          Processor: Pentium(R) Dual-Core  CPU      E5700  @ 3.00GHz (2 CPUs), ~3.0GHz
             Memory: 2048MB RAM
Available OS Memory: 1980MB RAM
          Page File: 1317MB used, 2643MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7600.16385 32bit Unicode
System events in XML view say: 
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> 
  <EventID>41</EventID> 
  <Version>2</Version> 
  <Level>1</Level> 
  <Task>63</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000002</Keywords> 
  <TimeCreated SystemTime="2014-04-05T11:11:43.116009800Z" /> 
  <EventRecordID>16184</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="4" ThreadID="8" /> 
  <Channel>System</Channel> 
  <Computer>Familia-PC</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <EventData>
  <Data Name="BugcheckCode">278</Data> 
  <Data Name="BugcheckParameter1">0xfffffa8001e65010</Data> 
  <Data Name="BugcheckParameter2">0xfffff88007225cb0</Data> 
  <Data Name="BugcheckParameter3">0x0</Data> 
  <Data Name="BugcheckParameter4">0xc</Data> 
  <Data Name="SleepInProgress">false</Data> 
  <Data Name="PowerButtonTimestamp">0</Data> 
  </EventData>
  </Event>
another says:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> 
  <EventID>41</EventID> 
  <Version>2</Version> 
  <Level>1</Level> 
  <Task>63</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000002</Keywords> 
  <TimeCreated SystemTime="2014-03-27T10:45:49.941213100Z" /> 
  <EventRecordID>9491</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="4" ThreadID="8" /> 
  <Channel>System</Channel> 
  <Computer>Familia-PC</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <EventData>
  <Data Name="BugcheckCode">59</Data> 
  <Data Name="BugcheckParameter1">0xc0000005</Data> 
  <Data Name="BugcheckParameter2">0xfffff96000686d15</Data> 
  <Data Name="BugcheckParameter3">0xfffff88002a200d0</Data> 
  <Data Name="BugcheckParameter4">0x0</Data> 
  <Data Name="SleepInProgress">false</Data> 
  <Data Name="PowerButtonTimestamp">0</Data> 
  </EventData>
  </Event>
And the latest says: 
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> 
  <EventID>41</EventID> 
  <Version>2</Version> 
  <Level>1</Level> 
  <Task>63</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000002</Keywords> 
  <TimeCreated SystemTime="2014-04-03T15:16:12.334410200Z" /> 
  <EventRecordID>14621</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="4" ThreadID="8" /> 
  <Channel>System</Channel> 
  <Computer>Familia-PC</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <EventData>
  <Data Name="BugcheckCode">0</Data> 
  <Data Name="BugcheckParameter1">0x0</Data> 
  <Data Name="BugcheckParameter2">0x0</Data> 
  <Data Name="BugcheckParameter3">0x0</Data> 
  <Data Name="BugcheckParameter4">0x0</Data> 
  <Data Name="SleepInProgress">false</Data> 
  <Data Name="PowerButtonTimestamp">0</Data> 
  </EventData>
  </Event>
I sincerely appreciate your support, I really like windows 7 but Windows XP I never thought such failures in the last hour I had 2 of them in the last 24 hours I've had 4 and in the last 7 days I've had 25. 
It is a very distressing situation.

Answer 1

YM
These were called BCC116 and are related to a video timeout/failure
"It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".
Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.
As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
The first step is to install the newest video driver.
If playing with video driver versions hasn't helped, make sure the box is not overheating.
 Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
 Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.
If so, it might be as simple as dust buildup and subsequently inadequate cooling.
I would download cpu-z and gpu-z (both free) and keep an eye on the video temps
For more information please read this blog  http://captaindbg.com/bug-check-0x116-video_tdr_error-troubleshooting-tips/
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263%28v=vs.85%29.aspx
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\040514-15771-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c90e50
Debug session time: Sat Apr 5 07:08:35.611 2014 (UTC - 4:00)
System Uptime: 0 days 0:25:10.484
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8001e65010, fffff88007225cb0, 0, c}
Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+23cb0 )
Followup: MachineOwner
1: kd> !analyze -v
* Bugcheck Analysis *
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8001e65010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007225cb0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000c, Optional internal context dependent data.
Debugging Details:
FAULTING_IP:
igdkmd64+23cb0
fffff880`07225cb0 4889542410 mov qword ptr [rsp+10h],rdx
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: firefox.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
STACK_TEXT:
fffff880`061000f8 fffff880`06d3ccbc : 00000000`00000116 fffffa80`01e65010 fffff880`07225cb0 00000000`00000000 : nt!KeBugCheckEx
fffff880`06100100 fffff880`06d3c938 : fffff880`07225cb0 fffffa80`01e65010 fffffa80`034ebd50 fffffa80`03253010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06100140 fffff880`06c0ff07 : fffffa80`01e65010 00000000`00017a38 fffffa80`034ebd50 fffffa80`03253010 : dxgkrnl!TdrIsRecoveryRequired+0x114
fffff880`06100170 fffff880`06c3dd7e : fffffa80`ffffffff 00000000`000179b8 fffff880`061002c0 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06100250 fffff880`06c23bb1 : fffffa80`034ee000 ffffffff`feced300 00000000`00000000 00000000`00000001 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`06100290 fffff880`06c3091c : 00000000`0000fea9 00000000`00000000 fffff880`06100798 fffffa80`01ef5010 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`06100390 fffff800`02f2fd38 : ffffffff`ffffffff ffffffff`ffffffff 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_MEMORY_SEGMENT::RotateCopyCallback+0xe0
fffff880`06100400 fffff880`06c3594c : 00000000`0f5c0000 fffff880`061006d8 00000000`00000000 fffff8a0`00000002 : nt!MmRotatePhysicalView+0x6e8
fffff880`06100640 fffff880`06c2feb8 : fffffa80`034eec60 00000000`00100000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Rotate+0x148
fffff880`061006d0 fffff880`06c21904 : fffffa80`034fdec0 fffff8a0`03643b00 00000000`00000001 fffff880`06100800 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x6f8
fffff880`06100840 fffff880`06c217e3 : fffffa80`034ee000 fffff880`06c2170a 00000000`00000000 fffffa80`02b253c0 : dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList+0x40
fffff880`06100880 fffff880`06c1e70d : 00000000`0000005a 00000000`00000000 00000000`00000000 fffffa80`00000000 : dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation+0x43
fffff880`061008d0 fffff880`06c3865d : 00000000`00000000 fffff8a0`02dd8510 fffffa80`00000000 fffffa80`02b253c0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xc79
fffff880`06100aa0 fffff880`06c38398 : fffff800`0401c080 fffff880`06c37d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`06100c90 fffff880`06c37e96 : 00000000`00000000 fffffa80`019de500 00000000`00000080 fffffa80`03253010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`06100cc0 fffff800`02d68166 : 00000000`01b39914 fffffa80`03252620 fffffa80`017e8840 fffffa80`03252620 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`06100d00 fffff800`02aa3486 : fffff800`02c3de80 fffffa80`03252620 fffff800`02c4bc40 fffff880`01246a90 : nt!PspSystemThreadStartup+0x5a
fffff880`06100d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
igdkmd64+23cb0
fffff880`07225cb0 4889542410 mov qword ptr [rsp+10h],rdx
SYMBOL_NAME: igdkmd64+23cb0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd64
IMAGE_NAME: igdkmd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a01d55b
FAILURE_BUCKET_ID: X64_0x116_IMAGE_igdkmd64.sys
BUCKET_ID: X64_0x116_IMAGE_igdkmd64.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x116_image_igdkmd64.sys
FAILURE_ID_HASH: {88759713-193a-fb8a-dab9-6846ea1a48f2}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag