Спонтанные перезагрузки, частые зависания

[i can help you]

Купил новое железо - начались проблемы

Довольно часто случаются спонтанные перезагрузки либо просто виснет наглухо. Мышь, намлок не реагируют. Звук циклируется (если он был включен).

Просто при работе иногда вылазит бсод, дампы прилагаю. Но пологаю что эти бсоды из за чего-то другого.

Конфиг:

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
---------

[spellozz]

попробуй помудрить что-то с драйверами(даж не знаю что посоветовать,скорее всего поставить все с диска),и проверить память мемтестом...или для проверки поставить какую-нибудь другую ось...

[rom2008]

перегревается проц или что-то с оперативной памятью

[ShellL]

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 винта »
какой блок питания - если noname то его мощности реально не хватает для твоей конфигурации
назови сколько лет БП и его модель
так же возможно твоя материнка начинает поддерживать установленный процессор начиная с какой то более новой версии биос, например
M2N-E в версиях биос 0203 - 0802 вводится поддержка новых процессоров
проверьте свою версию биос на материнской плате и обновитесь последним (1305)
поддержка твоего процессора включена с версии 0502
последний можно скачать по ссылке:
http://dlsvr01.asus.com/pub/ASUS/mb/socketAM2/M2N-E/1305.zip
суппорт процессоров проверить можно по этой ссылке: http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us
необходимо выбрать сокет, модель м.б. и посмотреть
http://support.asus.com/download/download.aspx?SLanguage=ru-ru&model=M2N-E
все последние обновления для M2N-E

[i can help you]

Большое спасибо за советы.
проверил с помощью http://testmem.nm.ru/ - все окей

Проц не перегревается.

блок питания от этого корпуса
http://www.jupiter-group.ru/product/?menu=Case&flag=2&id=24
Ему от силы 2 месяца.

Версия биоса 1202.
Сейчас буду перепрошивать

но думаю видяха конфликтует, ибо все просто тупо виснет. Бсодов нет.

[i can help you]

почитал что изменили в биосе. Решил не перепрошивать.
Опасно. Думаю дело явно не в этом

Поменял видео карту на старую... зависания продолжаются.
:( :( :(

[i can help you]

новый дамп выдали


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
---------

[Grub]

почитал что изменили в биосе. Решил не перепрошивать.
Опасно. Думаю дело явно не в этом »
Лучше перепрошить. Многие проблемы исчезают после перепрошивки. На сайте асуса все подробно описано как перепрошивать. Делается за минуту.

[i can help you]

да я к тому что
при перепрошивке очень велик шанс вне планового ребута.
Страшно :)

[Grub]

Включи комп и зайди в БИОС. Ничего не делай и подожди так минут 10. Можно повторить так раза 3. Если в во время нахождения в БИОСе ребута не будет, то можешь смело перепрошивать. Перепрошивается секунд за 20-30.

[i can help you]

Спасибо. Так и сделаю

Но, тут обнаружил что нужен флоп для перепрошивки... которого у меня нет.
:(

[Grub]

Но, тут обнаружил что нужен флоп для перепрошивки... которого у меня нет. »
попроси у знакомых, друзей, соседа и т.д. Можно купить б\у - что совсем дешево было, можно новый чтоб дешево, но уж не так :)

[yurfed]

i can help you, Type referenced: nt!_KPRCB ни что иное как Processor Control Block
Установи драйвера http://www.nix.ru/download_drivers_bios_firmware_manual_list.html?good_id=61594

[i can help you]

поставил все это
Изменений нет
зато есть новый дамп:
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: a54e20b1, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: a54e20b1, 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: NDIS

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41107ec3

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
a54e20b1

CURRENT_IRQL: 1c

FAULTING_IP:
+ffffffffa54e20b1
a54e20b1 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 00000000 to a54e20b1

FAILED_INSTRUCTION_ADDRESS:
+ffffffffa54e20b1
a54e20b1 ?? ???

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffffb060bde8

STACK_COMMAND: dds B060BDE8-0x20 ; kb

STACK_TEXT:
b060bdc8 00000000
b060bdcc 7c90eb94
b060bdd0 0000001b
b060bdd4 00200202
b060bdd8 0012f708
b060bddc 00000023
b060bde0 804ec791 nt+0x15791
b060bde4 f7411b85 NDIS+0x6b85
b060bde8 8897d400
b060bdec 00000000
b060bdf0 0020027f
b060bdf4 7c910000
b060bdf8 00000000
b060bdfc 00000000
b060be00 00000000
b060be04 00000000
b060be08 00001fa0
b060be0c 0000ffff
b060be10 895ebb00
b060be14 e35771f0
b060be18 0000ba34
b060be1c 00000000
b060be20 e35771f0
b060be24 00000004
b060be28 00003af2
b060be2c 00000000
b060be30 bf82327c win32k+0x2327c
b060be34 bc69e548
b060be38 000078a8
b060be3c 00000000
b060be40 0000038c
b060be44 e3bb0848


FOLLOWUP_IP:
NDIS+6b85
f7411b85 ?? ???

SYMBOL_NAME: NDIS+6b85

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: NDIS.sys

BUCKET_ID: WRONG_SYMBOLS

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

[ShellL]

выложи сами дампы несколько штук

по блоку питания, какой у вас из 3х - 6XR8/450(2.2), 6XR8/500(2.01) или 6XR8-PE/600(2.2)
хотя все три порядочные

[i can help you]

http://ifolder.ru/6196035
последние дампы.
(дампы делаются только в процентах 10 случаев. Когда есть бсод)

БП у меня на 450


Вчера тестил другой бп, проверенный на 350 правда. Эффект тот же

[gf100]

i can help you, я от похожей напасти избавился заменив шнурок SATA к диску... Я думаю, есть смысл погонять систему только с одним диском заменив ему интерфейсный шнур...

[yurfed]

Mini041708-02.dmp
Crash date: Thu Apr 17 09:20:53.828 2008 (GMT+4)
Stop error code: 0x7f_8
Probably caused by: ntoskrnl.exe ( nt+98f0 )

Mini041708-01.dmp
Crash date: Thu Apr 17 01:53:03.015 2008 (GMT+4)
Stop error code: 0xD1
Probably caused by: win32k.sys ( win32kGreCombineRgn+202 )

Mini041608-01.dmp
Crash date: Wed Apr 16 15:33:29.656 2008 (GMT+4)
Stop error code: 0x7f_8
Probably caused by: hardware ( nt+9800 )

Mini041508-02.dmp
Crash date: Tue Apr 15 18:32:24.593 2008 (GMT+4)
Stop error code: 0xD1
Probably caused by: ntkrpamp.exe ( ntKiTrap0E+238 )
[/QUOTE]

По ошибке 0xD1 (http://forum.oszone.net/thread-80297.html)
По ошибке 0x7f (http://support.microsoft.com/kb/137539/ru)
Протестируй всё железо стресс-тестом, с помощью S&M (http://www.overclockers.ru/softnews/27810.shtml)

[i can help you]

я это уже делал. 2 раза. Все окей.

[spellozz]

http://support.asus.com/download/download_item.aspx?product=1&model=M2N-E&SLanguage=ru-ru
раздел BIOS.скачиваем последнюю версию,потом залезаем в раздел Утилиты.Далее ищем ASUS Update V7.13.04.(Сервер у них бывает лагает,поэтому эту порграмму можно спокойно скачать с другого источника и другой версии,например 7.13.02).Опять качаем,устанавливаем.Запускаем,выбираем Update BIOS from file.Выбираем файл биоса 1305.rom,и обновляем из Windows.Обновление занимает секунд 30...если боитесь внепланового рестарта то лучше это сделать сразу же после загрузки системы.
Желаю удачи!;)

IMAGE_NAME: NDIS.sys »
Это NDIS wrapper driver.
NDIS позволяет транспортным протоколам, таким как TCP/IP взаимодействовать с нижестоящими протоколами устройства (например сетевой карты) чтобы они могли посылать данные по сети. NDIS Wrapper представляет стандартный интерфейс между драйверами протоколов и драйверами NDIS-устройств.
Попробуй переставить драйверы сетевой карты и модема