Здравствуйте!
Вобщем компьютер и раньше мне показывал bsod'ы, решалось это полной переустановкой винды.
Но сегодня ночью я был в шоке: 4 синих экрана за час!
Решил не переустанавливать винду(нудный и долгий процесс), решил посоветоваться со специалистами.
Вот собственно я и тут
Читал эту тему и раньше, память в мемтесте гонял - сбоев нет, перегрева нет,HDD - ошибок нет, БП слабоват немного но это не мешает работать без БСОДов свежей системе месяца 2 в режиме 24/7.
Бегло посмотрел дампы - 3 из за Скайпа, 1 из за Аваста.
Один из дампов на скайп:
читать дальше »
Код:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini062010-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Jun 20 02:30:49.302 2010 (GMT+4)
System Uptime: 0 days 12:13:01.843
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.............
Unable to load image 347.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for 347.sys
*** ERROR: Module load completed but symbols could not be loaded for 347.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, a93e9d9e, a9832ca0, 0}
Probably caused by : 347.sys ( 347+1d9e )
Followup: MachineOwner
---------
1: 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: c0000005, The exception code that was not handled
Arg2: a93e9d9e, The address that the exception occurred at
Arg3: a9832ca0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
347+1d9e
a93e9d9e f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
TRAP_FRAME: a9832ca0 -- (.trap 0xffffffffa9832ca0)
ErrCode = 00000000
eax=00000090 ebx=07188f40 ecx=00000008 edx=00000050 esi=07193000 edi=07192ee4
eip=a93e9d9e esp=a9832d14 ebp=a9832d2c iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
347+0x1d9e:
a93e9d9e f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: Skype.exe
LAST_CONTROL_TRANSFER: from a93e8d62 to a93e9d9e
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a9832d2c a93e8d62 00000000 07192f04 07192de8 347+0x1d9e
a9832d4c 8054163c 0000000b 07188f40 00009fc4 347+0xd62
a9832d64 7c90e514 badb0d00 0012fb00 aa0f0d98 nt!MiMakeOutswappedPageResident+0xf8
a9832d78 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
347+1d9e
a93e9d9e f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: 347+1d9e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: 347
IMAGE_NAME: 347.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4529809b
FAILURE_BUCKET_ID: 0x8E_347+1d9e
BUCKET_ID: 0x8E_347+1d9e
Followup: MachineOwner
---------
Система:
XP Pro SP 3
Athlon x2 6400+
MB Asus M2R32 MVP
ATI HD4870
Памяти 4GB, 4 планки по 1GB название сейчас уже не вспомню
Если нужна ещё информация - напишите.
Заранее спасибо.
