Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD playing videos/games (dota)..


28 Dec 2011   #1

Windows 7 Home Premium 64bit
 
 
BSOD playing videos/games (dota)..

Acer Aspire 4741G
Intel Core - I3-370M processor
Nvidia GeForce GT 415M (Up to 1754 Mb)
2Gb DDR3 Memory
OEM Windows 7 Home Premium 64b

My laptop suddenly had this issue whenever im playing game (dota) or i play any videos.. i recently reformatted my unit thinking it will solved the problem but it doesnt and still have the same problem till now.. it shows in the BSOD that it has hardware error.. pls ur help is so much appreciated!

My System SpecsSystem Spec
.

28 Dec 2011   #2

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sinzster\Windows_NT6_BSOD_jcgriff2\112711-13868-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`0305f000 PsLoadedModuleList = 0xfffff800`0329ce50 Debug session time: Sat Nov 26 19:29:36.337 2011 (UTC - 7:00) System Uptime: 0 days 0:16:52.929 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8002bec028, be000000, 800400} Unable to load image \SystemRoot\system32\DRIVERS\HECIx64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for HECIx64.sys *** ERROR: Module load completed but symbols could not be loaded for HECIx64.sys Probably caused by : hardware Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * 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: fffffa8002bec028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f STACK_TEXT: fffff880`0316ba58 fffff800`03028903 : 00000000`00000124 00000000`00000000 fffffa80`02bec028 00000000`be000000 : nt!KeBugCheckEx fffff880`0316ba60 fffff800`031e54d3 : 00000000`00000001 fffffa80`02bedea0 00000000`00000000 fffffa80`02bedef0 : hal!HalBugCheckSystem+0x1e3 fffff880`0316baa0 fffff800`030285c8 : 00000000`00000728 fffffa80`02bedea0 fffff880`0316be30 fffff880`0316be00 : nt!WheaReportHwError+0x263 fffff880`0316bb00 fffff800`03027f1a : fffffa80`02bedea0 fffff880`0316be30 fffffa80`02bedea0 00000000`00000000 : hal!HalpMcaReportError+0x4c fffff880`0316bc50 fffff800`03027dd5 : 00000000`00000004 00000000`00000001 fffff880`0316beb0 00000000`00000000 : hal!HalpMceHandler+0x9e fffff880`0316bc90 fffff800`0301be88 : fffffa80`027a4cc8 fffffa80`027a4cc0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55 fffff880`0316bcc0 fffff800`030cdeac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff880`0316bcf0 fffff800`030cdd13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff880`0316be30 fffff880`045b8024 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 fffff880`0318bb70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : HECIx64+0x1024 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sinzster\Windows_NT6_BSOD_jcgriff2\112711-14898-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`03015000 PsLoadedModuleList = 0xfffff800`03252e50 Debug session time: Sat Nov 26 19:39:11.146 2011 (UTC - 7:00) System Uptime: 0 days 0:08:23.738 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8002bfb028, be000000, 800400} Probably caused by : hardware Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * 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: fffffa8002bfb028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f STACK_TEXT: fffff800`00ba8a98 fffff800`03603903 : 00000000`00000124 00000000`00000000 fffffa80`02bfb028 00000000`be000000 : nt!KeBugCheckEx fffff800`00ba8aa0 fffff800`0319b4d3 : 00000000`00000001 fffffa80`027f99a0 00000000`00000000 fffffa80`027f99f0 : hal!HalBugCheckSystem+0x1e3 fffff800`00ba8ae0 fffff800`036035c8 : 00000000`00000728 fffffa80`027f99a0 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263 fffff800`00ba8b40 fffff800`03602f1a : fffffa80`027f99a0 fffff800`00ba8e70 fffffa80`027f99a0 00000000`00000000 : hal!HalpMcaReportError+0x4c fffff800`00ba8c90 fffff800`03602dd5 : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e fffff800`00ba8cd0 fffff800`035f6e88 : fffff800`031ffe80 fffffa80`02613a80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55 fffff800`00ba8d00 fffff800`03083eac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff800`00ba8d30 fffff800`03083d13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff800`00ba8e70 fffff880`0478b96a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 fffff800`00b9cb68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : HDAudBus!READ_REGISTER_ULONG+0xa STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sinzster\Windows_NT6_BSOD_jcgriff2\112911-15834-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`03007000 PsLoadedModuleList = 0xfffff800`03244e70 Debug session time: Mon Nov 28 20:58:17.875 2011 (UTC - 7:00) System Uptime: 0 days 1:32:09.077 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffff88002670000, 2, 1, fffff880058e94af} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** 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+e34af ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: fffff88002670000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff880058e94af, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032af0e0 fffff88002670000 CURRENT_IRQL: 2 FAULTING_IP: nvlddmkm+e34af fffff880`058e94af 42895c9004 mov dword ptr [rax+r10*4+4],ebx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff8800356a1a0 -- (.trap 0xfffff8800356a1a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8800266fffc rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880058e94af rsp=fffff8800356a338 rbp=0000000f70000000 r8=fffffa8001f14188 r9=0000000000000000 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nvlddmkm+0xe34af: fffff880`058e94af 42895c9004 mov dword ptr [rax+r10*4+4],ebx ds:0008:fffff880`02670000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80003076b29 to fffff800030775c0 STACK_TEXT: fffff880`0356a058 fffff800`03076b29 : 00000000`0000000a fffff880`02670000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0356a060 fffff800`030757a0 : 00000000`0010a48c 00000000`00000000 00000000`00000001 fffff880`059f3557 : nt!KiBugCheckDispatch+0x69 fffff880`0356a1a0 fffff880`058e94af : fffff880`05856517 00000000`00000000 0000000f`70002b88 fffffa80`01f14188 : nt!KiPageFault+0x260 fffff880`0356a338 fffff880`05856517 : 00000000`00000000 0000000f`70002b88 fffffa80`01f14188 00000000`00004000 : nvlddmkm+0xe34af fffff880`0356a340 00000000`00000000 : 0000000f`70002b88 fffffa80`01f14188 00000000`00004000 fffff880`00000050 : nvlddmkm+0x50517 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+e34af fffff880`058e94af 42895c9004 mov dword ptr [rax+r10*4+4],ebx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nvlddmkm+e34af FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c54286c FAILURE_BUCKET_ID: X64_0xD1_nvlddmkm+e34af BUCKET_ID: X64_0xD1_nvlddmkm+e34af Followup: MachineOwner ---------
  4. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sinzster\Windows_NT6_BSOD_jcgriff2\120411-21340-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03262000 PsLoadedModuleList = 0xfffff800`034a7670 Debug session time: Sat Dec 3 19:05:33.329 2011 (UTC - 7:00) System Uptime: 0 days 0:04:23.921 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9C, {0, fffff80000ba8bb0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MACHINE_CHECK_EXCEPTION (9c) A fatal Machine Check Exception has occurred. KeBugCheckEx parameters; x86 Processors If the processor has ONLY MCE feature available (For example Intel Pentium), the parameters are: 1 - Low 32 bits of P5_MC_TYPE MSR 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of P5_MC_ADDR MSR 4 - Low 32 bits of P5_MC_ADDR MSR If the processor also has MCA feature available (For example Intel Pentium Pro), the parameters are: 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error IA64 Processors 1 - Bugcheck Type 1 - MCA_ASSERT 2 - MCA_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing MCA. 3 - MCA_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA. 4 - MCA_FATAL FW reported a fatal MCA. 5 - MCA_NONFATAL SAL reported a recoverable MCA and we don't support currently support recovery or SAL generated an MCA and then couldn't produce an error record. 0xB - INIT_ASSERT 0xC - INIT_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing INIT event. 0xD - INIT_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event. 0xE - INIT_FATAL Not used. 2 - Address of log 3 - Size of log 4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO AMD64 Processors 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error Arguments: Arg1: 0000000000000000 Arg2: fffff80000ba8bb0 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x9C_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: wmplayer.exe CURRENT_IRQL: f LAST_CONTROL_TRANSFER: from fffff8000322b818 to fffff800032dec40 STACK_TEXT: fffff800`00ba8b78 fffff800`0322b818 : 00000000`0000009c 00000000`00000000 fffff800`00ba8bb0 00000000`00000000 : nt!KeBugCheckEx fffff800`00ba8b80 fffff800`0322af57 : 00000000`00000004 00000000`00000000 00000000`00000004 00000000`00000000 : hal!HalpMcaReportError+0x164 fffff800`00ba8cd0 fffff800`0321ee88 : 00000000`00000000 fffff800`03249500 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f fffff800`00ba8d00 fffff800`032dd52c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff800`00ba8d30 fffff800`032dd393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff800`00ba8e70 fffff800`032238ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 fffff880`088bc6d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHpetRolloverInterrupt+0x26 STACK_COMMAND: kb FOLLOWUP_IP: nt!KxMcheckAbort+6c fffff800`032dd52c 488d8c2400010000 lea rcx,[rsp+100h] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!KxMcheckAbort+6c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c Followup: MachineOwner ---------
  5. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\sinzster\Windows_NT6_BSOD_jcgriff2\120811-15038-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03204000 PsLoadedModuleList = 0xfffff800`03449670 Debug session time: Wed Dec 7 13:24:01.600 2011 (UTC - 7:00) System Uptime: 0 days 0:26:31.192 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 117, {fffffa8001bfd4e0, fffff88005932d20, 0, 0} Unable to load image nvlddmkm.sys, Win32 error 0n2 *** 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+11ad20 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_TIMEOUT_DETECTED (117) The display driver failed to respond in timely fashion. (This code can never be used for real bugcheck). Arguments: Arg1: fffffa8001bfd4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88005932d20, The pointer into responsible device driver module (e.g owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: 0000000000000000, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+11ad20 fffff880`05932d20 ?? ??? DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x117 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`022ec630 fffff880`040f45f7 : fffffa80`01bfd4e0 fffff880`04140e93 fffffa80`01bfd4e0 fffff880`040c2843 : watchdog!WdDbgReportRecreate+0xa3 fffff880`022ecb50 fffff880`040f52bc : fffff8a0`0a914430 fffff8a0`0a914430 00000000`00000080 fffffa80`01bfd4e0 : dxgkrnl!TdrUpdateDbgReport+0xcb fffff880`022ecba0 fffff880`040c96b3 : 00000000`00000001 fffffa80`05b06000 00000000`00000000 00000000`0000006b : dxgkrnl!TdrCollectDbgInfoStage2+0x220 fffff880`022ecbd0 fffff880`040f5e0f : fffffa80`019f8820 ffffffff`fffe7960 fffffa80`01bfd4e0 fffff880`041c61de : dxgkrnl!DXGADAPTER::Reset+0xef fffff880`022ecc80 fffff880`041c4ec1 : fffffa80`01e26010 00000000`00000080 00000000`00000000 fffffa80`05a7b010 : dxgkrnl!TdrResetFromTimeout+0x23 fffff880`022ecd00 fffff800`0351bfee : 00000000`01adb544 fffffa80`05b14060 fffffa80`017d1890 fffffa80`05b14060 : dxgmms1!VidSchiWorkerThread+0x101 fffff880`022ecd40 fffff800`032725e6 : fffff880`031d3180 fffffa80`05b14060 fffff880`031ddfc0 00640043`ffffffc8 : nt!PspSystemThreadStartup+0x5a fffff880`022ecd80 00000000`00000000 : fffff880`022ed000 fffff880`022e7000 fffff880`022ec110 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+11ad20 fffff880`05932d20 ?? ??? SYMBOL_NAME: nvlddmkm+11ad20 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c54286c FAILURE_BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------
Two hardware blue screen errors, an unknown blue screen error (probably related to the hardware), and two related to your nVidia driver.

You get hardware blue screens. See Stop 0x124 - what it means and what to try.

The following drivers should be updated via (Driver Reference) if possible:
Code:
NTIDrvr	fffff880`04c60000	fffff880`04c68000	Tue Mar 24 21:09:39 2009 (49c9a073)	0000e15e		NTIDrvr.sys
UBHelper	fffff880`04c58000	fffff880`04c60000	Mon Apr 27 02:48:19 2009 (49f57153)	0000589c		UBHelper.sys
If the hardware link I gave does not point you in the right direction for fixing the problems, let me know, and we will proceed with the above information.
My System SpecsSystem Spec
Reply

 BSOD playing videos/games (dota)..




Thread Tools



Similar help and support threads for2: BSOD playing videos/games (dota)..
Thread Forum
BSOD playing games (DOTA 2/LoL/Saints Row IV) (Using OBS) BSOD Help and Support
Random freeze while playing DOTA 2, watching youtube videos (Error 41) BSOD Help and Support
BSOD while playing videos and games. BSOD Help and Support
Solved BSOD while playing Dota, TF2 and other games BSOD Help and Support
Solved BSOD playing DOTA or any other online games. BSOD Help and Support
BSOD Watching youtube videos and playing dota 2 BSOD Help and Support
BSOD whenever playing games or videos BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:51 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33