Сини екрани Windows 7

[veronisia]

Здравейте,

 

Откакто март месец тази година ми преинсталираха уиндоуса на компютъра, започнаха да ми се появяват сини екрани и да ми се рестартира системата.

Още първия ден след преинсталацията се появи първият син екран. След това от време на време имаше пак такива екрани, обикновено веднъж-два пъти в месеца, но напоследък много зачестиха и вече не се издържа...

 

Това е инфото от WhoCrashed:

 

System Information (local)

computer name: VERONICA-MSIPC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: MS-7529, MICRO-STAR INTERNATIONAL CO.,LTD, G31TM-P21 (MS-7529)
CPU: GenuineIntel Pentium® Dual-Core CPU E6500 @ 2.93GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2146689024 total

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 6.10.2014 г. 05:38:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100614-14421-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCC6F3)
Bugcheck code: 0x4E (0x99, 0x5D7BD, 0x3, 0x1D122)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 6.10.2014 г. 05:38:01 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCC6F3)
Bugcheck code: 0x4E (0x99, 0x5D7BD, 0x3, 0x1D122)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 4.10.2014 г. 18:50:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100414-13484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD221C)
Bugcheck code: 0x4E (0x99, 0x325F6, 0x3, 0x57279)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.



On Wed 1.10.2014 г. 10:58:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100114-21109-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1C1FF)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFA7306420, 0xFFFFFFFFA7306670, 0xA4A080C)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 30.9.2014 г. 20:12:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093014-19031-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x175640)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFA24752B0, 0xFFFFFFFFA24752D8, 0x805000F)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 340.52
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 340.52
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 340.52 , NVIDIA Corporation).
Google query: NVIDIA Corporation BAD_POOL_HEADER



On Fri 26.9.2014 г. 16:18:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092614-13656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD221C)
Bugcheck code: 0x4E (0x99, 0x72CF4, 0x3, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.



On Thu 4.9.2014 г. 10:06:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090414-19781-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D0FF)
Bugcheck code: 0x116 (0xFFFFFFFF8710A008, 0xFFFFFFFF93931B92, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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 that cannot be identified at this time.



On Wed 27.8.2014 г. 18:38:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082714-17531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD221C)
Bugcheck code: 0x4E (0x99, 0x73581, 0x0, 0x6D341)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.



On Tue 5.8.2014 г. 05:42:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080514-14593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD221C)
Bugcheck code: 0x4E (0x99, 0x5F2CE, 0x1, 0x6AC0E)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.



On Wed 30.7.2014 г. 19:23:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073014-20765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD221C)
Bugcheck code: 0x4E (0x99, 0x78DBD, 0x0, 0x3097D)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 that cannot be identified at this time.

Conclusion

16 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 340.52 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

А тук съм качила и самите dump файлове:

 

http://dox.bg/files/dw?a=dbd24efe90

 

Актуализирах драйвера на видеокартата (NVIDIA GeForce GT 240) през Device Manager с последния актуален 340.520 миналата седмица и като че ли оттогава зачестиха сините екрани...

 

Моля за съвет и предварително благодаря

[Night_Raven]

Изтегли Autoruns и:

1) стартирай програмата;

2) изчакай да сканира всички местоположения за стартиращи обекти;

3) избери Options -> Filter Options... -> постави отметки на Hide Microsoft entries и Verify code signatures -> OK;

4) меню File -> Refresh;

5) меню File -> Save... (от падащото меню остави избран .arn за файлов формат).

6) архивирай създадения файл с удобен за теб архиватор и прикачи архива към коментара си.

 

Описание как се прикачат файлове (ако не знаеш):

- при публикуване на коментар кликни бутон Повече опции;

- долу в секция "Прикрепяне на файлове" посочи файла и кликни бутон Прикачи този файл;

- накрая кликни Добавяне в мнението.

[veronisia]

Благодаря ти, Night_Raven!

С нетърпение очаквах да се включиш. Ето файлчето.

AutoRuns.rar

[Night_Raven]

Извинявам се. Повтори горната процедура, но този път размаркирай Verify code signatures.

[veronisia]

Ето го

 

AutoRuns.rar

[Night_Raven]

По принцип е добра идея да се актуализират всички драйвери, не само този за видео картата. Дай доклад от AIDA64, за да видим с какви компоненти разполагаш.

[veronisia]

Такъв доклад ли искаш?

Report.txt

 

Това е инфо за температурите:

 

А като разглеждах в Device manager ми направи впечатление, че в Sound, video and game controllers има едно Unknown Device, но е без удивителни и въпросителни. Ето шот:

Не мога да кажа дали преди актуализиране на драйвера е било така, след това го забелязах и не се оправя...

 

[Night_Raven]

Преди да дам драйверите, да попитам, знаеш ли как се инсталират през Device Manager? Предполагам знаеш, след като даваш снимки, но все пак да попитам, за да съм сигурен.

 

Също така искам да знам дали хардуерните компоненти са тествани, по-конкретно твърдият диск и паметта.

[veronisia]

Само паметта съм тествала преди няколко дни с Windows Memory Diagnostic Tool.

Не откри никакви грешки или проблеми.

 

Колкото до инсталирането на драйвери от Device manager, нали от тук:

[Night_Raven]

Драйвер за дънната платка (стартирай го с допълнителен парамеътър -overall; ако не знаеш как, пиши)
Драйвер за мрежовата карта
Драйвер за звуковата карта

Също така бих посъветвал да деинсталираш твоята версия на DAEMON Tools и да инсталираш последната.

Колкото до тестът на паметта, това става с Memtest86+. Създава се стартиращ диск или стартираща флаш памет, стартира се системата от тях и се оставя да извърти поне 2-3 pass-а.

 

Тестът на твърдия диск обикновено се прави под DOS с инструмента на производителя, което в твоя случай ще е Data Lifeguard Diagnostic. За жалост тя обаче няма готова версия за стартиращ диск или флаш памет.

[veronisia]

Ок, много ти благодаря за съдействието.

Но понеже не съм голям разбирач и се опасявам, че сама ще омажа тотално нещата, май ще върви комп-а директно на сервиз...