KirilP Публикувано Юни 30, 2010 Report Share Публикувано Юни 30, 2010 Здравейте, напоследък съм изправен пред следния проблем: когато използвам компютъра само за интернет, скайп, музика и т.н. компютъра си работи нормално, но когато пусна някоя игра се рестартира, ако не веднага то в следващите 15 минути. Първоначално мислех, че проблема е в Windows-a и го преинсталирах, но без резултат...ОС - Microsoft Windows XP Professionalдъно - ECS G31T-Mпроцесор - DualCore Intel Celeron E1400, 2000 MHz (10 x 200)видео карта- Intel® G33/G31 Express Chipset Family ; 256 MBхард диск - SAMSUNG HD322HJ ; 320 GBRAM - 2 GBTjmax температура CPU - 85 °C (185 °F) ; в момента Temperature: CPU #1/ Core 1 - 32*C ; Temperature: CPU #1/ COre 2 - 27*C ; Tеmperature: CPU - 25*C Данните ги копирам от Everest UE, ако трябва да дам още някаква информация кажете...Преди малко изключих опцията компютъра да се рестартира автоматично при "провал" в системата, заредих енда игра и ми излезе следния син екран: http://dc183.4shared.com/img/330098227/495f2e7/013.jpg?rnd=0.799182850067426 Цитирай Link to comment Сподели другаде More sharing options...
snuri Публикувано Юли 1, 2010 Report Share Публикувано Юли 1, 2010 (Редактиран) Изтегли това инсталираш и даваш на анализирай.След това копирай резултата тука.Да нямаш инсталиран флекс тайп?И прикачи dump файла след грешка давидим за какво иде на реч.Всички драйвери актуални ли са?И с тея 85 градуса яйца ли пържиш?Чистил ли си от прах PC-то? Редактиран Юли 1, 2010 от snuri Цитирай Link to comment Сподели другаде More sharing options...
B-boy/StyLe/ Публикувано Юли 1, 2010 Report Share Публикувано Юли 1, 2010 win32k.sys is related to the graphics subsystem... it's more likely a conflict between win32k.sys and the graphics driver, but if you replace the card, you probably end up using a card that has different drivers and hence doesn't cause a problem. * Пробвай да обновиш драйверите за видеокартата. * Също така съществува и рууткит win32k.sys:1 така че е добре да сканираш и за зловреден сорфуер например с Malwarebytes' Anti-Malware 1.46 Цитирай Link to comment Сподели другаде More sharing options...
KirilP Публикувано Юли 1, 2010 Author Report Share Публикувано Юли 1, 2010 Изтегли това инсталираш и даваш на анализирай.След това копирай резултата тука.Да нямаш инсталиран флекс тайп?И прикачи dump файла след грешка давидим за какво иде на реч.Всички драйвери актуални ли са?И с тея 85 градуса яйца ли пържиш?Чистил ли си от прах PC-то?Analysis-------------------------------------------------------------------------------- Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Wed 6/30/2010 7:47:09 PM your computer crashedThis was likely caused by the following module: win32k.sysBugcheck code: 0x1000008E (0xC0000005, 0xBF80234E, 0xBA6FFA90, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_MDump file: C:\WINDOWS\Minidump\Mini063010-04.dmpfile path: C:\WINDOWS\system32\win32k.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Multi-User Win32 DriverThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Wed 6/30/2010 6:42:11 PM your computer crashedThis was likely caused by the following module: win32k.sysBugcheck code: 0x1000008E (0xC0000005, 0x805E4A13, 0xA9154790, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_MDump file: C:\WINDOWS\Minidump\Mini063010-03.dmpfile path: C:\WINDOWS\system32\win32k.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Multi-User Win32 DriverThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Wed 6/30/2010 6:38:24 PM your computer crashedThis was likely caused by the following module: igxpdv32.dllBugcheck code: 0xEA (0x88E3EBD8, 0x88CEB430, 0x88D4F350, 0x1)Error: THREAD_STUCK_IN_DEVICE_DRIVERDump file: C:\WINDOWS\Minidump\Mini063010-02.dmpfile path: C:\WINDOWS\system32\igxpdv32.dllproduct: Intel Graphics Accelerator Drivers for Windows NT®company: Intel Corporationdescription: Component GHAL Driver On Wed 6/30/2010 5:58:23 PM your computer crashedThis was likely caused by the following module: win32k.sysBugcheck code: 0x1000008E (0xC0000005, 0xBF80228F, 0xA81FFC04, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_MDump file: C:\WINDOWS\Minidump\Mini063010-01.dmpfile path: C:\WINDOWS\system32\win32k.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Multi-User Win32 DriverThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Tue 6/29/2010 3:43:27 PM your computer crashedThis was likely caused by the following module: ntoskrnl.exeBugcheck code: 0x10000050 (0xFF000010, 0x0, 0x80595259, 0x0)Error: UnknownDump file: C:\WINDOWS\Minidump\Mini062910-03.dmpfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Tue 6/29/2010 3:31:34 PM your computer crashedThis was likely caused by the following module: ntoskrnl.exeBugcheck code: 0x1000007E (0xC0000005, 0x80583861, 0xF78BEC50, 0xF78BE94C)Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_MDump file: C:\WINDOWS\Minidump\Mini062910-02.dmpfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Tue 6/29/2010 2:29:40 PM your computer crashedThis was likely caused by the following module: win32k.sysBugcheck code: 0x10000050 (0xFFEB1C6B, 0x0, 0xBF81BFD7, 0x0)Error: UnknownDump file: C:\WINDOWS\Minidump\Mini062910-01.dmpfile path: C:\WINDOWS\system32\win32k.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Multi-User Win32 DriverThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Mon 6/28/2010 3:32:13 PM your computer crashedThis was likely caused by the following module: ntoskrnl.exeBugcheck code: 0x1000008E (0xC0000005, 0x8056FD37, 0xA802EAD0, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_MDump file: C:\WINDOWS\Minidump\Mini062810-03.dmpfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Mon 6/28/2010 12:05:43 PM your computer crashedThis was likely caused by the following module: win32k.sysBugcheck code: 0x1000008E (0xC0000005, 0xBF801213, 0xB9C7EA48, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_MDump file: C:\WINDOWS\Minidump\Mini062810-02.dmpfile path: C:\WINDOWS\system32\win32k.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Multi-User Win32 DriverThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Mon 6/28/2010 6:16:46 PM your computer crashedThis was likely caused by the following module: igxpdv32.dllBugcheck code: 0xEA (0x88B4B020, 0x88B4EA90, 0x88AF5438, 0x1)Error: THREAD_STUCK_IN_DEVICE_DRIVERDump file: C:\WINDOWS\Minidump\Mini062810-01.dmpfile path: C:\WINDOWS\system32\igxpdv32.dllproduct: Intel Graphics Accelerator Drivers for Windows NT®company: Intel Corporationdescription: Component GHAL Driver On Sun 6/27/2010 6:17:30 PM your computer crashedThis was likely caused by the following module: pci.sysBugcheck code: 0x1000008E (0x80000004, 0x80707AE1, 0xB9C8B5A4, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_MDump file: C:\WINDOWS\Minidump\Mini062710-01.dmpfile path: C:\WINDOWS\system32\drivers\pci.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Plug and Play PCI EnumeratorThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Sat 6/26/2010 8:28:06 PM your computer crashedThis was likely caused by the following module: igxpdx32.dllBugcheck code: 0x1000008E (0xC0000005, 0xBF392CBE, 0xA7DA9B64, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_MDump file: C:\WINDOWS\Minidump\Mini062610-02.dmpfile path: C:\WINDOWS\system32\igxpdx32.dllproduct: Intel Graphics Accelerator Drivers for Windows NT®company: Intel Corporationdescription: DirectDraw® Driver for Intel® Graphics Technology On Sat 6/26/2010 7:02:49 PM your computer crashedThis was likely caused by the following module: pci.sysBugcheck code: 0x1000008E (0x80000004, 0x80707AE1, 0xA7FE85A4, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_MDump file: C:\WINDOWS\Minidump\Mini062610-01.dmpfile path: C:\WINDOWS\system32\drivers\pci.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Plug and Play PCI EnumeratorThe crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. --------------------------------------------------------------------------------Conclusion-------------------------------------------------------------------------------- 13 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. Преди около 3 часа почистих изцяло компютъра, оказа се че съм имал проблемен вентилатор; махнах страничния панел на кутията, сложих компютъра върху бюрото... след час и половина с включена игра все още върви нормално... Цитирай Link to comment Сподели другаде More sharing options...
oldmcz Публикувано Юли 2, 2010 Report Share Публикувано Юли 2, 2010 Здравей,този син екран е симптом на хардуерна недостатъчност какво ще рече това ами някоя част си е тръгнала за начало сложи вентилатор на кутията която да тегли топлият въздух от компютъра добре си го почистил защото няма нещо което да не се потдържа и да се очаква прекалено много та на мен лично ми правеше така когато погледнах заминала звукова карта викам си а така ! и ми исписваше този екран същият преди това ми се прецака цялото дъно и неможех да инсталирвам уиндоус и трябваше да сменя с ново дъно сега съм сложил вентилатор който е закрепен точно на дъното да се охлажда и в тия жеги нямам никакъв проблем с настолния какво извличаш последно като информация ами направи добро охлаждане гледам се справяш и сам в тия жеги е нормално да има аномалии но имай си едно на ум защото този син екран е едно от най-неприятните неща които срещаме или хард диск или дънна платка е проява на синият екран имай го в предвит успех приятел Цитирай Link to comment Сподели другаде More sharing options...
RamzesIII Публикувано Юли 2, 2010 Report Share Публикувано Юли 2, 2010 Здравейте, напоследък съм изправен пред следния проблем: когато използвам компютъра само за интернет, скайп, музика и т.н. компютъра си работи нормално, но когато пусна някоя игра се рестартира, ако не веднага то в следващите 15 минути. Първоначално мислех, че проблема е в Windows-a и го преинсталирах, но без резултат...ОС - Microsoft Windows XP Professionalдъно - ECS G31T-Mпроцесор - DualCore Intel Celeron E1400, 2000 MHz (10 x 200)видео карта- Intel® G33/G31 Express Chipset Family ; 256 MBхард диск - SAMSUNG HD322HJ ; 320 GBRAM - 2 GBTjmax температура CPU - 85 °C (185 °F) ; в момента Temperature: CPU #1/ Core 1 - 32*C ; Temperature: CPU #1/ COre 2 - 27*C ; Tеmperature: CPU - 25*C Данните ги копирам от Everest UE, ако трябва да дам още някаква информация кажете...Преди малко изключих опцията компютъра да се рестартира автоматично при "провал" в системата, заредих енда игра и ми излезе следния син екран: http://dc183.4shared.com/img/330098227/495f2e7/013.jpg?rnd=0.799182850067426 Това дъно е с вградена видеокарта и напълно нормално е да прави рестарти при натоварване с игри. Цитирай Link to comment Сподели другаде More sharing options...
oldmcz Публикувано Юли 2, 2010 Report Share Публикувано Юли 2, 2010 Това дъно е с вградена видеокарта и напълно нормално е да прави рестарти при натоварване с игри. симптом на повреда е този син екран как ще е нормално ??? дай да не играем игри и да не използваме компютъра само за красота без да го натоварваме понеже ще издаде този син екран и е напълно нормално не е така ! Цитирай Link to comment Сподели другаде More sharing options...
Julko Публикувано Юли 3, 2010 Report Share Публикувано Юли 3, 2010 Кажи поне кой е проблемния вентилатор? Цитирай Link to comment Сподели другаде More sharing options...
judaka Публикувано Август 1, 2011 Report Share Публикувано Август 1, 2011 И аз имам същия проблем Field ValueComputer Computer Type ACPI Uniprocessor PCOperating System Microsoft Windows XP ProfessionalOS Service Pack Service Pack 3Internet Explorer 7.0.5730.13 (IE 7.0)DirectX 4.09.00.0904 (DirectX 9.0c)Computer Name KRISO (Andrei)User Name krisSMTP E-mail Address andrei4o222@abv.bgLogon Domain KRISODate / Time 2011-08-01 / 15:53 Motherboard CPU Type AMD Athlon XP, 1533 MHz (11.5 x 133) 1800+Motherboard Name Albatron KX600 (Pro) (5 PCI, 1 AGP, 3 DDR DIMM, Audio)Motherboard Chipset VIA VT8377 Apollo KT600System Memory 768 MB (PC3200 DDR SDRAM)DIMM1 256 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz)DIMM2: Kingston K 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz) (2.5-3-3-7 @ 166 MHz)BIOS Type Award (09/17/03)Communication Port Communications Port (COM1)Communication Port Communications Port (COM2)Communication Port ECP Printer Port (LPT1) Display Video Adapter NVIDIA GeForce FX 5200 (128 MB)3D Accelerator nVIDIA GeForce FX 5200Monitor Lite-On/Litronic e1786FNST [17" CRT] (339291050) Multimedia Audio Adapter Realtek ALC650 @ VIA AC'97 Enhanced Audio Controller Storage IDE Controller VIA Bus Master IDE Controller - 0571Storage Controller AG40XEEE IDE ControllerFloppy Drive Floppy disk driveDisk Drive WDC WD400JB-00ETA0 (37 GB, IDE)Optical Drive BWJMLS F8XMNCHAVO SCSI CdRom DeviceOptical Drive SAMSUNG CD-ROM SC-152A (52x CD-ROM)SMART Hard Disks Status OK Partitions C: (NTFS) 38154 MB (2303 MB free)Total Size 38154 MB (2303 MB free) Input Keyboard Standard 101/102-Key or Microsoft Natural PS/2 KeyboardMouse HID-compliant mouseMouse PS/2 Compatible Mouse Network Primary IP Address 78.90.44.167Primary MAC Address 4C-00-10-70-46-78Network Adapter Realtek RTL8139/810x Family Fast Ethernet NIC (78.90.44.167) Peripherals Printer Microsoft XPS Document WriterUSB1 Controller VIA VT8235 USB Universal Host ControllerUSB1 Controller VIA VT8235 USB Universal Host ControllerUSB1 Controller VIA VT8235 USB Universal Host ControllerUSB2 Controller VIA VT8235 USB 2.0 Enhanced Host ControllerUSB Device USB Human Interface Device DMI DMI BIOS Vendor Phoenix Technologies, LTDDMI BIOS Version 6.00 PGDMI System Manufacturer VIA Technologies, Inc.DMI System Product KT600DMI System Version DMI System Serial Number DMI Motherboard Manufacturer DMI Motherboard Product KT600DMI Motherboard Version DMI Motherboard Serial Number DMI Chassis Manufacturer DMI Chassis Version DMI Chassis Serial Number DMI Chassis Asset Tag DMI Chassis Type Desktop CaseDMI Total / Free Memory Sockets 3 / 1 Problems & Suggestions Problem Disk free space is only 6% on drive C:.Това ми е компютарат не е от паметта имах повече памет и пак същата работа,трих кфо ли не правих пак нестава помогнете моля ви само Кънтър Страйк тръгва без да има проблеми Цитирай Link to comment Сподели другаде More sharing options...
Night_Raven Публикувано Август 1, 2011 Report Share Публикувано Август 1, 2011 Температурите и напреженията как са? Дай снимка да ги видим. Драйверите актуални ли са? Цитирай Link to comment Сподели другаде More sharing options...
judaka Публикувано Август 1, 2011 Report Share Публикувано Август 1, 2011 Ами температурите поне така пише е ,че са на дънната платка 46 на компютърът е 52 а другата немога да я разталкувам в черно квадратче е 44 градуса,доколкото за драйверите...незнам как да порверя :( Ето какво ми написа при прогтамата WHOCRASHED On Mon 8/1/2011 1:39:14 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini080111-06.dmpThis was probably caused by the following module: win32k.sys (win32k+0x1752) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF801752, 0xFFFFFFFFB9C0CC88, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_Mfile path: C:\WINDOWS\system32\win32k.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Multi-User Win32 DriverBug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Mon 8/1/2011 12:59:37 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini080111-05.dmpThis was probably caused by the following module: nv4_disp.dll (nv4_disp+0xC6EC4) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF0D8EC4, 0xFFFFFFFFB9D748BC, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_Mfile path: C:\WINDOWS\system32\nv4_disp.dllproduct: NVIDIA Compatible Windows 2000 Display driver, Version 175.19 company: NVIDIA Corporationdescription: NVIDIA Compatible Windows 2000 Display driver, Version 175.19 Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 175.19 , NVIDIA Corporation). Google query: nv4_disp.dll NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Mon 8/1/2011 11:52:48 AM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini080111-04.dmpThis was probably caused by the following module: ntfs.sys (Ntfs+0xDFF0) Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFF7B96A00, 0xFFFFFFFFF7B966FC, 0xFFFFFFFF8054BF0F)Error: NTFS_FILE_SYSTEMfile path: C:\WINDOWS\system32\drivers\ntfs.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT File System DriverBug check description: This indicates a problem occurred in the NTFS file system. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sun 7/31/2011 11:52:39 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini080111-03.dmpThis was probably caused by the following module: hal.dll (hal+0x2791) Bugcheck code: 0x1000000A (0x16, 0x2, 0x0, 0xFFFFFFFF804E4A8A)Error: CUSTOM_ERRORfile path: C:\WINDOWS\system32\hal.dllproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Hardware Abstraction Layer DLLThe crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sun 7/31/2011 11:08:57 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini080111-02.dmpThis was probably caused by the following module: hal.dll (hal+0x276E) Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF804DC11D)Error: CUSTOM_ERRORfile path: C:\WINDOWS\system32\hal.dllproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Hardware Abstraction Layer DLLThe crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Fri 7/29/2011 3:59:20 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini072911-02.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x5C846) Bugcheck code: 0x1A (0x41284, 0x734E001, 0x5B0B, 0xFFFFFFFFC0503000)Error: MEMORY_MANAGEMENTfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a severe memory management error occurred.This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Fri 7/29/2011 2:50:33 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini072911-01.dmpThis was probably caused by the following module: ntfs.sys (Ntfs+0xDFF0) Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFF7BA6AC8, 0xFFFFFFFFF7BA67C4, 0xFFFFFFFFF754832B)Error: NTFS_FILE_SYSTEMfile path: C:\WINDOWS\system32\drivers\ntfs.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT File System DriverBug check description: This indicates a problem occurred in the NTFS file system. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Tue 7/26/2011 12:22:14 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini072611-01.dmpThis was probably caused by the following module: win32k.sys (win32k+0x2330) Bugcheck code: 0x1000007F (0xD, 0x0, 0x0, 0x0)Error: UNEXPECTED_KERNEL_MODE_TRAP_Mfile path: C:\WINDOWS\system32\win32k.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Multi-User Win32 DriverBug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Mon 7/25/2011 8:13:35 AM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini072511-02.dmpThis was probably caused by the following module: dxg.sys (dxg+0x588F) Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFFBF00588F, 0xFFFFFFFFB98A3C00, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_Mfile path: C:\WINDOWS\system32\drivers\dxg.sysproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: DirectX Graphics DriverBug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sun 7/24/2011 9:13:52 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini072511-01.dmpThis was probably caused by the following module: nv4_disp.dll (nv4_disp+0x136411) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF148411, 0xFFFFFFFFB9E8C9C4, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_Mfile path: C:\WINDOWS\system32\nv4_disp.dllproduct: NVIDIA Compatible Windows 2000 Display driver, Version 175.19 company: NVIDIA Corporationdescription: NVIDIA Compatible Windows 2000 Display driver, Version 175.19 Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 175.19 , NVIDIA Corporation). Google query: nv4_disp.dll NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Sun 7/24/2011 4:59:12 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini072411-10.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x79A4) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF804DE9A4, 0xFFFFFFFFB9F21CF0, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_Mfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 7/24/2011 4:20:33 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini072411-09.dmpThis was probably caused by the following module: nv4_disp.dll (nv4_disp+0x20F9C8) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFFBA5579D4, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_Mfile path: C:\WINDOWS\system32\nv4_disp.dllproduct: NVIDIA Compatible Windows 2000 Display driver, Version 175.19 company: NVIDIA Corporationdescription: NVIDIA Compatible Windows 2000 Display driver, Version 175.19 Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 175.19 , NVIDIA Corporation). Google query: nv4_disp.dll NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Sun 7/24/2011 3:30:02 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini072411-08.dmpThis was probably caused by the following module: nv4_disp.dll (nv4_disp+0x184D28) Bugcheck code: 0x100000BE (0xFFFFFFFFBF196D67, 0x2190A021, 0xFFFFFFFFB9F7CA9C, 0xC)Error: CUSTOM_ERRORfile path: C:\WINDOWS\system32\nv4_disp.dllproduct: NVIDIA Compatible Windows 2000 Display driver, Version 175.19 company: NVIDIA Corporationdescription: NVIDIA Compatible Windows 2000 Display driver, Version 175.19 A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 175.19 , NVIDIA Corporation). Google query: nv4_disp.dll NVIDIA Corporation CUSTOM_ERROR On Sun 7/24/2011 1:48:43 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini072411-07.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x4EFD) Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF804DBEFD, 0xFFFFFFFFB9913AB4, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_Mfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 7/24/2011 1:35:52 PM GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\Mini072411-06.dmpThis was probably caused by the following module: nv4_disp.dll (nv4_disp+0xC468D) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF0D668D, 0xFFFFFFFFB4876A2C, 0x0)Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_Mfile path: C:\WINDOWS\system32\nv4_disp.dllproduct: NVIDIA Compatible Windows 2000 Display driver, Version 175.19 company: NVIDIA Corporationdescription: NVIDIA Compatible Windows 2000 Display driver, Version 175.19 Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 175.19 , NVIDIA Corporation). Google query: nv4_disp.dll NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M The following dump files were found but could not be read. These files may be corrupt:C:\WINDOWS\Minidump\Mini080111-01.dmp Цитирай Link to comment Сподели другаде More sharing options...
Night_Raven Публикувано Август 1, 2011 Report Share Публикувано Август 1, 2011 Дай снимка от HWMonitor. Цитирай Link to comment Сподели другаде More sharing options...
judaka Публикувано Август 1, 2011 Report Share Публикувано Август 1, 2011 Ето снимката Цитирай Link to comment Сподели другаде More sharing options...
Night_Raven Публикувано Август 1, 2011 Report Share Публикувано Август 1, 2011 Ако напреженията са точни или горе-долу точни, положението е много зле. Понеже отчитането чрез датчици може да не е особено точно, е силно препоръчително да замериш напреженията с мултиметър (описано е в тази тема към края й). Ако не знаеш точно как или не си сигурен в себе си, помоли познат, който има опит. Ако замерванията също покажат подобни отклонения в напреженията (или въобще отклонения извън допустимите 5%), значи захранването е за смяна. Цитирай Link to comment Сподели другаде More sharing options...
Пламен Дановски Публикувано Декември 7, 2011 Report Share Публикувано Декември 7, 2011 И аз имам същият проблем с рестартирването с компютър HP Compaq ds5100SFF Base Unit съм . Цитирай Link to comment Сподели другаде More sharing options...
Препоръчан пост
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.