Starší pc - při spuštění pc jsou všude závorky

[Spartak24]

Dobrý den,
měnili jsme u staršího pc desku+disk a při spouštění jsme si všimli závorek (vždy když je černá plocha, tak je černá plocha se závorkami)
Což by jsme ještě přehlédli, ale problém je i s OS/diskem. Včera jsme nainstalovali OS (windows 7 HP) - vše proběhlo v pořádku, ale pc se stále nenačte (zamrzne při startovací obrazovce - logo windows).
Nevíte, kde by mohl být problém?
Zkoušeli jsme zatím jiný OS, přepojit HDD do jiného SATA, přehodit prioritu boot zařízení, flashnout BIOS atd.
Předem děkuji.

[Rudy]

Zdravím!
Máte legální oper. systém?

[Spartak24]

Samozřejmě, že ano!

[Rudy]

Pravděpodobně se nenainstaloval regulérně. Dále nerozumím těm závorkám. Co tím myslíte?

[Spartak24]

no právě, že se správně nainstaloval (dokonce jsme zkoušeli ho přeinstalovat i nainstalovat jiný)
závorkami myslím doslova závorky, jen co budu moct, pošlu foto

[Rudy]

OK. Rád bych to viděl.

[Spartak24]

tady jsou slíbené fotky:
po zapnutí se objeví:

dále ony závorky:

jak je vidět, místo continue nebo pokračovaní je tam něco k..
a zde se pc vždy sekne:


pak vždy musíme pc natvrdo vypnout a po zapnutí se většinou objeví tato hláška:


už opravdu nevíme :/ zkoušeli jsme i vyndat baterku z desky a opět zandat, ale ani to nepomohlo..nemohl by být problém někde v biosu? není třeba v něm někde něco nastavit?
předem děkuji.

[Rudy]

Podle toho, co vidím, máte PC přetaktován a některý hardware se tomu brání. Vraťte takt v biosu na default, v biosu uložte nastavení, restartujte a zkuste znovu spustit.

[Spartak24]

nic jsme tam nikdy netaktovali - jediné co jsme v biosu dělali bylo aktualizaci/flash biosu, když začal být problém se zvukem a už jsme si nevěděli rady.
a jediné co se týče OC v biosu je:

a když rozklikneme to spodní/OC profily, tak se objeví:


nic víc jsme prostě nenašli.

PS: nemohlo by to být třeba i HDD?
vyluštíte z toho něco? myslím stav HDD? děkuji

smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-042stab112.15] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda ES
Device Model: ST3250620NS
Serial Number: 9QE2FYM2
Firmware Version: 3.AEG
User Capacity: 250,058,268,160 bytes [250 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Tue Feb 9 00:27:34 2016 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM level is: 254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is: Enabled
ATA Security is: Disabled, NOT FROZEN [SEC1]

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 430) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 92) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 110 088 006 - 234488564
3 Spin_Up_Time PO---- 097 095 000 - 0
4 Start_Stop_Count -O--CK 100 100 020 - 767
5 Reallocated_Sector_Ct PO--CK 100 100 036 - 0
7 Seek_Error_Rate POSR-- 089 060 030 - 875878058
9 Power_On_Hours -O--CK 071 071 000 - 26062
10 Spin_Retry_Count PO--C- 100 099 097 - 0
12 Power_Cycle_Count -O--CK 099 099 020 - 1861
187 Reported_Uncorrect -O--CK 100 100 000 - 0
189 High_Fly_Writes -O-RCK 100 100 000 - 0
190 Airflow_Temperature_Cel -O---K 061 040 045 Past 39 (71 119 43 26 0)
194 Temperature_Celsius -O---K 039 060 000 - 39 (0 22 0 0 0)
195 Hardware_ECC_Recovered -O-RC- 058 051 000 - 216295827
197 Current_Pending_Sector -O--C- 100 100 000 - 0
198 Offline_Uncorrectable ----C- 100 100 000 - 0
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
200 Multi_Zone_Error_Rate ------ 100 253 000 - 0
202 Data_Address_Mark_Errs -O--CK 100 253 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning

General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
GP/S Log at address 0x00 has 1 sectors [Log Directory]
GP/S Log at address 0x01 has 1 sectors [Summary SMART error log]
GP/S Log at address 0x02 has 5 sectors [Comprehensive SMART error log]
GP/S Log at address 0x03 has 5 sectors [Ext. Comprehensive SMART error log]
GP/S Log at address 0x06 has 1 sectors [SMART self-test log]
GP/S Log at address 0x07 has 1 sectors [Extended self-test log]
GP/S Log at address 0x09 has 1 sectors [Selective self-test log]
GP/S Log at address 0x10 has 1 sectors [NCQ Command Error log]
GP/S Log at address 0x11 has 1 sectors [SATA Phy Event Counters]
GP/S Log at address 0x20 has 1 sectors [Streaming performance log]
GP/S Log at address 0x21 has 1 sectors [Write stream error log]
GP/S Log at address 0x22 has 1 sectors [Read stream error log]
GP/S Log at address 0x23 has 1 sectors [Delayed sector log]
GP/S Log at address 0x80 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x81 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x82 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x83 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x84 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x85 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x86 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x87 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x88 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x89 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8a has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8b has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8c has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8d has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8e has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8f has 16 sectors [Host vendor specific log]
GP/S Log at address 0x90 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x91 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x92 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x93 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x94 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x95 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x96 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x97 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x98 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x99 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9a has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9b has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9c has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9d has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9e has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9f has 16 sectors [Host vendor specific log]
GP/S Log at address 0xa0 has 1 sectors [Device vendor specific log]
GP/S Log at address 0xa1 has 20 sectors [Device vendor specific log]
GP/S Log at address 0xa2 has 101 sectors [Device vendor specific log]
GP/S Log at address 0xa8 has 20 sectors [Device vendor specific log]
GP/S Log at address 0xa9 has 1 sectors [Device vendor specific log]
GP/S Log at address 0xe0 has 1 sectors [SCT Command/Status]
GP/S Log at address 0xe1 has 1 sectors [SCT Data Transfer]
GP Log at address 0xff has 23040 sectors [Reserved]

SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 124 (device log contains only the most recent 20 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 124 [3] occurred at disk power-on lifetime: 25854 hours (1077 days + 6 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 01 01 00 00 00 00 00 00 ed 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
37 00 ff 01 01 00 1d 51 00 1c 2e ed 00 06:53:27.566 SET MAX ADDRESS EXT
27 00 ff 00 00 00 1d 51 00 1c 2e e0 00 06:53:27.392 READ NATIVE MAX ADDRESS EXT
37 00 ff 00 00 00 1d 51 00 1c 2e ed 00 06:53:27.267 SET MAX ADDRESS EXT
27 00 ff 01 01 00 1d 51 00 1c 2e e0 00 06:53:27.205 READ NATIVE MAX ADDRESS EXT
37 00 ff 01 01 00 1d 51 00 1c 2e ed 00 06:53:20.408 SET MAX ADDRESS EXT

Error 123 [2] occurred at disk power-on lifetime: 25854 hours (1077 days + 6 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 01 01 00 00 00 00 00 00 ed 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
37 00 ff 01 01 00 1d 51 00 1c 2e ed 00 06:53:27.566 SET MAX ADDRESS EXT
27 00 ff 00 00 00 1d 51 00 1c 2e e0 00 06:53:27.392 READ NATIVE MAX ADDRESS EXT
37 00 ff 00 00 00 1d 51 00 1c 2e ed 00 06:53:27.267 SET MAX ADDRESS EXT
27 00 ff 00 01 00 1d 59 00 1c 6f e0 00 06:53:27.205 READ NATIVE MAX ADDRESS EXT
29 00 00 00 01 00 1d 59 00 1c 6f e0 00 06:53:20.408 READ MULTIPLE EXT

Error 122 [1] occurred at disk power-on lifetime: 23384 hours (974 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 01 01 00 00 00 00 00 00 ed 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
37 00 ff 01 01 00 1d 51 00 1c 2e ed 00 00:12:57.562 SET MAX ADDRESS EXT
27 00 ff 00 00 00 1d 51 00 1c 2e e0 00 00:12:57.503 READ NATIVE MAX ADDRESS EXT
37 00 ff 00 00 00 1d 51 00 1c 2e ed 00 00:12:57.278 SET MAX ADDRESS EXT
27 00 ff 01 01 00 1d 51 00 1c 2e e0 00 00:12:57.211 READ NATIVE MAX ADDRESS EXT
37 00 ff 01 01 00 1d 51 00 1c 2e ed 00 00:12:57.036 SET MAX ADDRESS EXT

Error 121 [0] occurred at disk power-on lifetime: 23384 hours (974 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 01 01 00 00 00 00 00 00 ed 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
37 00 ff 01 01 00 1d 51 00 1c 2e ed 00 00:12:57.562 SET MAX ADDRESS EXT
27 00 ff 00 00 00 1d 51 00 1c 2e e0 00 00:12:57.503 READ NATIVE MAX ADDRESS EXT
37 00 ff 00 00 00 1d 51 00 1c 2e ed 00 00:12:57.278 SET MAX ADDRESS EXT
27 00 ff 00 01 00 1d 59 00 1c 6f e0 00 00:12:57.211 READ NATIVE MAX ADDRESS EXT
29 00 00 00 01 00 1d 59 00 1c 6f e0 00 00:12:57.036 READ MULTIPLE EXT

Error 120 [19] occurred at disk power-on lifetime: 22904 hours (954 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 01 01 00 00 00 00 00 00 ed 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
37 00 ff 01 01 00 1d 51 00 1c 2e ed 00 00:20:44.888 SET MAX ADDRESS EXT
27 00 ff 00 00 00 1d 51 00 1c 2e e0 00 00:20:44.663 READ NATIVE MAX ADDRESS EXT
37 00 ff 00 00 00 1d 51 00 1c 2e ed 00 00:20:44.595 SET MAX ADDRESS EXT
27 00 ff 01 01 00 1d 51 00 1c 2e e0 00 00:20:44.421 READ NATIVE MAX ADDRESS EXT
37 00 ff 01 01 00 1d 51 00 1c 2e ed 00 00:20:44.296 SET MAX ADDRESS EXT

Error 119 [18] occurred at disk power-on lifetime: 22904 hours (954 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 01 01 00 00 00 00 00 00 ed 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
37 00 ff 01 01 00 1d 51 00 1c 2e ed 00 00:20:44.888 SET MAX ADDRESS EXT
27 00 ff 00 00 00 1d 51 00 1c 2e e0 00 00:20:44.663 READ NATIVE MAX ADDRESS EXT
37 00 ff 00 00 00 1d 51 00 1c 2e ed 00 00:20:44.595 SET MAX ADDRESS EXT
27 00 ff 00 01 00 1d 59 00 1c 6f e0 00 00:20:44.421 READ NATIVE MAX ADDRESS EXT
29 00 00 00 01 00 1d 59 00 1c 6f e0 00 00:20:44.296 READ MULTIPLE EXT

Error 118 [17] occurred at disk power-on lifetime: 22778 hours (949 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 01 01 00 00 00 00 00 00 ed 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
37 00 ff 01 01 00 1d 51 00 1c 2e ed 00 00:04:30.015 SET MAX ADDRESS EXT
27 00 ff 00 00 00 1d 51 00 1c 2e e0 00 00:04:29.790 READ NATIVE MAX ADDRESS EXT
37 00 ff 00 00 00 1d 51 00 1c 2e ed 00 00:04:29.722 SET MAX ADDRESS EXT
27 00 ff 01 01 00 1d 51 00 1c 2e e0 00 00:04:29.557 READ NATIVE MAX ADDRESS EXT
37 00 ff 01 01 00 1d 51 00 1c 2e ed 00 00:04:29.431 SET MAX ADDRESS EXT

Error 117 [16] occurred at disk power-on lifetime: 22778 hours (949 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 01 01 00 00 00 00 00 00 ed 00

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
37 00 ff 01 01 00 1d 51 00 1c 2e ed 00 00:04:30.015 SET MAX ADDRESS EXT
27 00 ff 00 00 00 1d 51 00 1c 2e e0 00 00:04:29.790 READ NATIVE MAX ADDRESS EXT
37 00 ff 00 00 00 1d 51 00 1c 2e ed 00 00:04:29.722 SET MAX ADDRESS EXT
27 00 ff 00 01 00 1d 59 00 1c 6f e0 00 00:04:29.557 READ NATIVE MAX ADDRESS EXT
29 00 00 00 01 00 1d 59 00 1c 6f e0 00 00:04:29.431 READ MULTIPLE EXT

SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 26062 -
# 2 Extended offline Completed without error 00% 25872 -
# 3 Short offline Completed: read failure 90% 25871 253403070508
# 4 Extended offline Completed without error 00% 19018 -
# 5 Extended offline Completed without error 00% 16174 -
# 6 Extended offline Completed: read failure 90% 15605 23184243248550
# 7 Extended offline Interrupted (host reset) 90% 15375 -
# 8 Extended offline Completed without error 00% 15344 -
# 9 Extended offline Completed without error 00% 15232 -
#10 Extended offline Aborted by host 90% 15231 -
#11 Short offline Completed without error 00% 15231 -
#12 Short offline Completed without error 00% 14921 -
#13 Extended offline Interrupted (host reset) 80% 14611 -
#14 Extended offline Completed without error 00% 14164 -
#15 Short offline Completed without error 00% 14016 -
#16 Short offline Completed without error 00% 13995 -
#17 Short offline Completed without error 00% 13974 -
#18 Extended offline Completed without error 00% 13955 -
#19 Short offline Completed without error 00% 13953 -
2 of 2 failed self-tests are outdated by newer successful extended offline self-test # 2

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version: 2
SCT Version (vendor specific): 521 (0x0209)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 39 Celsius
Power Cycle Max Temperature: 43 Celsius
Lifetime Max Temperature: 60 Celsius
SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 1 minute
Min/Max recommended Temperature: 0/ 0 Celsius
Min/Max Temperature Limit: 0/ 0 Celsius
Temperature History Size (Index): 128 (55)

Index Estimated Time Temperature Celsius
56 2016-02-08 22:20 39 ********************
... ..( 16 skipped). .. ********************
73 2016-02-08 22:37 39 ********************
74 2016-02-08 22:38 38 *******************
75 2016-02-08 22:39 39 ********************
... ..(107 skipped). .. ********************
55 2016-02-09 00:27 39 ********************

SCT Error Recovery Control:
Read: Disabled
Write: Disabled

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 3 Device-to-host register FISes sent due to a COMRESET
0x0001 2 0 Command failed due to ICRC error
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS

[Rudy]

Přeložím vám text na posledím obrázku:

CMOS nastavení je chybné
Přetaktování se nezdařilo! Prosíme vstupte do setup a překonfigurujte vaše (asi nastavení - je to mimo obrázek).
Stiskněte >F1< pro vstup do nastvení
Stiskněte >F2< pro nastavení výchozích hodnot a pokračujte

Z toho vyplývá, že je nastevno přetaktování, které se ovšem nedaří z důvodu nekompatibility hardwaru. Zároveň vám bios nabízí regulérní volbu.
Druhá možnost (vzhledem k tomu, že jste bios reflashoval) je, že reflash neproběhl korektně, případně nebyla použita správná verze.

[Spartak24]

dobře, dáme tam tedy F2 a snad to pomůže.
ale je to zajímavé, napsalo to totiž flash biosu proběhl úspěšně.
mimochodem, jak vypadá ten HDD?

[Rudy]

Po restartu se to ale může změnit, některý bios sám nastavení neuloží. Psát to mohlo cokoli, důležité je, aby tam byla správná verze.

[Spartak24]

dobře a co ten HDD?

[Rudy]

Pokud dokážete spustit CrystalDiskInfo: http://www.stahuj.centrum.cz/utility_a_ ... ldiskinfo/ (kontrolní utilitu disků) a dát log, milerád se na stav disku podívám.

[Spartak24]

to bohužel nemůžu - není tam už windows.
tohle je výpis ze smartu, je to prý to samé.