Зависает Microsoft Windows 7 (7600) x32 rus Ultimate

[Djus]

Компьютер:
Тип компьютера ACPI компьютер на базе x86 (Mobile)
Операционная система Microsoft Windows 7 Ultimate
Пакет обновления ОС -
Internet Explorer 8.0.7600.16385
DirectX DirectX 11.0

Системная плата:
Тип ЦП Mobile DualCore AMD Turion 64 X2 TL-58, 1900 MHz (9.5 x 200)
Системная плата Toshiba Satellite A210
Чипсет системной платы AMD 690V, AMD Hammer
Системная память 2048 Мб (DDR2-667 DDR2 SDRAM)
DIMM1: Samsung M4 70T2953EZ3-CE6 1 Гб DDR2-667 DDR2 SDRAM (5-5-5-15 @ 333 МГц) (4-4-4-12 @ 266 МГц) (3-3-3-9 @ 200 МГц)
DIMM2: Samsung M4 70T2953EZ3-CE6 1 Гб DDR2-667 DDR2 SDRAM (5-5-5-15 @ 333 МГц) (4-4-4-12 @ 266 МГц) (3-3-3-9 @ 200 МГц)
Тип BIOS Phoenix (06/10/08)
Коммуникационный порт BT Port (COM15)
Коммуникационный порт BT Port (COM16)
Коммуникационный порт BT Port (COM17)
Коммуникационный порт BT Port (COM18)
Коммуникационный порт BT Port (COM19)
Коммуникационный порт BT Port (COM20)
Коммуникационный порт BT Port (COM21)
Коммуникационный порт BT Port (COM22)
Коммуникационный порт BT Port (COM6)
Коммуникационный порт BT Port (COM7)

Отображение:
Видеоадаптер ATI Mobility Radeon HD 2600 (256 Мб)
Видеоадаптер ATI Mobility Radeon HD 2600 (256 Мб)
3D-акселератор ATI Mobility Radeon HD 2600 (M76M)
Монитор LG Philips LP154WX4-TLD2 [15.4" LCD]

Мультимедиа:
Звуковой адаптер ATI Radeon HDMI @ ATI Radeon HD 2600 - High Definition Audio Controller
Звуковой адаптер Realtek ALC268 @ ATI SB600 - High Definition Audio Controller

Хранение данных:
Контроллер IDE Texas Instruments PCIxx12 Integrated FlashMedia Controller
Контроллер IDE Стандартный двухканальный контроллер PCI IDE
Контроллер IDE Стандартный двухканальный контроллер PCI IDE
Дисковый накопитель Hitachi HTS541616J9SA00 ATA Device (160 Гб, 5400 RPM, SATA)
Оптический накопитель MATSHITA DVD-RAM UJ-850S ATA Device (DVD+R9:4x, DVD-R9:4x, DVD+RW:8x/8x, DVD-RW:8x/6x, DVD-RAM:5x, DVD-ROM:8x, CD:24x/16x/24x DVD+RW/DVD-RW/DVD-RAM)
Статус SMART жёстких дисков OK

Ввод:
Клавиатура Стандартная клавиатура PS/2
Мышь A4Tech USB Port Mouse
Мышь Synaptics PS/2 Port TouchPad

Сеть:
Сетевой адаптер Atheros AR5007EG Wireless Network Adapter (192.168.1.134)
Модем TOSHIBA Software Modem

Периферийные устройства:
Принтер Fax
Принтер Microsoft XPS Document Writer
Контроллер FireWire Texas Instruments OHCI Compliant IEEE 1394 Host Controller (PHY: TI TSB41AB1/2)
Контроллер USB1 ATI SB600 - OCHI USB Controller
Контроллер USB1 ATI SB600 - OCHI USB Controller
Контроллер USB1 ATI SB600 - OCHI USB Controller
Контроллер USB1 ATI SB600 - OCHI USB Controller
Контроллер USB1 ATI SB600 - OCHI USB Controller
Контроллер USB2 ATI SB600 - EHCI USB 2.0 Controller
USB-устройство USB-видеоустройство
USB-устройство USB-устройство ввода
USB-устройство Составное USB устройство
Батарея Адаптер блока питания (Microsoft)
Батарея Батарея с ACPI-совместимым управлением (Microsoft)
Батарея Составная батарея (Майкрософт)

DMI:
DMI поставщик BIOS TOSHIBA
DMI версия BIOS V2.00
DMI производитель системы TOSHIBA
DMI система Satellite A210
DMI системная версия PSAELE-01S00FRU
DMI системный серийный номер X7117160K
DMI системный UUID 7447799A-6AEA11DC-AD1B001B-3848CAC5
DMI производитель системной платы TOSHIBA
DMI системная плата IALAA
DMI версия системной платы 1.00
DMI серийный номер системной платы 0123456789AB
DMI производитель шасси TOSHIBA
DMI версия шасси N/A
DMI серийный номер шасси None
DMI Asset-тег шасси *
DMI тип шасси Notebook

На ноуте две винды Winxp и 7 в хп работа стабильна нареканий нет. 7 поставил недавно виснет в играх мертво картинка зависает и все не на что не реагирует. Менял дрова на видюху, звук, отключал службы диспетчер\ темы как зависала так и зависает.
последнее что выдала:

Сигнатура проблемы

Имя проблемного события: BlueScreen

Версия ОС: 6.1.7600.2.0.0.256.1

Код языка: 1049

Дополнительные сведения о проблеме

BCCode: 124

BCP1: 00000000

BCP2: 85BF4024

BCP3: 00000000

BCP4: 00000000

OS Version: 6_1_7600

Service Pack: 0_0

Product: 256_1

Код черпака: 0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

Информация сервера: 2ea16db0-fdfc-40c2-96c5-0a8d6d5d83d6


Очень хочетцо победить этот зависание , в остальном 7 устраивает полностью.
ЗЫ: точно не перегрев.(не так давно чистил и менял термопасту)
Зыы:под хп работает как часы.

[Morpheus]

Djus, память тестировали? (http://www.oszone.net/10428/memory_test) Синий экран появляется?

[Djus]

Djus, память тестировали? Синий экран появляется? »
Тестировал тока эверестом ошибок не было, синего экрана не было ни разу( ошибки смотрю в журнале стабильности)
приму любые советы .

[Djus]

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


Loading Dump File [F:\Windows\Minidump\121709-26520-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 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x82c01000 PsLoadedModuleList = 0x82d49810
Debug session time: Thu Dec 17 21:21:33.816 2009 (GMT+3)
System Uptime: 0 days 0:00:09.736
*********************************************************************
* 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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 85bf8024, 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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

Followup: MachineOwner
---------
Щаз попробую потестить память с помощью Windows Memory Diagnostic
потестил ошибок не обноружено
потестил еще Memtest86 ошибок нет, жесткий тоже проверил все нормально

[Djus]

Вот что пишет BlueScreenView, дамп прикрепил на всякий
hal.dll hal.dll+5ba9 0x83011000 0x83048000 0x00037000 0x4a5bbf07 14.07.2009 2:11:03 Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation F:\Windows\system32\hal.dll

ntoskrnl.exe ntoskrnl.exe+cefc5 0x82c01000 0x83011000 0x00410000 0x4a5bc007 14.07.2009 2:15:19 Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation F:\Windows\system32\ntoskrnl.exe

[Djus]

2 дня полет нормальный правдо не понял что помогло , после последнего зависания поставил дрова на видюху 9.12 каталист(пришлось модифицировать под ноут благо там все просто) и отключил qip infium, два дня не показатель конечно посмотрим что будет дальше. по поводу дампа который создавался он походу не причем, как я понял такой дамп возникал из за того что приходилось ноут выключать.
=============================================


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