BSOD i crashe programów

Mam problem z komputerem. Mianowicie częste BSoDy. Problem pojawił się po upgradzie.

System zainstalowany na czysto ze wszystkimi sterownikami. 

BSOD pojawia się nieregularnie, to przy oglądaniu filmu, to przy przeglądaniu internetu czy pracy w Wordzie. Dodam, że crashują też różne programy. Firefox co chwilę. Zmieniłem na Chroma i jest trochę lepiej. Tu często następuje crash wtyczki flash i wystarczy tylko odświeżyć stronę.

W trybie awaryjnym nic takiego się nie dzieje, więc podejrzewam, że to problem z softem.

Może macie jakieś propozycje jak to naprawić? Z góry dziękuję za wszelką pomoc.

 

Analiza WhoCrashed:

On Mon 2014-08-18 11:27:07 GMT your computer crashed

crash dump file: C:\Windows\Minidump\081814-4664-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ED3E94, 0xFFFFF88006832CA0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 

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 that cannot be identified at this time. 

 

 

 

On Mon 2014-08-18 11:27:07 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ED3E94, 0xFFFFF88006832CA0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 

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 that cannot be identified at this time. 

 

 

 

On Mon 2014-08-18 10:58:18 GMT your computer crashed

crash dump file: C:\Windows\Minidump\081814-3790-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 

Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA800969C770, 0x0)

Error: DRIVER_VERIFIER_DETECTED_VIOLATION

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. 

The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. 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 that cannot be identified at this time. 

 

 

 

On Mon 2014-08-18 10:24:38 GMT your computer crashed

crash dump file: C:\Windows\Minidump\081814-3868-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 

Bugcheck code: 0x4E (0x99, 0x1635E0, 0x2, 0x163DDF)

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 Sat 2014-08-02 22:16:06 GMT your computer crashed

crash dump file: C:\Windows\Minidump\080314-3868-01.dmp

This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x196C) 

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800454E96C, 0xFFFFF88009325BD0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\drivers\dxgmms1.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: DirectX Graphics MMS

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 

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 that cannot be identified at this time. 

 

 

 

On Sat 2014-08-02 12:33:44 GMT your computer crashed

crash dump file: C:\Windows\Minidump\080214-64584-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E92E94, 0xFFFFF8800653C4A0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 

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 that cannot be identified at this time. 

 

 

 

On Thu 2014-07-24 18:35:50 GMT your computer crashed

crash dump file: C:\Windows\Minidump\072414-9640-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 

Bugcheck code: 0x50 (0xFFFFFA9006633130, 0x0, 0xFFFFF80002FBFA4E, 0x5)

Error: PAGE_FAULT_IN_NONPAGED_AREA

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 invalid system memory has been referenced.

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 that cannot be identified at this time. 

 

 

 

On Thu 2014-07-24 18:19:45 GMT your computer crashed

crash dump file: C:\Windows\Minidump\072414-9110-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 

Bugcheck code: 0x19 (0x3, 0xFFFFFA80066342E0, 0xFFFFFA80064342E0, 0xFFFFFA80066342E0)

Error: BAD_POOL_HEADER

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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 

 

 

 

On Thu 2014-07-24 12:56:58 GMT your computer crashed

crash dump file: C:\Windows\Minidump\072414-9360-01.dmp

This was probably caused by the following module: shareduserdata.sys (SharedUserData+0x0) 

Bugcheck code: 0x1A (0x3452, 0x77631000, 0xFFFFF70001081BA0, 0x3500001D96E5424)

Error: MEMORY_MANAGEMENT

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

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: shareduserdata.sys . 

Google query: shareduserdata.sys MEMORY_MANAGEMENT

 

 

 

On Wed 2014-07-23 15:13:28 GMT your computer crashed

crash dump file: C:\Windows\Minidump\072414-8018-01.dmp

This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x324F) 

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880043A824F, 0xFFFFF88006E119F0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\drivers\dxgmms1.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: DirectX Graphics MMS

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 

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 that cannot be identified at this time.

 

Było tego więcej, ale najwidoczniej dane się już usunęły. Najczęściej powtarza się to nieszczęsne

Dxgmms1.sys oraz ntosknrl.exe. 

 

 

Moja specyfikacja:

Win 7 HB 64bit

Intel i5 4670

MSI B85-G43 Gaming

HIS HD 5850 iCooler V 1GB

2x 4GB ram DDR 3 1333 Samsunga

System na SSD Plextror M5S

 

 

Może macie jakieś propozycje jak to naprawić? Z góry dziękuję za wszelką pomoc.

Przetestuj pamięć RAM za pomocą Memtest, pobierz http://www.memtest86.com/downloads/memtest86-iso.zip wypakuj i nagraj na płytę (wersja na pendrive’a http://www.memtest86.com/downloads/memtest86-usb.zip), uruchom z niej komputer (każdy moduł przetestuj oddzielnie).

 

 

Jaką wersje oprogramowania ma dysk SSD?

Zapomniałem napisać. 

RAM używałem zamiennie po jednej kości, nadal to samo. Memtestem już testowałem. Nic nie wykazało.

Do SSD wgrałem najnowszy sterownik. Z poprzednią konfiguracją śmigało.

 

Zainstalowałem też starsze sterowniki do grafiki, jednak nic to nie nie dało.