thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: BSOD przy normalnej pracy
Jakie masz pamięci ram ?
Podmień sobie od kogoś choć jedną kostkę.
Po tym co piszesz wydaje mi się, że płyta już umiera. Nie wygląda mi to na symptom tzw "dual boot" - http://www.frazpc.pl/b/215696
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Documents and Settings\test.TEST-9EA607EDC7\Pulpit\mini110811_01_www.przeklej.pl.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \Symbols*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.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Nov 8 22: 21: 26.203 2011 (UTC + 1: 00)
System Uptime: 0 days 0: 00: 35.921
Loading Kernel Symbols
...............................................................
....................................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {8ace2624, 1, 8054b10f, 0}
Could not read faulting driver name
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+109 )
Followup: Pool_corruption
---------
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: 8ace2624, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8054b10f, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: 8ace2624
FAULTING_IP:
nt!ExDeferredFreePool+109
8054b10f 895f04 mov dword ptr [edi+4],ebx
MM_INTERNAL_CODE: 0
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: services.exe
LAST_CONTROL_TRANSFER: from 8054b75f to 8054b10f
STACK_TEXT:
b916c8f0 8054b75f 00000001 8a4a91d8 89dcdf30 nt!ExDeferredFreePool+0x109
b916c930 805bfeb6 e108c750 00000000 b916c96c nt!ExFreePoolWithTag+0x47f
b916c940 805c022e e108c750 b916c901 00000000 nt!ObReleaseObjectSecurity+0x1a
b916c96c 8062ebde e1cf41f0 89dcdf30 00000001 nt!ObCheckObjectAccess+0xd6
b916c9b8 8062f468 e1037008 00002d80 00000000 nt!CmpDoOpen+0x256
b916cbb0 805bf444 00002d80 00000000 89dcdf30 nt!CmpParseKey+0x558
b916cc28 805bb9d0 00000000 b916cc68 00000040 nt!ObpLookupObjectName+0x53c
b916cc7c 80624d07 00000000 8a4a9198 e1715901 nt!ObOpenObjectByName+0xea
b916cd50 8054161c 00aff5c8 00000001 00aff51c nt!NtOpenKey+0x1af
b916cd50 7c90e4f4 00aff5c8 00000001 00aff51c nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00aff55c 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExDeferredFreePool+109
8054b10f 895f04 mov dword ptr [edi+4],ebx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExDeferredFreePool+109
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: 0x50_nt!ExDeferredFreePool+109
BUCKET_ID: 0x50_nt!ExDeferredFreePool+109
Followup: Pool_corruption
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Documents and Settings\test.TEST-9EA607EDC7\Pulpit\mini110911_01_www.przeklej.pl.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \Symbols*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.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Nov 9 08: 55: 54.156 2011 (UTC + 1: 00)
System Uptime: 0 days 0: 00: 52.875
Loading Kernel Symbols
...............................................................
...................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, cd4, 30d0000, 8952a008}
Unable to load image aswMon2.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : aswMon2.SYS ( aswMon2+5bea )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 030d0000, Memory contents of the pool block
Arg4: 8952a008, Address of the block of pool being deallocated
Debugging Details:
------------------
POOL_ADDRESS: 8952a008
FREED_POOL_TAG: nMvA
BUGCHECK_STR: 0xc2_7_nMvA
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: DTLite.exe
LAST_CONTROL_TRANSFER: from 8054b583 to 804f9f33
STACK_TEXT:
b0fd290c 8054b583 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
b0fd295c b1507bea 8952a008 00000000 895c745f nt!ExFreePoolWithTag+0x2a3
WARNING: Stack unwind information not available. Following frames may be wrong.
b0fd2978 804f16b0 8a478940 895c7480 8952a008 aswMon2+0x5bea
b0fd29a8 b7ed5785 b0fd29c8 b7ed57d0 895c72a8 nt!IopfCompleteRequest+0xa2
b0fd29b0 b7ed57d0 895c72a8 00000000 00000000 fltMgr!FltpCompleteRequest+0x2d
b0fd29c8 b7ed5f2f 89543008 00000000 895c72a8 fltMgr!FltpSynchronizeIoCleanup+0x42
b0fd29f0 b7ee2754 b0fd2a10 00000000 00000000 fltMgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x29f
b0fd2a2c 804ef18f 89ab0d88 895c72a8 895c74a4 fltMgr!FltpCreate+0x26a
b0fd2a3c b1508c07 895c72b8 8a338830 89542be0 nt!IopfCallDriver+0x31
b0fd2a60 b1502a34 8a478940 895c72a8 b0fd2b60 aswMon2+0x6c07
b0fd2a70 804ef18f 8a478940 895c72a8 895c72a8 aswMon2+0xa34
b0fd2a80 805831fa 8a5e4018 89554a5c b0fd2c18 nt!IopfCallDriver+0x31
b0fd2b60 805bf444 8a5e4030 00000000 895549b8 nt!IopParseDevice+0xa12
b0fd2bd8 805bb9d0 00000000 b0fd2c18 00000040 nt!ObpLookupObjectName+0x53c
b0fd2c2c 80576033 00000000 00000000 00000001 nt!ObOpenObjectByName+0xea
b0fd2ca8 805769aa 0012f5bc 00100020 0012f574 nt!IopCreateFile+0x407
b0fd2d04 8057a1a9 0012f5bc 00100020 0012f574 nt!IoCreateFile+0x8e
b0fd2d44 8054161c 0012f5bc 00100020 0012f574 nt!NtOpenFile+0x27
b0fd2d44 7c90e4f4 0012f5bc 00100020 0012f574 nt!KiFastCallEntry+0xfc
0012f808 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
aswMon2+5bea
b1507bea ? ?
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: aswMon2+5bea
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswMon2
IMAGE_NAME: aswMon2.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4e668445
FAILURE_BUCKET_ID: 0xc2_7_nMvA_aswMon2+5bea
BUCKET_ID: 0xc2_7_nMvA_aswMon2+5bea
Followup: MachineOwner
---------
Reszta błędów identyczna.
![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
(Ten post był ostatnio modyfikowany: 09.11.2011 13:26 przez thermalfake.)
09.11.2011 12:58
|
Post: #5
