Hardware Problem

Dieses Thema im Forum "Mobile / PDA / Notebook" wurde erstellt von Akendo, 17.09.2012.

  1. Akendo

    Akendo 4k3nd0

    Dabei seit:
    05.02.2008
    Beiträge:
    396
    Zustimmungen:
    0
    Hey Leute, seid zwei Tag habe ich ein Problem mit meiner Hardware. Ich bekomme Hardware Expection, was mich etwas irritiert. Diese beziehn sich einerseits auf die zweite Festplatte in meinem Laptop(sdb) anderes Seite auf den Prozessor. Ich bin nur verwundert das diese Problem zum wiederholten aber nicht immer an der gleichen Stelle auftauschen. Ich haben verschieden Tests gemacht und nur sehr sporadisch tausch diese Problem auf. Jedermann eine Idee? Ich hab auch geschaut der Lüfter funktioniert ohne weiteres.

    dmesg:
    Code:
    EXT4-fs (sdb6): Unaligned AIO/DIO on inode 394774 by AioMgr0-N; performance will be poor.
    device vboxnet4 entered promiscuous mode
    CPU2: Core temperature above threshold, cpu clock throttled (total events = 1)
    CPU6: Core temperature above threshold, cpu clock throttled (total events = 1)
    CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
    CPU4: Package temperature above threshold, cpu clock throttled (total events = 1)
    CPU7: Package temperature above threshold, cpu clock throttled (total events = 1)
    CPU3: Package temperature above threshold, cpu clock throttled (total events = 1)
    CPU6: Package temperature above threshold, cpu clock throttled (total events = 1)
    CPU2: Package temperature above threshold, cpu clock throttled (total events = 1)
    CPU5: Package temperature above threshold, cpu clock throttled (total events = 1)
    CPU1: Package temperature above threshold, cpu clock throttled (total events = 1)
    CPU2: Core temperature/speed normal
    CPU6: Core temperature/speed normal
    CPU0: Package temperature/speed normal
    CPU1: Package temperature/speed normal
    CPU4: Package temperature/speed normal
    CPU5: Package temperature/speed normal
    CPU7: Package temperature/speed normal
    CPU3: Package temperature/speed normal
    CPU6: Package temperature/speed normal
    CPU2: Package temperature/speed normal
    [Hardware Error]: Machine check events logged
    ACPI: EC: GPE storm detected, transactions will use polling mode
    CPU6: Core temperature above threshold, cpu clock throttled (total events = 25)
    CPU2: Core temperature above threshold, cpu clock throttled (total events = 25)
    CPU3: Package temperature above threshold, cpu clock throttled (total events = 261)
    CPU7: Package temperature above threshold, cpu clock throttled (total events = 261)
    CPU1: Package temperature above threshold, cpu clock throttled (total events = 261)
    CPU5: Package temperature above threshold, cpu clock throttled (total events = 261)
    CPU2: Package temperature above threshold, cpu clock throttled (total events = 261)
    CPU6: Package temperature above threshold, cpu clock throttled (total events = 261)
    CPU0: Package temperature above threshold, cpu clock throttled (total events = 261)
    CPU4: Package temperature above threshold, cpu clock throttled (total events = 261)
    CPU2: Core temperature/speed normal
    CPU6: Core temperature/speed normal
    CPU3: Package temperature/speed normal
    CPU4: Package temperature/speed normal
    CPU7: Package temperature/speed normal
    CPU0: Package temperature/speed normal
    CPU1: Package temperature/speed normal
    CPU5: Package temperature/speed normal
    CPU6: Package temperature/speed normal
    CPU2: Package temperature/speed normal
    [Hardware Error]: Machine check events logged
    CPU2: Package temperature above threshold, cpu clock throttled (total events = 6496)
    CPU5: Package temperature above threshold, cpu clock throttled (total events = 6496)
    CPU4: Package temperature above threshold, cpu clock throttled (total events = 6496)
    CPU6: Package temperature above threshold, cpu clock throttled (total events = 6496)
    CPU1: Package temperature above threshold, cpu clock throttled (total events = 6496)
    CPU7: Package temperature above threshold, cpu clock throttled (total events = 6496)
    CPU3: Package temperature above threshold, cpu clock throttled (total events = 6496)
    CPU0: Package temperature above threshold, cpu clock throttled (total events = 6496)
    CPU5: Package temperature/speed normal
    CPU1: Package temperature/speed normal
    CPU0: Package temperature/speed normal
    CPU2: Package temperature/speed normal
    CPU6: Package temperature/speed normal
    CPU4: Package temperature/speed normal
    CPU7: Package temperature/speed normal
    CPU3: Package temperature/speed normal
    device vboxnet7 entered promiscuous mode
    CPU3: Package temperature above threshold, cpu clock throttled (total events = 10821)
    CPU2: Package temperature above threshold, cpu clock throttled (total events = 10821)
    CPU0: Package temperature above threshold, cpu clock throttled (total events = 10821)
    CPU6: Package temperature above threshold, cpu clock throttled (total events = 10821)
    CPU4: Package temperature above threshold, cpu clock throttled (total events = 10821)
    CPU5: Core temperature above threshold, cpu clock throttled (total events = 6182)
    CPU1: Core temperature above threshold, cpu clock throttled (total events = 6182)
    CPU7: Package temperature above threshold, cpu clock throttled (total events = 10821)
    CPU5: Package temperature above threshold, cpu clock throttled (total events = 10821)
    CPU1: Package temperature above threshold, cpu clock throttled (total events = 10821)
    CPU3: Package temperature/speed normal
    CPU7: Package temperature/speed normal
    CPU0: Package temperature/speed normal
    CPU2: Package temperature/speed normal
    CPU4: Package temperature/speed normal
    CPU6: Package temperature/speed normal
    CPU5: Core temperature/speed normal
    CPU1: Core temperature/speed normal
    CPU5: Package temperature/speed normal
    CPU1: Package temperature/speed normal
    [Hardware Error]: Machine check events logged
    hrtimer: interrupt took 16522 ns
    ata2.00: exception Emask 0x0 SAct 0x7ff SErr 0x0 action 0x6 frozen
    ata2.00: failed command: WRITE FPDMA QUEUED
    ata2.00: cmd 61/20:00:86:08:97/00:00:12:00:00/40 tag 0 ncq 16384 out
             res 40/00:00:2f:4f:c2/00:00:3a:00:00/00 Emask 0x4 (timeout)
    ata2.00: status: { DRDY }
    ata2.00: failed command: WRITE FPDMA QUEUED
    ata2.00: cmd 61/08:08:9e:33:a0/00:00:12:00:00/40 tag 1 ncq 4096 out
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2.00: status: { DRDY }
    ata2.00: failed command: WRITE FPDMA QUEUED
    ata2.00: cmd 61/08:10:6e:54:53/00:00:13:00:00/40 tag 2 ncq 4096 out
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2.00: status: { DRDY }
    ata2.00: failed command: READ FPDMA QUEUED
    ata2.00: cmd 60/01:18:10:79:5b/00:00:07:00:00/40 tag 3 ncq 512 in
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2.00: status: { DRDY }
    ata2.00: failed command: WRITE FPDMA QUEUED
    ata2.00: cmd 61/38:20:0e:f8:97/00:00:12:00:00/40 tag 4 ncq 28672 out
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2.00: status: { DRDY }
    ata2.00: failed command: WRITE FPDMA QUEUED
    ata2.00: cmd 61/08:28:8e:7f:6f/00:00:12:00:00/40 tag 5 ncq 4096 out
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2.00: status: { DRDY }
    ata2.00: failed command: WRITE FPDMA QUEUED
    ata2.00: cmd 61/58:30:1e:d3:9e/00:00:12:00:00/40 tag 6 ncq 45056 out
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2.00: status: { DRDY }
    ata2.00: failed command: READ FPDMA QUEUED
    ata2.00: cmd 60/08:38:f0:10:e2/00:00:0b:00:00/40 tag 7 ncq 4096 in
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2.00: status: { DRDY }
    ata2.00: failed command: WRITE FPDMA QUEUED
    ata2.00: cmd 61/08:40:b8:84:b3/00:00:12:00:00/40 tag 8 ncq 4096 out
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2.00: status: { DRDY }
    ata2.00: failed command: WRITE FPDMA QUEUED
    ata2.00: cmd 61/20:48:10:93:b5/00:00:36:00:00/40 tag 9 ncq 16384 out
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2.00: status: { DRDY }
    ata2.00: failed command: WRITE FPDMA QUEUED
    ata2.00: cmd 61/10:50:30:e3:b8/00:00:0f:00:00/40 tag 10 ncq 8192 out
             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    ata2.00: status: { DRDY }
    ata2: hard resetting link
    ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata2.00: configured for UDMA/133
    ata2.00: device reported invalid CHS sector 0
    ata2.00: device reported invalid CHS sector 0
    ata2.00: device reported invalid CHS sector 0
    ata2.00: device reported invalid CHS sector 0
    ata2.00: device reported invalid CHS sector 0
    ata2.00: device reported invalid CHS sector 0
    ata2.00: device reported invalid CHS sector 0
    ata2.00: device reported invalid CHS sector 0
    ata2.00: device reported invalid CHS sector 0
    ata2.00: device reported invalid CHS sector 0
    sd 1:0:0:0: [sdb]  
    Result: hostbyte=0x00 driverbyte=0x08
    sd 1:0:0:0: [sdb]  
    Sense Key : 0xb [current] [descriptor]
    Descriptor sense data with sense descriptors (in hex):
            72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
            00 00 00 2e 
    sd 1:0:0:0: [sdb]  
    ASC=0x0 ASCQ=0x0
    sd 1:0:0:0: [sdb] CDB: 
    cdb[0]=0x2a: 2a 00 12 97 08 86 00 00 20 00
    end_request: I/O error, dev sdb, sector 311888006
    sd 1:0:0:0: [sdb]  
    Result: hostbyte=0x00 driverbyte=0x08
    sd 1:0:0:0: [sdb]  
    Sense Key : 0xb [current] [descriptor]
    Descriptor sense data with sense descriptors (in hex):
            72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
            00 00 00 00 
    sd 1:0:0:0: [sdb]  
    ASC=0x0 ASCQ=0x0
    sd 1:0:0:0: [sdb] CDB: 
    cdb[0]=0x2a: 2a 00 12 a0 33 9e 00 00 08 00
    end_request: I/O error, dev sdb, sector 312488862
    sd 1:0:0:0: [sdb]  
    Result: hostbyte=0x00 driverbyte=0x08
    sd 1:0:0:0: [sdb]  
    Sense Key : 0xb [current] [descriptor]
    Descriptor sense data with sense descriptors (in hex):
            72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
            00 00 00 00 
    sd 1:0:0:0: [sdb]  
    ASC=0x0 ASCQ=0x0
    sd 1:0:0:0: [sdb] CDB: 
    cdb[0]=0x2a: 2a 00 13 53 54 6e 00 00 08 00
    end_request: I/O error, dev sdb, sector 324228206
    sd 1:0:0:0: [sdb]  
    Result: hostbyte=0x00 driverbyte=0x08
    sd 1:0:0:0: [sdb]  
    Sense Key : 0xb [current] [descriptor]
    Descriptor sense data with sense descriptors (in hex):
            72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
            00 00 00 00 
    sd 1:0:0:0: [sdb]  
    ASC=0x0 ASCQ=0x0
    sd 1:0:0:0: [sdb] CDB: 
    cdb[0]=0x28: 28 00 07 5b 79 10 00 00 01 00
    end_request: I/O error, dev sdb, sector 123435280
    sd 1:0:0:0: [sdb]  
    Result: hostbyte=0x00 driverbyte=0x08
    sd 1:0:0:0: [sdb]  
    Sense Key : 0xb [current] [descriptor]
    Descriptor sense data with sense descriptors (in hex):
            72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
            00 00 00 00 
    sd 1:0:0:0: [sdb]  
    ASC=0x0 ASCQ=0x0
    sd 1:0:0:0: [sdb] CDB: 
    cdb[0]=0x2a: 2a 00 12 97 f8 0e 00 00 38 00
    end_request: I/O error, dev sdb, sector 311949326
    sd 1:0:0:0: [sdb]  
    Result: hostbyte=0x00 driverbyte=0x08
    sd 1:0:0:0: [sdb]  
    Sense Key : 0xb [current] [descriptor]
    Descriptor sense data with sense descriptors (in hex):
            72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
            00 00 00 00 
    sd 1:0:0:0: [sdb]  
    ASC=0x0 ASCQ=0x0
    sd 1:0:0:0: [sdb] CDB: 
    cdb[0]=0x2a: 2a 00 12 6f 7f 8e 00 00 08 00
    end_request: I/O error, dev sdb, sector 309297038
    sd 1:0:0:0: [sdb]  
    Result: hostbyte=0x00 driverbyte=0x08
    sd 1:0:0:0: [sdb]  
    Sense Key : 0xb [current] [descriptor]
    Descriptor sense data with sense descriptors (in hex):
            72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
            00 00 00 00 
    sd 1:0:0:0: [sdb]  
    ASC=0x0 ASCQ=0x0
    sd 1:0:0:0: [sdb] CDB: 
    cdb[0]=0x2a: 2a 00 12 9e d3 1e 00 00 58 00
    end_request: I/O error, dev sdb, sector 312398622
    sd 1:0:0:0: [sdb]  
    Result: hostbyte=0x00 driverbyte=0x08
    sd 1:0:0:0: [sdb]  
    Sense Key : 0xb [current] [descriptor]
    Descriptor sense data with sense descriptors (in hex):
            72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
            00 00 00 00 
    sd 1:0:0:0: [sdb]  
    ASC=0x0 ASCQ=0x0
    sd 1:0:0:0: [sdb] CDB: 
    cdb[0]=0x28: 28 00 0b e2 10 f0 00 00 08 00
    end_request: I/O error, dev sdb, sector 199364848
    sd 1:0:0:0: [sdb]  
    Result: hostbyte=0x00 driverbyte=0x08
    sd 1:0:0:0: [sdb]  
    Sense Key : 0xb [current] [descriptor]
    Descriptor sense data with sense descriptors (in hex):
            72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
            00 00 00 00 
    sd 1:0:0:0: [sdb]  
    ASC=0x0 ASCQ=0x0
    sd 1:0:0:0: [sdb] CDB: 
    cdb[0]=0x2a: 2a 00 12 b3 84 b8 00 00 08 00
    end_request: I/O error, dev sdb, sector 313754808
    Buffer I/O error on device sdb6, logical block 27875445
    EXT4-fs warning (device sdb6): ext4_end_bio:250: I/O error writing to inode 263778 (offset 282624 size 4096 starting block 39219352)
    sd 1:0:0:0: [sdb]  
    Result: hostbyte=0x00 driverbyte=0x08
    sd 1:0:0:0: [sdb]  
    Sense Key : 0xb [current] [descriptor]
    Descriptor sense data with sense descriptors (in hex):
            72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
            00 00 00 00 
    sd 1:0:0:0: [sdb]  
    ASC=0x0 ASCQ=0x0
    sd 1:0:0:0: [sdb] CDB: 
    cdb[0]=0x2a: 2a 00 36 b5 93 10 00 00 20 00
    end_request: I/O error, dev sdb, sector 917869328
    Buffer I/O error on device sdb6, logical block 103389760
    Buffer I/O error on device sdb6, logical block 103389761
    Buffer I/O error on device sdb6, logical block 103389762
    Buffer I/O error on device sdb6, logical block 103389763
    EXT4-fs warning (device sdb6): ext4_end_bio:250: I/O error writing to inode 274863 (offset 0 size 16384 starting block 114733670)
    sd 1:0:0:0: [sdb]  
    Result: hostbyte=0x00 driverbyte=0x08
    sd 1:0:0:0: [sdb]  
    Sense Key : 0xb [current] [descriptor]
    Descriptor sense data with sense descriptors (in hex):
            72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
            00 00 00 00 
    sd 1:0:0:0: [sdb]  
    ASC=0x0 ASCQ=0x0
    sd 1:0:0:0: [sdb] CDB: 
    cdb[0]=0x2a: 2a 00 0f b8 e3 30 00 00 10 00
    end_request: I/O error, dev sdb, sector 263775024
    Buffer I/O error on device sdb6, logical block 21627972
    Buffer I/O error on device sdb6, logical block 21627973
    EXT4-fs warning (device sdb6): ext4_end_bio:250: I/O error writing to inode 274863 (offset 16384 size 8192 starting block 32971880)
    ata2: EH complete
    
    Ein Blick in die /var/log/mcelog zeigt folgendes auf:
    Code:
    HARDWARE ERROR. This is *NOT* a software problem!
    Please contact your hardware vendor
    MCE 0
    CPU 6 THERMAL EVENT TSC 13f614ccb92 
    TIME 1347880225 Mon Sep 17 13:10:25 2012
    Processor 6 heated above trip temperature. Throttling enabled.
    Please check your system cooling. Performance will be impacted
    STATUS 88020003 MCGSTATUS 0
    MCGCAP c09 APICID 5 SOCKETID 0 
    CPUID Vendor Intel Family 6 Model 42
    HARDWARE ERROR. This is *NOT* a software problem!
    Please contact your hardware vendor
    MCE 1
    CPU 2 THERMAL EVENT TSC 13f614d288e 
    TIME 1347880225 Mon Sep 17 13:10:25 2012
    Processor 2 heated above trip temperature. Throttling enabled.
    Please check your system cooling. Performance will be impacted
    STATUS 88020003 MCGSTATUS 0
    MCGCAP c09 APICID 4 SOCKETID 0 
    CPUID Vendor Intel Family 6 Model 42
    HARDWARE ERROR. This is *NOT* a software problem!
    Please contact your hardware vendor
    MCE 2
    CPU 6 THERMAL EVENT TSC 13f61704b62 
    TIME 1347880225 Mon Sep 17 13:10:25 2012
    Processor 6 below trip temperature. Throttling disabled
    STATUS 88030002 MCGSTATUS 0
    MCGCAP c09 APICID 5 SOCKETID 0 
    CPUID Vendor Intel Family 6 Model 42
    HARDWARE ERROR. This is *NOT* a software problem!
    Please contact your hardware vendor
    MCE 3
    CPU 2 THERMAL EVENT TSC 13f61709ae0 
    TIME 1347880225 Mon Sep 17 13:10:25 2012
    Processor 2 below trip temperature. Throttling disabled
    STATUS 88030002 MCGSTATUS 0
    MCGCAP c09 APICID 4 SOCKETID 0 
    CPUID Vendor Intel Family 6 Model 42
    HARDWARE ERROR. This is *NOT* a software problem!
    Please contact your hardware vendor
    MCE 4
    CPU 2 THERMAL EVENT TSC 295bad2ea7a 
    TIME 1347880225 Mon Sep 17 13:10:25 2012
    Processor 2 heated above trip temperature. Throttling enabled.
    Please check your system cooling. Performance will be impacted
    STATUS 88020003 MCGSTATUS 0
    MCGCAP c09 APICID 4 SOCKETID 0 
    CPUID Vendor Intel Family 6 Model 42
    HARDWARE ERROR. This is *NOT* a software problem!
    Please contact your hardware vendor
    MCE 5
    CPU 6 THERMAL EVENT TSC 295bad34ad8 
    TIME 1347880225 Mon Sep 17 13:10:25 2012
    Processor 6 heated above trip temperature. Throttling enabled.
    Please check your system cooling. Performance will be impacted
    STATUS 88020003 MCGSTATUS 0
    MCGCAP c09 APICID 5 SOCKETID 0 
    CPUID Vendor Intel Family 6 Model 42
    HARDWARE ERROR. This is *NOT* a software problem!
    Please contact your hardware vendor
    MCE 6
    CPU 6 THERMAL EVENT TSC 295baf62ce6 
    TIME 1347880225 Mon Sep 17 13:10:25 2012
    Processor 6 below trip temperature. Throttling disabled
    STATUS 88030002 MCGSTATUS 0
    MCGCAP c09 APICID 5 SOCKETID 0 
    CPUID Vendor Intel Family 6 Model 42
    HARDWARE ERROR. This is *NOT* a software problem!
    Please contact your hardware vendor
    MCE 7
    CPU 2 THERMAL EVENT TSC 295baf67f66 
    TIME 1347880225 Mon Sep 17 13:10:25 2012
    Processor 2 below trip temperature. Throttling disabled
    STATUS 88030002 MCGSTATUS 0
    MCGCAP c09 APICID 4 SOCKETID 0 
    CPUID Vendor Intel Family 6 Model 42
    HARDWARE ERROR. This is *NOT* a software problem!
    Please contact your hardware vendor
    MCE 8
    CPU 5 THERMAL EVENT TSC 6260dc8111d 
    TIME 1347880225 Mon Sep 17 13:10:25 2012
    Processor 5 heated above trip temperature. Throttling enabled.
    Please check your system cooling. Performance will be impacted
    STATUS 88020003 MCGSTATUS 0
    MCGCAP c09 APICID 3 SOCKETID 0 
    CPUID Vendor Intel Family 6 Model 42
    HARDWARE ERROR. This is *NOT* a software problem!
    Please contact your hardware vendor
    MCE 9
    CPU 1 THERMAL EVENT TSC 6260dc81fd1 
    TIME 1347880225 Mon Sep 17 13:10:25 2012
    Processor 1 heated above trip temperature. Throttling enabled.
    Please check your system cooling. Performance will be impacted
    STATUS 88020003 MCGSTATUS 0
    MCGCAP c09 APICID 2 SOCKETID 0 
    CPUID Vendor Intel Family 6 Model 42
    HARDWARE ERROR. This is *NOT* a software problem!
    Please contact your hardware vendor
    MCE 10
    CPU 5 THERMAL EVENT TSC 6260dea0bd1 
    TIME 1347880225 Mon Sep 17 13:10:25 2012
    Processor 5 below trip temperature. Throttling disabled
    STATUS 88030002 MCGSTATUS 0
    MCGCAP c09 APICID 3 SOCKETID 0 
    CPUID Vendor Intel Family 6 Model 42
    HARDWARE ERROR. This is *NOT* a software problem!
    Please contact your hardware vendor
    MCE 11
    CPU 1 THERMAL EVENT TSC 6260dea13f9 
    TIME 1347880225 Mon Sep 17 13:10:25 2012
    Processor 1 below trip temperature. Throttling disabled
    STATUS 88030002 MCGSTATUS 0
    MCGCAP c09 APICID 2 SOCKETID 0 
    CPUID Vendor Intel Family 6 Model 42
    
    Ich hab auch im Internet einige Beitrage dazu gefunden, die Antwort des LinuxQuestions passt aber nicht wirklich. Ich hab an dem Hardware Setup nicht geändert sein 1 Jahr und es lief immer ohne Probleme.

    Ich werde nun noch ein memtest+ laufen lassen.


    so weit
    Akendo
     
  2. Anzeige

    Schau dir mal diese Kategorie an. Dort findest du bestimmt etwas.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  3. Psyjo

    Psyjo Routinier

    Dabei seit:
    15.11.2005
    Beiträge:
    259
    Zustimmungen:
    0
    Ort:
    Hinter'm Berg
    Viel wichtiger als die MCE scheint mir die offenbar defekte Platte zu sein.
    Wegen der MCE könnte ein Microcodeupdate der CPU helfen. Diese Updates sind meiestens in BIOS-Updates enthalten.

    [edit]

    Da fällt mir ein: wenn die Platte lustige Sachen auf den Bus schiebt kann das unter Umständen auch die CPU verwirren.
     
  4. Akendo

    Akendo 4k3nd0

    Dabei seit:
    05.02.2008
    Beiträge:
    396
    Zustimmungen:
    0
    Das BIOS ist aber schon auf dem letzten Stand, ich habe auch schon eine neue Festplatte bestellt. Brauch meine alte Festplatte noch zum Arbeiten. Was meinst du ist das Problem an der Platte? Weshalb taucht das Problem dann auf, wenn ich etwas schreibe aber nicht wenn ich Daten lesen? Ich hatte gerade erst alle Daten gesichert gehabt und das sogar noch mit dd, dennoch war nicht zu sehen.
    Mir waere eine eindeutige Fehlererkennung lieb. Ich werde die Platte sofort austuaschen wenn ich kann, aber ich wuerde gerne erstmal das Problem verstehen wollen.

    so far
    akendo

    PS: Hast du vielleicht ein Link oder sowas wo ich das nach lesen kann (Also wenn die HDD lustige Sachen in den Bus wift)
     
Thema:

Hardware Problem

Die Seite wird geladen...

Hardware Problem - Ähnliche Themen

  1. W-Lan Installationsprobleme - Hardware_erkannt - Treiberprobleme (Fedora 10)

    W-Lan Installationsprobleme - Hardware_erkannt - Treiberprobleme (Fedora 10): Guten Tag, ich möchte meine W-Lan Karten Treiber gerne unter Fedora 10 installieren (es ist eine Trendware TEW-423PI), nachdem ich mit...
  2. Hardware Problem

    Hardware Problem: Hallo! Da ich kein anderes, halbwegs passendes Suborum gefunden hab, poste ich einfach mal hier. Es sieht so aus, als hätte mein Rechner...
  3. FTP-Übertragung zu langsam, Hardwareproblem?

    FTP-Übertragung zu langsam, Hardwareproblem?: Hallo, ich habe hier einen alten Rechner stehen, den ich als FTP-Fileserver nutze. Allerdings habe ich das Problem, dass die Datenübertragung...
  4. Probleme mit Hardware RAID

    Probleme mit Hardware RAID: Hallo mitnander... Also, ich hab jetz nen Promise SuperTrak100 RAID-Controller in meinem Server. An den sind 6 Samsung SP2514N Platten (á 250...
  5. Installationsprobleme/Hardwareprobleme !!!

    Installationsprobleme/Hardwareprobleme !!!: Installations- / Hardwareprobleme !!! So nun brauch ich auch mal eure Hilfe, da ich selber nun mittlerweile mit meinem Latain am Ende bin und...