Częste Blue screeny 0x0000000A

Wszelkie problemy komputerowe, których nie można jednoznacznie sklasyfikować do wybranego działu
konto_usuniete

Częste Blue screeny 0x0000000A

Post15 lip 2011, 15:04

Najpierw wsadź ją w jeden slot, a później drugi i zobacz czy będzie wszystko śmigać, później zrób to samo z drugą. ;)

advaldo

Użytkownik
Posty: 16
Rejestracja: 10 lip 2011, 16:52

Częste Blue screeny 0x0000000A

Post17 lip 2011, 17:06

Pierwszy Bsod od przejścia na jedną pamięć

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\Mini071611-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: Sat Jul 16 22:58:26.843 2011 (GMT+2)
System Uptime: 0 days 11:24:45.794
Loading Kernel Symbols
...............................................................
................................................................

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

Use !analyze -v to get detailed debugging information.

BugCheck C1, {8c656f68, 8c656d9b, 730094, 23}

Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+2f4 )

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

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

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: 8c656f68, address trying to free
Arg2: 8c656d9b, address where bits are corrupted
Arg3: 00730094, (reserved)
Arg4: 00000023, caller is freeing an address where nearby bytes within the same page have been corrupted

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


BUGCHECK_STR:  0xC1_23

SPECIAL_POOL_CORRUPTION_TYPE:  23

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  plugin-containe

LAST_CONTROL_TRANSFER:  from 8066ed94 to 804f9f43

STACK_TEXT: 
a3c78c04 8066ed94 000000c1 8c656f68 8c656d9b nt!KeBugCheckEx+0x1b
a3c78c50 8054b32a 8c656f68 a3c78cd3 89385c88 nt!MmFreeSpecialPool+0x2f4
a3c78c90 806601f6 8c656f68 00000000 80660391 nt!ExFreePoolWithTag+0x4a
a3c78c9c 80660391 0094d000 8c656f68 00000000 nt!VfIrpFree+0xc
a3c78cb8 80659071 0094d004 00000000 a3c78d48 nt!VerifierIoFreeIrp+0x129
a3c78cc8 80579028 8c656f68 a3c78d64 010bfdd4 nt!IovFreeIrpPrivate+0x41
a3c78d48 8054167c 000000c0 010bfe08 010bfdfc nt!NtRemoveIoCompletion+0x12a
a3c78d48 7c90e514 000000c0 010bfe08 010bfdfc nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
010bfde4 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MmFreeSpecialPool+2f4
8066ed94 8b4708          mov     eax,dword ptr [edi+8]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MmFreeSpecialPool+2f4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d00d46f

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xC1_23_nt!MmFreeSpecialPool+2f4

BUCKET_ID:  0xC1_23_nt!MmFreeSpecialPool+2f4

Followup: MachineOwner

Awatar użytkownika
cosik_ktosik

Administrator
Posty: 21416
Rejestracja: 13 lis 2008, 01:17
Lokalizacja: Szczecin
Kontaktowanie:

Częste Blue screeny 0x0000000A

Post18 lip 2011, 00:26

Kicha, nadal pamięć, zobacz na drugim module.
Hotfix
Pozdrawiam, cosik_ktosik :)

advaldo

Użytkownik
Posty: 16
Rejestracja: 10 lip 2011, 16:52

Częste Blue screeny 0x0000000A

Post20 lip 2011, 19:03

nowy bsod 4E:

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\Mini072011-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: Wed Jul 20 18:58:42.046 2011 (GMT+2)
System Uptime: 0 days 2:35:03.994
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 28e7e, 0, 0}

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

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

3: 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: 00028e7e, page frame number
Arg3: 00000000, current page state
Arg4: 00000000, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  services.exe

LAST_CONTROL_TRANSFER:  from 80522dfc to 804f9f43

STACK_TEXT: 
a7343ba8 80522dfc 0000004e 00000099 00028e7e nt!KeBugCheckEx+0x1b
a7343bd8 80511a75 c0884034 000000ce 8a33ecf8 nt!MiDecrementShareCount+0x3a
a7343bfc 805b0287 01001221 8a33eb00 007ffff8 nt!MiDeleteValidAddress+0x177
a7343c1c 80513517 8a33eb00 8a33ec38 8a33eb00 nt!MiDeleteAddressesInWorkingSet+0x65
a7343c50 805d274a 0033eb00 8908b190 c0000005 nt!MmCleanProcessAddressSpace+0x193
a7343cf0 805d282d c0000005 a7343d4c 804ff94f nt!PspExitThread+0x680
a7343cfc 804ff94f 8908b190 a7343d48 a7343d3c nt!PsExitSpecialApc+0x23
a7343d4c 805416e7 00000001 00000000 a7343d64 nt!KiDeliverApc+0x1af
a7343d4c 7c90e514 00000001 00000000 a7343d64 nt!KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following frames may be wrong.
00c3fed8 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
---------



Cały czas w pierwszym położeniu jednej pamięci.

Awatar użytkownika
cosik_ktosik

Administrator
Posty: 21416
Rejestracja: 13 lis 2008, 01:17
Lokalizacja: Szczecin
Kontaktowanie:

Częste Blue screeny 0x0000000A

Post24 lip 2011, 10:16

I cały czas to jest wskazanie pamięci, może pożycz od kogoś inną?
Hotfix
Pozdrawiam, cosik_ktosik :)



  • Reklama

Wróć do „Problemy”



Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 225 gości