|
|
|
|
| Компьютерный форум OSzone.net » Железо » Непонятные проблемы с Железом » Спонтанные перезагрузки, частые зависания |
|
|
Спонтанные перезагрузки, частые зависания
|
|
Новый участник Сообщения: 23 |
Купил новое железо - начались проблемы
Довольно часто случаются спонтанные перезагрузки либо просто виснет наглухо. Мышь, намлок не реагируют. Звук циклируется (если он был включен). Просто при работе иногда вылазит бсод, дампы прилагаю. Но пологаю что эти бсоды из за чего-то другого. Конфиг: DualCore AMD Athlon 64 X2, 2900 MHz (14.5 x 200) 5600+ Asus M2N-E (3 PCI, 2 PCI-E x1, 1 PCI-E x4, 1 PCI-E x16, 4 DDR2 DIMM, Audio, Gigabit LAN) PALIT NVIDIA GeForce 8600 GTS (256 mb) 2хDIMM2: OCZ XTC Platinum OCZ2P10001G БП 450 3 винта Винты, корпус и видяха от старого компа (там все ок) на видеокарте при переезде только заменил вентилятор на покруче Перегрева нет, температура отличная. Обновил дрова на видяху, енфорс - Не помогает  Когда писал этот пост - завис При зависании пробовал открывать лоток сидюка... - работает. Если бы были бсоды тогда все можно было понять из логов...а так...Идей уже нет Код:
 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: 71a5df52, memory referenced Arg2: 00000002, IRQL Arg3: 00000008, value 0 = read operation, 1 = write operation Arg4: 71a5df52, address which referenced memory Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* MODULE_NAME: nt FAULTING_MODULE: 804d7000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 45e5484a READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 71a5df52 CURRENT_IRQL: 2 FAULTING_IP: +71a5df52 71a5df52 ?? ??? DEFAULT_BUCKET_ID: WRONG_SYMBOLS BUGCHECK_STR: 0xD1 LAST_CONTROL_TRANSFER: from 71a5df52 to 80543a70 FAILED_INSTRUCTION_ADDRESS: +71a5df52 71a5df52 ?? ??? STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. af21ad64 71a5df52 badb0d00 7c90eb94 00000000 nt!Kei386EoiHelper+0x2834 af21ad68 badb0d00 7c90eb94 00000000 00000000 0x71a5df52 af21ad6c 7c90eb94 00000000 00000000 00000000 0xbadb0d00 af21ad70 00000000 00000000 00000000 00000000 0x7c90eb94 STACK_COMMAND: kb FOLLOWUP_IP: nt!Kei386EoiHelper+2834 80543a70 f7457000000200 test dword ptr [ebp+70h],20000h SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!Kei386EoiHelper+2834 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntkrpamp.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- Код:
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {2621e, 1c, 0, 805444c7}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : AmdK8.sys ( AmdK8+3552 )
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: 0002621e, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, 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: 805444c7, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
MODULE_NAME: AmdK8
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4496462b
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0002621e
CURRENT_IRQL: 1c
FAULTING_IP:
nt+6d4c7
805444c7 ff80c4050000 inc dword ptr [eax+5C4h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from ba99b552 to 805444c7
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
805503c0 ba99b552 badb0d00 00000001 00000000 nt+0x6d4c7
80550450 805450cc 00000000 0000000e 00000000 AmdK8+0x3552
80550454 00000000 0000000e 00000000 00000000 nt+0x6e0cc
STACK_COMMAND: kb
FOLLOWUP_IP:
AmdK8+3552
ba99b552 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: AmdK8+3552
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: AmdK8.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
|
|
|
Отправлено: 23:41, 15-04-2008 |
Старожил Сообщения: 485
|
Профиль | Отправить PM | Цитировать попробуй помудрить что-то с драйверами(даж не знаю что посоветовать,скорее всего поставить все с диска),и проверить память мемтестом...или для проверки поставить какую-нибудь другую ось...
|
|
Отправлено: 00:08, 16-04-2008 | #2 |
|
Новый участник Сообщения: 15
|
Профиль | Отправить PM | Цитировать перегревается проц или что-то с оперативной памятью
|
|
Отправлено: 00:10, 16-04-2008 | #3 |
Ветеран Сообщения: 2686
|
Профиль | Отправить PM | Цитировать Цитата i can help you:
назови сколько лет БП и его модель так же возможно твоя материнка начинает поддерживать установленный процессор начиная с какой то более новой версии биос, например M2N-E в версиях биос 0203 - 0802 вводится поддержка новых процессоров проверьте свою версию биос на материнской плате и обновитесь последним (1305) поддержка твоего процессора включена с версии 0502 последний можно скачать по ссылке: http://dlsvr01.asus.com/pub/ASUS/mb/...M2N-E/1305.zip суппорт процессоров проверить можно по этой ссылке: http://support.asus.com/cpusupport/c...Language=en-us необходимо выбрать сокет, модель м.б. и посмотреть http://support.asus.com/download/dow...ru&model=M2N-E все последние обновления для M2N-E |
|
|
------- Последний раз редактировалось ShellL, 16-04-2008 в 06:54. Отправлено: 06:40, 16-04-2008 | #4 |
|
Новый участник Сообщения: 23
|
Профиль | Отправить PM | Цитировать Большое спасибо за советы.
проверил с помощью http://testmem.nm.ru/ - все окей Проц не перегревается. блок питания от этого корпуса http://www.jupiter-group.ru/product/...e&flag=2&id=24 Ему от силы 2 месяца. Версия биоса 1202. Сейчас буду перепрошивать но думаю видяха конфликтует, ибо все просто тупо виснет. Бсодов нет. |
|
|
------- Отправлено: 09:44, 16-04-2008 | #5 |
|
Новый участник Сообщения: 23
|
Профиль | Отправить PM | Цитировать почитал что изменили в биосе. Решил не перепрошивать.
Опасно. Думаю дело явно не в этом Поменял видео карту на старую... зависания продолжаются. |
|
------- Отправлено: 10:57, 16-04-2008 | #6 |
|
Новый участник Сообщения: 23
|
Профиль | Отправить PM | Цитировать новый дамп выдали
Код:
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\WINDOWS\Minidump\Mini041608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed Apr 16 15:33:29.656 2008 (GMT+4)
System Uptime: 0 days 0:35:49.373
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...........................................................................................................................
Loading User Symbols
Loading unloaded module list
........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, f7717d70, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : hardware ( nt+9800 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: f7717d70
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
MISALIGNED_IP:
nt+9800
804e0800 4d dec ebp
LAST_CONTROL_TRANSFER: from 00000000 to 804e0800
STACK_TEXT:
af4ae004 00000000 804e01b2 00000008 00010002 nt+0x9800
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+9800
804e0800 4d dec ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+9800
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: f7717d70
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
MISALIGNED_IP:
nt+9800
804e0800 4d dec ebp
LAST_CONTROL_TRANSFER: from 00000000 to 804e0800
STACK_TEXT:
af4ae004 00000000 804e01b2 00000008 00010002 nt+0x9800
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+9800
804e0800 4d dec ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+9800
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
|
|
------- Отправлено: 12:19, 16-04-2008 | #7 |
Ветеран Сообщения: 662
|
Профиль | Отправить PM | Цитировать Цитата i can help you:
|
|
|
------- Отправлено: 15:50, 16-04-2008 | #8 |
|
Новый участник Сообщения: 23
|
Профиль | Отправить PM | Цитировать да я к тому что
при перепрошивке очень велик шанс вне планового ребута. Страшно  |
|
------- Отправлено: 17:26, 16-04-2008 | #9 |
|
Ветеран Сообщения: 662
|
Профиль | Отправить PM | Цитировать Включи комп и зайди в БИОС. Ничего не делай и подожди так минут 10. Можно повторить так раза 3. Если в во время нахождения в БИОСе ребута не будет, то можешь смело перепрошивать. Перепрошивается секунд за 20-30.
|
|
------- Отправлено: 17:42, 16-04-2008 | #10 |
|
Участник сейчас на форуме |
 |
Участник вне форума |
 |
Автор темы |
 |
Сообщение прикреплено |
| |||||
| Название темы | Автор | Информация о форуме | Ответов | Последнее сообщение | |
| [решено] Периодические зависания и перезагрузки ПК | Comrade_Zhukov | Непонятные проблемы с Железом | 4 | 17-10-2009 11:49 | |
| Разное - несистематичные перезагрузки и зависания | Лисси | Microsoft Windows 2000/XP | 14 | 14-05-2009 16:17 | |
| Спонтанные перезагрузки в играх | i can help you | Непонятные проблемы с Железом | 16 | 15-08-2008 11:48 | |
| Частые зависания компьютера (только UT 2k4 и FarCry) | FREEm4n | Непонятные проблемы с Железом | 15 | 25-04-2004 19:31 | |
|
|
Время: 23:20. | © OSzone.net 2001-
|
|
Powered by: vBulletin Copyright ©2000 - 2024, Jelsoft Enterprises Ltd. |
