So hier der Link:
http://www.xup.in/dl...2-21075-01.dmp/
Dieser Beitrag wurde von Windows44 bearbeitet: 25. Februar 2012 - 12:33
geschrieben 25. Februar 2012 - 12:28
Dieser Beitrag wurde von Windows44 bearbeitet: 25. Februar 2012 - 12:33
geschrieben 25. Februar 2012 - 12:48
Dieser Beitrag wurde von Mr. Floppy bearbeitet: 25. Februar 2012 - 12:48
geschrieben 25. Februar 2012 - 13:08
Dieser Beitrag wurde von Windows44 bearbeitet: 25. Februar 2012 - 13:39
geschrieben 25. Februar 2012 - 13:40
geschrieben 25. Februar 2012 - 13:42
Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [E:\Downloads\022512-21075-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\WinDDK\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 Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02a03000 PsLoadedModuleList = 0xfffff800`02c48670 Debug session time: Sat Feb 25 12:08:26.108 2012 (UTC + 1:00) System Uptime: 0 days 0:34:10.653 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) 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. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - Der Vorgang wurde erfolgreich beendet. FAULTING_IP: +6438356262386331 00000000`00000000 ? ? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff80000b9c328 -- (.exr 0xfffff80000b9c328) ExceptionAddress: fffff80002a88629 (nt!KiTimerWaitTest+0x0000000000000189) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff80000b9c3d0 -- (.trap 0xfffff80000b9c3d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000008 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002a88629 rsp=fffff80000b9c560 rbp=fffffa8005912828 r8=fffff80002bf8001 r9=0000000000000003 r10=000000000000007b r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KiTimerWaitTest+0x189: fffff800`02a88629 f0490fba6c244000 lock bts qword ptr [r12+40h],0 ds:00000000`00000040=? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a775fe to fffff80002a7fc10 STACK_TEXT: fffff800`00b9b408 fffff800`02a775fe : 00000000`00000000 fffff800`00b9c480 fffff800`00b9bb80 fffff800`02aab830 : nt!KeBugCheck fffff800`00b9b410 fffff800`02aab4fd : fffff800`02c8971c fffff800`02bc6c30 fffff800`02a03000 fffff800`00b9c328 : nt!KiKernelCalloutExceptionHandler+0xe fffff800`00b9b440 fffff800`02aaa2d5 : fffff800`02bca0fc fffff800`00b9b4b8 fffff800`00b9c328 fffff800`02a03000 : nt!RtlpExecuteHandlerForException+0xd fffff800`00b9b470 fffff800`02abb361 : fffff800`00b9c328 fffff800`00b9bb80 fffff800`00000000 fffffa80`05912820 : nt!RtlDispatchException+0x415 fffff800`00b9bb50 fffff800`02a7f2c2 : fffff800`00b9c328 fffffa80`05912828 fffff800`00b9c3d0 00000000`00000000 : nt!KiDispatchException+0x135 fffff800`00b9c1f0 fffff800`02a7dbca : fffff880`009e9180 fffffa80`0657c820 fffffa80`04831d30 fffff880`016865f7 : nt!KiExceptionDispatch+0xc2 fffff800`00b9c3d0 fffff800`02a88629 : ffffffff`fffb6c20 fffff800`02a8b5fc fffff800`00b9c660 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a fffff800`00b9c560 fffff800`02a8b43d : fffffa80`05912820 fffffa80`041cc168 fffffa80`041cc168 00000000`00000102 : nt!KiTimerWaitTest+0x189 fffff800`00b9c5e0 fffff800`02a8b37e : 00000004`c648edf4 fffff800`00b9cc58 00000000`0002017b fffff800`02bf91e8 : nt!KiProcessExpiredTimerList+0x6d fffff800`00b9cc30 fffff800`02a8b167 : 00000001`67c53ec2 00000001`0002017b 00000001`67c53e97 00000000`0000007b : nt!KiTimerExpiration+0x1be fffff800`00b9ccd0 fffff800`02a7796a : fffff800`02bf5e80 fffff800`02c03cc0 00000000`00000000 fffff880`0524c588 : nt!KiRetireDpcList+0x277 fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`02a775fe 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner --------- 0: kd> lmvm nt start end module name fffff800`02a03000 fffff800`02fec000 nt (pdb symbols) c:\winddk\symbols\ntkrnlmp.pdb\47F5C3BF9E0A493C9F63BB8F6413358B2\ntkrnlmp.pdb Loaded symbol image file: ntkrnlmp.exe Mapped memory image file: c:\winddk\symbols\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe Image path: ntkrnlmp.exe Image name: ntkrnlmp.exe Timestamp: Thu Jun 23 04:53:23 2011 (4E02AAA3) CheckSum: 0055C228 ImageSize: 005E9000 File version: 6.1.7601.17640 Product version: 6.1.7601.17640 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.7601.17640 FileVersion: 6.1.7601.17640 (win7sp1_gdr.110622-1506) FileDescription: NT Kernel & System LegalCopyright: © Microsoft Corporation. All rights reserved.Ich kann daran nicht erkennen was ihn ausgelöst hat. Sehr wahrscheinlich ein Treiber, aber welcher? Hast Du den Speicher mit Memtest86+ getestet oder woran machst Du fest, daß er in Ordnung ist?
geschrieben 25. Februar 2012 - 13:43
Dieser Beitrag wurde von Windows44 bearbeitet: 25. Februar 2012 - 13:44
geschrieben 25. Februar 2012 - 14:21
Zitat (Windows44: 25. Februar 2012 - 13:43)
Zitat (Windows44: 25. Februar 2012 - 14:06)
geschrieben 25. Februar 2012 - 14:25
Dieser Beitrag wurde von Windows44 bearbeitet: 25. Februar 2012 - 14:28
geschrieben 25. Februar 2012 - 14:30
Zitat
Zitat
Dieser Beitrag wurde von Mr. Floppy bearbeitet: 25. Februar 2012 - 14:34
geschrieben 25. Februar 2012 - 14:51
geschrieben 25. Februar 2012 - 15:30
geschrieben 25. Februar 2012 - 15:35