Komputer czasem przy starcie wyrzuca BSOD, w zasadzie nie częściej niż raz na tydzień. Do komputera podpięty jest tylko jeden dysk.
Cały dysk przeskanowałem Malwarebytes (zero zagrożeń) i wyczyściłem z problemów w rejestrze (Glary Utilities), a potem na dokładkę usunąłem pliki tmp i zdefragmentowałem systemowym narzędziem. Nie sądzę jednak aby jakakolwiek moja dotychczasowa akcja wpłynęła na problem, dlatego proszę o weryfikacją dwóch ostatnich minidumpów. Z tego co widzę problem jest w sprzęcie, ale na inne informacje jestem chyba ślepy
. Oto minidumpy:BSOD z dnia 27 stycznia
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\Mini011612-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.111025-1629
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b240
Debug session time: Mon Jan 16 09:50:10.246 2012 (GMT+1)
System Uptime: 0 days 0:01:34.832
Loading Kernel Symbols
...............................................................
............................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000C5, {4, 2, 1, 8054bc34}
Probably caused by : ntoskrnl.exe ( nt!ExAllocatePoolWithTag+673 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8054bc34, address which referenced memory
Debugging Details:
------------------
BUGCHECK_STR: 0xC5_2
CURRENT_IRQL: 2
FAULTING_IP:
nt!ExAllocatePoolWithTag+673
8054bc34 897104 mov dword ptr [ecx+4],esi
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: chrome.exe
LAST_CONTROL_TRANSFER: from 804e6bfc to 8054bc34
STACK_TEXT:
f38b3c08 804e6bfc 00000008 00000001 34344d43 nt!ExAllocatePoolWithTag+0x673
f38b3c2c 80594028 00000008 0000000c 34344d43 nt!ExAllocatePoolWithQuotaTag+0x46
f38b3c4c 80594159 00000002 00010000 00000000 nt!CmpAllocatePostBlock+0x4c
f38b3cfc 80593fd6 00000124 00000000 00000000 nt!NtNotifyChangeMultipleKeys+0x293
f38b3d34 804de7ec 00000124 00000128 00000000 nt!NtNotifyChangeKey+0x2c
f38b3d34 7c90e514 00000124 00000128 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012ef14 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExAllocatePoolWithTag+673
8054bc34 897104 mov dword ptr [ecx+4],esi
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExAllocatePoolWithTag+673
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ea6ba87
FAILURE_BUCKET_ID: 0xC5_2_nt!ExAllocatePoolWithTag+673
BUCKET_ID: 0xC5_2_nt!ExAllocatePoolWithTag+673
Followup: MachineOwner
---------BSOD z dnia 16 stycznia
Kod: Zaznacz cały
Loading Dump File [C:\WINDOWS\Minidump\Mini012712-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.111025-1629
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b240
Debug session time: Fri Jan 27 08:24:24.523 2012 (GMT+1)
System Uptime: 0 days 0:00:30.113
Loading Kernel Symbols
...............................................................
...................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, f6f2ef7f, f5d4b4f0, 0}
Probably caused by : hardware ( mouhid!MouHid_Create+139 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: f6f2ef7f, The address that the exception occurred at
Arg3: f5d4b4f0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {WYJ
FAULTING_IP:
mouhid!MouHid_Create+139
f6f2ef7f ff ???
TRAP_FRAME: f5d4b4f0 -- (.trap 0xfffffffff5d4b4f0)
ErrCode = 00000000
eax=861a2810 ebx=862e6df8 ecx=862e6e58 edx=862e6e58 esi=00000103 edi=00000000
eip=f6f2ef7f esp=f5d4b564 ebp=f5d4b588 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
mouhid!MouHid_Create+0x139:
f6f2ef7f ff ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: csrss.exe
MISALIGNED_IP:
mouhid!MouHid_Create+139
f6f2ef7f ff ???
LAST_CONTROL_TRANSFER: from 804e3807 to f6f2ef7f
FAILED_INSTRUCTION_ADDRESS:
mouhid!MouHid_Create+139
f6f2ef7f ff ???
STACK_TEXT:
f5d4b588 804e3807 862e6e54 861ea9a8 00000000 mouhid!MouHid_Create+0x139
f5d4b598 f7b2953f 861eab30 8618b0e8 e1040701 nt!IopfCallDriver+0x31
f5d4b5b8 f7b275f7 862e6d40 861ea9a8 00000000 mouclass!MouseSendIrpSynchronously+0x59
f5d4b5e8 f7b27d55 00000001 861ea9a8 8618b0e8 mouclass!MouEnableDisablePort+0x61
f5d4b624 804e3807 8618b030 861ea9a8 861ea9a8 mouclass!MouseClassCreate+0x1dd
f5d4b634 8056f1b5 8625f018 8622c854 f5d4b7dc nt!IopfCallDriver+0x31
f5d4b714 8056406c 8625f030 00000000 8622c7b0 nt!IopParseDevice+0xa12
f5d4b79c 805686ea 00000000 f5d4b7dc 00000040 nt!ObpLookupObjectName+0x56a
f5d4b7f0 8056f68f 00000000 00000000 d4b86c00 nt!ObOpenObjectByName+0xeb
f5d4b86c 8056f75e e17d4bdc 00100001 f5d4b9ec nt!IopCreateFile+0x407
f5d4b8c8 8056f894 e17d4bdc 00100001 f5d4b9ec nt!IoCreateFile+0x8e
f5d4b908 804de7ec e17d4bdc 00100001 f5d4b9ec nt!NtCreateFile+0x30
f5d4b908 804dc9b1 e17d4bdc 00100001 f5d4b9ec nt!KiFastCallEntry+0xf8
f5d4b9ac bf881c6f e17d4bdc 00100001 f5d4b9ec nt!ZwCreateFile+0x11
f5d4ba0c bf881bd6 00000000 804e3a1d e162b2c0 win32k!OpenDevice+0xd4
f5d4ba40 bf80a43f 00000000 bf9ae340 e162b2c0 win32k!ProcessDeviceChanges+0xa8
f5d4ba5c bf87ebe4 00000002 86194508 bf881b49 win32k!xxxMsgWaitForMultipleObjects+0x8d
f5d4bd30 bf8b8f76 bf9ae340 00000001 f5d4bd54 win32k!xxxDesktopThread+0x339
f5d4bd40 bf8010dd bf9ae340 f5d4bd64 0077fff4 win32k!xxxCreateSystemThreads+0x6a
f5d4bd54 804de7ec 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f5d4bd54 7c90e514 00000000 00000022 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
mouhid!MouHid_Create+139
f6f2ef7f ff ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: mouhid!MouHid_Create+139
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED_mouhid.sys
BUCKET_ID: IP_MISALIGNED_mouhid.sys
Followup: MachineOwner
---------Pozdrawiam!
I dziękuję za to, że zawsze można tu uzyskać pomoc
.
