PC-HELP.CZ

Dobrý den potřeboval bych poradit už strašně dlouho mi pc hází BSOD zkoušel jsem komplet formát, nová instalace win i změna i různé ovladače nevím si rady i na reklamačce mi to testovaly prej vše je v pořádku podle jednoho co jsem se ptal na jiném foru to není hardwarem ale softwarem nevím jestli mám špatně nastavený bios nebo co a jak přidávám všechny dmp soubory za tu dobu co mám ted nový win asi 3dny.
děkuji předem za jakoukoli informaci nebo pomoc

Já bych si zase dovolil tvrdit, že to bude nejspíše závada HW.
1) Otestuj paměť pomocí GoldMemory nebo Memtestu
2) Stáhni CrystalDiskInfo, v nabídce Úpravy zvol Kopírovat a obsah schránky sem vlož pomocí Ctrl+V.
Pokud to bude OK, nastavíme Verifier.

----------------------------------------------------------------------------
CrystalDiskInfo 4.1.3 (C) 2008-2011 hiyohiyo
Crystal Dew World : http://crystalmark.info/
----------------------------------------------------------------------------

OS : Windows 7 Home Premium Edition SP1 [6.1 Build 7601] (x64)
Date : 2011/11/14 23:22:07

-- Controller Map ----------------------------------------------------------
+ AMD SATA Controller (IDE Mode) [ATA]
- ATA Channel 0 (0)
- ATA Channel 1 (1)
+ AMD PCI IDE Controller [ATA]
+ ATA Channel 0 (0)
- ASUS DRW-24B3ST ATA Device
+ ATA Channel 1 (1)
- ST3160815AS ATA Device

-- Disk List ---------------------------------------------------------------
(1) ST3160815AS : 160.0 GB [0-3-1, pd1]

----------------------------------------------------------------------------
(1) ST3160815AS
----------------------------------------------------------------------------
Model : ST3160815AS
Firmware : 3.AAD
Serial Number : 9RA43DVB
Disk Size : 160.0 GB (8.4/137.4/160.0)
Buffer Size : 8192 KB
Queue Depth : 32
# of Sectors : 312579695
Rotation Rate : Neznámy údaj
Interface : Serial ATA
Major Version : ATA/ATAPI-7
Minor Version : ----
Transfer Mode : SATA/300
Power On Hours : 17068 hod.
Power On Count : 5283 krát
Temparature : 34 C (93 F)
Health Status : Pozor
Features : S.M.A.R.T., 48bit LBA, NCQ
APM Level : ----
AAM Level : ----

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 119 _90 __6 00000C51D973 Počet chyb čtení
03 _98 _97 __0 000000000000 Čas na roztočení ploten
04 _95 _95 _20 000000001551 Počet spuštění/zastavení
05 100 100 _36 000000000004 Počet přemapovaných sektorů
07 _89 _60 _30 000030FD7702 Počet chybných hledání
09 _81 _81 __0 0000000042AC Hodin v činnosti
0A 100 100 _97 000000000000 Počet opakovaných pokusů o roztočení ploten
0C _95 _95 _20 0000000014A3 Počet cyklů zapnutí zařízení
BB __1 __1 __0 00000000203D Ohlášeno neopravitelných chyb
BD _98 _98 __0 000000000002 Vysoká rychlost zápisu
BE _66 _45 _45 000022140022 Teplota toku vzduchu
C2 _34 _55 __0 001100000022 Teplota
C3 _75 _54 __0 0000085DFF10 Počet oprav chybného čtení
C5 100 100 __0 000000000002 Počet podezřelých sektorů
C6 100 100 __0 000000000002 Počet neopravitelných sektorů
C7 200 200 __0 000000000001 Počet chyb v kontrolním součtu UltraDMA
C8 100 253 __0 000000000000 Počet chyb při zápisu sektorů
CA _91 244 __0 000000000009 Počet chyb při směrování údajů

-- IDENTIFY_DEVICE ---------------------------------------------------------
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 0C 5A 3F FF C8 37 00 10 00 00 00 00 00 3F 00 00
010: 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20
020: 39 52 41 34 33 44 56 42 00 00 40 00 00 04 33 2E
030: 41 41 44 20 20 20 53 54 33 31 36 30 38 31 35 41
040: 53 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
050: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 80 10
060: 00 00 2F 00 40 00 02 00 02 00 00 07 3F FF 00 10
070: 00 3F FC 10 00 FB 01 10 FF FF 0F FF 00 00 00 07
080: 00 03 00 78 00 78 00 78 00 78 00 00 00 00 00 00
090: 00 00 00 00 00 00 00 1F 05 06 00 00 00 48 00 40
0A0: 00 FE 00 00 34 6B 7D 01 40 23 34 69 3C 01 40 23
0B0: 40 7F 00 00 00 00 FE FE FF FE 00 00 D0 00 00 00
0C0: 00 00 00 00 00 00 00 00 96 6F 12 A1 00 00 00 00
0D0: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00
0E0: 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 02
0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
100: 00 09 9E B0 12 A1 9E B0 12 A1 20 20 00 02 02 B6
110: 00 02 00 8A 3C 06 3C 0A 00 00 07 C6 01 00 08 00
120: 13 14 12 00 00 02 00 80 00 00 00 00 00 82 02 02
130: 00 00 04 04 00 00 00 00 00 00 00 00 1B 00 00 0B
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D9 A5

test paměti dám dneska (zítra a pak napíšu)
ted jsem nainstaloval driver max a zkusil jsem nainstalovat ovladač (nový) na nějaký řadič cpu atd a zatím jede tak zkusím ještě tu pamět

díky za pomoc

Ještě udělej test pomocí HD Tune, zda najde nějaké vadné bloky (Error scan)
Dovoluji si totiž tvrdit, že ten disk je vadný.
attribut
0x05 naznačuje, že už došlo k realokaci vadných sektorů
0xBB naznačuje, že dochází k takovému poškození dat v některých sektorech, že se je nepovede pomocí ECC zrekonstruovat.
0xC5 další sektory čekají na vyhodnocení stavu (už u nich v minulosti došlo k chybě při čtení)
0xC6 vadné sektory, které již nelze nahradit záložními sektory
0xCA také naznačuje problémy

Také vyexportuj systémový protokol. Mrknem se, jestli tam jsou chybové události od ovladače třídy disk nebo portu disku.
V Ovládací panely->Nástroje pro správu->Prohlížeč událostí->Protokoly systému Windows->klikni pravým myšítkem na protokol Systém, vyber Uložit všechny události jako, ulož to jako .evtx soubor a ten upni na http://www.leteckaposta.cz

no HD to zřejmě nebude protože jsem měl pc a na tom byl jiný hd a dělalo to taky(byl to složeny pc s alfy)a já jsem jen vyměnil hd protože tam byly soubory (filmy hudba ) a dělalo to taky(a ten hd co k tomu byl po prví jede normálně na jiným pc) nevím ale jestli třeba není bios špatně nastavený nebo tak něco.
omlouvám se ale letecká pošta mi nejde hodil jsem to na ulož to


jo a zkoušel jsem nejaký program na detekci dmp Whocrashed a tohle mi vyšlo

jsou tu všechny dmp za celou dobu co mám nově přeinstalovaný win (cca 4dny)

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 14.11.2011 22:56:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111411-21403-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A9C93C, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 Mon 14.11.2011 22:48:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111411-17472-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88003E28B80)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Mon 14.11.2011 22:48:42 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: athurx.sys (athurx+0xAFEA2)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88003E28B80)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athurx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: athurx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: athurx.sys Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Mon 14.11.2011 22:42:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111411-18174-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF80002AD5E38)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 14.11.2011 10:02:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111411-17518-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2DF7E)
Bugcheck code: 0xFE (0x5, 0xFFFFFA8004D531A0, 0x10024397, 0xFFFFFA8005714F68)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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 14.11.2011 9:49:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111411-18579-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x5DBE)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002AD22B2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 14.11.2011 9:43:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111411-23415-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000000.sys (Unloaded_Unknown_Module_00000000`00000000+0x29E92D)
Bugcheck code: 0xFE (0x5, 0xFFFFFA8004C781A0, 0x10024397, 0xFFFFFA8005710F68)
Error: BUGCODE_USB_DRIVER
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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: unknown_module_00000000`00000000.sys .
Google query: unknown_module_00000000`00000000.sys BUGCODE_USB_DRIVER




On Mon 14.11.2011 9:38:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111411-18860-02.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1EA5C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004189A5C, 0xFFFFF88003DF46D8, 0xFFFFF88003DF3F30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 a system thread 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 14.11.2011 9:27:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111411-18860-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x22F7)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.2 driver
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.
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 14.11.2011 8:46:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111411-31933-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFF80000B16084, 0x2, 0x1, 0xFFFFF80002AD58B6)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 14.11.2011 8:34:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111411-19952-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x8886, 0xFFFFFA8000952CB0, 0xFFFFFA8000645FC0, 0x605)
Error: MEMORY_MANAGEMENT
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 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 Mon 14.11.2011 2:15:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111411-18220-01.dmp
This was probably caused by the following module: unknown_module_00000001`00040000.sys (Unloaded_Unknown_Module_00000001`00040000+0xFB2CE388)
Bugcheck code: 0xFE (0x5, 0xFFFFFA8004E361A0, 0x10024397, 0xFFFFFA8005B53F68)
Error: BUGCODE_USB_DRIVER
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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: unknown_module_00000001`00040000.sys .
Google query: unknown_module_00000001`00040000.sys BUGCODE_USB_DRIVER




On Sun 13.11.2011 1:20:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111311-21715-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x864A9)
Bugcheck code: 0xA (0xFFFFF88008DC6FF8, 0x2, 0x0, 0xFFFFF80002E221A0)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sat 12.11.2011 22:21:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111211-19749-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D27D)
Bugcheck code: 0xFE (0x6, 0xFFFFFA8004C3E010, 0x50456368, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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 Sat 12.11.2011 22:12:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111211-23696-01.dmp
This was probably caused by the following module: unknown_module_fffffa80`04de0680.sys (Unloaded_Unknown_Module_fffffa80`04de0680+0x2F9F18)
Bugcheck code: 0x1A (0x61940, 0x21E000, 0x0, 0x0)
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: unknown_module_fffffa80`04de0680.sys .
Google query: unknown_module_fffffa80`04de0680.sys MEMORY_MANAGEMENT

1)Udělej ten test pomocí HD Tune (jestli se objeví nějaká červená kostička)
2)Napiš, jak dopadl test paměti.

Pak budeme pokračovat dál.

Tak test hd jak rychlí tak i ten normální vyšel pozitivně a memtest takynevím jestli mám teda zkusit ještě gold ale napadlo mě může to být wifi usb adaptérem jediná věc co k tomu nebyla protože jsem ho měl na reklamačce a tam pc testovaly 10dní a prej je v pořádku (testovaly pamět a hd + zkoušely brouzdání na netu atd) tak možná to může být tím ale nemám to jak vyzkoušet většinou mi to spadne při hraní multiplayeru nebo při zapnutí prohlížeče

Pozitivně znamená, že byly nalezeny chyby?

že nebyly protože ted je cena hd docela velká

No podle mě má ten disk problémy. Alespoň podle SMART atributů. Paměť taky v pohodě?

Ještě můžeš zkusit spustit Verifier

Spustit->napište "verifier"->OK->Vytvořit uživatelské nastavení->Vybrat individuální nastavení z úplného seznamu->mimo "Simulace nedostatku prostředků" zatrhněte vše->vybrat ovladače ze seznamu->vyberte vše, co není od Microsoftu->Dokončit->restartujte PC

Pokud verifier narazí na nějaký problém, objeví se BSOD a dojde k restartu počítače. Ve složce Windows\Minidump by se měl vytvořit nový výpis paměti, který mi upněte.
Pokud by k BSOD docházelo už při startu OS a nedařilo se i po několika restartech zavést systém,
spusťte nouzový režim (mačkání F8 při startu PC)
Tam spusťte Verifier a zvolte "Odstranit existující nastavení->Dokončit->restart PC.
Detekce chyby může trvat několik hodin i dní

Pokud je to ale HW (jak to vypadá) bude to stejně k ničemu.

testoval jsem to přes ten memtest a bez chyb a ten gold jsem dělal jen 10% a pak jsem tomusel přerušit ale můžu to dát zítra ráno a ten verifier jsem zkoušel ale zkusím znova a kde když tak může být v HW chyba v tom hd abych věděl kolik se plácnu přes kapsu

Zatím pusť ten Verifier, pokud bude nový minidump, upni mi ho.