Częste Blue screeny 0x0000000A

[XMan]

Sprawdzałeś sterowniki Chipset oraz do karty dźwiękowej AUDIO ze strony producenta płyty ?
Może już są nowsze/inne niż masz na płytce :
Dostępne tylko dla zarejestrowanych użytkowników

[advaldo]

Nic się nie zmieniło, prawdopodobnie takie same. Dalej jest wykrzyknik przy audio w menedżerze urządzeń, a program Aida pokazuje taki sam log.

Kolejny nowy bsod, pierwszy od zmiany adaptera. 0x0000004E

Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini071111-07.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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Jul 11 20:45:19.250 2011 (GMT+2)
System Uptime: 0 days 2:19:06.187
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 19250, 0, 0}

Probably caused by : memory_corruption ( nt!MiDecrementShareCount+3a )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 00019250, page frame number
Arg3: 00000000, current page state
Arg4: 00000000, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  7

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

PROCESS_NAME:  regsvr32.exe

LAST_CONTROL_TRANSFER:  from 80522dfc to 804f9f43

STACK_TEXT: 
a3abfbc0 80522dfc 0000004e 00000099 00019250 nt!KeBugCheckEx+0x1b
a3abfbf0 80511a75 c0884700 00000281 89a2d5a8 nt!MiDecrementShareCount+0x3a
a3abfc14 805b0287 77bd2101 89a2d3b0 007ffff8 nt!MiDeleteValidAddress+0x177
a3abfc34 80513517 89a2d3b0 89a2d4e8 89a2d3b0 nt!MiDeleteAddressesInWorkingSet+0x65
a3abfc68 805d274a 00a2d3b0 899be288 899be4d0 nt!MmCleanProcessAddressSpace+0x193
a3abfd08 805d290c 00000003 899be288 00000000 nt!PspExitThread+0x680
a3abfd28 805d2ae7 899be288 00000003 a3abfd64 nt!PspTerminateThreadByPointer+0x52
a3abfd54 8054167c 00000000 00000003 0007fee4 nt!NtTerminateProcess+0x105
a3abfd54 7c90e514 00000000 00000003 0007fee4 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0007fee4 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiDecrementShareCount+3a
80522dfc ff4e08          dec     dword ptr [esi+8]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiDecrementShareCount+3a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d00d46f

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x4E_99_nt!MiDecrementShareCount+3a

BUCKET_ID:  0x4E_99_nt!MiDecrementShareCount+3a

Followup: MachineOwner
---------



[cosik_ktosik]

Ciągle coś z pamięcią, zrób chkdsk na dysku.

[advaldo]

Próbowałem 3x chkdsk główny dysk C. Za każdym razem przy ostatnim kroku wyskakiwał bsod. O to zapis:

Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini071211-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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jul 12 00:01:33.203 2011 (GMT+2)
System Uptime: 0 days 1:02:25.155
Loading Kernel Symbols
...............................................................
................................................................

Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {497fffe4, 2, 1, 80522757}

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

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 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: 497fffe4, 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: 80522757, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS:  497fffe4

CURRENT_IRQL:  2

FAULTING_IP:
nt!MiRemovePageByColor+a5
80522757 891c01          mov     dword ptr [ecx+eax],ebx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  plugin-containe

LAST_CONTROL_TRANSFER:  from 80522c42 to 80522757

STACK_TEXT: 
a31e3bc8 80522c42 00000963 c0461a40 00000000 nt!MiRemovePageByColor+0xa5
a31e3be0 8066e8a9 00000028 a31e3c98 00000094 nt!MiRemoveAnyPage+0xbc
a31e3c0c 805370a0 00000094 2b707249 00000000 nt!MiAllocateSpecialPool+0x1f3
a31e3c2c 806601c3 00000000 00000094 2b707249 nt!ExAllocatePoolWithTagPriority+0x2c
a31e3c40 806604d6 00000000 00000001 8acfc801 nt!VfIrpAllocate+0x1f
a31e3c5c 806605d3 a31e3c84 00000000 00754004 nt!ViIrpAllocateLockedPacket+0x1c
a31e3c7c 806595bb 00000000 00754004 00000000 nt!VerifierIoAllocateIrp1+0x3f
a31e3cb4 8057c8a0 00000001 00000001 a31e3d64 nt!IovAllocateIrp+0x1d
a31e3d38 8054167c 00000090 00000000 00000000 nt!NtReadFile+0x3f2
a31e3d38 7c90e514 00000090 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fcb4 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiRemovePageByColor+a5
80522757 891c01          mov     dword ptr [ecx+eax],ebx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiRemovePageByColor+a5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d00d46f

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiRemovePageByColor+a5

BUCKET_ID:  0xA_nt!MiRemovePageByColor+a5

Followup: MachineOwner
---------


Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini071211-02.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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jul 12 11:19:47.750 2011 (GMT+2)
System Uptime: 0 days 0:57:44.693
Loading Kernel Symbols
...............................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {497fffe4, 2, 1, 80522757}

Unable to load image WlanBZXP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WlanBZXP.sys
*** ERROR: Module load completed but symbols could not be loaded for WlanBZXP.sys
Probably caused by : WlanBZXP.sys ( WlanBZXP+2de08 )

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 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: 497fffe4, 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: 80522757, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS:  497fffe4

CURRENT_IRQL:  2

FAULTING_IP:
nt!MiRemovePageByColor+a5
80522757 891c01          mov     dword ptr [ecx+eax],ebx

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 80522c42 to 80522757

STACK_TEXT: 
9b4a69b0 80522c42 00000963 c0463820 00000000 nt!MiRemovePageByColor+0xa5
9b4a69c8 8066e8a9 00000028 9b4a6a80 00000100 nt!MiRemoveAnyPage+0xbc
9b4a69f4 805370a0 00000100 2b707249 00000000 nt!MiAllocateSpecialPool+0x1f3
9b4a6a14 806601c3 00000000 00000100 2b707249 nt!ExAllocatePoolWithTagPriority+0x2c
9b4a6a28 806604d6 89f44da8 00000000 8acfc804 nt!VfIrpAllocate+0x1f
9b4a6a44 806605d3 9b4a6a6c 89f44da8 00000000 nt!ViIrpAllocateLockedPacket+0x1c
9b4a6a64 806595bb 00000000 00000000 89f44da8 nt!VerifierIoAllocateIrp1+0x3f
9b4a6a9c 998dce08 00000004 00000000 00000000 nt!IovAllocateIrp+0x1d
WARNING: Stack unwind information not available. Following frames may be wrong.
9b4a6b08 998dccd4 89caa000 9b4a6b34 9b4a6b30 WlanBZXP+0x2de08
9b4a6b38 998ba84f 89caa000 000096a4 9b4a6be8 WlanBZXP+0x2dcd4
9b4a6b58 998ba88b 89caa000 000006a4 9b4a6be8 WlanBZXP+0xb84f
9b4a6b74 998b6024 89caa000 000006a4 9b4a6be8 WlanBZXP+0xb88b
9b4a6dac 805cffa8 89caa000 00000000 00000000 WlanBZXP+0x7024
9b4a6ddc 8054615e 998b52a0 89caa000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
WlanBZXP+2de08
998dce08 ??              ???

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  WlanBZXP+2de08

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WlanBZXP

IMAGE_NAME:  WlanBZXP.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  43619d2b

FAILURE_BUCKET_ID:  0xA_WlanBZXP+2de08

BUCKET_ID:  0xA_WlanBZXP+2de08

Followup: MachineOwner
---------



Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini071211-03.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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jul 12 13:17:05.968 2011 (GMT+2)
System Uptime: 0 days 1:56:52.920
Loading Kernel Symbols
...............................................................
................................................................

Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {497fffe4, 2, 1, 80522757}

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

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: 497fffe4, 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: 80522757, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS:  497fffe4

CURRENT_IRQL:  2

FAULTING_IP:
nt!MiRemovePageByColor+a5
80522757 891c01          mov     dword ptr [ecx+eax],ebx

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 80522c42 to 80522757

STACK_TEXT: 
ba4c37f4 80522c42 000b86ce 00000000 00000000 nt!MiRemovePageByColor+0xa5
ba4c380c 8051cae7 00000000 00008000 00000000 nt!MiRemoveAnyPage+0xbc
ba4c3840 80699b94 8acad218 00000000 00000044 nt!MmZeroPageThread+0x153
ba4c3dac 805cffa8 80083000 00000000 00000000 nt!Phase1Initialization+0x1288
ba4c3ddc 8054615e 8069890c 80083000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiRemovePageByColor+a5
80522757 891c01          mov     dword ptr [ecx+eax],ebx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiRemovePageByColor+a5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d00d46f

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiRemovePageByColor+a5

BUCKET_ID:  0xA_nt!MiRemovePageByColor+a5

Followup: MachineOwner
---------


[cosik_ktosik]

Hmm, wszędzie to samo, ale w jednym mnie zaciekawiło to: PROCESS_NAME: plugin-contain
czyli proces Firefoxa od dodatków. Czasami nie ma BSODa zawsze gdy używasz Firefoxa?

[advaldo]

Czasami wyskakują przy używaniu Firefoxa.

[cosik_ktosik]

A w innych przypadkach? Może to sterowniki sieci świrują.

[advaldo]

Nie zauważyłem konkretnego przypadku w którym mam 100% bsod. Czasami tak jak pisałem nic nie robię na komputerze, ledwo włączę i jest bsod. Rzadko kiedy udaje się aby komputer działał 2-3h bez BSODa. Strasznie zaskakujące są bo nie jestem w stanie określić przy jakiej czynności się to dzieje dokładnie. Na sterownikach sieci się nic nie znam.

[cosik_ktosik]

Oki, zanim będę dalej kombinować, a ile Masz modułów pamięci? Może jak są dwa, to podziałaj na razie na jednym, jak wystąpi BSOD to wyciągnij tamten a zmień na drugi. Jeśli na obydwu tak się dzieje to będziemy dalej drążyć temat.

[advaldo]

mówisz o Ramie? W której szynie je ulokować? Ma to jakieś znaczenie?

[cosik_ktosik]

Tak, o ramie. Slot nie ma znaczenia najprawdopodobniej.

[advaldo]

Jeszcze będąc na 2 kościach pamięci:

Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini071311-04.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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Jul 13 11:59:54.343 2011 (GMT+2)
System Uptime: 0 days 0:51:12.918
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {497fffe4, 2, 1, 80522757}

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

Followup: MachineOwner
---------

2: 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: 497fffe4, 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: 80522757, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS:  497fffe4

CURRENT_IRQL:  2

FAULTING_IP:
nt!MiRemovePageByColor+a5
80522757 891c01          mov     dword ptr [ecx+eax],ebx

CUSTOMER_CRASH_COUNT:  4

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  HDeck.exe

LAST_CONTROL_TRANSFER:  from 80522c42 to 80522757

STACK_TEXT: 
946eeb84 80522c42 00000963 c0467950 00000000 nt!MiRemovePageByColor+0xa5
946eeb9c 8066e8a9 00000028 946eec54 000000b8 nt!MiRemoveAnyPage+0xbc
946eebc8 805370a0 000000b8 2b707249 00000000 nt!MiAllocateSpecialPool+0x1f3
946eebe8 806601c3 00000000 000000b8 2b707249 nt!ExAllocatePoolWithTagPriority+0x2c
946eebfc 806604d6 8a89d020 00000000 8acfc802 nt!VfIrpAllocate+0x1f
946eec18 806605d3 946eec40 8a89d020 00000000 nt!ViIrpAllocateLockedPacket+0x1c
946eec38 806595bb 00000000 00000000 8a89d020 nt!VerifierIoAllocateIrp1+0x3f
946eec70 80583a58 00000002 00000000 8a89d020 nt!IovAllocateIrp+0x1d
946eecb0 805bb4aa 8a89d038 00000000 8a89d020 nt!IopDeleteFile+0x6c
946eeccc 805266fa 8a89d038 00000000 0000020c nt!ObpRemoveObjectRoutine+0xe0
946eece4 805bc37f 8a865c88 e2a9c120 89bb7da8 nt!ObfDereferenceObject+0x4c
946eecfc 805bc415 e2a9c120 8a89d038 0000020c nt!ObpCloseHandleTableEntry+0x155
946eed44 805bc54d 0000020c 00000001 00000000 nt!ObpCloseHandle+0x87
946eed58 8054167c 0000020c 0351fdd8 7c90e514 nt!NtClose+0x1d
946eed58 7c90e514 0000020c 0351fdd8 7c90e514 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0351fdd8 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiRemovePageByColor+a5
80522757 891c01          mov     dword ptr [ecx+eax],ebx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiRemovePageByColor+a5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d00d46f

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiRemovePageByColor+a5

BUCKET_ID:  0xA_nt!MiRemovePageByColor+a5

Followup: MachineOwner
---------



usunąłem starą mozille, wyczyściłem rejestr z jej resztek i zainstalowałem nową. Teraz odepnę jedną kość i spróbuje chkdsk zrobić.

Chkdsk C dobiegł bezproblemowo do końca na jednej kości.

[cosik_ktosik]

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

Tamten skubaniec nadal oznacza błąd z pamięcią.

[konto_usuniete]

Proponuje przetestować kompa na jednej kości, a później na drugiej i zobaczyć czy będą Blue screeny ?

[advaldo]

Tak właśnie robię. Jak na razie bezproblemowo działa komputer.