molb0 Skrevet 11. november 2009 Del Skrevet 11. november 2009 Hei Jeg lurer på om noen kan hjelpe meg å tyde noen minne dumper? jeg har fulgt den guiden som sto øverst her. Det er min første post her så jeg beklager hvis jeg gjør noe galt Siste: PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffe96000380470, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff96000185583, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000007, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf40e0 ffffe96000380470 FAULTING_IP: win32k!fnHkINLPMSG+1cb fffff960`00185583 ff15e7ae1f00 call qword ptr [win32k!_imp_ExEnterPriorityRegionAndAcquireResourceExclusive (fffff960`00380470)] MM_INTERNAL_CODE: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800c0f46f0 -- (.trap 0xfffff8800c0f46f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8008882a90 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff96000185583 rsp=fffff8800c0f4880 rbp=0000000000030000 r8=fffff880009f1ec0 r9=fffff8800c0f4db0 r10=fffff8800c0f46c0 r11=fffff8800c0f4850 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc win32k!fnHkINLPMSG+0x1cb: fffff960`00185583 ff15e7ae1f00 call qword ptr [win32k!_imp_ExEnterPriorityRegionAndAcquireResourceExclusive (fffff960`00380470)] ds:fffff960`00380470=00000000002fd05a Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002b3bb19 to fffff80002abdf00 STACK_TEXT: fffff880`0c0f4588 fffff800`02b3bb19 : 00000000`00000050 ffffe960`00380470 00000000`00000000 fffff880`0c0f46f0 : nt!KeBugCheckEx fffff880`0c0f4590 fffff800`02abbfee : 00000000`00000000 fffff880`0c0f4b68 405cc000`20000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40edb fffff880`0c0f46f0 fffff960`00185583 : fffff900`0000002f fffff880`0c0f48f0 fffff880`0c0f4b68 fffff880`0c0f4a00 : nt!KiPageFault+0x16e fffff880`0c0f4880 fffff960`0016ea58 : 00000000`00000000 00000000`00000000 fffff900`c24bec30 00000000`00000000 : win32k!fnHkINLPMSG+0x1cb fffff880`0c0f4970 fffff960`001a9850 : fffff900`00000000 fffff900`c24bec30 fffff880`0c0f4ca0 00650070`00000000 : win32k!xxxCallCtfHook+0x184 fffff880`0c0f4a00 fffff960`001a9c19 : 00000000`00000000 fffff800`000025ff 00000000`00000000 fffffa80`ffffffff : win32k!xxxRealInternalGetMessage+0x518 fffff880`0c0f4ae0 fffff960`001a26a7 : 00000000`00000000 00000000`002efd20 fffff900`c0c3d4e0 fffff900`c01f2290 : win32k!xxxInternalGetMessage+0x35 fffff880`0c0f4b20 fffff800`02abd153 : fffffa80`0976db60 00000000`002ee068 fffff880`0c0f4bc8 00000000`74b62450 : win32k!NtUserPeekMessage+0x77 fffff880`0c0f4bb0 00000000`74bafbda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`002ee048 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74bafbda STACK_COMMAND: kb FOLLOWUP_IP: win32k!fnHkINLPMSG+1cb fffff960`00185583 ff15e7ae1f00 call qword ptr [win32k!_imp_ExEnterPriorityRegionAndAcquireResourceExclusive (fffff960`00380470)] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: win32k!fnHkINLPMSG+1cb FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0 FAILURE_BUCKET_ID: X64_0x50_win32k!fnHkINLPMSG+1cb BUCKET_ID: X64_0x50_win32k!fnHkINLPMSG+1cb Followup: MachineOwner --------- nest siste Microsoft ® Windows Debugger Version 6.11.0001.402 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\111009-33649-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a5b000 PsLoadedModuleList = 0xfffff800`02c98e50 Debug session time: Tue Nov 10 23:21:26.254 2009 (GMT+1) System Uptime: 0 days 5:33:52.283 Loading Kernel Symbols ............................................................... ................................................................ ....................................... Loading User Symbols Loading unloaded module list ......................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffe96000310470, 0, fffff96000115583, 7} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!fnHkINLPMSG+1cb ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffe96000310470, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff96000115583, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000007, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d030e0 ffffe96000310470 FAULTING_IP: win32k!fnHkINLPMSG+1cb fffff960`00115583 ff15e7ae1f00 call qword ptr [win32k!_imp_ExEnterPriorityRegionAndAcquireResourceExclusive (fffff960`00310470)] MM_INTERNAL_CODE: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800a31b6f0 -- (.trap 0xfffff8800a31b6f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80081da480 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff96000115583 rsp=fffff8800a31b880 rbp=0000000000030000 r8=fffff880009f1ec0 r9=fffff8800a31bdb0 r10=fffff8800a31b6c0 r11=fffff8800a31b850 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc win32k!fnHkINLPMSG+0x1cb: fffff960`00115583 ff15e7ae1f00 call qword ptr [win32k!_imp_ExEnterPriorityRegionAndAcquireResourceExclusive (fffff960`00310470)] ds:fffff960`00310470=00000000002fd05a Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002b4ab19 to fffff80002accf00 STACK_TEXT: fffff880`0a31b588 fffff800`02b4ab19 : 00000000`00000050 ffffe960`00310470 00000000`00000000 fffff880`0a31b6f0 : nt!KeBugCheckEx fffff880`0a31b590 fffff800`02acafee : 00000000`00000000 fffff880`0a31bb68 40729000`20000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40edb fffff880`0a31b6f0 fffff960`00115583 : 00000000`0000002f fffff880`0a31b8f0 fffff880`0a31bb68 fffff880`0a31ba00 : nt!KiPageFault+0x16e fffff880`0a31b880 fffff960`000fea58 : 00000000`00000000 00000000`00000000 fffff900`c09d3c30 00000000`00000000 : win32k!fnHkINLPMSG+0x1cb fffff880`0a31b970 fffff960`00139850 : fffff900`00000000 fffff900`c09d3c30 fffff880`0a31bca0 00650070`00000000 : win32k!xxxCallCtfHook+0x184 fffff880`0a31ba00 fffff960`00139c19 : 00000000`00000000 fffff800`000025ff 00000000`00000000 fffffa80`ffffffff : win32k!xxxRealInternalGetMessage+0x518 fffff880`0a31bae0 fffff960`001326a7 : 00000000`00000000 00000000`0020fd20 fffff900`c0c715a0 fffff900`c2867010 : win32k!xxxInternalGetMessage+0x35 fffff880`0a31bb20 fffff800`02acc153 : fffffa80`0a231730 00000000`0020e288 fffff880`0a31bbc8 00000000`00000000 : win32k!NtUserPeekMessage+0x77 fffff880`0a31bbb0 00000000`7379fbda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0020e268 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7379fbda STACK_COMMAND: kb FOLLOWUP_IP: win32k!fnHkINLPMSG+1cb fffff960`00115583 ff15e7ae1f00 call qword ptr [win32k!_imp_ExEnterPriorityRegionAndAcquireResourceExclusive (fffff960`00310470)] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: win32k!fnHkINLPMSG+1cb FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0 FAILURE_BUCKET_ID: X64_0x50_win32k!fnHkINLPMSG+1cb BUCKET_ID: X64_0x50_win32k!fnHkINLPMSG+1cb Followup: MachineOwner --------- Første Loading Dump File [C:\Windows\Minidump\110909-36519-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a59000 PsLoadedModuleList = 0xfffff800`02c96e50 Debug session time: Mon Nov 9 22:30:27.896 2009 (GMT+1) System Uptime: 0 days 2:40:41.925 Loading Kernel Symbols ............................................................... ................................................................ ........................................ Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffe960002c0470, 0, fffff960000c5583, 7} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!fnHkINLPMSG+1cb ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffe960002c0470, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff960000c5583, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000007, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d010e0 ffffe960002c0470 FAULTING_IP: win32k!fnHkINLPMSG+1cb fffff960`000c5583 ff15e7ae1f00 call qword ptr [win32k!_imp_ExEnterPriorityRegionAndAcquireResourceExclusive (fffff960`002c0470)] MM_INTERNAL_CODE: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800b7226f0 -- (.trap 0xfffff8800b7226f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800891a350 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff960000c5583 rsp=fffff8800b722880 rbp=0000000000030000 r8=fffff880009f1ec0 r9=fffff8800b722db0 r10=fffff8800b7226c0 r11=fffff8800b722850 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc win32k!fnHkINLPMSG+0x1cb: fffff960`000c5583 ff15e7ae1f00 call qword ptr [win32k!_imp_ExEnterPriorityRegionAndAcquireResourceExclusive (fffff960`002c0470)] ds:fffff960`002c0470=00000000002fd05a Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002b48b19 to fffff80002acaf00 STACK_TEXT: fffff880`0b722588 fffff800`02b48b19 : 00000000`00000050 ffffe960`002c0470 00000000`00000000 fffff880`0b7226f0 : nt!KeBugCheckEx fffff880`0b722590 fffff800`02ac8fee : 00000000`00000000 fffff880`0b722b68 ff401809`ff401800 ff401809`ff401809 : nt! ?? ::FNODOBFM::`string'+0x40edb fffff880`0b7226f0 fffff960`000c5583 : 00000000`0000002f fffff880`0b7228f0 fffff880`0b722b68 fffff880`0b722a00 : nt!KiPageFault+0x16e fffff880`0b722880 fffff960`000aea58 : 00000000`00000000 00000000`00000000 fffff900`c098bc30 00000000`00000000 : win32k!fnHkINLPMSG+0x1cb fffff880`0b722970 fffff960`000e9850 : fffff900`00000000 fffff900`c098bc30 fffff880`0b722ca0 00650070`00000000 : win32k!xxxCallCtfHook+0x184 fffff880`0b722a00 fffff960`000e9c19 : 00000000`00000000 fffff800`000025ff 00000000`00000000 fffffa80`ffffffff : win32k!xxxRealInternalGetMessage+0x518 fffff880`0b722ae0 fffff960`000e26a7 : 00000000`00000000 00000000`000efd20 fffff900`c0c43ce0 fffff900`c09d0ce0 : win32k!xxxInternalGetMessage+0x35 fffff880`0b722b20 fffff800`02aca153 : fffffa80`0a7cb060 00000000`000ee258 fffff880`0b722bc8 00000000`00000000 : win32k!NtUserPeekMessage+0x77 fffff880`0b722bb0 00000000`72d3fbda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`000ee238 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72d3fbda STACK_COMMAND: kb FOLLOWUP_IP: win32k!fnHkINLPMSG+1cb fffff960`000c5583 ff15e7ae1f00 call qword ptr [win32k!_imp_ExEnterPriorityRegionAndAcquireResourceExclusive (fffff960`002c0470)] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: win32k!fnHkINLPMSG+1cb FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0 FAILURE_BUCKET_ID: X64_0x50_win32k!fnHkINLPMSG+1cb BUCKET_ID: X64_0x50_win32k!fnHkINLPMSG+1cb Followup: MachineOwner --------- Lenke til kommentar
Mechablast Skrevet 11. november 2009 Del Skrevet 11. november 2009 (endret) Last ned memtest, brenn som image og start maskinen fra cd/dvden. La testen stå over en natt. http://memtest.org/download/4.00/memtest86+-4.00.iso.zip Brenne program http://www.ntfs.com/iso-burning.htm Endret 11. november 2009 av arjato Lenke til kommentar
molb0 Skrevet 12. november 2009 Forfatter Del Skrevet 12. november 2009 Memtest finner ingen feil Lenke til kommentar
Peachy Skrevet 14. desember 2009 Del Skrevet 14. desember 2009 Probably caused by : win32k.sys ( win32k!fnHkINLPMSG+1cb ) Der har du problemet. Nå som du vet hva som foresaker problemet, søk etter win32k.sys på Google i betrakning av en BSoD. Håper det hjalp Lenke til kommentar
Anbefalte innlegg
Opprett en konto eller logg inn for å kommentere
Du må være et medlem for å kunne skrive en kommentar
Opprett konto
Det er enkelt å melde seg inn for å starte en ny konto!
Start en kontoLogg inn
Har du allerede en konto? Logg inn her.
Logg inn nå