Hilfe
Neues Thema
Antworten
Hatte eben meinen ersten Bluescreen. Das hatte ich während meiner ganzen Vista Zeit nicht - aber egal.
Wie komme ich dahin, wo er mir nach dem Neustart gesagt hat, was genau passiert ist und das der Fehler gesendet wird?
Der Zuverlässigkeitsverlauf hängt ja immer einen Tag hinten dran...
Bluescreen
Nach oben
#2 _fjordblauer_
geschrieben 24. Oktober 2009 - 00:44
Ok, nun stehts auch im Wartungscenter:
Der Computer wurde nach einem schwerwiegenden Fehler neu gestartet. Der Fehlercode war: 0x0000001a (0x00041284, 0x01e1e001, 0x00000000, 0xc0402000). Ein volles Abbild wurde gespeichert in: C:\Windows\MEMORY.DMP. Berichts-ID: xx-yy-xx.
Weiß einer was das für ein Fehler war/ist?
Der Computer wurde nach einem schwerwiegenden Fehler neu gestartet. Der Fehlercode war: 0x0000001a (0x00041284, 0x01e1e001, 0x00000000, 0xc0402000). Ein volles Abbild wurde gespeichert in: C:\Windows\MEMORY.DMP. Berichts-ID: xx-yy-xx.
Weiß einer was das für ein Fehler war/ist?
#3
Hotbitchick 
geschrieben 24. Oktober 2009 - 01:11
Sys:
vmware: Madbox 10.04.01-i386
²PC -> Madbox 9.10:
[Ubuntu Karmic 9.10; Kernel : 2.6.31-16; Desktop Environment : Xfce 4.6.1; Display Manager : SLiM 1.3]
vmware: Madbox 10.04.01-i386
²PC -> Madbox 9.10:
[Ubuntu Karmic 9.10; Kernel : 2.6.31-16; Desktop Environment : Xfce 4.6.1; Display Manager : SLiM 1.3]
#4 _fjordblauer_
geschrieben 28. Oktober 2009 - 19:59
Ok, hier mal die Auswertung. Der obere Teil ist glaube ich ohne diese "Symbol File Path". Also weiter unten gucken, da habe ich das nachgeholt.
CODE
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
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+ *
**************************************************
*******************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c48000 PsLoadedModuleList = 0x82d87570
Debug session time: Fri Oct 23 08:01:34.566 2009 (GMT+1)
System Uptime: 0 days 12:27:43.111
**************************************************
*******************
* 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+ *
**************************************************
*******************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
..................................................
.............
..................................................
..............
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Loading unloaded module list
........
1: kd> !analyze -v
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041284, A PTE or the working set list is corrupt.
Arg2: 01e1e001
Arg3: 00000000
Arg4: c0402000
Debugging Details:
------------------
***** 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 ***
*** ***
**************************************************
***********************
**************************************************
*******************
* 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+ *
**************************************************
*******************
**************************************************
*******************
* 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+ *
**************************************************
*******************
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.
MODULE_NAME: nt
FAULTING_MODULE: 82c48000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbffc
BUGCHECK_STR: 0x1a_41284
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82cc0d85 to 82d19574
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
826d3aa4 82cc0d85 0000001a 00041284 01e1e001 nt!KeBugCheckEx+0x1e
826d3acc 82ccfca9 c0808878 01e1ffff 01e10002 nt!SeComputeAutoInheritByObjectType+0x1093
826d3ba8 82ce3f77 89167030 01e1ffff 89167030 nt!IoRetrievePriorityInfo+0x6b2
826d3c78 82cc1489 89167030 895b78f8 891062c0 nt!KeTryToAcquireGuardedMutex+0x344
826d3ca0 82e7e0e7 891062c0 00000000 ffffffff nt!ExAcquireSharedStarveExclusive+0x38e
826d3d04 82ea0a9f 89167030 01e10000 00000000 nt!MmCreateSection+0x16c6
826d3d24 82c7d79a ffffffff 01e10000 00bbf638 nt!CcCopyRead+0x3ea
826d3d34 76e364f4 badb0d00 00bbf628 00000000 nt!ZwYieldExecution+0xb5a
826d3d38 badb0d00 00bbf628 00000000 00000000 0x76e364f4
826d3d3c 00bbf628 00000000 00000000 00000000 0xbadb0d00
826d3d40 00000000 00000000 00000000 00000000 0xbbf628
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!SeComputeAutoInheritByObjectType+1093
82cc0d85 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!SeComputeAutoInheritByObjectType+1093
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: kd> .reload
Loading Kernel Symbols
..................................................
.............
..................................................
..............
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Loading unloaded module list
........
1: kd> !analyze -v
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041284, A PTE or the working set list is corrupt.
Arg2: 01e1e001
Arg3: 00000000
Arg4: c0402000
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
BUGCHECK_STR: 0x1a_41284
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82cc0d85 to 82d19574
STACK_TEXT:
826d3aa4 82cc0d85 0000001a 00041284 01e1e001 nt!KeBugCheckEx+0x1e
826d3acc 82ccfca9 c0808878 01e1ffff 01e10002 nt!MiLocateWsle+0xc1
826d3ba8 82ce3f77 89167030 01e1ffff 89167030 nt!MiDeleteVirtualAddresses+0x16e
826d3c78 82cc1489 89167030 895b78f8 891062c0 nt!MiRemoveMappedView+0x301
826d3ca0 82e7e0e7 891062c0 00000000 ffffffff nt!MiRemoveVadAndView+0xe5
826d3d04 82ea0a9f 89167030 01e10000 00000000 nt!MiUnmapViewOfSection+0x265
826d3d24 82c7d79a ffffffff 01e10000 00bbf638 nt!NtUnmapViewOfSection+0x55
826d3d24 76e364f4 ffffffff 01e10000 00bbf638 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00bbf638 00000000 00000000 00000000 00000000 0x76e364f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiLocateWsle+c1
82cc0d85 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiLocateWsle+c1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbffc
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+c1
BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+c1
Followup: MachineOwner
---------
1: kd> lmvm nt
start end module name
82c48000 83048000 nt (pdb symbols) c:\windows\symbols\ntkrnlmp.pdb\998A3472EEA6405CB8C089DE868F26222\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Tue Jul 14 01:15:08 2009 (4A5BBFFC)
CheckSum: 003C2F88
ImageSize: 00400000
File version: 6.1.7600.16385
Product version: 6.1.7600.16385
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.1.7600.16385
FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
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+ *
**************************************************
*******************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c48000 PsLoadedModuleList = 0x82d87570
Debug session time: Fri Oct 23 08:01:34.566 2009 (GMT+1)
System Uptime: 0 days 12:27:43.111
**************************************************
*******************
* 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+ *
**************************************************
*******************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
..................................................
.............
..................................................
..............
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Loading unloaded module list
........
1: kd> !analyze -v
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041284, A PTE or the working set list is corrupt.
Arg2: 01e1e001
Arg3: 00000000
Arg4: c0402000
Debugging Details:
------------------
***** 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 ***
*** ***
**************************************************
***********************
**************************************************
*******************
* 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+ *
**************************************************
*******************
**************************************************
*******************
* 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+ *
**************************************************
*******************
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.
MODULE_NAME: nt
FAULTING_MODULE: 82c48000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbffc
BUGCHECK_STR: 0x1a_41284
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82cc0d85 to 82d19574
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
826d3aa4 82cc0d85 0000001a 00041284 01e1e001 nt!KeBugCheckEx+0x1e
826d3acc 82ccfca9 c0808878 01e1ffff 01e10002 nt!SeComputeAutoInheritByObjectType+0x1093
826d3ba8 82ce3f77 89167030 01e1ffff 89167030 nt!IoRetrievePriorityInfo+0x6b2
826d3c78 82cc1489 89167030 895b78f8 891062c0 nt!KeTryToAcquireGuardedMutex+0x344
826d3ca0 82e7e0e7 891062c0 00000000 ffffffff nt!ExAcquireSharedStarveExclusive+0x38e
826d3d04 82ea0a9f 89167030 01e10000 00000000 nt!MmCreateSection+0x16c6
826d3d24 82c7d79a ffffffff 01e10000 00bbf638 nt!CcCopyRead+0x3ea
826d3d34 76e364f4 badb0d00 00bbf628 00000000 nt!ZwYieldExecution+0xb5a
826d3d38 badb0d00 00bbf628 00000000 00000000 0x76e364f4
826d3d3c 00bbf628 00000000 00000000 00000000 0xbadb0d00
826d3d40 00000000 00000000 00000000 00000000 0xbbf628
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!SeComputeAutoInheritByObjectType+1093
82cc0d85 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!SeComputeAutoInheritByObjectType+1093
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: kd> .reload
Loading Kernel Symbols
..................................................
.............
..................................................
..............
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Loading unloaded module list
........
1: kd> !analyze -v
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041284, A PTE or the working set list is corrupt.
Arg2: 01e1e001
Arg3: 00000000
Arg4: c0402000
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
BUGCHECK_STR: 0x1a_41284
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82cc0d85 to 82d19574
STACK_TEXT:
826d3aa4 82cc0d85 0000001a 00041284 01e1e001 nt!KeBugCheckEx+0x1e
826d3acc 82ccfca9 c0808878 01e1ffff 01e10002 nt!MiLocateWsle+0xc1
826d3ba8 82ce3f77 89167030 01e1ffff 89167030 nt!MiDeleteVirtualAddresses+0x16e
826d3c78 82cc1489 89167030 895b78f8 891062c0 nt!MiRemoveMappedView+0x301
826d3ca0 82e7e0e7 891062c0 00000000 ffffffff nt!MiRemoveVadAndView+0xe5
826d3d04 82ea0a9f 89167030 01e10000 00000000 nt!MiUnmapViewOfSection+0x265
826d3d24 82c7d79a ffffffff 01e10000 00bbf638 nt!NtUnmapViewOfSection+0x55
826d3d24 76e364f4 ffffffff 01e10000 00bbf638 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00bbf638 00000000 00000000 00000000 00000000 0x76e364f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiLocateWsle+c1
82cc0d85 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiLocateWsle+c1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbffc
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+c1
BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+c1
Followup: MachineOwner
---------
1: kd> lmvm nt
start end module name
82c48000 83048000 nt (pdb symbols) c:\windows\symbols\ntkrnlmp.pdb\998A3472EEA6405CB8C089DE868F26222\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Tue Jul 14 01:15:08 2009 (4A5BBFFC)
CheckSum: 003C2F88
ImageSize: 00400000
File version: 6.1.7600.16385
Product version: 6.1.7600.16385
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.1.7600.16385
FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
Dieser Beitrag wurde von Urne bearbeitet: 28. Oktober 2009 - 20:32
Änderungsgrund: Urne hat mal geboxt.
#5 _MagicAndre1981_
geschrieben 28. Oktober 2009 - 23:29
tipp bei symbol Pfad mal das hier ein:
srv*C:\symbols*http://msdl.microsoft.com/download/symbols
#6
XyMcCoy
geschrieben 29. Oktober 2009 - 22:38
bei dem fehler liegt scheinbar ein speicherproblem / speicherfehler vor .. speicher testen .. man glaubt gar nicht wieviele bluescreens wegen speicher auftauchen ..
Der Größte Fehler bei Computern sitzt meißtens davor ! :-)
#7 _fjordblauer_
geschrieben 30. Oktober 2009 - 10:50
Wie kommst du auf den Speicher, an welcher Stelle wird das erwähnt? Gibts da ein Win 7 Boardmittel zum testen?
#8 _MagicAndre1981_
geschrieben 30. Oktober 2009 - 10:55
hast du den Pfad eingetragen und die Analyse nochmals gemacht?
#9 _fjordblauer_
geschrieben 30. Oktober 2009 - 11:18
Ne leider nicht, hatte vorgestern neu formatiert.
Aber war nicht mal "memtest" oder so zu DOS Zeiten ein Speichertest- Programm?
Aber war nicht mal "memtest" oder so zu DOS Zeiten ein Speichertest- Programm?
#10
Andi_84
- Gruppe: aktive Mitglieder
- Beiträge: 401
- Beigetreten: 30. November 08
- Reputation: 1
- Geschlecht:Männlich
- Wohnort:Bayern
geschrieben 30. Oktober 2009 - 11:46
Lad dir mal bei
http://www.memtest86.com/download.html
das "ISO image for creating bootable CD" herunter, brenne damit eine bootfähige CD.
Damit kannst du deinen RAM mal komplett durchtesten (sogar unabhängig von Windows).
VG,
Анди
http://www.memtest86.com/download.html
das "ISO image for creating bootable CD" herunter, brenne damit eine bootfähige CD.
Damit kannst du deinen RAM mal komplett durchtesten (sogar unabhängig von Windows).
VG,
Анди
Laptop: HP EliteBook 8560p; Core i7-2720QM, 16 GB DDR3 1333, 500 GB HDD, Intel HD Graphics 3000, Win 7 x64 SP1 Build 7601.17514
Internetzugang: T-Home VDSL 50 @ 51392 kbit/s down, 10048 kbit/s up || Router: FritzBox 7360 @ FW 111.05.24
Internetzugang: T-Home VDSL 50 @ 51392 kbit/s down, 10048 kbit/s up || Router: FritzBox 7360 @ FW 111.05.24
#11
Michael41a
- Gruppe: aktive Mitglieder
- Beiträge: 208
- Beigetreten: 01. Juli 07
- Reputation: 21
- Geschlecht:Männlich
geschrieben 30. Oktober 2009 - 13:03
Zitat (Andi_84: 30.10.2009, 12:46)
Lad dir mal bei
http://www.memtest86.com/download.html
das "ISO image for creating bootable CD" herunter, brenne damit eine bootfähige CD.
Damit kannst du deinen RAM mal komplett durchtesten (sogar unabhängig von Windows).
http://www.memtest86.com/download.html
das "ISO image for creating bootable CD" herunter, brenne damit eine bootfähige CD.
Damit kannst du deinen RAM mal komplett durchtesten (sogar unabhängig von Windows).
Oder einfach eine Knoppix-CD starten, "memtest" eintippen und Enter drücken.
Ich hatte in den vergangenen Jahren zwei- oder dreimal Bluescreens, und immer war ein Speicherriegel kaputt.
Michael
Hier könnte Ihre Werbung stehen.
#12 _fjordblauer_
geschrieben 30. Oktober 2009 - 14:33
Okay, aber hat Windows 7 sowas nicht, wenn DOS es vor Tausend Jahren schon hatte? 
#13
Mr. Floppy
- Gruppe: VIP Mitglieder
- Beiträge: 4.126
- Beigetreten: 01. Juli 08
- Reputation: 271
- Geschlecht:Männlich
geschrieben 30. Oktober 2009 - 16:31
Es macht schlicht und ergreifend keinen Sinn den Arbeitsspeicher unter einem laufenden Betriebssystem zu testen. Der Teil der gerade verwendet wird, kann nämlich nicht getestet werden. Und wenn sich der Fehler im benutzten RAM versteckt, kann man dem Ergebnis des Tests nicht trauen.
#14 _fjordblauer_
geschrieben 30. Oktober 2009 - 21:16
Zitat (Mr. Floppy: 30.10.2009, 17:31)
Es macht schlicht und ergreifend keinen Sinn den Arbeitsspeicher unter einem laufenden Betriebssystem zu testen. Der Teil der gerade verwendet wird, kann nämlich nicht getestet werden. Und wenn sich der Fehler im benutzten RAM versteckt, kann man dem Ergebnis des Tests nicht trauen.
Okay, das macht Sinn. Ich werde das Tool mal downloaden und brennen. Ist das korrekt, dass es nicht einmal 1 MB groß ist?
#15
XyMcCoy
geschrieben 30. Oktober 2009 - 21:23
ist nicht groß nur ein kleines dos tool
Der Größte Fehler bei Computern sitzt meißtens davor ! :-)
- ← [erledigt] Keine Aero Nach Ruhezustand
- Windows 7 - System & Software
- Desktop Anzeigen Ganz Rechts Aus Der Taskleiste Ausblenden? →
