Goedemorgen Helpmij,
Sinds een tijdje is het dat ik tijdens een graphic intense spelletje het probleem heb dat hij vast slaat, mijn beeldscherm gaat dan naar verschillende kanalen zoeken Digitaal/hdmi/analoog maar hij vind geen beeld ( dit terwijl mijn computer door draait)
De computer staat wel compleet vast.
Als ik hem hardnekkig afsluit en weer herstart krijg ik de melding: Windows is onverwachts afgesloten en vervolgens hersteld.
hieronder heb ik alle informatie geplaatst.
---------------------
Probleemhandtekening:
Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.1.7601.2.1.0.768.3
Landinstelling-id: 1043
Aanvullende informatie over dit probleem:
BCCode: 116
BCP1: FFFFFA80047934E0
BCP2: FFFFF8800F85B970
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\052111-15756-01.dmp
C:\Users\Eigenaar\AppData\Local\Temp\WER-27861-0.sysdata.xml
Lees de onlineprivacyverklaring:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0413
Als de onlineprivacyverklaring niet beschikbaar is, lees dan onze offlineprivacyverklaring:
C:\Windows\system32\nl-NL\erofflps.txt
Nadat ik de dump file geopent heb krijg ik het volgende.:
-----------------------------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\052111-15756-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Invalid directory table base value 0x0
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e08000 PsLoadedModuleList = 0xfffff800`0304de90
Debug session time: Sat May 21 01:11:01.965 2011 (UTC + 2:00)
System Uptime: 0 days 0:20:03.043
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80047934e0, fffff8800f85b970, ffffffffc000009a, 4}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80047934e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f85b970, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
FAULTING_IP:
+3164623132633437
fffff880`0f85b970 ?? ???
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
CURRENT_IRQL: 0
STACK_TEXT:
fffff800`00b9cb80 fffffa80`04b58c40 : ffffffff`ffffffff 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffff880`0fd783c2
fffff800`00b9cb88 ffffffff`ffffffff : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`014f6440 : 0xfffffa80`04b58c40
fffff800`00b9cb90 00000000`00000002 : 00000000`00000000 00000000`00000000 fffff880`014f6440 fffffa80`0598f1a0 : 0xffffffff`ffffffff
fffff800`00b9cb98 00000000`00000000 : 00000000`00000000 fffff880`014f6440 fffffa80`0598f1a0 00000000`00000000 : 0x2
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
---------
Sinds een tijdje is het dat ik tijdens een graphic intense spelletje het probleem heb dat hij vast slaat, mijn beeldscherm gaat dan naar verschillende kanalen zoeken Digitaal/hdmi/analoog maar hij vind geen beeld ( dit terwijl mijn computer door draait)
De computer staat wel compleet vast.
Als ik hem hardnekkig afsluit en weer herstart krijg ik de melding: Windows is onverwachts afgesloten en vervolgens hersteld.
hieronder heb ik alle informatie geplaatst.
---------------------
Probleemhandtekening:
Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.1.7601.2.1.0.768.3
Landinstelling-id: 1043
Aanvullende informatie over dit probleem:
BCCode: 116
BCP1: FFFFFA80047934E0
BCP2: FFFFF8800F85B970
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\052111-15756-01.dmp
C:\Users\Eigenaar\AppData\Local\Temp\WER-27861-0.sysdata.xml
Lees de onlineprivacyverklaring:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0413
Als de onlineprivacyverklaring niet beschikbaar is, lees dan onze offlineprivacyverklaring:
C:\Windows\system32\nl-NL\erofflps.txt
Nadat ik de dump file geopent heb krijg ik het volgende.:
-----------------------------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\052111-15756-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Invalid directory table base value 0x0
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e08000 PsLoadedModuleList = 0xfffff800`0304de90
Debug session time: Sat May 21 01:11:01.965 2011 (UTC + 2:00)
System Uptime: 0 days 0:20:03.043
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80047934e0, fffff8800f85b970, ffffffffc000009a, 4}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80047934e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f85b970, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
FAULTING_IP:
+3164623132633437
fffff880`0f85b970 ?? ???
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
CURRENT_IRQL: 0
STACK_TEXT:
fffff800`00b9cb80 fffffa80`04b58c40 : ffffffff`ffffffff 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffff880`0fd783c2
fffff800`00b9cb88 ffffffff`ffffffff : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`014f6440 : 0xfffffa80`04b58c40
fffff800`00b9cb90 00000000`00000002 : 00000000`00000000 00000000`00000000 fffff880`014f6440 fffffa80`0598f1a0 : 0xffffffff`ffffffff
fffff800`00b9cb98 00000000`00000000 : 00000000`00000000 fffff880`014f6440 fffffa80`0598f1a0 00000000`00000000 : 0x2
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
---------