Prosze O Pomoc

[acidi]

Witam

 

Dzisiaj juz kolejny raz instalowalem system ... Kolejne BSOD np. 1000008E

 

Bardzo prosze o sprawdzenie 2 plikow minidump . Spakowane w zipie

 

http://odsiebie.com/pokaz/1807617---798c.html

 

Nie wiem czy dobrze to zrobile ale ponizej zamiszczam ostatni log z pliku minidump

 

 

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini031409-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp_sp3_qfe.080814-1300

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Sat Mar 14 11:01:07.125 2009 (GMT+1)

System Uptime: 0 days 0:05:30.856

Loading Kernel Symbols

...............................................................

...............................................

Loading User Symbols

Loading unloaded module list

...........

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1000000A, {0, 2, 1, 805226f8}

 

Probably caused by : memory_corruption ( nt!MiRemovePageByColor+66 )

 

Followup: MachineOwner

---------

 

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 00000000, memory referenced

Arg2: 00000002, IRQL

Arg3: 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: 805226f8, address which referenced memory

 

Debugging Details:

------------------

 

 

WRITE_ADDRESS: 00000000

 

CURRENT_IRQL: 2

 

FAULTING_IP:

nt!MiRemovePageByColor+66

805226f8 ff08 dec dword ptr [eax]

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: DRIVER_FAULT

 

BUGCHECK_STR: 0xA

 

PROCESS_NAME: SimPack.exe

 

LAST_CONTROL_TRANSFER: from 80522a90 to 805226f8

 

STACK_TEXT:

b54c1cdc 80522a90 00000000 c00097e0 0000001a nt!MiRemovePageByColor+0x66

b54c1cf8 80520885 012fc000 00000015 010cbbea nt!MiRemoveZeroPage+0x8a

b54c1d4c 80544588 00000001 012fc000 00000001 nt!MmAccessFault+0xeb3

b54c1d4c 61b902dc 00000001 012fc000 00000001 nt!KiTrap0E+0xd0

WARNING: Frame IP not in any known module. Following frames may be wrong.

010cbbea 00000000 00000000 00000000 00000000 0x61b902dc

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

nt!MiRemovePageByColor+66

805226f8 ff08 dec dword ptr [eax]

 

SYMBOL_STACK_INDEX: 0

 

SYMBOL_NAME: nt!MiRemovePageByColor+66

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: nt

 

DEBUG_FLR_IMAGE_TIMESTAMP: 48a40463

 

IMAGE_NAME: memory_corruption

 

FAILURE_BUCKET_ID: 0xA_nt!MiRemovePageByColor+66

 

BUCKET_ID: 0xA_nt!MiRemovePageByColor+66

 

Followup: MachineOwner

---------

 

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 00000000, memory referenced

Arg2: 00000002, IRQL

Arg3: 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: 805226f8, address which referenced memory

 

Debugging Details:

------------------

 

 

WRITE_ADDRESS: 00000000

 

CURRENT_IRQL: 2

 

FAULTING_IP:

nt!MiRemovePageByColor+66

805226f8 ff08 dec dword ptr [eax]

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: DRIVER_FAULT

 

BUGCHECK_STR: 0xA

 

PROCESS_NAME: SimPack.exe

 

LAST_CONTROL_TRANSFER: from 80522a90 to 805226f8

 

STACK_TEXT:

b54c1cdc 80522a90 00000000 c00097e0 0000001a nt!MiRemovePageByColor+0x66

b54c1cf8 80520885 012fc000 00000015 010cbbea nt!MiRemoveZeroPage+0x8a

b54c1d4c 80544588 00000001 012fc000 00000001 nt!MmAccessFault+0xeb3

b54c1d4c 61b902dc 00000001 012fc000 00000001 nt!KiTrap0E+0xd0

WARNING: Frame IP not in any known module. Following frames may be wrong.

010cbbea 00000000 00000000 00000000 00000000 0x61b902dc

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

nt!MiRemovePageByColor+66

805226f8 ff08 dec dword ptr [eax]

 

SYMBOL_STACK_INDEX: 0

 

SYMBOL_NAME: nt!MiRemovePageByColor+66

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: nt

 

DEBUG_FLR_IMAGE_TIMESTAMP: 48a40463

 

IMAGE_NAME: memory_corruption

 

FAILURE_BUCKET_ID: 0xA_nt!MiRemovePageByColor+66

 

BUCKET_ID: 0xA_nt!MiRemovePageByColor+66

 

Followup: MachineOwner

---------

Edytowane 13 Marca 2009 przez acidi

[Kolobos]

Po co zakladasz kolejny temat?! Juz Ci napisalem co zrobic, wiec po co zasmiecasz?