Hallo zusammen!
Bin neu in diesem Forum, habe bereits viele viele andere Foren durchsucht, aber bisher nich die Antwort auf mein Problem gefunden.
Folgendes:
Habe einem Bekannten einen neuen Computer zusammengebaut (bereits der 2.), aber diesmal macht der Computer richtig schwierigkeiten.
Folgendes ist verbaut:
- Asus P7P55D-E LX Mainboard
- Intel i5 750 CPU
- OCZ DDR3-PC1333 DIMM (2x 2,0 GB)
- Nvidia GeForce 9600 GT (512 MB RAM)
- WD HDD S-ATA 500GB
- DVD/RW-Laufwerk S-ATA
- 560 Watt Netzteil
Zum Anfang hin lief der Computer stabil und schnell. Dann berichtete mir mein Bekannter, dass er beim Surfen im Internet abgestürzt sei mit BSOD.
Neuesten Treiber sind installiert. Bios ist aktuell. RAM wurden auf Fehler überprüft, sind aber OK. RAM sind auch in der QVL von Asus. Temperaturen von CPU normal.
Habe gelesen dass es womöglich der IDE-Controler von Asus sein könnte der Probleme macht, oder Avira, oder die HDD (bisher noch nicht auf Fehler überprüft) oder die unzureichende Stromversorgung. Letzteres kann nicht sein, da laut Berechnungen die minimale Stromversorgung bei ca. 450 W liegen sollte.
Habe nun die Minidump von Windows auslesen wollen. Die neueste Minidump ergibt folgendes Ergebnis:
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Robbie\Desktop\091810-21184-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\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 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a06000 PsLoadedModuleList = 0x82b4e810
Debug session time: Sat Sep 18 15:29:24.209 2010 (GMT+2)
System Uptime: 0 days 0:05:09.209
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
.....
Die zweitletzte Minidump:
Code:
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, 965d8cff, 9113ec0c, 0}
***** 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 ***
*** ***
*************************************************************************
Probably caused by : win32k.sys ( win32k!NtUserDrawIconEx+1e )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: 965d8cff, The address that the exception occurred at
Arg3: 9113ec0c, Trap Frame
Arg4: 00000000
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 ***
*** ***
*************************************************************************
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: win32k
FAULTING_MODULE: 82814000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c425a
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {AUSNAHME} Ung ltige Anweisung Es wurde versucht, eine ung ltige Anweisung auszuf hren.
FAULTING_IP:
+4344a
965d8cff ?? ???
TRAP_FRAME: 9113ec0c -- (.trap 0xffffffff9113ec0c)
ErrCode = 00000000
eax=9113ed0c ebx=9591586a ecx=8571ed48 edx=9591586a esi=0459eb70 edi=000b05d7
eip=965d8cff esp=9113ec80 ebp=9113ed1c iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
965d8cff ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 9591587b to 965d8cff
FAILED_INSTRUCTION_ADDRESS:
+4344a
965d8cff ?? ???
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
9113ec7c 9591587b 04bb8dce 000b05d7 0459eb70 0x965d8cff
9113ed1c 8285744a 000b05d7 0459eb78 0459eb88 win32k!NtUserDrawIconEx+0x1e
9113ed34 76f164f4 badb0d00 0459eb60 00000000 nt+0x4344a
9113ed38 badb0d00 0459eb60 00000000 00000000 0x76f164f4
9113ed3c 0459eb60 00000000 00000000 00000000 0xbadb0d00
9113ed40 00000000 00000000 00000000 00000000 0x459eb60
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!NtUserDrawIconEx+1e
9591587b b203 mov dl,3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: win32k!NtUserDrawIconEx+1e
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: win32k.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
--------- Und die letzte Minidump:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 828ecc16, a32e3afc, 0}
***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntkrnlpa.exe ( nt+acc16 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 828ecc16, The address that the exception occurred at
Arg3: a32e3afc, Trap Frame
Arg4: 00000000
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 ***
*** ***
*************************************************************************
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: 82840000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nt+acc16
828ecc16 8b07 mov eax,dword ptr [edi]
TRAP_FRAME: a32e3afc -- (.trap 0xffffffffa32e3afc)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=85ce3728 edx=00003400 esi=85d42030 edi=00000000
eip=828ecc16 esp=a32e3b70 ebp=a32e3b98 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
nt+0xacc16:
828ecc16 8b07 mov eax,dword ptr [edi] ds:0023:00000000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 828ec68e to 828ecc16
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a32e3b98 828ec68e c0600010 c00020c8 c080204c nt+0xacc16
a32e3bb8 828c14d4 85ce3538 883ed140 85d42030 nt+0xac68e
a32e3c14 82a8cc68 883ed140 00419000 00001000 nt+0x814d4
a32e3d14 8288344a ffffffff 003df02c 00000000 nt+0x24cc68
a32e3d34 771864f4 badb0d00 003deff8 00000000 nt+0x4344a
a32e3d38 badb0d00 003deff8 00000000 00000000 0x771864f4
a32e3d3c 003deff8 00000000 00000000 00000000 0xbadb0d00
a32e3d40 00000000 00000000 00000000 00000000 0x3deff8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+acc16
828ecc16 8b07 mov eax,dword ptr [edi]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+acc16
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlpa.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
--------- Vielleicht kann sich einer von Euch einen Reim draus bilden? Was kann man dort in Erfahrung bringen? Ich lese immer nur
Probably caused by : ntkrnlpa.exe ( nt+acc16 )
Danke für Eure Mühen!
MFG
Robbie
Hardware/Treiber/Software Problem? Ständige Abstürze Win 7 
Linear-Darstellung
