Компьютерный форум - После 10 минут игры компьютер перезагружается....

Компьютерный форум (http://pchelpforum.ru/index.php)

- Windows XP (http://pchelpforum.ru/forumdisplay.php?f=34)

После 10 минут игры компьютер перезагружается....

Добрый день!
После примерно 10 минут игры, на мгновение появляется синий экран и компьютер перезагружается, на синим экране прочитать что либо не возможно, очень быстро это происходит.
После перезагрузки, появляется окно ошибки. ОТПРАВИТЬ НЕ ОТПРАВЛЯТЬ

В отчете этого окна вот что пишет.

Цитата:

Подпись ошибки.

BCCode : 1000008e BCP1 : C0000005 BCP2 : BFA82953 BCP3 : B6247770
BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

Файлы которые будут отправлены.
C:\DOCUME~1\57F6~1\LOCALS~1\Temp\WERac91.dir00\Min i080610-01.dmp
C:\DOCUME~1\57F6~1\LOCALS~1\Temp\WERac91.dir00\sys data.xml

Помогите расшифровать

mishanya84, здесь почитайте. Ну или предоставьте файлы минидампа.

Файл минидампа

Цитата:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini080610-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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Aug 6 00:24:05.953 2010 (GMT+4)
System Uptime: 0 days 3:54:23.642
************************************************** *******************
* 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
..................
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bfa82953, b6247770, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** *******************
* 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 : nv4_disp.dll ( nv4_disp+ad953 )

Followup: MachineOwner

Судя по всему проблемы с оперативкой. Попробуйте ее заменить.

---------- Добавлено в 12:44 ---------- Предыдущее сообщение было написано в 12:43 ----------

Или переустановите дрова на видеокарточку.

mishanya84, переставьте дрова на видяху. Сначала в "Безопасном режиме" удалите драйвер. Потом уж переустанавливайте.

У меня дрова не первой свежести, может из за этого
Оперативка эта стояла на Пентиум 4 3000Гц все было великолепно, как сделал абгрейд (заменил материнку, процессор) начались эти проблемы

Цитата:

Сообщение от mishanya84 (Сообщение 275220)

У меня дрова не первой свежести, может из за этого

Ну минидамп указывает на него. Пробуйте разные версии дров, пока не добьетесь стабильной работы.

Обновил дрова, тоже самое:

Цитата:

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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Aug 12 17:51:41.171 2010 (GMT+4)
System Uptime: 0 days 0:12:06.855
************************************************** *******************
* 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
.............
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {891808a8, 879a1580, b84ebcbc, 1}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
************************************************** *******************
* 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+ *
************************************************** *******************
ERROR - could not read driver name for bugcheck parameter 3

************************************************** *******************
* 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 : nv4_disp.dll ( nv4_disp+ec0a0 )

Followup: MachineOwner

mishanya84,у вас наверно винда - сборка.Установите чистую ОС.

да вроде оригинал... Я уж не знаю где её найти такую...

Мне кажется это из за материнки или процессора, потому что эти проблемы появились после апгрейда компьютера, до этого было все хорошо, на любых виндовсах