Ich habe seit einiger Zeit in Windows (in Linux nicht, aber das benutzt ich auch nicht so lange) Bluescreens.
Mein Laptop stockt nach dem Login, will kein WLAN finden und gibt einen Bluescreen nach 1 Minute aus.
Seit neustem stürtzt er ohne Fehlermeldung auch einfach mal ab.
In meiner Dropbox habe ich eine ZIP mit all meinen Dumps hochgeladen, da ich sonst jede einzelne Datei in den Anhang laden müsste. Hier mal die WinDBG Analyse von einem Dump, vlt hilft das weiter. Ich selber habe aber sehr wenig Ahnung davon und hoffe, dass ihr mir helfen könnt.
Vielen Dank
Microsoft ® Windows Debugger Version 6.11.0001.404 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\101512-26816-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Inaccessible path: '"' Symbol search path is: "srv*c:\cache*http://msdl.microsoft.com/download/symbols;" Executable search path is: Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17944.x86fre.win7sp1_gdr.120830-0333 Machine Name: Kernel base = 0x8324f000 PsLoadedModuleList = 0x833994d0 Debug session time: Mon Oct 15 09:52:30.436 2012 (GMT+2) System Uptime: 0 days 0:03:05.184 Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list ..... 0: kd> ! analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INVALID_EXTENDED_PROCESSOR_STATE (131) Invalid combination of parameters was detected while saving or restoring extended processor state. Arguments: Arg1: 00000003, The previously saved state is for a different thread. Arg2: ce3b7d48, The saved thread. Arg3: cdd57d48, The current thread. Arg4: 00000000 Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for igdkmd32.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: 8324f000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e973580 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x131 CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 832d9a6c to 8332de98 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. b826b06c 832d9a6c 00000131 00000003 ce3b7d48 nt+0xdee98 b826b0a4 832d9db6 897ecb54 b826b0c4 92c7390b nt+0x8aa6c b826b0b0 92c7390b 897ecb54 c000000d 00000000 nt+0x8adb6 b826b0c4 92e81db7 887d4000 897ecb54 b826b0f4 igdkmd32+0x4d90b b826b0d4 92e85f38 887d4000 00000000 000000f1 igdkmd32+0x25bdb7 b826b0f4 92e86470 027f4000 b826b6c4 00000e7f igdkmd32+0x25ff38 b826b178 92e86730 017d4000 b826b6c4 00000000 igdkmd32+0x260470 b826b1a0 92e868de 887d4000 b826b6c4 b826b6a8 igdkmd32+0x260730 b826b60c 92c5dc31 887d4000 b826b6c4 8321d6ee igdkmd32+0x2608de b826b6b0 92c5dd8c 887d4000 b826b6c4 00000000 igdkmd32+0x37c31 b826b734 92c75a8d 887d4000 b826b750 00000001 igdkmd32+0x37d8c b826b760 92c2d985 887d4000 895d6410 b826b777 igdkmd32+0x4fa8d b826b78c 9358426c 887d4000 b826b7cc b826b7d4 igdkmd32+0x7985 b826b7b4 93583a0c 0026b7cc 917d91b0 917d907e dxgkrnl+0x3e26c b826b7dc 93583b6a dceabc08 b826b80b 917d91b0 dxgkrnl+0x3da0c b826b800 935846b1 00eabc08 00000005 00000001 dxgkrnl+0x3db6a b826b844 9357c7bc db95d1d8 00000001 917d91b0 dxgkrnl+0x3e6b1 b826b878 9357c197 9184e798 dceabc08 00000000 dxgkrnl+0x367bc b826b8b4 9357c472 9184e798 dceabc08 00000000 dxgkrnl+0x36197 b826b8e4 9357bd57 00000000 dceabc08 00000000 dxgkrnl+0x36472 b826b918 9357bb14 00000003 00000003 fd8c1bc0 dxgkrnl+0x35d57 b826b954 9357d306 fd8c1bc0 88658000 00000001 dxgkrnl+0x35b14 b826b990 93581c7b fd8c1bc0 0000cf79 00000000 dxgkrnl+0x37306 b826b9c0 93583e1c 00028000 917d907e b826bab8 dxgkrnl+0x3bc7b b826ba08 95fc71e4 00028000 fd8c1bc0 917d907e dxgkrnl+0x3de1c b826ba28 95fb92b2 00000001 0002900f 00000000 win32k+0x371e4 b826bb14 9609f82d 00000000 ffb8a008 00000000 win32k+0x292b2 b826bb70 9609f96c 00000000 00000000 89883958 win32k+0x10f82d b826bbe0 9608107c 00000000 00000000 89883958 win32k+0x10f96c b826bd04 95fadf9d 8da2fd08 00000004 8da2fd08 win32k+0xf107c b826bd18 96064640 00000004 0299fccc b826bd34 win32k+0x1df9d b826bd28 8328c8fa 00000004 0299fd0c 77757094 win32k+0xd4640 b826bd34 77757094 badb0d00 0299fcc8 00000000 nt+0x3d8fa b826bd38 badb0d00 0299fcc8 00000000 00000000 0x77757094 b826bd3c 0299fcc8 00000000 00000000 00000000 0xbadb0d00 b826bd40 00000000 00000000 00000000 00000000 0x299fcc8 STACK_COMMAND: kb FOLLOWUP_IP: igdkmd32+4d90b 92c7390b ? ? SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: igdkmd32+4d90b FOLLOWUP_NAME: MachineOwner MODULE_NAME: igdkmd32 IMAGE_NAME: igdkmd32.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------
Dieser Beitrag wurde von Wiesel bearbeitet: 10. November 2012 - 20:37
Änderungsgrund: code - boxed