פורסם 2008 במרץ 1117 שנים המחשב ניתקע ניכנס למסך כחול ואז עשה ריסט הנה המפרט של קבצי DUMP Microsoft ® Windows Debugger Version 6.8.0004.0 X86Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [C:\WINDOWS\Minidump\Mini031008-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSBuilt by: 2600.xpsp_sp2_gdr.070227-2254Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700Debug session time: Mon Mar 10 07:04:41.031 2008 (GMT+2)System Uptime: 0 days 8:14:07.769Loading Kernel Symbols...Loading User SymbolsLoading unloaded module list..................******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1000000A, {90edc008, 2, 1, 80522bd9}Probably caused by : memory_corruption ( nt!MiReleasePageFileSpace+55 )Followup: MachineOwner---------1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 90edc008, memory referencedArg2: 00000002, IRQLArg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: 80522bd9, address which referenced memoryDebugging Details:------------------WRITE_ADDRESS: 90edc008 CURRENT_IRQL: 2FAULTING_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0xAPROCESS_NAME: HPZipm12.exeLAST_CONTROL_TRANSFER: from 80523110 to 80522bd9STACK_TEXT: b5a4c674 80523110 00000000 40000000 629c3000 nt!MiReleasePageFileSpace+0x55b5a4c6ac 80523284 c0314e18 629c3000 00000000 nt!MiDeletePte+0x4a2b5a4c774 80519509 e1ab13c0 629c8fff 00000000 nt!MiDeleteVirtualAddresses+0x164b5a4c824 805b17f1 88e46af8 890a5708 b5a4c894 nt!MiRemoveMappedView+0x237b5a4c868 805b18e0 8a603e30 89525928 00000000 nt!MiUnmapViewOfSection+0x12bb5a4c884 8054086c ffffffff 88e46af8 0012ecf8 nt!NtUnmapViewOfSection+0x54b5a4c884 7c90eb94 ffffffff 88e46af8 0012ecf8 nt!KiFastCallEntry+0xfcWARNING: Frame IP not in any known module. Following frames may be wrong.0012ecf8 00000000 00000000 00000000 00000000 0x7c90eb94STACK_COMMAND: kbFOLLOWUP_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediSYMBOL_STACK_INDEX: 0SYMBOL_NAME: nt!MiReleasePageFileSpace+55FOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9dIMAGE_NAME: memory_corruptionFAILURE_BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55Followup: MachineOwner---------1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 90edc008, memory referencedArg2: 00000002, IRQLArg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: 80522bd9, address which referenced memoryDebugging Details:------------------WRITE_ADDRESS: 90edc008 CURRENT_IRQL: 2FAULTING_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0xAPROCESS_NAME: HPZipm12.exeLAST_CONTROL_TRANSFER: from 80523110 to 80522bd9STACK_TEXT: b5a4c674 80523110 00000000 40000000 629c3000 nt!MiReleasePageFileSpace+0x55b5a4c6ac 80523284 c0314e18 629c3000 00000000 nt!MiDeletePte+0x4a2b5a4c774 80519509 e1ab13c0 629c8fff 00000000 nt!MiDeleteVirtualAddresses+0x164b5a4c824 805b17f1 88e46af8 890a5708 b5a4c894 nt!MiRemoveMappedView+0x237b5a4c868 805b18e0 8a603e30 89525928 00000000 nt!MiUnmapViewOfSection+0x12bb5a4c884 8054086c ffffffff 88e46af8 0012ecf8 nt!NtUnmapViewOfSection+0x54b5a4c884 7c90eb94 ffffffff 88e46af8 0012ecf8 nt!KiFastCallEntry+0xfcWARNING: Frame IP not in any known module. Following frames may be wrong.0012ecf8 00000000 00000000 00000000 00000000 0x7c90eb94STACK_COMMAND: kbFOLLOWUP_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediSYMBOL_STACK_INDEX: 0SYMBOL_NAME: nt!MiReleasePageFileSpace+55FOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9dIMAGE_NAME: memory_corruptionFAILURE_BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55Followup: MachineOwner---------1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 90edc008, memory referencedArg2: 00000002, IRQLArg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: 80522bd9, address which referenced memoryDebugging Details:------------------WRITE_ADDRESS: 90edc008 CURRENT_IRQL: 2FAULTING_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0xAPROCESS_NAME: HPZipm12.exeLAST_CONTROL_TRANSFER: from 80523110 to 80522bd9STACK_TEXT: b5a4c674 80523110 00000000 40000000 629c3000 nt!MiReleasePageFileSpace+0x55b5a4c6ac 80523284 c0314e18 629c3000 00000000 nt!MiDeletePte+0x4a2b5a4c774 80519509 e1ab13c0 629c8fff 00000000 nt!MiDeleteVirtualAddresses+0x164b5a4c824 805b17f1 88e46af8 890a5708 b5a4c894 nt!MiRemoveMappedView+0x237b5a4c868 805b18e0 8a603e30 89525928 00000000 nt!MiUnmapViewOfSection+0x12bb5a4c884 8054086c ffffffff 88e46af8 0012ecf8 nt!NtUnmapViewOfSection+0x54b5a4c884 7c90eb94 ffffffff 88e46af8 0012ecf8 nt!KiFastCallEntry+0xfcWARNING: Frame IP not in any known module. Following frames may be wrong.0012ecf8 00000000 00000000 00000000 00000000 0x7c90eb94STACK_COMMAND: kbFOLLOWUP_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediSYMBOL_STACK_INDEX: 0SYMBOL_NAME: nt!MiReleasePageFileSpace+55FOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9dIMAGE_NAME: memory_corruptionFAILURE_BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55Followup: MachineOwner---------1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 90edc008, memory referencedArg2: 00000002, IRQLArg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: 80522bd9, address which referenced memoryDebugging Details:------------------WRITE_ADDRESS: 90edc008 CURRENT_IRQL: 2FAULTING_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0xAPROCESS_NAME: HPZipm12.exeLAST_CONTROL_TRANSFER: from 80523110 to 80522bd9STACK_TEXT: b5a4c674 80523110 00000000 40000000 629c3000 nt!MiReleasePageFileSpace+0x55b5a4c6ac 80523284 c0314e18 629c3000 00000000 nt!MiDeletePte+0x4a2b5a4c774 80519509 e1ab13c0 629c8fff 00000000 nt!MiDeleteVirtualAddresses+0x164b5a4c824 805b17f1 88e46af8 890a5708 b5a4c894 nt!MiRemoveMappedView+0x237b5a4c868 805b18e0 8a603e30 89525928 00000000 nt!MiUnmapViewOfSection+0x12bb5a4c884 8054086c ffffffff 88e46af8 0012ecf8 nt!NtUnmapViewOfSection+0x54b5a4c884 7c90eb94 ffffffff 88e46af8 0012ecf8 nt!KiFastCallEntry+0xfcWARNING: Frame IP not in any known module. Following frames may be wrong.0012ecf8 00000000 00000000 00000000 00000000 0x7c90eb94STACK_COMMAND: kbFOLLOWUP_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediSYMBOL_STACK_INDEX: 0SYMBOL_NAME: nt!MiReleasePageFileSpace+55FOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9dIMAGE_NAME: memory_corruptionFAILURE_BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55Followup: MachineOwner---------1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 90edc008, memory referencedArg2: 00000002, IRQLArg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: 80522bd9, address which referenced memoryDebugging Details:------------------WRITE_ADDRESS: 90edc008 CURRENT_IRQL: 2FAULTING_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0xAPROCESS_NAME: HPZipm12.exeLAST_CONTROL_TRANSFER: from 80523110 to 80522bd9STACK_TEXT: b5a4c674 80523110 00000000 40000000 629c3000 nt!MiReleasePageFileSpace+0x55b5a4c6ac 80523284 c0314e18 629c3000 00000000 nt!MiDeletePte+0x4a2b5a4c774 80519509 e1ab13c0 629c8fff 00000000 nt!MiDeleteVirtualAddresses+0x164b5a4c824 805b17f1 88e46af8 890a5708 b5a4c894 nt!MiRemoveMappedView+0x237b5a4c868 805b18e0 8a603e30 89525928 00000000 nt!MiUnmapViewOfSection+0x12bb5a4c884 8054086c ffffffff 88e46af8 0012ecf8 nt!NtUnmapViewOfSection+0x54b5a4c884 7c90eb94 ffffffff 88e46af8 0012ecf8 nt!KiFastCallEntry+0xfcWARNING: Frame IP not in any known module. Following frames may be wrong.0012ecf8 00000000 00000000 00000000 00000000 0x7c90eb94STACK_COMMAND: kbFOLLOWUP_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediSYMBOL_STACK_INDEX: 0SYMBOL_NAME: nt!MiReleasePageFileSpace+55FOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9dIMAGE_NAME: memory_corruptionFAILURE_BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55Followup: MachineOwner---------1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 90edc008, memory referencedArg2: 00000002, IRQLArg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: 80522bd9, address which referenced memoryDebugging Details:------------------WRITE_ADDRESS: 90edc008 CURRENT_IRQL: 2FAULTING_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0xAPROCESS_NAME: HPZipm12.exeLAST_CONTROL_TRANSFER: from 80523110 to 80522bd9STACK_TEXT: b5a4c674 80523110 00000000 40000000 629c3000 nt!MiReleasePageFileSpace+0x55b5a4c6ac 80523284 c0314e18 629c3000 00000000 nt!MiDeletePte+0x4a2b5a4c774 80519509 e1ab13c0 629c8fff 00000000 nt!MiDeleteVirtualAddresses+0x164b5a4c824 805b17f1 88e46af8 890a5708 b5a4c894 nt!MiRemoveMappedView+0x237b5a4c868 805b18e0 8a603e30 89525928 00000000 nt!MiUnmapViewOfSection+0x12bb5a4c884 8054086c ffffffff 88e46af8 0012ecf8 nt!NtUnmapViewOfSection+0x54b5a4c884 7c90eb94 ffffffff 88e46af8 0012ecf8 nt!KiFastCallEntry+0xfcWARNING: Frame IP not in any known module. Following frames may be wrong.0012ecf8 00000000 00000000 00000000 00000000 0x7c90eb94STACK_COMMAND: kbFOLLOWUP_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediSYMBOL_STACK_INDEX: 0SYMBOL_NAME: nt!MiReleasePageFileSpace+55FOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9dIMAGE_NAME: memory_corruptionFAILURE_BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55Followup: MachineOwner---------1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 90edc008, memory referencedArg2: 00000002, IRQLArg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: 80522bd9, address which referenced memoryDebugging Details:------------------WRITE_ADDRESS: 90edc008 CURRENT_IRQL: 2FAULTING_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0xAPROCESS_NAME: HPZipm12.exeLAST_CONTROL_TRANSFER: from 80523110 to 80522bd9STACK_TEXT: b5a4c674 80523110 00000000 40000000 629c3000 nt!MiReleasePageFileSpace+0x55b5a4c6ac 80523284 c0314e18 629c3000 00000000 nt!MiDeletePte+0x4a2b5a4c774 80519509 e1ab13c0 629c8fff 00000000 nt!MiDeleteVirtualAddresses+0x164b5a4c824 805b17f1 88e46af8 890a5708 b5a4c894 nt!MiRemoveMappedView+0x237b5a4c868 805b18e0 8a603e30 89525928 00000000 nt!MiUnmapViewOfSection+0x12bb5a4c884 8054086c ffffffff 88e46af8 0012ecf8 nt!NtUnmapViewOfSection+0x54b5a4c884 7c90eb94 ffffffff 88e46af8 0012ecf8 nt!KiFastCallEntry+0xfcWARNING: Frame IP not in any known module. Following frames may be wrong.0012ecf8 00000000 00000000 00000000 00000000 0x7c90eb94STACK_COMMAND: kbFOLLOWUP_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediSYMBOL_STACK_INDEX: 0SYMBOL_NAME: nt!MiReleasePageFileSpace+55FOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9dIMAGE_NAME: memory_corruptionFAILURE_BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55Followup: MachineOwner---------1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 90edc008, memory referencedArg2: 00000002, IRQLArg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)Arg4: 80522bd9, address which referenced memoryDebugging Details:------------------WRITE_ADDRESS: 90edc008 CURRENT_IRQL: 2FAULTING_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0xAPROCESS_NAME: HPZipm12.exeLAST_CONTROL_TRANSFER: from 80523110 to 80522bd9STACK_TEXT: b5a4c674 80523110 00000000 40000000 629c3000 nt!MiReleasePageFileSpace+0x55b5a4c6ac 80523284 c0314e18 629c3000 00000000 nt!MiDeletePte+0x4a2b5a4c774 80519509 e1ab13c0 629c8fff 00000000 nt!MiDeleteVirtualAddresses+0x164b5a4c824 805b17f1 88e46af8 890a5708 b5a4c894 nt!MiRemoveMappedView+0x237b5a4c868 805b18e0 8a603e30 89525928 00000000 nt!MiUnmapViewOfSection+0x12bb5a4c884 8054086c ffffffff 88e46af8 0012ecf8 nt!NtUnmapViewOfSection+0x54b5a4c884 7c90eb94 ffffffff 88e46af8 0012ecf8 nt!KiFastCallEntry+0xfcWARNING: Frame IP not in any known module. Following frames may be wrong.0012ecf8 00000000 00000000 00000000 00000000 0x7c90eb94STACK_COMMAND: kbFOLLOWUP_IP: nt!MiReleasePageFileSpace+5580522bd9 213e and dword ptr [esi],ediSYMBOL_STACK_INDEX: 0SYMBOL_NAME: nt!MiReleasePageFileSpace+55FOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9dIMAGE_NAME: memory_corruptionFAILURE_BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55BUCKET_ID: 0xA_W_nt!MiReleasePageFileSpace+55Followup: MachineOwner---------
פורסם 2008 במרץ 1517 שנים יש לך איזה קובץ שם שקופץ מספר פעמיםלפי דעתי זו בעיית של טרוייאני או משהו זדוני אחרתסתכל פהhttp://www.neuber.com/taskmanager/process/hpzipm12.exe.html
ארכיון
דיון זה הועבר לארכיון ולא ניתן להוסיף בו תגובות חדשות.